DOC_OP_A_CROSS_DOC_OBLIGATION_TRACKER_V2.md
OP-A and Operations and Trackers/Archived DOC OP-A and Operations DOCS/DOC_OP_A_CROSS_DOC_OBLIGATION_TRACKER_V2.md
ELNOR REPO READER TEXT MIRROR Original path: OP-A and Operations and Trackers/Archived DOC OP-A and Operations DOCS/DOC_OP_A_CROSS_DOC_OBLIGATION_TRACKER_V2.md Source repo: /Users/OpenClaw1/Elnor/Elnor Specs Git branch: main Git commit: dbaa25962edc11ab30e8d4ca1715f9ae5bf77331 Generated: 2026-06-09T01:23:58.539Z --- # DOC OP-A — Cross-Doc Obligation Tracker V2 **DOC ID:** DOC OP-A (operations spec, A series — cross-doc obligation tracker) **Version:** V2 (corrections pass over V1 — no fold-in work performed) **Date created (V1):** 2026-04-26 **Date V2 produced:** 2026-04-26 **Status:** Active operations file (not a proposal; not a spec; this IS the tracker) **Owner:** Will (architect); maintained by reviewing LLMs during sessions **Folder:** `Current Specs/Operations Docs/` per architect's selection. **V2 changes from V1:** Removed unverified source documents from §3 "not yet folded in" list (DOC72 Companion Knowledge Store Integration Map R2 + Verification, DOC10 Orchestration Integration Ledger R10, DOC16 Deferred Additions R5.3, Running Brief Remediation v6, ELNOR Knowledge Store Unification Plan R1). These were inherited from CD Master Integration Index R1 (archived) without verification of current existence or currency. Moved to §9 Open Meta-Architecture Questions as an inventory item requiring investigation. Tightened scope rule (§3 preamble) to clarify what counts as a foldable source. No obligation rows in §6 changed. **Replaces / supersedes:** - `CD_MASTER_INTEGRATION_INDEX_R1.md` (April 1, 2026) — index/pointer model superseded by direct content - `DOC15_Cross_Document_Integration_Contract_R3_1_Consolidated_Current_Draft.md` (latest dated content March 12, 2026) — content folded into this tracker by-target The superseded documents remain in their existing folder locations as historical reference. They are NOT to be updated going forward; new obligations land here. --- ## 1. How to use this document **The single rule:** attach this tracker to every red team review and every spec drafting session. The reviewer (you, an LLM, or both) opens the section for the target doc being worked on, reads pending obligations, and either: 1. **Absorbs** an obligation into the spec revision (move row to "Absorbed" with date and revision number). 2. **Defers** an obligation explicitly with reason (move row to "Deferred" with reason). 3. **Adds** new obligations surfaced during the session (append to "Active" with source citation). 4. **Updates** an existing row's status (e.g., `[MISSING]` → `[PARTIAL]` after partial integration). When the session closes, the reviewer's last step is to update this tracker. If the tracker doesn't get updated, the system loses memory of what was done. **For new findings:** every cross-doc finding from a red team review or proposal becomes one or more rows here. The originating document (review file, proposal file, etc.) is cited as the source. Future revisions sweep this tracker to find their work. **For session-start prep:** to know what's pending for the doc you're about to work on, read only the relevant `### DOC<N>` subsection under §6 "By Target Document — Active." That's your worklist. --- ## 2. Status Key Inherited from DOC15 R3.1 contract format (it works; don't reinvent): - `[REQ]` — Required. Target doc is broken or misleading without this. - `[ENH]` — Enhancement. Target doc works but loses quality/trust/efficiency without it. - `[FUT]` — Future. Needed for later phases, domain-pack work, or post-launch. - `[EXISTS]` — Already defined in the target doc (current revision). - `[PARTIAL]` — Partially defined; ownership or contract extension still needed. - `[MISSING]` — Not defined in target doc. A row's status uses one or two markers: e.g., `[REQ] [MISSING]` (required and not yet defined), `[ENH] [PARTIAL]` (enhancement, partially defined), `[REQ] [EXISTS]` (required and already in the spec — verification only). --- ## 3. Source Document Registry Every document that has fed obligations into this tracker. Each source's content is now represented in §6 below; the source itself is preserved for historical reference and for citing detail. | Source Document | File Reference | Last Updated | Status | Folded In | |---|---|---|---|---| | DOC24 R2.5 §22 Cross-Doc Amendment Matrix | `DOC24_UNIFIED_KNOWLEDGE_CAPABILITY_ONBOARDING_ARCHITECTURE_R2_5.md` | April 2026 | Active spec revision | Yes — full §22 content extracted | | V2 DOC24 Red Team Review | `DOC24_R2_5_RED_TEAM_REVIEW_CLAUDE_OPUS_4_7_V2.md` | 2026-04-26 | Just produced | Yes — cross-doc findings extracted (ISS-01b, ISS-03, ISS-11, ISS-12, ISS-17, ISS-22, ISS-23, ISS-26, ISS-28) | | DOC15 Cross-Doc Integration Contract R3.1 | `DOC15_Cross_Document_Integration_Contract_R3_1_Consolidated_Current_Draft.md` | Latest dated content March 12, 2026 (Part 2 R3 revision); Part 3 authority salience additions undated; R3.1 consolidation date unspecified | **STALE — predates DOC72 R5.72, DOC73 V1.4, DOC25, DOC24 R2.5, BDSM V6.4, KDA R2, Persistent Onboarding Curiosity amendment, GIE V2.2, KIE R2** | Yes — feature-area-grouped extraction of §§1-11 | | CD Master Integration Index R1 | `CD_MASTER_INTEGRATION_INDEX_R1.md` | 2026-04-01 | Superseded by this tracker | Yes — registry content folded into §3 | ### Scope rule for folding sources into this tracker Only standalone documents whose primary purpose is tracking cross-doc obligations are foldable into OP-A. **Out of scope:** - **Spec-internal cross-doc content** (e.g., DOC24 §22 amendment matrix, DOC3 §22). These migrate to OP-A when the owning spec next revises, as part of normal revision work. - **Currently-outdated implementation guides.** Their successors fold in when those exist. - **Documents whose existence or currency is unverified.** Listed in §9 Open Meta-Architecture Questions for investigation, not in this registry. - **Documents being superseded by major revisions in progress** (e.g., DOC10-related trackers when DOC10 itself is being significantly revised). Wait for the post-revision tracker. A document only enters this registry once the architect has confirmed (a) it exists in the folder structure, (b) its content reflects current architecture or its staleness is explicitly known and acceptable, and (c) it is not pending replacement by a forthcoming revision. ### Source documents NOT yet folded in (verified active sources awaiting fold-in session) | Source Document | File Reference | Status | Plan | |---|---|---|---| | DOC3 Companion Doc Delta Plan R9.2 Canonical | `DOC3_Companion_Doc_Delta_Plan_R9_2_Canonical.md` | Confirmed exists; user has shared file | Fold in during Session 2 (DOC3 + DOC14 + CD-A grouped) | | DOC14 Cross-Document Delta Companion R2 | `DOC14_CROSS_DOCUMENT_DELTA_COMPANION_R2.md` | Confirmed exists; user has shared file | Fold in during Session 2 | | CD-A 4.1.26 DOC3/DOC24 Cycle staging doc | `CD-A_4-1-26_DOC3_DOC24_CYCLE.md` | Confirmed exists; user has shared file | Fold in during Session 2 | | Memory Intake and At-Use Disciplines Proposal V1 | `MEMORY_INTAKE_AND_AT_USE_DISCIPLINES_PROPOSAL_V1.md` | **Held off pending red team** — proposal in first draft; obligations not yet pinned to integrated specs | Add after proposal red team confirms approach and target sections are stable | | Persistent Onboarding Curiosity amendment | (filename TBD) | Drafted; references in V2 DOC24 review | Add as standalone source if/when adopted into a target spec | --- ## 4. Calibration / shelf-life note Obligations in this tracker are calibrated against specific spec versions at the dates noted in §3. When a target spec revises: 1. **All rows targeting that doc** are reviewed against the new revision. 2. Rows whose obligations are now satisfied → moved to Absorbed. 3. Rows whose obligations changed shape due to revision → updated with new status/description. 4. Rows whose obligations are now obsolete due to architectural change → moved to Deferred with reason. When a SOURCE document supersedes (e.g., DOC73 V1.5 supersedes V1.4 and changes a primitive that obligations referenced): rows derived from the older source are flagged for re-validation. The "Calibrated against" field on each row identifies its anchoring source versions. --- ## 5. Quick reference — Source-doc currency snapshot For at-a-glance assessment of how stale this tracker's content might be: | Spec / Source | Current Version | As Of | Sources In This Tracker That Reference It | |---|---|---|---| | DOC72 | R5.72 | 2026-04-15 | V2 DOC24 review (current); DOC24 §22 (current); DOC15 R3.1 (predates DOC72) | | DOC73 | V1.4 FINAL | 2026-04-25 | V2 DOC24 review (current); DOC15 R3.1 (predates DOC73 entirely) | | DOC24 | R2.5 | April 2026 | V2 DOC24 review (current); DOC15 R3.1 (predates DOC24 R2.5) | | DOC25 | V1.0 | 2026-04-11 | V2 DOC24 review (referenced); DOC15 R3.1 (predates DOC25) | | DOC15 | R7.1 (per V3 carryover) | TBD | DOC15 R3.1 contract is the cross-doc companion, not the spec itself | | DOC1 | R1 | TBD | All sources reference DOC1; partially stale per V3 carryover §10.3 | **Implication:** DOC15 R3.1's content predates major architecture additions. Some obligations it raises may now be satisfied (e.g., DOC72 may now define seams DOC15 needed) or now obsolete (e.g., topics absorbed into DOC72/DOC73 since). DOC15 R3.1 obligations included in §6 below are extracted faithfully but may need review against current spec state during integration. --- ## 6. By Target Document — Active Obligations Sections appear in DOC-number order. A target doc with no current obligations has the section header but `(no current obligations recorded)`. --- ### §6.1 DOC1 — Memory Resilience | Obligation | Field/Change | Status | |---|---|---| | **OBL-D1-01:** Durable authority schema adoption | `authority_scope`, `creation_path` metadata, broader-correction approval gating | `[REQ] [PARTIAL]` | - **Source:** DOC15 R3.1 §10 / Priority Matrix #36, #37, #38, #39 - **Why:** Without durable authority scope and creation-path metadata, broader-than-session corrections silently apply globally; freeform task instructions wrongly become standing orders. - **Acceptance:** DOC1 schema includes `authority_scope`; correction-broadening requires explicit approval; transient instructions pass through without auto-promotion. - **Calibrated against:** DOC15 R3.1 (March 12, 2026) - **Note:** May overlap with V3 carryover §3.4 DOC1 Authority/Heuristic distinction — verify current status against DOC1 R1. | **OBL-D1-02:** Maturity bypass eligibility check | Verify current §10.4 against ISS-01b cascade implications | `[REQ] [PARTIAL]` | - **Source:** V2 DOC24 Red Team Review §ISS-01b - **Why:** Per ISS-01b, source-anchored authority must not be Beta-derived. DOC1's maturity bypass interacts with this — bypass eligibility may need to consider AuthorityAnchor presence. - **Acceptance:** DOC1 §10.4 specifies that AuthorityAnchor-bearing nodes use anchor-derived authority, not Beta confidence, for bypass decisions. - **Calibrated against:** DOC72 R5.72; DOC73 V1.4 | **OBL-D1-03:** Memory governance audit surface | Inspector exposes provenance, scope, last-updated | `[REQ] [EXISTS]` | - **Source:** V3 carryover §3.4 (existing requirement); DOC15 R3.1 §10.5 - **Why:** Operator inspection of memory provenance is a stated invariant. - **Status note:** Likely already in DOC1 R1; verify during next DOC1 revision. --- ### §6.2 DOC3 — App Skills (no current obligations recorded directly in this tracker; DOC3 R11.3 adjudication card and DOC3 Companion Delta Plan R9.2 contain the canonical DOC3-targeting obligations and should be folded in to this tracker in next maintenance pass) Cross-references for DOC3 work: - DOC3 §22 (internal amendment matrix — read during R11.3 revision) - V2 DOC24 review ISS-09 (ConversationHistoryService) — partially affects DOC3 if demonstration mode capture interacts with conversation history --- ### §6.3 DOC4 — OpenClaw Bridge | **OBL-D4-01:** CIL Advisor agent definition | Agent registry entry for `cil_advisor` and similar advisor agents | `[REQ] [MISSING]` | - **Source:** DOC15 R3.1 §9.1, §9.2 - **Why:** CIL needs registered advisor agents; DOC10 advisor dispatch (§7) requires DOC4 agent definitions. - **Calibrated against:** DOC15 R3.1 (March 12, 2026) | **OBL-D4-02:** Agent document dependency fields | `requires_documents`, `recommended_documents` on agent registrations | `[REQ] [MISSING]` | - **Source:** DOC15 R3.1 §9.3 - **Why:** Document dependency declarations enable DOC10 + DocIndex resolution; advisor experience depends on having needed docs available. - **Calibrated against:** DOC15 R3.1 --- ### §6.4 DOC6 — Panels, Forums, Self-Improvement **Status check needed:** DOC6 numbering may be obsolete or absorbed into DOC12 / other. V3 carryover §1 doesn't list DOC6 explicitly. Verify current status during next maintenance pass. DOC15 R3.1 §3 lists obligations targeting DOC6: - §3.1 Panel Close ReviewOutcome `[REQ]` - §3.2 Configuration Dissatisfaction Detection `[ENH]` - §3.3 Panel Feedback Events to CIL Bridge `[REQ]` - §3.4 Panel Turn Prompt Lineage (multi-turn) - §3.5 Ask Elnor Integration `[REQ]` - §3.6 Durable-Correction vs Use-Only-Here Controls `[REQ]` - §3.7 Ask/Why Telemetry `[ENH]` Refer to DOC15 R3.1 §3 for detail. Re-target rows when DOC6 status is confirmed. --- ### §6.5 DOC7 — Context Buckets & Files | **OBL-D7-01:** MaterializationPreview API | Preview before injection of bucket-materialized content | `[ENH] [MISSING]` | - **Source:** DOC15 R3.1 §6.1 / Priority Matrix #15 - **Calibrated against:** DOC15 R3.1 | **OBL-D7-02:** Hierarchical bucket levels | Bucket nesting / parent-child structure | `[ENH] [MISSING]` | - **Source:** DOC15 R3.1 §6.2 / Priority Matrix #16 | **OBL-D7-03:** Bucket access telemetry to DOC8 | Track bucket access patterns for learning | `[ENH] [PARTIAL]` | - **Source:** DOC15 R3.1 §6.3 | **OBL-D7-04:** DocIndex-aware budget allocation | Bucket budget consults DocIndex for relative document weighting | `[ENH] [PARTIAL]` | - **Source:** DOC15 R3.1 §6.4 | **OBL-D7-05:** Document priority hints consumption | Consume hints from DocIndex / DOC10 | `[ENH] [PARTIAL]` | - **Source:** DOC15 R3.1 §6.5 | **OBL-D7-06:** Unified Context Budget Governance integration | Coordinate with DOC24 unified budget; overlap detection | `[REQ] [PARTIAL]` | - **Source:** DOC24 R2.5 §22 (cross-doc matrix); §27A transition note - **Why:** DOC24 §27A explicitly flags pending integration. DOC7 must accept unified budget governance once integrated. - **Calibrated against:** DOC24 R2.5 --- ### §6.6 DOC8 — Self-Learning | **OBL-D8-01:** Signal bridge entry point | Stable hook for CIL signals to DOC8 nightly | `[REQ] [MISSING]` | - **Source:** DOC15 R3.1 §4.1 / Priority Matrix #4 - **Why:** Without a stable bridge, CIL learning loop has no consumer. - **Calibrated against:** DOC15 R3.1 | **OBL-D8-02:** Cost firewall compliance | Enforced cost limits per DOC13 + Core | `[REQ] [PARTIAL]` | - **Source:** DOC15 R3.1 §4.2 | **OBL-D8-03:** Nightly scheduler extension points | Eval-lane scheduling separate from main learning | `[ENH] [MISSING]` | - **Source:** DOC15 R3.1 §4.3 / Priority Matrix #17 | **OBL-D8-04:** Learning controls integration | UI controls map to DOC8 actions | `[REQ] [PARTIAL]` | - **Source:** DOC15 R3.1 §4.4 | **OBL-D8-05:** Reflection event contracts (DOC24 §11.3A) | DOC8 consumes typed reflection events from DOC24 | `[REQ] [PARTIAL]` | - **Source:** DOC24 R2.5 §22 row "DOC8"; §11.3A - **Why:** DOC24 reflection events (probe_adjustment_proposed, threshold_update_proposed, etc.) need DOC8 consumers. - **Calibrated against:** DOC24 R2.5 | **OBL-D8-06:** Delivery feedback ingestion (PacketUsageFeedback) | DOC8 reads packet trim, ignored cards, cache-warm signals | `[REQ] [MISSING]` | - **Source:** DOC24 R2.5 §22 row "DOC8"; §26.6 - **Calibrated against:** DOC24 R2.5 | **OBL-D8-07:** BDSM computational engine role | DOC8 implements BDSM nightly Layer 1/2/3 processing | `[REQ] [PARTIAL]` | - **Source:** DOC72 R5.72 (BDSM as DOC8's computational engine); BDSM V6.4 - **Why:** BDSM Matrix scoring uses DOC8 nightly batch infrastructure. - **Calibrated against:** BDSM V6.4 --- ### §6.7 DOC10 — Unified Engagement Orchestration | **OBL-D10-01:** Generic advisor dispatch endpoint | `+ask` / `+advise` routing for CIL and other advisor surfaces | `[REQ] [MISSING]` | - **Source:** DOC15 R3.1 §7.1, §7.3 / Priority Matrix #33 - **Calibrated against:** DOC15 R3.1 | **OBL-D10-02:** Advisor thread persistence | Advisor threads persist across surfaces with stable IDs | `[REQ] [PARTIAL]` | - **Source:** DOC15 R3.1 §7.2 | **OBL-D10-03:** Agent document dependency resolution | DOC10 + Core resolves document dependencies on dispatch | `[ENH] [PARTIAL]` | - **Source:** DOC15 R3.1 §7.4 / Priority Matrix #34 | **OBL-D10-04:** `use_profile` field on dispatch envelope | Per-dispatch profile selection | `[ENH] [MISSING]` | - **Source:** DOC15 R3.1 §7.5 | **OBL-D10-05:** CIL suggestion cards with document recommendations | Suggestion cards trigger DocIndex loads | `[ENH] [MISSING]` | - **Source:** DOC15 R3.1 §7.6 / Priority Matrix #35 | **OBL-D10-06:** Ask/Why/Advise telemetry + memory-origin visibility | Telemetry on advisory paths shows memory provenance | `[ENH] [PARTIAL]` | - **Source:** DOC15 R3.1 §7.7 / Priority Matrix #40 | **OBL-D10-07:** Routing cascade ownership clarification | DOC24 owns executable routing function (§13.2A); DOC10 owns cross-surface orchestration | `[REQ] [PARTIAL]` | - **Source:** DOC24 R2.5 §22 row "DOC10" - **Why:** Boundary between DOC24 routing and DOC10 orchestration must be explicit. - **Calibrated against:** DOC24 R2.5 --- ### §6.8 DOC11 — OpenClaw Gateway | **OBL-D11-01:** Bootstrap builder accepts ContextPlan | `assembleContextCard(contextPlan?)` API | `[REQ] [PARTIAL]` | - **Source:** DOC15 R3.1 §5.1 / Priority Matrix #5 - **Why:** Single most critical runtime seam per DOC15 §13. - **Calibrated against:** DOC15 R3.1 | **OBL-D11-02:** Cache-optimized ordering support | Stable ordering for prompt caching | `[ENH] [PARTIAL]` | - **Source:** DOC15 R3.1 §5.2 / Priority Matrix #14 | **OBL-D11-03:** Runtime truth for DispatchCheckpoint | Cache telemetry, hit/miss exposed | `[REQ] [PARTIAL]` | - **Source:** DOC15 R3.1 §5.3 / Priority Matrix #25 | **OBL-D11-04:** Lean annotation delivery | Annotations passed without bloat | `[ENH] [MISSING]` | - **Source:** DOC15 R3.1 §5.4 | **OBL-D11-05:** Summary lineage export | With DOC7 coordination | `[ENH] [PARTIAL]` | - **Source:** DOC15 R3.1 §5.5 / Priority Matrix #26 | **OBL-D11-06:** Receipt subsystem alignment | Receipt schema, queue/confirm semantics, fail-closed stale write behavior | `[REQ] [PARTIAL]` | - **Source:** DOC24 R2.5 §22 row "DOC11"; §18.3A receipt subsystem - **Calibrated against:** DOC24 R2.5 | **OBL-D11-07:** R15 Amendment integration | Plugin/capability discovery, command discovery, memory/dreaming controls, channel generalization | `[REQ] [PARTIAL]` | - **Source:** V3 carryover §4.5 (DOC11 R15 Amendment Proposal); V2 DOC24 review (referenced) - **Why:** Aligns DOC11 R14 with OpenClaw releases through 2026.4.12. - **Calibrated against:** OpenClaw v2026.4.23 --- ### §6.9 DOC12 — Inter-Agent Communication | **OBL-D12-01:** Room close signal emission with CIL bridge | Signal at room close → CIL bridge → DOC8 | `[REQ] [MISSING]` | - **Source:** DOC15 R3.1 §2.1 / Priority Matrix #8 - **Calibrated against:** DOC15 R3.1 | **OBL-D12-02:** Room turn signal emission and prompt lineage | Per-turn signals with prompt lineage attribution | `[REQ] [PARTIAL]` | - **Source:** DOC15 R3.1 §2.2 / Priority Matrix #10 | **OBL-D12-03:** Room configuration export to ContextFacts | review_target_kind, evidence_domain | `[REQ] [PARTIAL]` | - **Source:** DOC15 R3.1 §2.3, §2.7 / Priority Matrix #13 | **OBL-D12-04:** RetentionAndLearningPolicyBundle | Per-room retention and learning policy | `[ENH] [MISSING]` | - **Source:** DOC15 R3.1 §2.5 | **OBL-D12-05:** DecisionBasis artifact export to CIL | `finding_cited_in_decision`, decision_type | `[REQ] [MISSING]` | - **Source:** DOC15 R3.1 §2.6 / Priority Matrix #9, #19 | **OBL-D12-06:** `decision_without_basis` signal | Detection when decisions lack support | `[ENH] [MISSING]` | - **Source:** DOC15 R3.1 / Priority Matrix #18 | **OBL-D12-07:** Graph projection of rooms | Internal collaboration objects → graph nodes (per DOC72 §4) | `[REQ] [PARTIAL]` | - **Source:** DOC24 R2.5 §22 row "DOC12" - **Calibrated against:** DOC24 R2.5 --- ### §6.10 DOC13 — Cost Tracking & Enforcement | **OBL-D13-01:** Cost firewall coordination | Cross-doc cost limit enforcement | `[REQ] [PARTIAL]` | - **Source:** DOC15 R3.1 §8.1 - **Calibrated against:** DOC15 R3.1 | **OBL-D13-02:** Cost data for DispatchCheckpoint | Cost reporting at dispatch | `[REQ] [PARTIAL]` | - **Source:** DOC15 R3.1 §8.2 --- ### §6.11 DOC14 — CANDOR | **OBL-D14-01:** Finding judgment enhancement | `novelty`, `starred`, `original_dispatch_id` | `[REQ] [MISSING]` | - **Source:** DOC15 R3.1 §1.1 / Priority Matrix #1 - **Why:** Distinguishes "accepted because true" from "accepted because surprising/useful." - **Calibrated against:** DOC15 R3.1 | **OBL-D14-02:** ReviewOutcome at room close | goal_type, close_reason, user_goal_met, findings_starred, findings_by_novelty | `[REQ] [MISSING]` | - **Source:** DOC15 R3.1 §1.2 / Priority Matrix #2 | **OBL-D14-03:** Prompt lineage on every room turn | prompt_overlay_hash, role_overlay_hash, model_id, effective_topology | `[ENH] [PARTIAL]` | - **Source:** DOC15 R3.1 §1.3 / Priority Matrix #10 | **OBL-D14-04:** Room health metrics export | room_health → CIL bridge | `[ENH] [PARTIAL]` | - **Source:** DOC15 R3.1 §1.4 / Priority Matrix #11, #27 | **OBL-D14-05:** Finding-to-action tracking | finding_exported, finding_became_proposal, finding_survived_dedup | `[REQ] [MISSING]` | - **Source:** DOC15 R3.1 §1.5 | **OBL-D14-06:** review_target_kind / evidence_domain | activates target-specific profiles | `[REQ] [PARTIAL]` | - **Source:** DOC15 R3.1 §1.6 / Priority Matrix #13 --- ### §6.12 DOC15 — Cognitive Infrastructure Layer | **OBL-D15-01:** Self-referencing — internal obligations | DOC15 R3.1 contract has many obligations on DOC15 itself | `[REQ] [PARTIAL]` | - **Source:** DOC15 R3.1 (self-reference); DOC15 Cross-Document Integration Contract R3.1 (which IS the obligation document) - **Note:** DOC15 R3.1's status fields are themselves the canonical record. - **Calibrated against:** DOC15 R3.1 | **OBL-D15-02:** Hot-path interactive profile definition | ~200-token authority injection profile (per ADJ-82) | `[REQ] [MISSING]` | - **Source:** DOC24 R2.5 §22 row "DOC15"; §19.1A budget waterfall ADJ-82 note - **Why:** DOC24 packet assembly assumes DOC15 hot-path profile shape; needs explicit definition. - **Calibrated against:** DOC24 R2.5 | **OBL-D15-03:** KOI injection position assignment | DOC15 owns KOI baseline position in CIL hierarchy | `[REQ] [MISSING]` | - **Source:** DOC24 R2.5 §22 row "DOC15"; §26.1 Three-Level Delivery Model - **Calibrated against:** DOC24 R2.5 | **OBL-D15-04:** Accept DOC24 budget waterfall (§19.1A) | DOC15 ContextPlanner provides knowledge_nodes allocation | `[REQ] [PARTIAL]` | - **Source:** DOC24 R2.5 §22 row "DOC15" | **OBL-D15-05:** Integration with DOC72 R5.72 knowledge card types | DOC15 needs to consume DOC72 entity card types | `[REQ] [PARTIAL]` | - **Source:** V3 carryover §10.3 (staleness note: DOC15 R7.1 needs integration) - **Why:** New injection tags from DOC24 §26 and knowledge card types from DOC72 are pending integration into DOC15. - **Calibrated against:** DOC72 R5.72; DOC24 R2.5 --- ### §6.13 DOC16 — M365 Integration | **OBL-D16-01:** Provider seam alignment | Source-policy, shallow bootstrap, live-state, graph/indexing patterns | `[REQ] [PARTIAL]` | - **Source:** DOC24 R2.5 §22 row "DOC16" - **Calibrated against:** DOC24 R2.5 | **OBL-D16-02:** Calendar event contracts | For DOC24 §35 semantic cache warming via calendar | `[ENH] [PARTIAL]` | - **Source:** DOC24 R2.5 §22 row "DOC16"; §35 --- ### §6.14 DOC18 — LlamaIndex Retrieval Sidecar (no current obligations recorded directly; cross-references in DOC15 R3.1 §11 mention retrieval owners; DOC18 not deeply integrated in current cycle) --- ### §6.15 DOC20 — Browser/Notes/Document Viewer | **OBL-D20-01:** Inline reply action family | `note.reply_inline` action wiring | `[REQ] [PARTIAL]` | - **Source:** DOC24 R2.5 §22 row "DOC20"; §20.4 - **Calibrated against:** DOC24 R2.5 | **OBL-D20-02:** Note-thread context seams | NotesContextService → DOC24 graph integration | `[REQ] [PARTIAL]` | - **Source:** DOC24 R2.5 §22 row "DOC20" | **OBL-D20-03:** Note-linked preference capture | Capture surfaces in note context | `[ENH] [PARTIAL]` | - **Source:** DOC24 R2.5 §22 row "DOC20" --- ### §6.16 DOC21 / DOC22 — Master UI Spec / Page Inventory | **OBL-D21-01:** Real pages/routes for §20.7 inspectability surfaces | All DOC24 §20.7 surfaces need DOC21/22 page registration | `[REQ] [PARTIAL]` | - **Source:** DOC24 R2.5 §22 row "DOC21/22" - **Why:** Phantom-surface prevention. Every named surface must have a real page. - **Calibrated against:** DOC24 R2.5 | **OBL-D21-02:** Active Context Controls sidebar component | Per ADJ-86 | `[REQ] [PARTIAL]` | - **Source:** DOC24 R2.5 §22 row "DOC21/22"; ADJ-86 | **OBL-D21-03:** DOC24 operational inspectors registered separately | Distinct from DOC72 Knowledge Manager tabs (per ADJ-36) | `[REQ] [PARTIAL]` | - **Source:** DOC24 R2.5 §22 row "DOC21/22"; ADJ-36 --- ### §6.17 DOC23 — Task System (no current obligations recorded; DOC23 R3.0 frozen baseline; obligations may surface in next cycle) --- ### §6.18 DOC24 — Unified Knowledge, Capability, and Onboarding (R2.5+) The largest active section. Most obligations originate from V2 DOC24 review (with severity tags from that review carried forward). #### Critical findings (must resolve before R3) | **OBL-D24-01:** `exclude_from_injection` filter not wired | §9.5B / §27.0B / §26.6 source policy filter | `[REQ] [MISSING]` | - **Source:** V2 DOC24 review §ISS-02 (CRITICAL) - **Why:** Privacy/safety. SourceExclusionFilter has three actions but only the extraction path is wired. - **Acceptance:** §27.0B pre-filter consults both `SourcePolicyRecord` AND `SourceExclusionFilter`. SourceExclusionService added to §21. - **Calibrated against:** DOC24 R2.5; V2 DOC24 review | **OBL-D24-02:** Confidence floor override contradicts AuthorialVoice | §26.5.2 step 2 vs §29.1 mapping | `[REQ] [MISSING]` | - **Source:** V2 DOC24 review §ISS-01 (CRITICAL) - **Why:** AUTHORITY_PROTECTED_TAGS floor needed; step-0 mapping currently overridden by step-2 confidence collapse. See ISS-01b for cross-doc cascade. - **Calibrated against:** V2 DOC24 review | **OBL-D24-03:** AUTHORITY_PROTECTED_TAGS floor (defense-in-depth) | §26.5.2 step 2 amendment | `[REQ] [MISSING]` | - **Source:** V2 DOC24 review §ISS-01b (CRITICAL — cross-doc cascade row C) - **Why:** Third defense layer; pairs with OBL-D72-01 and OBL-D73-01. - **Calibrated against:** V2 DOC24 review | **OBL-D24-04:** Routing chain helper functions undefined | §13.4A `extractEntityMentions`, `hasUnresolvedReferences`, `extractRecentConversationEntities` | `[REQ] [MISSING]` | - **Source:** V2 DOC24 review §ISS-05 (CRITICAL) | **OBL-D24-05:** Step 4 workspace context queries blow latency budget | §13.4A | `[REQ] [PARTIAL]` | - **Source:** V2 DOC24 review §ISS-06 (CRITICAL) - **Why:** Sequential `await` × 7 queries on every turn; parallelize + short-circuit. | **OBL-D24-06:** `selectToolForStep` non-deterministic on cold start | §13.4B | `[REQ] [PARTIAL]` | - **Source:** V2 DOC24 review §ISS-04 (CRITICAL); also F1 frontier idea (Thompson sampling) | **OBL-D24-07:** Studio onboarding session has no abandonment policy | §12.2A, §12.7 | `[REQ] [MISSING]` | - **Source:** V2 DOC24 review §ISS-07 (CRITICAL) | **OBL-D24-08:** Suspended context stack lost when saving profile | §5.3B + §12.7A | `[REQ] [PARTIAL]` | - **Source:** V2 DOC24 review §ISS-08 (CRITICAL) | **OBL-D24-09:** ConversationHistoryService missing | §13.4A + §21 service catalog | `[REQ] [MISSING]` | - **Source:** V2 DOC24 review §ISS-09 (CRITICAL) | **OBL-D24-10:** Five-step chain candidate selection function unspecified | §13.4A return value | `[REQ] [MISSING]` | - **Source:** V2 DOC24 review §ISS-10 (CRITICAL) #### High-severity findings | **OBL-D24-11:** BDSM `force_level` field missing from CompactEntityCard | §19.2 | `[REQ] [MISSING]` | - **Source:** V2 DOC24 review §ISS-11 (HIGH) | **OBL-D24-12:** Persistent Onboarding Curiosity amendment integration | §11.5 ProbeBudget, §12.4D gap detection | `[REQ] [PARTIAL]` | - **Source:** V2 DOC24 review §ISS-12 (HIGH) - **Note:** Amendment exists as draft; integration into R2.5+ pending. | **OBL-D24-13:** Concept-level relevance scoring needs embedding-missing fallback | §26.6 P1A | `[REQ] [PARTIAL]` | - **Source:** V2 DOC24 review §ISS-13 (HIGH) | **OBL-D24-14:** Transient instruction promotion needs storage | §12.4C | `[REQ] [MISSING]` | - **Source:** V2 DOC24 review §ISS-14 (HIGH) | **OBL-D24-15:** Cache-warming TTL invalidation source unspecified | §35 + §21 | `[REQ] [PARTIAL]` | - **Source:** V2 DOC24 review §ISS-15 (HIGH) | **OBL-D24-16:** Citation hallucination detection naive string-match | §26.9 | `[ENH] [PARTIAL]` | - **Source:** V2 DOC24 review §ISS-16 (HIGH) | **OBL-D24-17:** Tool capability injection conflicts with §13.4B principle | §13.4B vs §26.4B | `[REQ] [PARTIAL]` | - **Source:** V2 DOC24 review §ISS-17 (HIGH) | **OBL-D24-18:** request_cadence high-throughput mode lacks owner | §19.7A + §21 | `[REQ] [MISSING]` | - **Source:** V2 DOC24 review §ISS-18 (HIGH) | **OBL-D24-19:** Cross-matter retrieval missing exclusion-list schema | §37.2 | `[REQ] [MISSING]` | - **Source:** V2 DOC24 review §ISS-19 (HIGH) | **OBL-D24-20:** Suspended-context restoration trigger implicit | §5.3B | `[REQ] [PARTIAL]` | - **Source:** V2 DOC24 review §ISS-20 (HIGH) #### Medium-severity findings | **OBL-D24-21 through OBL-D24-30:** Medium severity items | Various sections | `[ENH]` or `[REQ] [PARTIAL]` | - **Source:** V2 DOC24 review §§ISS-21–30 (MEDIUM) - **Detail:** See V2 review for individual fixes — resolution coefficient justification, KDA tier vocabulary alignment, missing event in §21.2, asymmetric tool weight, cross-doc sequencing, wrong section reference in §12.7C, digest delivery preference, matter_only mode tool scoping, rollback double-counting, active context concurrency. #### Low-severity findings | **OBL-D24-31 through OBL-D24-34:** Low / cosmetic | — | `[ENH]` | - **Source:** V2 DOC24 review §§ISS-31–34 (LOW) #### §22 own amendment matrix obligations (should be regenerated when this tracker supersedes) The DOC24 R2.5 §22 amendment matrix lists 12 cross-doc obligation rows. They are now distributed across this tracker by target doc. When DOC24 R3 ships, §22 should reference this tracker (DOC OP-A) as the authoritative source rather than re-listing. --- ### §6.19 DOC25 — Document Intelligence & Universal Ingestion | **OBL-D25-01:** `DOC25_IngestionResult` consumer contract finalization | §15.2 (per DOC73) | `[REQ] [PARTIAL]` | - **Source:** V3 carryover §3.3; DOC73 V1.4 §15.2 references DOC25 - **Why:** DOC73 PBE corpus extraction consumes this contract; DOC25 must finalize it. - **Calibrated against:** DOC73 V1.4; DOC25 V1.0 | **OBL-D25-02:** DOC24 intake aware of DOC25 | Pre-computation pipeline integration | `[REQ] [MISSING]` | - **Source:** V2 DOC24 review (cross-doc gap noted) --- ### §6.20 DOC72 — Hyper Intelligence Overlay (R5.72+) | **OBL-D72-01:** AuthoritySourceClass + AuthorityAnchor trait | §2.2 + new §X | `[REQ] [MISSING]` | - **Source:** V2 DOC24 review §ISS-01b (cross-doc cascade row A) - **Why:** Source-anchored authority must be preservable independent of Beta evidence. - **Acceptance:** AuthoritySourceClass schema on DomainSignalProfile (profile-driven, no domain enums in spec); AuthorityAnchor trait applicable to multiple node kinds. - **Blocks:** OBL-D73-01 - **Calibrated against:** DOC72 R5.72; DOC73 V1.4 | **OBL-D72-02:** `tool_capability` sparsity tier | §2.2 sparsity table | `[REQ] [MISSING]` | - **Source:** V2 DOC24 review §ISS-03 (CRITICAL) - **Why:** ~50-200 tool nodes at scale lack tier assignment; storage and query cost diverge. - **Acceptance:** tool_capability assigned to Tier C default; promotion rule (usage_count ≥ 20 AND age_days ≥ 7 → Tier B) in §6.1. - **Calibrated against:** DOC72 R5.72 | **OBL-D72-03:** Add `suggested` entity confidence threshold for routing | Per ADJ-NEW-04 | `[REQ] [PARTIAL]` | - **Source:** DOC24 R2.5 §22 row "DOC72" - **Why:** Allow `suggested` entities in routing at confidence ≥ 0.6. | **OBL-D72-04:** New edge types | `has_tool`, `executes_via`, `alternative_to` | `[REQ] [PARTIAL]` | - **Source:** DOC24 R2.5 §22 row "DOC72" (ADJ-91); DOC72 R5.72 §4.6 confirms presence - **Status:** Likely `[EXISTS]` — verify in current DOC72 R5.72. | **OBL-D72-05:** Verify internal cross-doc obligation section | DOC72 §TBD | `[REQ] [PARTIAL]` | - **Source:** CD Master Integration Index R1 maintenance note - **Why:** R1 flags need to verify whether DOC72 has internal amendment matrix; consider adding given volume. --- ### §6.21 DOC73 — Positronic Brain Enhancement (V1.4+) | **OBL-D73-01:** §3.2A.1 `authority_of()` branches on AuthorityAnchor | §3.2A.1 (lines 555-573) | `[REQ] [MISSING]` | - **Source:** V2 DOC24 review §ISS-01b (cross-doc cascade row B) - **Why:** Source-anchored authority must use `source_authority(class, profile)`, not Beta-derived authority. Cascades to CU `authority_level` correctness. - **Acceptance:** authority_of() branches on AuthorityAnchor BEFORE VersionedClaim. Locked anchors bypass status modifiers. - **Depends on:** OBL-D72-01 - **Calibrated against:** DOC72 R5.72; DOC73 V1.4 | **OBL-D73-02:** §3.3 VersionedClaim eligibility carve-out cross-reference | §3.3 | `[ENH] [MISSING]` | - **Source:** V2 DOC24 review §ISS-01b - **Why:** §3.3 already names "authority-fixed content" in carve-outs but doesn't operationalize as a structural field; cross-reference AuthorityAnchor. - **Calibrated against:** DOC73 V1.4 --- ### §6.22 EC Core / DocIndex | **OBL-EC-01:** Standing-order change event | Event emission for standing-order mutations | `[REQ] [MISSING]` | - **Source:** DOC15 R3.1 §11 / Priority Matrix #29 - **Calibrated against:** DOC15 R3.1 | **OBL-EC-02:** Profile-config change event | Event emission for profile-config mutations | `[REQ] [MISSING]` | - **Source:** DOC15 R3.1 / Priority Matrix #30 | **OBL-EC-03:** CIL state file registration in DocIndex | Per Priority Matrix #32 | `[REQ] [MISSING]` | - **Source:** DOC15 R3.1 § / Priority Matrix #32 | **OBL-EC-04:** Operation compiler entry point | Per Priority Matrix #6 | `[REQ] [MISSING]` | - **Source:** DOC15 R3.1 / Priority Matrix #6 | **OBL-EC-05:** Implement DOC24 §21 services | All 11 services + commands (e.g., `active_context.mutate` per ADJ-86) | `[REQ] [PARTIAL]` | - **Source:** DOC24 R2.5 §22 row "EC Core" - **Calibrated against:** DOC24 R2.5 | **OBL-EC-06:** EC Core Addendum A V3.3 obligations | Global memory hierarchy, runtime truth, route/command/read-model closure, etc. | `[REQ] [PARTIAL]` | - **Source:** V3 carryover §7.8 (EC Core Addendum A V3.3) --- ## 7. By Target Document — Absorbed Obligations (Empty — V1 is a fresh tracker. Items move here when integrated into target doc revisions, with date and revision number.) Schema for absorbed entries (when populated): ``` **OBL-DXX-NN:** [original obligation title] - Absorbed into: DOC<N> R<X> - Absorbed at: YYYY-MM-DD - Verification: [acceptance test result, CI gate confirmation, or "verified by [reviewer] on [date]"] - Notes: [any drift from original obligation, scope changes, etc.] ``` --- ## 8. By Target Document — Deferred Obligations (Empty — V1 is a fresh tracker. Items move here when explicitly punted with reason.) Schema for deferred entries (when populated): ``` **OBL-DXX-NN:** [original obligation title] - Deferred at: YYYY-MM-DD - Deferred by: [Will / reviewer name] - Reason: [why deferred] - Re-evaluate when: [trigger condition or date] ``` --- ## 9. Open Meta-Architecture Questions Items not yet obligation-grade but worth not losing track of. | Question | Surfaced By | Notes | |---|---|---| | Should the cross-doc tracking system collapse to fewer surfaces? | This tracker's existence | Once DOC OP-A is proven in use for some sessions, evaluate whether per-doc companions (DOC15 R3.1, DOC3 R9.2, DOC14 R2) are still adding value or whether everything should live in DOC OP-A. Tentative plan: archive each per-doc companion after it is fully folded in. | | **Inventory of cross-doc tracking documents inherited from CD Master Integration Index R1 — verification needed** | CD Master Integration Index R1 (archived 2026-04-26) | R1 listed several tracking documents whose current existence and currency are NOT verified by the current OP-A maintainer. Each may be: (a) a real file in the architect's folders not yet shared, (b) drafted but abandoned, (c) renamed/absorbed into other docs, (d) planned but never created, (e) old version superseded. Names from R1: **DOC72 Companion Knowledge Store Integration Map R2 + Verification** (R1 attributed to DOC72 R5.5 era); **DOC10 Orchestration Integration Ledger R10 Consolidated** (R1 noted active; user has since indicated DOC10 is slated for significant revision, so this tracker may be superseded soon regardless); **DOC16 Deferred Additions R5.3 Complete** (R1 noted ~6,953 lines, large running punch list); **Running Brief Remediation v6.0** (user has indicated outdated); **ELNOR Knowledge Store Unification Plan R1** (R1 attributed to "unifying knowledge stores across DOC72/DOC1/DOC3/DOC7"); **Cross-Document Integration Plan v4** (R1 noted "12 hubs with pairwise review prompt template"). Investigate each when bandwidth permits. Resolve disposition (real-and-active / real-and-stale / abandoned / never-existed / renamed) before any fold-in. Until resolved, these are NOT in §3 source registry. | | Memory Intake and At-Use Disciplines proposal — adopt? | V2 DOC24 review follow-up | Pending red team. If adopted, ~7 OBL rows enter this tracker against DOC72/DOC24/DOC1/DOC73. | | DOC24↔DOC73 full seam audit — when? | V2 DOC24 review extension | Recommended: after DOC73 V1.5 stabilizes. ISS-01b is the canary; more seam findings likely. | | DOC6 status (still active doc number?) | DOC15 R3.1 §3 | DOC15 R3.1 has obligations targeting DOC6 (panels). Verify against current spec list. | | DOC74 reference in user note | Conversation 2026-04-26 | User mentioned DOC74; not in any current doc list. Possibly typo for DOC73, possibly a deprecated number. Verify. | | DOC15 R3.1 contract maintenance | This tracker's source registry | DOC15 R3.1 is stale (predates DOC72/DOC73/DOC25/most addenda). After full fold-in into OP-A, archive R3.1; do not refresh as standalone. | | DOC1 R1 status | V3 carryover §10.3 | "Partially stale — Storage model JSONL → SQLite. Governance logic current." Schedule next review. | --- ## 10. Maintenance Log | Date | Action | By | |---|---|---| | 2026-04-26 | **Created V1.** Folded in: V2 DOC24 review (full cross-doc findings); DOC24 R2.5 §22 amendment matrix; DOC15 R3.1 contract (feature-area-grouped extraction of §§1-11); CD Master Integration Index R1 (registry content). Deferred: Memory Intake and At-Use Disciplines proposal (pending red team); DOC3 R9.2 / DOC14 R2 / DOC72 maps / CD-A 4.1.26 / DOC10 ledger / DOC16 deferred / Running Brief / Knowledge Store Unification (not yet read). | Claude Opus 4.7 | | 2026-04-26 | **V2 corrections pass.** Removed unverified source documents from §3 "not yet folded in" list (DOC72 Knowledge Store Integration Map R2 + Verification, DOC10 Orchestration Integration Ledger R10, DOC16 Deferred Additions R5.3, Running Brief Remediation v6, ELNOR Knowledge Store Unification Plan R1, Cross-Document Integration Plan v4). These were inherited from CD Master Integration Index R1 without verification. Moved to §9 Open Meta-Architecture Questions as inventory item requiring investigation. Tightened §3 scope rule. No fold-in work performed; no §6 obligation rows changed. | Claude Opus 4.7 | --- ## 11. End of tracker **Self-test for usability:** before closing this tracker as V1, verify each of the following: 1. ✅ Reader can find what's pending for a target doc by reading exactly one section (§6.X for that doc). 2. ✅ Each obligation row has source citation, status, calibration anchor. 3. ✅ Status key is consistent with existing DOC15 R3.1 format (no learning curve for reviewers familiar with that doc). 4. ✅ Source documents are listed with last-updated dates so staleness is assessable. 5. ✅ Schema for Absorbed and Deferred sections is established (even though both are empty in V1). 6. ✅ Meta-architecture questions captured so they don't get lost. 7. ⚠ Coverage gap explicit: §3 lists which sources are not yet folded in, with plan. **Maintenance discipline:** at the end of every red team review or spec revision session, the reviewer's last step is to update §6 (move absorbed items, update statuses, add new findings as new rows), §10 (log the action), and if applicable §3 (register newly-folded source documents). If this tracker stops being maintained, fall back to the per-doc companions and source documents listed in §3.