Story: Clean ores.reporting 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.reporting 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.reporting joins COMPONENTS_UNDER_TEST. Order 27 of 35 in the sprint 26 component clean-up, tier 3 (domain component).
The clean-standard pass ran here, and the defects and gaps it recorded and did not close split to Complete the ores.reporting clean-up at the sprint 26 close on 2026-10-05.
2. Status
| Field | Value |
|---|---|
| State | DONE |
| Parent sprint | Sprint 26 |
| Now | Nothing. |
| Waiting on | Nothing. |
| Next | Nothing. |
| Last touched | 2026-10-05 |
On 2026-10-05, at the sprint 26 close, this story was reworded to the
clean-standard pass it delivered and closed DONE: the checklist record is
complete, G08 and H03 are fixed, V08 is closed, and ores.reporting is
listed in COMPONENTS_UNDER_TEST. The recorded defects and gaps are
Complete the ores.reporting
clean-up, and its seven tasks moved there.
3. Acceptance
- The checklist items that apply to a component of kind Entity pass, except the items Complete the ores.reporting clean-up carries: the
report_definitionsshell menu collision, P01, S01, G04, H01, M04, M08 and V04's remaining causes, each with its evidence recorded on the task. - Every item that does not apply is recorded as not applicable, with the reason.
- Every generator defect the pass closed is fixed at its source, with a regression test; the shared template defects it recorded are carried by the successor story.
- ores.reporting is listed in
COMPONENTS_UNDER_TEST, andcheck_component_drift.py --allpasses.
4. Tasks
| Task | State | Start | End | Description |
|---|---|---|---|---|
| Bring ores.reporting to the clean standard | DONE | 2026-09-26 | 2026-09-27 | Work ores.reporting through the Component Clean Standard in order and record each item. |
| Make the scheduler-triggered report execution correct | DONE | 2026-09-26 | 2026-09-27 | Determine how much of the report instance FSM and the report execution workflow is actually implemented, and make the scheduler-to-report trigger path work end to end. |
| Close the ores.reporting checklist | DONE | 2026-09-27 | 2026-09-27 | Task for: Clean ores.reporting to the component clean standard |
| Scaffold the remaining ores.reporting clean-up | DONE | 2026-09-27 | Task for: Clean ores.reporting to the component clean standard |
5. Notes
- Survey on 2026-09-23: 5 entity, junction or operation models; 163 C++ files outside tests, 127 of them generated (77%); 28 messaging headers, 8 of them hand-written.