Cross repo isolation

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

@@ -4,7 +4,7 @@ type: workplan
 title: "Provenance-Aware Characteristic Rebuild"
 domain: capabilities
 repo: repo-scoping
-status: active
+status: done
 owner: codex
 topic_slug: foerster-capabilities
 created: "2026-05-01"
@@ -195,7 +195,7 @@ Acceptance criteria:
 
 ```task
 id: RREG-WP-0009-T07
-status: todo
+status: done
 priority: medium
 state_hub_task_id: "7afd6550-e4a4-4a8a-94bf-d974b0ccb8d2"
 ```
@@ -216,7 +216,7 @@ Acceptance criteria:
 
 ```task
 id: RREG-WP-0009-T08
-status: todo
+status: done
 priority: high
 state_hub_task_id: "05077f3d-d40d-45fd-865c-0924407beb4f"
 ```
@@ -256,3 +256,24 @@ Acceptance criteria:
   analysis while preserving approved characteristics.
 - key-cape is documented as the motivating failure mode without hard-coding
   product-specific behavior into the scanner.
+
+## Cross-Repository Analysis Isolation
+
+```task
+id: RREG-WP-0009-T10
+status: done
+priority: high
+```
+
+Validate that analyzing one repository never depends on approved maps,
+candidate graphs, facts, chunks, or derived scope data from any other
+repository in the registry database.
+
+Acceptance criteria:
+- A repository with stale approved characteristics cannot influence fresh
+  candidate generation for another repository.
+- Candidate graph, observed fact, and content chunk lookups remain scoped by
+  repository and analysis run.
+- Tests cover a poisoned-repo scenario where repo A contains old LLM/provider
+  characteristics and repo B still generates only its own repository-owned
+  candidates.