Assurance
Your model makes claims — about who may read which rows, what must hold before a command runs, which errors an endpoint can return. Assurance derives every one of them as a checkable obligation and reports how many are actually backed by evidence, so an architecture description becomes a control rather than documentation.
- What assurance isYour model makes claims. An entity says which callers may read its rows. A command says what must be true before it runs and which errors it can return. A route says who may call it. A capability says…
- ObligationsAn obligation is one falsifiable statement your model makes about runtime behaviour. You never write one: they are derived from what you have already declared, which is what makes the list complete…
- The dimensionsThe report scores your model along several independent dimensions. They are kept separate on purpose: a single number would let a strong showing in one hide a hole in another, and the holes are the…
- Assurance levelsA level answers "what is now true?". Each one is a set of enumerable, checkable predicates, so a claim of "Level 2" decomposes into specific statements someone can audit one at a time — which is what…
- Running the reportIn the Workshop, the Assurance lens shows this continuously — nothing to run. From a terminal, one command: