- 10When are specifications not enough?
- 11Where is the state of the work kept?
- 12Who prepares a change before coding starts?
- 13What does impact analysis tell you, and when does it run?
- 14How do coding agents use the graph?
- 15How is each change checked, and how does the graph stay current?
- 16Who decides which work agents do?
- 17How do managers see what people and agents are doing?
- 18What happens across many products?
- 19What about existing systems and technical debt?
- 20What changes for the team?
- 21What results have teams seen?
Home / Follow the story / Scene 15: How is each change checked, and how does the graph stay current?
Loading the video
Transcript
15. How is each change checked, and how does the graph stay current?
Every pull request goes through the PR Validation Agent before it can merge. The PR Validation Agent compares the change with the impact report, and checks the change against all four layers of the graph. The check fails when a change misses an outcome the specification required, duplicates an existing design component, crosses a service boundary, or breaks something that depends on it. A failed check names the violation and the item in the graph involved, and a mismatch with the impact report goes to a person for review. Style, linting and unit test coverage stay in the team's existing build pipeline. The BDD Generation Agent writes test scenarios from the functional layer, each describing how the application should respond to a user's action. Before the pull request merges, the KG Sync Agent updates the graph to match the new code. The graph then matches the main branch, and the next impact analysis runs against the application as it is.
On the site: The PR Validation Agent · What the Gate Checks · What the Gate Does Not Do
Choose a path
The full video in six parts and an appendix, one part at a time.