Version. 0.1
Date. 2026-08-06
Author. Claude.ai (drafting session). Operator: Marvin Percival.
Applies to. verticals/venture-diligence/venture-diligence-candidate-seed-v0_3; investigations/loomworks-foray-operational-visibility-investigation-v0_2; scoping-notes/loomworks-c5-scoping-note-domain-reference-model-v0_3.
Produces. Three version bumps. No prior version is edited; each stands as a sibling.
Why this exists. All three were corrected today for naming the wrong authorization substrate. All three were read end to end afterwards, and each turned out to report the status of work that has since completed. The vocabulary was the symptom.
> The pattern, and it is the same one the C5 note produced. A sweep looks for the thing it was told to look for. **These documents' stale vocabulary was a surface; their stale status is what would mislead someone picking up the work — a dependency named as pending that shipped, a claim named as undemonstrable that was demonstrated, a manifest reference thirty versions behind. None of it was findable by searching for a term.**
One thing this does not do. The FORAY investigation invokes a no-live-recall-demonstration rule twice, once to bar a demo. B-11 shipped and may have made that rule liftable. That is a decision rather than a correction and is put to the Operator separately; the splices below leave every mention of it exactly as written.
venture-diligence-candidate-seed-v0_3 → v0.4Three changes: two remaining mechanism mentions my earlier amendment did not reach, and one claim that is no longer true.
Replace:
> the isolation shape is a committed seed posture (OVA reach enforcement) with a commissioned scoping arc, not a designation question.
With:
> the isolation shape is a committed seed posture with a commissioned scoping arc, not a designation question.
Replace:
> found the frame itself wrong — not a designation question but OVA reach enforcement, a committed seed posture with the seam declared and not yet enforcing — and the scoping arc is commissioned.
With:
> found the frame itself wrong — not a designation question but reach enforcement, a committed seed posture with the seam declared and not yet enforcing — and the scoping arc is commissioned.
Replace:
> Until it lands, external-contributor isolation is committed direction, not demonstrable behavior, and this vertical is presented accordingly.
With:
> External-contributor isolation is now demonstrable. CR-2026-157 shipped on 2026-08-05 and built exactly this pathway: a person holding a credential for this engagement contributes into it without becoming a member, their contribution is held until a member with commit authority admits it, and they read nothing else. The exclusion is structural rather than a rule — membership is what every existing read checks, and a credentialed non-member has none, so they are excluded from every one of them without a single existing read being changed. Its acceptance gate verified this before it merged. (What remains unbuilt is reach restriction below membership — withholding some of an engagement's record from its own members — which is a different question and is not what this vertical's isolation claim rests on.)
Add to the version block:
> Amendment note (v0.4). A status correction, not a vocabulary one. v0.3 stated that external-contributor isolation was committed direction rather than demonstrable behavior. CR-2026-157 shipped on 2026-08-05 and demonstrated it; the vertical was being presented as weaker than it is. Two remaining mentions of the superseded substrate are also corrected — the v0.3 amendment reached the operative clause and not the header summary or the drafter's notes. Nothing else changes.
loomworks-foray-operational-visibility-investigation-v0_2 → v0.3Two changes, both about a dependency that is no longer one.
Replace:
> - CR-2026-157 (filed, awaiting execution) — the credentialed human contribution path for Model 1's target-side people. Already scoped; nothing new.
With:
> - CR-2026-157 — shipped 2026-08-05, merged and deployed. The credentialed human contribution path for Model 1's target-side people exists and is verified: attributed, held until admitted, reading nothing else. No longer a dependency; a foundation.
Replace:
> Recommendation: commission, sequenced after CR-2026-157 execution so the scoping session inherits a settled authorizer and credential substrate.
With:
> Recommendation: commission. Its sequencing condition is satisfied — CR-2026-157 shipped 2026-08-05, so a scoping session now inherits the settled authorizer and credential substrate this recommendation was waiting for.
Replace:
> developed here now that its named prerequisite — the OVA reach-enforcement resolution — exists.
With:
> developed here now that its named prerequisite — the reach-enforcement resolution — exists.
Add to the version block:
> Amendment note (v0.3). A status correction. v0.2 listed CR-2026-157 as filed and awaiting execution, and gated decision D-2's recommendation on its execution. It shipped on 2026-08-05. D-2's sequencing condition is satisfied, and the credentialed contribution path Model 1 depends on exists rather than being scoped. One remaining mention of the superseded substrate is corrected in the Origin line. Model 1, Model 2, §5's visibility schedule, §6's incentive realism, §8's pilot and decisions D-1 and D-3 are unchanged.
>
> Deliberately not changed: every mention of the no-live-recall-demonstration rule, at §7 and D-3. B-11 shipped and may have made that rule liftable, and that is an Operator decision rather than a correction. It is raised separately and left standing here until it is answered.
loomworks-c5-scoping-note-domain-reference-model-v0_3 → v0.4Two orientation references, both far behind.
Replace the whole of §1.3's first two sentences:
> Current-status manifest is genuinely v0.48 (header/Status line say 0.48; footer and changelog are stale at v0.47 — a known internal inconsistency, not a version error). v0.48 is dated 2026-05-31 and predates the seed v0.10 landing, so it carries no C5 or domain-layer entry by name.
With:
> [Amended v0.4] This orientation is thirty versions out of date and is preserved as written below. The current-status manifest reached v0.78, and the day-to-day status role has since moved to current-status/dunin7-status-brief. Anyone orienting to C5 should read the current status brief and the highest-versioned manifest actually present, not this paragraph. (v0.3 and earlier read: "Current-status manifest is genuinely v0.48… v0.48 is dated 2026-05-31 and predates the seed v0.10 landing, so it carries no C5 or domain-layer entry by name.")
And replace:
> A manifest v0.49 absorption pass is overdue and out of scope for this note.
With:
> [Amended v0.4] The absorption this paragraph called overdue has long since happened. Out of scope for this note either way.
Replace:
> ### 1.1 Settled in seed v0.10 (canonical, at origin dc9c784) — not reopened
With:
> ### 1.1 Settled in seed v0.10 — not reopened (the seed is now at v0.14; these four commitments survive, and where one has since moved it is marked)
Add to the version block:
> Amendment note (v0.4). Two orientation references corrected. §1.3 oriented against current-status manifest v0.48 and called a v0.49 absorption overdue; the manifest reached v0.78 and the day-to-day status role has moved to the status brief. §1.1 cited seed v0.10 as canonical; the seed is at v0.14 and its four commitments survive with the access mechanism corrected at v0.13, as this note's own v0.3 records. Neither correction touches the seven specification items, the contribution-authority finding, or any recommendation.
CR-2026-157 as pending, filed-but-unexecuted, or awaiting execution. Sweep for CR-2026-157 and check each mention.DUNIN7 — Done In Seven LLC — Miami, Florida Loomworks — status pass across three corrected documents — amendment instructions — v0.1 — 2026-08-06 Each was corrected for saying the wrong word. Each also said a finished thing was pending.