Loomworks — Session Handoff — Stele brief v0.4 authoring — v0.1

Version. 0.1 Date. 2026-06-14 Author. Marvin Percival (DUNIN7 Operator), drafting supervised from Claude.ai; push/commit by CC on DUNIN7-M4. Status. Session handoff. Records the v0.4 brief authoring session: what landed on the record, current loomworks-record state, the decisions settled and surfaced, and the next live action (the Phase 1 change request). Markdown primary (technical consumer).

Plain-language summary

This session drafted the Stele body-of-work brief v0.4, amending v0.3 with the standalone-distribution destination, the persons.id FK framing for Phase 1, and a re-sequenced phase plan. It then bumped the current-status manifest to v0.54 to point the live build front at v0.4. Both are committed and pushed to loomworks-record origin/main at 773b6d4. The next live action is the Phase 1 change request, which must surface the FK decision (own-its-own-table vs. host-supplied-contract) explicitly.

1. What landed this session

Two documents, both on loomworks-record origin/main, pushed fast-forward 8f181c2..773b6d4:

| Commit | Document | What it is | |---|---|---| | a7ed9e6 | standing-notes/loomworks-stele-body-of-work-brief-v0_4.md | The current Stele frame. Amends v0.3. v0.3 preserved beside it. | | 773b6d4 | current-status/current-status-manifest-v0_54.md | Pointer bump — live build front now names brief v0.4. Carries v0.53 Phase-0-complete state forward. |

origin/main == local == 773b6d4. Working tree clean except a pre-existing untracked planning/loomworks-companion-path-to-finalized-sequencing-plan-v0_1.md (not this session's, never staged).

2. What v0.4 added to v0.3 (the drafting work)

Settled going in (treated as settled, not re-litigated):

• Stele's terminal destination is a clone-and-run standalone repository — own code, SDK, docs-with-runnable-examples, reference UI template, no residual DUNIN7/Loomworks dependency.
• That destination has a dated externally-visible milestone: the Operator takes Stele to the Claude Code Miami group for independent testing. Bar: a stranger clones it and reaches a passing test run and a working sign-in without the Operator in the room.
• The persons.id FK is the gating design question, landing in Phase 1.
• The full-cryptographic WebAuthn ceremony (deferred from Phase 0) is carried forward to the Miami standalone-UI milestone.

Worked out this session (the open items, now drafted):

• Structural choice — re-sequence, not parallel-track (lean A, Operator-chosen). The standalone deliverables are folded into the phase plan as Phases 6 (de-engine + packaging) and 7 (docs-with-runnable-examples + reference UI template), rather than running a separate packaging track. Reason: the largest standalone workstream (de-engine-ing) is not separable from the phases — each engine thread is cut cleanest by the phase that already touches it. The parallel-track alternative is recorded and set aside in brief §5A per corrections-not-smoothed discipline.
• The standalone work list (§5A): five workstreams — de-engine-ing, packaging (own manifest + own migrations), the SDK surface, docs-with-runnable-examples, the reference UI template — distributed into phases (migrations begin Phase 1, residue cut Phase 6, SDK Phase 6, docs + UI Phase 7).
• The FK decision framed for Phase 1 (§4G, §5B): one question — does standalone Stele ship its own principal table (FKs point inward) or declare persons.id as a host-supplied contract (FKs point at a host table)? Both branches and their standalone consequences stated. Recommendation surfaced, not pre-decided: own-its-own-table (a stranger cloning needs the table their keys depend on to be present). Phase 1's Base/FK decision is this decision.
• WebAuthn ceremony close-point (§4H): closes at the Phase 7 reference UI, which drives a real authenticator end to end — the first point a real UI and real authenticator are both in the loop.

3. Current record state (orientation pair after this session)

• Seed: candidate-seeds/loomworks/loomworks-candidate-seed-v0_12 — canonical, unchanged this session.
• Manifest: current-status/current-status-manifest-v0_54 — current; live build front points at brief v0.4.
• Stele canonical documents (all on origin/main 773b6d4):
• standing-notes/loomworks-stele-body-of-work-brief-v0_4 — current frame; v0.3 preserved beside it.
• scoping-notes/loomworks-stele-integration-design-v0_2 — the host-agnostic API contract. Note carried in the manifest: brief v0.4 §4G/§5B pulls the integration design's §5.2 identity/account physical-table split forward from service-extraction to Phase 1; the integration design's next version should record this.
• change-requests/cr-2026-103-stele-extraction-phase-0-v0_1 — Phase 0 plan, complete and pushed.
• phases/stele-extraction-phase-0/loomworks-stele-phase-0-completion-record-v0_1 — Phase 0 close, the two boundary corrections, the WebAuthn gap, the Phase 1 handoff.

4. Build-front state (carried from manifest v0.54 / v0.53, unchanged this session)

• Engine origin/main: e4656b4. Stele extraction Phase 0 complete and pushed. stele/ module stood up; recovery.py/webauthn.py/session.py moved as pure renames, 113 importers repointed; isolation harness green; suite 2920/46/0; real-DB sign-in verified.
• Phase 1 is next — moves PersonRow + registry, and now also carries the credential row models (WebauthnCredentialRow, RecoveryCodeRow) and persons/credentials.py (reassigned out of Phase 0). Makes the shared-Base / persons.id FK decision once, for all identity rows together.
• Locked decisions (do not relitigate): (1) contract surface approved incl. white-label hooks tenant_context + locale; (2) sign-up split = approach B (mint-then-onboard with heal path) — Phase 4; (3) move, not duplicate.

5. Next live action — the Phase 1 change request

Fresh session. Draft the Phase 1 CR for the Stele extraction. It must:

• Surface the persons.id FK decision explicitly (brief v0.4 §5B) — present both branches (own-its-own-table / host-supplied-contract), the standalone consequence of each, and the surfaced recommendation (own-table); record which branch the Operator chooses and why (corrections-not-smoothed). Do not default it.
• Carry the Phase 0 pattern: read "zero external callers" as "zero outside the identity set"; count importers against the live tree before moving; bundle each file's move + all its repoints in one commit; verify against database truth, not suite-only.
• Watch the name collision: persons/credentials.py (the person WebAuthn store — moves) vs. the top-level credentials/ package (the KEK home — stays). Do not conflate.
• Honor standing discipline: halt-before-push; per-step commits; Operator go-ahead before irreversible steps; database-truth regression.

First-reads for that session: seed v0.12, manifest v0.54, brief v0.4 (§4G/§5B especially), the Phase 0 completion record (the Phase 1 handoff section), and the integration design v0.2 (the mint↔onboarding seam and §5.2 table-split note).

Open Operator decisions named in brief v0.4 §7 (still open):

1. The persons.id FK decision (own-table vs. host-contract) — resolves in the Phase 1 CR.
2. Confirm the re-sequenced phase plan (standalone deliverables in Phases 6–7; agent build sequenced independently of the Miami date).
3. Set the Miami date against real phase progress.

DUNIN7 — Done In Seven LLC — Miami, Florida Loomworks — Session Handoff — Stele brief v0.4 authoring — v0.1 — 2026-06-14