Loomworks — Stage 3 (representatives, content, consequences) — Scoping handoff — v0.1

Version. 0.1 Date. 2026-07-19 Author. Claude.ai, on Operator direction. Status. Scoping handoff. Orients a fresh chat for Stage 3 scoping. Stage 3 does not start building until the entry condition below is met. Reads with. The Stage 2 completion report (loomworks-record/completion-records/, filing pending at drafting time), loomworks-stage-2-build-brief-v0_2, loomworks-dunin7-perimeter-session-handoff-v0_4, CR-2026-152 (v0.26 in the record).

Plain-language summary

Stage 1 built the door. Stage 2 moved the sales generator inside, metered and capped, behind the representative gate. Stage 3 lets people in and improves what they find: provision identities for Aldous, Warwick, and test users; advance the generator content past the v0.23 freeze; and land the consequences of representatives existing — the public marketing generator comes down, representative storage becomes administered, and quota calibration becomes decidable on real data.

Entry condition

Stage 2 closed in the record: retirements executed, the live end-to-end proof through the UI run, the completion report filed and pushed. The fresh chat verifies this against loomworks-record before scoping.

Workstream 1 — People (the core of Stage 3)

Provision representative identities: Aldous (Miami/London), Warwick Halcrow (Sydney), and test users.

The open scoping question, and it is the big one: enrollment. Sign-in is passkey-based; identity is the system UUID; there is no email-based identity or recovery, by seed commitment. Today the only enrolled person is the Operator, enrolled by direct action on the machine. Aldous and Warwick are remote. The fresh chat's first job is a Step-0 inspection: what enrollment paths exist in the engine and Stele v0.4.0 today (invitation flow? add_passkey ceremony reachability? anything from Phase 48's operator sign-in work?), and what the gap is between what exists and "a person in Sydney enrolls a passkey against app.dunin7.com without the Operator's hands on their device." The Stele Phase 7 material (CR-2026-116, the ~100-line add_passkey ceremony lift) is prior art to inspect, not assume.

Representative standing: today a declared list (system_config key dunin7_representative_person_ids). Stage 3 is the named point where this moves to a host_account column — representatives become administered, not declared. Scope the migration and the admin surface (who grants standing, through what UI, with what Operator approval step — Operator-authority applies to standing grants).

Person-tier keys: the sibling resolver's tier 2 means a representative with their own Anthropic key pays their own way; otherwise the system key pays. Decide per person: do Aldous and Warwick ride the system key (simplest; metering attributes anyway) or carry their own? Default recommendation: system key for both at Stage 3 start — cost attribution is what the metering is for, and asking a pilot prospect to bring an API key is friction with no upside.

Workstream 2 — Content (unfreezing v0.23)

• v0.25: sits on cr-2026-152-sales-v0_25-wip (d8a718a) — the seventh landscape section, a new leave-behind budget, reversals of v0.21/v0.22 rules from the second real client run (2026-07-17). First content action: review whether that work is finished or mid-thought, finish it deliberately, and land it into the engine's sales_tools package — the marketing branch is history now; the engine is where content lives. Prompt changes re-run the parity discipline in reverse: hashes update, the design commentary updates with them, and the change is recorded as a content version, not a silent edit.
• v0.26 and decision B: as recorded in CR-2026-152 v0.26 in the record — the fresh chat reads that CR before scoping content work.
• The dropped plain-example fallback: if a lightweight mode is wanted, it gets scoped here deliberately (recorded deviation from Stage 2, decision 1).

Workstream 3 — Consequences of representatives existing

• Marketing generator teardown. Ruled at Stage 2 close: stays up until Stage 3. The trigger is not "Stage 3 starts" but "Aldous and Warwick are enrolled and using the perimeter version" — teardown when the audience has moved, and the marketing Worker's separate Anthropic key is retired with it.
• Quota calibration. Deliberately deferred by Operator ruling until diversified usage data exists. Stage 3 generates that data; the quota ruling is a later Operator decision made on it — likely after Stage 3, not within it. The metering and the loose ceiling (2M tokens/24h) stand until then.
• Onboarding surface. Representatives arriving at app.dunin7.com see the Operator Layer built for the Operator. Scope the minimum: what a representative sees on first sign-in, what they can and cannot reach (only-show-what-is-available already handles the menu), and whether anything Operator-only currently leaks to representative level — a Step-0 inspection item.

Inherited queue (standing items, not Stage 3 blockers)

1. b0dc30b classifier prompt — cherry-pick onto its own branch, add the three contrast-case tests plus the "Set the pH to 6.5" control, land or discard on the result. Resolution note in investigations/.
2. Secrets-hygiene sweep — plists, .dev.vars (that key is still live), permissions audit.
3. Session-scoped-list scoping — /engagements 200-empty vs 401.
4. Node symlink maintenance point — ~/.local/bin/loomworks-node repoint after any nvm upgrade.
5. test_stele_router_mount — harness-only, test-correctness priority.
6. VPS cutover — the standing proper fix for login-dependent availability; the job pattern and launchd services were built to inherit it.

Standing discipline (unchanged)

Two-role: Claude.ai scopes and writes; Claude Code executes, inspects against live code, halts before every push. Fresh chat per work type. Step-0 inspection before build briefs. Corrections preserved, not smoothed. Verification checks fail on missing input and anchor to controls that can disagree — the pattern is now filed methodology with six recorded instances across Stages 1–2.

What the fresh chat does first

1. Verify the Stage 2 close in the record (entry condition).
2. Draft the Stage 3 Step-0 inspection brief: enrollment paths (engine + Stele), representative-standing storage and admin seams, first-sign-in surface at representative level, and the v0.25 WIP branch's finished-or-mid-thought state.
3. Findings return; the Stage 3 build brief drafts from them with the open decisions above put to the Operator.

DUNIN7 — Done In Seven LLC — Miami, Florida Loomworks — Stage 3 scoping handoff — v0_1 — 2026-07-19