Outcomes over implementation.
Lead with what the reader gets. Mechanism belongs in docs.
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.
Lead with what the reader gets. Mechanism belongs in docs.
Every claim we make about a decision must be independently verifiable.
The proof format is open. Receipts outlive the vendor.
Governance decides what may happen. Logs describe what did. Never confuse the two.
A page that defends one idea is remembered. A page that defends five is not.
New primitives must unlock a customer or simplify the story. Otherwise defer.
Production infrastructure should feel predictable, not clever.
Tired reader, late hour, something on fire. If it needs a second read, rewrite it.
Governance state changes are receipted. Operational data is disposable. Nothing you can delete was ever evidence.