03 · Independent assurance and decision boundary
Guardian
Check whether an exact consequential action on an exact state is authorized and supported by evidence.
Designed for
Product owners, engineering teams and organisations using AI-assisted development for consequential work.
Why it exists
Technical capability is too easily mistaken for authority to act.
- Stale approval or evidence
- Self-review and wrong-state action
- Unclear release and activation boundaries
How it works
Guardian flow
- Candidate
- Evidence
- Independent review
- Guardian decision
- Authorized next step
Product evidence
A concise passport
- Purpose
- Check whether an exact consequential action on an exact state is authorized and supported by evidence.
- Current product state
- Qualified assurance capability in active development
- Evidence basis
- Guardian architecture, controls and deterministic test evidence.
- Human-controlled or bounded
- Guardian does not by itself perform semantic review, enforce every external system, or grant merge, deployment or activation permission.
What it does
A bounded product response
- Binds decisions to exact candidate state
- Separates authority from capability
- Requires independent evidence and review where applicable
- Fails closed when consequential state is unknown
Product relationship
Part of a wider system
Conceptual product relationships; this diagram does not claim active technical integration.
- Evidence preserves attributable support for decisions
- Custodian can execute only a separately bounded authorized change
- Orchestrator can route work to the decision boundary
Next step
Explore with the right expectation
Product is evolving to the next product version.