A single model can give a clean answer and still miss the important edge. Use a model council when the cost of a missed perspective is higher than the cost of waiting.
Fusion is one way to run that pattern locally: send the same bounded software question to multiple configured providers, wait for the panel to finish, let a finalizer compare the outputs, then make the engineering decision from the result and the repo evidence.
It can take all of those results and then fuse them with the model of your choice. Meaning that… you get multiple opinions, you can have them kind of argue against each other.
— John Lindquist
Use It For Hard Decisions
Reach for a council when you need coverage, not speed.
Good fits:
- large PR review
- architecture tradeoffs
- migration risk
- security and performance tension
- uncertain debugging plans
- product or UX direction
- release or rollback strategy
Do not use it as a way to avoid making the call. The council gives you independent critique. You still own the decision.
The Mental Model
bounded software question
-> independent model/provider perspectives
-> terminal provider states
-> finalizer comparison
-> summary.json
-> final.md
-> engineering decision
Fusion is for coverage, not voting. The useful output is not "three models said yes." The useful output is consensus, contradictions, unique warnings, blind spots, and a final recommendation you can test against the codebase.
Run The Whole Council
Partial panel output is not the answer. Wait until every configured provider reaches a terminal state before treating the result as complete.
Before a real run:
- inspect the configured providers
- run the full configured panel by default
- wait for terminal provider states
- read
summary.json - read
final.md - reconcile the result with repo evidence
Panel artifacts are partial until the final artifacts exist.
Handle Missing Voices
A missing provider degrades the council. It does not automatically make the run useless.
If a provider times out, fails, or hits quota after artifacts exist, treat that as a missing voice. The final answer can still be useful if it clearly names the degraded state and enough other panel output exists to synthesize.
Do not hide the missing voice. Make it part of the decision record.
Good Software Uses
Large PR review:
Use Fusion to review this PR before merge.
Context:
- PR summary:
- changed files:
- risky areas:
- test output:
- migration or rollout notes:
Ask the council to find:
- correctness risks
- security risks
- performance risks
- missing tests
- rollout or rollback issues
- documentation gaps
Return:
- consensus
- contradictions
- unique warnings
- blind spots
- recommended merge/block decision
- verification commands
Architecture tradeoff:
Compare three implementation paths for the billing webhook fix:
A. provider event id dedupe
B. invoice-level lock
C. processing ledger
Include:
- failure modes
- migration risk
- rollback path
- test plan
- operational logging
- smallest shippable recommendation
Role/perspective panel:
Review this auth/session plan from four perspectives:
1. security reviewer
2. performance reviewer
3. migration reviewer
4. product/UX reviewer
Each reviewer should name what could go wrong.
The finalizer should preserve minority warnings instead of flattening them.
Optional Pattern: Stop-Hook Review
For risky AFK work, a prompt marker can ask a later stop gate to review changes before reporting done.
Conceptual shape:
When the user prompt includes #review, write a marker for the stop hook.
At Stop:
- check whether files changed
- check whether the marker exists
- run Fusion against the diff
- read summary.json and final.md
- report the council result before claiming done
Treat this as a pattern until the hook payload, marker passing, and current CLI behavior are verified.
Copyable Artifact: Fusion Decision Brief
Decision:
[the software decision under review]
Why a council:
[what one model might miss]
Context:
- repo area:
- changed files:
- relevant tests:
- logs or traces:
- constraints:
Provider instructions:
Ask each provider to review independently.
Preserve disagreements.
Do not treat majority agreement as proof.
Finalizer instructions:
Return:
- consensus
- contradictions
- unique warnings
- blind spots
- recommended decision
- verification commands
- confidence and why
Human decision:
[accept / revise / block / run another pass]
Claim Boundaries
Hosted products may publish their own benchmark or cost claims for panel-style research workflows. Treat those as vendor claims that need dated citations. Local Fusion is a local CLI pattern inspired by the same panel/finalizer idea, not proof of hosted benchmark results.
I can, like, anecdotally vouch for the results, but I can't give you some sort of percentage of… it's this close to Fable or whatever.
— John Lindquist
Provider availability, pricing, quotas, auth, and data handling are local/account-dependent. Verify current provider terms before sending private code or prompts.
Model council output is advisory. Tests, code review, product judgment, and repo evidence still decide the work.