- 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 14: How do coding agents use the graph?
Loading the video
Transcript
14. How do coding agents use the graph?
Developers keep the coding agents they already use, such as Claude Code or Cursor. The coding agents connect to the knowledge graph through the Breeze.AI MCP server, a standard interface that AI tools use to call other services. The impact report goes into the coding agent's prompt. With the report in its prompt, the coding agent knows which services, components and tables the change must touch. The coding agent cannot ignore what the impact report found, and the specification tells it what to build. Rules for the functional layer are checked on the developer's machine before any change reaches the graph. Code generated twice from the same prompt still differs in detail, such as variable names and the order of operations. The impact report fixes the structure of the change, so the remaining differences are in detail only. Code review moves from asking whether the agent changed the right files to asking whether the details are right.
On the site: The Claude Code Plugin · Integration Surface · Ontology Guardrails
Choose a path
The full video in six parts and an appendix, one part at a time.