DUNIN7 · LOOMWORKS · RECORD
record.dunin7.com
Status Current
Path inspection-briefs/loomworks-creation-dead-end-findings-v0_1.md

Loomworks — the create-engagement dead end — live finding, read-only — v0.1

Date. 2026-08-11 · Author. Claude Code (read-only, at context limit). Operator: Marvin Percival, from live testing on app.dunin7.com (engine 64610b4, surface build of 35a49c9). Nothing built.

The defect, mechanism established

The commit handler (_route_commit_project_draft, router.py:2890-2913) requires an existing candidate engagement — it delegates to the Phase 54 commit endpoint, which reads the candidate's latest companion_turn brief and inducts from it. On engagement_id is None it dead-ends with exactly the reply the Operator saw ("I need to know which project draft to commit…").

The Operator's five-question "I'll tell you" exchange ran as ordinary conversation with no engagement context: create_project (which calls draft_engagement and creates the candidate the commit needs) was never fired, so no candidate, no brief, no draft — the answers lived only in chat turns. The draft-creation step is missing from the path as experienced, and the invitation text ("say the word and I'll set it up") was model prose promising a commit the flow never armed — the prose-asserted-outcome family again, here as an unarmed promise about a future action rather than a false claim about a past one.

Unfinished check (context limit): whether "Talk it through" and "Here's my specification" arm the seam (i.e., classify to create_project/the creation intents and create the candidate) or share the defect. That comparison decides the priority — front door broken on one path vs all three. The create-stage-doors scoping notes in this record are the starting point.

The good news, for the record

Under exactly the conditions CR-2026-199 was built for, the reply was honest: no success claim, and a correct report that Shaping was empty and nothing had been drafted or saved. The truthfulness layer held live, in the Operator's own hands.

Filed separately — the scroll defect

On the conversation page, the whole document scrolls rather than the transcript: an arriving reply lands off-screen, the header scrolls away, and there is no auto-scroll to newest — the Operator had to hunt for each response. (Same family as the ONE-WIDTH/layout laws: the scroll container is the page, not the pane.)

Needs from the Operator

Two filings to rule on: the creation dead end (with the three-door check as its first scoping step) and the transcript scroll. Both found live, by the Operator, on current main.


DUNIN7 — Done In Seven LLC — Miami, Florida — v0.1 — 2026-08-11