# Track E Ledger Status Overlay Report

## Scope

This round does not rewrite the frozen workbook snapshot from `2026-04-18 16:48:05`.

It adds a current-status overlay asset so the roadmap Track E state can reflect the code-backed family baselines that were established after the workbook snapshot was frozen.

## Delivered

Added:

1. `tests/fixtures/generated_scene/scene_ledger_status_2026-04-18.json`
2. `tests/scene_ledger_status_test.rs`

## Why This Overlay Exists

By this point in the roadmap, the repo already contains code-backed baseline assets for:

1. `G2`
2. `G1-E`
3. `G3`
4. `G6/G7/G8` boundary-runtime families

But the original workbook snapshot still reflects an earlier mid-run state.

Track E therefore needs two layers:

1. frozen snapshot layer
2. current baseline overlay layer

## Current Mainline Overlay Status

The overlay now records:

1. `G2 = batch-expansion-promoted`
2. `G1-E = batch-expansion-promoted`
3. `G3 = batch-expansion-promoted`

And explicitly records promoted ledger-facing entries for:

1. the `G2` promoted baseline and promoted expansion fixtures
2. the `G1-E` promoted baseline
3. the `G3` promoted baseline
4. the current `G3` promoted expansion fixtures

## Validation

Passed:

1. `cargo test --test scene_ledger_status_test -- --nocapture`
2. `cargo test --test scene_ledger_snapshot_test -- --nocapture`
3. `cargo test --test scene_generator_family_policy_test -- --nocapture`

## Outcome

Track E now has a stable way to express both:

1. the original frozen `102`-scene workbook state
2. the current code-backed roadmap status

That means the next roadmap round can continue promoting candidates without losing visibility into which family baselines have already been formally established.