English | νκ΅μ΄
fablize β run Opus like Fable

A Claude Code plugin that makes Opus (or any Claude model) see a task through to the end β with evidence and verification β as procedure, not as luck.
Why
When Fable 5 shipped, I ran a controlled comparison of Fable 5 and Opus 4.8 (an A/B set of 19 runs plus 26 real working sessions, ~1,500 tool calls). The finding:
- On closed, answer-bearing work (code, logic, builds), the two models were effectively tied.
- The gap appeared only on open-ended work, and its nature was "following an implication one step further."
- That depth is model capability β it could not be transferred by instructions or a harness. An injection experiment confirmed it: Opus could not reproduce the defects Fable found on its own.
- But the procedure of good work β actually running what you build, seeing it through, investigating systematically β does transfer.
fablize applies only the procedures whose effect was verified. It does not raise the model's ceiling; it makes the model reach its own ceiling.
What transfers and what doesn't
| Trait |
Transferable? |
Reason |
| Verification grounding (run & observe the artifact) |
β
shipped |
A procedure Opus skipped "not because it can't, but because it didn't." Injecting it raised render-verification behavior measurably. |
| Multi-story completion + evidence gate |
β
shipped |
A procedure β decompose, checkpoint, refuse completion without proof. |
| Systematic investigation (reproduce β hypotheses β causal chain) |
β
shipped |
A procedure β on par with what the strong model already does. |
| Early-stop prevention |
β
shipped |
A deterministic hook β catches "I'll do X" without doing it. |
| Out-of-spec defect discovery |
β not possible |
Capability. |