Architecture Overrides
How to document intentional deviations from school-os defaults.
Use this file to record intentional deviations from school-os defaults.
Why this exists
The school-os is intentionally opinionated, but not rigid. Overrides are valid when they enable a better fit for a specific project requirement.
How to override safely
- Document the override in this file.
- Explain why the default is insufficient.
- Describe risks and rollback strategy.
- Add or update tests to protect the new behavior.
- If needed, add project-local rules in
`<project>/ARCHITECTURE.md`.
Override template
### Override: <name>
- **Scope:** <app/package/path>
- **Default being overridden:** <rule>
- **Reason:** <why this project needs it>
- **Risk:** <trade-offs>
- **Mitigation:** <tests/checks/docs>
- **Owner:** <name>
- **Date:** <YYYY-MM-DD>Active overrides
None yet.