make boundaries obvious
Systems should make ownership and data flow understandable.
reference/principles.md
# Principles
design for failure
Queues, retries, observability, idempotency, and rollout behavior are part of the system.
stay close to implementation
Architecture decisions improve when the person making them understands code and production behavior.
optimize for other engineers
Good abstractions remove work without hiding important behavior.