Research Question: RQ-workflow-model
Does the quality of a TDD workflow depend on the model — is there a universally best workflow, or do different workflows swap places depending on the model?
claim-office-example-mapping
| n, run dates | Correctness | Cost | ||
|---|---|---|---|---|
| ↑ | ○ | ↑ | ↓ | |
| model: opus-4-7-no-thinking · exact-subagents-v1-cctest listn = 10, 2026-05-10 → 05-15 | 67% ± 36 🏆 | 10.0 ± 5.33 | 100% 🏆10/10 | $37.06 ± 8.53 |
| model: opus-4-6-portkey-no-thinking · exact-subagents-v1-cctest listn = 4 of 5, 2026-05-19 | 92% ± 8 🏆 | 13.8 ± 1.26 | 100% 🏆4/4 | $96.75 ± 15.03 |
| model: opus-4-7-no-thinking · exact-single-context-v1-cctest listn = 9, 2026-05-08 → 05-15 | 97% ± 9 🏆 | 14.6 ± 1.33 | 100% 🏆9/9 | $9.97 ± 2.96 🏆 |
| model: opus-4-6-portkey-no-thinking · exact-single-context-v1-cctest listn = 5, 2026-05-11 → 05-12 | 87% ± 30 🏆 | 13.0 ± 4.47 | 100% 🏆5/5 | $100.23 ± 9.52 |
| model: opus-4-7-no-thinking · exact-hybrid-v1-cctest listn = 5, 2026-05-15 | 100% ± 0 🏆 | 15.0 ± 0.00 | 100% 🏆5/5 | $26.52 ± 6.72 |
| model: opus-4-6-portkey-no-thinking · exact-hybrid-v1-cctest listn = 15, 2026-05-19 | 68% ± 33 🏆 | 10.1 ± 4.90 | 87%13/15 | $52.40 ± 57.35 |
Runs behind this table
- 2026-05-08_15-43-45_claim-office-example-mapping_v5-exact-single-context_opus-4-7-no-thinking
- 2026-05-08_15-54-26_claim-office-example-mapping_v5-exact-single-context_opus-4-7-no-thinking
- 2026-05-08_16-04-50_claim-office-example-mapping_v5-exact-single-context_opus-4-7-no-thinking
- 2026-05-10_03-35-32_claim-office-example-mapping_v4-exact-subagents_opus-4-7-no-thinking
- 2026-05-10_04-51-56_claim-office-example-mapping_v4-exact-subagents_opus-4-7-no-thinking
- 2026-05-10_06-11-58_claim-office-example-mapping_v4-exact-subagents_opus-4-7-no-thinking
- 2026-05-10_14-27-28_claim-office-example-mapping_v4-exact-subagents_opus-4-7-no-thinking
- 2026-05-10_15-33-36_claim-office-example-mapping_v4-exact-subagents_opus-4-7-no-thinking
- 2026-05-10_16-33-29_claim-office-example-mapping_v4-exact-subagents_opus-4-7-no-thinking
- 2026-05-11_23-37-29_claim-office-example-mapping_v5-exact-single-context_opus-4-6-portkey-no-thinking
- 2026-05-11_23-37-46_claim-office-example-mapping_v5-exact-single-context_opus-4-6-portkey-no-thinking
- 2026-05-12_04-57-39_claim-office-example-mapping_v5-exact-single-context_opus-4-6-portkey-no-thinking
- 2026-05-12_07-44-08_claim-office-example-mapping_v5-exact-single-context_opus-4-6-portkey-no-thinking
- 2026-05-12_07-48-00_claim-office-example-mapping_v5-exact-single-context_opus-4-6-portkey-no-thinking
- 2026-05-12_23-14-06_claim-office-example-mapping_v5-exact-single-context_opus-4-7-no-thinking
- 2026-05-15_03-50-02_claim-office-example-mapping_v4-exact-subagents_opus-4-7-no-thinking
- 2026-05-15_04-46-00_claim-office-example-mapping_v4-exact-subagents_opus-4-7-no-thinking
- 2026-05-15_05-48-04_claim-office-example-mapping_v4-exact-subagents_opus-4-7-no-thinking
- 2026-05-15_06-41-11_claim-office-example-mapping_v4-exact-subagents_opus-4-7-no-thinking
- 2026-05-15_07-08-48_claim-office-example-mapping_v5-exact-single-context_opus-4-7-no-thinking
- 2026-05-15_07-20-00_claim-office-example-mapping_v5-exact-single-context_opus-4-7-no-thinking
- 2026-05-15_07-33-51_claim-office-example-mapping_v5-exact-single-context_opus-4-7-no-thinking
- 2026-05-15_07-42-55_claim-office-example-mapping_v5-exact-single-context_opus-4-7-no-thinking
- 2026-05-15_07-54-40_claim-office-example-mapping_v5-exact-single-context_opus-4-7-no-thinking
- 2026-05-15_10-11-23_claim-office-example-mapping_v6-hybrid_opus-4-7-no-thinking
- 2026-05-15_10-42-09_claim-office-example-mapping_v6-hybrid_opus-4-7-no-thinking
- 2026-05-15_11-26-09_claim-office-example-mapping_v6-hybrid_opus-4-7-no-thinking
- 2026-05-15_12-14-30_claim-office-example-mapping_v6-hybrid_opus-4-7-no-thinking
- 2026-05-15_12-51-19_claim-office-example-mapping_v6-hybrid_opus-4-7-no-thinking
- 2026-05-19_00-33-23_claim-office-example-mapping_v4-exact-subagents_opus-4-6-portkey-no-thinking
- 2026-05-19_00-33-23_claim-office-example-mapping_v4-exact-subagents_opus-4-6-portkey-no-thinking-3
- 2026-05-19_00-48-02_claim-office-example-mapping_v4-exact-subagents_opus-4-6-portkey-no-thinking
- 2026-05-19_00-48-02_claim-office-example-mapping_v4-exact-subagents_opus-4-6-portkey-no-thinking-2
- 2026-05-19_10-28-16_claim-office-example-mapping_v6-hybrid_opus-4-6-portkey-no-thinking
- 2026-05-19_10-28-16_claim-office-example-mapping_v6-hybrid_opus-4-6-portkey-no-thinking-2
- 2026-05-19_10-28-16_claim-office-example-mapping_v6-hybrid_opus-4-6-portkey-no-thinking-3
- 2026-05-19_10-28-16_claim-office-example-mapping_v6-hybrid_opus-4-6-portkey-no-thinking-4
- 2026-05-19_10-28-16_claim-office-example-mapping_v6-hybrid_opus-4-6-portkey-no-thinking-5
- 2026-05-19_17-10-58_claim-office-example-mapping_v6-hybrid_opus-4-6-portkey-no-thinking
- 2026-05-19_17-10-58_claim-office-example-mapping_v6-hybrid_opus-4-6-portkey-no-thinking-2
- 2026-05-19_17-10-58_claim-office-example-mapping_v6-hybrid_opus-4-6-portkey-no-thinking-3
- 2026-05-19_17-10-58_claim-office-example-mapping_v6-hybrid_opus-4-6-portkey-no-thinking-4
- 2026-05-19_17-10-58_claim-office-example-mapping_v6-hybrid_opus-4-6-portkey-no-thinking-5
- 2026-05-19_17-10-58_claim-office-example-mapping_v6-hybrid_opus-4-6-portkey-no-thinking-6
- 2026-05-19_17-10-58_claim-office-example-mapping_v6-hybrid_opus-4-6-portkey-no-thinking-7
- 2026-05-19_17-10-58_claim-office-example-mapping_v6-hybrid_opus-4-6-portkey-no-thinking-8
- 2026-05-19_18-06-14_claim-office-example-mapping_v6-hybrid_opus-4-6-portkey-no-thinking
- 2026-05-19_18-19-31_claim-office-example-mapping_v6-hybrid_opus-4-6-portkey-no-thinking
Findings
Findings: RQ-workflow-model — Workflow × Model Interaction
Data basis: claim-office-example-mapping, external verification suite (verification_pct).
Origin: extracted from the localization RQ research/workflow-dev/5.1-correctness-regression/
(formerly F-regression.6), where the subagents-v1/single-context-v1/hybrid-v1 columns arose as a side finding.
F-workflow-model.1 — subagents-v1 and hybrid-v1 Swap Places Depending on the Model
| Workflow | opus-4-7 (n) | opus-4-6 (n) |
|---|---|---|
| exact-subagents-v1-cc | 0.67 (10) | 0.93 (5) 🏆 |
| exact-single-context-v1-cc | 0.97 (9) | 0.87 (5) |
| exact-hybrid-v1-cc | 1.00 (5) 🏆 | 0.68 (15) |
verification_pct: higher = better; 🏆 per model column — the core statement is precisely that the winner changes depending on the model.
subagents-v1 and hybrid-v1 are complementary in a model-dependent way: exact-hybrid-v1-cc is the opus-4-7 optimum (1.00) but unstable on opus-4-6 (0.68). exact-subagents-v1-cc is stable on opus-4-6 (0.93) but bimodal on opus-4-7 (0.67). single-context-v1 is the least model-sensitive of the three (0.97 / 0.87) — it never wins a column, but it is also the only workflow that stays above 0.85 on both models.
There is therefore no universally best workflow on this axis — the choice is
model-dependent. The practice recommendation derived from this is in
research/workflow-dev/model-recommendation-matrix.md.
F-workflow-model.2 — Mechanism: Orchestration Delegation vs. Explicit Subagent Prompt
exact-hybrid-v1-cc delegates orchestration to the model (skill-invocation semantics in the shared context).
opus-4-7 masters this. opus-4-6 loses the claim half of the spec in ~40 % of the runs — the model
implements only quote and ignores claim entirely (grep "claim\|payout\|deductible" claim-office.ts = 0 hits, tests_total nevertheless 19–23 because the internal tests only cover
quote).
subagents-v1 gives every phase an explicit subagent prompt. opus-4-6 benefits from this structure, while opus-4-7 becomes "overly creative" on subagents-v1 and more often picks the wrong reading when facing ambiguities.