The engine opened this item itself — you didn't create it.
What this is. A conformance audit of the build against the locked engine-planning design confirmed the divergences below (re-verified against current main) and grouped them into one build-session-sized unit for the lifecycle subsystem.
The memory substrate now recalls, consolidates, rolls up, and reversibly forgets -- and boot renders none of it, leaving a cold session under-oriented and stale hedges in place. A cold-start briefing carries state and the knowledge neighborhood but pulls NO memory recall at step 2, so recent decisions and lessons are absent from orientation and reachable only if the scent fires later. The same missing wire leaves the attention recent_decisions lane a permanently empty bucket that has budget/precedence/trim in the reviewable policy but never surfaces anything, misleading an operator who checks policy against behavior. And boot renders no reversible-forgetting readout though the substrate actively performs it, with boot.py:52 still hedging 'renders only once that substrate exists' -- stale, since the substrate exists; the locked doc requires a readout of what changed with an undo handle per item. A single build session adds the boot-assembled memory-recall element to gather_signals, routes it into the recent_decisions candidate, and adds the reversible-forgetting readout (confirming per the flagged litigation whether it lands in boot or the audit digest under D-209/D-210 before building) while removing the stale hedge.
Findings in this unit:
-
U06: Add a boot-assembled memory-recall element to gather_signals so a cold session arrives with recalled memory in its orientation (step 2).
-
U06: Route that recall into the attention recent_decisions candidate in assemble_candidates so the declared lane (budget/precedence in policy) surfaces real content.
-
U09: Add the reversible-forgetting readout (what changed + an undo handle per item) -- confirm boot vs audit digest against D-209/D-210 first (litigation-flagged) -- and remove the stale 'renders only once that substrate exists' hedge at boot.py:52.
-
Spec authority: systems/lifecycle/boot/README.md step 2, step 3, 'Reversible forgetting' bullet; systems/attention/README.md:49; systems/memory/README.md:25,208-217; decision-log.md D-154 S3, D-209, D-210
-
Quality attributes: Cold-start-readiness, Reversibility, Trustworthiness-for-a-non-engineer
What happens next. A single build session should resolve every item in the checklist above, each fixed to full spec capability (principles §20). The engine opened this item for your review; nothing merges without the protected-branch gate.
More detail.
The engine opened this item itself — you didn't create it.
What this is. A conformance audit of the build against the locked engine-planning design confirmed the divergences below (re-verified against current
main) and grouped them into one build-session-sized unit for the lifecycle subsystem.The memory substrate now recalls, consolidates, rolls up, and reversibly forgets -- and boot renders none of it, leaving a cold session under-oriented and stale hedges in place. A cold-start briefing carries state and the knowledge neighborhood but pulls NO memory recall at step 2, so recent decisions and lessons are absent from orientation and reachable only if the scent fires later. The same missing wire leaves the attention recent_decisions lane a permanently empty bucket that has budget/precedence/trim in the reviewable policy but never surfaces anything, misleading an operator who checks policy against behavior. And boot renders no reversible-forgetting readout though the substrate actively performs it, with boot.py:52 still hedging 'renders only once that substrate exists' -- stale, since the substrate exists; the locked doc requires a readout of what changed with an undo handle per item. A single build session adds the boot-assembled memory-recall element to gather_signals, routes it into the recent_decisions candidate, and adds the reversible-forgetting readout (confirming per the flagged litigation whether it lands in boot or the audit digest under D-209/D-210 before building) while removing the stale hedge.
Findings in this unit:
U06: Add a boot-assembled memory-recall element to gather_signals so a cold session arrives with recalled memory in its orientation (step 2).
U06: Route that recall into the attention recent_decisions candidate in assemble_candidates so the declared lane (budget/precedence in policy) surfaces real content.
U09: Add the reversible-forgetting readout (what changed + an undo handle per item) -- confirm boot vs audit digest against D-209/D-210 first (litigation-flagged) -- and remove the stale 'renders only once that substrate exists' hedge at boot.py:52.
Spec authority: systems/lifecycle/boot/README.md step 2, step 3, 'Reversible forgetting' bullet; systems/attention/README.md:49; systems/memory/README.md:25,208-217; decision-log.md D-154 S3, D-209, D-210
Quality attributes: Cold-start-readiness, Reversibility, Trustworthiness-for-a-non-engineer
What happens next. A single build session should resolve every item in the checklist above, each fixed to full spec capability (principles §20). The engine opened this item for your review; nothing merges without the protected-branch gate.
More detail.