Adapt specs and workplans to SWOT Stage 0 sequencing

Introduce SCOPE, expanded README, CONTRIBUTING, and provisional open-question
defaults. Rescope Trust Service work to offline schemas/fold/fixtures, add
normative core extraction workplan, and split PRD roadmap Phase 4 into
foundation vs hosted service. Sync workplans with State Hub.
This commit is contained in:
tegwick 2026-07-28 18:34:10 +02:00
parent 7286b52f07
commit 4496244bb8
16 changed files with 1252 additions and 227 deletions

View file

@ -125,6 +125,6 @@ The mature framework should be understandable enough for small projects, rigorou
This document defines the durable purpose and intended direction of the Target Revenue Framework repository.
**INTENT is stable and aspirational.** `SCOPE.md`, specifications, workplans, and implementation documents should describe what is actually being designed or built at a particular time. A gap between INTENT and current SCOPE is expected while the framework matures and should be treated as a visible maturity signal rather than resolved by weakening this document.
**INTENT is stable and aspirational.** [`SCOPE.md`](SCOPE.md), specifications, workplans, and implementation documents should describe what is actually being designed or built at a particular time. A gap between INTENT and current SCOPE is expected while the framework matures and should be treated as a visible maturity signal rather than resolved by weakening this document. Stage 0 scope, sequencing, and “done enough” criteria are maintained in `SCOPE.md` (as of 2026-07-28: concept + orientation specs + offline foundation; not production legal text or hosted Trust Service).
Changes to this file should represent a deliberate shift in what the Target Revenue Framework is meant to become, not ordinary scope evolution, implementation learning, or release planning.