Iteration directions and admission conditions¶
Current iteration follows actual measurements and original exit conditions. The complete strategy remains in later iterations and team execution; the original ledgers maintain per-task status. This page provides task entry points without duplicating status updates.
Order |
Work |
Authority for admission and exit conditions |
|---|---|---|
First |
Connect real stations for the three initial and source-reference boards; calibrate safe initial levels and clocks |
HIL status and original station/qualification contracts |
Next |
Measure existing IRQ/DMA/continuous-stream/cancellation-drain modes and full-load shutdown |
Original I/O, OS and SoC ledgers, and real traces for the same candidate |
Expand according to measurements |
New controllers/routes, broader H743 DMA/Cache and U575 DMA/security domains |
Original SoC exit conditions; first freeze ownership and failure contracts for each slice |
Design separately |
Running-state handoff, DVFS, deep STOP and genuine userspace I/O transport |
Original unimplemented items such as SOC-33–35; completion cannot be inferred from current fixed profiles |
Maintain delivery |
Tools, dependencies, SDK, documentation publication and recovery |
Original ledgers and exact-source execution records; accept software/publication/physical scope separately |
Codex owns all maintenance domains; role divisions allocate capabilities and capacity without inventing personal accounts. Local ownership files do not prove remote GitHub branch rules are enabled. Retain independent review for high-risk changes. New behavior and bug fixes require actual RED before GREEN, with GoogleTest/GoogleMock for C contracts. Product tasks, recovery, secure updates, manufacturing keys and proprietary PCBs belong in external projects.