G31 — Source-dependency and change-impact graph · Graph systems

186 words. Researched design, reviewed 2026-09-12: a library view or proposed design with its sources stated; not a deployed system, a live audit or a provider requirement. Source: Graph/G31-source-dependency-and-change-impact-graph.md. Graph systems, shelf 5 of 8; library release 2026.09.12-g40.

Status: NEW RESEARCHED DESIGN; not deployed
Reviewed: 2026-09-12
Nature: library governance view
Priority: P2
Accountability: R14, R24, R21

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.