I · The keystone
Architecture is decisive.
As implementation becomes faster and more accessible, the quality of the architecture increasingly determines the outcome.
As implementation costs fall, architecture determines the outcome, so it comes first and every engagement is measured against the result.
In practice
What it means for your system.
Agents can write code quickly. Deciding what the system should be stays with engineers and owners, and it comes first. Every later step is measured against that decision.
- Boundaries, sources of truth, and approval points are set before any build.
- Acceptance criteria are written into the plan, so the build has a target.
- Changing the architecture is a decision a person makes, with its cost stated.
The word for it
Architektonikē
ἀρχιτεκτονική
Architektonikē is Greek for “the master craft that directs the others.” The design that directs every other decision comes first.
Why it matters
When building gets faster, the plan carries more weight.
Agents now write working code in hours. That changes where the risk sits. A system can be built quickly in the wrong shape, and every later change pays for that shape.
The decisions that set cost and reliability come before the code: what the system is for, which records it trusts, and where people approve. Those decisions cost little to change on paper and a great deal to change in production.
So architecture comes first, and it is written down. Every build, test, and release is then measured against a plan your team has read and signed.
Read it accurately
Scope of the rule.
- It starts with the system you need now.
- The architecture describes the system you need now and leaves room for what follows. One workflow can be designed well without designing the whole business.
- Technology choices stay open to change.
- The architecture fixes boundaries, records, and approval points. Models and tools behind those boundaries can change when measurement supports the change.
- Agents help build, against a clear target.
- Agents still write much of the code. The architecture gives their work a target, and engineers review what they produce against it.
How it is measured
Every rule is something you can check.
Acceptance criteria met on the first pass; rework and architecture reversals avoided.
In an engagement
Where the rule is applied.
The rule is checked at each stage of the work, from the first design to the system in operation.
In the design
A System Blueprint sets the boundaries, the sources of truth, and the approval points. Acceptance criteria go into an Acceptance Charter your owner signs before any build.
In the build
Custom Agentic Systems builds to the agreed design. Agents write code within it, and engineers review each change against the architecture.
At acceptance
The system is tested against the criteria agreed before the build began. The measure is whether those criteria are met on the first pass.
In operation
Each design decision stays on record with its reason. Later changes start from that record, so the system keeps the shape your team approved.
Check your own system
Five questions to ask this week.
Each one has a yes or no answer. A no marks where to start.
- Can someone on your team describe what the system is for in one sentence?
- Is there one agreed source for each kind of record the system uses?
- Are the points where a person approves written into the design?
- Were the acceptance criteria agreed before the build began?
- Is each major design decision recorded with its reason?
Delivered through
The services that apply this rule.
Apply the rule
Check it against your own system.
Questions
Does architecture first mean a long planning phase?
No. The plan is sized to the work. For one workflow it can be a short document; for several systems, a System Blueprint.
Who decides the architecture?
A senior engineer proposes it and your owner approves it. Agents can help draft options, but a person makes the decision.
Can the architecture change during a build?
Yes, when the evidence calls for it. The change is reviewed, its cost is stated, and your owner approves it before work continues.
How do we check this rule on our own system?
Ask whether the acceptance criteria were met on the first pass. Then count the rework and design reversals that followed.
What does the written architecture contain?
The system’s purpose, its boundaries, the records it trusts, and where people approve. It also records each major decision with its reason, and the criteria the build must meet.
Can we test an idea before committing to an architecture?
Yes. The Agentic Engineering Diagnostic tests one workflow in code first, so the architecture starts from evidence about your own work.