Fusion council decisions and evidence: practice drills

Exercises for deciding when a model council helps, framing bounded decisions, invoking Fusion, validating providers and completion artifacts, reconciling disagreement, handling failures, and defining a verified first implementation slice.

These exercises practice choosing when a local model council is worth the time, writing a bounded prompt, and confirming the council output was used before implementation.

Use a real software project when possible. Keep the task narrow enough that the council can compare concrete choices.

Exercise 1: Decide Whether Fusion Fits

For each task, choose use Fusion or skip Fusion.

Task Use / Skip Why
Choose between three billing webhook idempotency strategies
Fix a typo in a button label
Review auth/session refresh-token architecture before implementation
Compare one model outage fallback plan against another
Run one known formatter command
Debug a bug with three plausible causes and incomplete logs
Implement an exact requested API shape
Review a risky checkout refactor before editing

Write:

# Fusion Fit

- task:
- decision:
- why disagreement helps or does not help:
- evidence available:
- likely verification:
- use Fusion? yes/no:

Rule:

If disagreement cannot change the decision, skip Fusion.

Exercise 2: Write The Decision Question

Pick one software decision:

  • billing webhook idempotency
  • checkout saved payment method architecture
  • auth/session refresh-token rotation
  • model outage fallback
  • risky refactor plan

Fill out:

# Decision Question

## Goal

## Candidate Strategies

-
-
-

## Current Evidence

-
-
-

## Constraints

-
-
-

## Verification

-
-

## What Disagreement Should Decide

Check it:

Can a model reasonably disagree about this?
Can repo evidence settle the disagreement?
Can the final answer name a first implementation slice?

Exercise 3: Ask For $fusion

Rewrite this vague request:

Use Fusion to review auth.

Into a strong request that asks the agent to:

  • use the $fusion skill
  • list providers first
  • write a prompt file
  • dry-run if command shape is uncertain
  • run the full configured panel
  • wait for terminal provider states
  • read summary.json and final.md
  • report consensus and disagreement
  • avoid implementation until after the council output is reconciled

Draft:

Use the $fusion skill.

...

Exercise 4: Provider And Prompt Preflight

Run or ask an agent to run:

fusion-high --list-providers
fusion-high --dry-run --file path/to/prompt.md

Fill out:

# Fusion Preflight

- selected preset:
- provider ids:
- prompt file:
- dry-run command:
- output location:
- any missing provider:
- any auth warning:
- safe to run? yes/no:

Exercise 5: Confirm The Agent Waited

After a Fusion run, fill this out from the agent's report.

# Wait Check

- Fusion session path:
- summary.json read? yes/no:
- final.md read? yes/no:
- providers reached terminal states? yes/no:
- terminal states:
  -
  -
  -
- any quota-limited provider:
- any failed or timed-out provider:
- did the agent act from partial panel output? yes/no:
- did implementation start only after final artifacts were read? yes/no:

Weak answer to reject:

One model had a good answer, so I continued.

Strong answer:

I waited for summary.json and final.md, then reconciled consensus and disagreement with repo evidence.

Exercise 6: Extract Council Disagreement

From final.md or the agent summary, fill out:

# Council Review

## Consensus

-
-

## Disagreement

| Topic | Position A | Position B | What evidence decides? |
| --- | --- | --- | --- |
| | | | |

## Hidden Risks

-
-

## Missing Tests

-
-

## Recommendation

- chosen path:
- why:
- what to avoid:
- rollback:

Question:

What did the disagreement change about the implementation plan?

Exercise 7: Turn Council Output Into A First Slice

Write the implementation slice.

# First Slice After Fusion

- chosen strategy:
- files to inspect:
- files likely to change:
- tests to add or update:
- verification command:
- rollback note:
- risks left for later:
- what the council disagreed about:
- why this slice is safe enough to try:

Do not include broad roadmap work unless it blocks the first slice.

Exercise 8: Quota Or Provider Failure Drill

Choose a recovery.

Failure Recovery
one provider quota-limited
one provider timed out
final.md missing
summary.json says interrupted
prompt file accidentally included secrets
provider ids were wrong
agent used --only without being asked
agent started editing while Fusion was still running
final answer ignored disagreement

Recovery options:

  • continue with degraded panel
  • name the missing voice
  • read partial artifacts only as failure evidence
  • rerun after fixing provider ids
  • rewrite prompt without secrets
  • ask for summary.json and final.md
  • stop implementation and wait
  • rerun full panel
  • extract consensus and contradictions

Fill one out:

# Failure Recovery Detail

- failure:
- likely cause:
- command or artifact to inspect:
- recovery:
- how to know recovery worked:

Exercise 9: Compare Fusion To Other Workflows

Choose the right workflow.

Scenario Workflow Why
broad repo architecture review needing packed code context
compare three generated checkout UI candidates
choose idempotency strategy before implementation
capture exact browser bug moment
find code paths with one search tool
convert a screen recording into repro steps
compose a careful prompt before launch

Options:

  • Oracle PackX
  • Prompt Builder
  • Section 6 variations
  • Fusion
  • Video workflow
  • Agent markers
  • Imps

Exercise 10: Final Check

Use this checklist before trusting the result.

# Final Fusion Check

- Fusion was the right tool? yes/no:
- skill was invoked? yes/no:
- provider list checked? yes/no:
- prompt file written? yes/no:
- dry-run used when uncertain? yes/no:
- full configured panel run? yes/no:
- providers reached terminal states? yes/no:
- summary.json read? yes/no:
- final.md read? yes/no:
- consensus captured? yes/no:
- disagreement captured? yes/no:
- recommendation reconciled with repo evidence? yes/no:
- verification command named? yes/no:
- private artifacts protected? yes/no:
- ready for implementation? yes/no:

Source references