Iteration directions and admission conditions¶
The next iteration continues from the 0.2.1 software preview, preserving the identity of historical sealed candidates. See subsequent iterations for 71 planning entries and dependencies; maintain status and exits only in the original delivery ledger, without a completion percentage here.
Order |
Main delivery |
Admission and exit conditions |
|---|---|---|
Software first |
Baseline navigation, configuration explanations, plan previews and complete development operations |
B, C01, T01 and X01; reuse existing capabilities without new ledgers or test frameworks |
Independent integration |
External SoC/provider, CMake and installed SDK |
P; explicit package identity reaches resolution, queries, generation and build, with actual external-fixture success |
Practical use |
Industrial-control and bounded secure-networking reference systems |
D/R/N/S/E; first fix exact combinations and budgets, then complete failure, shutdown and recovery |
After equipment connection |
Stations and per-mode measurements for the three initial and source-reference boards |
H; follow HIL status and original station contracts; tooling is not physical execution |
Integration exit |
Current clean-source candidate, SDK, bilingual docs and publication |
L; execute the complete plan and independent offline reproduction without inheriting preview or old-candidate qualification |
Conditional extensions |
Exact PM, a second sensor, filesystems and advanced SoC modes |
R04/R05/S06 and original SoC exits; enter through actual requirements and hardware contracts |
Codex owns all maintenance domains without requiring named accounts. Retain independent review for high-risk changes; execute actual RED before GREEN for new behavior and fixes, using GoogleTest/GoogleMock for C contracts. Judge server rules from actual readback and retain product policy and private data in external projects.