coulomb/repo-scoping
2
0
Fork 0
generated from coulomb/repo-seed
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Capture clean self-assessment regression signal

Browse Source
This commit is contained in:
Bernd Worsch
2026-05-15 17:15:35 +02:00
parent abcb2cebbc
commit 458eb410c4
6 changed files with 2958 additions and 3 deletions
Download Patch File Download Diff File Expand all files Collapse all files

6
docs/self-scoping/README.md
View File

@@ -11,6 +11,12 @@ instead of relying on memory or screenshots.
- `assessments/repo-scoping-known-bad-2026-05-15-run-39.json` captures the
known-bad self-analysis that promoted LLM-provider vocabulary into native
repo-scoping capability truth.
- `assessments/repo-scoping-post-wp0015-clean-2026-05-15.json` captures the
first clean, release-bound deterministic challenger after acceptance-boundary
and input-hygiene work. It remains a rejected regression because candidate
generation still collapses repo-scoping's native surfaces under the forbidden
provider-routing capability, but its source set no longer includes
`var/checkouts/` contamination.
- `workflow.md` explains how to run challenger assessments, interpret outcomes,
and decide whether to update the golden profile or fix the engine.
- `outcomes/` stores append-only reviewer decisions created from side-by-side

2775
docs/self-scoping/assessments/repo-scoping-post-wp0015-clean-2026-05-15.json Normal file
View File

File diff suppressed because it is too large Load Diff

36
docs/self-scoping/assessments/repo-scoping-post-wp0015-clean-2026-05-15.md Normal file
View File

@@ -0,0 +1,36 @@
# Self-Scoping Comparison: repo-scoping-challenger-run-1
- Status: `regression`
- Golden profile: `repo-scoping-golden-profile-v1`
- Target repo: `repo-scoping`
- Summary: Assessment repeats known or forbidden self-scoping patterns; prefer the golden profile until the engine is corrected.
## Missing Expected Capabilities
- Explore Dependency And Impact Graphs
- Generate And Maintain SCOPE.md
- Generate Reviewable Candidate Characteristics
- Index Source Content With Provenance
- Provide Scope Context To Downstream Agents
- Register And Track Repositories
- Review And Approve Candidate Characteristics
- Scan Repositories Into Observed Facts
- Search Compare And Export Approved Profiles
## Forbidden Native Capabilities Present
- Route LLM Requests Across Providers
## Known Regression Patterns
- `RREG-SELF-REG-001` LLM provider vocabulary promoted as native capability: Generated tree contains Route LLM Requests Across Providers as a repo-scoping capability.
- `RREG-SELF-REG-002` Native API and CLI surfaces attached under false capability: API or CLI surface features are nested below provider routing.
## Misplaced Features
- `HTTP API surface: possible API surface, GET /health, @app.get(, +49 more` under `Route LLM Requests Across Providers` (API): API/CLI surface is nested below provider-routing capability.
- `CLI command surface: CLI command build_parser, CLI command make_service` under `Route LLM Requests Across Providers` (CLI): API/CLI surface is nested below provider-routing capability.
## Matched Expected Capabilities
- None
## Review Hints
- Do not promote this assessment as a preferred baseline.
- Inspect forbidden capabilities and misplaced features first.
- Use the findings as signal for scanner, generator, or acceptance-policy changes.