Continuous assurance over point-in-time approval
Sign-off at a gate describes a system that no longer exists by the time it reaches users. Assurance is a standing property of the system, re-earned with every change.
Umbrella · 2001-2026
The Assurance Manifesto
Agile gave us delivery. Digital gave us governance. Confidence gave us evidence. Assurance holds all three to one accountable thread: from intent, through delivery, to behaviour in production.
6 values · 12 principles · sits over Agile (2001), Digital (2016) and Confidence (2026)
One umbrella, three lineages.
Assurance does not replace the manifestos beneath it. It binds them, so that agility, governance and evidence answer the same question together.
2001
Agile
How we build
Iteration, collaboration and working software as the measure of progress.
Read it →2016Digital
What we build and govern
Think, Make, Check — digital delivery, adaptive outcomes and continuous governance.
Read it →2026Confidence
How we know it works
Probabilistic evidence over binary assertion in AI-infused systems.
Read it →Across all three, we have come to value:
Evidence chains over isolated artefacts
A test result, a metric, a review and a release note only mean something when they connect back to the intent they serve. Assurance is the thread, not the individual bead.
Accountable ownership over delegated inspection
Assurance cannot be outsourced to a stage, a team or a tool. The people changing the system are the people answerable for what is known about it.
Outcome integrity over output compliance
Meeting the specification is not the same as serving the intent. Assurance asks whether the outcome held, for real users, under real conditions.
Transparent uncertainty over manufactured certainty
Where evidence is thin, say so and quantify it. Hidden gaps become incidents; declared gaps become decisions.
Assurance as design over assurance as inspection
Observability, traceability and evaluability are architectural concerns. Systems that cannot explain themselves cannot be assured.
Twelve principles of assurance
- 01
Assurance begins at intent. If we cannot state what good looks like, nothing downstream can prove it.
- 02
Every claim about a system carries its evidence, its freshness, and its confidence.
- 03
Prefer fewer, better questions over more, cheaper checks.
- 04
Assurance flows continuously through delivery — it is not a phase, a gate, or a department.
- 05
Risk, not coverage, decides where effort goes.
- 06
Production is the primary source of truth; everything before it is a rehearsal.
- 07
Automate the evidence, not the judgement.
- 08
Treat governance as a product: usable, versioned, and improved by feedback.
- 09
Assure the whole system — people, process, models and services compose into behaviour no component owns.
- 10
Make failure survivable before making it unlikely.
- 11
Retire evidence that no longer earns trust as readily as we retire code.
- 12
Assurance is complete when a team can honestly answer: do we know enough to ship, and how would we know if we were wrong?
The through-line
Working software, adaptive outcomes and calibrated evidence are the same commitment seen from three angles. Assurance is what you call it when you refuse to drop any of them.