Architecture as code
Diagrams are committed to the repo and generated from real config where possible, so they stay true instead of decaying.
← The K-Framework
★ Judgment · Intellectual ControlLayer 13 of 16Visual guide
PILLAR C · LAYER 02 · C.02Architectural Visibility.
See the big picture, make better calls.
What a CEO/CTO needs to know
If the architecture lives only in one engineer's head, every change is a guess and that engineer is a single point of failure. Visibility is what makes refactors evidence-driven instead of fear-driven.
The system made legible: service catalog, data-flow map, and decision records, all in version control.
[WHAT IT IS]
The engineer’s view, in plain language.
You cannot optimize a system you cannot see. Architecture diagrams are first-class artifacts: kept current in version control, referenced in every review, and the substrate for every architecture decision.
[HOW WE BUILD IT]
What “done right” looks like.
Maps and catalogs
Service catalogs and data-flow maps make the system legible to anyone, not just its author.
Referenced, not filed
The on-call runbook points at the actual diagram, and reviews use it, so visibility is part of the workflow, not a poster.
[MATURITY LADDER]
Where does your build sit?
Four rungs from absent to production-grade. Level 3 is the target, and the only one that survives a real production incident.
L0
Absent
The architecture is tribal knowledge. There is no current diagram.
L1
Ad-hoc
Diagrams exist but are stale and rarely opened.
L2
Managed
Diagrams are maintained, but not generated from config and not used in reviews.
L3Target
Production-grade
Architecture-as-code, current maps and catalogs, ADRs, and diagrams referenced in reviews and runbooks.
[VALIDATE IT YOURSELF]
How to check it’s really there.
You do not need to read the code. Ask these questions and demand these artifacts. Vague answers are the finding.
★ Ask your team
- ?Where is the current architecture diagram, and who keeps it true?
- ?If our lead engineer left, could the team still see how the system fits together?
- ?Do reviews and runbooks reference the real architecture?
★ Demand to see
- Architecture diagrams in version control, generated from config where possible
- A service catalog and data-flow maps
- ADRs and a runbook that points at the live diagram
● WHAT L0 LOOKS LIKE
The failure mode, in production.
The architecture lives in the head of the original engineer. They leave. The team cannot see how the pieces fit. Every change is a guess, and refactors are driven by fear instead of evidence.
Want this layer audited in your stack?
We run the K-Framework against your AI build and hand you the gap list, ranked by what it will cost you in production.