Fusion decomposes one goal into a team of model-pinned subagents. A middle manager keeps the handoff lossless while every artifact is attested to what actually ran.
hermes plugins install BoredSexyJordan/fusion-marketplace#hermes hermes plugins enable fusion hermes fusion plan "ship the feature" hermes fusion run fusion/packet.json
The 1950s–70s management era died because the handoff between planner and doer was lossy in both directions. Fusion applies the fix that actually worked: boring middle managers, correctness-preserving handoffs, and a feedback loop that escalates decisions, not struggles.
A T0 model (Claude, GPT, Grok…) turns the goal into a validated packet: the team roster, each member's model + delegation kind, scope, and verification criteria. It never implements.
A cheap-but-careful MM strips any "prescribing the solution" noise from each worker prompt (hard gate), then hands one bounded, model-pinned task to each genius worker. Delegation kinds are pinned in the roster — nobody re-decides mid-run.
Each worker is a specialist with its own model, tools, and context. Tier boundaries are session boundaries: no model switching mid-turn. Handoffs are artifacts, never transcripts.
Every run writes harness.json receipts of exactly what models actually served — never the roster. The weekly scorer learns which team templates win per task type, so next week's recommendation is grounded in real fidelity.
Intelligence level is one axis. Claude writes cleaner prose, GPT is the numbers analyst, Grok counterbalances dynamic variables. Fusion picks character, not just IQ — and never asks a model to do what it's bad at.
Capability-driven selection, not bans. Cost, availability, and subscription-vs-API all weigh in.
Model pinned per roster member. Tier boundary = session boundary. No hijack bugs.
Workers hand back files. Handoffs are lossless because the unit of work is a file, not a summary.
Provenance comes from execution receipts, so the feedback loop never scores a template that didn't really run.
Fusion ships as a single marketplace plugin. The same packet and run-state contract runs on Hermes, Claude Code, Grok Build, and Codex.
hermes plugins install BoredSexyJordan/fusion-marketplace#hermes hermes plugins enable fusion hermes fusion plan "your goal" hermes fusion run fusion/packet.json
claude plugin marketplace add \ BoredSexyJordan/fusion-marketplace claude plugin install fusion-orchestrator@boredsexy-hermes # then, in a session: /fusion-run "ship the feature"
grok plugin marketplace add BoredSexyJordan/fusion-marketplace grok plugin install fusion-orchestrator --trust # then, in a session: /fusion-run "ship the feature"
# Fusion on Codex = its worker roles. codex fusion workflows add fusion-orchestrator # full guide ships with the Codex package
Every harness reads and writes the same shape — so the weekly scorer is cross-harness from day one.
| File | Purpose |
|---|---|
| plan.json | The validated packet — roster, phases, scope, verification. |
| team.json | The executed roster + audit counters. |
| harness.json | Per-dispatch receipts: actual model, provider, status, seconds. The attestation. |
| out-<role>.md | One artifact per worker. |
| header.txt | The provenance line — built only from what actually ran. |