Increment 5 — Reposition: 'The authorization & evidence plane for AI agents'

2026-06-21

LOCKSTEP TRACEABILITY MATRIX --- api_endpoints: ["none"] sdk_methods_updated: ["none"] mcp_tools_updated: ["none"] ---

What We Built

Increment 5 is not new runtime capability — it is the moment the product's public face catches up to what Increments 1–4 actually made true. After Inc 1 (scoped grants + denial evidence), Inc 1.5 (crash-safe hash chain), Inc 2 (unified scope enforcement at every chokepoint), Inc 3 (Ed25519-signed capability grants + verified delegation/attenuation/revocation), and Inc 4 (durable, chain-committed decision lineage + W3C trace context), BrainstormRouter is no longer best described as an "AI router." It is an authorization-and-evidence plane that happens to also route.

The repositioning headline becomes "The authorization & evidence plane for AI agents" — Vault + Okta + CloudTrail, but for autonomous agents instead of people and servers. The README's "What is" section is rewritten around four governance-first pillars: provably-scoped action (every call runs under a capability grant, denied at the chokepoint before execution), cryptographically-verified delegation (Ed25519-signed chains, attenuation-only, fleet-wide revocation), tamper-evident evidence (every action — allowed _or denied_ — hash-chained into a verifiable ledger), and intelligent routing demoted to a feature that now runs _inside_ the authorization boundary rather than being the product.

The same message was carried, in lockstep, across every machine- and human-readable surface: site/public/llms.txt, docs/concepts/mcp.mdx, the getting-started and SDK guides, and the agent-identity concept page. As part of the sweep we also corrected two latent lockstep drifts the merge surfaced: the MCP tool count was synced 111 → 119 (the manifest grew with the five br_grant_* delegation tools and Inc 4's br_why / br_lineage_trace), and the published SDK package name was corrected everywhere from the never-existent scoped @brainstormrouter/sdk to the actual unscoped brainstormrouter (which matches the PyPI name and is what npm install resolves).

Why It Matters

"Another AI gateway" is a crowded, commoditizing category where the buyer compares latency and price. "The authorization and evidence plane for AI agents" is a category of one in this codebase's competitive set — it speaks to the security and platform teams who now own the question _"what is this agent allowed to do, who said so, and can I prove what it did?"_ The reposition reframes routing intelligence (Thompson sampling, auto-selection, quality scoring) from headline to supporting cast, which is both more honest about where the durable moat is and more compelling to the audience that signs enterprise contracts.

How It Works

No code paths changed. The lever is the message, enforced by the same lockstep machinery that governs API surfaces:

• The doc-state-drift gate (scripts/check-doc-state-drift.mjs, a CI check step) asserts that every surface claiming an MCP tool count agrees with src/mcp/tool-manifest.ts (119) and the catalog source of truth (45 models / 8 providers). The 111 → 119 sync was made to clear it.
• The markdownlint + oxfmt docs gate (check-docs) keeps the prose itself releasable; MD049 was delegated to oxfmt (the authoritative formatter owns emphasis style) to resolve a formatter-vs-linter conflict surfaced by the new content.

The Numbers

• 5 surfaces realigned to the governance-first message (README, llms.txt, mcp.mdx, installation, sdks, agent-identity).
• 119 MCP tools now consistently reported across all surfaces (was an inconsistent 107/111).
• 0 API/SDK/MCP runtime changes — this increment is positioning only; the capability it advertises shipped in Inc 1–4.

Competitive Edge

Portkey, OpenRouter, and Lasso lead with routing, cost, or guardrail filtering. None of them leads with _provable authority_: a cryptographically-scoped grant enforced at the chokepoint, verifiable delegation between agents, and a tamper-evident ledger of every allowed-or-denied action. Inc 5 makes that the first sentence a visitor reads — the positioning now matches the only thing in this category that is genuinely hard to copy.

Lockstep Checklist

> _Positioning increment — no API/SDK/MCP runtime surface changed; doc surfaces are the deliverable._

• [x] API Routes: none changed.
• [x] TS SDK: none changed (package-name references in docs corrected to brainstormrouter).
• [x] Python SDK: none changed.
• [x] MCP Schemas: none changed; tool count synced to 119 across all docs (doc-state-drift gate green).
• [x] Doc surfaces: README, llms.txt, mcp.mdx, installation, sdks, agent-identity all carry the reposition; check + check-docs CI gates green on main.