Systems built.Decisions made visible.
Notes on the boundaries that decide, verify, and record — written while building systems that have to hold up.
Reading paths · 01 curated
Read them in order.
Some notes argue one idea together. Each path states what it claims, the order to read it in, and why every note sits where it does.
3 notes
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.
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.
Notebook · 04 published
Writing through the work.
Solutions, tradeoffs, and the reasoning underneath systems that need to hold up.
Tag
Format
Notes
03- Server-enforced authorizationHiding a button is not authorization. Permissions belong where protected data leaves the system.authorizationpermissionsaccess control
- Designing maker–checker workflowsStopping people approving their own changes is the easy part. An approval must cover exactly what was read, and count exactly once.approvalsstate machinesconcurrency
- Audit trails as product infrastructureA log helps you debug. An audit trail has to answer, months later, who asked, who approved, and what went live.audit trailsevidencedata integrity