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.

  1. 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.

    1. Server-enforced authorization
    2. Designing maker–checker workflows
    3. Audit trails as product infrastructure

Notebook · 04 published

Writing through the work.

Solutions, tradeoffs, and the reasoning underneath systems that need to hold up.

Tag
Format