The Permission Gate
You are here · Protocol 41
Shift briefing · Identity and Permission Wing
A user revokes access while a queued job still holds an old authorisation. Ensure subsequent actions respect the updated permission and leave an audit trail.
Read before the shift. It tells you what is at stake, never how to do it.
What you practise
Implement consent, authorisation, least privilege, retention, and deletion across the data lifecycle.
- Authorisation
- least privilege
- consent
- data lifecycle
- auditability
Decide Commit to a defensible choice under real constraints.
The facility for this shift
3 rooms, 4 stations, two hands.
- 01Identity HallIdentity terminal · Consent ledger
- 02Job Queue RoomJob queue
- 03Lifecycle RoomData lifecycle station
Compromised Signal · sealed
Something in this shift will change, and the briefing will not tell you what. You find it from the evidence, or your after-action review shows you where it was.
How the shift is assessed
3 criteria · 0 to 6
Scored from what you did: the evidence you checked, the stations you operated, the artifacts you produced and the gates you passed. The criteria are revealed in your after-action review, not before.
Capabilities evidenced
- JudgmentChooses proportionate actions and knows when to verify, abstain, or escalate.In 27 of 48
- ReliabilityTests, reproduces, validates, recovers, and produces consistent outcomes.In 39 of 48
- ResponsibilityProtects privacy, limits permissions, documents decisions, and blocks unsafe releases.In 23 of 48
Chamber III · Action Chamber
Build only what you can stand behind, and stop a release that is not safe.
Construct, integrate, evaluate, debug, secure, deploy, observe and responsibly operate AI-enabled systems.
Play Protocol 41 in first person, with the clock running.