Implement scope-derived candidate review infrastructure

This commit is contained in:
2026-05-16 00:26:29 +02:00
parent f4d782c997
commit ba2228e889
14 changed files with 1740 additions and 39 deletions

View File

@@ -31,7 +31,7 @@ abilities, and draft scope from facts, source-linked text, and existing
## Dataset Assessment
The current `var/repo-scoping.sqlite3` dataset contains eight repositories. The
The initial `var/repo-scoping.sqlite3` dataset contained eight repositories. The
new non-repo-scoping repositories all completed analysis, but only
`ops-warden` produced a candidate capability and feature. Railiance repos mostly
produced one candidate ability, zero candidate capabilities, zero candidate
@@ -59,7 +59,7 @@ Observed patterns:
```task
id: RREG-WP-0018-T01
status: todo
status: done
priority: high
state_hub_task_id: "dd00a642-7c69-4ae2-b7ac-954c31a1c72a"
```
@@ -80,7 +80,7 @@ Acceptance criteria:
```task
id: RREG-WP-0018-T02
status: todo
status: done
priority: high
state_hub_task_id: "01eb03da-7a0e-4e22-ae2d-7596752d178e"
```
@@ -106,7 +106,7 @@ Acceptance criteria:
```task
id: RREG-WP-0018-T03
status: todo
status: done
priority: high
state_hub_task_id: "fd572f4d-d2f6-4c85-bbf5-f77829fd6e6a"
```
@@ -129,7 +129,7 @@ Acceptance criteria:
```task
id: RREG-WP-0018-T04
status: todo
status: done
priority: high
state_hub_task_id: "286d96e0-ec5a-4a55-bb50-62d20ab25830"
```
@@ -152,7 +152,7 @@ Acceptance criteria:
```task
id: RREG-WP-0018-T05
status: todo
status: done
priority: high
state_hub_task_id: "80bc671c-2361-47e5-8135-7c945de66437"
```
@@ -175,7 +175,7 @@ Acceptance criteria:
```task
id: RREG-WP-0018-T06
status: todo
status: done
priority: medium
state_hub_task_id: "4b74a058-b759-42d2-a243-7134dd907093"
```
@@ -197,7 +197,7 @@ Acceptance criteria:
```task
id: RREG-WP-0018-T07
status: todo
status: in_progress
priority: medium
state_hub_task_id: "cd1a3c14-076b-42da-8319-48310a964611"
```
@@ -213,3 +213,30 @@ Acceptance criteria:
- Dependency graph element counts are non-zero for repositories with facts.
- The comparison report makes it easy to judge whether the new result is better
than the previous sparse output.
## Implementation Update
Implemented the comparison and generation infrastructure needed to rerun the
dataset:
- Added `repo-scoping assess-dataset` to summarize latest runs by facts,
chunks, candidate/approved hierarchy counts, graph coverage, document
presence, and sparse-hierarchy quality issues.
- Updated candidate generation so `SCOPE.md` one-liners and `Provided
Capabilities` blocks seed reviewable current-state abilities/capabilities,
while deterministic fact fallback now requires stronger configuration facts
and does not promote dependency-only repositories.
- Added review-only `INTENT.md`/`SCOPE.md` API and UI draft views. Missing
`INTENT.md` now produces an ambitious draft derived from scope/candidates
without writing the file.
- Added dependency graph fallback nodes/edges for candidate and draft
hierarchies so repos with facts no longer render empty just because approved
characteristics are absent.
- Added transparent quality criteria for template contamination and
scope-vs-intent separation; deterministic gates can require review but do not
accept registry truth.
The latest local assessment command currently sees nine repositories because
`vantage-point` has been added. It still reports old sparse Railiance candidate
counts because those stored analysis runs predate this implementation. T07 stays
open until the affected repositories are rerun and compared against the sparse
baseline.