Exploring the echoes reverberating through time left by the technology of yesterday as we embrace the technology of tomorrow.
GTC 2026 anchors the week. Vera Rubin, a $1T order book through 2027, and a partnership map from Uber to Disney to Eli Lilly. Mistral ships Small 4 and announces Forge for training-on-your-own-data. AI hits 25% of March layoffs. The EU's child-safety amendment lands.
What I actually run, in March 2026, four boxes, a NAS, a small set of services, and the open-weights models that do the daily work. Practical and concrete; this is the stack as it sits, not the stack as I'd pitch it.
You've inherited a 1,500-line values.yaml. The fix isn't refactoring it in place, it's the six-step migration to a DaC shape: catalog, cluster, identify, push down, version, ship. Here's the walkthrough, concrete enough to mirror.
Every vendor is shipping a personal AI now. Almost none of them can answer the basic ownership questions, who owns the model, the memory, the patterns. Without that story, personal AI is a marketing label on a vendor relationship.
Atlassian and Block stack the largest AI-cited cuts of the cycle, the Challenger numbers put AI at 25% of US March layoffs, Anthropic sues over a Pentagon supply-chain-risk designation while Google quietly takes the contract, and NVIDIA opens GTC with $1T in Blackwell-plus-Rubin orders booked.
The 2026 audit conversation about AI usage has gotten sharp. The questions are sophisticated, the evidence asks are specific, and most shops can't produce what's being asked for. Here's what the conversation actually sounds like and where the gap sits.
Article five of my personal coding constitution: every action that mutates state must leave evidence. The trail isn't for the auditors. It's the thing that earns me the right to keep going.
A year ago I wrote about treating each AI interaction as its own bounded unit, own context, own audit, own memory boundary. Twelve months of building inside that pattern is enough material to grade what held up, what didn't, and what I missed entirely.
MWC Barcelona puts agentic AI in every booth, GPT-5.4 ships mid-week, Oracle telegraphs the largest layoffs in its history to fund AI capex, and the EU Council adds non-consensual deepfakes to the AI Act's prohibited list. The week the cuts started being about funding compute, not replacing workers.
Starter notes for the practitioner who wants to build their own personal AI in 2026. The substrate is finally ready. Hardware, model, MCP-or-not, memory, privacy boundaries, the pragmatic shape of 'if I were starting today.'
MCP won the integration layer. That doesn't mean every tool integration in 2026 should be MCP. The honest architecture is MCP for 80% of cases plus a small set of deliberate escape hatches for the 20% where the protocol shape doesn't fit. Worth being specific.
The recurring laptop-and-Studio model rundown, March 2026 edition. Llama 4, Qwen 3, Mistral 3, Kimi K2 Thinking, and the small distills, what runs where, what it's actually good for, what I'd reach for first.
