First authored design, 2026-09-15. This elaborates exactly WM-09. It is a reviewable design, not implementation, independent acceptance or machine completion. The existing build loop continues under claude-2; these documents do not dispatch new jobs or override recorded decisions.
All WM cascades · Checklist item · Machine-readable cascade
WM-09 is the ruled transformation of a prior cascade, candidate action space, repository and independently supplied admission attribution into a CascadeDiff. A graph with plausible edges is not enough. The design must explain what the organiser changed and which laws concern nodes it did not add.
WM-09 — organise constructs the ruled attributed cascade change. PARTIAL: serving activation, ordinary constructed family and click receipt with preserved authored relations, nonvacuous no-bootstrap/precedence/acting evidence and exact downstream policy identity. Legacy organise still has a sorry; its replacement must be explicitly connected. [T,L] Built evidence: Four-input F12RuledCarrier and Snatch formal exemplar exist. Runtime bd803bc0, admissions repair 24dc6068, and receipt-mode call sites now exist; claude-20 independently reviewed codex-27's implementation; owner follow-up fixes have not themselves received independent review.
The preceding evidence is the checklist’s dated account. It has not been re-audited as a current deployment census for this design.
Pattern: wm-pattern-design/attribute-organising-change.
Bind the prior cascade, selected candidate set, source repository and admittedBy argument as distinct inputs. Retain before-state identity and provenance. Do not derive admission attribution from the output or treat organiser-added nodes as externally admitted.
Pattern: wm-pattern-design/composition-changes-the-problem.
Explain how proposed relations change applicability or consequences using actual pattern arguments. Separate authored repository relations, organisation-derived edges and a proposed new relation awaiting admission. The organiser cannot manufacture its own evidence of repository reachability.
Pattern: wm-pattern-design/attribute-organising-change.
Check selected/authored/admittedBy preservation and the node union; require organised-edge reachability. Evaluate O3 on nodes minus addedByOrganise, as the ruled carrier states, not on the newly added nodes. Do not generalize an exemplar with empty addedByOrganise to all cases without proving the needed set relation.
Pattern: wm-connected-learning/same-interpretation-predicted-and-enacted.
Retain precedence and acting order before/after, guards, history and any score evidence. Under the ruled O4, changed precedence entails changed acting order or changed score. A dummy score or arbitrary order marker cannot stand for canonical G; where that evidence is required it depends on WM-10/12.
Pattern: wm-pattern-design/same-policy-through-comparison.
Bind the diff and resulting cascade/precedence identity to candidate construction and eventual enactment. Preserve the specification’s distinction between precedence context and nodes; do not reject the approved exemplar merely because precedence mentions non-nodes. Unsupported firing interpretations remain missing inputs.
Pattern: wm-qualifying-run/certificate-and-world-must-meet.
Explicitly connect the ruled implementation to the legacy organise obligation and retain source/test/review/ordinary-use evidence separately. A conformant empty-change witness is not evidence of nonvacuous production organisation. Record an actual before/after operation exercising the laws.
These are design input/constraint relationships; they do not assert automatic runtime firing. Each contribution constrains the next actual artifact.
| From | To | Relationship | Why |
|---|---|---|---|
| WM-09-C1 | WM-09-C2 | prerequisite | Relations must be justified against these inputs. |
| WM-09-C1 | WM-09-C3 | prerequisite | The ruled predicates quantify over the supplied sets. |
| WM-09-C2 | WM-09-C3 | prerequisite | Proposed organisation must preserve repository authority. |
| WM-09-C3 | WM-09-C4 | prerequisite | Precedence evidence belongs to the same validated diff. |
| WM-09-C4 | WM-09-C5 | prerequisite | Policy identity includes actual execution semantics. |
| WM-09-C5 | WM-09-C6 | prerequisite | Correspondence must concern the delivered result. |
| WM-09-C6 | WM-09-C1 | revision-feedback | An ineffective organised change can reveal an incorrect attribution or input account. |
Input binder → four-input envelope. Relation proposer → attributed proposed diff. Ruled checker → osel/oauth/oattr/o1–o4 results. Policy exporter → exact cascade and precedence. Legacy/refinement adapter → same operation with evidence. Names are proposed responsibilities, not a claim that all adapters already exist.
Each envelope must retain its schema, content identity, source/model revisions, task/occurrence and information boundary. Typed missing inputs remain missing; do not replace them with success-shaped defaults. Implementers may reuse existing compatible components, but must identify the real producer and consumer before crediting integration.
Adding evidence discipline to a handoff design may change which claim can be emitted. The organiser must show the prior design, the new contribution and why its relation is licensed. A graph reconstructed only from the final result hides whether the organiser preserved the original nodes and source relations.
This situation is illustrative, not a measured production result or an adopted probability table.
Distinguishing controls: Use a nonempty pre-existing population, independently admitted nodes, organiser-added nodes, an unsupported edge, and precedence changes with and without actual consequences. Reject changing the O3 population or inventing admittedBy. Include a constructed law check and a separate ordinary-use receipt at the actual call site.
Do not rerun the entire machine merely to validate a local edit. Select checks for the changed invariant; retain commits, commands and results. A future qualifying run still requires every required node and connection.
WM-03 · WM-08 · WM-10 · WM-11 · WM-12 · WM-14
Open: source-to-legacy correspondence, genuine nonvacuous precedence/acting evidence, and full G-dependent checks. Existing empty/default witnesses prove only their stated laws. Follow-up owner fixes and serving activation require their own review/evidence.
The dependency links express interface constraints, not a topological build order. A producer and consumer can jointly constrain an interface without requiring that all other implementations be finished first. Use a bounded packet once its relevant semantics are settled.
The companion JSON pins the governing checklist, September rulings, current cascade-policy semantics and every applied pattern. Where the semantics source distinguishes a ruling, extrapolation or open proposal, that distinction controls. No generic finite witness is promoted to a machine instance. Existing patterns are reused within the application stated above; their other examples, thresholds and historical implementation claims are not automatically adopted.