# G6 Host Bridge First Slice Report

> Date: 2026-04-18
> Scope: `G6` classification and fail-closed safety slice

## Summary

The first `G6` implementation slice is complete.

This round did not attempt runnable host bridge execution. It implemented the safer first step:

1. new `host_bridge_workflow` archetype
2. deterministic host bridge action detection
3. `G6` classification priority over `G1-E`
4. `G6` readiness gates
5. fail-closed generation behavior
6. regression protection so ordinary localhost export noise does not become `G6`

## Assets Updated

1. `src/generated_scene/ir.rs`
2. `src/generated_scene/analyzer.rs`
3. `src/generated_scene/generator.rs`
4. `tests/fixtures/generated_scene/g6_host_bridge_workflow/index.html`
5. `tests/scene_generator_test.rs`

## Behavioral Result

The new representative fixture validates:

1. `workflowArchetype = host_bridge_workflow`
2. host bridge action evidence includes `sgBrowerserJsAjax2`
3. host runtime evidence includes `localhost:13313`
4. business callbacks include `getWorkOrderToDoList`
5. business callbacks include `queryMeterPlanFormulateApp`
6. generation fails closed with `host_bridge_workflow`

## Boundary Correction

The implementation initially exposed one boundary risk: plain `localhost:*` noise could promote a scene to `G6`.

The classifier was corrected so `G6` requires explicit host bridge action evidence. `localhost:*` alone remains host-runtime evidence and does not define the archetype.

## Validation

Executed:

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

All target regressions passed.

## Result

`G6` is now safely separated from `G1/G1-E` at classification time.

The family is intentionally still fail-closed until a real host bridge runtime contract is designed and implemented.