Version. 0.14
Date. 2026-08-03
Status of this document. The single guide we work to: everything we are building, in order, with its current status. This is the one page the Operator reads at each sitting. Charter v0.1 ratified 2026-07-30; autonomous regime in effect. Day-to-day status also lives in current-status/dunin7-status-brief, which carries the decision queue.
Author. Claude.ai; v0.3–v0.4 and v0.10 by Claude Code; the rest by Claude.ai.
Changes from v0.13. The carried block was stale in three ways and had not been re-read since v0.12. It said "five new items" where there are six, B-35 to B-40; "all small" where two of the six are decisions to scope rather than builds; and "surfaced by the four builds" where one came out of B-25's work rather than a room. Carried text reads as already-checked, which is how it escaped the sweep that caught the deployment count. (v0.13 was drafted and never filed.)
Changes from v0.12, re-checked rather than carried. One count corrected. v0.12 said "six change requests are merged" above a table listing five. Six is the count of merges, not of change requests — CR-2026-162 spans both repositories. The document's own opening said "six merges" correctly, so it stated both. (v0.12 was drafted and never filed.)
Changes from v0.11, re-checked. Five items closed — B-5, B-6, B-7, B-25 and B-28. The four-room model is complete: Memory, Manifestation, Shaping and Rendering all exist. Six new items — B-35 to B-40 — surfaced by the work just closed. Four are small builds; two are decisions to scope. And one thing has been waiting on you longer than it should: six merges are built, tested and not live.
A dating correction. Versions v0.9 through v0.11 carry the date 2026-08-01. The work they describe ran through 2026-08-03, and the drafting session was propagating a stale date rather than reading it. Nothing in the content changes; the timestamps in those headers are wrong and are recorded here rather than edited in place.
It is written for you first. Every item has a plain-English line saying what it is and why it matters. Technical cross-references sit at the end of each line for the sessions; you can ignore them.
It updates as we go. The responsible session saves the next version with the change made and the date on it — old versions stay as history. The highest-numbered version is always the truth — and once a series passes nine, sort the versions as numbers, not as text, or v0.10 hides between v0.1 and v0.2.
The statuses, in plain terms: READY — a session can start it today · IN PROGRESS — a session is on it now · NEEDS YOU: decision — waiting on an answer · NEEDS YOU: act — waiting on something only you can physically do · WAITING — queued behind an earlier item · DONE — finished, filed, verified · PARKED — deliberately set aside.
The finish line, in one sentence: the full live demonstration works with no excuses — a firm's own document becomes a working engagement, information flows in, the summary view appears, a finished report comes out, a question gets a truthful answer with its sources shown, and an outsider can contribute without seeing anything else.
This is the milestone the last three days were for. The seed names four rooms and until this week two of them were placeholders that lied about your data. All four now exist, and each carries the same rule: a room says only what a completed read supports.
| Room | What it does | Built | |---|---|---| | Memory | Accumulates what is contributed, with provenance | Earlier | | Manifestation | Organizes Memory at a moment in time | B-5 | | Shaping | Arranges organized knowledge for a particular reader | B-6 | | Rendering | Produces the finished artifact, or the specification for one | B-7 |
Three rooms now refuse to say something they cannot support, and each refusal was a defect caught before it shipped:
B-1 to B-4. DONE (2026-07-30 to 07-31).
B-5. The Manifestation screen. DONE. (CR-2026-160; loomworks 7e81e30, tag manifestation-room-v0_1.)
B-6. The Shaping screen. DONE. The first room where pressing something here makes work appear elsewhere: confirming a Shape asks for renders to be produced. So the control names what it will produce before you press it — by name, never by count, because the engine may skip a type it has nothing registered to produce and does not say which. (CR-2026-163; loomworks f477c87, tag shaping-room-v0_1.)
B-7. The Rendering flow, end to end. DONE. Download was a wire, not a build — the engine had served the route all along and the surface had never called it. (CR-2026-162; loomworks 50252e1, tag render-flow-v0_1.)
B-8. Teach the Companion the last three rooms. READY — unblocked. All three rooms it needs to know about now exist. (Change request D. First Step 0 item: does a vaguely-worded request skip the authority check entirely?)
B-9. The "show me where this came from" walk. READY — and this is the next big one. Click any statement in a finished report and walk backward to the person who said it. Every blocker is gone: the version-pinned lookup existed all along, the fabricated provenance field is fixed, and authorship is now true. (Change request E. Needs its own Step 0.)
B-10. Outside contributors, safely. READY. (CR-2026-157, filed, not executed.)
B-11. Make answers truthful. READY. The answer isn't wrong, it's unstable — the same question three times gave correct, then a false confession of fabrication, then correct with its source cited.
B-12. Make the record searchable. WAITING on B-11. The biggest single piece of engineering on this list. May merge with B-11.
B-13. Ask your engagement. WAITING on B-12.
B-14. Read spreadsheets and slide decks. READY (independent).
B-15. DONE. B-16. Update the foundation document. READY to draft · NEEDS YOU: act (read it first). (Seed v0.13.)
B-17. The portfolio filter. READY. One parameter. B-18. File the four protocol requirements. READY. B-19. Keep this list alive. IN PROGRESS (this document).
B-25. The record writes that aren't true. DONE. Eleven places where the system wrote something plausible and wrong into the permanent record, nine of them invisible from any screen. Two turned out not to be defects at all — the engine's own definitions said so — and one would have been actively harmful to fix: collapsing two actor kinds would have made the Companion's own draft committable as a human act. (CR-2026-161; engine a6a3ed6, tag authorship-truth-v0_1.)
B-26. Correct the record about door 3. READY (small).
B-27. DONE — it was already fixed.
B-28. Stop losing contributed documents. DONE. Two type declarations disagreed with what the system actually emits. Two, not four — widening the other two would have declared a value that path cannot produce, which is half of what caused the defect in the first place. (CR-2026-162; engine ffc29af, tag discovery-source-mode-v0_1.)
B-29. The provenance field that was fabricated everywhere. DONE. (CR-2026-159; engine e106917, tag provenance-seam-v0_1.)
B-30. The trap that caused B-27. READY — small. Never repaired; only the broken door was removed. The test suite cannot see it.
B-31. The post-admission lifecycle investigation. READY to open. An investigation arc, not a build.
B-32. The re-derive button on the Manifestation screen. READY — small. The screen tells you when your record has moved on since the summary was built and gives you no way to rebuild it. A button you press, because rebuilding costs credits and changes the record.
B-33. The engine's one broken test. READY — small. Nobody can say "the tests pass" — only "they pass except that one," which is how a second failure hides.
B-34. The surface's twelve warnings. READY — small. Same problem, other side: no failures, but the run still ends in an error state.
B-35. A missing key looks like a crash. READY — new, small. When the document-reading service isn't configured, the system returns an internal error instead of "temporarily unavailable" — unlike its two siblings, which get it right. Found only because a live check was run; no test covers it.
B-36. A way to retire a render. READY — new, small. The engine can retire a render and the route exists, but nothing on screen offers it. This is how you say which document is superseded — the judgement the system correctly refuses to make for you.
B-37. Show when a shape's production has failed. READY — new, small (engine). Right now a failed production and a running one look identical. The database already links a shape to its job; only a way to read it is missing.
B-38. Bring the Rendering screen onto the shared contract. READY — new, small. Three of the four rooms use the shared state rule; Rendering still has its own hand-rolled version.
B-39. Ephemeral agent identities. READY to scope — new. When no agent is named, the system invents one and stamps it onto the permanent record. It is declared behaviour, so it is not a lie — but a record naming an agent that never existed is worth a decision.
B-40. Where contributed Markdown should go. READY to scope — new. It currently routes through seed extraction, and that registration's own comment says the canonical path is elsewhere.
B-20. The marketing website. READY. B-21. DONE. B-22. Package Stele. WAITING (background). B-23. The security story. READY. B-24. Investor-visible FORAY. READY — unblocked by B-29.
Restricted-visibility slices 2–3 · target-hosted visibility · protocol wire-format changes · OVA's remaining standalone role · cross-fund questions · the stray zip file in the record · how many live records already carry a fabricated author (needs a production database query) · whether a held shape whose job failed is ever cleaned up (the B-37 gap does not depend on the answer).
The restart, and it has been waiting the longest. Five change requests are merged, tagged, tested and not live — six merges, because one of them spans both repositories. Everything above marked DONE is done in the repository and absent from the running system. The restart is yours by the charter and cannot be delegated. They batch into one act.
| Merged and not deployed | Where | |---|---| | CR-2026-159 — the provenance field | engine | | CR-2026-160 — the Manifestation screen | surface | | CR-2026-161 — the record writes that aren't true | engine | | CR-2026-162 — the lost contribution, and downloads | both | | CR-2026-163 — the Shaping screen | surface |
B-16. Read seed v0.13 before it commits.
Everything else proceeds without you. Decisions inside the authorized build items are taken by the sessions and recorded with their reasoning in the status brief, where you can overturn any of them at cadence in one word.
DUNIN7 — Done In Seven LLC — Miami, Florida DUNIN7 — the build list — v0.14 — 2026-08-03