BOSTON, MAY 21, 2026
PRODUCT ACTIVE
Vault Knowledge MCP: Design Lock
─ METHODS ─
| TASK | AGENT / TOOL | MODEL / COST |
|---|---|---|
| protocol design | MCP SDK | open-source / $0 |
| vault read-layer | Code Brain (concept_edges + JSONL) | Sonnet 4.6 (HybridRouter) |
| design lock | spec authoring + Notion review | $0 |
─ EXPLANATION ─
What is this?
A Model Context Protocol that exposes Sean’s vault as a queryable agent surface. Design-locked May 21, 2026; ship-target ~June 4. The architecture argument lives at /architecture/vault-scorecard/ (Phase 3c.2). This row tracks the shipped artifact (the MCP transport + tool surface), not the thesis.
Why this approach?
The vault is the only PM vault that passes the agent-infrastructure tests. The MCP wraps it. Recruiter from Glean lands on /architecture/vault-scorecard/ → reads the scoreboard → clicks through to the ledger row → sees the ship date. The two surfaces close the loop: architecture argues, ledger ships.
What would break?
If the MCP HTTP transport spec revs between design-lock and ship, the design re-opens. If concept_edges hits the 47-edge production limit (likely), the read-layer paginates or the vault sharding strategy lands first.
What did I learn?
Design-lock is the artifact, not the code. Locking the design on May 21 with a June 4 ship target gives 14 days of runway: enough for a real implementation cycle without scope drift. The pattern: lock at T-14, ship at T-0.
─ WHAT THIS DOESN'T YET DO ─
- Design only at this point: the read-layer is wired to concept_edges but the MCP transport layer is stubbed.
- The five-Nate-test scoreboard pass depends on the Audit pillar, which itself depends on the queryable JSONL filesystem layer landing first.