Story: Clean ores.iam 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.iam 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.iam joins COMPONENTS_UNDER_TEST. Order 23 of 35 in the sprint 26 component clean-up, tier 3 (domain component).
2. Status
| Field | Value |
|---|---|
| State | STARTED |
| 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.iam is listed in
COMPONENTS_UNDER_TEST, andcheck_component_drift.py --allpasses.
4. Tasks
| Task | State | Start | End | Description |
|---|---|---|---|---|
| Bring ores.iam to the clean standard | STARTED | 2026-09-26 | Work ores.iam through the Component Clean Standard in order and record each item. |
5. Notes
- Survey on 2026-09-23: 20 entity, junction or operation models; 392 C++ files outside tests, 297 of them generated (75%); 68 messaging headers, 11 of them hand-written.
- The reference component: the standard was written from its sprint 25 work, and it is the only component under test. Verify it against every item and record the result, so the standard is proved on the component it came from.