one time bootstrap path

workplans/RREG-WP-0009-provenance-aware-characteristic-rebuild.md

@@ -23,8 +23,9 @@ dependency, import, or operational convention mentioned in its files.
 The target behavior is facts-first and provenance-aware:
 
 - Deterministic scanning observes facts without over-interpreting them.
-- Facts carry source roles such as product documentation, scope summary,
-  implementation source, dependency declaration, agent guidance, or CI/tooling.
+- Facts carry source roles such as intent summary, derived scope, product
+  documentation, implementation source, dependency declaration, agent guidance,
+  or CI/tooling.
 - Characteristic generation promotes only repository-owned utility unless the
   repository clearly acts as a facade or adapter for another capability.
 - Rebuild workflows can discard old approved characteristics and regenerate a
@@ -44,7 +45,12 @@ generation can distinguish product evidence from ambient context.
 
 Initial source roles:
 
-- `scope_summary`: `SCOPE.md` and other canonical scope files.
+- `intent_summary`: `INTENT.md` and other design-intent files that describe why
+  the repository should exist and what utility it is meant to provide.
+- `derived_scope`: `SCOPE.md` and other generated or curated current-scope
+  files. These are valuable context, but should not be treated as primary
+  evidence for regenerating characteristics unless a curator explicitly chooses
+  a bootstrap/import mode.
 - `product_documentation`: README, docs, specifications, user-facing guides.
 - `implementation_source`: code files owned by the repository.
 - `test_evidence`: test and acceptance files.
@@ -59,8 +65,10 @@ Initial source roles:
 Acceptance criteria:
 - Observed facts can carry a source role in metadata without breaking existing
   storage or API consumers.
-- `SCOPE.md` is indexed as `scope_summary` and gets high priority during
+- `INTENT.md` is indexed as `intent_summary` and gets high priority during
   candidate generation.
+- `SCOPE.md` is indexed as `derived_scope` and remains distinguishable from
+  source evidence and design intent.
 - Agent guidance files are classified separately from product documentation.
 - Content chunks preserve the fact source role used to produce them.
 
@@ -113,19 +121,24 @@ Acceptance criteria:
 
 ```task
 id: RREG-WP-0009-T04
-status: todo
+status: in_progress
 priority: high
 state_hub_task_id: "4f666cd6-471e-4af9-b53c-4f3d7a1d1973"
 ```
 
-Use canonical scope files and product documentation as stronger evidence for
+Use explicit intent files and product documentation as stronger evidence for
 expected repository utility than ambient config, CI files, dependency mentions,
-or agent instructions.
+agent instructions, or previously derived scope files.
 
 Acceptance criteria:
-- Candidate ability naming prefers `SCOPE.md` one-liner/core idea when present.
-- Candidate capability generation can extract explicit `Provided Capabilities`
-  blocks from `SCOPE.md`.
+- Candidate ability naming prefers `INTENT.md` one-liner/core idea when present.
+- Candidate capability generation can extract explicit intended capability
+  blocks from `INTENT.md`.
+- `SCOPE.md` is treated as derived current scope, not as ordinary evidence for
+  rebuilding the characteristic model from scratch.
+- Existing `SCOPE.md` files can be explicitly bootstrapped into initial
+  `INTENT.md` files when no intent file exists; this is a one-time migration
+  aid, not an ongoing equivalence between scope and intent.
 - README/docs/spec evidence is weighted above CI/tooling and generic config.
 - key-cape generates candidates centered on lightweight IAM, OIDC/PKCE profile
   enforcement, migration tooling, and LDAP/schema validation rather than LLM
@@ -226,7 +239,7 @@ Acceptance criteria:
 
 ```task
 id: RREG-WP-0009-T09
-status: todo
+status: in_progress
 priority: medium
 state_hub_task_id: "071f6d76-c92b-4ac1-825c-edcbef4bdbf6"
 ```