B.10 Make Hidden Dependencies Queryable
Problem. Cross-cutting mechanisms depend on assumptions about the substrate they inspect. When those dependencies remain implicit, a substrate change can either break many controls at once or silently invalidate part of their coverage.
Move. Represent consequential dependencies explicitly so the impact of a proposed change can be queried before it lands.
Figure B.10-1 fans a change out to its dependents.
Example — Control blast radius. Each control declares its substrate dependencies as structured metadata. A query identifies which controls depend on a proposed substrate change and how each relation should be interpreted.
Example — Traceability. Symbol-anchored traceability applies the same move across engineering artifacts. Model elements, lints, code, proofs, and registries join through derived, re-checked edges. The resulting graph lets engineers query what a change affects and inspect why.
Related mechanisms: Control ↔ substrate dependency · Computed Control Blast Radius · Governance Graph · Symbol-anchored traceability · Derived Traceability.