E05 — Qualifying timestamped run + Lean validation

Authored design — 2026-09-15. Section 4. This cascade elaborates the existing checklist item. It is not a dispatch, implementation receipt or completion verdict. Work outside WM-01–14 still requires Joe’s explicit greenlight; having a cascade is necessary but not permission.

Section 3/4 index · Exact TODO · Cascade JSON

Situation and design problem

The qualifying claim requires one real timestamped run and Lean-computed validation of its certificate. Combining unrelated component successes cannot establish that occurrence.

Governing checklist snapshot

E05 — Qualifying timestamped run + Lean validation. OPEN: every required node and connection positively validated at the specified meaning, actual real work, retained inputs/outputs and independently computed certificate. Machinery r8 and annotation A8 cannot replace this.

This is the checklist’s dated evidence account, not a new deployment census. Existing source/test evidence keeps its bounded credit. The acceptance obligation above governs this design.

Pattern applications

E05-1 — Fix real work and success meaning

Pattern: wm-qualifying-run/criterion-before-outcome

Retain the authorized task, its participant-relevant criterion and input boundary before the outcome. Verify readiness against every required node and connection; a run with unvalidated nodes remains a machinery test.

E05-2 — Execute the authorized complete episode

Pattern: wm-qualifying-run/one-episode-all-required-connections

When separately authorized, retain actual selection, enactment, observation and continuation with full policy/model identities. On-demand operation is sufficient under the ruling; cron is not added as a prerequisite.

E05-3 — Assemble same-run evidence

Pattern: wm-qualifying-run/one-episode-all-required-connections

Acquire all mandatory nodes/edges from this episode through TRACE/E02, plus independent outcomes and exact review commissions. Refuse substitution of r8, annotation A8 or another episode for missing evidence.

E05-4 — Compute independent formal validation

Pattern: wm-qualifying-run/certificate-and-world-must-meet

Generate and check the authentic certificate using the admitted Lean predicates. Retain both artifacts: the timestamped real run and Lean-computed validation, with independent semantic review and Joe’s acceptance of the qualifying fact.

Composition and interfaces

Each node’s stated artifact is the input or constraint for the related node below. These are design dependencies, not a claim that a runtime scheduler automatically fires patterns. Existing WM producers are reused through the linked contracts; no second implementation is implied.

Retain the actual subject, source/model revision, task/occurrence, cutoff, producer and consumer for each interface. A missing field is a named gap; a default that changes the meaning is not an adapter. Reuse existing records where they satisfy these obligations. If a new component is indispensable, identify its exact TODO/cascade clause before seeking a separately bounded implementation instruction.

Worked situation

A machinery run reaches a successful stop line and emits a truthful false certificate. This can validate the detector, but E05 still lacks the all-node working episode and its positive validation.

This is a distinguishing design example, not a claimed production experiment.

Implementation sequence and closure evidence

1. Bind the first application to the actual source, task and authority. Resolve the decisions below before their dependent change; do not reproduce a known gap merely to claim activity.
2. Implement only the specifically dispatched producer/consumer change from the middle applications. Retain the meaningful pre-change failure and relevant post-change controls; do not start a general infrastructure project.
3. Acquire the final application’s evidence and independent review. Compare it against every clause of the exact TODO, identifying any still-open dependency. Source, tests, serving state, ordinary use and whole-run validation receive different credit.

Distinguishing controls: Reject unvalidated node, unfired mandatory edge, changed criterion, cross-run borrowing, fake enactment and negative certificate relabeled positive. Test the checker before claiming the real success.

Closure rule: every part of the quoted obligation must be supported by the indicated artifacts and actual connections. A useful rejection proves the rejecting boundary only. One accepted subclause does not tick the whole item. A bellback must supply the exact reviewed subject, executed checks, independent verdict and remaining clauses.

Dependencies and authority boundaries

E01 · E02 · E03 · E04 · TRACE · E10

Execution is not greenlit by this design. Readiness evidence and a separately authorized run are required; remaining Holes obligations cannot be waived.

Dependency links describe required interfaces; they do not authorize work on those items. No implementation outside the existing TODO list is approved. Publication does not select a numerical law, settle an unresolved operator ruling or authorize a run.

Pattern and source scope

All seeded patterns are applied above. The JSON pins their source bytes and the governing checklist/rulings. Historical formulas, thresholds and examples in a pattern remain scoped examples unless the governing contract adopts them. This draft adds no pattern-library entries and claims no independent semantic ratification.