# G6 G7 G8 Family Asset Sync Report

## Scope

This round does not change `G6/G7/G8` runtime contracts themselves.

It promotes the three boundary families into formal family-level assets so they are no longer only protected by implementation tests.

## Synced Assets

Updated:

1. `tests/fixtures/generated_scene/p1_family_manifest.json`
2. `tests/fixtures/generated_scene/p1_family_results.json`
3. `tests/fixtures/generated_scene/family_expansion_policy.json`
4. `tests/scene_generator_p1_family_test.rs`
5. `tests/scene_generator_family_policy_test.rs`

## Result

`G6`, `G7`, and `G8` are now represented at the same family-asset layer as the existing mainline families.

That means the repo now preserves these facts as first-class assets:

1. `G6` is an independent `host_bridge_workflow` family
2. `G7` is an independent `multi_endpoint_inventory` family
3. `G8` is an independent `local_doc_pipeline` family
4. none of them should fall back into `G1`, `G1-E`, or `G3`

## Policy Position

The policy asset now separates:

1. mainline groups: `G1/G2/G3`
2. boundary-runtime groups: `G6/G7/G8`
3. deferred groups: `G4/G5`

This matches the current roadmap state:

1. mainline capability growth still centers on `G1/G2/G3`
2. `G6/G7/G8` are no longer just reassignment notes; they now have code-backed runtime contracts and family-level preservation

## Validation

Passed:

- `cargo test --test scene_generator_p1_family_test -- --nocapture`
- `cargo test --test scene_generator_test -- --nocapture`
- `cargo test --test scene_generator_family_policy_test -- --nocapture`
- `cargo test --test scene_generator_canonical_test -- --nocapture`

## Outcome

The roadmap has moved past pure boundary reassignment.

`G6/G7/G8` now exist as synchronized family assets with:

1. representative migration baselines
2. results records
3. policy placement
4. regression protection