- 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 / Appendix: Where it came from
Transcript
30. Where it came from
Semantic Engineering was assembled over eight years of client work at Accion Labs, from 2017 to 2025. In 2017, an internal Accion Labs framework called Breeze set out what product owners, UX designers and architects need to produce. Teams maintained the Breeze documents by hand, and tended to drop them under deadline pressure. In 2022, on a drug-discovery project for a pharmaceutical client, connecting the AI model to a knowledge graph kept its hallucinations, the answers it invents, under control. In 2023, the knowledge-graph approach became a commercial platform, KAPS, used across customer engagements. By 2024, the Breeze guidelines had become the four layers of the knowledge graph, with agents built around them, in a platform named Breeze.AI. The method took the name Semantic Engineering in 2025. The framework and concepts of Semantic Engineering are public and free to apply. The methodology runs on Breeze.AI for new and existing applications, and on ASIMOV for legacy modernization. Teams can adopt the methodology with Accion Labs, and an engagement can start with a two-day workshop.
On the site: The 2017 Framework: Breeze · The 2022 Discovery: Drug Discovery and Hallucination · Productizing the KG Approach: KAPS, 2023
Choose a path
The full video in six parts and an appendix, one part at a time.