Principles
Design principles

Eight rules we build by.

These are the tiebreakers. When a decision is close, one of these decides it — the same way, every time. They govern how we build and write; for what the runtime enforces, see the product principles.

  1. Outcomes over implementation.

    Lead with what the reader gets. Mechanism belongs in docs.

  2. Evidence over assertion.

    Every claim we make about a decision must be independently verifiable.

  3. Portability over lock-in.

    The proof format is open. Receipts outlive the vendor.

  4. Enforce before you explain.

    Governance decides what may happen. Logs describe what did. Never confuse the two.

  5. One idea per surface.

    A page that defends one idea is remembered. A page that defends five is not.

  6. Subtraction is a feature.

    New primitives must unlock a customer or simplify the story. Otherwise defer.

  7. Boring where it matters.

    Production infrastructure should feel predictable, not clever.

  8. Write for the person on call.

    Tired reader, late hour, something on fire. If it needs a second read, rewrite it.

  9. Evidence is append-only.

    Governance state changes are receipted. Operational data is disposable. Nothing you can delete was ever evidence.