Purpose. Read-only inspection for B-15 (the June→July absorption pass). No writes, no commits made in the course of producing this report against loomworks-record, loomworks-engine, or loomworks (Operator Layer). This file itself is the sole write, delivered to Downloads.
Window. 2026-06-01 through 2026-07-30.
Author. Claude Code (Fable 5). Operator: Marvin Percival.
Date. 2026-07-30.
dunin7-build-list-v0_5.md and .md's HTML sibling are present on origin/main of loomworks-record (confirmed via git ls-tree origin/main -- standing-notes/ after git fetch).main HEAD: 43bb66f ("build list v0.5 — decisions 2-8 answered; B-24 opened; B-11 prerequisite corrected to B-15"), local and origin in sync.
current-status-manifest-v0_75.md (plus its recipe sibling current-status-manifest-v0_75-amendment-v0_1.md) is the highest-versioned manifest in current-status/. The current-status/archive/ directory exists and is empty — nothing superseding v0.75 has been filed or archived.
> Absorption gap: OL and engine work landed 2026-06-28 → 2026-07-19/28 with no §3 entry (filed v0.75). The manifest's last recorded build fronts are v0.72's OL b107290 / engine 0b2c232 (2026-06-28). The repos' actual fronts (verified 2026-07-28) are OL main 99f7f64 (2026-07-19, "Merge Item 7a into main: /claim standing→credit fall-through + admin claim_url") and engine main 1aac815. Neither advance is absorbed: the OL Item 7a claim/credit arc appears nowhere in the manifest, and 1aac815 is cited (v0.73/v0.74) only as the SHA the inspections read, never as a recorded advance from 0b2c232. Engine test names at 1aac815 (e.g. CR-2026-124 open/close intents, CR-2026-129 recall truthfulness, CR-2026-137 find-files, CR-2026-154 supersession-aware answering) indicate the window carries multiple landed CRs. Owed: an absorption pass from the session records for that window — a proper pass, not a reconstruction from test names. Until it runs, treat §1's substrate-state SHAs for OL/engine as superseded by the fronts named here.
The immediately preceding §5 item (the resolved-residue record this one follows) is also load-bearing context:
> OL Companion work — MERGED to main (2026-06-28). [RESOLVED] … Re-verified against the repo 2026-07-28: git merge-base --is-ancestor feat-companion-surface main true; main..feat-companion-surface = 0 commits; tag add-side-rework-ol-v0_1 present (annotated, at cbd1742 → commit 8bd73f2, confirmed in main). OL main has since advanced to 99f7f64 (2026-07-19; 60 commits past 3f2fca8) — see the v0.75 absorption-gap residue.
Note: since v0.75 was filed (2026-07-28), both repo fronts have advanced further — engine to a317051 (CR-2026-158, this session) and OL is unchanged at 99f7f64. §2–3 below give the full window history so the eventual absorption pass has the complete substrate, not just the delta the v0.75 residue already named.
loomworks-engine: commit and merge history, windoworigin/main in window: 351.489ceb6 (2026-06-02).a317051 (2026-07-30 — CR-2026-158 implementation notes, this session's work, merge c4014d6).1aac815 (2026-07-19/28-verified); the engine has since advanced 1aac815 → a317051 via this session's CR-2026-158 (5 commits + merge + notes), itself now also outside the last-absorbed manifest state.
489ceb6 2026-06-02 Merge: map object-store outage to 503 in get_object_store
3e76fc8 2026-06-02 Merge: image_vision_analysis converts before the vision call
129d124 2026-06-17 Merge Stele Phase 6b: Person-view split — Principal + HostAccount views, get_current_principal, Person name retired (CR-2026-110)
bee2b4c 2026-06-18 Merge Stele contract phase (host-side teardown): persons principal-only (CR-2026-111)
d0f302e 2026-06-18 Merge CR-2026-112 (Stele CR-C): principals canonical identity; trigger reversed; stele/models.py SteleBase-only
fe7c3f1 2026-06-19 Merge CR-2026-113 Stele Extraction CR-B: host-FK re-target, mirror retire, persons drop
0ae231b 2026-06-24 Merge CR-2026-121 — Companion Human Commit Affordance
59c8249 2026-06-25 Merge CR-2026-122 — Conversational Fidelity (persona state-to-word mapping)
6f785f9 2026-06-26 Merge CR-2026-123 — Current-engagement spine (v0.3)
cfeebd0 2026-06-26 Merge CR-2026-124 — Spoken open/close intents (v0.2)
eeae9c2 2026-06-27 Merge list-loading CR-1 (engine cursor contract) into main
bd8baea 2026-06-27 Merge CR-2 engine (lists.page_size setting)
41704ef 2026-06-27 Merge Companion truthfulness fix into main
ed5b2b4 2026-06-28 Merge removal matcher robustness into main
5dc1257 2026-06-28 Merge add-side rework Phase 1 (F1 classifier) into main
3baf277 2026-06-28 Merge add-side rework Phase 3 into main
5ccc3d7 2026-06-28 Merge add-side rework Phase 4 into main
5578a05 2026-06-28 Merge create-entry cold-open into main
37a3be5 2026-06-29 Merge door-2 engine seam into main
0b2c232 2026-06-29 Merge door-3 engine seam into main
d32c99b 2026-06-29 Merge commit step-up enrichment into main
a90aee8 2026-06-30 Merge CR-2026-120: actor-kind read contract + commit/discard gate
fe0ffc4 2026-06-30 Merge CR-2026-127: addressable held-tray grammar
fe6edc9 2026-07-01 Merge CR-2026-128 — retract boundary (Finding 1b): human-authority retract + forget-me/delegation propose→confirm
2abcfd1 2026-07-01 Merge CR-2026-129 — recall truthfulness (Finding 3): server-compose recall_personal + delegation-grant ack
c57c3ad 2026-07-01 Merge CR-2026-131 — upload turn persistence
1afc723 2026-07-02 Merge CR-2026-130 — upload content reaches Memory
2632037 2026-07-02 Merge CR-2026-132 — folder upload: structure preservation (engine)
7f84f10 2026-07-02 Merge CR-2026-133 — upload interpretation: formats, summarization (engine)
f9cf51f 2026-07-02 Merge CR-2026-135 — brief file and image descriptions (engine)
766f21c 2026-07-02 Merge CR-2026-136 — persist full upload description in the Companion turn (engine)
69c8d8d 2026-07-03 Merge CR-2026-137 — locate and list files by request (engine)
5f1d54c 2026-07-03 Merge CR-2026-138 — persist structured list data; pin classifier temperature (engine)
0002335 2026-07-03 Merge CR-2026-140 — thread source_mode through to the upload wire response (engine)
54489a1 2026-07-03 Merge CR-2026-141 — upload result card survives reload (engine)
fa4d308 2026-07-03 Merge CR-2026-142 — hard_delete_engagement must not delete a principal's account
d02f5a0 2026-07-03 Merge fix — duplicate description in upload chat bubble
542e09c 2026-07-04 Merge CR-2026-143 — expose original_filename on AssertionResponse (engine)
5e9c857 2026-07-04 Merge CR-2026-145 — correction-recognition, propose-and-confirm (engine)
7f01b7b 2026-07-06 Merge CR-2026-146 — retain audio for live-dictation voice captures (engine)
0dfe1ac 2026-07-06 Merge CR-2026-146 v0.7 — retain recordings on non-assertion-creating turns (engine)
030b9b0 2026-07-06 Merge CR-2026-147 (Finding 2) — accurate image-capability line in persona (engine)
ea29a79 2026-07-06 Merge CR-2026-148 — record a companion turn on discard, so it's not stale (engine)
bf18fe7 2026-07-08 Merge CR-2026-149 — fix missing now= argument in totp_rotate_confirm_route (engine)
a971c60 2026-07-08 Merge CR-2026-151 — recognize "dismiss" as a discard_held trigger word (engine)
eee71ff 2026-07-08 Merge R1 fix — deterministic save-offer number carry-forward (held-tray referent-tracking)
4fe7541 2026-07-08 Merge R2 Problem 2 fix — correction-matcher drift (original-content anchor)
cc21759 2026-07-19 Merge stage-3-v0_25-content: land leave-behind content v0.23 -> v0.25 (Stage 3 Item 6)
ea858b3 2026-07-19 Merge Stage 3 (representatives perimeter) into main
79262c5 2026-07-19 Merge Item 7a into main: standing-invitation claim_url (engine)
355fe7a 2026-07-28 Merge CR-2026-154 into main: graph hygiene, Stage 1 (engine)
7ba761e 2026-07-28 Merge CR-2026-155 into main: graph Stage 2, forward walk / dependents (engine)
c4014d6 2026-07-30 Merge CR-2026-158 into main: Memory Registry Completeness
| Date | Tag |
|---|---|
| 2026-06-10 | companion-orientation-discovery-v0_1 |
| 2026-06-10 | companion-orientation-discovery-v0_2 |
| 2026-06-11 | companion-orientation-discovery-v0_3 |
| 2026-06-11 | personal-recall-v0_1 |
| 2026-07-28 | graph-hygiene-v0_1 |
| 2026-07-28 | graph-stage-2-v0_1 |
| 2026-07-30 | registry-completeness-v0_1 |
Notable gap: no engine tag between personal-recall-v0_1 (2026-06-11) and graph-hygiene-v0_1 (2026-07-28) — 47 days and roughly 30 merges (CR-2026-110 through CR-2026-153, plus the Stage-3/Item-7a work) landed untagged. This is consistent with, and gives quantitative shape to, the v0.75 residue's observation that the window "carries multiple landed CRs" absorbed nowhere.
loomworks (Operator Layer): commit and merge history, windoworigin/main in window: 114.99f7f64 (2026-07-19) — unchanged since the v0.75 residue was filed; OL has had no further work this window beyond what v0.75 already names.
60226ce 2026-06-02 Merge: activity-ribbon idle gate + header-anchored overlay, and §F comment fix
f1d8fd1 2026-06-02 Merge: re-anchor activity ribbon to transcript top + 2-line clamp
bafdb07 2026-06-24 Merge CR-2026-121 — Companion Human Commit Affordance
abc6eb2 2026-06-27 Merge CR-2 frontend (load-more + page size; engagements + roomless deferred)
132296f 2026-06-28 Merge create-conversation opening turn into main
3f2fca8 2026-06-28 Merge Companion-surface arc into main — CR-2026-125 focus, dev-env fixes, Companion surface (mockups 1-4), list-loading CR-2, voice panel + timestamps, add-side rework, mobile Companion, create-restore, seed viewer (36 commits, all previously on origin/feat-companion-surface)
807ef8e 2026-06-29 Merge door-2 surface into main
b107290 2026-06-29 Merge door-3 surface into main
fa3268d 2026-06-29 Merge commit ceremony into main (passkey step-up, all three doors)
d0cae54 2026-06-30 Merge CR-2026-127: addressable held-tray grammar (Operator Layer)
4566233 2026-07-02 Merge CR-2026-130 — upload content reaches Memory (Operator Layer)
3526385 2026-07-02 Merge CR-2026-132 — folder upload: restore button + structure preservation (OL)
cb8a11a 2026-07-02 Merge CR-2026-133 — batch-fallback consolidation (OL)
5311dca 2026-07-02 Merge CR-2026-134 — View source on committed assertions (OL)
443c950 2026-07-03 Merge CR-2026-137 — locate and list files by request (OL)
3ec8aeb 2026-07-03 Merge CR-2026-138 — persist structured list data (OL)
6e9c49a 2026-07-03 Merge CR-2026-139 — file type on Memory entries (OL)
342b9bc 2026-07-03 Merge CR-2026-140 — file type and View on chat upload bubble (OL)
2acf321 2026-07-03 Merge CR-2026-141 — upload result card survives reload (OL)
9938628 2026-07-04 Merge CR-2026-143 — specific file format alongside the type label (OL)
2a320fd 2026-07-05 Merge CR-2026-144 — Move Assertion to Another Engagement (OL)
86e070e 2026-07-06 Merge CR-2026-146 — retain audio for live-dictation voice captures (OL)
3c43adb 2026-07-06 Merge CR-2026-146 v0.7 — retain recordings on non-assertion-creating turns (OL)
8adade6 2026-07-06 Merge CR-2026-147 (Finding 1) — preserve line breaks in chat bubbles (OL)
fa6994d 2026-07-19 Merge Stage 3 (representatives perimeter) into main
99f7f64 2026-07-19 Merge Item 7a into main: /claim standing→credit fall-through + admin claim_url
| Date | Tag |
|---|---|
| 2026-06-10 | companion-orientation-discovery-v0_1 |
| 2026-06-28 | add-side-rework-ol-v0_1 |
Same shape as the engine: nothing tagged between 2026-06-28 and the window's end (2026-07-19's Item 7a / Stage 3 merges are untagged).
loomworks-record in window, by path
Method: git log --diff-filter=A --name-only per directory, window-bounded, deduplicated. Both .md and .html siblings counted where present (the record's standing HTML-companion discipline).
Scale: ~460 files added across the directories below. The CR sub-arc cr-2026-152-example-generator-sales-perspective-spike alone accounts for 26 versioned files (v0.1–v0.26) — a single fast-iterating spike, not 26 distinct CRs.
change-requests/ (highest density — 200 files)Numbered CRs filed or versioned in window: CR-2026-098 (v0.2, v0.3), 101, 102, 103 (v0.1–v0.3), 104, 105 (v0.1–v0.2), 106 (v0.1–v0.4), 107 (v0.1–v0.4), 108 (v0.1–v0.2), 109 (v0.1–v0.7), 110 (v0.1–v0.7), 111 (v0.1–v0.3), 112 (v0.1–v0.2), 113 (v0.1–v0.2), 114, 115 (v0.1–v0.2), 116 (v0.2–v0.3), 120, 122 (two docs — held-tray grammar + conversational fidelity), 123, 124, 125, 126, 128, 129 (v0.1–v0.2), 130 (v0.1–v0.2), 131, 132, 133, 134, 135, 136, 137, 138, 139, 140, 141, 142, 143, 144 (v0.1–v0.2), 145, 146 (v0.1–v0.7 — seven versions, the window's fastest-iterating numbered CR after 152), 147, 148, 149, 150, 151, 152 (v0.1–v0.26), 153, 154, 155 (v0.1–v0.2), 157, 158 (v0.1–v0.2).
Un-numbered / named CRs: composer-placement-and-message-order (v0.1–v0.2), cr-companion-actor-serialization-fix, cr-create-commit-ceremony, cr-create-conversation-opening-turn, cr-create-entry-cold-open, cr-create-stage-door-2, cr-create-stage-door-3, cr-create-stage-polish, cr-engine-api-boundary-closure, cr-inbound-seam-minimal-slice, cr-mobile-companion-surface, cr-reply-source-legibility, cr-restore-engagement-creation-affordance, cr-seed-editor, cr-seed-viewer, loomworks-cr-add-side-rework, loomworks-example-generator-cr (v0.1–v0.3) + its scoping notes (v0.2–v0.3) + foundation draft, loomworks-list-loading-cr-1-engine-cursor-contract (v0.2–v0.3), loomworks-list-loading-cr-2-frontend-load-more (v0.2–v0.5), loomworks-me-passkeys-endpoints-cr, loomworks-me-security-recovery-codes-cr, loomworks-ol-security-settings-surface-cr, loomworks-signin-email-conformance-cr, loomworks-stele-cr-c-scoping-note.
phase-crs/ (1 file — this directory is now sparsely used; most CR/implementation-note pairs live in change-requests/ + completion-records/, distinct from the engine repo's own docs/phase-crs/)phase-crs/phase-cr-creation-conversation-memory-pathway-v0_1.mdscoping-notes/ (43 files)
loomworks-api-documentation-phase-5-scoping-note-v0_1, loomworks-api-documentation-scoping-note-v0_1, loomworks-c5-scoping-note-domain-reference-model-v0_1, loomworks-command-settings-discoverability-scoping-note-v0_1, loomworks-companion-orientation-discovery-scoping-note-v0_1/v0_2, loomworks-companion-surface-scoping-note-v0_2, loomworks-companion-truthfulness-fix-scoping-note-v0_1, loomworks-conversation-search-scoping-note-v0_1, loomworks-conversational-fidelity-scoping-note-v0_1, loomworks-create-stage-door-2-scoping-note-v0_1, loomworks-create-stage-door-3-scoping-note-v0_1, loomworks-create-stage-three-doors-scoping-note-v0_1, loomworks-creation-conversation-memory-pathway-scoping-note-v0_2, loomworks-current-engagement-spine-scoping-note-v0_1/v0_2 (+ plain-v0_2), loomworks-folder-upload-scoping-note-v0_1, loomworks-graph-hygiene-cr-scoping-note-v0_1, loomworks-graph-stage-2-cr-scoping-note-v0_1, loomworks-in-engagement-commit-affordance-scoping-note-v0_1, loomworks-level-c-kms-infrastructure-scoping-note-v0_1, loomworks-list-loading-scoping-note-v0_1, loomworks-mobile-companion-surface-scoping-note-v0_1, loomworks-navigation-graph-scoping-note-v0_1, loomworks-ogilvy-writing-audit-seed-voice-scoping-note-v0_2, loomworks-ol-security-surface-scoping-note-v0_1, loomworks-operator-tools-menu-scoping-note-v0_1/v0_2/v0_3, loomworks-ova-reach-enforcement-scoping-note-v0_1, loomworks-personal-recall-scoping-note-v0_1, loomworks-remember-about-me-confirmation-loop-scoping-note-v0_1, loomworks-restore-engagement-creation-affordance-scoping-note-v0_1, loomworks-role-vocabulary-reconciliation-scoping-note-v0_1, loomworks-scoping-note-inbound-seam-minimal-slice-v0_1/v0_2, loomworks-seed-viewer-scoping-note-v0_1, loomworks-session-scoped-list-refusal-scoping-note-stub-v0_1, loomworks-stele-extraction-scoping-note-v0_1, loomworks-stele-integration-design-v0_1/v0_2, loomworks-stele-phase-3-scoping-note-v0_1, loomworks-stele-phase-5-scoping-note-v0_1, loomworks-topic-filtered-recall-scoping-note-v0_1, loomworks-voice-entry-confirm-back-simplification-scoping-note-v0_1.
investigations/ (99 files, including a competitive-positioning/ sub-area)
Full path list in the working grep output; headline groupings: competitive-positioning (Cognisee, Hebbia ×3, C5 external-reference-targets, marketing-site venture-pair note) — 7 files; security/positioning (dunin7-security-positioning-investigation, dunin7-governed-agent-construction-investigation v0.1/v0.2, loomworks-data-at-rest-protection-investigation-v0_2, loomworks-engagement-content-confidentiality-investigation-v0_1); assertion/graph (finding-retracted-assertions-visibility-v0_1, finding-r1-r2-held-tray-v0_2/v0_3, loomworks-finding-1b-retract-boundary-scoping-v0_1, loomworks-frictionless-held-inference-gap-v0_1, loomworks-graph-memory-field-scan-v0_1, loomworks-graph-role-elaboration-v0_1, loomworks-provenance-threads-finding-one-edge-one-end-v0_2); engine boundary/API (loomworks-engine-api-boundary-inspection-findings-v0_1, loomworks-engine-api-parity-audit-v0_1, loomworks-engine-boundary-inventory-v0_1, loomworks-engine-standalone-api-walk-v0_1, finding-playground-dev-stele-migration-drift-v0_1, finding-session-resolution-test-failure-v0_1); recall/answering (see §7 below); seed/creation (loomworks-seed-creation-engine-contract-v0_1, loomworks-seed-creation-mechanism-map-v0_1, loomworks-seed-creation-three-paths-deep-dive-v0_1, loomworks-seed-model-grounding-inspection-v0_1, loomworks-title-review-at-induction-design-v0_1); upload pathway (loomworks-upload-pathway-ground-truth-v0_1, loomworks-upload-vision-conversion-bug-diagnosis-v0_1/v0_2); OKF/domain concepts (loomworks-okf-comparison-investigation-v0_1, loomworks-okf-positioning-and-use-cases-v0_1, loomworks-okf-use-case-legacy-estate-v0_1, loomworks-okf-use-case-regulatory-restatement-v0_1, loomworks-memory-sourcing-okf-findings-fold-in-v0_1, loomworks-indigenous-knowledge-opportunity-v0_1, loomworks-gaussian-splat-investigation-v0_1); plus loomworks-b0dc30b-parked-state-resolution-v0_1, loomworks-boundaries-arc-opening-thesis-v0_1, loomworks-companion-bin3-capability-findings-v0_1, loomworks-companion-skill-customization-verification-response-v0_1, loomworks-companion-surface-coherence-findings-v0_1, loomworks-create-flow-and-old-surface-omissions-inspection-v0_1, loomworks-finding-content-to-engagement-routing-v0_1, loomworks-foray-operational-visibility-investigation-v0_1, loomworks-investigation-bidirectional-governed-integration-substrate-v0_1, loomworks-investigation-companion-source-provider-abstraction-v0_1, loomworks-legacy-systems-companion-concept-v0_2, loomworks-memory-disclosure-layer-investigation-v0_1, loomworks-operator-tools-menu-pre-cr-verification-investigation-v0_1, loomworks-reach-enforcement-grantha-correction-note-v0_1, loomworks-semantic-meaning-foundation-v0_1/v0_2/v0_3, loomworks-stele-agentic-identity-investigation-v0_1, loomworks-stele-principal-nature-neutrality-investigation-v0_1, loomworks-stele-third-party-readiness-investigation-v0_1, loomworks-test-stele-router-mount-characterization-v0_1, memory-room-conformance-bar-v0_2, object-store-outage-status-code-memo-v0_1, clarification-card-findings-v0_1.
completion-records/ (10 files): cr-2026-158-checkpoint-a-report-v0_1 (this session), loomworks-add-side-rework-completion-record-v0_1, loomworks-dunin7-perimeter-stage-1-completion-report-v0_1, loomworks-graph-hygiene-completion-record-v0_1, loomworks-stage-2-completion-report-v0_1, loomworks-status-check-completion-record-v0_1/v0_2/v0_3.inspection-briefs/ (17 files, includes the walk-audit trio): loomworks-agent-construction-spec-verification-v0_1, loomworks-creation-conversation-memory-pathway-step-0-inspection-brief-v0_1, loomworks-graph-hygiene-step-0-inspection-report-v0_1, loomworks-graph-stage-2-step-0-inspection-brief-v0_1/-report-v0_1, loomworks-list-loading-cr-1-step0perstep-report-v0_1, loomworks-list-loading-cr-2-build-checkpoint-v0_1/-step0-report-v0_1, loomworks-list-loading-step-0-report-v0_1, loomworks-ova-reach-enforcement-step-0-inspection-brief-v0_1/-report-v0_1, loomworks-ova-slice-1-cr-preflight-report-v0_1, loomworks-topic-filtered-recall-step-0-inspection-brief-v0_1/-report-v0_1, loomworks-walk-audit-cc-brief-v0_1, loomworks-walk-audit-operator-checklist-v0_1, loomworks-walk-audit-report-v0_1.cr-drafting-handoffs/ (5 files): loomworks-cr-2026-123-step-4-redraft-handoff-v0_1, loomworks-creation-conversation-memory-pathway-cr-drafting-handoff-v0_1, loomworks-graph-hygiene-cr-drafting-handoff-v0_1, loomworks-key-custody-cr-drafting-handoff-v0_1, loomworks-list-loading-cr-drafting-handoff-v0_1, loomworks-ova-slice-1-cr-drafting-handoff-v0_1.cr-execution-plans/ (10 files): loomworks-c2-discipline-in-process-brain-plan-v0_1…v0_5, loomworks-cr-2026-097-verification-then-merge-plan-v0_1/v0_2, loomworks-cr-2026-125-companion-surface-phase1-step0-findings-v0_1, loomworks-step-up-4b-engagement-override-plan-v0_1, loomworks-step-up-authentication-mechanism-plan-v0_1…v0_4, loomworks-thin-seed-fix-plan-v0_1.session-handoffs/ (13 files, window-filed): handoff-v1_0, loomworks-c5-seed-amendment-session-handoff-v0_1, loomworks-companion-build-session-handoff-2026-07-29-v0_2, loomworks-dunin7-perimeter-session-handoff-v0_1…v0_4, loomworks-ova-reach-enforcement-scoping-handoff-v0_1, loomworks-recovery-completeness-handoff-v0_1, loomworks-session-handoff-2026-06-01-engagement-creation-walk-v0_1, loomworks-session-handoff-2026-06-05-c5-arc-v0_1, loomworks-session-handoff-2026-06-05-seed-v0_11-v0_1, loomworks-session-handoff-2026-06-25-v0_1, loomworks-session-handoff-stele-brief-v0_4-authoring-v0_1, loomworks-stage-3-scoping-handoff-v0_1/v0_2.
From change-requests/cr-2026-158-memory-registry-completeness-v0_2.md §1 and §2a (Step 0, run 2026-07-29 against engine 1aac815):
memory/registry.py: discovery_to_seed_extracted, engagement_created_from_assistance, grant_request_received, jurisdiction_routing_decided, manual_content_contributed, reconciliation_proposal, seed_committed_from_brief, upload_event_received. Registrations stopped at Phase 37; every event family added since (the door-3 extract path, the doors-1/2 creation paths, the upload pipeline, four other writers) is unregistered.1aac815: 35 declared object_type literals, 27 registered, the 8 above unregistered; registered-but-never-declared: zero.upload_event_received is the common case — 80 events across 4 engagements — meaning any engagement that has ever received an upload is in the affected class.1aac815 — no matching commit or branch; _alpha_authorizer_stub present and called at credit/cross_engagement_memory.py:65,120; no credential or non-member code in tree. Its event types are out of CR-158's scope.main at c4014d6/a317051, tag registry-completeness-v0_1, pushed, and deployed via launchd restart). The handoff's citation of this sweep as absorption-pass evidence is now doubly apt: it is both a diagnostic of what the window's writers did (eight new event-kind classes across five phases — 48, 50, 52, 53, 54, 55, 58, 59) and a closed, shippable example of what "properly absorbing" one piece of the window's residue looks like.What they are. Not yet-existing artifacts — owed corrections, named twice outside the manifest itself:
> standing-notes/dunin7-master-build-sequence-v0_1.md, item 2.1: "Manifest absorption pass — the June→July window (v0.75 residue), citing CR-158's sweep; entries-119/120 supersession markers ride along."
> session-handoffs/loomworks-companion-build-session-handoff-2026-07-29-v0_2.md, build-sequence table: "Manifest absorption pass — the June→July window (v0.75 residue); cite CR-158's Step 0 sweep as evidence; also carries the entries-119/120 supersession markers | Owed | Diagnoses W-5's history; record integrity."
Where they sit. Entries 119 and 120 are current-status-manifest-v0_75.md §3 items (lines 669–703): Entry 119 is the venture-diligence vertical arc (2026-07-28), Entry 120 is the OVA reach-enforcement scoping arc (2026-07-28, same day, later session). Both were filed at v0.73/v0.74 and carried unchanged into v0.75. Neither entry currently carries any [Superseded…] marker — inspected directly; none present. This is unlike the v0.75-era markers already applied elsewhere in the same manifest (header ×2, Entry 113 ×1, Entry 114 ×1, per the amendment-v0.1 splice list), which corrected stale v0.69-era "not merged" language once the OL merge (3f2fca8) made it false.
What state they are in. Outstanding — not yet applied. The build sequence and the session handoff both name them as riders on the manifest absorption pass (B-15), not as independent work. The implication, read against the pattern the v0.75 markers already set: something about Entries 119/120's content is expected to have become stale or partially superseded by the June→July window's actual landed work (the same class of drift the v0.75 residue names generally), and the absorption pass is expected to apply the correction-preserved marker convention to them the way it already did for the header and Entries 113/114. No specific stale claim within 119/120 was identified by this read-only pass — that identification is exactly what the absorption pass itself is for.
Organized by the shape of the touch, not by directory. All items below were filed or landed inside 2026-06-01–2026-07-30.
change-requests/cr-2026-129-recall-truthfulness-v0_1.md, v0_2.md) — merged 2abcfd1 (2026-07-01). Server-composes recall_personal responses and the delegation-grant ack, closing a truthfulness gap in what recall claims happened. Directly named in the v0.75 residue as one of the window's landed-but-unabsorbed CRs.scoping-notes/loomworks-personal-recall-scoping-note-v0_1.md — predates CR-2026-100 (Phase 50, tagged personal-recall-v0_1 2026-06-11, in-window).scoping-notes/loomworks-topic-filtered-recall-scoping-note-v0_1.md + inspection-briefs/loomworks-topic-filtered-recall-step-0-inspection-brief-v0_1.md / -report-v0_1.md — the queued-directions §18.2 subset-recall direction the venture-diligence inspection (Entry 119, V5) and the no-live-recall-demonstration standing rule (current-status-manifest v0.75 §5) both point at as the fix for "recall is wholesale, 50-most-recent, no search index."scoping-notes/loomworks-remember-about-me-confirmation-loop-scoping-note-v0_1.md — personal-memory write path adjacent to recall's read path.scoping-notes/loomworks-conversation-search-scoping-note-v0_1.md — explicitly named-distinct from recall (searches the message stream, not committed assertions) but same failure class (no search index).investigations/loomworks-recordable-facts-and-topic-investigation-v0_1.md — durable-vs-ephemeral facts and whether assertions should carry a topic, feeding both recall and removal-by-subject.investigations/loomworks-ask-your-engagement-investigation-v0_1.md + -plain-language-v0_1.md — the "ask a plain question, get a truthful answer with sources" capability recall and answering both feed.change-requests/cr-2026-154-graph-hygiene-v0_1.md, merged 355fe7a 2026-07-28) — verification-only item confirming AS_CURRENT_STATES = ("held", "committed") in engagement/assertions.py and that all fourteen answer-composing read paths (report E.19) route through it correctly, with an explicit named-exempt list (history reads, at-version reads, seed induction history, state_of_engagement_at_version, state_of_object_at_time, consideration surfacing, relationship reads, the 1a redirect backfill). This is the most directly relevant single item to B-11's diagnosis — it is the engine's own audit of whether a superseded/retracted assertion can be answered-as-current, and it closed "verification-only," meaning the fourteen paths checked out clean at 355fe7a. If B-11's six-note engagement bug reproduces on one of the CR's four exempt paths, or on a fifteenth path the audit didn't enumerate, that is the lead to pull.7ba761e, 2026-07-28) — the dependents read on a retracted/redirected assertion; adjacent to answering correctness for the graph-shaped case.investigations/loomworks-provenance-threads-finding-one-edge-one-end-v0_2.md — the wasDerivedFrom-edge asymmetry finding CR-2026-154 names as filed-not-fixed (CD-1 in its corrections table).fe6edc9, 2026-07-01) — human-authority retract + forget-me/delegation propose→confirm.investigations/finding-retracted-assertions-visibility-v0_1.md and investigations/loomworks-finding-1b-retract-boundary-scoping-v0_1.md — the scoping pair behind CR-2026-128.fe0ffc4, 2026-06-30) and its two follow-on fixes: CR-2026-148 — "record a companion turn on discard, so it's not stale" (merged ea29a79, 2026-07-06) and CR-2026-151 — "recognize 'dismiss' as a discard_held trigger word" (merged a971c60, 2026-07-08). All three touch the held (pre-commit) assertion state machine.investigations/finding-r1-r2-held-tray-v0_2.md / -v0_3.md and investigations/loomworks-frictionless-held-inference-gap-v0_1.md — held-tray robustness findings behind the R1/R2 fixes (merged eee71ff, 4fe7541, both 2026-07-08).a90aee8, 2026-06-30) — who may commit/discard, foundational to lifecycle correctness.2a320fd, 2026-07-05, for the OL half) — a lifecycle operation this report has not traced to an engine-side merge commit in the window; flag for the absorption pass to confirm engine-side landing status, since the OL merge exists but no matching "Merge CR-2026-144" appears in the engine merge list above.5e9c857, 2026-07-04) — the correction-matcher path that revises rather than replaces an assertion; adjacent to lifecycle and to CR-2026-129's truthfulness fix.change-requests/cr-2026-134-view-source-committed-v0_1.md (OL merge 5311dca, 2026-07-02) — "View source on committed assertions," a read-side surface over the same lifecycle state CR-2026-154 audits.Summary for B-11. The window shows sustained, repeated engineering attention to exactly the failure class B-11 is diagnosing — assertion lifecycle correctness feeding answer truthfulness — across at least four numbered CRs (127/128/148/151 on held-state; 120 on the commit/discard gate; 129 on recall truthfulness; 145 on correction handling) plus the CR-2026-154 supersession-aware-answering audit that verified fourteen paths clean. The six-note engagement bug B-11 names either predates this cluster of fixes (worth checking against timestamps once B-11 has the bug's discovery date), reproduces on one of CR-2026-154's four named-exempt paths, or is a fifteenth path the September audit's enumeration missed — CR-2026-154's own exempt-path list is the fastest place to start.
origin/main; record HEAD is 43bb66f.1aac815 → a317051 this session alone (CR-2026-158).current-status-manifest-v0_75.md §3 entries, explicitly scoped as riding along with B-15, not a separate item.DUNIN7 — Done In Seven LLC — Miami, Florida Loomworks June–July inspection report — v0.1 — 2026-07-30 Read-only. No repository writes performed in producing this report.