Story: Clean ores.synthetic to the component clean standard
Table of Contents
This page documents a story in Sprint 30, carried unfinished from Sprint 28 at close. It captures the goal, current status, acceptance criteria, and the tasks that compose it.
1. Goal
ores.synthetic 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.synthetic joins COMPONENTS_UNDER_TEST. Order 28 of 35 in the sprint 26 component clean-up, tier 3 (domain component).
2. Status
| Field | Value |
|---|---|
| State | DONE |
| Parent sprint | Sprint 30 |
| Now | Nothing. |
| Waiting on | Nothing. |
| Next | Nothing. |
| Last touched | 2026-11-08 |
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.synthetic is listed in
COMPONENTS_UNDER_TEST, andcheck_component_drift.py --allpasses.
4. Tasks
| Task | State | Start | End | Description |
|---|---|---|---|---|
| Bring ores.synthetic to the clean standard | DONE | 2026-09-23 | 2026-11-08 | Work ores.synthetic through the Component Clean Standard in order and record each item. |
5. Notes
- Survey on 2026-09-23: 9 entity, junction or operation models; 319 C++ files outside tests, 252 of them generated (78%); 54 messaging headers, 9 of them hand-written.
6. Decisions
- Every task is done, the component is under the drift gate and it reports no drift. (review at sprint 30 start, 2026-11-08.)