94 lines
3.3 KiB
Markdown
94 lines
3.3 KiB
Markdown
# Remaining Route Conflict Correction Design
|
|
|
|
> Date: 2026-04-19
|
|
> Status: Draft
|
|
> Upstream Report: `docs/superpowers/reports/2026-04-19-102-full-sweep-improvement-coverage-delta-report.md`
|
|
|
|
## Design Intent
|
|
|
|
Resolve the remaining `4` route conflicts from the follow-up `102` sweep without reopening the broader full-sweep improvement roadmap.
|
|
|
|
The design answers:
|
|
|
|
`which of the remaining G3/G2 vs host_bridge_workflow conflicts should be corrected, and which should be formally adjudicated as valid host-bridge workflows?`
|
|
|
|
## Fixed Input
|
|
|
|
The fixed input set is exactly the `4` misclassified records from `tests/fixtures/generated_scene/full_sweep_improvement_followup_2026-04-19.json`:
|
|
|
|
| Scene | Expected group | Expected archetype | Current inferred archetype |
|
|
| --- | --- | --- | --- |
|
|
| `95598报修工单日管控` | `G3` | `paginated_enrichment` | `host_bridge_workflow` |
|
|
| `95598重要服务事项报备统计表` | `G3` | `paginated_enrichment` | `host_bridge_workflow` |
|
|
| `台区线损台区月度高负损预测` | `G2` | `multi_mode_request` | `host_bridge_workflow` |
|
|
| `配网支撑月报(95598抢修统计报表)` | `G3` | `paginated_enrichment` | `host_bridge_workflow` |
|
|
|
|
## Scope Guardrails
|
|
|
|
1. do not add new scene families
|
|
2. do not reopen timeout work
|
|
3. do not reopen readiness-before-report work
|
|
4. do not update `scene_execution_board_2026-04-18.json`
|
|
5. do not promote scenes automatically
|
|
6. do not weaken `G6` host-bridge real-sample pass
|
|
7. do not weaken `G2` or `G3` canonical / real-sample pass
|
|
8. do not make `host_bridge_workflow` lose when it is the only complete contract
|
|
|
|
## Route Decision Model
|
|
|
|
Each conflict must be assigned exactly one final route decision:
|
|
|
|
1. `route-corrected-to-g3`
|
|
2. `route-corrected-to-g2`
|
|
3. `valid-host-bridge-workflow`
|
|
4. `board-expectation-stale`
|
|
5. `route-conflict-unresolved`
|
|
|
|
## Evidence Rules
|
|
|
|
### G3 Wins Over G6 Only When
|
|
|
|
1. business endpoint evidence is present
|
|
2. pagination evidence is present
|
|
3. response path evidence is present
|
|
4. at least one of enrichment, join-key, or export workflow evidence is present
|
|
5. host bridge evidence is subordinate rather than the only execution path
|
|
|
|
### G2 Wins Over G6 Only When
|
|
|
|
1. line-loss / electricity business signal is present
|
|
2. mode or prediction signal is present
|
|
3. request contract can be inferred
|
|
4. host bridge evidence is subordinate rather than the only execution path
|
|
|
|
### G6 Remains Valid When
|
|
|
|
1. host bridge action is the only complete execution path
|
|
2. callback / localhost dependency dominates the workflow
|
|
3. business-chain evidence does not close the expected G2/G3 contract
|
|
|
|
## Expected Deliverables
|
|
|
|
1. route conflict decision JSON
|
|
2. route conflict correction report
|
|
3. bounded routing regression tests if implementation correction is needed
|
|
4. follow-up probe result for the same `4` records
|
|
|
|
## Completion Criteria
|
|
|
|
This design is complete when:
|
|
|
|
1. all `4` conflicts have explicit final decisions
|
|
2. corrected routes are verified by targeted generation probes
|
|
3. valid host-bridge cases remain documented rather than forced into G2/G3
|
|
4. existing `G2/G3/G6` regressions still pass
|
|
|
|
## Out of Scope
|
|
|
|
1. full `102` sweep rerun unless explicitly required after route correction
|
|
2. timeout optimization
|
|
3. new family creation
|
|
4. login / host runtime implementation
|
|
5. execution board status sync
|
|
|