Plain-language summary. retract_assertion removes committed memory and is gated at neither layer — no data-layer actor-kind check, and its HTTP route uses the permissive get_resolved_actor instead of the human-only get_committing_resolved_actor that commit/discard use. A non-human actor (agent or companion) can therefore retract committed knowledge. CC empirically confirmed (rolled back) a companion retracting a committed Goosey assertion.
This is the same bug class as the commit-gate hole CR-2026-120 closed, and more exposed: discard (now gated) is held-only; retract (ungated) removes committed knowledge — the more consequential operation was the less-gated one.
Retract is human-authority. A non-human actor cannot retract committed memory. The Companion may propose a retraction; only the human authorizes it — identical to commit, identical to the seed's Operator-authority principle ("the machine surfaces and signals; the Operator approves").
This was chosen over Option B (a personal-vs-engagement carve-out letting the companion retract personal committed memory) because:
No transitional seam. An interim "gate engagement-retract now, fix personal later" was explicitly rejected — that interim is Option B temporarily, and the no-seam principle holds even to patch a live hole faster. The decision: carry the recorded exposure until 1b closes it fully, rather than introduce a B-shaped state even transiently.
The Companion's "forget about me" feature (_route_forget_about_me, router.py:2477) today builds actor_from_companion and calls retract_assertion directly — the companion retracts committed personal memory on its own authority. That is the same principle-violation the gate closes, so full-A must re-route forget-about-me through human confirmation: the Companion surfaces "remove this from your record?", the human confirms, it retracts.
That confirmation surface is the same confirm-step CR-2026-127 builds for committed-revision (change N on a committed fact → supersession-with-confirm). So 1b reuses 127's machinery rather than duplicating it — which is why 1b sequences after 127.
Note: routing forget-about-me through one confirmation is an improvement, not a regression — permanent erasure of one's own committed memory warrants a confirming beat.
retract_assertion (data layer) and switch its HTTP route from get_resolved_actor to the human-only get_committing_resolved_actor. Mirror CR-2026-120's pattern; reuse NON_HUMAN_ACTOR_KINDS.Until 1b lands, a non-human actor could retract committed engagement or personal memory — gated at neither layer. Must be closed in 1b; must not drift past Room-1 closure.
Bounded: no current automatic path drives a non-human to retract; it requires a deliberately-constructed companion-retract call (as CC's rollback demo did). Recorded here as the oversight.
revise_engagement, add_relationship — ungated but narrow/low-consequence. Note for a later pass.revise_assertion — ungated but output is held (needs its own commit) — acceptable by design.Room 1 closes when all four are done and the room passes bar v0.2 (five checks; monitor-observability held-question carried to the boundaries arc).