Architecture frame
Code is getting cheap. The order above it is not.
Coding agents produce in hours what took teams weeks. This page shows how I, as a principal architect, build order across many repositories on my own system: who may deviate, what gets measured, what belongs together.
The situation
What the AI era makes scarce
Code used to be the bottleneck. A coding agent now writes in an hour what took a team a week. Every team copies the organisation's standards into its own repository, improves them there and forgets the copy. A year later each standard exists in several versions, and nobody can say which applies.
The bottleneck moves up, to the order above the code. Who may deviate, and for how long? Whether a repository runs on the paved road the organisation gave itself is asserted and rarely measured. And whether the systems belong together or merely sit side by side, often nobody knows. In many companies governance is a meeting, not an order you can check.
That shifts the architect's work from the single design to order across many systems. Tools measure. Who is accountable, they do not decide. That is how I read it after 25 years in grown landscapes.
Where the method comes from
Three eras, one question: which version applies?
Plant · 2004–2006
Machine control and warehouse logistics, close to the hardware in C, Java on top, installed during live plant operations.
Group · 2006–2020
Group-wide software development across seven plants: ERP, MES, logistics, production control. Then enterprise architecture, application portfolio and migration during live operations.
Platform · 2022–2025
A business-critical embedded software platform, twelve teams, shared delivery standards and quality gates with measured effect.
The order
Paved road downwards, promotion upwards
One repository is the canon. Every copy of a standard elsewhere is measured against it and lands in exactly one of four states. Only one of them is a question. What has improved in a repository becomes a candidate for the canon.
Canon
Identical to the canon. Nothing to do.
Outdated
Matches an earlier state of the canon, unchanged. Safe to update, no judgement needed.
Drift
Deviates from the canon and matches none of its states. The only question: harmonise, pin, promote or retire.
Standalone
There is no canon for it. The repository is the source, and the copy becomes a candidate for the canon once it occurs more than once.
Three dimensions
Three questions for any system landscape
Governance
Who may deviate, for how long, with what right?
An exception applies to exactly one state of the artefact and carries a reason. If the artefact changes, the deviation is a question again. Every repository declares what it must never contain. A machine may propose and build, but not merge. In the werkbank: the pin in the canon register, and a merge command you copy instead of a button you click.
Compliance
Does every repository run on your own paved road?
Compliance here means that a repository keeps the organisation's own rules: templates, gates, scripts. Each copy's state comes from Git history, not from self-reporting. Red is a finding with a stable key. Green is not yet a merge right.
Coherence
Do these systems belong together, or merely sit side by side?
A register shows which concepts are implemented where and how often each version is used. What nobody uses becomes visible. Business affinity between systems is not measured yet; see limits.
Four decisions
Four decisions, each with a price
| Decision | Price | Limit |
|---|---|---|
| Hash instead of judgement. The state of a copy follows from its content hash against the canon.Evidence: base/backbone/portfolio-claude.py:206–213 · werkbank BIBLE INV-1 | Every deviation is provable, including the unimportant one. | The hash compares bytes. Two versions that mean the same count as different. |
| Container as the board, host as the hand. The container displays and manages the queue; it only reads the reports. Measuring and executing is done solely by the operator's machine, on its own branch.Evidence: werkbank BIBLE 2026-09-01 “Container as the board” · INV-4 · docker-compose.yml:32–33 | Between board and hand, every handover is an explicit step; without a running runner, a job stays put. | What the run did not collect, the board does not know. |
| A green gate is not a merge right. The gate reports, a human merges.Evidence: scripts/laeufer.sh:344–374 · web/src/pages/Auftraege.tsx:236–251 · werkbank BIBLE INV-5 | A finding waits for a person. That is slower than auto-merge. | The gate only checks what it has a rule for. |
| Deterministic before model. Mechanical findings are fixed mechanically; a model only proposes where a judgement is missing, and never merges.Evidence: werkbank BIBLE 2026-09-01 “Two tracks” · INV-4/5 | Less automation. The model gets proposals, not decisions. | Judgement cases remain human work, and with drift there are many. |
Limits
What the order does not decide
- The hash compares bytes. It cannot see whether two versions mean the same.
- Concepts are recognised by path patterns. One in an unusual place is missing from the register.
- The hash sees no proximity. A copy shifted by one line is drift to it, not outdated.
- Business affinity between systems is not measured yet. Coherence here is register and usage.
- The judgement stays with a human. The order proves that one is needed.
Transfer
What this looks like in your organisation
| In the werkbank | In your organisation |
|---|---|
| Canon | Your platform team's templates, gates and scripts, as a repository with history |
| Drift | A team's deviation, with an ADR that gives the reason |
| Pin | An exception bound to artefact, state and reason. The review date is yours to add; in the werkbank the pin expires with the next change. |
| Promotion | An InnerSource contribution back to the platform, with the decision in the register |
| Finding with a stable key | A ticket that keeps its key until it is closed |
| Measured and decided kept apart | Evidence classes as in the review: proven, confirmed, assumption, open |
To the special case in the review →
2026-10-18 · The werkbank is a private system for my own portfolio. Evidence is path and line in the private repository, not a link.