Propagate Failed Prerequisites
Revoke downstream passes that depend on a prerequisite which failed its own validation.
These examples and illustrative results are independently authored teaching materials, not measured model results.
Use case
Audit A, B, C and independent D: B requires valid A and C requires B. If B passes first but A later fails ordering, raw A events cannot sustain B/C.
Mechanism
Validate dependency identities/graph and separate ungraded, fail, pass and unknown. Check own conditions, then revoke/demote dependent passes until stable, preserving unrelated D. Record direct failure versus prerequisite blocking. Missing IDs/cycles are configuration errors, not satisfied defaults.
Bad example
A’s event exists, so pass B and retain B/C after A fails.
Good example
After A’s own check fails, revoke B and then C while preserving independent valid D. Record A’s failure and downstream dependency reasons until no pass relies on invalid prerequisites, independent of declaration order.
Why the change matters
Occurrence differs from validity. Propagation repairs out-of-order grading and makes pass conclusions consistent with their prerequisites.
Observable expectation
Teaching final states are A fail, B/C blocked, D pass regardless of ordering. Missing IDs/cycles do not pass; unknown prerequisites do not establish dependent success. Finite monotone pass removal terminates.
Limits
A fixed point establishes propagation only, not classification, evidence or execution truth. Conditional dependencies/recovery need actual contracts; this is not every workflow state machine.