Towards systematic evidence

workplans/RREG-WP-0003-automatic-repository-exploration.md

@@ -201,3 +201,28 @@ Follow-up hardening completed 2026-04-29: candidate graphs are normalized before
 storage so duplicate or overlapping LLM/deterministic claims merge into one
 review item while preserving stronger descriptions, confidence, source refs, and
 nested capabilities/features/evidence.
+
+## P1: Characteristic Scope And Evidence Model
+
+```task
+id: RREG-WP-0003-T10
+status: in_progress
+priority: medium
+state_hub_task_id: "0d3fa9e0-bb3e-4bf2-bf8d-4681c5b7bdf5"
+```
+
+Evolve the registry model from a fixed `Ability → Capability → Feature →
+Evidence` presentation into a repository characteristic model with a single
+`Scope` root above abilities. Treat abilities, capabilities, and features as
+characteristics at different abstraction levels. Evidence should be modeled as
+support for a characteristic and may reference observed facts or lower-level
+characteristics; upward references from features to capabilities/abilities should
+be avoided, and same-layer references should be allowed but treated as a review
+smell that can indicate suboptimal granularity or organization.
+
+Acceptance: the UI explains and presents scope as the root of the approved
+characteristic tree, separates features from evidence/support under each
+capability, and allows manual tuning of evidence in a way that makes the support
+relationship clear. The data model has an additive path toward characteristic
+references so existing approved/candidate workflows continue to work while
+future iterations can link evidence to facts or deeper characteristics.