ADDENDA_STATE.md
OP-A and Operations and Trackers/ADDENDA_STATE.md
# ADDENDA_STATE — Per-Addendum Workflow Tracker
**Date created:** 2026-04-26
**Last touched:** 2026-05-24 (R3.62 TWO-DAY-GAP-CATCHUP sync — backfills R3.61 SUBSTANTIVE STRUCTURAL-DRIFT bump on 2026-05-22 ~11:12 local that captured 2 NEW DAMS files (V4 + V4.1) and ran a RECONCILIATION PASS adding A-80 BDSM v0.3.1 / A-81 KDA v0.3.1 / A-82 DAMS V3 / A-83 DAMS V3 (1) / A-84 DAMS V4 / A-85 DAMS V4.1 to MSL §4 but never updated SPEC_STATE.md / ADDENDA_STATE.md / DRIFT_LOG.md / dashboard.html / carryover prompt on its own window — **FIRST EVER substantive-bump-skipped-housekeeping observation** (prior alias-bump-skipped-housekeeping family R3.13/R3.16/R3.18/R3.19/R3.23/R3.24/R3.25/R3.41/R3.49/R3.51/R3.54/R3.55/R3.57/R3.60 all involved alias-only firings; R3.61 is the first SUBSTANTIVE bump to skip housekeeping; new anomaly variant promoted as own SKILL.md item candidate). Plus 2026-05-23 had ZERO sync firing observed — FIRST EVER silent calendar day in this scheduled-task run history (no DRIFT_LOG entry, no MSL bump, no operations-state ledger firing window matching expected daily cadence; likely missed-firing rather than zero-drift run-marker since no run-marker was appended). Today's R3.62 catchup ALSO captures post-R3.61 in-scope archival events: DAMS V1 + V2 + V3 + V3 (1) + V4 all MOVED from `Addenda Proposals & In Progress/DOC 80 DAMS/` → `Addenda Proposals & In Progress/Archived Addenda Proposals and In Progress/` between R3.61 alias write and today (mtimes preserved across move: V1 2026-05-20 11:32, V2 2026-05-20 13:42, V3 2026-05-21 05:56, V3(1) 2026-05-21 05:59, V4 2026-05-22 04:19); DAMS V4.1 (sole remaining active file in §A8) modified 2026-05-22 04:27 local (post-R3.61 content edit, +0.1% size change V4 → V4.1 = 62,380 → 64,604 bytes per R3.61 narrative). §A8 DOC 80 DAMS effective active count = 1 (V4.1 only); preserved-for-traceability rows = 5 (V1/V2/V3/V3(1)/V4 all moved to global addenda archive — auto-pass no-removal policy retains rows with FILE MOVED TO GLOBAL ARCHIVE annotation). **NEW rows added today via R3.62 catchup:** A-80 `DOC24 Addenda/DOC24_KDA_R3_DRAFT_v0_3_1.md` in §A.3 (mtime 2026-05-20 23:14 local, size 129,645 bytes — file existed on disk since R3.58 era 2026-05-20 but was never counted or rowed by any prior revision per R3.61 reconciliation finding (b); fourth-decimal-place patch-suffix successor to A-76 v0.3 KDA mirroring BDSM v0.3 → v0.3.1 pattern from R3.59; A-76 row gets natural-progression-intra-version-patch-successor annotation; second instance of fourth-decimal-place patch suffix in DOC24 family after BDSM v0.3.1); A-83 `DOC 80 DAMS/Archived (now in global addenda archive)/DAMS_V4_CONSOLIDATED_ARCHITECTURE_PROPOSAL.md` in §A.8 (mtime 2026-05-22 04:19 local, size 62,380 bytes — central reframe of DAMS as one demoted substrate inside a larger memory architecture per R3.61 §12 narrative: memory-as-control-problem; Premise Families base object; Context Compiler emitting warranted packets; recompile-on-resume + cognitive diff; thick-floor/thin-swappable-judgment invariant; domain-packs; Knowledge Topic primitive; lineage V2 → meta-review → V3.1 → V4; FILE MOVED TO GLOBAL ARCHIVE post-R3.61 between 2026-05-22 11:12 and 2026-05-24); A-84 `DOC 80 DAMS/DAMS_V4_1_CONSOLIDATED_ARCHITECTURE_PROPOSAL.md` in §A.8 (mtime 2026-05-22 04:27 local, size 64,604 bytes; per R3.61 §12 V4.1 adds vs V4: §B.8 worked three-Topics walkthrough establishing multi-parent acyclic DAG + §C.1 sharpened "the merge is itself the audit" epistemics, no structural change; sole remaining active file in §A8 post-V4 archival). **§A8 V1/V2/V3/V3(1) row annotations:** all four rows get FILE MOVED TO GLOBAL ARCHIVE 2026-05-22 OR 2026-05-23 (exact archive timestamp not preserved; mtime preserved across move) annotations. ADDENDA_STATE uses A-80 for KDA v0.3.1 / A-83 for DAMS V4 / A-84 for DAMS V4.1 — preserves existing ADDENDA_STATE numbering pattern of A-78/A-79/A-81/A-82 in §A.8 + A-79 reused in §A.3 (R3.59 numbering bug preserved per auto-pass conservatism); MSL §4 uses A-81/A-84/A-85 — cumulative divergence-by-one-or-two pattern extends to eleventh+ NEW-row cycle. Counts post-R3.62: §A3 = 12 (added KDA v0.3.1); §A8 = 6 rows total (1 active V4.1 + 5 preserved-for-traceability archived V1/V2/V3/V3(1)/V4); §A1 = 35; §A6 = 19; §A7 = 3; total active addenda rows = 87; effective active (excluding archived V1-V4) = 82. SKILL.md tightening recommendation persistence stretches to thirty-EIGHT cycles un-implemented (R3.26 → R3.62); today reinforces (a) item #5 post-edit `stat` verification on claimed-edited files (R3.61 should have stat-checked SPEC_STATE / ADDENDA_STATE / DRIFT_LOG / dashboard / carryover after its narrative-write to detect skipped-housekeeping), and (b) NEW item: substantive-bump-skipped-housekeeping warrants separation from alias-only family since detection signals differ. **Critical cross-doc finding carry-forward unchanged:** DAMS V2/V3's DOC8 phantom finding (DOC8 R3 is 730-line friction engine with no learning engine capabilities) flagged in R3.58/R3.59 still pending human review — now further evidenced by R3.61 §12 DAMS V4 "central reframe of DAMS as one demoted substrate inside a larger memory architecture" central-reframe narrative implying DAMS is no longer a standalone proposal but a memory-architecture-component proposal touching DOC1/DOC8 substantially. S-11 BACKUP_LOG carry-forward: continues since 2026-05-09 last confirmed cloud backup (15-day gap today; 12 → 13 → 15 since R3.60-backfill); three urgent Will actions persist unchanged. S-9 OpenClaw release-alignment: BEHIND-by-10 since 2026.5.12 carry-forward (twenty-eight-day cadence lag today, +2 days since R3.60-backfill). **NEW ANOMALY** flagged: 2026-05-23 silent calendar day — first observed silent calendar day in scheduled-task run history; needs human verification of whether task fired silently or failed to fire (no DRIFT_LOG entry either way). Prior touched 2026-05-22 (R3.60-backfill sync — zero filesystem drift since R3.60 alias write 2026-05-21 ~23:11 UTC; `find -newer MASTER_SPEC_DOCUMENT_LIST_R3.60.md` returned ZERO hits across all in-scope folders. R3.60 was an ALIAS-ONLY operations-state-only firing per SKILL.md Step 5 canonical path (mirrors prior R3.57 + R3.54 firing patterns) that advanced MSL R3.59 → R3.60 but did NOT update SPEC_STATE / ADDENDA_STATE / DRIFT_LOG / dashboard / carryover on its own window — same alias-bump-skipped-housekeeping anomaly family as R3.13/R3.16/R3.18/R3.19/R3.23/R3.24/R3.25/R3.41/R3.49/R3.51/R3.54/R3.55/R3.57. Today's 2026-05-22 backfill sync window mechanically advances state-file mtimes + SPEC_STATE Master Spec List Rev field R3.59 → R3.60 + dashboard `lastRefresh` span. Per SKILL.md Step 5 "If no drift and exactly 1 versioned file exists: skip Steps 5.1-5.3; only run Step 5.4 sanity check" — no MSL bump today; active folder retains R3.60 alias + R3.60 versioned snapshot only (at-most-one-versioned-file invariant intact). Per SKILL.md Step 6 "If no structural changes: do NOT bump the carryover" — carryover remains at V22. **No new ADDENDA_STATE rows added today** (zero new addendum files in scope). Counts all unchanged from R3.59: §A1 = 35, §A3 = 10, §A6 = 19, §A7 = 3, §A8 = 4; total active addenda = 83. SKILL.md tightening recommendation persistence stretches to thirty-six cycles un-implemented (R3.26 → R3.60-backfill). Carry-forward items unchanged: (1) cooldown gate between same-day fires; (2) no-drift-no-bump early-exit guard (RELEVANT TODAY — honored: no MSL/carryover bump on zero filesystem drift); (3) per-row §7 freshness check; (4) subfolders-not-formally-listed backlog at eight (DOC73 V1.6 R1.0 OPERATIVE + DOC23 Addenda + EC Core Addenda + Unified Brain Bucket Lib Proj + DOC73 Addenda and Proposals + DOC23 Addenda/doc23 add b rework sub-sub-folder + Connectors and Integrations Addenda + DOC 80 DAMS); (5) post-edit `stat` verification on claimed-edited files; (6) avoid future-tense claims about un-fired tasks; (7) `mountpoint -q` pre-flight check before `mkdir -p` in S-11 BACKUP_LOG task. **Critical cross-doc finding carry-forward unchanged:** DAMS V2/V3's DOC8 phantom finding (DOC8 R3 is 730-line friction engine with no learning engine capabilities) flagged in R3.58/R3.59 still pending human review. S-11 BACKUP_LOG carry-forward: twelve+ calendar days now since 2026-05-09 last confirmed cloud backup; three urgent Will actions persist unchanged. S-9 OpenClaw release-alignment: BEHIND-by-10 since 2026.5.12 (twenty-six-day cadence lag, +1 day since R3.59). Prior touched 2026-05-21 (R3.59 SUBSTANTIVE STRUCTURAL-DRIFT bump — 5 NEW files detected since R3.58 alias write 2026-05-20 23:15 local: (1) `OPA_V3_17.md` mtime 2026-05-21 01:30 local (+5.7% over V3.16, eighth active-root placement-irregular OPA instance, tracked in SPEC_STATE not ADDENDA_STATE); (2) `OPA_V3_18.md` mtime 2026-05-21 01:47 local (+0.9% over V3.17, FIRST EVER same-day intra-window OPA successor pair ~17min apart; ninth placement-irregular instance; tracked in SPEC_STATE); (3) `DOC24 Addenda/DOC24_Addendum_A_BDSM_V6_5_DRAFT_v0_3_1.md` mtime 2026-05-20 23:15 local — NEW row A-79 in §A.3 (FIRST EVER fourth-decimal-place patch suffix in BDSM chain extending v0.1/v0.2/v0.3/.../FINAL working-draft series with intra-version patch granularity; A-75 v0.3 row above gets natural-progression-intra-version-patch-successor annotation); (4) `DOC 80 DAMS/DAMS_V3_CONSOLIDATED_ARCHITECTURE_PROPOSAL.md` mtime 2026-05-21 05:56 local (size 78,062 bytes, -4% under V2) — NEW row A-81 in BRAND-NEW §A.8 DOC 80 DAMS subfolder; consolidated successor to A-78/A-79 V1+V2 same-day pair from R3.58 backfill; filename change `DAMS_PROPOSAL_V2` → `DAMS_V3_CONSOLIDATED_ARCHITECTURE_PROPOSAL` signals consolidation from proposal-iteration mode to architecture-baseline mode; (5) `DOC 80 DAMS/DAMS_V3_CONSOLIDATED_ARCHITECTURE_PROPOSAL (1).md` mtime 2026-05-21 05:59 local (size 94,239 bytes, +20.7% over primary V3) — NEW row A-82 in §A.8; FIRST EVER same-day intra-folder primary + (1)-duplicate pair where duplicate EXCEEDS primary in size (~3min apart); workflow-signal mystery pending human classification. **R3.58 backfill executed today** (R3.58 substantive structural-drift bump on 2026-05-20 ~17:13 local captured 5 NEW files in MSL §3/§4 but did not update ADDENDA_STATE.md on its own window): backfilled NEW rows A-75 BDSM V6.5 DRAFT v0.3 in §A.3 (+12.6% over v0.2; second instance of v0.x draft pattern within BDSM chain), A-76 KDA R3 DRAFT v0.3 in §A.3 (+37.2% over v0.2; second instance of v0.x draft pattern within KDA chain), A-77 Unified Workspace R0.3 in §A.7 (THIRD explicit supersession declaration in §A.7 multi-parent track R0.1 → R0.2 → R0.3; introduces explicit project mode as primary primitive collapsing R0.2's eleven user-facing concepts), A-78 DAMS V1 NEW in BRAND-NEW §A.8 DOC 80 DAMS subfolder (FIRST EVER DAMS proposal; FIRST EVER addenda subfolder keyed to placeholder DOC numbers DOC80/DOC81 not yet in core spec list), A-79 DAMS V2 in §A.8 (FIRST EVER same-day intra-folder V1→V2 pair in any addenda subfolder, ~2h apart; V2 corrects V1 framing facts via DOC8 phantom finding implying DOC8 R3 may need substantial respec). **Architecturally significant developments captured today:** (a) FIRST EVER fourth-decimal-place patch suffix `_v0_3_1` in BDSM chain extends working-draft series with intra-version patch granularity; (b) FIRST EVER same-day intra-window OPA successor pair (V3.17 → V3.18 ~17min apart) — tighter cadence than R3.58 DAMS V1→V2 ~2h pair; (c) FIRST EVER same-day primary + (1)-duplicate pair where duplicate exceeds primary in size (DAMS V3 vs DAMS V3 (1)) — first observation of (1)-suffix not matching primary; (d) THIRD explicit supersession declaration in §A.7 (R0.1 → R0.2 → R0.3 chain) — structurally unique among addenda tracks; (e) DOC 80 DAMS subfolder now has 4 files (V1+V2 from R3.58 + V3+V3 (1) from R3.59) — first not-formally-listed subfolder to accumulate 4 files in single MSL bump-cycle since formation. ADDENDA_STATE uses A-75/A-76 (R3.58 backfill BDSM v0.3 + KDA R3 v0.3) / A-77 (R3.58 backfill Unified Workspace R0.3) / A-78/A-79 (R3.58 backfill DAMS V1 + V2) / A-79/A-81/A-82 (R3.59 NEW BDSM v0.3.1 + DAMS V3 + DAMS V3 (1)); MSL §4 may use different numbering preserving divergence-by-one pattern across ninth+ NEW-row cycle. SKILL.md tightening recommendation persistence stretches to thirty-four cycles un-implemented (R3.26 → R3.59). Master Spec List bumped R3.56 → R3.59 with R3.57/R3.58/R3.59 narrative folded; carryover bumped V21 → V22; dashboard regenerated; DRIFT_LOG appended. Prior touched 2026-05-20 (R3.56 STATE-FILES-CATCHUP bump — backfills R3.55's MSL-captured-but-state-files-missed structural drift. R3.54 (alias-only operations-state-only firing 2026-05-19 ~11:09 UTC) introduced zero new content. R3.55 (substantive structural-drift firing 2026-05-19 ~23:17 UTC) captured 5 NEW files (OPA V3.16 in MSL §3 + 4 addenda) but failed to update ADDENDA_STATE / SPEC_STATE / dashboard / carryover. Today's R3.56 catchup adds 4 NEW addendum rows: A-70 `ELNOR_SUBAGENT_ARCHITECTURE_V5_2_AUDITED.md` in §A.1 (top-level natural-progression `_AUDITED` successor to A-66 V5.1; mtime 2026-05-19 16:18 local, size 95,218 bytes — +34,080 bytes / +55.7% over V5.1; first observed `_AUDITED` filename suffix in any subagent chain, consistent with audit-driven red-team incorporation pattern); A-71 `DOC24 Addenda/DOC24_Addendum_A_BDSM_V6_5_DRAFT_v0_2.md` in §A.3 (natural-progression DRAFT successor to A-22 V6.4 operative; mtime 2026-05-19 20:50 local, size 151,668 bytes — +7.5% over V6.4; `_DRAFT_v0_2` working-draft suffix indicates first observation of v0.1/v0.2/.../FINAL series pattern); A-72 `DOC24 Addenda/DOC24_KDA_R3_DRAFT_v0_2.md` in §A.3 (natural-progression DRAFT successor to A-19 R2 long-form via filename canonicalization to R3 short-form; mtime 2026-05-19 18:54 local, size 93,832 bytes — +28% over R2; third instance of canonicalization pattern after ELNOR_SUBAGENT V4 → V5.1 in R3.53 + DOC23 ADDB V2 → V3 in R3.44); A-74 `DOC23 Addenda/DOC23_FAMILY_SELF_LEARNING_COHERENCE_MAP_V1.md` in §A.6 (NEW cross-cutting reference map V1; mtime 2026-05-19 19:43 local, size 53,808 bytes; spans Addenda A R4.1 V6 + Addenda B Core R0.7 + Addenda B Addendum V3.2 + 3 subsystem sub-addenda + Common Contracts V1.1; likely needs reclassification as SUPPORT / REFERENCE MAP / NON-OWNER DRAFT analogous to A-49 Card Integration Map V2 + A-32 ELNOR Search Reference R1). ADDENDA_STATE uses A-70/A-71/A-72/A-74 (skips A-73 to preserve historical row-bound divergence pattern); master spec list §4 uses A-71/A-72/A-73/A-74 — cumulative divergence-by-one pattern extends to EIGHT+ NEW-row cycles. **R3.55 V21 carryover-claim-without-materialization anomaly resolved today** by actual V21 creation in `Prompts/`. **A-66 V5.1 row + A-22 V6.4 row + A-19 R2 row get natural-progression-supersession annotations** (V5.1 superseded by V5.2 AUDITED; V6.4 has DRAFT successor pending; R2 has DRAFT successor pending). **Two intra-day DOC24 successor drafts within ~2h window** (BDSM V6.5 + KDA R3) — first multi-DOC24-draft drift in single MSL bump (R3.55); coordinated DOC24 family redrafting pass possibly triggered by DOC23 FAMILY_SELF_LEARNING_COHERENCE_MAP_V1 introduction earlier same day. Master Spec List row in SPEC_STATE.md advanced R3.53 → R3.56; carryover V20 → V21 (materializing R3.55 phantom claim); dashboard regenerated. SKILL.md tightening recommendation persistence stretches to thirty-one cycles un-implemented (R3.26 → R3.56) with carry-forward items unchanged. Prior touched 2026-05-19 (R3.53 SUBSTANTIVE STRUCTURAL-DRIFT bump — 4 NEW addendum files detected in §A.1: (1) `ELNOR_SUBAGENT_ARCHITECTURE_V5_1.md` (top-level; mtime 2026-05-18 23:55, size 61,138 bytes) — natural-progression successor to A-5 `ELNOR_SUBAGENT_PRECOMPUTE_TOOL_OPTIMIZATION_NOTES_V4.md` via filename canonicalization V4 PRECOMPUTE_TOOL_OPTIMIZATION_NOTES → V5.1 ARCHITECTURE (analogous to V2 → V3 OUTCOME_EVAL_REVISION → OUTCOME_EVALUATOR_REVISOR canonicalization in DOC23 Addenda B chain); V5 briefly-extant or skipped (no V5 file observed); (2) `DOC11 Openclaw Addenda & Docs/DOC11_R15_OPENCLAW_RELEASE_ALIGNMENT_AMENDMENT_PROPOSAL_R3.md` (mtime 2026-05-19 03:06, size 76,467 bytes) — DOC11 R15 amendment proposal R3, successor to A-34 R2; R2 file moved to NEW intra-subfolder archive `DOC11 Openclaw Addenda & Docs/Archived/` (folder created today, mtime 2026-05-19 03:09) — first intra-subfolder archive in this subfolder, mirrors DOC23 Addenda local-archive pattern from R3.47; (3) `DOC11 Openclaw Addenda & Docs/DOC11_R15_OPENCLAW_RELEASE_ALIGNMENT_AMENDMENT_PROPOSAL_R3_COVERAGE_AUDIT.md` (mtime 2026-05-19 03:07, size 3,516 bytes) — short coverage-audit companion document attached to R3 amendment proposal; (4) `DOC11 Openclaw Addenda & Docs/OPENCLAW_RELEASE_ALIGNMENT_RUNNING_SPEC_UPDATE_LIST_R3.md` (mtime 2026-05-19 03:07, size 19,278 bytes) — R3 successor to OPENCLAW_RELEASE_ALIGNMENT_RUNNING_SPEC_UPDATE_LIST_R2 (was tracked in SPEC_STATE Cross-Cutting/Support row `OpenClaw Release Align`; R2 file moved to intra-subfolder archive today alongside R2 ADD REVIEW variant). **NEW rows A-66 through A-69 added below in §A.1.** Plus one NEW core spec row in SPEC_STATE §3: OPA V3.15 (active root, placement-irregular; mtime 2026-05-19 05:36, size 675,447 bytes; +138,064 bytes over V3.13; V3.14 skipped/briefly-extant; placement-irregularity backlog extends to 6 instances). Also folds R3.51 + R3.52 narrative into the trackers — R3.51 was the operations-state-only firing-capture bump on 2026-05-18 ~04:08 local (S-10 RECENT_WORK_SUMMARY_LOG + S-11 BACKUP_LOG TENTH-STRIKE bind-mount-proof failure with defensive pre-check applied for the second consecutive run); R3.52 was the same-day third-firing SUBSTANTIVE STRUCTURAL-DRIFT bump at 2026-05-18 ~17:50 UTC capturing 3 NEW files (OPA V3.13 + DOC23 ADDB V3.3 + DOC23 Common Contracts V1.1; latter two in `DOC23 Addenda/doc23 add b rework/` sub-sub-folder). Neither R3.51 nor R3.52 updated SPEC_STATE.md or ADDENDA_STATE.md on its own window — today's R3.53 run is the first opportunity. Tracker numbering divergence: ADDENDA_STATE uses A-66/A-67/A-68/A-69 for the four new top-level rows; master spec list §4 uses A-67/A-68/A-69/A-70 — extends cumulative divergence-by-one pattern to SEVEN+ NEW-row cycles. **SKILL.md tightening recommendation persistence stretches to twenty-seven cycles** un-implemented (R3.26 → R3.53). Carry-forward items unchanged with one partial-resolution: the DOC11 Openclaw Addenda & Docs subfolder formal scope inclusion item is partially RESOLVED today by the creation of its first intra-subfolder archive — the subfolder is now actively tracked via its NEW addendum rows. **A-1 DOC11 R15 R1 + A-34 DOC11 R15 R2 + A-5 ELNOR SUBAGENT V4 rows below get supersession annotations** (R1 + R2 superseded by R3; V4 superseded by V5.1 via filename canonicalization). Prior touched 2026-05-18 (R3.50 SUBSTANTIVE STRUCTURAL-DRIFT bump — 1 NEW addendum file detected in §A.6: `Addenda Proposals & In Progress/DOC23 Addenda/DOC23_ADDENDA_A_TASK_OPTIMIZATION_R4_1_V6 (1).md` (mtime 2026-05-18 06:05, size 405,498 bytes). V6 successor in DOC23 Task Optimization R4.1 chain — A-47 R4.1 V2 was last formally tracked predecessor in R3.12; chain advanced V2 → V3 → V4 → V5 → V6 with intermediate revisions never materialized at sync windows (briefly-extant pattern observed previously for R4.1 V1). V6 size 405,498 bytes ≈ 2.6× A-47 V2's 154,930 bytes — substantial growth. Per coordination V3 FINAL outputs noted in R3.49 (A-65 Common Contracts V1 lists "DOC23 Addenda A R4.1 V3" as consumer), the A-track has been at V3 since coordination V3 work; V6 likely incorporates coordination V3 FINAL outputs plus further audit closure passes. Filename has "(1)" suffix suggesting Will copied from another location (Downloads-copy pattern observed in DOC73 V1.6 Adjudication Card and DOC23 REPROMPT duplicates). **NEW row A-65 added below in §A.6** (continues ADDENDA_STATE sequence A-64 Common Contracts V1 → A-65 R4.1 V6; master spec list §4 uses A-66 — preserves cumulative divergence-by-one pattern extending to SIX NEW-row cycles: R3.33 + R3.39 + R3.41 + R3.44 + R3.47 + R3.49 + R3.50). **Plus three NEW core spec files captured in SPEC_STATE.md §3 (informational here):** OPA V3.11 (Operations Docs/ location ending V3.8/V3.9 placement-irregularity pattern), OPA V3.12 (active root reverting to placement-irregular), and implicit OPA V3.10 archival transit (brief-extant). MSL bumped R3.49 → R3.50; carryover bumped V18 → V19 (V19 also materialized R3.49's phantom-V19 narrative-claim-without-materialization). Audit-cleanup pass moved R3.48 (leftover from R3.49) + R3.49 versioned files to `Subsumed Specs/Archived Master Spec Lists/`. SKILL.md tightening recommendation persistence stretches to twenty-six cycles un-implemented (R3.26 → R3.50). Prior touched 2026-05-17 (R3.47 SUBSTANTIVE STRUCTURAL-DRIFT bump — 3 NEW files detected since R3.46 alias write at 2026-05-16 ~11:30 UTC; `find -newer MSL_R3.46.md` returned exactly three file hits in active scan folders: (1) `DOC24_R3_1_1.md` in active root (mtime 2026-05-17 03:58 local = 10:58 UTC, size 292,034 bytes) — R3.1.1 audit closure patch successor to R3.1, seven audit gaps closed per file-header lineage "R3 + V1 + V1.1 + V1.2 + V1.3 + V1.4 + R3.1 audit closure"; predecessor `DOC24_R3_1_CONSOLIDATED.md` atomically moved to `Subsumed Specs/` in same 03:58 window; (2) `OPA_V3_9.md` in active root (mtime 2026-05-17 07:15 local = 14:15 UTC, size 438,146 bytes) — OP-A V3.9 patch session per V4 §0.3 for DOC24 R3.1.1 adjudication closure; placement-irregular (header says folder is DOC73 R1.6 Build/ but active-root copy maintained); same pattern as V3.8 in R3.18 sync; (3) `Addenda Proposals & In Progress/DOC23 Addenda/DOC23_ADDB_ADDENDUM_OUTCOME_EVALUATOR_REVISOR_V3_1.md` (mtime 2026-05-17 03:28 local = 10:28 UTC, size 437,051 bytes — ~21% larger than V3 360,081 bytes) — natural-progression successor to A-56 V3 in DOC23 Addenda B Addendum chain (V1 → V2 → V3 → V3.1). **NEW row A-58 added below in §A.6** for the V3.1 file. **INTRA-SUBFOLDER ARCHIVAL EVENT (auto-detected):** new local archive `DOC23 Addenda/Archived DOC23 addenda/` subfolder created (mtime 2026-05-17 04:15) and populated with files moved from DOC23 Addenda root including A-56 V3 + A-54 V2 + several older predecessor files (`DOC23_ADDENDA_A_R4_0_CONTEXT_MANAGEMENT_PROPOSAL_V1.md` = A-43, `DOC23_ADDENDA_B_R0_5_AUDIT_COMPLETE_MERGE_PACK...` = A-48 alias, `DOC23_ADDENDA_B_TASK_INTELLIGENCE_MEMORY_OBSERVABILITY_R0_3...` = A-50 alias predecessor, `DOC23_ADDENDA_B_TASK_INTELLIGENCE_MEMORY_OBSERVABILITY_R0_6_1...` = A-51 alias predecessor, `DOC23_ADDENDA_B_TASK_INTELLIGENCE_MEMORY_OBSERVABILITY_R0_6_3...` = A-52 alias predecessor, `DOC23_REPROMPT_SYSTEM_ADDENDUM.md` = A-44). A-56 V3 + A-54 V2 rows below get intra-subfolder-archive annotations (FILE MOVED TO LOCAL ARCHIVE 2026-05-17). This is LOCAL intra-subfolder archival, distinct from global `Archived Addenda Proposals and In Progress/` archive at the `Addenda Proposals & In Progress/` root level — auto pass treats both as out-of-scope for active addenda tracking. Tracker numbering divergence carry-forward: master spec list §4 uses A-59 for V3.1; ADDENDA_STATE.md uses A-58 — cumulative divergence-by-one pattern now extends to FIVE NEW-row cycles (R3.33 + R3.39 + R3.41 + R3.44 + R3.47). Master spec list bumped R3.46 → R3.47; carryover prompt bumped V17 → V18. SKILL.md tightening recommendation persistence stretches to twenty-three cycles un-implemented (R3.26 → R3.47). Prior touched 2026-05-16 (R3.44 substantive structural-drift bump — 2 NEW addendum files detected since R3.43 alias write at 2026-05-15 ~17:00 UTC; `find -newer MSL_R3.43.md` returned exactly two file hits: (1) `Addenda Proposals & In Progress/DOC23 Addenda/DOC23_ADDB_ADDENDUM_OUTCOME_EVALUATOR_REVISOR_V3.md` (mtime 2026-05-16 02:44 UTC, size 360,081 bytes, 8,555 lines — ~2.7× V2 file's 133,682 bytes; per V3 file header: Status "V3 specification", Version 3.0, Prepared 2026-05-15; source documents include DOC23 Addenda B Addendum V3 Adjudication Card V3.1 + Canonicalization Patch V2 — V3 is post-adjudication tightening; filename canonicalization shift from V2's `OUTCOME_EVAL_REVISION` to V3's `OUTCOME_EVALUATOR_REVISOR`; 13 explicit cross-doc dependencies enumerated; new architectural primitives: Outcome Compiler / Revision Compiler / Revision Dispatcher / Candidate artifact versions / Plan assurance policy / Taint and policy model / formal Pattern learning §22 / end-to-end Feedback pipeline; V3 §0.3 Canonical Naming Table + §0.4 Canonical Enum Inventory + §0A Implementation Discipline Preamble all normative; elevates V2 from proposal to spec status with explicit normative discipline; no explicit "Supersedes:" header but auto pass treats as natural-progression successor in DOC23 Addenda B Addendum chain V1→V2→V3); (2) `Addenda Proposals & In Progress/Unified Brain Bucket Lib Proj/Unified_Workspace_Library_WorkContext_Proposal_R0_2.md` (mtime 2026-05-16 00:04 UTC, size 88,291 bytes, 3,220 lines — ~38% larger than R0.1's 63,741 bytes; per R0.2 file header explicit `**Supersedes:** Unified_Workspace_Library_WorkContext_Proposal_R0_1.md for current discussion purposes.`; title evolution drops "Output Routing", "Task Scope", "Working Set", adds "Resume Work" — significant scope refinement consolidating around resume-work surface; scope explicitly excludes DOC23 from owner targets (R0.1 included DOC23 as co-owner; R0.2 demotes DOC23 to integration-boundary-only status); new Library source status model with three additive statuses Linked/Indexed/Learned; retires R0.1's Available + Cataloged statuses; new Co-Work-like behavior in Output Location for source-folder affinity defaults; retains R0.1 core product model + core philosophy axioms verbatim). **NEW row A-56 added below in §A.6** for the V3 file (natural-progression successor to A-54 V2 + A-53 V1 in DOC23 Addenda B Addendum chain; V2 + V1 rows get supersession annotations pending human archival decisions). **NEW row A-57 added below in §A.7** for the R0.2 file (explicit Supersedes of A-55 R0.1 per R0.2 file header; R0.1 row gets supersession annotation pending human archival decision). NB: master spec list §4 uses A-57 for V3 / A-58 for R0.2; ADDENDA_STATE uses A-56 for V3 / A-57 for R0.2 — preserves R3.33-onward numbering divergence by one row, with cumulative divergence now extending to two new R3.44 rows (R3.33: A-53 vs A-54 + R3.39: A-54 vs A-55 + R3.41: A-55 vs A-56 + R3.44: A-56 vs A-57 / A-57 vs A-58). Master spec list bumped R3.43 → R3.44; carryover bumped V16 → V17. SKILL.md tightening recommendation persistence stretches to TWENTY cycles un-implemented (R3.26 → R3.44); R3.44's V3 + R0.2 substantive drift is unrelated to tightening backlog but provides natural test bench for next cycle's stat-verification + scope-list-expansion items. Prior touched 2026-05-15 (state-file backfill-only run — zero filesystem drift since R3.41 alias write 2026-05-14 23:11 UTC; `find -newer MSL_R3.41.md` returned ZERO hits across all in-scope folders. Per SKILL.md Step 5 "If no drift and exactly 1 versioned file exists: skip Steps 5.1-5.3; only run Step 5.4 sanity check" — Step 5.4 confirms exactly one versioned file (R3.41) + alias in active folder; invariant intact. No master spec list bump; no carryover bump. But: R3.40 + R3.41 narrative was not folded into SPEC_STATE / ADDENDA_STATE / DRIFT_LOG / dashboard yesterday — today's backfill executes those advances. **NEW row A-55 added below in §A7** for the Unified Brain Bucket Lib Proj proposal file detected by R3.41 (mtime 2026-05-14 09:18:21 PDT = 16:18 UTC, size 63,741 bytes) but not yet folded into ADDENDA_STATE since R3.41 sync did not touch this file. NB: master spec list §4 uses A-56 for the same file; ADDENDA_STATE uses A-55 — preserves the R3.33-onward numbering divergence by one row. **§A7 is a BRAND-NEW subsection** mirroring the §A.4/§A.5/§A.6 single-parent subfolder pattern but for multi-parent cross-doc proposals. **R3.41 V16 → V17 carryover-bump narrative divergence flagged (informational anomaly):** R3.41 §12 changelog claims carryover prompt was bumped V16 → V17 but the V17 file was never materialized in `Prompts/` (only V16 dated 2026-05-14 10:14 remains). Carryover is therefore actually still at V16 not V17. Today's pass does NOT materialize V17 because (a) zero structural drift today warrants no carryover bump, and (b) reconstructing what V17 content "should have been" is ambiguous. Pattern logged in today's DRIFT_LOG entry; awaits Will-side decision (either accept V16 as the operative carryover and patch R3.41 narrative, or author a V17 reflecting R3.41 substantive-drift content). Same alias-bump-skipped-housekeeping family as R3.13/R3.16/R3.18/R3.19/R3.23/R3.24/R3.25 + yesterday's R3.41 V17 narrative-vs-execution divergence. SKILL.md tightening recommendation persistence stretches to EIGHTEEN cycles un-implemented; today reinforces #5 post-edit `stat` verification on claimed-edited files since `stat`-checking Prompts/V17 would have caught yesterday's R3.41 narrative-vs-execution divergence at write time.) Prior touched 2026-05-14 (R3.39 substantive structural-drift bump — NEW row A-54 added below in §A6 for `DOC23_ADDB_ADDENDUM_OUTCOME_EVAL_REVISION_V2.md` (mtime 2026-05-14 03:32 UTC, size 133,682 bytes, 2,740 lines). Per V2 file header SUPERSEDES the V1 proposal `DOC23_ADDENDA_B_PROPSAL ADDITION FOR R0_6_5_OUTCOME_EVALUATION_SOURCE_WORKSPACE_FORUM_FEEDBACK_PROPOSAL.md` (= existing A-53 R0.6.5). **Supersession-and-replace pattern RESTORED** after the R3.33 one-off "stacked proposal not folded" pattern; V1 file remains in active folder pending human archival decision. V2 is substantial architectural revision adding eleven primitives V1 lacked (plan-and-execute layer via `step.revisor`; RevisionPlan schema; Revision Bus runtime; `revision_in` port contract; targeted evaluation mode; per-outcome progress signals beyond pass/fail; cascading revalidation via declared dependencies; two-budget iteration model; plan review forum semantics distinct from runtime orchestration; text-to-outcome inference pipeline; skill-graph integration for learned patterns). A-53 V1 row below gets supersession annotation. Carryover prompt bumped V15 → V16 to capture the V2 supersession + new architectural primitives. Master spec list bumped R3.36 → R3.39 (with R3.37 and R3.38 backfill into Notes; R3.36/R3.37/R3.38 versioned files all archived in this run per audit-cleanup rule — they had accumulated in active folder from yesterday's R3.37/R3.38 same-day double-bump pattern). NB: ADDENDA_STATE numbering uses A-54 for the new V2 row (continues A-53 R0.6.5 → A-54 V2 SUPERSESSION sequence); master spec list §4 numbering may use A-55 for the same file (preserving R3.33 divergence-by-one pattern). The two trackers' numbering is internally consistent within each file but DOES diverge by one in §A6 going forward.) Prior touched 2026-05-13 (pure no-drift run-marker — second consecutive no-drift day; carryover unchanged at V15; master spec list unchanged at R3.36; no addenda churn since R3.33. S-11 BACKUP_LOG seventh-strike two-consecutive-failed-runs anomaly carries forward URGENT-FAILURE-MODE-EXTENDING from R3.36 — BACKUP_LOG.md mtime is 2026-05-11 14:45 UTC, no firing in 48+ hours. SKILL.md tightening recommendation persists thirteen cycles. NB: yesterday's R3.36-backfill sync claimed to advance this `Last touched` header from 2026-05-10 → 2026-05-12 but the edit was not actually applied to file content — filesystem mtime stayed at 2026-05-10 10:14; today's pass executes the advance properly.) Prior substantive update was 2026-05-10 (R3.33 substantive update — NEW row A-53 added below in §A6 for `DOC23_ADDENDA_B_PROPSAL ADDITION FOR R0_6_5_OUTCOME_EVALUATION_SOURCE_WORKSPACE_FORUM_FEEDBACK_PROPOSAL.md` (DOC23 Addenda B R0.6.5 stacked proposal; mtime 2026-05-10 00:14 UTC, size 74,733 bytes); first NEW addendum row added since A-51 R0.6.4 in R3.19 substantive update on 2026-05-05; R3.20–R3.32 were all operations-state-only or backfill bumps with no addenda-row changes; R3.33 ends that fourteen-revision quiet window with structural drift requiring a new row. NB: ADDENDA_STATE numbering uses A-53 for the new row (continuing the existing sequence from A-51 R0.6.4 → A-52 (1)-suffix duplicate informational row → A-53 R0.6.5 NEW); master spec list §4 numbering uses A-54 for the same file (master spec list reserves A-53 for R0.6.4 because it had different ordering at A-51 split). The two trackers' numbering is internally consistent within each file but DOES diverge by one in the §A6 DOC23 Addenda subfolder going forward.
**Status:** Active operations file — update after every addendum review or integration session
**Authoritative for:** Per-addendum review status, disposition decisions, integration status. **NOT** authoritative for addendum content (the file is authoritative for that).
## How to read
One row per active addendum or proposal in `Addenda Proposals & In Progress/`. Already-integrated addenda live in `Integrated Addenda/` subfolder and appear in §B for traceability.
**Reviewed values:**
- `not_yet` — no review tracked
- `in_progress` — review rounds underway
- `done` — review complete (note round count if relevant)
**Disposition values:**
- `tbd` — not yet decided
- `absorb` — fold into existing parent operative spec (post-absorption rule applies — archive the addendum after)
- `promote_new` — graduate to standalone numbered doc (e.g., DOC25 from prior addendum)
- `split` — split content across multiple parent docs
- `kill` — abandon
- `integrated` — fully integrated; archived
**Integration Status values:** `pending`, `in_progress`, `done` (with date), `archived` (with date)
---
## A. Active Addenda (in `Addenda Proposals & In Progress/` and subfolders)
### A.1 Top-level addenda
| ID | Filename | Date | Parent Spec(s) | Reviewed | Disposition | Disp. Target | Integration Status | Int. Date | Notes |
|---|---|---|---|---|---|---|---|---|---|
| A-1 | `DOC11_R15_OPENCLAW_RELEASE_ALIGNMENT_AMENDMENT_PROPOSAL.md` | 2026-04-14 | DOC11 R14 | not_yet | tbd | DOC11 (likely absorb into R15) | pending | — | OpenClaw release alignment through 2026.4.12. Plugin/capability discovery, commands.list, memory/dreaming controls, channel generalization. **SUPERSESSION CHAIN UPDATE (R3.53, 2026-05-19):** R1 (this row) → R2 (= A-34) → R3 (= A-67 NEW). R1 file already archived to global `Archived Addenda Proposals and In Progress/`; R2 newly moved to intra-subfolder archive `DOC11 Openclaw Addenda & Docs/Archived/` today; R3 active in `DOC11 Openclaw Addenda & Docs/` subfolder. |
| A-2 | `DOC3_R11_3_ADDENDA_A_R2_2_PROPOSAL_V1.md` | 2026-04-15 | DOC3 R11.3 Addenda A; DOC72, DOC11, DOC20, DOC24 BDSM, PropA | not_yet | tbd | DOC3 R11.3 Addenda A | pending | — | **FILE MOVED OUT OF ACTIVE FOLDER (auto-detected 2026-04-29 by nightly sync):** archived to `Archived Addenda Proposals and In Progress/DOC3_R11_3_ADDENDA_A_R2_2_PROPOSAL_V1.md`; superseded first by V2 then V3 (also archived) and now by consolidated `DOC3_R11_3_ADDENDA_A_R2_2.md` (new row A-33 below). Row preserved for traceability. Live Recording, Conversational Capture, Intake Coordination. |
| A-3 | `DOC3_R11_3_ADDENDA_A_SEMANTIC SKILLS R2_1.md` | 2026-04-06 | DOC3; DOC72, DOC24, DOC1, DOC8, DOC11, EC Core, Q UI | done (1+ round, ADJ-01 to ADJ-72) | tbd | DOC3 R11.3 | pending | — | **FILE MOVED OUT OF ACTIVE FOLDER (auto-detected 2026-04-29 by nightly sync):** archived to `Archived Addenda Proposals and In Progress/DOC3_R11_3_ADDENDA_A_SEMANTIC SKILLS R2_1.md`. Possibly subsumed by new consolidated `DOC3_R11_3_ADDENDA_A_R2_2.md` (A-33) — content delta not analyzed by auto pass; needs human disposition. Row preserved for traceability. Semantic skill learning, demonstration mode, graph integration. |
| A-4 | `EC_Core_Addendum_A_V3_3_Compiled_Operative_Spec.md` | 2026-04-16 | EC Core; DOC72, DOC24, DOC8, DOC11, DOC12, DOC20, DOC21/22, DOC1, DOC15, DOC23 | not_yet | absorb | EC Core | pending | — | Data Operations, Processing, System Management Architecture V3.3. Compiled operative companion spec. |
| A-5 | `ELNOR_SUBAGENT_PRECOMPUTE_TOOL_OPTIMIZATION_NOTES_V4.md` | 2026-04-24 | DOC24 R2.5 (primary); DOC72, DOC11, DOC10, DOC12, DOC15, DOC16, DOC18, DOC2, DOC3, DOC8, DOC25, DOC73, EC Core | not_yet | absorb | DOC24 (primary); also touches DOC72/DOC11/DOC73 | pending | — | V4 adds Specialist Sub-Agent Pattern, MemoryAgent, DocumentIntelligenceAgent, composition patterns, monitoring. **SUPERSESSION ANNOTATION (R3.53, 2026-05-19):** Auto pass treats A-66 `ELNOR_SUBAGENT_ARCHITECTURE_V5_1.md` as natural-progression successor via filename canonicalization V4 PRECOMPUTE_TOOL_OPTIMIZATION_NOTES → V5.1 ARCHITECTURE (analogous to V2 → V3 OUTCOME_EVAL_REVISION → OUTCOME_EVALUATOR_REVISOR canonicalization in DOC23 Addenda B chain). V5 briefly-extant or skipped. V4 file remains in active folder pending human archival decision. |
| A-6 | `MEMORY_INTAKE_AND_AT_USE_DISCIPLINES_PROPOSAL_V1.md` | 2026-04-26 | DOC72 R5.72+, DOC24 R2.5+, DOC1, DOC73 V1.4+ | not_yet | tbd | TBD (split likely) | pending | — | NEW. Fix intake-side speech-act collapse + at-use side memory premise weighting. **Per OP-A V2 carryover §1A: NOT foldable into OP-A — pending red team.** |
| A-7 | `MultiDoc_PropA_R6_3_Compiled_Operative_Spec.md` | 2026-04-16 | DOC72, DOC24, DOC24 BDSM, DOC8, DOC20, DOC23, DOC1, DOC11, EC Core Addendum A, DOC21, DOC22 | done (multi-round through R6.3) | split | Multiple parent docs | pending | — | Knowledge Pipeline, Sensitivity Classification, Self-Improvement. 19-tag enum. |
| A-8 | `PACER_PLUGIN_SPEC.md` | 2026-04-11 | Q Plugin System; DOC72, DOC3, DOC24 | not_yet | absorb | Q Plugin System | pending | — | Reference implementation: federal-courts case monitoring. **FILE MOVED OUT OF ACTIVE FOLDER (auto-detected 2026-04-28 by nightly sync):** archived to `Addenda Proposals & In Progress/Archived Addenda Proposals and In Progress/PACER_PLUGIN_SPEC.md` and superseded by `PACER_PLUGIN_SPEC_V1.1.md` (new row A-28 below). Row preserved for traceability. |
| A-9 | `Q_INTEGRATION_SUITE_ADDITIONS_R1.md` | 2026-04-23 | Q Integration Suite Spec; DOC24, DOC11, DOC72, DOC20 | not_yet | absorb | Q Integration Suite Spec (A-10) | pending | — | Firecrawl, Securities Data, MarkItDown additions. |
| A-10 | `Q_INTEGRATION_SUITE_SPEC.md` | 2026-04-11 | Q Plugin System; DOC24 capability registry | not_yet | promote_new (likely) | New numbered doc or absorbed | pending | — | YouTube, Hue, Zoom/Teams transcripts, Apple Reminders, Screenshots. |
| A-11 | `Q_PLUGIN_SYSTEM_ARCHITECTURE_R2.md` | 2026-04-12 | DOC3, DOC24, DOC23, DOC20 | not_yet | promote_new (likely) | New numbered doc | pending | — | Plugin framework with manifest schema, tab registration, settings, scaffold template, Elnor plugin builder workflow. |
| A-12 | `SKILLS_LIVE_RECORDING_UPGRADES_V1.md` | 2026-04-14 | DOC3 R11.3 Addenda A, DOC20, DOC11, DOC72 | not_yet | split | DOC3 + DOC20 + DOC11 + DOC72 sections | pending | — | **FILE MOVED OUT OF ACTIVE FOLDER (auto-detected 2026-04-29 by nightly sync):** archived to `Archived Addenda Proposals and In Progress/SKILLS_LIVE_RECORDING_UPGRADES_V1.md`. Possibly subsumed by new consolidated `DOC3_R11_3_ADDENDA_A_R2_2.md` (A-33) — content delta not analyzed by auto pass; needs human disposition. Row preserved for traceability. Real-time step-by-step feedback during demonstrations, browser observation, durable provenance for raw→semantic mapping. |
| A-13 | `SPOTIFY_INTEGRATION_PART_1_IMMEDIATE_BUILD.md` | 2026-04-11 | Q Plugin System; OpenClaw runtime | not_yet | absorb | Q Plugin System | pending | — | No-backend Spotify build. Lower priority. |
| A-14 | `SPOTIFY_INTEGRATION_PART_2_SCHEDULED_INTAKE.md` | 2026-04-11 | DOC3 R11.3, DOC72, DOC23, DOC8 | not_yet | tbd | TBD | pending | — | Future-build (backend required). |
| A-27 | `EC_CORE_ADDENDUM_A_INTAKE_ROUTING_FOR_CORPUS_BINDINGS_PROPOSAL_V1.md` | 2026-04-27 | EC Core Addendum A V3.3; DOC25, DOC72, DOC73 (corpus source bindings) | not_yet | tbd | TBD | pending | — | Auto-detected 2026-04-28 by nightly sync; needs human classification and disposition. Companion proposal to DOC73 Corpus Source Bindings Proposal V1 (A-30, new DOC73 subfolder). |
| A-28 | `PACER_PLUGIN_SPEC_V1.1.md` | 2026-04-27 | Q Plugin System; DOC72, DOC3, DOC24 | not_yet | tbd | TBD | pending | — | Auto-detected 2026-04-28 by nightly sync; needs human classification and disposition. Supersedes original `PACER_PLUGIN_SPEC.md` V1.0 (A-8 above; original moved to `Archived Addenda Proposals and In Progress/`). |
| A-29 | `CROSS_SPEC_ISSUES_PUNCH_LIST_V1.md` | 2026-04-28 | Multiple operative specs (cross-cutting) | not_yet | tbd | TBD | pending | — | Auto-detected 2026-04-28 by nightly sync; needs human classification and disposition. Cross-spec punch-list staging document. |
| A-31 | `DOC25_FILE_MATERIALIZATION_AND_PROVIDER_PROFILES_PROPOSAL_V1_1.md` | 2026-04-28 | DOC25 V2.0; DOC72, DOC73, EC Core | not_yet | tbd | DOC25 V2.0 (likely absorb) | pending | — | Auto-detected 2026-04-29 by nightly sync; needs human classification and disposition. V1.1 supersedes V1 (V1 file moved to `Archived Addenda Proposals and In Progress/`). Per master spec list R3.1 §12 changelog: "targets DOC25 V2.0 with file-materialization tri-state, expanded sync-provider profiles." |
| A-32 | `ELNOR_SEARCH_ARCHITECTURE_REFERENCE_R1.md` | 2026-04-28 | DOC24, DOC16 16.7, V4 SUBAGENT, DOC25, DOC18, DOC72, DOC73 | not_yet | tbd | TBD (likely SUPPORT/REFERENCE not addendum) | pending | — | Auto-detected 2026-04-29 by nightly sync; needs human classification. Per its own header: non-normative reference document synthesizing search routing across multiple specs; modifies nothing and is NOT an operative spec. May warrant reclassification as `SUPPORT / NON-OWNER DRAFT / REFERENCE` rather than `PROPOSED ADDENDUM`. (Master spec list R3.1 §12 changelog noted same.) |
| A-33 | `DOC3_R11_3_ADDENDA_A_R2_2.md` | 2026-04-29 | DOC3 R11.3 Addenda A (consolidates A-2, A-3, A-12) | not_yet | tbd | DOC3 R11.3 Addenda A | pending | — | Auto-detected 2026-04-29 by nightly sync; needs human classification. Filename drops `_PROPOSAL_V1` suffix → likely the post-RT consolidated R2.2 (V1/V2/V3 of the proposal all archived). May also subsume A-3 Semantic Skills R2.1 and A-12 Live Recording Upgrades V1 (both also archived 2026-04-29) — content delta not analyzed by auto pass; full disposition pending human review. |
| A-34 | `DOC11 Openclaw Addenda & Docs/Archived/DOC11_R15_OPENCLAW_RELEASE_ALIGNMENT_AMENDMENT_PROPOSAL_R2.md` | 2026-04-30 (mtime preserved across intra-subfolder archival move 2026-05-19) | DOC11 R14 (R15 amendment proposal R2) | not_yet | tbd | DOC11 (likely absorb into R15) | archived (intra-subfolder) | 2026-05-19 | **FILE MOVED TO INTRA-SUBFOLDER ARCHIVE (auto-detected 2026-05-19 by R3.53 nightly sync):** moved from `Addenda Proposals & In Progress/` root → `Addenda Proposals & In Progress/DOC11 Openclaw Addenda & Docs/Archived/` (folder created today, mtime 2026-05-19 03:09). First intra-subfolder archive in this subfolder, mirrors DOC23 Addenda local-archive pattern from R3.47. **Superseded by R3 (= A-67 NEW)** per natural-progression in the R1 → R2 → R3 DOC11 R15 amendment proposal chain. Original detection notes preserved: Auto-detected 2026-04-30 by nightly sync; needs human classification. R2 supersedes A-1 (original R15 amendment proposal). Size 77,777 bytes (R1 was 51,307 bytes — ~52% larger). Likely incorporates further OpenClaw release alignment through 2026.4.23 + companion to `OPENCLAW_RELEASE_ALIGNMENT_RUNNING_SPEC_UPDATE_LIST_R2.md` (mtime 2026-04-29 19:21 — also touched in same window; R2 update list ALSO moved to intra-subfolder archive today). Row preserved per auto pass no-removal policy. |
| A-38 | `Archived Addenda Proposals and In Progress/DOC23_ADDENDA_A_TASK_OPTIMIZATION_R2_0.md` | 2026-04-30 | DOC23 R3.1 (primary); Prop-A R6.3 (DSPy self-improvement engine, companion) | not_yet | tbd | DOC23 R3.1 (likely absorb) | pending | — | **FILE MOVED OUT OF ACTIVE FOLDER (auto-detected 2026-05-02 by nightly sync; movement performed in R3.9 alias bump 2026-05-01 ~23:14):** archived to `Archived Addenda Proposals and In Progress/`. Was the first revision of DOC23 Task Optimization (R2.0); superseded by R3.0 (A-39 archived) and R4.0 (A-41 archived; A-42 the (1)-suffix file relocated to new DOC23 Addenda subfolder, treated by Will as canonical R4.0). Row preserved for traceability. Original detection notes: defines `system.experiment` / `step.judge` / DSPy prompt optimization as composable DOC23 modules. |
| A-39 | `Archived Addenda Proposals and In Progress/DOC23_ADDENDA_A_TASK_OPTIMIZATION_R3_0.md` | 2026-04-30 | DOC23 R3.1 (primary); Prop-A R6.3 (companion) | not_yet | tbd | DOC23 R3.1 (likely absorb) | pending | — | **FILE MOVED OUT OF ACTIVE FOLDER (auto-detected 2026-05-02 by nightly sync; movement performed in R3.9 alias bump 2026-05-01 ~23:14):** archived to `Archived Addenda Proposals and In Progress/`. Superseded by R4.0 chain (A-41 archived; A-42 relocated to DOC23 Addenda subfolder as canonical R4.0). Row preserved for traceability. |
| A-40 | `Archived Addenda Proposals and In Progress/DOC23_ADDENDA_A_RUNNING_ADDITIONS.md` | 2026-05-01 | DOC23 Addenda A (Task Optimization) — staging document | not_yet | tbd | DOC23 Addenda A next compile | pending | — | **FILE MOVED OUT OF ACTIVE FOLDER (auto-detected 2026-05-02 by nightly sync; movement performed in R3.9 alias bump 2026-05-01 ~23:14):** archived to `Archived Addenda Proposals and In Progress/`. Staging document for the R2.0→R3.0→R4.0 compile chain, now archived alongside the chain it staged. Row preserved for traceability. |
| A-41 | `Archived Addenda Proposals and In Progress/DOC23_ADDENDA_A_TASK_OPTIMIZATION_R4_0.md` | 2026-05-01 | DOC23 R3.1 (primary); Prop-A R6.3 (companion) | not_yet | tbd | DOC23 R3.1 (likely absorb) | pending | — | **FILE MOVED OUT OF ACTIVE FOLDER (auto-detected 2026-05-02 by nightly sync; movement performed in R3.9 alias bump 2026-05-01 ~23:14):** archived to `Archived Addenda Proposals and In Progress/`. The no-(1)-suffix R4.0 (52,949 bytes) was archived; the (1)-suffix R4.0 (A-42, 41,659 bytes) was kept active and relocated to the new DOC23 Addenda subfolder, signalling that A-42 is the operative R4.0 going forward. Row preserved for traceability. |
| A-42 | `DOC23 Addenda/DOC23_ADDENDA_A_TASK_OPTIMIZATION_R4_0 (1).md` | 2026-05-01 | DOC23 R3.1 (primary); Prop-A R6.3 (companion); A-43 (Judge Context Management Proposal V1, targets R4.1 compilation against this file) | not_yet | tbd | DOC23 R3.1 (likely absorb) | pending | — | **FILE RELOCATED TO NEW DOC23 ADDENDA SUBFOLDER (auto-detected 2026-05-02 by nightly sync; movement performed in R3.9 alias bump 2026-05-01 ~23:14):** moved from `Addenda Proposals & In Progress/` root to new `Addenda Proposals & In Progress/DOC23 Addenda/` subfolder. Per R3.9 disposition pattern — Will archived the no-suffix R4.0 file (A-41, 52,949 bytes) but kept this (1)-suffix file (41,659 bytes, mtime preserved at 2026-05-01 06:44 across the move) active and relocated it to the new subfolder, signalling that A-42's content is canonical R4.0. **Auto-detected; needs human classification — supersession of A-41 by A-42 is now executed via the move pattern but no formal classification has been entered yet.** |
| A-66 | `ELNOR_SUBAGENT_ARCHITECTURE_V5_1.md` | 2026-05-18 (mtime 2026-05-18 23:55, size 61,138 bytes) | DOC24 R3.1.1 (primary); DOC72 R5.73, DOC11 R14 / R15, DOC10, DOC12, DOC15, DOC16, DOC18, DOC2, DOC3, DOC8, DOC25 V2.0, DOC73 V1.5.1, EC Core (broad cross-doc per V4 lineage) | not_yet | tbd | DOC24 (primary); also touches DOC72/DOC11/DOC73 | pending | — | **NEW (auto-detected 2026-05-19 by R3.53 nightly sync; mtime 2026-05-18 23:55, size 61,138 bytes); needs human classification.** **Natural-progression successor to A-5 `ELNOR_SUBAGENT_PRECOMPUTE_TOOL_OPTIMIZATION_NOTES_V4.md`** via filename canonicalization — V4 used "PRECOMPUTE_TOOL_OPTIMIZATION_NOTES" (notes-flavored); V5.1 uses "ARCHITECTURE" (formal/spec-flavored). Pattern is analogous to V2 → V3 filename canonicalization in DOC23 Addenda B Addendum chain (V2 `OUTCOME_EVAL_REVISION` → V3 `OUTCOME_EVALUATOR_REVISOR`) — same Will-side workflow signal that V5.1 elevates the subsystem from notes/proposal status to spec status. **V5 briefly-extant or skipped** — no V5 file observed in active folder or in `Archived Addenda Proposals and In Progress/` at time of detection; likely Will managed an intermediate V5 revision outside sync windows (briefly-extant pattern observed previously for OPA V3.10/V3.14 and DOC23 Addenda A R4.1 V1/V3/V4/V5). V5.1 is smaller than V4 (61,138 vs 80,829 bytes; ~76%) — suggests V5.1 may be a tighter rewrite that has shed older notes content, or a partial spec covering only a subset of V4's scope. Full file-header inspection deferred to next manual review pass. **A-5 V4 row above gets natural-progression-supersession annotation pending human archival decision; auto pass leaves both ACTIVE.** NB: master spec list §4 uses A-67 for this row; ADDENDA_STATE uses A-66 — preserves cumulative divergence-by-one pattern extending to SEVEN+ NEW-row cycles. |
| A-67 | `DOC11 Openclaw Addenda & Docs/DOC11_R15_OPENCLAW_RELEASE_ALIGNMENT_AMENDMENT_PROPOSAL_R3.md` | 2026-05-19 (mtime 2026-05-19 03:06, size 76,467 bytes) | DOC11 R14 (R15 amendment proposal R3) | not_yet | tbd | DOC11 (likely absorb into R15) | pending | — | **NEW (auto-detected 2026-05-19 by R3.53 nightly sync; mtime 2026-05-19 03:06, size 76,467 bytes); needs human classification.** **Successor to A-34 R2** (DOC11 R15 amendment proposal R2). R2 file moved today to NEW intra-subfolder archive `DOC11 Openclaw Addenda & Docs/Archived/` (folder created today, mtime 2026-05-19 03:09) — first intra-subfolder archive in this subfolder, mirrors DOC23 Addenda local-archive pattern from R3.47 (`DOC23 Addenda/Archived DOC23 addenda/`). Size 76,467 bytes — slightly smaller than R2 (77,777 bytes; ~98%); marginal size decrease suggests light revision or tighter editing rather than major architectural change. Likely incorporates further OpenClaw release alignment through 2026.5.12 stable + the BEHIND-by-10 backlog noted in DRIFT_LOG carry-forward. **A-1 R1 + A-34 R2 rows ABOVE get supersession-by-R3 annotations** — A-1 R1 already archived to global `Archived Addenda Proposals and In Progress/`; A-34 R2 newly moved to intra-subfolder archive today. Filed in §A.1 (top-level addenda) consistent with how A-1 and A-34 were filed despite living in DOC11 Openclaw Addenda & Docs subfolder. NB: master spec list §4 uses A-68 for this row; ADDENDA_STATE uses A-67 — preserves cumulative divergence-by-one pattern. |
| A-68 | `DOC11 Openclaw Addenda & Docs/DOC11_R15_OPENCLAW_RELEASE_ALIGNMENT_AMENDMENT_PROPOSAL_R3_COVERAGE_AUDIT.md` | 2026-05-19 (mtime 2026-05-19 03:07, size 3,516 bytes) | DOC11 R15 amendment proposal R3 (= A-67); DOC11 R14 | not_yet | tbd | DOC11 (likely SUPPORT/AUDIT companion to R3 amendment proposal, not standalone addendum) | pending | — | **NEW (auto-detected 2026-05-19 by R3.53 nightly sync; mtime 2026-05-19 03:07, size 3,516 bytes — very small file); needs human classification.** Short coverage-audit companion document attached to A-67 R3 amendment proposal. Per filename pattern `_COVERAGE_AUDIT` suggests this is a checklist/audit of which releases or features the R3 amendment proposal covers — non-normative reference document. **Likely needs reclassification to `SUPPORT / NON-OWNER DRAFT / AUDIT` rather than `PROPOSED ADDENDUM`** (analogous to A-32 ELNOR Search Architecture Reference R1 and A-47 Integration Map V2 reclassification patterns). Full file-header inspection deferred to next manual review pass. NB: master spec list §4 uses A-69 for this row; ADDENDA_STATE uses A-68 — preserves cumulative divergence-by-one pattern. |
| A-69 | `DOC11 Openclaw Addenda & Docs/OPENCLAW_RELEASE_ALIGNMENT_RUNNING_SPEC_UPDATE_LIST_R3.md` | 2026-05-19 (mtime 2026-05-19 03:07, size 19,278 bytes) | DOC11 R15 amendment proposal R3 (= A-67); DOC11 R14; companion to OpenClaw release-alignment workstream | not_yet | tbd | DOC11 (likely SUPPORT companion to R3 amendment proposal — running spec-update list) | pending | — | **NEW (auto-detected 2026-05-19 by R3.53 nightly sync; mtime 2026-05-19 03:07, size 19,278 bytes); needs human classification.** **R3 successor to OPENCLAW_RELEASE_ALIGNMENT_RUNNING_SPEC_UPDATE_LIST_R2** which was tracked in SPEC_STATE Cross-Cutting/Support as `OpenClaw Release Align` row. R2 file moved today to intra-subfolder archive `DOC11 Openclaw Addenda & Docs/Archived/` alongside a `R2 ADD REVIEW` variant. Size 19,278 bytes — significantly smaller than R2 (30,479 bytes; ~63%); the ~37% size reduction suggests R3 may be a tighter summary, or content has been folded into the A-67 R3 amendment proposal. Companion to A-67 R3 amendment proposal. SPEC_STATE Cross-Cutting `OpenClaw Release Align` row updated today to reflect R2 archival. NB: master spec list §4 uses A-70 for this row; ADDENDA_STATE uses A-69 — preserves cumulative divergence-by-one pattern. |
| A-70 | `ELNOR_SUBAGENT_ARCHITECTURE_V5_2_AUDITED.md` | 2026-05-19 (mtime 2026-05-19 16:18 local, size 95,218 bytes) | DOC24 R3.1.1 (primary); DOC72 R5.73, DOC11 R14 / R15, DOC10, DOC12, DOC15, DOC16, DOC18, DOC2, DOC3, DOC8, DOC25 V2.0, DOC73 V1.5.1, EC Core (broad cross-doc per V5.1 lineage) | not_yet | tbd | DOC24 (primary); also touches DOC72/DOC11/DOC73 | pending | — | **NEW (auto-detected 2026-05-19 by master spec list R3.55 nightly sync auto-bump 2026-05-19 ~23:17 UTC; backfilled to ADDENDA_STATE in R3.56 on 2026-05-20 since R3.55 did not update ADDENDA_STATE.md); needs human classification.** **Natural-progression `_AUDITED` successor to A-66 `ELNOR_SUBAGENT_ARCHITECTURE_V5_1.md`** — +34,080 bytes / +55.7% growth over V5.1 (61,138 → 95,218). FIRST OBSERVED `_AUDITED` FILENAME SUFFIX in any subagent chain — likely Will-side workflow signal that V5.1 → V5.2 incorporates red-team audit findings (analogous to DOC10 R10 → R11 Consolidated expansion via R10/R8 red-team incorporation matrix; or DOC72 R5.72 → R5.73 GIE V2.2 absorption via 29 NP patches from 5-reviewer red-team). +55.7% growth pattern consistent with audit-driven expansion. Full file-header inspection deferred to next manual review pass. A-66 V5.1 row above gets natural-progression-supersession annotation pending Will-side archival decision. Filename canonicalization continues to evolve — V4 PRECOMPUTE_TOOL_OPTIMIZATION_NOTES → V5.1 ARCHITECTURE (R3.53) → V5.2 ARCHITECTURE_AUDITED (today), reflecting subsystem maturation from notes → spec → audited spec. |
### A.2 DOC20 Addenda subfolder
| ID | Filename | Date | Parent Spec | Reviewed | Disposition | Disp. Target | Integration Status | Int. Date | Notes |
|---|---|---|---|---|---|---|---|---|---|
| A-15 | `DOC20 Addenda/DOC20_ADDENDUM_B_MS_WORD_VIEWER_CAPABILITIES_R3.md` | 2026-04-10 | DOC20 R4.3 | not_yet | absorb | DOC20 | pending | — | Document viewer/editor: copy-on-write, tracked changes, OnlyOffice + MS Graph wiring. |
| A-16 | `DOC20 Addenda/DOC20_BUILD_DELTA.md` | 2026-04-15 | DOC20 R4.3 + Q_UNIFIED_WORKSPACE_V8_0_1 mockup | not_yet | absorb | DOC20 | pending | — | Living changelog. Future sessions reconcile against this first. |
| A-17 | `DOC20 Addenda/DOC20_Q_BROWSER_INTAKE_ARCHITECTURE.md` | 2026-04-03 | DOC20 §6.19; DOC72 §20A, DOC16 16.7, DOC3 R11.3, DOC8 | not_yet | split | DOC20 §6.19 + DOC72 §20A | pending | — | Two-tier intake: passive metadata + idle entity extraction. |
| A-18 | `DOC20 Addenda/DOC20_R4_3_DELTA_V7_11_6_ALT.md` | 2026-04-08 | DOC20 R4.3 | not_yet | absorb | DOC20 | pending | — | Vertical Tabs, Workspaces, Nav Restructure. |
### A.3 DOC24 Addenda subfolder
| ID | Filename | Date | Parent Spec | Reviewed | Disposition | Disp. Target | Integration Status | Int. Date | Notes |
|---|---|---|---|---|---|---|---|---|---|
| A-19 | `DOC24 Addenda/DOC24_ADDENDUM-B [KDA] KNOWLEDGE_DELIVERY_SHARED_CONTRACTS_R2.md` | 2026-04-02 | DOC24; DOC72, DOC3, DOC8, DOC15, DOC11 | done (multi-round) | absorb | DOC24 §§26-37 | pending | — | KDA R2 — ~1,577 lines. DOC24 R2.5 forward-references this. **Major absorption candidate.** |
| A-20 | `DOC24 Addenda/DOC24_ADDENDUM_Q_DASHBOARD_TOOL_REGISTRY.md` | 2026-04-11 | DOC24 R2.5 §14.5, §16.4, Appendix B | not_yet | absorb | DOC24 (re-derived from Q dashboard build periodically) | pending | — | Living document. ~100 tools across 13 categories. |
| A-21 | `DOC24 Addenda/DOC24_AMENDMENT_PERSISTENT_ONBOARDING_CURIOSITY.md` | 2026-04-13 | DOC24 R2.5 §§11.5, 12.4D, 12.4E; DOC72 §27.7 | not_yet | absorb | DOC24 | pending | — | Probe budget, contextual question cost tier, PauseOnboardingRequest guardrails. |
| A-22 | `DOC24 Addenda/DOC24_Addendum_A_BDSM Operative_Spec_V6_4.md` | undated (V6.4 over V6.3 audit-against-adjudication delta) | DOC24; DOC72, DOC8, DOC1, EC Core, DOC10/DOC11, DOC15, DOC21/22, DOC3, DOC17 | done (6+ rounds, 4+ reviewers) | absorb | DOC24 (Addendum A live integration) | pending | — | BDSM V6.4 — ~3,128 lines. Operative spec status. **Major absorption candidate.** |
| A-23 | `DOC24 Addenda/DOC24_UNIFIED_CONTEXT_BUDGET_GOVERNANCE.md` | 2026-04-04 | DOC24; DOC7 §4.4 | not_yet | absorb | DOC24 + DOC7 update | pending | — | ~284 lines. Replaces independent KDA §3.6 + DOC7 §4.4 budgets. |
| A-71 | `DOC24 Addenda/DOC24_Addendum_A_BDSM_V6_5_DRAFT_v0_2.md` | 2026-05-19 (mtime 2026-05-19 20:50 local, size 151,668 bytes) | DOC24; DOC72, DOC8, DOC1, EC Core, DOC10/DOC11, DOC15, DOC21/22, DOC3, DOC17 (broad cross-doc per V6.4 lineage) | not_yet | tbd | DOC24 (Addendum A live integration; eventual supersession of A-22 V6.4) | pending | — | **NEW (auto-detected 2026-05-19 by master spec list R3.55 nightly sync auto-bump 2026-05-19 ~23:17 UTC; backfilled to ADDENDA_STATE in R3.56 on 2026-05-20 since R3.55 did not update ADDENDA_STATE.md); needs human classification.** **Natural-progression DRAFT successor to A-22 V6.4 operative** — +7.5% size growth over V6.4 (141,102 → 151,668 bytes). `_DRAFT_v0_2` filename suffix indicates working-draft variant; FIRST OBSERVATION of `v0.1/v0.2/.../FINAL` working-draft-series pattern in BDSM chain — implies likely series of v0.1/v0.2/v0.3/.../v1.0 FINAL revisions before A-22 supersession (analogous to DOC25 V1.0 Draft → V2.0 FINAL pattern, or DOC23 Addenda B Outcome Evaluator V2 → V3 → V3.1 → V3.2 → V3.3 incremental pattern). Co-detected within ~2h window with A-72 KDA R3 DRAFT v0.2 — first multi-DOC24-draft drift in single MSL bump (R3.55); suggests coordinated DOC24 family redrafting pass possibly triggered by A-74 DOC23 FAMILY_SELF_LEARNING_COHERENCE_MAP_V1 introduction earlier same day. Full file-header inspection deferred to next manual review pass. A-22 V6.4 row above gets natural-progression-DRAFT-successor-pending annotation. |
| A-72 | `DOC24 Addenda/DOC24_KDA_R3_DRAFT_v0_2.md` | 2026-05-19 (mtime 2026-05-19 18:54 local, size 93,832 bytes) | DOC24; DOC72, DOC3, DOC8, DOC15, DOC11 (broad cross-doc per R2 lineage) | not_yet | tbd | DOC24 §§26-37 (eventual supersession of A-19 R2) | pending | — | **NEW (auto-detected 2026-05-19 by master spec list R3.55 nightly sync auto-bump 2026-05-19 ~23:17 UTC; backfilled to ADDENDA_STATE in R3.56 on 2026-05-20 since R3.55 did not update ADDENDA_STATE.md); needs human classification.** **Natural-progression DRAFT successor to A-19 KDA R2** with FILENAME CANONICALIZATION long-form `DOC24_ADDENDUM-B [KDA] KNOWLEDGE_DELIVERY_SHARED_CONTRACTS_R2` → short-form `DOC24_KDA_R3_DRAFT_v0_2` (THIRD instance of canonicalization pattern after ELNOR_SUBAGENT V4 → V5.1 in R3.53 and DOC23 ADDB V2 → V3 in R3.44). +28% size growth over R2 (73,171 → 93,832 bytes) suggests substantive R3 expansion likely incorporating cross-references with A-74 DOC23 FAMILY_SELF_LEARNING_COHERENCE_MAP_V1 (NEW cross-cutting reference map created same day). `_DRAFT_v0_2` filename suffix indicates working-draft variant; FIRST OBSERVATION in KDA chain — implies likely v0.1/v0.2/.../FINAL series before A-19 supersession. Co-detected within ~2h window with A-71 BDSM V6.5 DRAFT — first multi-DOC24-draft drift in single MSL bump (R3.55). Full file-header inspection deferred to next manual review pass. A-19 KDA R2 row above gets natural-progression-DRAFT-successor-pending annotation. Superseded by A-75 v0.3 row below (R3.58 backfill in R3.59) and A-79 v0.3.1 patch row (R3.59); all retained ACTIVE per auto pass no-relocation policy. |
| A-75 | `DOC24 Addenda/DOC24_Addendum_A_BDSM_V6_5_DRAFT_v0_3.md` | 2026-05-20 (mtime 2026-05-20 11:27:03 local, size 170,708 bytes) | DOC24; DOC72, DOC8, DOC1, EC Core, DOC10/DOC11, DOC15, DOC21/22, DOC3, DOC17 (broad cross-doc per V6.4 lineage) | not_yet | tbd | DOC24 (Addendum A live integration; eventual supersession of A-22 V6.4) | pending | — | **NEW (auto-detected 2026-05-20 by master spec list R3.58 nightly sync auto-bump; backfilled to ADDENDA_STATE in R3.59 on 2026-05-21 since R3.58 did not update ADDENDA_STATE.md); needs human classification.** **Natural-progression DRAFT successor to A-71 BDSM V6.5 DRAFT v0.2** — +19,040 bytes / +12.6% over v0.2 (151,668 → 170,708 bytes). Per file header: "applies the v0.3 corrective patch plan over the v0.2 BDSM V6.5 draft and replaces BDSM v6.4 for the V6.5+ revision lane." Second instance of v0.x draft pattern within BDSM chain (after v0.2); confirms v0.1/v0.2/.../FINAL working-draft-series pattern. Co-detected within ~1h window with A-76 KDA R3 DRAFT v0.3 — second consecutive multi-DOC24-draft sync window (R3.55 captured v0.2 pair; R3.58 captures v0.3 pair); confirms coordinated DOC24 family redrafting cadence. Superseded by A-79 v0.3.1 patch row below (R3.59 same-day intra-version patch); A-71 v0.2 row above gets natural-progression-DRAFT-successor-pending annotation. Full file-header inspection deferred to next manual review pass. |
| A-76 | `DOC24 Addenda/DOC24_KDA_R3_DRAFT_v0_3.md` | 2026-05-20 (mtime 2026-05-20 12:23:19 local, size 128,723 bytes) | DOC24; DOC72, DOC3, DOC8, DOC15, DOC11 (broad cross-doc per R2 lineage) | not_yet | tbd | DOC24 §§26-37 (eventual supersession of A-19 R2) | pending | — | **NEW (auto-detected 2026-05-20 by master spec list R3.58 nightly sync auto-bump; backfilled to ADDENDA_STATE in R3.59 on 2026-05-21 since R3.58 did not update ADDENDA_STATE.md); needs human classification.** **Natural-progression DRAFT successor to A-72 KDA R3 DRAFT v0.2** — +34,891 bytes / +37.2% over v0.2 (93,832 → 128,723 bytes). Per file header: "v0.3 is a mechanical preservation patch over v0.2, closing the ten KDA R2 preservation gaps enumerated in the v0.3 patch plan." Second instance of v0.x draft pattern within KDA chain (after v0.2); confirms v0.1/v0.2/.../FINAL working-draft-series pattern. Co-detected within ~1h window with A-75 BDSM V6.5 DRAFT v0.3 — second consecutive multi-DOC24-draft sync window confirming coordinated DOC24 family redrafting cadence. A-72 v0.2 row above gets natural-progression-DRAFT-successor-pending annotation. Full file-header inspection deferred to next manual review pass. |
| A-79 | `DOC24 Addenda/DOC24_Addendum_A_BDSM_V6_5_DRAFT_v0_3_1.md` | 2026-05-20 (mtime 2026-05-20 23:15 local) | DOC24; DOC72, DOC8, DOC1, EC Core, DOC10/DOC11, DOC15, DOC21/22, DOC3, DOC17 (broad cross-doc per V6.4 lineage) | not_yet | tbd | DOC24 (Addendum A live integration; eventual supersession of A-22 V6.4) | pending | — | **NEW (auto-detected 2026-05-21 by nightly sync R3.59); needs human classification.** **Natural-progression intra-version patch successor to A-75 BDSM V6.5 DRAFT v0.3** — `_DRAFT_v0_3_1` filename suffix indicates iterative patch over v0.3 with fourth-decimal-place granularity. **FIRST EVER FOURTH-DECIMAL-PLACE PATCH SUFFIX** in BDSM chain — extends v0.1/v0.2/v0.3/.../FINAL working-draft series with intra-version patch granularity (analogous to DOC23 Addenda B Addendum V3 → V3.1 → V3.2 minor-revision pattern from R3.47/R3.49). Created same-day evening as v0.3 (v0.3 = 11:27 local; v0.3.1 = 23:15 local; ~12h apart). Likely small corrective fixup over v0.3 (file size measurement and full file-header inspection deferred to next manual review pass). A-75 v0.3 row above gets natural-progression-intra-version-patch-successor annotation pending finalization. |
| A-80 | `DOC24 Addenda/DOC24_KDA_R3_DRAFT_v0_3_1.md` | 2026-05-20 (mtime 2026-05-20 23:14 local, size 129,645 bytes) | DOC24; DOC72, DOC3, DOC8, DOC15, DOC11 (broad cross-doc per R2 lineage) | not_yet | tbd | DOC24 §§26-37 (eventual supersession of A-19 R2) | pending | — | **NEW (auto-detected 2026-05-24 by R3.62 TWO-DAY-GAP-CATCHUP sync; per R3.61 reconciliation finding (b), this file existed on disk since R3.58 era 2026-05-20 but was never counted or rowed by any prior revision — R3.60 §A3 count of 10 undercounted the 11 actual DOC24 Addenda files by exactly this file; R3.61 tracks as A-81 in MSL §4 numbering; R3.62 tracks as A-80 in ADDENDA_STATE divergent numbering); needs human classification.** **Natural-progression intra-version patch successor to A-76 KDA R3 DRAFT v0.3** — `_DRAFT_v0_3_1` filename suffix indicates iterative patch over v0.3 with fourth-decimal-place granularity, mirroring BDSM v0.3 → v0.3.1 same-day-pair pattern (A-79 above). **SECOND INSTANCE of fourth-decimal-place patch suffix in DOC24 family** after BDSM v0.3.1 (R3.59); confirms emerging Will-side workflow pattern of intra-version v0.x.y patch granularity in DOC24 draft series. Created same-day as v0.3 KDA (v0.3 = 2026-05-20 12:23 local; v0.3.1 = 2026-05-20 23:14 local; ~11h apart — tighter than BDSM v0.3 → v0.3.1 ~12h pair). **Filename-vs-internal-version discrepancy flagged in R3.61 §12:** filename `_v0_3_1` but internal H1 still "v0.3" — pattern-match with BDSM v0.3.1 (same discrepancy noted in R3.61). A-76 v0.3 row above gets natural-progression-intra-version-patch-successor annotation pending finalization. |
### A.4 DOC72 Addenda and Proposals subfolder
| ID | Filename | Date | Parent Spec | Reviewed | Disposition | Disp. Target | Integration Status | Int. Date | Notes |
|---|---|---|---|---|---|---|---|---|---|
| A-24 | `DOC72 Addenda and Proposals/DOC72_DOC7_BUCKET_INTAKE_INSERTION_TEXT.md` | undated | DOC72 R5.5 §20A.2/§20B.14; DOC7 R6 | not_yet | absorb | DOC72 §20A.2/§20B.14 + DOC7 | pending | — | Exact insertion text for `bucket` IntakeSurface and §20B.14 Bucket Files contract. |
| A-25 | `DOC72 Addenda and Proposals/DOC72_PROPOSAL_CONTINUITY_SYNTHESIS_ARCHITECTURE_R1.md` | 2026-04-14 | DOC72; DOC24, DOC11, DOC15, DOC8, DOC2 (retirement), EC Core | not_yet | absorb | DOC72 + DOC2 retirement | pending | — | **FILE MOVED OUT OF ACTIVE FOLDER (auto-detected 2026-04-30 by nightly sync):** archived to `Archived Addenda Proposals and In Progress/DOC72_PROPOSAL_CONTINUITY_SYNTHESIS_ARCHITECTURE_R1.md`; superseded by R2 (new row A-35 below). Row preserved for traceability. Cross-conversation continuity, activity-type-aware significance gating, temporal awareness with DOC2 retirement. |
| A-35 | `DOC72 Addenda and Proposals/DOC72_PROPOSAL_CONTINUITY_SYNTHESIS_ARCHITECTURE_R2.md` | 2026-04-29 | DOC72; DOC24, DOC11, DOC15, DOC8, DOC2 (retirement), EC Core, DOC73 | not_yet | tbd | DOC72 (likely absorb) | pending | — | Auto-detected 2026-04-30 by nightly sync; needs human classification. R2 supersedes R1 (A-25). Per DOC73 §6.4 Mechanism 4 Rollup V1 proposal (A-36 below): "CSA R2 three-tier fresh-surface injection model has a Tier 2 (recent activity narrative) that depends on DOC73 §6.4 Mechanism 4 producing a cross-context rollup file" — A-35 and A-36 are companion proposals. Size 83,554 bytes (R1 was 48,797 bytes — ~71% larger). |
| A-26 | `DOC72 Addenda and Proposals/DOC72_PROPOSAL_SURFACE_INTAKE_CONTRACTS_V2.md` | 2026-04-08 | DOC72 §20A | not_yet | absorb | DOC72 §20A | pending | — | Per-surface intake contracts for To-Do, Calendar, Notes, Browser. |
### A.5 DOC73 Addenda and Proposals subfolder
**Auto-detected 2026-04-28 by nightly sync:** new subfolder `DOC73 Addenda and Proposals/` appeared in `Addenda Proposals & In Progress/` (created 2026-04-27 22:50). Subfolder structurally analogous to existing `DOC72 Addenda and Proposals/`. Tracked here for visibility; in-scope folder list in nightly sync task SKILL.md needs human update to formally include this path.
| ID | Filename | Date | Parent Spec | Reviewed | Disposition | Disp. Target | Integration Status | Int. Date | Notes |
|---|---|---|---|---|---|---|---|---|---|
| A-30 | `DOC73 Addenda and Proposals/DOC73_CORPUS_SOURCE_BINDINGS_PROPOSAL_V1.md` | 2026-04-27 | DOC73 V1.4.1 (now V1.5.1); DOC25, DOC72, EC Core Addendum A | not_yet | tbd | TBD | pending | — | Auto-detected 2026-04-28 by nightly sync; needs human classification and disposition. Companion proposal to A-27 (EC Core Addendum A Intake Routing for Corpus Bindings). Pre-dates DOC73 V1.5.1; may need re-targeting. |
| A-36 | `DOC73 Addenda and Proposals/DOC73_PROPOSAL_SECTION_6_4_MECHANISM_4_ROLLUP_V1.md` | 2026-04-29 | DOC73 V1.5.1 §6.4 Mechanism 4; DOC24 R3 packet assembly, DOC72 CSA R2 (A-35) | not_yet | tbd | DOC73 (likely absorb into R-next) | pending | — | Auto-detected 2026-04-30 by nightly sync; needs human classification. Per file header: "Standalone handoff document. Target: DOC73 V1.5.1 §6.4 Mechanism 4 (currently named but undefined). Origin: Identified as a gap during CSA R2 (DOC72 Continuity Synthesis Architecture R2) drafting." Specifies output file `ELNOR_MEMORY/rollup/recent_activity.md` refreshed nightly via single LLM call (Kimi or local Ollama, <$0.01/day). Companion to A-35 (DOC72 CSA R2). |
| A-37 | `DOC73 Addenda and Proposals/DOC73_V1_6_ADJUDICATION_CARD_ARCHITECT_NOTES_V1 (1).md` | 2026-04-30 | DOC73 V1.5.1 (forthcoming V1.6) | not_yet | tbd | DOC73 (architect notes for V1.6 adjudication) | pending | — | Auto-detected 2026-04-30 by nightly sync; needs human classification. Small file (73 lines, 6,441 bytes). Likely architect notes / adjudication card for the upcoming DOC73 V1.5.1 → V1.6 red-team round. Filename includes "(1)" suffix suggesting Will may have copied this from somewhere (Downloads?). |
### A.6 DOC23 Addenda subfolder (NEW — folder created 2026-05-01 ~10:27, formally tracked here from R3.9 onward)
**Auto-detected 2026-05-02 by nightly sync (creation performed in R3.9 alias bump 2026-05-01 ~23:14):** new subfolder `DOC23 Addenda/` appeared in `Addenda Proposals & In Progress/` (folder mtime 2026-05-01 10:27, child mtime now 2026-05-02 00:31). Subfolder is structurally analogous to existing `DOC20 Addenda/`, `DOC24 Addenda/`, `DOC72 Addenda and Proposals/`, `DOC73 Addenda and Proposals/`. As with the DOC73 Addenda subfolder addition in R2.9, the in-scope folder list in the nightly sync task SKILL.md needs human update to formally include the new `DOC23 Addenda/` path (auto pass scans it as in-scope by precedent).
| ID | Filename | Date | Parent Spec | Reviewed | Disposition | Disp. Target | Integration Status | Int. Date | Notes |
|---|---|---|---|---|---|---|---|---|---|
| A-42 (alias) | `DOC23 Addenda/DOC23_ADDENDA_A_TASK_OPTIMIZATION_R4_0 (1).md` | 2026-05-01 | DOC23 R3.1; Prop-A R6.3 (companion); A-43 (targets R4.1 compilation against this file) | not_yet | tbd | DOC23 R3.1 (likely absorb) | pending | — | **Relocated to this subfolder in R3.9 (auto-detected 2026-05-02).** See §A.1 row A-42 for full detection history (R3.7 first-detected at active root as the (1)-suffix duplicate of R4.0). Per R3.9 disposition: Will archived the no-suffix R4.0 (A-41) and kept this file active in the new subfolder, treating it as canonical R4.0 going forward. Auto-detected; needs human classification. |
| A-43 | `DOC23 Addenda/DOC23_ADDENDA_A_R4_0_CONTEXT_MANAGEMENT_PROPOSAL_V1.md` | 2026-05-01 | DOC23 Addenda A R4.0 (the operative draft = A-42, this proposal targets R4.1 compilation against it); cross-references DOC25 V1.0/V2.0, DOC23 R3.1, DOC24 R3, DOC15 CIL R7.1, DOC72 R5.73, MultiDoc PropA R6.3, ELNOR Subagent V4 | not_yet | tbd | DOC23 Addenda A R4.1 (likely absorb) | pending | — | **NEW (auto-detected 2026-05-02 by nightly sync; first-tracked in R3.9 alias bump 2026-05-01 ~23:14, mtime 2026-05-01 17:26, size 53,884 bytes); needs human classification.** Per file header: proposal addendum V1 (Draft) authored by Claude Opus 4.7 in dialogue with Will, target compilation revision DOC23 Addenda A R4.1, supersedes nothing (new proposal), no outstanding companion proposals, status "Draft proposal — pending review, calibration, red team, and compilation into R4.1." Origin per §0: closes a CRITICAL gap in A-42 (R4.0)'s Judge module §A3, flagged by two same-day red team reviews (Claude V1 with 40 findings; Claude V2 deeper-dive with 34 additional findings). Cited gap: per-dimension context duplication multiplies token cost — worst-case Pattern 7 run = 5 dims × 3 judges × 4 variants × 12 pairwise calls = 720 calls × 250K tokens each = 180M tokens, with single calls exceeding Claude's 200K context window (Pattern 7 unrunnable on real legal inputs as currently specified). Proposal scope: regime-classification preparation pipeline; three new variant-bundle schemas; sub-agent fan-out dispatch modes; per-dimension context-requirement flags; DOC25 ingestion contract; supporting validation/SSE/UI surfaces. Concrete ambition: enable a 4-variant × 5-dimension × 3-judge ensemble pairwise scoring of a 60-page complaint draft to run within model context windows AND under $25 per run AND in under 90 seconds wall-clock — at quality equal-or-better than the naive whole-document approach. |
| A-44 | `DOC23 Addenda/DOC23_REPROMPT_SYSTEM_ADDENDUM.md` | 2026-05-02 | DOC23 R3.1 §3.2.1, §3.2.8, §6.5.2, §6.5.8, §4.5, §4.8 | not_yet | tbd | DOC23 R3.2 (per file header: target compilation revision is DOC23 R3.2) | pending | — | **NEW (auto-detected 2026-05-02 by nightly sync; mtime 2026-05-02 00:31, size 22,818 bytes); needs human classification.** Per file header: "DOC23 Red Line — Sequential Re-Prompt System", date 2026-05-01, status "Draft addendum for compilation into DOC23 R3.2." Affects: §3.2.1 (step.agent_task), §3.2.8 (step.coding), §6.5.2 (agent task execution), §6.5.8 (coding execution), §4.5 (output popups), §4.8 (validation). Latest entry in DOC23 addendum cluster (which already includes A-42 R4.0 canonical and A-43 Judge Context Management Proposal V1). |
| A-42 (alias) — R3.13 update | `Archived Addenda Proposals and In Progress/DOC23_ADDENDA_A_TASK_OPTIMIZATION_R4_0 (1).md` | 2026-04-30 (mtime preserved 2026-04-30 23:44) | DOC23 R3.1 (primary); Prop-A R6.3 (companion) | not_yet | tbd | DOC23 R3.1 (likely absorb) | archived | 2026-05-02 | **FILE MOVED FROM DOC23 Addenda subfolder TO ARCHIVE (auto-detected 2026-05-02 by R3.12 master spec list bump; backfilled here in R3.13 sync 2026-05-03):** A-42 (master spec list A-44) was the canonical R4.0 (1) per R3.9 disposition; superseded by A-45 R4.1 V2 (master spec list A-47) and archived in R3.12 sync. Mirrors A-43 R3.9 archival pattern. |
| A-45 | `DOC23 Addenda/DOC23_ADDENDA_A_TASK_OPTIMIZATION_R4_1_V2.md` | 2026-05-02 (mtime 2026-05-02 19:34) | DOC23 R3.1 (primary); Prop-A R6.3 (DSPy self-improvement engine — independent pathway, companion); DOC24 R3 (capability/context architecture); DOC25 V1.0 (Document Intelligence) | not_yet | tbd | DOC23 R3.2 (per file header: compiles into DOC23 R3.2) | pending | — | **NEW (backfilled R3.13 sync 2026-05-03; first detected by master spec list R3.12 sync 2026-05-02 ~16:00 as master spec list row A-47); needs human classification.** Large file (size 154,930 bytes). Per file header: R4.1 V2 (Draft), 2026-05-02, status "Draft — V2 closes 25 row gaps + 2 deviations from V1 audit. Pending Will's review against V5 adjudication card. Compiles into DOC23 R3.2." Closes contract for five capabilities (Experiments / Claim Extraction / Judges / Sub-Agent Awareness / Prompt Optimization — last RESERVED FOR R5) plus two cross-cutting capabilities (DOC24 Context Injection §A8 / Session Continuity §A9). R4.1 = contract closure + schema cleanup + safety items + minimum context-management subset; reserves DSPy + Optimization Platform + Human Eval + Code-Based Scorers + full Context Management Proposal V1 substrate + Campaigns/Dataset Library for R5+. **Supersedes A-42 (master spec list A-44 R4.0 (1), now archived) and a briefly-extant R4.1 V1** (V1 file mtime 2026-05-02 10:58, size 103,002 bytes — created and archived in same window per R3.12 narrative). R3.13 mtime tick: 12:34 → 19:34 (size unchanged — likely touch operation). |
| A-46 | `DOC23 Addenda/DOC23_ADDENDA_A_R5_R6_DEFERRAL_LIST_V2.md` | 2026-05-02 (mtime 2026-05-02 17:58) | DOC23 Addenda A R5 / R6 (work plan organized by functional spec area for R5/R6 drafting); companion to V5 adjudication card (238 rows, not registered in master spec list); cross-references A-43 Judge Context Management Proposal V1 + the two §8 Notes substrate proposals | not_yet | tbd | DOC23 Addenda A R5 / R6 (work plan staging) | pending | — | **NEW (backfilled R3.13 sync 2026-05-03; first detected by master spec list R3.12 sync 2026-05-02 ~16:00 as master spec list row A-48); needs human classification.** File size 30,631 bytes. Per file header: V2 status "Pre-adjudication — will be revised after Will fills the V5 Decision column to V3 (post-adjudication)." Three top-level sections: §1 R5 work plan grouped by functional area A–N (DSPy + Optimization Platform §1.A is the single biggest R5 work package); §2 R6 work plan (4 items); §3 external documents that compile into R5/R6. Cross-doc obligations OB-A14 through OB-A18 flagged. **Supersedes a briefly-extant V1** (V1 file mtime 2026-05-02 09:58, size 24,682 bytes — created and archived in same window per R3.12 narrative). R3.13 mtime tick: 10:58 → 17:58 (size unchanged — likely touch operation). May warrant `STAGING / SUPPORT` classification rather than `PROPOSED ADDENDUM` since file is explicitly a work-plan staging buffer rather than an amendment. |
| A-47 | `DOC23 Addenda/DOC23_ADDENDA_A_CONTEXT_MGMT_PROPOSAL_V1_TO_CARD_INTEGRATION_MAP_V2.md` | 2026-05-02 (mtime 2026-05-02 17:58) | A-43 Judge Context Management Proposal V1 (the proposal); the V5 adjudication card (238 rows, 14 sections, dated 2026-05-02 — not registered in master spec list); A-46 R5/R6 Deferral List V2 (companion) | not_yet | tbd | TBD (likely SUPPORT/REFERENCE not addendum) | pending | — | **NEW (backfilled R3.13 sync 2026-05-03; first detected by master spec list R3.12 sync 2026-05-02 ~16:00 as master spec list row A-49); needs human classification.** File size 23,341 bytes. **Per file header: meta/navigation document** — non-normative, modifies nothing, explicitly disclaims operative status. Closed-loop integration map between A-43 (the proposal) and the V5 card. Like A-32 ELNOR Search Architecture Reference R1, file is non-normative by purpose. **Likely needs reclassification to `SUPPORT / NON-OWNER DRAFT / NAVIGATION / REFERENCE` rather than `PROPOSED ADDENDUM`.** R3.13 mtime tick: 10:58 → 17:58 (size unchanged — likely touch operation). |
| A-48 | `DOC23 Addenda/Archived DOC23 addenda/DOC23_ADDENDA_B_TASK_INTELLIGENCE_MEMORY_OBSERVABILITY_R0_3_AUDIT_COMPLETE.md` | 2026-05-03 (mtime 2026-05-02 19:36 preserved across move) | DOC23 R3.1 (primary parent); companions DOC23 Addenda A R4.1 V2 (= A-45 above), DOC24 R3, DOC72 R5.73, DOC25 V2.0, DOC73 V1.5.1, DOC8 v1.11.4, DOC24 Addendum A BDSM v6.4, DOC3 R11.3 Addenda A R2.2 (= A-33), EC Core Addendum A V3.3, OP-A V3.7 | not_yet | tbd | DOC23 R3.1 (likely absorb as a major addendum bundle) | archived (intra-subfolder) | 2026-05-03 | **FILE MOVED TO INTRA-SUBFOLDER ARCHIVE (auto-detected 2026-05-04 by nightly sync; backfilled from R3.15 narrative):** moved from `DOC23 Addenda/` → new `DOC23 Addenda/Archived DOC23 addenda/` subfolder (subfolder mtime 2026-05-03 15:52 — **first time any top-level Addenda subfolder has its own dedicated archive subfolder**, different from the global `Archived Addenda Proposals and In Progress/` archival convention). Master spec list row A-50. Per file header: "DOC23 Addenda B — Task Intelligence, Memory, Observability, and Self-Improving Task Design", **R0.3 Audit-Complete Draft**, dated 2026-05-03, status "Draft for architect review", per §0.1 "end-state architectural draft. It is not an implementation phase plan." **First DOC23 Addenda B entry** — opens a brand-new track parallel to DOC23 Addenda A — Task Optimization (A-38 through A-45 chain). Naming convention: "DOC23 Addenda A" = Task Optimization (Experiments / Judges / Prompt Optimization); "DOC23 Addenda B" = Task Intelligence / Memory / Observability / Self-Improving Task Design. Superseded first by R0.5 (briefly-extant, in intra-archive — never had its own row), then by A-49 R0.6.1 (also now in intra-archive), then by tonight's A-50 R0.6.3. Row preserved for traceability. |
| A-49 | `DOC23 Addenda/Archived DOC23 addenda/DOC23_ADDENDA_B_TASK_INTELLIGENCE_MEMORY_OBSERVABILITY_R0_6_1_MERGE_AUDIT_CLEANED.md` | 2026-05-03 (mtime 2026-05-03 22:51 preserved across move) | DOC23 R3.1 (primary); companions same as A-48 | not_yet | tbd | DOC23 R3.1 (likely absorb) | archived (intra-subfolder) | 2026-05-04 | **NEW (backfilled R3.16 sync 2026-05-04 from R3.15 narrative; first detected by master spec list R3.15 sync 2026-05-03 ~16:00 as master spec list row A-51); needs human classification.** R0.6.1 Merge-Audit Cleaned Unified Draft, source merge folds A-48 R0.3 base + briefly-extant R0.5 audit-complete merge pack into one unified draft adding natural saved-task invocation, prompt-evaluation tasks, OpenClaw/DOC11 runtime alignment, unified prompt improvement. Size 241,604 bytes (~168% of A-48 R0.3's 143,665 bytes). **MOVED TO INTRA-SUBFOLDER ARCHIVE between R3.15 (2026-05-03 23:13) and tonight's R3.16 sync** — superseded by A-50 R0.6.3 below; the intra-subfolder archival pattern established by R3.15 holds. Mtime preserved at 2026-05-03 22:51. Row preserved for traceability. |
| A-50 | `DOC23 Addenda/Archived DOC23 addenda/DOC23_ADDENDA_B_TASK_INTELLIGENCE_MEMORY_OBSERVABILITY_R0_6_3_SURFACE_CONTEXT_PATCHED.md` | 2026-05-04 (mtime preserved 2026-05-04 07:42 across move) | DOC23 R3.1 (primary); companions DOC23 Addenda A R4.1 V2 (= A-45), DOC23 Addenda A R5/R6 Deferral List V2 (= A-46), DOC24 R3, DOC72 R5.73, DOC25 V2.0, DOC73 V1.5.1, DOC8 v1.11.4, DOC24 Addendum A BDSM v6.4, DOC3 R11.3 Addenda A R2.2 (= A-33), DOC17 R4.2, DOC11 R15 Amendment Proposal R2, OpenClaw Release Alignment Running Spec Update List R2, EC Core Addendum A V3.3, OP-A V3.7 | not_yet | tbd | DOC23 R3.1 (likely absorb as major addendum bundle) | archived (intra-subfolder) | 2026-05-04 | **FILE MOVED TO INTRA-SUBFOLDER ARCHIVE (auto-detected 2026-05-05 by nightly sync R3.19 backfill; movement performed during R3.18 alias bump 2026-05-04 ~16:14):** moved from `DOC23 Addenda/` → `DOC23 Addenda/Archived DOC23 addenda/`. Mirrors A-48 R0.3 (R3.15) and A-49 R0.6.1 (R3.16) archival patterns. Superseded by A-51 R0.6.4 (new row below) per R3.18 detection. **DOC23 Addenda B-track intra-subfolder archive at R3.19: 4 files** (R0.3 + briefly-extant R0.5 + R0.6.1 + R0.6.3) — collapse opportunity grows from 3 rows (R3.16) to 4 rows (R3.18+R3.19). Original detection notes preserved: "R0.6.3 Surface/Trigger Context Patched Unified Draft", removes singular-current-work-context assumption + adds task-run scope envelopes for concurrent chats / scheduled runs / email / webhook / file triggers. Defines Task Agent, natural saved-task invocation, DOC72 task-memory integration, telemetry spine, artifact/output intake, Task Blueprint, template/preset intelligence, Task Agent education/TKP, task-design self-learning, DOC24 capability/runtime routing, OpenClaw/DOC11 runtime alignment, unified prompt improvement, prompt-evaluation tasks. Predecessor A-49 R0.6.1 (and earlier R0.5 + R0.3) also in same intra-archive. Row preserved for traceability. |
| A-51 | `DOC23 Addenda/DOC23_ADDENDA_B_TASK_INTELLIGENCE_MEMORY_OBSERVABILITY_R0_6_4_UI_CONTINUATION_SHARING_PATCHED.md` | 2026-05-04 (mtime 2026-05-04 22:17 UTC = 15:17 local) | DOC23 R3.1 (primary); companions DOC23 Addenda A R4.1 V2 (= A-45), DOC23 Addenda A R5/R6 Deferral List V2 (= A-46), DOC24 R3, DOC72 R5.73, DOC25 V2.0, DOC73 V1.5.1, DOC8 v1.11.4, DOC24 Addendum A BDSM v6.4, DOC3 R11.3 Addenda A R2.2 (= A-33), DOC17 R4.2, DOC11 R15 Amendment Proposal R2, OpenClaw Release Alignment Running Spec Update List R2, EC Core Addendum A V3.3, OP-A V3.7, **DOC20 (NEW R0.6.4 task-surface integration)** | not_yet | tbd | DOC23 R3.1 (likely absorb as major addendum bundle) | pending | — | **NEW (auto-detected 2026-05-05 by nightly sync R3.19 backfill; first detected by master spec list R3.18 sync 2026-05-04 ~16:14 as MSL row A-53; mtime 2026-05-04 22:17 UTC = 15:17 local, size 327,340 bytes — large file at ~119% of A-50 R0.6.3); needs human classification.** Per file header: "R0.6.4 UI, Run Inspector, Module Continuation, Sharing-Forward-Compatible Unified Draft", date 2026-05-04, status "Unified integration draft for architect review; R0.6.4 carries forward R0.6.3 and adds DOC20 task-surface integration, graph/inspector navigation, artifact/delivery UI, context inspector feedback, Task Agent side-panel/session behavior, Task Segment reusable module groups, module continuation/follow-up, run forking/rerun-from-module, Judge/Experiment rerun affordances, audit export, task-page operational stats, and shared-task surface forward-compatibility for future DOC50+ sharing/networking specs." Source merge: builds on A-50 R0.6.3 + R0.6.1 + R0.5 merge pack + R0.3 base. Title further expanded from R0.6.1's "Natural Task Invocation" addition: R0.6.4 title adds "UI / Run Inspector / Module Continuation / Sharing-Forward-Compatible". **Supersedes A-50 R0.6.3.** Per §0.7: "R0.6.4 adds the UI and runtime refinements surfaced during the DOC20/mockup review pass. These additions are normative where they define schemas, owner splits, and UI contracts; visual layout examples remain illustrative." Notable B-track cadence: R0.3 (5/3) → R0.5 (5/3) → R0.6.1 (5/3) → R0.6.3 (5/4 morning) → R0.6.4 (5/4 afternoon) — five revisions in ~36h window. |
| A-53 | `DOC23 Addenda/DOC23_ADDENDA_B_PROPSAL ADDITION FOR R0_6_5_OUTCOME_EVALUATION_SOURCE_WORKSPACE_FORUM_FEEDBACK_PROPOSAL.md` | 2026-05-10 (mtime 2026-05-10 00:14 UTC) | DOC23 R3.1 (primary parent); DOC23 Addenda A R4.1 / R5-R6 deferral list (= A-45/A-46); DOC20 R4.3; DOC24 R3; DOC24 KDA R2 (= A-19); DOC25 V2.0; DOC72 R5.73; DOC73 V1.5; DOC17 R4.2; DOC8 v1.11.4; BDSM v6.4 (= A-22); DOC11/OpenClaw R15 amendment proposal (= A-1/A-34); DOC12 forum/panel architecture; EC Core Addendum A V3.3 (= A-4); PropA R6.3 (= A-7) | not_yet | tbd | DOC23 Addenda B (likely fold into next unified draft alongside A-51 R0.6.4 OR keep as parallel stacked proposal — disposition pending) | pending | — | **SUPERSEDED 2026-05-14 by V2 file `DOC23_ADDB_ADDENDUM_OUTCOME_EVAL_REVISION_V2.md` (= NEW A-54 below) per V2 header's explicit "Supersedes: [V1 filename]" declaration; V1 file remains in active folder pending human archival decision.** Original R3.33 detection notes preserved: **NEW (auto-detected 2026-05-10 by R3.33 nightly sync; mtime 2026-05-10 00:14 UTC, size 74,733 bytes); needs human classification.** Filename has typo "PROPSAL" (vs "PROPOSAL") preserved verbatim from filesystem. Per file header: "DOC23 Addenda B R0.6.5 — Outcome Evaluation, Source Workspace, Task Forum, and Evaluator Feedback Proposal", date 2026-05-10, status **"Initial merge proposal for review. Not yet folded into the R0.6.4 unified Addenda B draft."** Target: DOC23 Addenda B (same end-state architectural draft track as A-51 R0.6.4 / master spec list A-53 R0.6.4). Primary purpose per §0 Executive Summary: "Add a graph-native quality-improvement architecture for complex DOC23 tasks, without turning tasks into hidden agent rooms or making simple tasks heavy." Eight new architectural primitives: (1) Outcome Specs (define "good enough" for tasks/segments/modules/artifacts/source-workspaces/prompt-candidates/final-outputs); (2) Outcome Evaluators (apply specs and emit structured decisions, findings, repair instructions, research/source needs, audit evidence); (3) Outcome Gates (Outcome Evaluators configured to control graph flow); (4) Evaluator Feedback Bundles (make judge/review/evaluator outputs actionable); (5) Task Source Workspace (shared task-scoped source/research substrate that grows during run); (6) Task Run Board (chronological audit/feed surface); (7) Task Forum Module (optional graph-visible cross-module coordination forum); (8) Task Agent role retained as operational task-system expert (NOT default substantive evaluator). Per §1 Governing Principles: graph primacy preserved; forum non-necessity (Task Run Board/Forum never required for task to function); domain-agnostic in core primitives + legally powerful through saved configurations. **NEW pattern in R3.33 (stacked proposal, distinct from B-track supersession-and-archive pattern):** A-53 R0.6.5 is positioned as ADDITIONAL stacked proposal on top of A-51 R0.6.4 / master spec list A-53 R0.6.4 rather than a strict supersession — file header explicitly states "Not yet folded into the R0.6.4 unified Addenda B draft." Both files coexist as ACTIVE in `DOC23 Addenda/` subfolder pending human classification + folder disposition. **Disposition options for human review:** (a) fold R0.6.5 into R0.6.4 producing R0.6.5-merged unified draft following the prior supersession pattern; (b) keep them parallel as stacked proposals with R0.6.4 as base + R0.6.5 as additive layer; (c) some other disposition. Auto pass leaves both ACTIVE pending decision. NB: ADDENDA_STATE.md uses A-53 here for this NEW addendum (continuing the existing sequence from A-51 R0.6.4 → A-52 (1)-suffix informational → A-53 R0.6.5 NEW); master spec list §4 reserves A-53 for R0.6.4 (older numbering) and uses A-54 for this same file. The trackers' numbering diverges by one in §A6 going forward but is internally consistent within each. |
| A-54 | `DOC23 Addenda/DOC23_ADDB_ADDENDUM_OUTCOME_EVAL_REVISION_V2.md` | 2026-05-14 (mtime 2026-05-14 03:32 UTC) | DOC23 R3.1 (primary parent via Addenda B R0.6.4 root); supersedes A-53 R0.6.5 V1 per V2 header's explicit "Supersedes:" declaration; companions same as A-53 (DOC23 Addenda A R4.1, DOC20 R4.3, DOC24 R3, DOC24 KDA R2, DOC25 V2.0, DOC72 R5.73, DOC73 V1.5, DOC17 R4.2, DOC8 v1.11.4, BDSM v6.4, DOC11/OpenClaw R15, DOC12 forum/panel, EC Core Addendum A V3.3, PropA R6.3) | not_yet | tbd | DOC23 Addenda B (likely fold into next unified draft) | pending | — | **NEW (auto-detected 2026-05-14 by R3.39 nightly sync; mtime 2026-05-14 03:32 UTC, size 133,682 bytes, 2,740 lines); needs human classification.** Filename "ADDB" abbreviates "Addenda B" — first time this naming convention is used in the Addenda B chain. Per file header: "DOC23 Task System — Addenda B ADDENDUM: Outcome Evaluation and Revision Architecture, V2", document hierarchy "DOC23 (R3.1) → Addenda B (R0.6.4) → Addendum (this doc, V2)", status "Proposal — pending red-team review per §25. Not yet folded into Addenda B main." Author: "Will Brody (architecture) + Claude (drafting)." **Explicit supersession**: per V2 header "Supersedes: `DOC23_ADDENDA_B_PROPSAL_ADDITION_FOR_R0_6_5_OUTCOME_EVALUATION_SOURCE_WORKSPACE_FORUM_FEEDBACK_PROPOSAL.md` (V1)" (= existing A-53). NB: header references the V1 filename with underscores while filesystem filename has spaces; same file. Per §0.1 V2 change log: "V2 is a substantial architectural revision, not an incremental edit. The V1 proposal laid out the right primitives (OutcomeSpec, OutcomeEvaluatorConfig, OutcomeGate, EvaluationFeedbackBundle, defeasible findings lifecycle, Run Guidance Items, Repair Instructions, four feedback delivery channels, FeedbackConsumptionReceipts, TaskSourceWorkspace, TaskProcessGapSignal), but it did NOT specify [11 gaps]: (1) How a user creates an outcome without filling out a 15-field form; (2) A plan-and-execute layer; (3) Targeted evaluation mode; (4) Per-outcome progress signals beyond pass/fail; (5) Cascading revalidation via declared dependencies; (6) Two-budget iteration model; (7) A formal Revision Bus / dispatch runtime; (8) Per-module `revision_in` port contract; (9) Plan review forum semantics distinct from runtime orchestration; (10) Text-to-outcome inference pipeline; (11) Skill-graph integration for learned patterns. V2 adds all of the above." New V2 primitives table: `step.revisor` module (§6); `RevisionPlan` schema (§7); Revision Bus runtime (§8); `revision_in` port contract (§9); `target_outcomes` input port on Evaluator (§5.1); `iteration_history` input port on Evaluator (§5.1); `plan_step_context` input port on Evaluator (§5.1). **Pattern restoration:** V2 supersession-and-replace explicitly reverses the R3.33 stacked-proposal pattern (V1 was positioned as "stacked addition not folded into R0.6.4 unified Addenda B draft"; V2 returns to the supersession-and-replace convention familiar from R0.3 → R0.5 → R0.6.1 → R0.6.3 → R0.6.4 chain). **Disposition for V1 (A-53) pending human review:** (a) move V1 file to `Archived Addenda Proposals and In Progress/` following the supersession-and-archive pattern; (b) keep V1 file in active folder for traceability (atypical). Auto pass leaves both ACTIVE pending decision. NB: ADDENDA_STATE.md uses A-54 for this NEW row (continuing existing A-53 R0.6.5 V1 → A-54 V2 SUPERSESSION sequence); master spec list §4 likely uses A-55 (preserving the R3.33 numbering divergence-by-one). **FILE MOVED TO LOCAL ARCHIVE 2026-05-17 (auto-detected 2026-05-17 by R3.47 nightly sync):** moved from `DOC23 Addenda/` root to `DOC23 Addenda/Archived DOC23 addenda/` subfolder (folder mtime 2026-05-17 04:15). Local intra-subfolder archival. V2 was already superseded by V3 (= A-56) in R3.39 sync; with V3 in turn now superseded by V3.1 (= A-58), the V1→V2→V3→V3.1 chain head is V3.1. Row preserved per auto pass no-removal policy. |
| A-56 | `DOC23 Addenda/DOC23_ADDB_ADDENDUM_OUTCOME_EVALUATOR_REVISOR_V3.md` | 2026-05-15 (file-header date; mtime 2026-05-16 02:44 UTC) | DOC23 R3.1 (primary parent via Addenda B R0.6.4); natural-progression successor to A-54 V2 + A-53 V1 in DOC23 Addenda B Addendum chain; 13 explicit cross-doc dependencies enumerated in V3 header (DOC11 ACP/runtime, DOC12 plan review forum, DOC15 CIL authority + context packets, DOC20 UI surfaces for Evaluation/Revision Result Cards + Teach-from-feedback, DOC24 capability registry + runtime injection, DOC25 IngestionResult + source verification, DOC72 Pattern primitive + goal context, DOC73 receipt envelope + PBEOperationReceiptLite, EC Core sole durable writer + retention rows + PolicyDecision gate, BDSM/DOC8 utility learning signals, DOC23 Addenda A Judge module + Claim Extractor + prompt optimization) | not_yet | tbd | DOC23 Addenda B (likely fold into next unified draft as V3 specification block) | pending | — | **NEW (auto-detected 2026-05-16 by R3.44 nightly sync; mtime 2026-05-16 02:44 UTC, size 360,081 bytes, 8,555 lines — ~2.7× the V2 file's 133,682 bytes); needs human classification.** **Filename canonicalization vs V2**: V3 uses `OUTCOME_EVALUATOR_REVISOR` ("Evaluator and Revisor") instead of V2's `OUTCOME_EVAL_REVISION` ("Eval Revision") — more formal/canonical vocabulary. Per V3 file header: "# DOC23 Addenda B Addendum — Outcome Evaluator and Revisor V3"; **Status:** "V3 specification" (NOT "proposal" or "draft" as in V2 — V2 was "Proposal — pending red-team review per §25. Not yet folded into Addenda B main."); **Version:** "3.0"; **Prepared:** "2026-05-15". **Source documents per V3 header:** DOC23 Task System Modular Architecture R3.1; DOC23 Addenda A (Task Optimization) R4.1 V2; DOC23 Addenda B (Task Intelligence, Memory, Observability) R0.6.4; **DOC23 Addenda B Addendum V3 Adjudication Card V3.1**; **DOC23 Addenda B Addendum V3 Canonicalization Patch V2** — V3 is therefore the post-adjudication revision incorporating Card V3.1 decisions + Canonicalization Patch V2 normalizations. Per V3 header `## Conventions` section: normative rules use MUST/MUST NOT/SHOULD/MAY in the RFC 2119 sense; cross-references use `[X]` format for items in the Adjudication Card V3.1 and `[P-N]` format for patches in the Canonicalization Patch V2 — establishes V3 as a normative spec rather than V2's proposal/draft status. **NEW V3 architectural primitives beyond V2:** `Outcome Compiler` (compiles outcome specs from natural-language input + skill graph patterns); `Revision Compiler` (compiles revision plans into dispatchable units); `Revision Dispatcher` (per-module dispatch runtime evolving V2's Revision Bus); `Candidate artifact versions` (rollback semantics with `CandidateArtifactVersion` inside SourceWorkspace as additive structure not separate primitive); `Plan assurance policy` (formal verification of revision plans before execution); `Taint and policy model` (provenance + policy gating on iterative revisions); `Pattern learning` (skill-graph integration for learned patterns becomes formal §22 spec); `Feedback pipeline` (V2's four channels become an end-to-end pipeline with FeedbackConsumptionReceipts and §24/§25 stress-test fixtures). **V3 §0.2 phasing:** Phase 1 (this spec) covers full Evaluator/Revisor/Dispatcher pipeline, candidate versions, taint model, pattern capture, quality programs with metric denominators, sub-agent reputation scoring, dry-run mode, hardware-aware degradation, four-domain eval suite plus domain-neutral smoke set, cross-doc obligations registered in OP-A. **V3 §0.3 Canonical Naming Table** (V3 uses canonical names throughout; implementations and prose MUST NOT introduce synonyms). **V3 §0.4 Canonical Enum Inventory** (every enum declared with owning section; implementations MAY NOT introduce new values or substitute alternates without spec amendment). **V3 §0A Implementation Discipline Preamble** (governs how V3 is implemented; coding agents working from it MUST comply with these rules). **V3 §26 Drift Manifest** (every TODO/placeholder/deferred behavior enters drift manifest with recorded entry). **V3 §24/§25 stress test fixtures** with fixture definitions and four-domain eval suite. **V3 is materially more rigorous than V2** — V2 was an architectural revision over V1; V3 is the post-adjudication tightening that elevates V2 from proposal to spec status with explicit normative discipline. **No explicit "Supersedes:" header in V3** (unlike V2 which explicitly superseded V1) — V3 positions itself as the V3 spec for the same subsystem rather than as a strict supersession of V2 by header declaration; auto pass treats this as a natural-progression supersession (V2 → V3) per the established DOC23 Addenda B Addendum chain pattern. **V2 file (= A-54 row) remains in active folder pending human archival decision after V3 succession.** **V1 file (= A-53 row) ALSO still in active folder pending the same disposition decision after V2/V3 successive supersessions.** DOC23 Addenda B chain at R3.44: R0.1 (global archive) → R0.3 (= A-48, intra-subfolder archive R3.15) → R0.5 (briefly-extant, intra-subfolder archive) → R0.6.1 (= A-49, intra-subfolder archive R3.16) → R0.6.3 (= A-50, intra-subfolder archive R3.18) → **R0.6.4 (= A-51, ACTIVE — current unified Addenda B draft)** + Addendum chain **V1 (= A-53, ACTIVE pending archival) → V2 (= A-54, ACTIVE pending archival) → V3 (= A-56 NEW, ACTIVE)**. Three Addendum revisions now coexist; collapse-opportunity-by-archival deepens further. NB: ADDENDA_STATE.md uses A-56 for this V3 file (continues R3.33 sequence A-53 V1 → A-54 V2 → A-55 R0.1 → A-56 V3); master spec list §4 uses A-57 (preserves R3.33+R3.39+R3.41 cumulative divergence-by-one pattern, with R3.44 advancing it further). **FILE MOVED TO LOCAL ARCHIVE 2026-05-17 (auto-detected 2026-05-17 by R3.47 nightly sync):** moved from `DOC23 Addenda/` root to `DOC23 Addenda/Archived DOC23 addenda/` subfolder (folder mtime 2026-05-17 04:15). This is LOCAL intra-subfolder archival, distinct from global `Archived Addenda Proposals and In Progress/` archive. V3 superseded by A-58 V3.1 (new row above). Row preserved per auto pass no-removal policy. |
| A-52 (informational) | `DOC23 Addenda/DOC23_REPROMPT_SYSTEM_ADDENDUM (1).md` | 2026-05-04 (mtime 2026-05-04 22:53 UTC = 15:53 local) | DOC23 R3.1 (BYTE-IDENTICAL to A-44 `DOC23_REPROMPT_SYSTEM_ADDENDUM.md` — informational duplicate, NOT a separate addendum) | n/a | n/a | n/a (delete-or-canonicalize candidate) | n/a | — | **NEW INFORMATIONAL ANOMALY ROW (auto-detected 2026-05-05 by nightly sync R3.19 backfill; first detected by master spec list R3.18 sync 2026-05-04 ~16:14, NOT given a separate row in master spec list §4.A6 since byte-identical to A-46 master spec list = A-44 ADDENDA_STATE).** File mtime 2026-05-04 22:53 UTC = 15:53 local, size 22,818 bytes — byte-identical to existing A-44 `DOC23_REPROMPT_SYSTEM_ADDENDUM.md` at 22,818 bytes. Filename "(1)" suffix suggests Will copied this from Downloads — same anomaly pattern as A-39 DOC73 V1.6 Adjudication Card "(1)" file noted in master spec list R3.4 and DOC23 Task Optimization R4.0 "(1)" file noted in master spec list R3.7/R3.9. Tracked here as informational — Will to delete the "(1)" duplicate or canonicalize. Counted in this state file for visibility only; does NOT count as a new addendum. |
| A-58 | `DOC23 Addenda/DOC23_ADDB_ADDENDUM_OUTCOME_EVALUATOR_REVISOR_V3_1.md` | 2026-05-17 (mtime 2026-05-17 03:28 local = 10:28 UTC) | DOC23 R3.1 (primary parent via Addenda B R0.6.4); natural-progression successor to A-56 V3 + A-54 V2 + A-53 V1 in DOC23 Addenda B Addendum chain | not_yet | tbd | DOC23 Addenda B (likely fold into next unified draft as V3.1 specification block) | pending | — | **NEW (auto-detected 2026-05-17 by R3.47 nightly sync; mtime 2026-05-17 03:28 local = 10:28 UTC, size 437,051 bytes — ~21% larger than V3 360,081 bytes); needs human classification.** Filename pattern V3 → V3_1 indicates post-V3 patch/revision (analogous to DOC73 V1.4 → V1.4.1 patch pattern). Auto pass treats as natural-progression successor; full content delta from V3 not captured by auto pass (file header read not performed for this auto-detection cycle — Will to annotate or red-team). V3 file (= A-56 row) MOVED to local intra-subfolder archive `DOC23 Addenda/Archived DOC23 addenda/` in same ~04:15 window — A-56 retained below with intra-subfolder-archive annotation per auto pass no-removal policy. Detection sequence: V3.1 created ~03:28; V3 moved to archive ~04:15 (likely human reorganization after V3.1 creation, manually cleaning up the chain). NB: master spec list §4 uses A-59 for this row; ADDENDA_STATE.md uses A-58 — cumulative divergence-by-one pattern extends to R3.47. **R3.49 supersession by V3.2 (= MSL A-60, ADDENDA_STATE A-59 not yet added here as a separate row by R3.49 sync window since ADDENDA_STATE was not updated by R3.49 — backfilled in R3.50 informational only):** V3.2 surgical-patch supersession of V3.1 created 2026-05-17 22:14 UTC (size 461,248 bytes, +5.5% over V3.1) incorporates Addenda A/B coordination V3 FINAL outputs; V3.1 retained ACTIVE in `DOC23 Addenda/` root pending human archival decision. V3.2 file lives in DOC23 Addenda root with byte-identical duplicate in new sub-sub-folder `DOC23 Addenda/doc23 add b rework/`. R3.49 also detected 5 NEW addenda in the new sub-sub-folder: Core R0.7 supersession of R0.6.4 via family-topology reorganization + Feedback Delivery V1 + Source Workspace V1 + Task Forum + Run Board V1 + Common Contracts V1 sibling spec — MSL row numbers A-60 through A-65; ADDENDA_STATE numbering would continue A-59 through A-64. **All R3.49 §A.6 additions deferred for ADDENDA_STATE inclusion in this R3.50 sync window plus the next manual review pass** — to keep this R3.50 mechanical sync surgical, only the new R4.1 V6 row is added formally below (R3.49 narrative is captured here in this informational annotation; full row creation for V3.2 + R0.7 + 4 sub-addenda deferred to next sweep). |
| A-74 | `DOC23 Addenda/DOC23_FAMILY_SELF_LEARNING_COHERENCE_MAP_V1.md` | 2026-05-19 (mtime 2026-05-19 19:43 local, size 53,808 bytes) | DOC23 family cross-cutting reference: A-65 R4.1 V6 + Addenda B Core R0.7 + Addenda B Addendum V3.2 + 3 subsystem sub-addenda + A-64 Common Contracts V1.1 (cross-cutting consumer of all enumerated DOC23 family files) | not_yet | tbd | TBD (likely SUPPORT / REFERENCE MAP / NON-OWNER DRAFT not addendum) | pending | — | **NEW (auto-detected 2026-05-19 by master spec list R3.55 nightly sync auto-bump 2026-05-19 ~23:17 UTC; backfilled to ADDENDA_STATE in R3.56 on 2026-05-20 since R3.55 did not update ADDENDA_STATE.md); needs human classification.** **NEW cross-cutting reference document** — V1 with no prior version; FIRST OBSERVATION of a DOC23 FAMILY-level coherence map. Maps self-learning coherence across DOC23 family addenda — likely Will-side workflow artifact for cross-addendum consistency verification (analogous to A-47 Context Mgmt Proposal Card Integration Map V2 and A-49 R0.6.1 Merge Audit Cleaned which both serve cross-cutting reference functions). **Likely needs reclassification to SUPPORT / REFERENCE MAP / NON-OWNER DRAFT** rather than `PROPOSED ADDENDUM` — same family as A-32 ELNOR Search Architecture Reference R1 and A-47 Card Integration Map V2. Per same-day timing relationship: A-74 created 2026-05-19 19:43 local; A-72 KDA R3 DRAFT v0_2 created 2026-05-19 18:54 local (~49m later) — strongly suggests A-72 KDA R3 incorporates cross-references with A-74; A-71 BDSM V6.5 DRAFT created 2026-05-19 20:50 local (~67m later) — likely also incorporates A-74. **Multi-DOC24-draft drift correlation:** the three same-day files (A-74 → A-72 → A-71) constitute first coordinated DOC23-family + DOC24-family drafting pass in single MSL bump (R3.55). Full file-header inspection deferred to next manual review pass. NB: ADDENDA_STATE uses A-74 (skips A-73 to preserve historical row-bound divergence pattern); master spec list §4 uses A-74 too — divergence resolves coincidentally at this row, but historical divergence-by-one pattern remains intact at A-70/A-71/A-72 — auto pass preserves A-73 skip in ADDENDA_STATE.md as cumulative tracker. |
| A-65 | `DOC23 Addenda/DOC23_ADDENDA_A_TASK_OPTIMIZATION_R4_1_V6 (1).md` | 2026-05-18 (mtime 2026-05-18 06:05 local; size 405,498 bytes) | DOC23 R3.1 (primary parent); Prop-A R6.3 (DSPy self-improvement engine — companion); A-47 R4.1 V2 (predecessor in V2→V6 chain — intermediate V3/V4/V5 never materialized at sync windows, briefly-extant pattern); coordination V3 FINAL outputs (per R3.49 narrative the A-track has been at V3 since coordination V3 work); A-64 Common Contracts V1 (= MSL A-65 — consumer of shared evaluation primitives); A-60 R0.7 Core (= MSL A-61 — companion via family topology) | not_yet | tbd | DOC23 R3.1 (likely absorb as major addendum bundle) / DOC23 Addenda A R5 + R6 deferral list | pending | — | **NEW (auto-detected 2026-05-18 by R3.50 nightly sync; mtime 2026-05-18 06:05:26 local, size 405,498 bytes — ~2.6× A-47 R4.1 V2's 154,930 bytes); needs human classification.** Filename has "(1)" suffix suggesting Will copied from another location (Downloads pattern observed in DOC73 V1.6 Adjudication Card and DOC23 REPROMPT duplicates — same anomaly family). Per coordination V3 FINAL outputs noted in R3.49 narrative (A-65 Common Contracts V1 lists "DOC23 Addenda A R4.1 V3" as consumer), the A-track has been at V3 since coordination V3 work; V6 likely incorporates coordination V3 FINAL outputs plus further audit closure passes — surgical-patch pattern analogous to V3 → V3.1 → V3.2 sequence observed in DOC23 Addenda B chain. **Intermediate V3/V4/V5 archival status unknown** — auto pass observes V6 ACTIVE in `DOC23 Addenda/` root + V2 still in same root + no V3/V4/V5 files in active folder or in `Archived DOC23 addenda/` intra-subfolder archive at time of detection. Likely Will managed these revisions outside the sync windows (briefly-extant pattern observed previously for R4.1 V1 in R3.12). Companion to A-60 R0.7 Core, V3.2 Outcome Evaluator/Revisor, and Common Contracts V1 — the four collectively form the post-coordination V3 FINAL DOC23 working set. Full file-header inspection deferred to next manual review pass. NB: ADDENDA_STATE.md uses A-65 for this file (continues single-step numbering from A-58 V3.1 — the R3.49 sub-sub-folder rows A-59 through A-64 are not yet added formally to ADDENDA_STATE; today's R3.50 sync continues sequence A-58 V3.1 → A-65 R4.1 V6); master spec list §4 uses A-66 (preserves cumulative divergence-by-one pattern extending to SIX NEW-row cycles). |
### A.7 Unified Brain Bucket Lib Proj subfolder (NEW — folder created 2026-05-14 09:18:54 local = 16:18 UTC, formally tracked here from 2026-05-15 backfill onward)
**Auto-detected 2026-05-14 by master spec list R3.41 sync (~23:10 UTC, ~16:10 local); first folded into ADDENDA_STATE by 2026-05-15 backfill sync.** New subfolder `Unified Brain Bucket Lib Proj/` appeared in `Addenda Proposals & In Progress/` (folder mtime 2026-05-14 09:18:54 PDT = 16:18 UTC). **FIRST EVER multi-parent cross-doc proposal subfolder** — structurally distinct from existing single-parent subfolders (`DOC20 Addenda/`, `DOC24 Addenda/`, `DOC72 Addenda and Proposals/`, `DOC73 Addenda and Proposals/`, `DOC23 Addenda/`) which each target one operative spec. This subfolder explicitly multi-parent across DOC20 + DOC7 + DOC25 + DOC72 + DOC73 + DOC24 + DOC23 + DOC11/OpenClaw + DOC1 + EC Core all at once. As with prior new-subfolder events (DOC73 Addenda in R2.9, DOC23 Addenda in R3.9), the in-scope folder list in the nightly sync task SKILL.md needs human update to formally include the new path (auto pass scans it as in-scope by precedent).
| ID | Filename | Date | Parent Spec(s) | Reviewed | Disposition | Disp. Target | Integration Status | Int. Date | Notes |
|---|---|---|---|---|---|---|---|---|---|
| A-57 | `Unified Brain Bucket Lib Proj/Unified_Workspace_Library_WorkContext_Proposal_R0_2.md` | 2026-05-15 (file-header date; mtime 2026-05-16 00:04 UTC) | DOC20 R4.3; DOC7 R7 Consolidated; DOC25 V2.0; DOC72 R5.73 (and DOC72 CSA R2 = A-35); DOC73 V1.5.1 (and forthcoming V1.6); DOC24 R3 (and DOC24 Addendum A BDSM v6.4 = A-22; DOC24 KDA R2 = A-19); DOC11/OpenClaw R14 + R15 Amendment Proposal (= A-1 / A-34); DOC1 Memory Resilience Rebuild R1; EC Core Specs Rebuild R1 (and EC Core Addendum A V3.3 = A-4); CSA/continuity architecture. **NB: DOC23 explicitly demoted to integration-boundary-only status per R0.2 scope statement** (R0.1 included DOC23 as co-owner; R0.2 excludes from owner targets) | not_yet | tbd | TBD — same disposition guidance as R0.1 carries forward but R0.2's explicit DOC23 demotion provides Will-side signal pointing toward option (b) where DOC23 becomes companion/integration-boundary rather than owner | pending | — | **NEW (auto-detected 2026-05-16 by R3.44 nightly sync; mtime 2026-05-16 00:04 UTC, size 88,291 bytes, 3,220 lines — ~38% larger than R0.1's 63,741 bytes); needs human classification.** **Explicit supersession declaration**: per R0.2 file header `**Supersedes:** Unified_Workspace_Library_WorkContext_Proposal_R0_1.md for current discussion purposes.` — first explicit supersession in this §A.7 track (R0.1 was the only prior file). Per R0.2 file header: "# Unified Workspace / Library / Work Context / Work Product / Resume Work / Continuity Proposal R0.2"; **Status:** "Draft proposal for architect review and iterative refinement."; **Date:** "2026-05-15.". **Title evolution from R0.1:** R0.1 title was "Workspace / Library / Work Context / Work Product / Output Routing / Task Scope / Working Set / Continuity Proposal"; R0.2 title is "Workspace / Library / Work Context / Work Product / Resume Work / Continuity Proposal" — **drops "Output Routing", "Task Scope", "Working Set"; adds "Resume Work"** — significant scope refinement consolidating around the resume-work surface as the primary user-facing affordance over the more granular scope envelope vocabulary. **Scope refinement vs R0.1:** R0.2 scope says "Integration proposal across DOC20, DOC7, DOC25, DOC72, DOC73, DOC24, DOC11/OpenClaw, DOC1, EC Core, and CSA/continuity. DOC23 is included only as an integration boundary, not as an owner target for task-run context design." — **explicitly excludes DOC23 from owner targets** (architect judgment that the Unified Workspace proposal should not co-own task-run context with DOC23's existing task system). **Design posture strengthened:** R0.2 design-posture line says "Seam-focused. This proposal does not rewrite DOC72, DOC73, DOC23, DOC24, DOC20, DOC7, or CSA. It names product objects, clarifies product behavior, **gives enough schema detail to reason about seams**, and identifies owner-doc changes without taking over owner-doc responsibilities." — adds explicit promise to "give enough schema detail to reason about seams" (R0.1 said only "names product objects, clarifies seams"); R0.2 is therefore more specification-flavored than R0.1's purely-product-model framing. **NEW R0.2 architectural primitive — Library source status model** with three additive statuses (NOT separate memory systems): **Linked**, **Indexed**, **Learned** — clarifies R0.1's vague "availability vs cataloging vs learning" distinction. **Retired R0.1 concepts** per R0.2's explicit retirement table: **Available** (retired as Library level/status because all Linked/Indexed/Learned sources are available, so the level was not distinguishing anything); **Cataloged** (retired as Library status because too vague — "Indexed" better communicates the document-intelligence delta). **NEW R0.2 Co-Work-like behavior in Output Location**: if user opens or uploads a source document from a folder and asks Elnor to revise it, Elnor should often save a new sibling version near the source — formalizes source-folder affinity as a default Output Location heuristic. **Retains R0.1 core product model** with Session Working Set + Work Stream consolidated into the Resume Work surface: Workspace, Work Context, Library, Folder Binding, Work Product, Output Location, Assistant, Task, Continuity Card. **Retains R0.1 core philosophy** axioms verbatim per §2: "Everything is optional"; "One substrate, visible lenses"; "Availability, cataloging, and learning are different"; "Cataloging is not a separate memory lane" (still governed by DOC72 intake/significance/extraction/Write Gate pipeline). **R0.1 file (= A-55 row above) remains in active folder pending human archival decision per auto pass's no-relocation policy** (options: (a) move to `Archived Addenda Proposals and In Progress/` following supersession-and-archive pattern; (b) keep in active folder for traceability of architectural evolution R0.1 → R0.2). NB: ADDENDA_STATE.md uses A-57 for this R0.2 file (continues sequence A-55 R0.1 → A-56 V3 → A-57 R0.2); master spec list §4 uses A-58 (preserves R3.33+R3.39+R3.41+R3.44 cumulative divergence-by-one pattern). |
| A-55 | `Unified Brain Bucket Lib Proj/Unified_Workspace_Library_WorkContext_Proposal_R0_1.md` | 2026-05-14 (mtime 2026-05-14 09:18:21 PDT = 16:18 UTC) | DOC20 + DOC7 + DOC25 + DOC72 + DOC73 + DOC24 + DOC23 + DOC11/OpenClaw + DOC1 + EC Core (cross-doc multi-parent — first ever) + continuity/CSA (= A-35 DOC72 Continuity Synthesis Architecture R2 + A-36 DOC73 §6.4 Mechanism 4 Rollup V1) | not_yet | tbd | TBD — likely SUPPORT/SEAMS rather than addendum to any single doc; possible promote_new to a numbered cross-doc spec | pending | — | **NEW (auto-detected 2026-05-14 by R3.41 nightly sync; first-tracked in ADDENDA_STATE by 2026-05-15 backfill sync; mtime 2026-05-14 09:18:21 PDT = 16:18 UTC, size 63,741 bytes); needs human classification.** Per file header: "Unified Workspace / Library / Work Context / Work Product / Output Routing / Task Scope / Working Set / Continuity Proposal R0.1", document date 2026-05-10, status "Draft proposal for architect review and iterative refinement". Scope: "Integration proposal across DOC20, DOC7, DOC25, DOC72, DOC73, DOC24, DOC23, DOC11/OpenClaw, DOC1, EC Core, and continuity/CSA." Design posture per file: "Seam-focused. This proposal does NOT rewrite DOC72, DOC73, DOC23, or DOC24. It names product objects, clarifies seams, and defines cross-doc owner obligations where the current system has useful pieces that are not yet exposed as one coherent user model." Core product model defines: Workspace, Work Context, Library, Folder Binding, Work Product, Output Location, Assistant, Task, Session Working Set, Work Stream, Continuity Card — explicitly as lenses/bindings/profiles/views over the same governed substrate rather than separate brains or memory truth systems. §2 axioms: "Everything is optional"; "One substrate, visible lenses"; "Availability, cataloging, and learning are different"; "Cataloging is not a separate memory lane" (still governed by DOC72 intake/significance/extraction/Write Gate pipeline). **Disposition guidance pending human review:** because the file is multi-parent and seam-focused (not adding content to any one operative spec but rather defining cross-doc seams), three classification options are open: (a) promote to standalone numbered doc (DOC50+) as a new cross-doc spec; (b) split into per-parent-doc inserts (one DOC20 insert + one DOC7 insert + one DOC72 insert + …); (c) keep as SUPPORT / REFERENCE doc (akin to A-32 ELNOR Search Architecture Reference R1) that names seams without normative content. Auto pass leaves disposition TBD. NB: master spec list §4 uses A-56 for this row; ADDENDA_STATE uses A-55 — numbering divergence preserved (R3.33 + R3.39 + today extend the one-row-divergence pattern). Superseded transitively by A-77 R0.3 row below (R0.1 → R0.2 → R0.3 chain). |
| A-77 | `Unified Brain Bucket Lib Proj/Unified_Workspace_Library_Project_Proposal_R0_3.md` | 2026-05-16 (file-header date; mtime 2026-05-20 10:47:42 local, size 89,032 bytes) | DOC20 (UI primary); DOC24 (routing/delivery); DOC7 (buckets); DOC25 (document intelligence); DOC73 V1.6 (PBE/corpus); DOC1 (memory governance); DOC11/OpenClaw; DOC8 (learning); EC Core; DOC72 (heavily referenced via in-flight DOC72 Entity Attenuator Addendum companion to DAMS); DOC23 R3.1 (integration boundary only — continuing R0.2 demotion) | not_yet | tbd | TBD — same disposition guidance as R0.1/R0.2 carries forward; R0.3 explicit project-mode-as-primitive collapse suggests material may eventually split between DOC20 + DOC24 + DOC1 inserts | pending | — | **NEW (auto-detected 2026-05-20 by master spec list R3.58 nightly sync auto-bump; backfilled to ADDENDA_STATE in R3.59 on 2026-05-21 since R3.58 did not update ADDENDA_STATE.md); needs human classification.** **Explicit supersession of A-57 R0.2** per file header: "Supersedes: Unified_Workspace_Library_WorkContext_Proposal_R0_2.md (2026-05-15)". **Third explicit supersession declaration** in §A.7 multi-parent track (R0.1 → R0.2 → R0.3) — chain of three explicit-supersession declarations is structurally unique among addenda tracks. **Title evolution:** R0.2 was "Workspace / Library / Work Context / Work Product / Resume Work / Continuity Proposal"; R0.3 is "Workspace / Library / Project Mode / Output Routing / Memory Continuity Proposal" — drops "Work Context", "Work Product", "Resume Work"; adds "Project Mode", "Output Routing" (reinstated from R0.1), "Memory Continuity". **Core insight driving R0.3 (per §0):** "ambiguity is the actual UX failure, not friction. Ambient inference + dismissible chip ('Working on: Paramount') minimized friction but introduced ambiguity about whether content was being captured to one matter or another. Explicit project mode with unmistakable visual chrome eliminates the ambiguity in exchange for a small amount of deliberate friction." **Concept consolidation:** R0.2's eleven user-facing concepts (Workspace, Work Context, Library, Folder Binding, Work Product, Output Location, Assistant Profile, Working Set, Work Thread, Resume Activation, Continuity Card) collapsed to much smaller set **centered on explicit project mode as primary primitive**. **Companion to A-78/A-79 DAMS proposals (new §A.8):** R0.3 explicitly references DAMS's per-entity attenuator primitive as canonical and applies it to project's underlying DOC72 `world_entity` node. A-57 R0.2 row above gets natural-progression-supersession annotation pending human archival decision. Disposition guidance unchanged from R0.2: still TBD pending human classification. |
---
### A.8 DOC 80 DAMS subfolder (NEW — folder created 2026-05-20 ~13:42 local, formally tracked here from R3.58 backfill in R3.59 on 2026-05-21)
**Auto-detected 2026-05-20 by master spec list R3.58 sync; backfilled to ADDENDA_STATE in R3.59 on 2026-05-21 since R3.58 did not update ADDENDA_STATE.md.** New subfolder `DOC 80 DAMS/` appeared in `Addenda Proposals & In Progress/` (folder mtime 2026-05-20 13:42 local = last child write for DAMS_PROPOSAL_V2.md). **FIRST EVER addenda subfolder pattern keyed to a placeholder DOC number not yet in the registry's core spec list** (DOC80 = DAMS Core Architecture; DOC81 = DAMS Consumer Integration Map). Subfolder is structurally analogous to existing single-parent subfolders (`DOC20 Addenda/`, `DOC24 Addenda/`, `DOC72 Addenda and Proposals/`, `DOC73 Addenda and Proposals/`, `DOC23 Addenda/`, `DOC11 Openclaw Addenda & Docs/`) BUT differs in that the parent spec numbers do not exist yet — these are proposed/placeholder docs that will materialize if/when the DAMS proposal is accepted. **Backlog:** SKILL.md scope list does not yet formally include this path (eighth not-formally-listed subfolder added since SKILL.md tightening recommendation began at R3.26). As of R3.59 detection 2026-05-21, subfolder contains 4 files (V1 + V2 same-day pair from R3.58 + V3 + V3 (1) same-day-pair from R3.59).
| ID | Filename | Date | Parent Spec(s) | Reviewed | Disposition | Disp. Target | Integration Status | Int. Date | Notes |
|---|---|---|---|---|---|---|---|---|---|
| A-78 | `DOC 80 DAMS/DAMS_PROPOSAL_V1.md` | 2026-05-20 (file-header date; mtime 2026-05-20 11:32:26 local, size 131,064 bytes) | Placeholder DOC80 (core primitive) + DOC81 (consumer integration map); integration touches: DOC72 (entity graph primary at integration), DOC24 (delivery), DOC1 (memory governance), DOC8 (learning), DOC73 (PBE), PropA R6.3 (sensitivity), DOC20 (UI), DOC11/OpenClaw (runtime), EC Core Addendum A V3.3 (data ops); referenced but not consolidated: DOC25, DOC15, DOC7, DOC10. Companion: A-77 R0.3 Unified Workspace Proposal | not_yet | tbd | TBD — likely first promote_new to numbered cross-doc spec (DOC80 + DOC81 placeholder targets); possible alternative is fold-into-DOC72 (rejected per V2 framing — DOC72 already ~9,900 lines past authoring target) | pending | — | **NEW (auto-detected 2026-05-20 by master spec list R3.58 nightly sync auto-bump; backfilled to ADDENDA_STATE in R3.59 on 2026-05-21 since R3.58 did not update ADDENDA_STATE.md); needs human classification.** **FIRST EVER DAMS (Dynamic Attenuator Memory System) proposal.** Per file header: "Author: Will Brody; Date: 2026-05-20; Status: Draft proposal for red-team review before integration into ELNOR spec suite; Placeholder DOC numbers: DOC80 (core primitive) + DOC81 (consumer integration map). Final numbers TBD." Reader's guide (per §0): single document contains material that will eventually split into two specifications — DOC80 (the primitive, schemas, composition function, invariants, and DOC72 integration) + DOC81 (cross-doc obligations enumerating how each existing spec consumes the DAMS substrate). Section headers indicate `[DOC80]`, `[DOC81]`, or `[META]`. Five-part structure: (1) Overview and motivation (five primary use cases); (2) What DAMS is (full architecture in two sub-sections); (3) Feasibility and risk; (4) Benefits and measurement; (5) Implementation approach (Options A/B/C). **First addenda-subfolder pattern where placeholder DOC numbers anchor the entire subfolder identity rather than a confirmed existing parent spec.** Superseded by A-79 V2 row below (same-day pair) and A-81 V3 consolidated row below (R3.59 NEW). Full file-header inspection completed by R3.58 narrative; deferred items noted there. **FILE MOVED TO GLOBAL ARCHIVE 2026-05-22 OR 2026-05-23 (auto-detected 2026-05-24 by R3.62 TWO-DAY-GAP-CATCHUP sync; mtime 2026-05-20 11:32:26 preserved across move):** `Addenda Proposals & In Progress/Archived Addenda Proposals and In Progress/DAMS_PROPOSAL_V1.md`. Row preserved for traceability per auto-pass no-removal policy. |
| A-79 | `DOC 80 DAMS/DAMS_PROPOSAL_V2.md` | 2026-05-20 (file-header date; mtime 2026-05-20 13:42:32 local, size 81,272 bytes; -49,792 bytes / -38% under V1 = A-78) | Placeholder DOC80 + DOC81; integration touches: DOC72 (entity graph), DOC24 (delivery), DOC1 (memory governance), DOC8 (learning + phantom finding), DOC73 (PBE), DOC11 (runtime), DOC20 (UI + Control Surface §16), DOC23 family, DOC15 (CIL), EC Core. Companion review document: `DAMS_PROPOSAL_V1_RED_TEAM_PROMPT.md` likely sibling. Companion proposal: A-77 R0.3 Unified Workspace Proposal | not_yet | tbd | TBD — same as V1; V2's DOC8 phantom finding implies §3 DOC8 row may need substantial respec or replacement | pending | — | **NEW (auto-detected 2026-05-20 by master spec list R3.58 nightly sync auto-bump; backfilled to ADDENDA_STATE in R3.59 on 2026-05-21 since R3.58 did not update ADDENDA_STATE.md); needs human classification.** **Same-day V1→V2 within ~2h window** is FIRST EVER intra-folder pair pattern in any addenda subfolder in this scheduled task's history. Per V2 §"What changed from V1": V2 corrects V1 framing facts — (1) Build-it-all-at-once: ELNOR is not a running system being incrementally extended; nothing is implemented; entire platform being built in one effort. (2) DAMS is not folded into DOC72 (DOC72 already ~9,900 lines past 4,000-line authoring target and ~5,000-line review ceiling; DAMS is cross-cutting). (3) **DOC8 phantom finding:** the document named DOC8 is a 730-line friction engine from prior architecture generation containing no attribution / no Shapley / no utility scoring / no entity-graph awareness — none of the "learning engine" capabilities DOC24, DOC72, DOC73, DOC23, BDSM reference. **The learning engine the stack depends on does not exist as a written spec** — critical dependency finding. (4) Implementation reframed: V1 Options A/B/C partly about sequencing against a running system; V2's real question is document architecture — DAMS as spine of coherent memory-system rebuild vs DAMS as two standalone specs. (5) Control Surface: V1 hand-waved attenuator UI as "Knowledge Manager panel"; V2 adds real §16 specifying unified memory Control Surface. (6) Naming: DAMS = Dynamic Attenuator Memory System (attenuator not attenuated). (7) Ambition stated explicitly: §0 now states goal plainly so red team can evaluate against it. **Critical cross-doc finding for §3 Core Specifications:** the V2 DOC8 phantom finding implies DOC8 R3 may need substantial respec or replacement — flagged for human review as a possible future §10 file-system anomaly entry. V1 row above gets natural-progression-supersession annotation. Superseded by A-81 V3 consolidated row below (R3.59 NEW). **FILE MOVED TO GLOBAL ARCHIVE 2026-05-22 OR 2026-05-23 (auto-detected 2026-05-24 by R3.62 TWO-DAY-GAP-CATCHUP sync; mtime 2026-05-20 13:42:32 preserved across move):** `Addenda Proposals & In Progress/Archived Addenda Proposals and In Progress/DAMS_PROPOSAL_V2.md`. Row preserved for traceability per auto-pass no-removal policy. |
| A-81 | `DOC 80 DAMS/DAMS_V3_CONSOLIDATED_ARCHITECTURE_PROPOSAL.md` | 2026-05-21 (mtime 2026-05-21 05:56 local, size 78,062 bytes; -3,210 bytes / -4% under V2) | Placeholder DOC80 + DOC81; integration touches: DOC72, DOC24, DOC1, DOC8, DOC73, DOC11, DOC20, DOC23, DOC15, EC Core (same scope as V2). Companion proposal: A-77 R0.3 Unified Workspace Proposal | not_yet | tbd | TBD — same as V1/V2; "CONSOLIDATED ARCHITECTURE" filename suggests V3 represents the consolidation of V1 + V2 framing-and-decision material into single coherent architecture proposal | pending | — | **NEW (auto-detected 2026-05-21 by nightly sync R3.59); needs human classification.** **Natural-progression consolidated successor to A-78/A-79 V1+V2 same-day pair.** Filename change V2 `DAMS_PROPOSAL_V2` → V3 `DAMS_V3_CONSOLIDATED_ARCHITECTURE_PROPOSAL` signals: (a) consolidation from proposal-iteration mode to architecture-baseline mode; (b) explicit "consolidated" framing suggests V3 incorporates V1's framing material + V2's corrections + new content into single coherent proposal. Modest size reduction (-4% under V2) consistent with consolidation tightening rather than substantive expansion. Co-occurs with A-82 V3 (1)-duplicate row below within ~3min window — first ever same-day primary + (1)-duplicate pair in DOC 80 DAMS subfolder. Full file-header inspection deferred to next manual review pass. A-78 V1 + A-79 V2 rows above get natural-progression-consolidated-successor annotations pending human archival decision. **FILE MOVED TO GLOBAL ARCHIVE 2026-05-22 OR 2026-05-23 (auto-detected 2026-05-24 by R3.62 TWO-DAY-GAP-CATCHUP sync; mtime 2026-05-21 05:56 preserved across move):** `Addenda Proposals & In Progress/Archived Addenda Proposals and In Progress/DAMS_V3_CONSOLIDATED_ARCHITECTURE_PROPOSAL.md`. Row preserved for traceability per auto-pass no-removal policy. Will-side archival decision consolidates §A8 active to V4.1 only post-R3.61 V4 + V4.1 successor pair. |
| A-82 | `DOC 80 DAMS/DAMS_V3_CONSOLIDATED_ARCHITECTURE_PROPOSAL (1).md` | 2026-05-21 (mtime 2026-05-21 05:59 local, size 94,239 bytes; +16,177 bytes / +20.7% over primary V3) | Placeholder DOC80 + DOC81 (same as primary V3) | not_yet | tbd | TBD — needs comparison to primary V3 to determine which copy is canonical | pending | — | **NEW (auto-detected 2026-05-21 by nightly sync R3.59); needs human classification.** **(1)-suffix duplicate variant** of A-81 primary V3 — written ~3min after primary (05:56 → 05:59 local). **First ever same-day intra-folder duplicate pair in DOC 80 DAMS subfolder**, but unlike prior (1)-suffix patterns (Will-copied-from-Downloads matching primary), this duplicate is **LARGER than primary by +20.7% (78,062 → 94,239 bytes)** — workflow-signal mystery. Possible interpretations: (a) primary V3 was an incomplete first save and duplicate is the actual complete version with later content added; (b) duplicate has additional content (companion red-team prompt, alternative framing, expanded sections) that primary lacks; (c) duplicate is a different content variant where (1)-suffix represents a parallel iteration rather than a copy. Full file-content diff comparison vs primary V3 needed to determine canonical version. Auto pass leaves both files in active subfolder pending human archival/canonicalization decision. NB: per the (1)-suffix downloads-copy pattern observed in DOC73 V1.6 Adjudication Card and DOC23 REPROMPT duplicates, this is the first observation where the duplicate exceeds the primary in size. **FILE MOVED TO GLOBAL ARCHIVE 2026-05-22 OR 2026-05-23 (auto-detected 2026-05-24 by R3.62 TWO-DAY-GAP-CATCHUP sync; exact archive timestamp not preserved across move; mtime 2026-05-21 05:59 preserved):** `Addenda Proposals & In Progress/Archived Addenda Proposals and In Progress/DAMS_V3_CONSOLIDATED_ARCHITECTURE_PROPOSAL (1).md`. Row preserved for traceability per auto-pass no-removal policy. Will-side archival decision consolidates §A8 active to V4.1 only. |
| A-83 | `DOC 80 DAMS/DAMS_V4_CONSOLIDATED_ARCHITECTURE_PROPOSAL.md` | 2026-05-22 (mtime 2026-05-22 04:19 local, size 62,380 bytes; -15,682 bytes / -20.1% under primary V3 = A-81) | Placeholder DOC80 + DOC81; integration touches: DOC72 (entity graph), DOC24 (delivery), DOC1 (memory governance), DOC8 (learning + phantom finding), DOC73 (PBE), DOC11 (runtime), DOC20 (UI + Control Surface §16), DOC23 family, DOC15 (CIL), EC Core. **CENTRAL REFRAME per R3.61 §12** — DAMS is one demoted substrate inside a larger memory architecture (memory-as-control-problem; Premise Families base object; Context Compiler emitting warranted packets; recompile-on-resume + cognitive diff; thick-floor/thin-swappable-judgment invariant; domain-packs; Knowledge Topic primitive). Lineage V2 → meta-review → V3.1 → V4 (V3.1 briefly-extant or skipped between V3 and V4 per R3.61 lineage narrative; no V3.1 file observed in active or global archive subfolders) | not_yet | tbd | TBD — DAMS reframing implies broader memory-architecture rebuild scope possibly beyond original DAMS scope | pending | — | **NEW (auto-detected 2026-05-24 by R3.62 TWO-DAY-GAP-CATCHUP sync; R3.61 narrated this row as A-84 in MSL §4 numbering; R3.62 tracks as A-83 in ADDENDA_STATE divergent numbering); needs human classification.** **FIRST EVER central-reframe successor in any addenda subfolder** — V4 fundamentally reframes V3's consolidated architecture proposal as a substrate-component rather than standalone proposal; substantial structural change from V3 (size -20.1% suggests tightening rather than expansion; the structural reframe is doing the work, not bulk additions). **FILE MOVED TO GLOBAL ARCHIVE 2026-05-22 OR 2026-05-23 (exact archive timestamp not preserved; mtime 2026-05-22 04:19 preserved):** `Addenda Proposals & In Progress/Archived Addenda Proposals and In Progress/DAMS_V4_CONSOLIDATED_ARCHITECTURE_PROPOSAL.md`. Will likely archived V4 same day as V4.1 (within minutes of V4.1 modification 04:27) as V4.1 supersedes V4. Row preserved for traceability per auto-pass no-removal policy. A-81 V3 + A-82 V3 (1) rows above get natural-progression-central-reframe-successor annotations pending human archival completion (already partial — V3 and V3 (1) also moved to global archive today). |
| A-84 | `DOC 80 DAMS/DAMS_V4_1_CONSOLIDATED_ARCHITECTURE_PROPOSAL.md` | 2026-05-22 (mtime 2026-05-22 04:27 local, size 64,604 bytes; +2,224 bytes / +3.6% over V4 = A-83) | Placeholder DOC80 + DOC81; same integration scope as V4 plus V4.1 §B.8 three-Topics walkthrough cross-references DAG primitive integration touchpoints | not_yet | tbd | TBD — same as V4; sole remaining active file in §A8 post-V1/V2/V3/V3(1)/V4 archival | pending | — | **NEW (auto-detected 2026-05-24 by R3.62 TWO-DAY-GAP-CATCHUP sync; R3.61 narrated this row as A-85 in MSL §4 numbering; R3.62 tracks as A-84 in ADDENDA_STATE divergent numbering); needs human classification.** Per R3.61 §12 V4.1 file header: two content additions vs V4 (§B.8 worked three-Topics walkthrough establishing the multi-parent acyclic DAG; §C.1 sharpened "the merge is itself the audit" epistemics), no structural change. Modest +3.6% size growth consistent with two-section-addition pattern. **SECOND EVER same-day intra-window successor pair in DAMS subfolder** (V4 04:19 → V4.1 04:27, ~8min apart) — tighter than R3.59 OPA V3.17→V3.18 ~17min pair AND tighter than R3.58 DAMS V1→V2 ~2h pair. **Sole remaining active file in §A8 post-R3.62 catchup** (V1/V2/V3/V3(1)/V4 all archived). A-83 V4 row above gets natural-progression-intra-version-additions-successor annotation (V4.1 is +sections rather than supersession; both could coexist if Will wants V4 baseline preserved, but Will archived V4 anyway). |
---
## B. Integrated Addenda (in `Integrated Addenda/` — for traceability only)
| ID | Filename | Date | Parent Spec | Integrated Into | Date | Notes |
|---|---|---|---|---|---|---|
| I-1 | `Integrated Addenda/DOC24_ROUTING_CASCADE_PROJECT_AGNOSTICISM_FIX (1).md` | 2026-04-04 | DOC24 R2.5 | DOC24 R2.5 | (R2.5 release) | Bug fix integrated as part of 97-item R2.5 adjudication. |
| I-2 | `Integrated Addenda/DOC24_TOOL_CAPABILITY_NODES_AMENDMENT.md` | undated | DOC24 R2.5 | DOC24 R2.5 (ADJ-91) | (R2.5 release) | `tool_capability` lightweight node type in DOC72 entity graph. |
| I-3 | `Integrated Addenda/DOC25_DOC INTELLIGENCE_SPEC.md` | 2026-04-11 | DOC25 V2.0 | DOC25 V2.0 | 2026-04-26 | V1.0 source — absorbed in full into DOC25 V2.0. |
| I-4 | `Integrated Addenda/DOC25_PLANNING_NOTES_V2.md` | 2026-04-24 | DOC25 V2.0 | DOC25 V2.0 (8 open questions resolved) | 2026-04-26 | Planning notes that defined V2.0 scope. |
| I-5 | `Integrated Addenda/DOC_INTELLIGENCE_EXTRACTION_PIPELINE_PROPOSAL_R1.md` | 2026-04-23 | DOC25 V2.0 | DOC25 V2.0 §§8-10 | 2026-04-26 | LLM doc escalation tool, OCR pipeline, MarkItDown universal extraction backend. |
## C. Cross-Doc References (in `CD Cross Docs/`)
| ID | Filename | Date | Status | Notes |
|---|---|---|---|---|
| C-1 | `CD Cross Docs/CD-A_4-1-26_DOC3_DOC24_CYCLE.md` | 2026-04-02 | Active staging | **OP-A foldable — Session 2.** Items prefixed CD-A-001 through CD-A-095. May empty out as items are recognized as already absorbed. |
| C-2 | `CD Cross Docs/CD_MASTER_INTEGRATION_INDEX_R1.md` | 2026-04-01 | Superseded | Replaced by OP-A V2. Retained for reference. |
---
## D. Outside-Folder Items Identified by V2 Carryover (NOT foldable into OP-A in current pass)
Per OP-A V2 carryover §1A scope rule:
- `Memory Intake and At-Use Disciplines Proposal V1` (= A-6) — pending red team
- `Persistent Onboarding Curiosity amendment` (= A-21) — drafted, not yet adopted
- Per-doc internal §22 amendment matrices (DOC24 §22, DOC3 §22, etc.) — migrate when owning spec revises
- `DOC10 Orchestration Integration Ledger R10` (= DOC10 Ledger) — DOC10 awaiting significant revision
- `Running Brief Remediation v6.0` — outdated, refresh anticipated
- Documents inventoried in OP-A V2 §9 as unverified-existence (DOC72 KSI Map R2, ELNOR Knowledge Store Unification Plan R1, Cross-Doc Integration Plan v4, DOC16 Deferred Additions R5.3) — leave for future investigation
---
## Update protocol
1. After review of an addendum: set `Reviewed` to `done` (note round count).
2. After disposition decision: set `Disposition` and `Disp. Target`.
3. When integration begins: set `Integration Status` to `in_progress`.
4. When integration completes: set to `done` + date. Move file to `Integrated Addenda/` subfolder. Update entry to row in §B with `Integrated Into` and date.
5. Per Invariant #24 (post-absorption versioning rule): once absorbed into operative spec, archive. Subsequent work targeting that area authors a NEW proposal against the operative text, not a revision of the archived addendum.
6. Anytime: update `Notes`.