Architectural Decision Records (ADR) Index — DERIVED VIEW
🤖 GENERATED FILE — DO NOT EDIT. Regenerate with python3 scripts/derive-adr-index.py; verify with --check. The individual ADR files’ own Status lines are the single source of truth; this index is a build artifact (Architectural Review 2026 workstream B4, closes #1455). Per the B3 rule: counts here TRIAGE, they never DISPOSE — check the live document before treating any status as the whole story.
Total ADR files: 83 · Numbering gaps (never filed): 067, 068 · Counts by status: Accepted: 57 · Proposed: 11 · Dormant (Proposed, unratified): 2 · Superseded: 9 · Other: 4
Accepted (57)
- ADR-001: MCP Integration Pilot — Accepted · July 3, 2025
- ADR-002: Claude Code Integration — Accepted · July 6, 2025
- ADR-004: Action Humanizer Integration — Accepted
- ADR-005: Eliminate Dual Repository Implementations via Pattern #1 Migration — Accepted · July 14, 2025
- ADR-006: Standardize Async Session Management Pattern — Accepted · July 14, 2025
- ADR-008: MCP Connection Pooling Strategy for Production — Accepted · July 20, 2025
- ADR-009: Health Monitoring System Design — Accepted · July 20, 2025
- ADR-010: Configuration Access Patterns — ✅ Implemented (October 2025, Phase 3)
- ADR-011: Test Infrastructure Hanging Fixes — Accepted - 2025-07-30
- ADR-012: Protocol-Ready JWT Authentication — ACCEPTED · 2025-08-10
- ADR-017: Spatial-MCP Refactoring — Implemented · August 17, 2025 (Documenting August 12, 2025 decision)
- ADR-022: Autonomy Experimentation — Accepted · August 17, 2025
- ADR-023: Test Infrastructure Activation Pattern — Accepted · August 20, 2025
- ADR-027: Configuration Architecture - User vs System Separation — Accepted · 2025-08-30
- ADR-029: Domain Service Mediation Architecture — Accepted (September 12, 2025)
- ADR-030: Configuration Service Centralization — Accepted (September 12, 2025)
- ADR-031: MVP Redefinition - Core vs Feature Distinction — Accepted
- ADR-032: Intent Classification as Universal Entry Point — Accepted & Validated (GREAT-4E Phase 4 - October 6, 2025)
- ADR-033: Multi-Agent Scripts Deployment — Accepted
- ADR-034: Plugin Architecture Implementation — Implementation Status: Complete (October 2-4, 2025)
- ADR-035: The Inchworm Protocol — Accepted · September 20, 2025
-
- ADR-037: Test-Driven Locking Strategy — Accepted · September 26, 2025
- ADR-038: Spatial Intelligence Architecture Patterns — Accepted · AMENDED 2026-07-30 (Amendment A, Arch) — decision stands; verification claims corrected. Read Amendment A at the foot of this file before citing any operational claim. · September 30, 2025 (Updated: October 1, 2025)
- ADR-039: Canonical Handler Fast-Path Pattern — ✅ Approved and Implemented · October 7, 2025
- ADR-040: Local Database Per Environment Architecture — Accepted · 2025-11-01
- ADR-041: Domain Primitives - Item and List Refactoring — ✅ Implemented (November 2025)
- ADR-042: Mobile Strategy - Progressive Enhancement — Accepted
- ADR-043: Application-Layer Stored Procedures Pattern — Accepted · November 22, 2025
- ADR-044: Lightweight RBAC vs Traditional Role-Permission Tables — ✅ Accepted · November 22, 2025
- ADR-045: Object Model - “Entities Experience Moments in Places” — Accepted · November 28, 2025
- ADR-050: Conversation-as-Graph Model — Accepted · January 21, 2026 (Accepted)
- ADR-051: Unified User Session Context — AMENDED — Completed with scope-clarification (Phase 2/3, 2026-05-16) · 2026-01-13 (original) / 2026-05-16 (amendment)
- ADR-052: Standardize on Tool-Based MCP Implementation — Accepted · October 17, 2025
- ADR-053: Trust Computation Architecture — ACCEPTED · 2026-01-13
- ADR-054: Cross-Session Memory Architecture — APPROVED · 2026-01-13
- ADR-055: Object Model Implementation - Core Grammar & Lens Infrastructure — Accepted (Implemented January 21, 2026) · January 19, 2026
- ADR-057: CommandRegistry - Unified Command Discovery and Routing — APPROVED (Phase 3 Implementation In Progress) · 2026-01-22
- ADR-058: Multi-Tenancy Isolation Architecture — APPROVED · 2026-01-30
- ADR-059: Workflow Dispatcher and Offer System Consolidation — APPROVED (2026-03-19, Chief Architect) · 2026-03-19
- ADR-060: Floor-First Routing Architecture — Approved · 2026-03-19
- ADR-061: LLM-Touch Boundary Enforcement — Two-Layer Detection with Floor as De-Facto Ethics Layer — Ratified v1.0 (PM verbal ratification 2026-05-03); v1.1 amendment 2026-05-15 (output-side companion shipped per #1017 — see §”Amendment 2026-05-15”); v1.2 amendment 2026-11-13 (Layer 1 removed, #2364; effective on merge — see §”Amendment 2026-11-13”) · 2026-04-28 (v0.1) → 2026-04-30 (v1.0 — Lead Dev fixes + CEO calibration reframe applied) → 2026-05-03 (verbally ratified) → 2026-05-04 (status block updated) → 2026-05-15 (v1.1 — output-side companion amendment per #1017)
- ADR-069: Domain Concept Projection Contract — System of Record vs. In-Process Working State — v0.2 (RATIFIED 2026-06-12) — Lead-Dev-authored from the #1207 implementation; Architect ratified the carve (memo ~19:35 “strong concur”) and the artifact (memo ~22:30 “v0.1 clean, ratified”). v0.2 folds in Arch’s three optional polish edits (D6 Intent-shape sketch · Source-incidents tracer · D5 negative-pattern made code-explicit). · 2026-06-12
- ADR-070: MCP-Consumer Connector Architecture — v0.1 (filed 2026-06-15) — Architect-authored; PM-ratified direction (2026-06-14: connectors move to MCP-consumer; staying native is “dated and clunky”); gates Lead Dev WS-1..9 decomposition on the RECONNECT sprint (#1220 umbrella + 12 issues). Amended: A (2026-07-10, logical server key) and B (2026-10-13, one credential resolver per connector). · 2026-06-15
- ADR-071: User-Auth Anchoring Pattern for Content Stores — v0.1 (Lead-authored 2026-06-15) — RATIFIED by Arch 2026-06-15 (“clean fold; every guidance point folded faithfully”; 2 minor cross-refs folded below). Grounded in the #1241 content-anchoring audit (PM-directed systemic flag 2026-06-14; Arch D1 ruling + D1–D7 grounding-confirm 2026-06-15). Companion to ADR-058 (Multi-Tenancy Isolation) at the content altitude — same make-impossible-by-construction shape, one layer down from credentials. · 2026-06-15
- ADR-072: Skill-Routing Architecture — Fluid Model with Defense-in-Depth — ACCEPTED (v0.2) — D1–D4 Arch-ratified in-lane; D5 ratified 2026-06-17 with CXO + HOST trust-lens folded (both aligned: gate Piper-initiated, never user-reaching-for-own; + HOST’s consequential-action carve-out + transparency-when-gated) · 2026-06-17
- ADR-073: No Destructive Git in PM’s Main Checkout Working Tree — ACCEPTED — PM-approved 2026-06-27. The operational rule has been in force via the CLAUDE.md ⚠️ HARD RULE callout since 2026-06-21 (
6d1292d09); this ADR is the formal decision record + rationale for the archive. · 2026-06-27
- ADR-074: Encryption at Rest Strategy — ACCEPTED (documenting already-shipped work) — written 2026-07-05 (Lead Dev) as part of #358’s closure, retroactively recording the design + decisions behind work implemented 2026-06-20 and live-verified on alpha 2026-06-25. No new decision is made here; this is the durable record #358 asked for.
- ADR-075: Configuration / Personalization Ownership — Per-User Scoping for Instance Config — v0.2 ACCEPTED (2026-07-06) — Arch-authored; CXO + HOST trust-lens both PASS and folded (OQ-3 fully resolved); cut ACCEPTED per HOST ratification + CXO sign-off. (v0.1 was DRAFT-for-trust-lens.) Grounded in #1366 (PM-caught 2026-07-06:
PIPER.user.md is a single unscoped instance-level file that leaks PM’s personalization + GitHub default-repo to every user on the shared alpha.pipermorgan.ai instance). Component A (github default-repo scoping) shipped earlier this session (Lead, f04cbeea6/1784ae017). Component B (system-prompt personalization) — IMPLEMENTED, BUILD-ratified, live-verified, and CLOSED (Lead, #1373, closed 2026-07-07): owner_id-scoped store (personalization_contexts, migration d075persctx), principal resolution wired into every confirmed request-path caller, seeded neutral-default persona + one-time first-response notice per CXO’s OQ-3 spec, D5 enforcement guard. Arch’s BUILD ratification (2026-07-07): clean against D1-D5 + OQ-1/2/3, and structurally “impossible-by-construction” for the #1366 leak — the FK-constrained, always-scoped repository methods mean an unscoped read/write can’t be expressed, not merely that it’s avoided. Live-verified 2026-07-07 against a real local Postgres (direct-service verification, not mocked): distinct-principal scoping, lazy-seeding, and the one-time notice all confirmed against real DB rows. OQ-1 (dedicated store, not personality_profiles) and OQ-2 (default_labels stays with ConnectorConfigService, not a new store) both decided at build time as the ADR reserved. Component C (#1260 mechanism repoint) deferred as a smaller follow-up per D6 — the only open item, tracked separately. Completes the server-owned-state family: ADR-070 (per-user connector bindings), ADR-071 (per-user content stores), ADR-075 (per-user config/personalization) — all three now ratified AND implemented. · 2026-07-06
- ADR-076 — Usage-Cap Enforcement (Alpha Load Backstop) — ACCEPTED (v0.1, 2026-07-06) — Arch-authored; HOST trust-lens PASS folded; implemented and closed (#1370,
01c28848b, 2026-07-06; BUILD-ratified clean against D1-D6 by Arch 2026-07-07; live-verified 2026-07-07 against a real server + real Redis — rate limit, concurrency cap, and fail-closed all hit their exact documented boundary and response shape) — web/middleware/usage_cap_middleware.py, 12 unit tests. Fully closed, no open items.
- ADR-077 — Routing-Integrity Contract (Action↔Handler Reachability) — ACCEPTED (v0.1, 2026-07-09) — Arch-authored; formalizes the #1283 AC-4 SSOT ruling (2026-07-08) after Lead’s static audit + behavioral probe validated the approach. Lead builds the enforcement.
- ADR-079 — Owner-Scoping Integrity Contract (unscoped reads impossible-by-construction, mechanically enforced) — ACCEPTED (v0.1, 2026-07-16) — Arch-authored, on the integrity authority PM delegated + Lead’s confirmation that the #1419 multi-tenancy audit’s scope is systemic. Synthesizes already-accepted per-feature owner-scoping decisions into one contract + its mechanical enforcement. HOST trust-lens welcome (this is a trust-boundary contract) — informative, not gating, since the constituent decisions are already accepted. PM retains veto.
- ADR-080 — LLM decides meaning; code decides permission, checks meaning against real data, and shows before it acts — ACCEPTED (2026-10-06). Arch-authored; PM confirmed the division on 2026-10-06 (via Exec): *“I agree with the division Arch laid
- ADR-081: GitHub identity — whose token serves a request, which app mints it, and who else may act — ACCEPTED, 2026-10-24 (Arch-authored, on xian’s go-ahead in the Production-map rulings, 2026-10-24 17:28: “one ADR on GitHub identity”). D3 is accepted on the condition that its compatibility check passes; if it fails, D3’s fallback governs. 2026-11-11: the condition is met (Arch, from #2174’s two runs); D3 governs and the fallback does not apply. See “D3’s check, result” under D3. Finding F5 in
docs/internal/planning/production-map-review-round2-2026-10-23.md.
- ADR-082: The offered-connector set is the one gate — ACCEPTED, 2026-11-06 (Arch-authored). This ADR records rulings already made and landed (decisions.log, 2026-10-30 to 2026-11-05) as one decision, so the next change to the offer set has a single place to read. It changes no code.
- ADR-083: The router may see the kind of numbered list Piper just showed — ACCEPTED, 2026-11-07, as D5 only. xian said go by 08:03 (relayed by Exec, decisions.log 11-07 08:04): his explicit word on this ADR-078 amendment, not a lapsed window. D1–D3 (the slot on every router call) FAILED their screen and are not accepted. D5 is the decision; D1a (the wording) and D3a (the expiry) are accepted as the parts D5 uses. Lead lands
claude/lead-adr083 through the normal gate. PA checks it served.
- ADR-084: Seat resources are separate, granted once, and bounded — ACCEPTED, 2026-11-16. xian’s word at 06:20 PT, relayed by Exec (mail 01M7JBP51M), verbatim: “1. Yes to ADR-084 and budget 2. Nothing I run personally uses that key, no”. The figures: a seat may spend $10 a run without asking, and the
lead-scoring workspace’s $150 monthly limit is the hard cap. Paid runs stay stopped until Step A has put the seat key where a seat can use it and Lead’s check passes. Drafted 2026-11-15 (Arch-authored, from Exec’s docs/internal/operations/seat-test-harness-proposal-2026-11-15.md, draft 2 at 7c571b8fec, with CIO’s, HOST’s and PA’s replies of 19:26 to 19:28).
Proposed (11)
- ADR-000: Piper Morgan as Meta-Platform Vision — Proposed · August 17, 2025
- ADR-003: LLM-Based Intent Classification — Proposed · July 8, 2025
- ADR-014: Attribution-First Development — Proposed · August 17, 2025
- ADR-015: Wild Claim Verification Protocol — Proposed · August 17, 2025
- ADR-047: Async Event Loop Awareness for Database Connections — Draft (Pending Chief Architect Review) · December 3, 2025
- ADR-062: Project-Scope End-to-End Suite — Generalizing ADR-061 Simulation Harness — Phase 0 ADR (scoping) — v0.1 (drafted 2026-05-16); CEO ratification of proposal direction received 2026-05-15 via Architect decision walkthrough (Item 1); Phase 1+ gated on trigger signals (see §”Phase Sequencing”) · 2026-05-16 (v0.1 — Phase 0 scoping ADR per CEO ratification of e2e suite design proposal direction May 15)
- ADR-063: User-Facing Audit Envelope Read Surface — ADR-061 Companion (Four-Element READ-Side Principle) — v0.1 (drafted 2026-05-16) — pairs with Surface 7 MUX doc (CXO + Comms lane); CEO ratification of paired-deliverable approach received 2026-05-16 via MUX/UI Round 2 ratification (Architect decision walkthrough Item 2) · 2026-05-16 (v0.1 — Phase 2 of MUX/UI Round 2 implementation; companion to #1095’s Pattern-071 first fix shipped this morning)
- ADR-064: Project-Scope Search Index Architecture — Pre-1.0 Commitment for Surface 5 — v0.1 (drafted 2026-05-16) — pre-1.0 Architect-lane ADR per MUX/UI Round 2 (Surface 5 user-facing search is post-1.0; this ADR commits to the index architecture before 1.0 so new surfaces have known indexing shape) · 2026-05-16 (v0.1 — third ADR in the MUX/UI Round 2 sequence: ADR-062 (e2e suite) → ADR-063 (audit-envelope read) → ADR-064 (search index))
- ADR-065: Canonical Context-Package Format (BYOC / Plugin-Packaged) — v0.1 (filed 2026-06-06) — Architect-authored; companion to PDR-005 v1.0 §Open question 6; in-house material per Klatch-pause Evolution-section convention (HOST 2026-05-24). Three-fire bursty-lane drafted (Fire 1 skeleton + plugin-packaging framing; Fire 2 §Decision D1-D6 substantive content; Fire 3 polish + §Consequences refinement + v0.1 final). · 2026-06-06
- ADR-066: Packaging-Layer Abstraction (BYOC Plugin Per-Host Deployment) — v0.2 (amended 2026-06-14) — Architect-authored; companion to PDR-005 v1.0 §Open question 7; gated by ADR-065 v0.1 ✅. · 2026-06-06
- ADR-078 — Session-Activity Ledger + Pre-Classifier Reference Resolution (the #1394 cross-turn continuity architecture) — ACCEPTED (v0.2, 2026-07-14) — Arch-accepted on the integrity authority PM delegated (2026-07-12, “maintain the architectural integrity”) + greenlit authorship. Both ACCEPT gates cleared: (1) Lead’s ledger-feasibility read — DONE (2026-07-14; it corrected D1 from association-over-existing to a dedicated additive
session_activity ledger — see OQ-1); (2) pre-classifier direction (D2/D4) — Lead CONCURS + HOST trust-lens PASS (2026-07-13). PM retains veto — flagged to PM on acceptance (this is the architecture call PM asked me to hold; surfaced, not silently flipped). Lead is cleared to build B4 against the D1 session_activity contract. (v0.1 PROPOSED 2026-07-12; HOST D1a folded 2026-07-13; D1 corrected + accepted 2026-07-14. B4 built + Arch-ratified 2026-07-15 — SessionActivityDB + owner-scoped reader + central observer + recall, suite-green; B3 pre-classifier resolution pending, needs new ADR-077 D5 rows.)
Dormant (Proposed, unratified) (2)
Superseded (9)
- ADR-007: Staging Environment Architecture with Docker Compose — Superseded (2026-09-29, Arch) · July 20, 2025
- ADR-013: MCP + Spatial Intelligence Integration Pattern — Superseded/Deprecated (via notice heading — no formal Status line)
- ADR-016: Ambiguity-Driven Architecture with Chain-of-Draft Integration — Superseded (status corrected 2026-08-29) · August 17, 2025
- ADR-018: Server Functionality Architecture — Superseded (status corrected 2026-08-29; prior status ‘Implemented’ was inaccurate) · August 17, 2025
- ADR-019: Full Orchestration Commitment — Superseded (status corrected 2026-08-29) · August 17, 2025
- ADR-020: Protocol Development Investment — Superseded — never executed (status corrected 2026-08-29) · August 17, 2025
- ADR-021: Multi-Federation Achievement — Superseded — implementation claims disavowed (status corrected 2026-08-29) · August 17, 2025
- ADR-024: Persistent Context Foundation Architecture — Superseded by ADR-075 (status corrected 2026-08-29 — see Status correction at end of file) · August 20, 2025
- ADR-028: Three-Tier Verification Pyramid Architecture — SUPERSEDED (2026-07-26 — Arch fix-or-delete ruling 2026-07-25, decisions.log ~23:35 PT; PM-flagged per the #1322-supersession precedent). The runtime
methodology/ package this ADR specified was deleted as a zero-importer dead island; the pyramid’s ideas live on as the cohort’s prose discipline (evidence-required, verify-first, completion-theater pattern family, the #1452 CI-arbitrated gate). Design lineage: docs/internal/architecture/current/design-record-methodology-as-code-2025.md. · September 2, 2025
Other (4)