Across the areas
Every decision record and every screen contract in the corpus, in one list each.
Rhythm 2.0
How Rhythm 2.0 will be built. Design answers one question — given what Planning says the product must do, how is each key concept realised and who is responsible for what? Choose a product area to see its modules; a module to see its domain objects, state models, workflows, contracts, screens and decisions.
Last updated 23 October 2026, 11:05 AM EDT · commit 0180126baf
2237 design artifacts are waiting on approval.
Open a product area to see how each of its modules is designed.
Every decision record and every screen contract in the corpus, in one list each.
Planning says what the product must do, feature by feature. Design makes the technical choices once, reviewably, and citable by everything they constrain. A downstream phase may elaborate an upstream decision; it may not contradict one or silently invent one.