Know where the evidence stops.
A useful evaluation makes the action, the connection and the limits clear.
Illustrated scenario · no live execution
Why did we release it?
Start with the decision record.
- Who approved?
- The appointed release owner.
- Approved what?
- Release 42 to the customer portal.
- Which rule?
- Release rule, version 7.
- What did they see?
- The change, functional checks, security review and rollback plan.
- AI permission?
- Prepare only. The release service had separate authority to deploy version 42.
- What happened?
- The release service recorded deployment of version 42 at 09:14.
Put it to work.
Start with what needs to happen. Make the next decision clear.
The check must be in the action path.
ZAK can enforce a decision only where the connected system respects that decision before executing. An action taken outside that path needs its own control.
Permission needs a real authority.
A recommendation from AI is advisory. It cannot grant permission by itself. The applicable policy, authority and evidence determine what can proceed.
A record needs its context.
A receipt describes a recorded outcome. To evaluate a production claim, inspect its origin, signer, evidence, storage and the action it refers to.
Public examples have a defined scope.
The examples explain decisions. Browser tools use local data and simulated requests. A successful local hash comparison does not establish that a business action occurred.
Recorded tests have a date.
The test catalogue preserves recorded results and limitations. It is not a live status page or a fresh deployment assessment.