Version. 0.1
Date. 2026-08-25
Author. Claude Code on DUNIN7-M4. Operator: Marvin Percival.
Status. Proposal for the ruling sitting. Not a decision, not a recommendation with a default. Raised in current-status/loomworks-completion-inventory-v0_1 §7 as an observation; recorded here as its own item because it changes what a sitting decision commits to, and a decision sheet line should say so rather than let the sitting inherit the change silently.
Wave 2's walk currently reads: "one folder upload through the pre-flight; one description corrected by hand; one buffer review against a new seed" (program §5) — an invented folder, exercised once, then discarded.
Use the Enrollium material as that corpus instead. The Drive starter set (five files, schema metamodel + EHR architecture + two reporting amendments + a Forge skill doc) is a real multi-file folder of the exact kind the ingestion pre-flight (CR-C) was built to pre-flight — not a fixture manufactured to exercise the code path, but the first real material the Wave 2 walk would otherwise wait for.
The ingestion walk and the first-run-complete material become one act instead of two. Today the program schedules them separately: Wave 2 proves ingestion works, Wave 4 (or later) proves Loomworks works on Enrollium. Folding them means the folder that proves the pre-flight is the folder that starts the first-run-complete engagement, and the Operator's Wave-2 walk time buys progress on both fronts at once rather than one.
It also means the pre-flight is proven against real 258KB-scale material rather than an invented folder sized to be convenient. Whatever the pre-flight's volume threshold and per-file cost line (D10) actually feel like at Enrollium's scale, the sitting finds out during Wave 2 instead of guessing.
The distillation choice arrives in Wave 2, not Wave 4. Right now nothing in the program forces a decision about how much of the 258KB V61 spec (or the five-file starter set) becomes Memory until whenever Enrollium induction happens. Making Enrollium the Wave 2 corpus means that choice — full document, starter-set subset, or an Operator-curated cut — has to be made before Wave 2 can be walked, which is materially sooner than the program currently schedules it.
The seed-route question comes forward with it. Inventory §7 named two live routes — the Phase 53 product route (shell → upload → extract → induct → instantiate) or an April-style one-off induction brief. Which route produces the engagement Wave 2 uploads into has to be picked at the same moment, not deferred to whenever Enrollium's induction was otherwise going to happen.
Both of these are real decisions moved earlier, not eliminated. The proposal does not make them smaller; it makes them due at Wave 2's start rather than at some later point the program leaves open.
If Enrollium is the Wave 2 corpus, Wave 4's walk is no longer a fixture walk.
The program currently gives Wave 4 its own fixtures — "a test account, a test engagement, a test contributor, created on the production perimeter under the walk-audit pattern" (program §5) — disposable scaffolding built to prove the finish line works, not meant to be kept. If Enrollium's engagement already exists from Wave 2, Wave 4's comprehensive-test walk has an obvious, better target sitting in front of it: walk the finish line against Enrollium itself, the Operator's actual chosen first-run-complete case, rather than against throwaway fixtures.
That is not a small substitution. It changes what Wave 4 is for — from "prove the mechanism works on anything" to "prove the mechanism works on the case that matters." The program's own §9 states what it does not promise: "it makes the finish-line sentence true on the production perimeter and puts you in a position to test it comprehensively." Testing against Enrollium instead of fixtures is arguably closer to that promise's spirit — but it is a change to the shape of Wave 4, and the sitting should rule on it as that, not absorb it as a detail of Wave 2's corpus choice.
It does not choose the distillation approach, the seed route, or whether Wave 4 becomes an Enrollium walk. It does not touch the program or the inventory — both stand as filed. It states one idea, its cost, and its downstream consequence, for the sitting to take or leave.
DUNIN7 — Done In Seven LLC — Miami, Florida Loomworks — Enrollium as the Wave 2 corpus — Proposal — v0.1 — 2026-08-25