Check reference
Check model-verification continuity through a hierarchy
A parent requirement can carry model-verification results while a newly added child remains unchecked. verification_chain_complete identifies that particular hierarchy gap.
Explicit parents define this chain
The check analyzes active requirements connected by their explicit parent field. Cross-cutting satisfies traces do not create hierarchy obligations here. It starts with parents that have a qualifying recorded result and inspects their children requiring FRETish verification. Retired, superseded and rejected requirements are excluded before analysis. The default severity is warning.
Illustrative example: an added rejection child
Parent: request handling
recorded realizability: realizable
Child A: accept a valid request
recorded consistency: checked
Child B: reject an oversized request
no qualifying model result
Child B is the outstanding analysis in this example. Child A can satisfy this check through consistency even if its realizability field differs from the parent's. The implementation deliberately uses an OR: realizability, checked consistency or a passed vacuity result can supply qualifying child credit. It does not require every analysis arm to match.
Repair the named edge
Inspect whether the child is correctly placed under that parent and whether its formalization strategy is appropriate. Run the child's relevant verification path and retain the actual result. If analysis cannot decide, keep that uncertainty visible. Do not copy the parent's fields into the child or add a false hierarchy link just to obtain a complete-looking chain.
proof workflow check --stage verify --verbose
proof audit --check verification_chain_complete --verbose
This is not end-to-end evidence propagation
The check compares recorded model-verification state. It does not execute tests, prove that a child refines its parent, establish fixture freshness or prove the implementation correct. A parent with no qualifying result does not create a chain to check, so a pass can also mean there was no eligible chain. Use cross-layer domain analysis, trace review and runtime evidence for those additional claims.
Follow the evidence
Inspect the first named child and the model result it is actually missing.
Review one incomplete verification chain. Bring the parent, named child and recorded results so we can identify the missing analysis without overstating what a complete chain would establish.