What this document does. Records three facts that the current-status manifest (v0.51) and prior session memory carry incorrectly, so the next manifest version corrects them. It is a focused correction, not a full manifest rewrite.
What changed. Three facts moved or were found stale: the Companion functional spec version on record main; the status of the A3 founder-authority decision; and the CR-2026-098 A3 blocker.
Decision needed. None. This delta records corrected facts with their sources. Claude Code folds it into manifest v0.52.
In scope. The three corrected facts, each with prior-state, corrected-state, and source.
Out of scope. Any build work. Any change to the seed. The v0.4 reconciliation of the Companion spec §10.3 (queued separately).
The manifest is the first-read orientation document. When it carries a stale fact, the next session inherits it. Three facts drifted; this delta names each with its source so the correction is traceable, per the corrections-preserved-not-smoothed discipline. Prior positions are stated alongside corrected ones — the trajectory is walkable, not overwritten.
Prior recorded state (manifest v0.51 / session memory): Companion functional spec at v0.1, filed 2026-06-11.
Corrected state:
9f90827).96dec68, same commit added queued-directions v0.26). This is what "filed 2026-06-11" actually refers to — the date attached to v0.2, not v0.1.add-companion-functional-spec-v0_3).What went wrong: the prior record conflated v0.1's version number with v0.2's commit date. Two facts to fix, not one — the version (v0.1 → current v0.3) and the date attribution.
Source: Claude Code git-history investigation of loomworks-record, 2026-06-13. git log on the spec filename stem; file-header reads on each version.Prior recorded state (manifest v0.51 / session memory): CR-2026-098 A3 — privilege check on /admin/* credit routes — HALTED pending Operator decision on the authority model. Operator lean recorded as option (b): single shared named authorization dependency. Treated as unsettled.
Corrected state: A3 / the founder-authority model is settled and built.
src/loomworks/authority/founder.py — get/set founder, stored as a singleton in system_config under platform_founder_person_id, bootstrapped out-of-band); a require_founder dependency (src/loomworks/api/deps.py) that 403s any non-founder caller and fails closed when no founder is set; applied to the three /admin/* credit routes (POST /admin/grants, GET /admin/grants, POST /admin/provisioning).7159870 (2026-06-12 23:27), an ancestor of current engine main HEAD — live and gating real routes, with tests. Not scaffolding.Distinct and still pending: operator-mediated account recovery (the seed's recovery mechanism 3 — the operator→person credential-reset action) is not built. CR-2026-101 ruling R4 placed it explicitly out of scope, "a separate later CR built on this dependency." The founder-authority gate is built; the recovery action that would sit on top of it is not.
Source: Claude Code read-only investigation of loomworks-engine, 2026-06-13. CR-2026-101 commit 7159870; file reads of founder.py, deps.py, admin_grants.py; ruling record R1–R4.Prior recorded state (manifest v0.51 / session memory): CR-2026-098 execution blocked on the A3 Operator decision; "A3 Operator/founder authority decision needs to land before execution."
Corrected state: the A3 decision has landed and been built (Correction 2). The A3 blocker on CR-2026-098 is cleared. The founder-authority model CR-2026-098 A3 was waiting on now exists on engine main. CR-2026-098's remaining boundary findings (A1, A2, B1, the folded BUG1 forward-ref fix) no longer wait on an unsettled authority decision.
What this does not assert: it does not assert CR-2026-098 has been executed — only that its A3 blocker is removed. Whether the rest of CR-2026-098 has run, and against which commit, is a current-engine-state fact for Claude Code to confirm when folding this delta into v0.52.
Confirmed 2026-06-13: CR-2026-098 is fully executed and closed on engine main. BUG1, A1, A2, B1 landed at commit 2685103; the A3 dead-route resolution landed at commit e8706ee (both 2026-06-07, both ancestors of engine main HEAD). The founder-authority gate that CR-2026-098 deferred is built via CR-2026-101. No CR-2026-098 follow-up is outstanding; the only open items it named (organization-admin role column, signup throttle) are intentional long-horizon deferrals, not unfinished execution.
The v0.3 spec just merged describes its §10.3 founder prerequisite as not-yet-built — accurate as of its grounding commit (engine 158d4bc, 2026-06-12 15:55), which predates founder.py. CR-2026-101 merged ~7.5 hours later. So v0.3 is correct-at-grounding; the staleness is reality moving forward the same evening, not an authoring error. Reconciling §10.3 against CR-2026-101 belongs in a future spec v0.4, not in this manifest delta. Recorded here only so the next manifest version does not mistake v0.3's §10.3 for current truth.