The boundary
result
├─ depends_on → price
├─ depends_on → limit
└─ does_not_depend_on → themeI59
State changed does not imply relevant state changed.
I60
Applicability should bind to the state subgraph that causally justified the result.
I61
Global version mismatch may be a conservative signal, not proof of invalidity.
I62
Relevant dependency drift requires revalidation, recomputation or domain proof before consequence.
Canonical path
DECLARE DEPENDENCY SET
↓
CAPTURE DEPENDENCY VALUES
↓
COMPUTE DEPENDENCY FINGERPRINT
↓
COMPUTE ARTIFACT
↓
STATE CHANGES
↓
OBSERVE CURRENT DEPENDENCY SUBGRAPH
↓
COMPARE FINGERPRINT
├─ same → MAY REMAIN APPLICABLE
├─ mismatch → REVALIDATE / RECOMPUTE / HOLD
└─ dependency model unknown → CONSERVATIVE BROADER CHECK
↓
CURRENT AUTHORITY ADOPTS
↓
CURRENT FENCE AT MUTATION BOUNDARY
↓
PROVE DEPENDENCIES → ARTIFACT → APPLICABILITY → EFFECTSafety boundary
A matching fingerprint proves only that the declared dependency representation matches. It does not prove that the dependency set is complete or causally correct. If dependency completeness is uncertain, use broader revalidation or conservative invalidation.