Story: Clean ores.compute 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.compute 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.compute joins COMPONENTS_UNDER_TEST. Order 26 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 | Nothing. |
| Last touched | 2026-09-26 |
| End | 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.compute is listed in
COMPONENTS_UNDER_TEST, andcheck_component_drift.py --allpasses.
4. Tasks
| Task | State | Start | End | Description |
|---|---|---|---|---|
| Bring ores.compute to the clean standard | DONE | 2026-09-23 | 2026-09-26 | Work ores.compute through the Component Clean Standard in order and record each item. |
5. Notes
- Survey on 2026-09-23: 7 entity, junction or operation models; 258 C++ files outside tests, 189 of them generated (73%); 42 messaging headers, 9 of them hand-written.
6. Decisions
- Reshape the model where the standard demands it, rather than exempt the
component. The platform entity, the two telemetry tables as
current-state hypertables, and the work surface and telemetry protocol
as operation models all exist because an item could not pass without
them. The task records each, and the per-item decisions are in
clean-compute/decisions.tsv. - Fix a generator at its source, then refresh. Nine generator defects were fixed with seventeen cases; the two still open in the tooling are recorded against G07 with the artefacts they hold back.
- The five items the standard gained on 2026-09-25 apply to every component. B06, G07, H04, V07 and V08 came from the infrastructure survey, and this task runs them like the rest.
- A component is not clean until it runs. Every gate passed while the event pipeline dropped every notification and the grid dispatched nothing. Bringing the grid up and running the sample job end to end is part of this story's acceptance, not an extra.