Six months later, someone asks why.
The release happened. The team moved on. Now someone needs to know who approved it and what they knew.
Back to the decisionWithout the check
A search through memory.
Messages, files and recollections explain parts of the story. The basis of the decision is difficult to reconstruct.
Why did we release it?
Someone must remember.
- Who approved?
- Check the email thread.
- Approved what?
- Search the chat.
- Which rule?
- Find the old instructions.
- What did they see?
- Find the attachments.
- AI permission?
- Ask the person who set it up.
- What happened?
- Ask whoever was there.
With ZAK checking the action
The decision stays with the work.
Inspect the request, permission, evidence and recorded result together.
A decision should come with its reasons.
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.
Here is where
the ending changes.
01
A request comes in.
The action has a purpose, an owner and information it relies on.
02
A decision is made.
The record identifies the action, the required authority and the evidence used.
03
Later, the question comes back.
Return to the exact record. Distinguish permission to act from what was actually completed.
Where could this happen
in your work?
Start with one action you would like to delegate. Work out the permission, the connection and the evidence it needs.
What would this require in practice?
A receipt supports the bounded event it records. Provider acceptance is not proof of delivery, and a matching local hash is not signer verification. The evidence pages explain these distinctions.
The scenes show the decision being explained. They are not screenshots of a connected product or records of a customer incident.
Read the scope and limits