53 lines
1.5 KiB
Markdown
53 lines
1.5 KiB
Markdown
# G1-E Candidate Batch Alignment Report
|
|
|
|
## Scope
|
|
|
|
This round keeps the roadmap inside the `G1-E` Track B and Track D boundary.
|
|
|
|
It does not add a third `G1-E` implementation sample. It converts the already validated representative plus first expansion state into a formal candidate-batch asset.
|
|
|
|
## Delivered
|
|
|
|
Added or updated:
|
|
|
|
1. `tests/fixtures/generated_scene/g1e_candidate_batch_2026-04-18.json`
|
|
2. `tests/g1e_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_ledger_status_test.rs`
|
|
|
|
## Batch Meaning
|
|
|
|
The batch asset now freezes the current `G1-E` status as:
|
|
|
|
1. one promoted baseline
|
|
2. one promoted expansion
|
|
3. one queued downstream candidate
|
|
|
|
This keeps `G1-E` aligned with the same family-asset shape already used by `G2` and `G3`, without forcing unsupported expansion beyond the current evidence.
|
|
|
|
## Validation
|
|
|
|
Passed:
|
|
|
|
1. `cargo test --test g1e_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
|
|
|
|
`G1-E` now has:
|
|
|
|
1. representative baseline
|
|
2. promoted expansion baseline
|
|
3. formal candidate batch
|
|
4. synchronized Track E ledger overlay status
|
|
|
|
That completes the same core asset shape for the three roadmap mainline families:
|
|
|
|
1. `G1-E`
|
|
2. `G2`
|
|
3. `G3`
|