The name, the owner, the test and the date: one toolbox for ten books
For a mixed audience of architects, governance and security leads, operators and managers in European enterprises and public authorities
Ten books of The Transformed Architecture define or name more than sixteen hundred tools. Read side by side, they show one design in many dialects: records with a shared anatomy, identifiers that link them into chains, evidence that carries a date, checks made from outside the thing checked, and autonomy that is earned, budgeted and revocable. The lecture shows how to find a tool in ten minutes, how a cautious buyer and a builder assemble different toolboxes from the same parts, and why the series' rule holds everywhere: adopted means in use, and working means tested with a date.
6 min
The problem: which of ten books holds the tool for X?
A practitioner had to know which volume to open; the reference organises the tools by what the practitioner is doing.
Four kinds: artefact, own tool, third-party tool and method; laws and bare concepts are not tools.
The test of a reference: find the tools for the next piece of work in about ten minutes.
8 min
What every artefact has in common
Purpose, inputs and outputs, an identifier, an owner, a decision record, links, a review date and an expiry.
The chain from a service record of Nordvik Region to a failed restore test, a change and a risk acceptance reads in both directions.
A prefix can name more than one artefact, so read the Origin row.
9 min
From rule to evidence, from threat to verified control
A rule becomes a tool with an engine, tests, an independent decision point and a record of every decision.
A threat, a detection and a recovery are claims until a dated test turns them into evidence.
Authorised testing is scoped by a signed manifest, stoppable from outside and ends in a defensive improvement.
A register that counts untested claims gives a board a smaller and more honest number.
8 min
Agents: a label without a control
Mandate per agent, delegation profile per service; an unlisted action is undelegated and the lowest ceiling governs.
An observer the agent cannot write, an autonomy budget the observer counts, and a stop path outside the platform.
A rise in level is a recorded decision by a named authority; a fall is immediate.
7 min
People: agree first what a record may not be used for
Every decision about a person has a named human decider, a route to contest and a reviewer outside the line.
A competence record that cannot rank or discipline can be shared widely enough to condition an agent's autonomy.
Contested claims are graded, labelled, owned and given triggers in both directions.
7 min
Two toolboxes and what to do on Monday
The order follows the gap: Nordvik Region makes a procured system legible, Hansa Mutual bounds agents that already act.
Measure the toolbox by evidence age, adoption and retirements.
Read the Origin row, record the template version, choose defaults by decision, reserve identifier ranges and date every claim.
What the audience takes away
The series is one design in many dialects: anatomy, linked identifiers, evidence age, independence and earned autonomy.
Adopted means in use; working means tested with a date; a tool past its clock is unverified.
The tools are in the volumes; a toolbox adds the name, the owner, the test and the date.
A toolbox is a set of dated claims, not a shelf of templates
The lecture carries the argument of Part I: a reference is useful in proportion to how fast it answers and how far its sources can be trusted. It defines the four kinds of tool, shows what the inventory of 1,629 entries claims and leaves out, walks the identifier chain from a service record of Nordvik Region to a risk acceptance, and then follows a tool through its four decisions: select, adopt, review and retire. The thread is the rule that adopted means in use and working means tested with a date.
8 min
What counts as a tool, and what does not
The four kinds: artefact, own tool, third-party tool and method, with one example of each from the series.
Laws and regulations are instruments that obligations come from; a tool may help to evidence an obligation but is never the obligation.
The usage modes and the degrees of delegation are concepts; a delegation profile that applies them is an artefact.
8 min
How the catalogue was compiled and what it claims
An inventory of 1,629 entries across ten volumes: 641 artefacts, 378 methods, 370 third-party tools and 240 own tools, of which 227 are publishing scripts.
Three rules: nothing is invented, disagreements between volumes are recorded, and the order of the series holds.
Appendix A is the safeguard: every entry is listed there, so a tool missing from the prose can still be found by name or prefix.
10 min
The common anatomy and the identifier chain
Every artefact states a purpose, inputs and outputs, carries an identifier, names an owner, cites a decision record and gives a review date and an expiry.
Field names differ between templates, so search by identifier and not by field name.
The chain from SVC-NR-002 through SLO-NR-002, the failed restore test RST-NR-2027-002 and CHG-NR-2028-0007 to the risk acceptance in DRF-NR-001 reads in both directions.
Some prefixes name more than one artefact, so the Origin row is read before the prefix is trusted.
12 min
Four decisions in the life of a tool
Select against one unit of value: build, buy, reuse a feature already held, solve without AI or do nothing, each mapped onto a kind of tool.
Adopt on a dated readiness reading, through a gate whose items name their evidence, and show use with a dashboard that protects the people it measures.
Review from records; retire by criteria written into the decision record at adoption.
An anti-pattern is closed by a passed re-test and not by a merged remedy.
7 min
Two organisations, two scales of toolbox
Nordvik Region buys, has one legal regime, a seven-person platform team and no agent at Mode 5.
Hansa Mutual builds, spans several jurisdictions and operates agents with write access to production.
A tool that suits one often needs adaptation for the other, and the entries say so where the originating books do.
What the audience takes away
A tool is an artefact, an own tool, a third-party tool or a method; laws and bare concepts are not tools.
Search by identifier and read the Origin row, because field names differ and a prefix can name two artefacts.
Adopted means in use; working means tested with a date; retirement is decided when the tool is adopted.
Module 2 · Part II · Architecture and Delivery · 45 minutes
Text, checks and evidence: one pull request from model to proof
The lecture carries the argument of Part II. The model, the requirements and the reason for a decision are text under version control, reviewed in one pull request. A rule becomes a tool when an engine can evaluate it, it has tests, a decision point its author does not control evaluates it and every decision leaves a record. The platform is declared in files that a pipeline can check, and the declaration is kept apart from the system it governs. Examples come from Architecture as Code, AI Platform and Security, The Transformed Security Architect and AI Operations.
10 min
Architecture that a rule can read
Diagram decay: a drawing and a system drift apart when updating the drawing is a separate manual act.
The C4 model in the Structurizr DSL is the series' default; CALM is an alternative with a younger ecosystem.
Trust zone, data class, usage mode, identity, owner and policy point as properties let a pipeline fail an unprotected crossing.
8 min
Why it looks that way: the decision record family
The ADR, the AI Decision Record and the decision minute are one family with different jobs.
Keep the format small and add only fields that a script reads.
A validator is part of the record's definition: the repository of Architecture as Code ships four scripts for its ADRs and describes one in a chapter.
12 min
From rule to gate to evidence
Open Policy Agent and Rego are the common engine and language; the policies differ mainly in their input documents.
A gate is only as good as the inputs it reads, so a check on the resulting state belongs with every gate that reads a plan.
Bill of materials, provenance attestation and signature answer what is in an artefact, how it was built and who vouches for it.
Evidence is written once, signed by the pipeline run, bound to an obligation and given an expiry.
10 min
The platform as declared files
State needs its own care: it can hold secrets, and declared and actual state diverge between runs.
The gateway is the one component that is not optional, because logging, redaction, routing and budgets apply there to every AI call.
Every promotion has an owner who did not build what is promoted.
5 min
Limits on autonomy that these tools set
The policy decision point stays outside the agent at every degree of delegation.
An agent-authored change has an independent human approver, and no agent identity holds the right to sync a state engine.
What the audience takes away
Choose a model language by whether a rule can read it, and keep the decision beside the model.
A rule is a tool only with an engine, tests, an independent decision point and a record of every decision.
Choose one shape of evidence manifest, keep the gateway, and give every promotion an approver who did not build it.
The lecture carries the argument of Part III: governance is a small number of records, each with an owner, a purpose and a date on which it stops being valid. It follows the chain from the inventory entry to the AI Decision Record, then the second chain from an article of law to a control, an independent test and a board page, and the third chain from tender to exit test. It shows where the volumes use one name for different things, and why an exception without an expiry or a mapping without an evidence age is not a weaker tool but an unmanaged thing.
12 min
From inventory to decision record
You cannot classify what you cannot list: the inventory is derived from descriptors, and the usage-mode register catches Modes 0 to 3.
The questionnaire, the classification policy and the risk appetite statement turn a use into a tier.
A record without an owner, a review date or a trigger is treated as stale, and a stale record counts as an open risk.
The AI Decision Record carries the decision and its retirement criteria; each volume reuses it with its own number range.
8 min
Exceptions that stay temporary
As a meeting outcome an exception tends to become permanent; as a record with an expiry it stays temporary.
The exception gate rule denies a change that relies on an expired exception.
The prefix EXC names three different records in two volumes, so the kind and the schema identify the record.
12 min
From article to board page
Assure once, comply many: execute and evidence a control once and map it to many frameworks.
The mapping tools differ in what they refuse to leave out: an assurance artefact, a gate and evidence path, an evidence age and an owner.
A catalogue entry without a test is a statement; assurance is said by someone other than the control's owner.
Oversight-quality metrics are reported for groups and never to evaluate individual overseers.
8 min
What a maturity result means
Two models of the series with different scales and subjects are not interchangeable.
Maturity models measure practice, not outcome, and a self-assessment that nobody tests is a conversation starter.
10 min
Buying AI and being able to leave
A requirement states how it will be verified, and a clause names the control that enforces it.
An annex fixes a sample and a stop right outside the provider's platform.
Origin assessment, requirements profile and decision matrix are three sovereignty tools that should not be confused.
An exit plan carries the date and the result of its last test.
What the audience takes away
Every governance record answers who owns it, what it is for and when it stops being valid.
The chain from article to board page breaks at its weakest field, usually a missing evidence age.
Dependence on a supplier is acceptable when it can be undone and the exit has been tested.
Module 4 · Part IV · Securing and Testing · 55 minutes
From named threat to verified control: securing and testing as one chain
The lecture carries the argument of Part IV. A threat is a belief until a test named in the threat model verifies it. A test is lawful and safe only inside signed rules of engagement enforced outside the executor, and every authorised offensive activity ends in a defensive improvement. A detection is a record, not a rule, and a passing test has a half-life. Recovery is a claim with six parts and an age. The purple loop joins these into one chain in which closure is a named person's signature and the checker can fail in ways the checked does not share.
10 min
Naming and recording threats
STRIDE names the harm, MITRE ATT&CK and ATLAS name how an adversary produces it, D3FEND names what answers it.
The threat model as code is regenerated on change, reviewed against seven soundness checks and enforced by a gate.
The priority list connects the model to the test plan; a technique never selected for a scenario remains a belief.
10 min
Authorised testing under rules of engagement
The rules-of-engagement manifest comes first: scope, window, permitted scenarios, AI participation, stop conditions and stop path.
The expectation is written before the run, so a result is compared with a commitment.
Libraries and simulation products show that a control reacted to a catalogued behaviour, not that anyone acted.
10 min
Detection and investigation as records
A detection record adds to the rule an owner, tests, an alert budget and a review date.
A case record separates what the AI did from what a person checked.
The chain from intelligence record to hunt to detection to case shows an auditor how a detection came to exist.
12 min
Response and recovery: the age of a proof
Incident records fix times and decision holders and keep the assistant's contributions marked as drafts.
A clock sheet makes reporting deadlines owned before they are needed.
A recoverability claim has six parts; a failed result is never overwritten, and a later pass supersedes it.
A register whose denominator includes untested claims gives a board a smaller and more honest number.
Operating by record: see, act within bounds, account for the cost
The lecture carries the argument of Part V. The chain from signal to person has a tool for every link, and the observer is itself a service that needs something outside it to watch it. An action on a service is bounded by a record that is data, evaluated by something other than the actor and stoppable from outside, and its ceiling moves with evidence. A decision about cost, capacity or energy is written in a file with an owner and a date before money is committed, and the system that enforces it reads the same file as the report.
12 min
From signal to person
Seven links: instrumentation standard, collector, service record, objective record, burn-rate rules, correlation policy and metric catalogue.
An objective is measured at a point outside the service as well as inside it, so the service cannot report itself healthy alone.
A heartbeat to a receiver outside the platform tells a quiet observer from a failed one.
A correlation policy gives an AI layer a mandate, a never-suppress list, sampling and stop conditions.
13 min
Acting within bounds
A change is classified by the diff and the target; the declared class is a claim.
Rings and bake times bound exposure, and the first ring is never skipped for any class.
A runbook manifest bounds a remediation by preconditions, a dry run and an independent verification.
No engine supplies independence: verifier, policy decision point and stop path are separate components.
8 min
Ceilings that move with evidence
A class is suspended on two correlated incidents, and a runbook drops a level when it is past its review date.
A Level 3 class falls a level when its autonomy budget is consumed.
A tool that states its ceiling without a suspension rule has stated a hope.
12 min
Cost, capacity and energy as decisions in files
The allocation map and the envelope attribute and limit consumption at the gateway.
The unit of cost of an agent is the run, so a daily cap alone is not a control.
A capacity record without a back-test and an uplift is a hope.
An energy figure without a metered boundary cannot be compared; the right entry is that the claim is not yet available.
What the audience takes away
Every tool that watches needs something outside it that watches the watcher.
Bound every action by data, evaluate it outside the actor, and keep the stop path outside the platform.
Write cost, capacity and energy decisions in the file that both the enforcing system and the report read.
Module 6 · Part VI · Agents and Autonomy · 50 minutes
A label without a control: mandates, observers and containment for agents
The lecture carries the argument of Part VI. Deciding what an agent may do is a chain: scale, decision record, delegation profile, mandate, enforcement point, observer, budget and register. A break at any link, such as a Level 3 entry that names no enforcement or a budget counted by the agent itself, leaves a label without a control. The observer is a design and not a dashboard, a stop path is a timed property, and a level is earned and expires. The agent itself is a principal with one identity, and its containment must hold whether or not its manifest is obeyed.
12 min
Two answers to one question: mandate and delegation profile
The mandate belongs to the agent; the delegation profile belongs to the system, team or service.
The books use the prefixes MND and DLG with different schemas, so adopt the numbers of the book whose file you copy.
An unlisted action is undelegated, the lowest ceiling governs, and Level 3 Bounded needs a codified playbook and a decision point outside the agent.
A rise is a recorded decision by a named authority; a fall is immediate.
8 min
The autonomy budget and the register
A ceiling says what the agent may do; a budget says how much of that allowance it may keep.
The observer counts faulty actions, not the agent; review at 70 per cent, demotion by one level at 100 per cent.
The register and the reversibility test show whether a delegation can be withdrawn.
12 min
Observers, seeds and stop paths
Three tests: verification independent of action, an observer not dependent on the observed system, a stop path that works when the platform does not.
A check that has never failed has not been shown to work, so seeded faults, gaps and errors give a measured catch rate.
A stop that works by telling the agent to stop is a request, not a control.
The record of a failed drill is worth more than a policy that has never been exercised.
10 min
The agent as a principal
One identity per agent, issued by a broker outside its runtime, short-lived and bound to a task.
The permission manifest is the agent's declared intent; the containment profile is the platform's commitment.
A read-only switch in a tool server is a convenience; the hard limit is the permission of the identity behind it.
8 min
Why the operator's AI is Tier 0
Credentials, runbooks, telemetry and the stop path meet in the operator's AI.
Its controls are designed for reach and not intent.
Level 4 Autonomous is never used for an irreversible action on production data, outside an authorised window, to disable observation or the stop path, or to decide about a named person's access to work.
What the audience takes away
Mandate per agent, profile per service: an unlisted action is undelegated and the lowest ceiling governs.
An observer the agent cannot write and a stop path outside the platform are tested, timed and dated.
Containment must hold whether or not the manifest is obeyed, because it is designed for reach and not intent.
Module 7 · Part VII · People, Organisation and Society · 50 minutes
Who decides, who can do it, who can contest it, and what to believe
The lecture carries the argument of Part VII. The tools about people work only under limits agreed with employee representatives: a record that cannot be used for ranking, pay or discipline can be shared widely enough to be useful. A role charter fixes decision rights, a competence record conditions autonomy, a Management Decision Record names the human decider and a contestation record gives the person a reviewer outside the line. The same discipline is applied to belief: a claim is graded and labelled, held in a register with an owner and triggers, and debated in four steps.
12 min
Roles and competence as architecture
A role charter states decision rights with a time limit and names what is never delegated.
A competence framework counts the lower of the unassisted and the AI-assisted level.
Competence conditions read only levels and validity, and lower an agent's ceiling when too few evidenced holders remain.
The first thing to agree with employee representatives is what the record may not be used for.
13 min
Decisions about people: before, after and in dispute
Before: the delegation profile and the decision-rights file fix what a system may do per management function, M1 Direction to M5 Care.
After: the Management Decision Record shows a named human decider, the basis and the route to contest.
In dispute: a reviewer is never the decider, and a contest is never an input to evaluation.
Level 4 Autonomous is never used for M3 Consequence, and an adverse consequence is never above Level 1 Assisted.
8 min
What no single decision shows
A disparate-impact test, agreed with the representatives, looks for group disadvantage on every release.
The change-class annex keeps a works agreement true as the system changes.
Care tools protect development and rest as constraints, not as intentions.
12 min
Weighing evidence about threats and futures
The evidence ladder has five rungs: fiction, argument, laboratory demonstration, incident in the wild, pattern at scale.
The rung and the label observable, expected or speculation are kept in separate fields.
The threat register holds no probability; it holds rung, label, exposure and influence, with triggers in both directions.
The constructive debate ends in cruxes with owners and no-regret actions.
5 min
The common thread
Figures about people are reported at team level unless the person asks for their own.
Reversibility is the posture for what cannot be evidenced, and the stop path outside the system is the common no-regret action.
What the audience takes away
Agree prohibited uses first: a record that cannot rank or discipline can be shared widely enough to be useful.
Every decision about a person has a named human decider, a route to contest and a reviewer outside the line.
Grade the evidence, label the outlook, name an owner and write the trigger that would change your mind.
Module 8 · Part VIII · Experience and Conclusions · 40 minutes
One design, many dialects: building and judging a toolbox
The lecture carries the argument of Part VIII. A toolbox is not built from a list of tools: its order follows the obligation or risk that is already present and has no tool. A cautious buyer and a builder take up the same tools in a different order and leave different things out on purpose. Read side by side, the ten volumes show one design in many dialects: a shared anatomy, linked identifiers, evidence age, independence and earned autonomy. The gaps concern names, numbers, locations and dates, and a practitioner can act on them at once.
10 min
The order follows the gap
Nordvik Region starts by making a procured high-risk system legible: inventory entry, tier, decision record with retirement criteria.
Hansa Mutual starts by bounding agents that already act: mandate manifest and delegation profile.
What is left out is part of the design and is recorded with the condition under which it returns.
8 min
Three measures of a toolbox
Evidence age: the share of tools in use whose evidence is within its clock.
Adoption: use by the unit for which the tool was chosen, the team at Nordvik Region and the market at Hansa Mutual.
Retirements against stated criteria: a year with none means that no tool was reviewed.
The toolbox grows with delegation, and the measure that matters most at Level 3 is the one that can fail.
10 min
Five patterns across ten volumes
A shared anatomy and identifier families that link records into chains.
Evidence age: a claim without a date is not a claim the organisation can make.
Independence: a check is evidence only if the checker can fail in ways the checked does not share.
Autonomy that is earned, budgeted and revocable.
7 min
Gaps, dialects and what the series does not ship
Thirty-two prefix families appear in two or more volumes, and only the AI Decision Record has reserved ranges.
The series provides texts, records and procedures, not software: 227 of 240 own tools are publishing scripts.
No finding was a disagreement about a conclusion; they concern names, numbers, locations and dates.
5 min
Monday
Read the Origin row, take the template with its version, and record a decision where the series gives two defaults.
Reserve identifier ranges, treat a script shown in a chapter as a design, and date every claim with an independence statement.
What the audience takes away
Start from the obligation or risk that has no tool, not from the catalogue.
Judge a toolbox by the age of its evidence, its adoption and its retirements.
The tools exist in the volumes; a toolbox adds the name, the owner, the test and the date.
