At the start of every session working in this repository, read these documents in full and use them as governing design guidance for all analysis, code changes, reviews, and recommendations:
These documents are not optional background reading. They define the expected engineering standards for this repository.
Apply them concretely:
- Treat system behavior under failure, concurrency, networking, persistence, and observability as first-class design concerns.
- Treat data formats, schemas, and interfaces as long-lived contracts.
- Prefer simple, deep modules with strong boundaries and hidden implementation details.
- Eliminate accidental complexity, refactor when design debt appears, and avoid pushing complexity to callers.
- Measure and verify behavior instead of assuming it.
If a requested change appears to conflict with these precepts, call out the conflict explicitly and propose an approach that satisfies the request while preserving the design principles where possible.