61 lines
2.0 KiB
Markdown
61 lines
2.0 KiB
Markdown
# G2 Candidate Batch Alignment Report
|
|
|
|
## Scope
|
|
|
|
This round continues the roadmap Track D and Track E mainline work for `G2`.
|
|
|
|
It converts the current line-loss family progress into a formal repo-local batch asset instead of leaving the state split across separate markdown reports only.
|
|
|
|
## Delivered
|
|
|
|
Added or updated:
|
|
|
|
1. `tests/fixtures/generated_scene/g2_candidate_batch_2026-04-18.json`
|
|
2. `tests/g2_candidate_batch_test.rs`
|
|
3. `tests/fixtures/generated_scene/p1_family_manifest.json`
|
|
4. `tests/fixtures/generated_scene/p1_family_results.json`
|
|
5. `tests/fixtures/generated_scene/scene_ledger_status_2026-04-18.json`
|
|
6. `tests/scene_generator_p1_family_test.rs`
|
|
7. `tests/scene_ledger_status_test.rs`
|
|
|
|
## Batch Meaning
|
|
|
|
The batch asset now freezes the current `G2` line-loss family status as:
|
|
|
|
1. one `P0` anchor baseline
|
|
2. four promoted expansion baselines
|
|
3. one deferred queue item
|
|
|
|
The promoted expansion baselines are:
|
|
|
|
1. week-only mode variant
|
|
2. mixed linked workflow variant
|
|
3. comparison crosscheck variant
|
|
4. diagnosis drilldown variant
|
|
|
|
## Deferred Scope
|
|
|
|
`G2-D` remains deferred in this round because the current representative sample still does not expose a stable business endpoint contract.
|
|
|
|
That stays within the roadmap plan boundary and does not force non-contract-first implementation work into the current mainline.
|
|
|
|
## Validation
|
|
|
|
Passed:
|
|
|
|
1. `cargo test --test g2_candidate_batch_test -- --nocapture`
|
|
2. `cargo test --test scene_generator_p1_family_test -- --nocapture`
|
|
3. `cargo test --test scene_ledger_status_test -- --nocapture`
|
|
4. `cargo test --test scene_generator_family_policy_test -- --nocapture`
|
|
|
|
## Outcome
|
|
|
|
`G2` now matches the same Track D and Track E asset shape already established for `G3`:
|
|
|
|
1. representative baseline
|
|
2. promoted expansion baselines
|
|
3. formal batch asset
|
|
4. current-status ledger overlay
|
|
|
|
That means the remaining roadmap work can continue from a stable asset baseline instead of reconstructing `G2` progress from scattered markdown reports.
|