Specs-First Workflow
Use the internal specs as the implementation source of truth before changing behavior.
OpenSana uses a specs-first workflow for behavior changes.
Expected Process
- find the relevant spec in
docs/specs - implement against that spec
- update the spec if behavior changes
- update public docs when the change is user-visible
Why It Exists
This keeps product behavior, implementation details, and contributor expectations aligned.
Practical Rule
Do not treat public docs as the sole implementation contract. Public docs explain behavior. Specs define the detailed internal rules contributors should preserve.