Loomworks — the ungated chat route around the delegation layer, + the creation-session batch — v0.1

Date. 2026-08-11 · Read-only, from Operator live testing (app.dunin7.com, engine 64610b4). Nothing built. At session context floor — findings established, one check stated as done-by-knowledge rather than fresh read.

1. The bypass — established

E0127's turns (from the record): the ask classified request_draft → the server-composed denial (correct). The suggested sentence — typed lowercase, no period: "you can draft specifications" — classified general_conversation, and the unpinned responder wrote a full specification as chat prose.

• The classification miss: a LIVE RECURRENCE of B-86's dependency, with the composed denial present in history — the exact condition the B-86 deferral named ("unless a live recurrence demands it"). The deferral's own trigger has now fired. Differences from CR-2026-200's passing eye-test: longer preceding history (an ask_about_past_input exchange) and the lowercase/unpunctuated sentence — which the B-81 probes already showed classifying general_conversation (0.85) without framing.
• The finding proper, stated plainly: nothing prevents the responder from producing specification- or artifact-shaped content directly in chat. general_conversation.md forbids triggering operations; CR-2026-199's rules forbid claiming performed actions; the persona constrains state-naming and act-claiming. No layer constrains content production. The delegation layer gates the governed route; the chat channel is an ungated route to the same outcome — refused for lack of authority, served the artifact one turn later.
• The other Tier-1 capabilities: the same bypass exists wherever the artifact is text — a "report" or render content can be written as prose identically. Only binary render files are out of chat's reach; their content is not.
• The reply's tail ("…before you okay it") is the unarmed-promise member again — no okay-flow exists for chat prose; the text is nowhere.

The two caveats, recorded: nothing false entered the record — the chat text is not a Shape, carries no provenance, is not in Memory; and the refusal was accurate about the capability. The defect is that refusing the governed route does not constrain the outcome.

2. The creation-session batch, filed as reported

1. Two of three doors dead-end ("I'll tell you", "Talk it through" → "I need to know which project draft to commit"); "Here's my specification" works end to end through passkey to a committed project. (Answers v0.2's three-door first question: a bug with one working door, not a full outage — but the two conversational doors are broken.)
2. No title derivation on the specification door: engagements named with the truncated "what the work is" text — list, header, focus chip; E0089 shows it, so it predates today.
3. The commit screen's sentence breaks on the same cause ("Commit A short printed handbook that enables… library. with your passkey").
4. The success page after creation is a dead end — no link to the created project.
5. Markdown renders raw in the in-engagement transcript (Purpose as asterisks).
6. The create-engagement composer has no mic; the in-engagement one does.
7. The two chat surfaces order messages oppositely; in-engagement is internally contradictory (newest-first, composer at bottom). OPERATOR RULING, recorded: newest-first with the composer at the TOP is the intended design.
8. The paste textarea on the specification door does not grow; its file chooser is an unstyled browser default.
9. From the prior brief, still standing: the transcript-scroll defect (page scrolls, no auto-scroll to newest).

For the fresh session

Priority order implied by the rulings and findings: the ungated-chat-production question (a policy decision — what MAY the Companion produce as prose — before any mechanism); B-86's deferral trigger has fired (the persist-the-outcome remedy stands ruled and undrafted; whether the classifier change now also rises is the Operator's call); the two dead doors; then the batch.

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