Series · 3 notes in reading order
Dependable boundaries
Three notes on where a system decides, how a second person verifies that decision, and what evidence remains once both have moved on.
What you should take away
You should be able to place the authorization decision, the approval requirement, and the audit record in a feature you are designing, and say which of the three is currently missing.
Start with “Server-enforced authorization”Server-enforced authorization
Hiding a button is not authorization. Permissions belong where protected data leaves the system.
Why here Start at the boundary. The server must enforce permission before a protected action can proceed.
Designing maker–checker workflows
Stopping people approving their own changes is the easy part. An approval must cover exactly what was read, and count exactly once.
Why here For changes that require independent review, a second person checks the proposal before it takes effect.
Audit trails as product infrastructure
A log helps you debug. An audit trail has to answer, months later, who asked, who approved, and what went live.
Why here An audit trail preserves the evidence needed to reconstruct who decided what and why.