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

Date. 2026-08-12 · CR. change-requests/cr-2026-207-loomworks-candidate-ceremony-home-v0_1 · Baselines at Step 0. Engine cd91176, surface 7ac3cb2; both clean. Built at. Engine c04afd9, surface b3b01d7 — committed, NOT tagged, NOT pushed, NOT deployed. Halted at Checkpoint A.

Steps 0–4, as run

• Step 1 — one premise better than drafted, one narrowed. state already flows end-to-end (EngagementSummary.state → ProjectSummary.state → the page's resolved engagement) — the projection extension narrowed to viewer_is_creator alone, computed in the list SQL ((e.created_by_person_id = :pid) IS TRUE — a legacy NULL creator reads false for everyone; absent-creator never claims creatorship; the raw id never ships). The double-commit guard exists (the instantiate route's candidate-state check, 409 on non-candidates) and is now pinned by test. Tests observed failing first (2 engine + the surface component's collection failure against the missing component; the 409 pin green both sides by design — it pins existing behavior).
• Step 2 — both halves, as ruled.
• Engine: the persisted step-up sentence recomposed — "Your project is drafted, not yet committed. You can make it official from the project's page whenever you're ready." State + the durable pointer; the imperative gone; request_action unchanged (the in-flow ceremony still mounts live). viewer_is_creator on both list SQL branches, the row unpack, the schema (computed boolean, documented).
• Surface: CandidateCommitBanner — renders the state sentence + the shared CommitCeremony for state === "candidate" && viewerIsCreator, nothing otherwise; derived from state on every render; wired above the in-engagement header; commit → re-resolve. Strings in strings.ts.
• Gates. Engine 3710 passed, 0 failed; ruff clean; mypy at baseline (verdicts read in full). Surface 776 passed, 0 failed (121 files); tsc clean.
• Step 4. Engine bounced onto the built tree (listener verified). Live facts verified for the acceptance walk: E0128 and E0129 both candidate with Marvin as recorded creator — the banner's predicate is true for both the moment the surface deploys. The recomposed sentence and the projection are pinned by unit/HTTP tests.

Deviations, named

1. The banner's on-screen check moves post-deploy (the CR-204/206 precedent, twice accepted): the deployed surface predates the component, and the dev host has no session. Covered pre-gate by the three component tests + the full-suite wiring; Step 5's post-deploy walk is the real acceptance — your E0128 walk, repeated, with the ceremony present.
2. The E0128 live tab still stands, untouched — checked this session, still open at its ceremony. Post-deploy it stops being the only route; per §0.3 it stays open until your walk succeeds from the page.

seed-mutability impact

Kind C — no contact. Checked: a computed membership/creator boolean, a recomposed sentence, a state-derived banner; the instantiate endpoint untouched. A null finding is an entry; recorded either way.

Acceptance-gate status (CR §6)

1. Banner + fences — green (component tests: candidate+creator renders; active and non-creator render nothing).
2. The persisted sentence describes state, names the durable affordance; imperative gone — green (unit-asserted on the composed reply).
3. Double-commit 409 — pinned.
4. Suites green; gates clean. Push runs + redeploy + the Operator's repeated walk: pending the gate.
5. seed-mutability recorded.

Halted. Awaiting GATE A APPROVED — PROCEED for CR-2026-207 before Step 5 (tag cr-2026-207-candidate-ceremony-home, push both, watch both runs, redeploy — then your walk).

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