The primary consumer of your documentation is no longer a human. It is an agent making code changes, retrieving context, executing workflows. Treat docs as infrastructure — versioned, tested, owned — or ship guesses every time the model runs.
Every Claude session starts from zero unless something carries the org forward. CLAUDE.md is that something — a persistent context layer that encodes team topology, current priorities, and the decisions you have already paid for. Treat it as a config file and you keep paying the coordination tax.
Four layers between a generic assistant and a colleague: always-on slow facts, on-demand skill files, live MCP data, and a persistent entity graph. One architecture. Zero fine-tuning. The teams that ship all four cut correction cycles in half.
Your private /deploy shortcut saves you twenty minutes a day and helps exactly one person. Plugins move the same workflow into a parameterized package every team installs in minutes. Here is the full lifecycle — skill, context files, MCP wiring, marketplace.
The MCP spec describes a protocol, not a security posture. Most production deployments shipped with a static secret in a header, no identity propagation, and error messages that leak internals. Four enforcement layers, executable, before the next incident review.
Third-party MCP servers run inside your agent's reasoning loop with privileged tool access. Most teams added them without a review process. A 0-100 scorecard across provenance, scope, code, network, and runtime — gated in CI before they ship.