Guide 03 · SEPARATION OF DUTY
LOCAL SIMULATION · TEST_ONLYLocal validation surfaces and fixed fixtures only · no real login, organizational authority, operational API, external execution, or authority issuance
Separate requester, reviewer, approver, and executor.
Make role conflicts and reviewer requirements explicit so one actor cannot silently own every authority step.
Do not collapse four events into one
- REQUESTED — who requested what and why
- REVIEWED — who inspected which evidence and conditions
- APPROVED or DENIED — which policy basis produced the disposition
- EXECUTED — which actor performed the action and what occurred
Check role conflicts explicitly
- 01Compare requester and reviewer
Do not allow the same actor when policy requires independent review.
- 02Compare approver and executor
Keep execution separate for actions that require it.
- 03Inspect the delegation chain
Reject self-approval and circular delegation.
- 04Apply step-up conditions
Higher-impact scope may require additional assurance or another reviewer.
Reviewer context is versioned evidence
A displayed name or role label does not establish reviewer authority. Bind reviewer context to current policy, delegation, session assurance, scope, and revocation revision.