- 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 5: Four principles
Transcript
5. Four principles
Semantic Engineering answers the problem with four principles that apply to every kind of project. The first principle is to record the knowledge that governs the application in a knowledge graph, with explicit items and the relationships between them. Each agent asks the knowledge graph for just the part its task needs. The second principle is that every change is analyzed against the knowledge graph before code is written, and agents cannot ignore what the analysis finds. The specification still describes what to build, including the details the graph leaves out, and the knowledge graph governs how each change fits the application. The third principle is named ownership: every part of the knowledge graph has a person accountable for keeping it accurate. When part of the knowledge graph falls out of date, the methodology holds the owner of that part responsible. The fourth principle is validation gates: automatic checks that test every change against the knowledge graph. Each validation gate records a pass or a fail that the team can audit.
On the site: The Methodology · Agentic Software Engineering and Modernization, powered by Semantic Engineering
Choose a path
The full video in six parts and an appendix, one part at a time.