Version. 0.2 Date. 2026-07-29 Status. Session handoff. Hands from the 2026-07-28/29 sessions to a fresh chat continuing the Companion/Loomworks build. Carries the forward schedule so the Operator orients from one document. Author. Claude.ai. Operator: Marvin Percival. v0.2 (2026-07-29): adds the concurrent-session rule to the standing discipline, prompted by a live collision: two Claude Code sessions wrote to the record concurrently, HEAD moved mid-task, and an amend misfired. v0.1 superseded before filing; no other change. The organizing principle, set by the Operator: complete the Companion and the pipeline so an engagement can be followed from seed through render completion as one unbroken thread. The walk is the acceptance test: the arc is done when the walk runs CLEAN end to end. Only what breaks the walk gets built; everything else stays queued.
loomworks-record/current-status/ — v0.75 as of this handoff; do not assume, find it. Note its §5 absorption-gap residue (June→July engine/OL window unabsorbed).candidate-seeds/loomworks/) — with three v0.13 riders queued: held-gate extension to engagements; "seam is in place" as posture; OVA→GRANTHA substitution (access-control-list language → grant-as-sole-primitive).investigations/loomworks-reach-enforcement-grantha-correction-note-v0_1 — the standing correction: GRANTHA holds the authorization seat (Decision J1); OVA displaced, consumed underneath for blind verification. Any document naming OVA in that seat is historical trajectory.inspection-briefs/loomworks-walk-audit-report-v0_1 — the break list this build works from — plus architecture/dunin7-stack-architecture-and-dependencies-v0_1 for the suite's seats, states, and open seams (S1–S8).
The walk audit (2026-07-28/29) walked one synthetic engagement seed-to-render and found the thread stops, not frays. Stage 1 (Memory) is largely continuous through the Companion. Stages 2–4 are continuous nowhere: the Manifestation and Shaping rooms are hardcoded placeholders (RoomView.tsx:56-66), no Companion intent produces a manifestation, shape, or render, and the Companion-continuity number is 8 (departures to raw mechanics). The provenance backward walk (render → shape → Manifestation → assertion → contributor) is possible only via API — the substrate is genuinely good; no surface exposes a single hop.
Beneath the surfaces, replay is poisoned engine-wide (W-1, class-fixed by CR-2026-158 v0.2, drafted and filed, not yet executed). Eight event types are written but unregistered; six live engagements — including E0005 (19 manifestations, poisoned mid-life, newest permanently stale with no surface saying so), E0060, E0006, E0030 — cannot derive a Manifestation. No user hits the 500 today only because the rooms are placeholders: W-1 and W-9 mask each other, and the completion arc removes the mask — CR-158 must land first.
Recall is doubly barred from demonstration: the §18.2 gap (fifty-item wholesale window, no search index has ever existed) plus W-5 (active wrongness — a six-assertion engagement answered with a superseded value in the wrong lifecycle state). The no-live-recall-demonstration rule stands on both grounds. The ask-your-engagement investigation (filed) charters the fix: truthful → searchable → conversational, with the W-5 diagnosis gated on the June→July absorption pass.
Two CRs are drafted and filed, neither executed: CR-2026-158 v0.2 (registry completeness — the prerequisite) and CR-2026-157 (non-member contribution pathway — grant-shaped, survives the GRANTHA correction whole; unblocks the deal vertical's isolation claim).
Environment reality, learned the hard way: the :8000 engine serves the live app.dunin7.com perimeter, and the production database is named playground_dev — a standing naming trap, filed. All dev work uses the walk-audit pattern: second engine on a spare port, inline env only, fresh database (playground_walkaudit, where the WALK-AUDIT-2026-07-28 engagement stands), dev OL on a port the tunnel does not route, live processes and .env untouched. Deploying any merged engine fix to the serving perimeter is a launchd restart — an Operator act, always named, never assumed.
In order. Items marked ∥ run in parallel with the mainline.
| # | Item | State | What it unblocks | |---|---|---|---| | 0 | Gap-closing commit — the seven skipped files (Hebbia set, ask-your-engagement pairs, marketing alignment note, CR-158 v0.2) from Downloads to the record; destinations settled | Files awaiting the Operator's download step; CC block issued | Record fully current | | 1 | CR-2026-158 execution (v0.2 kickoff, its §8) + the Operator's launchd restart to deploy | Ready today | Replay healed; the six engagements derivable; the Manifestation surface safe to build | | 2 | Operator browser-checklist pass + walk report absorbed into this thread | Checklist in Downloads; restart commands inside it | Confirms or overturns the Lane B source-inspection findings (W-4, W-8, W-11) | | 3 | The completion scoping note — the fresh chat's first drafting task: the full W-list ordered into a bounded arc (Manifestation surface with a staleness indicator from its first version, Shaping surface, Rendering surface, Companion intents for stages 2–4, the provenance backward-walk surface) with the CLEAN walk as acceptance gate | Blocked on items 1–2 | The build itself | | 4 | Completion arc execution — CRs per the scoping note, walk re-run after each | Follows 3 | The unbroken thread; the working-session demo whole | | 5 | CR-2026-157 execution (its §11 kickoff; note at Step 0 that its OVA naming is historical per the correction note) | Ready; can interleave after 1 | Deal-vertical isolation demonstrable; walkthrough v0.4→v0.5 trigger | | 6 | Ask-your-engagement arc — one scoping arc absorbing §18.2 + the W-5 diagnosis + the conversational capability; Step 0 gated on the absorption-pass slice for the recall window | Investigation filed; D-1–D-3 pending | The no-recall-demo rule lifts; the second live sales moment | | ∥ | Ingestion arc — spreadsheet/presentation extraction, two-pathway reconciliation, plus the document-management source class (OKF fold-in D-1) | Findings filed | The data-room claim; wider askable corpus | | ∥ | Manifest absorption pass — the June→July window (v0.75 residue); cite CR-158's Step 0 sweep as evidence; also carries the entries-119/120 supersession markers | Owed | Diagnoses W-5's history; record integrity | | ∥ | Seed v0.13 — the three riders in one amendment event | Queued | Stale-seed drift closed | | ∥ | Workspace-parameter small CR — dashboard routes lack only the parameter | Cheap win | Fund-record cross-deal surface; may shrink the aggregating-scope amendment | | ∥ | Commercial track — marketing site (D-1–D-5), Aldous reply, working-session conversations, FORAY-visibility pilot conversation (its D-3: the conversation can lead the build) | Operator-time, not engine-time | Pipeline while the build runs |
Marketing site D-1–D-5 (scope/positioning line/CTA/claim discipline/copy commission) · FORAY operational visibility D-1–D-3 (Model 1 / adapter arc / pilot conversation) · Ask-your-engagement D-1–D-3 (boundary / sequencing / scoping commission) · OKF fold-in D-1–D-2 (source class — read as accepted 2026-07-29; OKF candidate-direction reaffirmed) · Restatement v0.2 deferred-deliberately · The suite-priority standing document (offered, not commissioned) · The loomworks-seed-transfer-v0_1.zip decision · S1–S6 protocol seams (per the stack diagrams; S1 — OVA's standalone role — costs one conversation).
Two-role (Claude.ai scopes and drafts; CC inspects and executes — CC never drafts CRs or manifest content). Inspect-first; halt-before-push; explicit-path staging always; check git status for staged parallel work before any merge. CR numbers verified across all three locations including stele/change-requests/. Manifest and queued-directions bumps are add-new-file siblings via splice-instruction documents authored on the Claude.ai side. Corrections preserved, never smoothed. HTML primary with Markdown alongside for Operator-facing documents. No live recall demonstration until item 6 lands. Synthetic engagements only for live verification — never E0060, E0007, E0030, E0006. Concurrent-session rule (new, 2026-07-29): multiple Claude Code sessions may write to loomworks-record in the same period — every CC task re-verifies HEAD immediately before each write rather than trusting an earlier reading, never amends or force-updates without first confirming no other session is mid-flight, and prefers append-shaped work (new commits, new sibling files) over history-editing operations, which the record's discipline favors anyway. And when an unfamiliar term appears, search the record before drafting — the GRANTHA lesson, one arc old.
DUNIN7 — Done In Seven LLC — Miami, Florida Loomworks — Companion build continuation — session handoff — v0.2 — 2026-07-29