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.

spec/TargetRevenueLicenseConcept.md

@@ -5,6 +5,8 @@
 **Document status:** Concept draft  
 **Purpose:** Define the conceptual foundation for a revenue-triggered software licensing and monetization framework.  
 
+**Related documents:** Living scope in `SCOPE.md`; product requirements in `specs/ProductRequirementsDocument.md`; schema orientation in `specs/TechnicalSpecificationDocument.md`; provisional open-question defaults in `specs/OpenQuestions-WorkingDefaults.md`. Normative extracts under `specs/` (WP-0003) will freeze day-to-day terminology without relocating this file (`spec/` vs `specs/` policy: README / TSD §7).
+
 > The Target Revenue Framework combines a source license and trust service to monetize software development transparently until a defined target is satisfied and the governed release automatically becomes permissively open source.
 
 ---
@@ -1184,5 +1186,3 @@ The Target Revenue Framework is built around a deliberately small kernel:
 - one constrained extension interface.
 
 This minimal structure allows the framework to remain understandable while supporting a broad and evolving monetization canon. Development licensing funds the protected improvement. Operations monetization pays for operating the capability. Other forms of value creation may be integrated through explicit profiles and extensions. Target degeneration provides an eventual path into the commons when commercial validation is weak. The Trust Service enables consistent learning and adoption through centralization first, while open records and deterministic calculations prepare the framework for later federation.
-
-xxx