Story: Clean ores.ore 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.ore 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.ore joins COMPONENTS_UNDER_TEST. Order 31 of 35 in the sprint 26 component clean-up, tier 3 (domain component).
2. Status
| Field | Value |
|---|---|
| State | DONE |
| Parent sprint | Sprint 26 |
| Now | Nothing. |
| Waiting on | Nothing. |
| Next | Not a standard item: bring ores.marketdata to a regenerable state, then move the series key shape entity to it. |
| Last touched | 2026-09-26 |
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.ore is listed in
COMPONENTS_UNDER_TEST, andcheck_component_drift.py --allpasses.
4. Tasks
| Task | State | Start | End | Description |
|---|---|---|---|---|
| Bring ores.ore to the clean standard | STARTED | 2026-09-26 | Work ores.ore through the Component Clean Standard in order and record each item. |
5. Investigations
Two point-in-time records, written while working the task. They say what the component looked like and what was decided on the day; they are not the description of the component. Read the component models for that.
| Investigation | Question it answered |
|---|---|
| ores.ore design and documentation survey | What is the component made of, where does its structure deviate from the component architecture, and which documents were stale? |
| what ores.ore should own | Which of the jobs the component does are ORE representation work, who actually consumes each, and where should the rest live? |
6. Notes
- Survey on 2026-09-23: 1 entity, junction or operation models; 114 C++ files outside tests, 28 of them generated (24%); 11 messaging headers, 6 of them hand-written.
- Most of the C++ is the ORE domain generated from the XSD by xsdcpp, a different generator. Record that boundary under B03.