The agent plane

An agent asked "what's blocked on iOS?" shouldn't have to swallow a four-thousand-line JSON file. The MCP server exposes the map as tools instead: list and filter nodes, open one with its neighbors and history, fetch a map, the changelog or the backlog. Every screen a human sees has an agent-shaped twin, built from the same functions.

Writing goes through a gate. Create a node, patch it, add an edge: the change is applied in memory, the matching journal events are derived, and the whole thing is validated. Any error, and nothing is written. The agent gets the exact problems back instead of a broken map.

Quality lives here too. A family of Kritik tools lets an agent read the audit matrix, list findings, check signals and spot regressions between two audits, so "is this screen getting better?" becomes a question an agent can answer.

It runs wherever your map does. Point it at the bundle in your repo, or at a hosted Arkaik project with an agent token. Same catalog, same rules. Setup is a single npx line.