# G3 Real Sample Output Contract Verification Design

> Date: 2026-04-19
> Upstream Closure: [2026-04-19-g3-real-sample-runtime-contract-correction-closure-report.md](D:/data/ideaSpace/rust/sgClaw/claw-new/docs/superpowers/reports/2026-04-19-g3-real-sample-runtime-contract-correction-closure-report.md)

## 1. Intent

The previous bounded plan corrected the remaining runtime-scope failure for the real sample `95598工单明细表`.

The sample now:

1. routes inside `G3 / paginated_enrichment`
2. passes `g3_runtime_scope_compatible`
3. reaches `readiness.level = A`

The remaining mainline gap is narrower:

`output_contract_not_verified`

This design defines the next bounded scope:

`G3 real-sample output / contract verification`

## 2. Observed Remaining Gap

The generated real-sample package now satisfies structural routing and runtime-scope gates, but the validation layer still does not verify:

1. whether the main request / enrichment split matches the intended business output
2. whether recovered join keys and dedupe rules are semantically correct rather than merely syntactically complete
3. whether the current generated artifact shape matches the expected real-sample output contract

This means the remaining risk is no longer routing or runtime admission. It is output-level contract fidelity.

## 3. Scope Guardrails

1. do not reopen the completed `G3` archetype-correction scope
2. do not reopen the completed `G3` runtime-scope correction scope
3. do not broaden this work into `G8` runtime implementation
4. do not reopen `G3` family expansion or new fixture growth
5. do not open `G4 / G5`
6. do not weaken fail-closed behavior to force a `passed` record

## 4. Correction Target

The bounded target is:

1. verify the real-sample `G3` output contract against the intended business contract
2. narrow the remaining mismatch from generic `output_contract_not_verified` to:
   - verified pass
   - or a smaller named contract/output mismatch
3. keep the result anchored in the real sample rather than repo-local proxies

## 5. Expected Outcome

After this scope:

1. the validation record for `rsv-g3-001` should either become `executed-pass`
2. or it should retain `executed-mismatch` with a more specific output/contract code than the current generic label
3. the next scope recommendation should move away from `G3` unless a genuinely narrower output issue remains