Field guides for a subject that won’t sit still.

Own the model, own the tools, own the stack. In images, audio, and embeddings, open runs lighter than the coding models — and stands at the frontier.

Unit three of the local-models cluster: open models for image generation, speech in and out, and the embedding layer behind local RAG — with the license traps that bite hardest in media, the data-sovereignty payoff of a private knowledge layer, and an honest account of the one premium ceiling closed still holds.

Own the model, then own the tools. A self-hosted coding agent keeps your source on your machine — and the open stack is closer to the frontier than most people think.

Unit two of the local-models cluster: the open coding models and how to read their benchmarks, the open agents that drive them, the fully-local stack where your code never leaves the box, and an honest account of where open still trails the closed frontier.

The frontier is roughly four months from your own hardware. Owning the model — not renting it — is the sovereign move.

Unit one of the local-models cluster: what 'open' actually buys you (open-weight vs open-source, the licenses that bite, the closing gap), how a model is shaped (parameters, quantization, context, temperature), and why running it locally is a question of authority, not just cost.

Own your knowledge in files you can read and ship — instead of renting it inside a vendor's catalog.

Google's Open Knowledge Format formalizes the LLM-wiki pattern into a portable bundle of Markdown files. What the spec actually requires (one field), how to build and validate a conformant bundle, the own-versus-rent argument for keeping your knowledge layer in version control, where OKF sits beside MCP and RAG, and an honest account of what its minimalism leaves unsolved.

A prompt says what you want, once. A skill says how to do it, every time — and travels to any agent that reads the open format.

A skill is a folder that teaches an agent how to do one job the right way — and since December 2025, an open format that runs unchanged across Claude, Codex, Gemini, and Copilot. Build one from an empty folder: the SKILL.md, progressive disclosure, the description that does the triggering, when to split a reference file, and the decision rule for when a skill beats a prompt or a server.

AI levels some fields and steepens others. The difference is who has to supply the judgment.

Two careful bodies of research on AI at work reach opposite conclusions — compression that lifts novices, and returns that reward expertise. The reconciliation is one question you can ask of any task: who supplies the judgment? With the jagged frontier, the verification burden, persuasion bombing, and an honest account of what we still cannot say.

The through-line is deletion: instructions written for weaker models now work against this one.

A working adaptation of Anthropic's official guide — the behavioral deltas from Opus 4.8, effort calibration, long runs and their edge cases, memory, and the drop-in blocks worth keeping verbatim.

The leverage point moved: stop prompting agents, and design the systems that prompt them.

From the viral June 2026 discourse to a buildable discipline — the lineage, the loop contract, the six building blocks, independent verification, memory, hard stops, and the three risks that sharpen as loops improve.