- 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 8: Keeping the graph accurate
Transcript
8. Keeping the graph accurate
Every change is checked against all four layers of the graph before it can merge. An agent called the PR Validation Agent runs this check on every pull request before it merges into the main branch. The check fails when a change misses a required outcome, duplicates an existing design component, crosses a service boundary, or breaks something that depends on it. When the code changes, the KG Sync Agent updates the graph before the pull request merges, so the graph matches the main branch. The health of the graph itself is measured too, with twenty-nine metrics and fourteen verification checks. A merge that fails one of the most critical checks is blocked until the problem is fixed. The four custodians stay human. Each custodian works with information that exists only in conversations and decisions between people, such as customer calls, compliance decisions, vendor contracts and user research. No system an agent can read contains that information. Agents draft updates to the graph for the custodians to approve, and enforce the graph when code merges.
On the site: The Validation Gate · Governance and Metrics · The 14 Verification Checks
Choose a path
The full video in six parts and an appendix, one part at a time.