Software generated from design documents has a hidden problem: a change in one design element can affect many code pieces. that generate code cannot reliably trace those chains, so they miss updates or break unrelated code.
The authors build a , a network of connected design items, organized like Git. Each item carries a content hash: a fingerprint of its details and dependencies. Changing one item changes the fingerprints of everything depending on it. Comparing old and new snapshots yields the exact affected chain, fed to the model as its only allowed context.
An early industrial payment deployment computed exact boundaries and produced code changes matching the design update. Impact analysis becomes verifiable structure, not guesswork.
