Graph system G31 Realm V, volume 32 of 42
Source dependency and change impact graph
Which lessons, code, tests, and pages must be reviewed when guidance changes?
Researched designNot deployed
Question§
Which lessons, code, tests, and pages must be reviewed when guidance changes?
Nodes§
Source section; Claim; Lesson; Template; Code artifact; Test; Public page
Relationship sketch§
- artifact → depends on claim
- claim → source section
- change → affected artifact
Evidence inputs§
Explicit dependency mappings, source review events, version hashes, actual artifact identifiers.
Implementation§
Track direct dependencies rather than merely storing a bibliography. A source change generates a scoped review queue; it must not silently rewrite production code or mark dependent claims false.
Acceptance checks§
- A simulated source change identifies known dependents
- Unknown impact is reported
- Human review controls promotion of changed requirements
Do not infer§
A changed webpage hash does not prove that the relevant technical requirement changed.
Publication boundary§
Private maintenance graph; public changelog may summarize real updates.
Source basis§
S14, S16. See Research/sources.json. Sources support the primitives or named technology. The organization, labels, actions, and acceptance contracts in this catalog are this library's design, not claimed provider requirements.