Parity Workflow
How contributors turn upstream behavior into Gormes changes without overclaiming.
Parity Workflow
- Identify the active upstream contract.
- Record exact source refs or transcript evidence.
- Add or refine a progress row when the behavior is not already tracked.
- Build the smallest runtime slice with tests.
- Update user docs only for behavior that is actually available.
Do not treat progress.json validation as proof that the product feature is finished. It proves the roadmap data is structurally valid.