Skip to content

Decision principles

Created and maintained with AI agents. Humans own review and publication.

Proposed · human review required · r2

Context and default

Durable architecture means that change, failure, and loss of individual knowledge are survivable. It is not a promise that one stack lasts forever. Start with explicit boundaries, a small dependency surface, and an owner for every operational obligation. Prefer reversible decisions until stronger evidence justifies commitment.

Project profiles

Profile Starting point Obligations
Personal or exploratory Static site or one process, managed storage if needed Reproducible setup, secrets hygiene, export and restore
Product with real users Modular application, managed database, background worker when needed Service objectives, recovery test, deployment rollback, support owner
High traffic or many teams Measured partitioning, explicit contracts, capacity planning On-call coverage, load testing, isolation and migration plans
High consequence Any scale, including one user Threat model, auditability, retention, legal and domain review

Profiles describe constraints, not a maturity competition. A regulated small service may need stronger controls than a large public catalog. Record what you deliberately defer and the signal that will make it necessary.

Decision record

Every consequential choice names the problem, constraints, options, evidence, owner, expected costs, verification, and escape route. Separate a fact from an assumption and a local policy from an external standard. Set a review date and an observable trigger, such as sustained queue age beyond the agreed objective.

Verify and revisit

A new contributor must reproduce the development workflow, trace a user action to its data, and recover from a failed release. If only the original author or model session can explain the system, improve documentation and boundaries before adding components. Revisit decisions after incidents, material cost changes, product pivots, or changed legal obligations.

Choose and connect architectures · Scale from measurements · Governance and unanswered decisions

Primary evidence

owasp · observability · github-rulesets