Story: Clean ores.refdata to the component clean standard
Table of Contents
This page documents a story in Sprint 26. It captures the goal, current status, acceptance criteria, and the tasks that compose it.
1. Goal
ores.refdata meets the Component Clean Standard: every item: All, Protocol and Entity pass, each item that does not apply is recorded with its reason, and ores.refdata joins COMPONENTS_UNDER_TEST. Order 24 of 35 in the sprint 26 component clean-up, tier 3 (domain component).
2. Status
| Field | Value |
|---|---|
| State | BACKLOG |
| Parent sprint | Sprint 26 |
| Now | Not yet started. |
| Waiting on | Nothing. |
| Next | Start the task. |
| Last touched | 2026-09-23 |
3. Acceptance
- Every checklist item that applies to a component of kind Entity passes, with its evidence recorded on the task.
- Every item that does not apply is recorded as not applicable, with the reason.
- Every generator defect found is fixed at its source, with a regression test.
- ores.refdata is listed in
COMPONENTS_UNDER_TEST, andcheck_component_drift.py --allpasses.
4. Tasks
| Task | State | Start | End | Description |
|---|---|---|---|---|
| Bring ores.refdata to the clean standard | BACKLOG | Work ores.refdata through the Component Clean Standard in order and record each item. |
5. Notes
- Survey on 2026-09-23: 77 entity, junction or operation models; 2134 C++ files outside tests, 2079 of them generated (97%); 363 messaging headers, 8 of them hand-written.
- The canonical protocol is adopted and 97% of the C++ is generated. Finish the remainder: the hand-written messaging files, the web half (out of scope, since there is no TypeScript UI), and joining the registry, which a branch removed.