The EU AI Act deadline moved: the engineering did not
What the EU AI Act asks engineers to build — risk classification, Article 50 transparency, data lineage and inference logs — and why a moved deadline is a bad reason to start.
→ read_post()Long-ish posts about work we shipped — the decisions, the bugs, the numbers. No think-pieces, no listicles.
What the MCP 2026-07-28 revision requires, how to move per-session state out of a production server, and an honest account of what the migration costs.
What the EU AI Act asks engineers to build — risk classification, Article 50 transparency, data lineage and inference logs — and why a moved deadline is a bad reason to start.
→ read_post()Prefix caching is shipped as a throughput switch, but it is a cache with a hit rate, an eviction policy and a cold path that quietly governs your p99 latency.
→ read_post()Why upgrading your embedding model stops paying, what a cross-encoder recovers that a single vector cannot, and how to size a reranker candidate budget on your own data.
→ read_post()The arithmetic behind self-hosting versus an API, what low-precision serving actually buys, and which inference optimisations survive the next vendor price cut.
→ read_post()Why text-to-SQL still returns confidently wrong numbers in production, what a governed semantic layer has to contain to stop it, and how to evaluate the result honestly.
→ read_post()What LoCoMo actually scores, why the published memory numbers moved by 25 points, and why write policy and invalidation are the parts no benchmark grades.
→ read_post()Why speculative decoding speedups measured at batch size one shrink or invert under continuous batching, what acceptance rate actually controls, and how to decide.
→ read_post()Hi, I'm the ImmovableTech assistant. Ask me about our services, past projects, or how to get in touch.