Reconcile product inputs and prove durable work handoffs

2026-08-06 16:06:18 +02:00
parent 69ba1037bf
commit b269791c48
18 changed files with 523 additions and 40 deletions
@@ -14,6 +14,7 @@ volatile repository, issue, release, or maturity counts as current facts.
 | Which institutional concepts and owners form the target architecture? | [Institutional Governance Target Architecture](INSTITUTIONAL_GOVERNANCE_TARGET_ARCHITECTURE.md) |
 | Which end-to-end proofs should guide implementation? | [Reference Journey Program](REFERENCE_JOURNEY_PROGRAM.md) |
 | What is the reconciled state now? | [Strategy Status](STRATEGY_STATUS.md) |
+| Which collected ideas and user stories inform the product direction? | [Product Input Register](PRODUCT_INPUT_REGISTER.md) |

 The dated [Strategic Review](STRATEGIC_REVIEW_2026-08-05.md) explains why the
 current reset and sequencing were chosen. It is an assessment record, not a
@@ -74,3 +75,5 @@ be edited manually.
   repository. Meta documentation defines cross-module outcomes and contracts.
 6. A new strategy document must replace, narrow, or link an existing source;
   it must not introduce a parallel roadmap.
+7. The Product Input Register preserves external idea and story notes, but only
+   Gitea issues carry live priority, ownership, and implementation state.