CR-2026-203 — Checkpoint A report — v0.1

Date. 2026-08-11 · CR. change-requests/cr-2026-203-loomworks-raw-message-grant-extraction-v0_1 · Baseline confirmed. 64610b4, tree clean at Step 0. Built at. Engine local commit b4a7881 — committed, NOT tagged, NOT pushed. Halted at Checkpoint A per the gate.

Steps 0–4, as run

• Step 0. Baseline 64610b4 confirmed; tree clean.
• Step 1. All §1 premises verified against code. Tests written first and observed failing as assertions (not collection errors — the redirect was stubbed as a pass-through, which IS pre-fix behavior, so all three failures name the pre-fix defect: matcher matched "You can find the render settings…"; grid cell general_conversation + the grant sentence stayed unwired; the ack opened "Got it, held:"). Adjacency mechanism picked: one combined pattern — prefix, at most one intervening non-negating word, word-boundary longest-first action alternation.
• Step 2. The three changes: tightened _GRANT_ADJACENT in delegation/schema.py (applies at every call site, deliberately); redirect_grant_misroute in classifier.py, wired post-redirect_orient_recall_misroute in converse.py (revoke-first via public extract_delegation_revocation); both grant acks reframed tentative — "I think you may have granted me this: “{sentence}” It's held and takes effect only if you confirm it on its held card — if that's not what you meant, say so and nothing happens."
• Step 3. Full suite 3683 passed, 0 failed (68 skipped — the standing skip set). ruff clean. mypy: 537, all baseline-covered. Corpus sweep re-run: battery — every tightened-out class dead (including "you can't render", which now dies at the matcher itself: the apostrophe breaks \byou can\b+whitespace adjacency), genuine and chosen-by-ruling classes intact; 412-turn corpus: exactly one match, E0127's genuine grant — unchanged.
• Step 4 — eye-test, observed live. Engine bounced (old PID 7538 → new 17812, start 20:57:20, listener verified). In E0121, with prior July history present and in-project context — the deterministic-misroute condition — typed E0127's sentence verbatim (you can draft specifications, lowercase, unpunctuated). The reply was the tentative server-composed ack, word for word. Forensics captured before teardown: companion turn classified_intent = remember_about_me (the redirect fired); delegation held in the personal engagement — produce_specification, scope [E0121], per_action, state held. The held card rendered readably ("Held 33 … in the project “CR-2026-146-v0.7 Browser Verify”, asking you each time").

Deviations from the CR, named

1. Eye-test venue: Marvin + E0121, not Marvin-Test2 + a dedicated throwaway. The browser session was signed in as the primary Operator, and signing in as Test2 requires the passkey ceremony only the Operator can perform. E0121 is the existing browser-verify test engagement. Full teardown ran: held delegation dismissed through its own lifecycle (card's Dismiss; state now discarded — no row deletion in the memory substrate), both eye-test turns deleted (E0121 recent-turn count 0), browser tab closed.
2. current_engagement_id capture: my visits moved Marvin's focus pointer to E0030; restored to E0127 (the night session's last venue) — recorded here because the pre-visit value was not captured first; if the Operator's focus was elsewhere, say so and I'll set it.

seed-mutability impact

Kind C — no contact. Checked: extract_delegation_grant reads the Operator's message text only; redirect_grant_misroute is pure over (intent, message); the ack composes from the parsed grant plus the engagement row title via render_delegation_sentence — title is seed-derived at creation but read from the engagement row here (seed-adjacent is not seed-dependent; the ShapeEvent.seed_version_at_production worked example applies). Null finding recorded as an entry.

Acceptance-gate status (CR §6)

1. Ten re-measurement cells wired via pure-function fence — green (test_redirect_grid_all_cells_wired + tightened classes never redirect).
2. Battery classes per §3 — green, ruling named in the test comments.
3. Revoke-first — green (three dual-match sentences pinned unredirected).
4. Tentative ack, CR-200 suite — green (23/23 across both files).
5. Corpus: one genuine historical match, no new captures — confirmed.
6. Eye-test observed live — done; suite zero failures; both gates clean. Push run: pending the gate (nothing tagged or pushed).
7. seed-mutability — recorded above.

Halted. Awaiting GATE A APPROVED — PROCEED for CR-2026-203 before Step 5 (tag cr-2026-203-raw-message-grant-extraction, push, watch the run).

DUNIN7 — Done In Seven LLC — Miami, Florida — CR-2026-203 Checkpoint A — v0.1 — 2026-08-11