Task: Roll out the classification tool to all remaining components and delete stale docs
Table of Contents
This page documents a task in the Entity classification and drift baseline across all components story. It captures the goal, current status, acceptance, and any notes or results.
Goal
Narrowed 2026-08-04. Originally: extend the trusted, refdata-proven tool to
every remaining component, produce the full quantified drift baseline, and
retire everything the tool now supersedes. The re-scoping half is done —
each of the 14 ad hoc tasks was re-scoped directly against the codegen
component catalogue rather than a report (see the parent story's
Decisions). What remains: retire entity_coverage_matrix.org,
entity_evaluation_checklist.org, and entity_catalogue.org, and decide
whether the quantified classification report is still worth producing now
that 12 remediation stories already exist.
Status
| Field | Value |
|---|---|
| State | BACKLOG |
| Parent story | Entity classification and drift baseline across all components |
| Now | Not yet started. |
| Waiting on | Nothing. |
| Next | Decide whether the report is still worth producing; retire the 3 stale docs either way. |
| Last touched | 2026-08-04 |
Acceptance
- Each of the 14 ad hoc "Apply safe drift to X-cpp" tasks is closed as
covered: 12 re-scoped into their own entity classification and drift
baseline stories (one per component, composite components split into
subcomponent tasks), 1 (
ores.controller) ABANDONED as decommissioned. Done. entity_coverage_matrix.org,entity_evaluation_checklist.org, andentity_catalogue.orgare deleted; anything from them still useful is captured first (in the 12 stories' notes, or elsewhere).- (Optional) The classification tool is run across every remaining component and produces a combined drift report with per-component breakdowns and totals — only if judged still worth producing once the 12 stories close; not required to close this task if the per-component stories already supersede its value.
Plan
(Implementation strategy. Written when work starts; key decisions
are distilled into the parent story's * Decisions at close, but the
plan itself stays — it is the historical record of what we did.)
Notes
Test Scenarios
Manual QA scenarios (scaffolded via compass add test_scenario, run
through the QA Validation Runner panel) that verify this task. Link
new ones here as they're created; the scenario doc itself links back
via its "Verifies task" field.
| Scenario | State | Notes |
|---|---|---|
PRs
| PR | Title |
|---|---|
Review
| Comment summary | File | Decision | Notes |
|---|---|---|---|