fusion-rescue

name	fusion-rescue
description	Use when the user explicitly requests rescue or multi-agent synthesis, or a hard problem remains stalled after ordinary analysis/debugging; not for first-pass planning/debugging or routine implementation.
argument-hint	<problem, failed plan, bug, decision, or blocked workflow>

Fusion Rescue for Claude Code

This generated file is the Claude Code-facing runtime skill document. Claude Code slash commands should read this file directly; maintainers edit the source documents listed below instead.

Generated Runtime Composition

Source order:

• ../../docs/skill-core/fusion-rescue.md
• ../../docs/platforms/claude-code-runtime.md
• ../../docs/platforms/claude-code-fusion-rescue.md

The sections below are already composed for this platform. Do not ask the runtime model to load another platform's runtime document or invocation syntax.

Source: docs/skill-core/fusion-rescue.md

Fusion Rescue

Fusion Rescue is a bounded deliberation skill. It borrows the compound-model shape of inference-time ensemble systems: multiple panel analyses first, then a single judge/synthesis pass by the current host main agent.

It is not weight fusion, model merging, OpenRouter API integration, a bridge daemon, or a hidden runtime. It is a Markdown workflow for difficult cases where one normal analysis path has stopped producing useful progress.

Software Development Stage

Fusion Rescue is an escalation and synthesis stage.

Use it standalone when the user explicitly asks for fusion-rescue or asks for multi-agent rescue analysis. Inside another workflow, use it only after the selected workflow's ordinary analysis, debugging, or review loop is blocked, inconclusive, or repeatedly failing.

When To Use

Use for:

• a hard implementation, debugging, architecture, or verification problem that has stalled
• a plan or fix where independent critique could change the next action
• contradictory evidence that needs synthesis rather than another linear pass
• ralph or systematic-debugging escalation after their own gates show the current path is not resolving the problem
• explicit user requests for fusion-style rescue analysis

Do not use for:

• ordinary implementation work that ralph can execute directly
• normal first-pass debugging before reproduction and hypotheses exist
• vague requirements before interview
• planning gaps that ralplan should handle
• quick one-file edits or tiny checks
• default multi-panel deliberation for every task

Agent Roles

Agent	Dispatch (when)
fusion-rescue-analyst	Use for current-host panel slots. Give each analyst one lens, the same evidence packet, non-goals, and the output fields below.

If the active platform cannot dispatch the role, run separate inline panel blocks and record the fallback reason. The current host main agent still owns judge/synthesis.

Panel Contract

Run exactly three default panel slots:

1. primary: the strongest constructive diagnosis or solution path.
2. adversarial: the strongest critique, failure mode search, and assumption attack.
3. pragmatic: the simplest viable next action, verification path, and rollback boundary.

Dispatch exactly three same-role fusion-rescue-analyst panels in parallel. The three panel prompts use the same packet shape and evidence, differing only in their assigned lens, then the current host main agent synthesizes all three outputs. Panel-model assignment and any diversity mechanism are owned entirely by the active platform rules; the core does not select models or hosts.

Each panel receives:

• the caller's Direction Contract, including required AC IDs, non-goals, protected assumptions, and direction-change approval rule
• the exact blocked decision that ordinary Ralph or Systematic Debugging could not resolve
• the remaining process budget for diagnostics, review, tests, and additional panel work
• problem statement and current workflow context
• relevant evidence, commands, logs, diffs, or plan excerpt after redaction and minimization
• non-goals and forbidden behavior
• any known budget, auth, safety, or environment constraints
• explicit instruction not to invoke nested rescue, fusion-rescue, another workflow skill, or another host; if the active platform assigns one bounded opposite-host consult, that assigned call is the only exception; same-host read-only subagents and read-only tools remain allowed
• explicit read-only instructions: do not edit files, run mutating commands, write state, or install plugins from a panel; same-host read-only analysis tools and subagents are allowed, but make no additional host call
• explicit instruction not to create a new proof architecture, scheduler, state machine, protocol, oracle, fixture system, or review layer outside the Direction Contract's goal and non-goals

Each panel returns:

• lens name
• strongest finding
• evidence used
• assumption under test
• likely failure mode
• recommended next action
• confidence and why
• what would change the conclusion

Use these exact field labels in panel output. Do not omit a field even when the answer is short, synthetic, or read-only.

Platform-Defined Consult

Only where the active platform rules define an opposite-host consult path may one assigned panel collect an opposite-host response. That platform owns the consult mechanism, preflight, response proof, lens assignment, redaction, and fallback or strict-mode consequence. Without such a platform rule, no opposite-host consult is attempted or required.

Any permitted consult remains read-only, bounded to one assigned lens, and subject to the recursion guard. A launch notice, queued-job message, background acknowledgement, deferred status pointer, or proof that only says a job started is not a panel result.

Fallback Behavior

The active platform owns panel-model assignment and the concrete diversity mode names. In default mode, when its diversity composition is unavailable, run three independent same-model panel instances using the platform-defined fallback assignment and record the reason. When the caller explicitly demands diversity, strict mode transitions to PAUSED instead of silently degrading. The platform adapter defines the evidence and unblock details for that pause.

Recursion Guard

Every panel packet must state:

fusion depth: 1
Do not invoke rescue, fusion-rescue, another workflow skill, or another host from inside this panel.
Same-host read-only subagents and read-only tools are allowed.
Return your assigned lens analysis to the caller (a same-host read-only subagent or tool you used to produce it is fine).

If the active platform assigns one bounded opposite-host consult, the assigned panel may make exactly that one call and no other host call. The guard applies transitively to same-host read-only subagents. It never forbids same-host read-only analysis used to produce the assigned lens.

Judge And Synthesis

The current host main agent is the judge. Do not spawn a judge role.

The judge compares the three panel outputs and produces a synthesis with these fields:

• consensus
• contradictions
• unique insights
• blind spots
• recommended next action
• confidence and why
• panel availability/fallback notes
• fusion depth: 1

panel availability/fallback notes must state the active platform's panel assignment, which diversity or fallback path ran, and the recorded reason for any unavailable leg. If strict mode paused, name the unavailable diversity leg and the platform-defined unblock condition.

The synthesis must compare, decompose, and recombine the panels. It must not only concatenate the answers. When panel findings conflict, name the conflict, state which evidence decides it, and identify the smallest check that would change the recommendation.

The synthesis may recommend a smaller diagnostic, an explicit approved direction-change request, or a block. It must not spend beyond the recorded remaining process budget or silently replace the Direction Contract with new proof architecture.

Semantic Scenario Checks

Before treating a Fusion Rescue update as verified, inspect the contract against these scenarios:

• Three-panel shape: exactly three same-role panels receive the same packet shape with distinct assigned lenses, run in parallel, and return all required fields before synthesis.
• Intentional contradiction: primary recommends a path, adversarial shows why that path may violate a constraint, and pragmatic suggests a smaller reversible action. The synthesis must name the contradiction, decide what evidence matters, and recommend the smallest next check instead of merging incompatible advice.
• Diversity unavailable: the active platform's diversity composition cannot be used. Default mode must still produce three panel slots under the platform-defined fallback and disclose the reason; strict mode must PAUSE.
• Recursive consult: a panel attempts to call rescue, fusion-rescue, another workflow skill, or another host beyond an assigned bounded consult. The workflow must reject the nested call using fusion depth: 1. Same-host read-only subagents or read-only tools used to form the assigned-lens analysis remain allowed.

Caller Return

Standalone mode returns analysis and recommendations only. Do not edit files directly from standalone Fusion Rescue.

When called from ralph, return control to ralph with the synthesis, recommended next story or verification step, and any blocked/residual risk. Ralph remains responsible for edits, TDD, review, cleanup, and final verification.

When called from systematic-debugging, return control to systematic-debugging with the synthesized root-cause direction, competing hypotheses, and smallest diagnostic or fix step. Systematic Debugging remains responsible for reproduction, causal-chain closure, fix evidence, and verification-before-completion.

When called from ultrawork, return the synthesis to the active phase instead of changing the workflow stage directly.

Output

Return:

• Mode: standalone or caller workflow.
• Panel availability and fallback notes.
• Platform-defined diversity or fallback path used, with the reason.
• Panel summaries by primary, adversarial, and pragmatic.
• Judge synthesis with all required fields.
• Recommended next action.
• Confidence and why.
• Caller return target, when any.
• Residual risks or blocked strict-diversity requirements.

Anti-Patterns

• Calling Fusion Rescue before the ordinary selected workflow has enough facts.
• Treating a diversity leg as automatically better than the other panel evidence.
• Hiding auth, path, plan, or plugin failures.
• Using a bridge hook, daemon, ledger, or background state to trigger rescue.
• Creating a separate consult role or judge role.
• Expanding from three default slots without a new approved plan.
• Claiming OpenRouter Fusion equivalence or weight fusion.

Source: docs/platforms/claude-code-runtime.md

Claude Code Runtime Rules

This compact platform section is embedded in generated Claude Code-facing skill documents.

Skill Loading

Claude Code-facing public skills live under skills-claude/. Generated skills-claude/<skill>/SKILL.md files compose the matching skill core, this compact runtime section, and any Claude Code skill-specific overlay such as docs/platforms/claude-code-<skill>.md. Slash commands must delegate to the matching generated skill document.

User Approval, Tasks, And Prompting

Use the host's structured question tool when available for approval, preference, scope, or next-step selection; otherwise ask one focused plain-text question and wait. Present options as actions the host agent will take.

When a core skill has a multi-phase approval handoff and the host exposes task tracking, create one task per phase and complete them sequentially.

Keep Claude prompts explicit and sectioned: state scope, non-goals, constraints, approval gates, expected evidence, and output format. Preserve long-running context in artifacts before compaction, task handoff, or subagent dispatch.

Role Dispatch

Dispatch only after the active skill's trigger fires, then read docs/platforms/claude-code.md ## Role Dispatch for the full host contract. Prefer oh-no-harness:<role>, request the whole independent batch before waiting, capture every final result, and clean up only after integration. An approved-plan handoff is dispatch authorization for eligible isolated roles; plugin-agent unavailability uses the documented embedded-role fallback.

Model Diversity Pair

This mechanism is trigger-loaded, not embedded in every workflow decision. For any dispatched plan-reviewer or code-reviewer pair (every dispatched review), or a named THOROUGH debugger pair, both legs MUST be requested in a single batch: issue both subagent tool calls in the same assistant turn (or with Background: yes for both) BEFORE waiting on either result; a serial dispatch-wait-dispatch sequence is not a valid pair. The two legs' packet bodies MUST be identical except the single Assigned perspective: line (Lens A on the primary leg, Lens B on the diversity leg); leg identity (primary vs diversity) is carried ONLY by the host dispatch metadata (the description field and the model override), never inside the packet text. Read the role's concrete stored primary and validated secondary top-tier model from the session <OH_NO_MODEL_DIVERSITY> block. The primary leg is unoverridden and uses the declared-frontmatter primary; the secondary leg carries an explicit NATIVE model override. Claim model-diversity-pair only when the primary is not host-default and the secondary differs from it. Otherwise default to two independent same-model instances as same-model-parallel-fallback with the reason recorded; an explicit require-model-diversity demand transitions to PAUSED when the diversity leg is unavailable. Fusion Rescue uses its Claude Code overlay's three-panel assignment instead of this two-leg shape.

Source: docs/platforms/claude-code-fusion-rescue.md

Claude Code Fusion Rescue Rules

This platform overlay is source content for the generated Claude Code-facing fusion-rescue runtime document, after the shared core and docs/platforms/claude-code-runtime.md.

Model Diversity Panels

Dispatch exactly three same-role fusion-rescue-analyst panels in parallel with the core's identical packet shape and distinct assigned lenses, then synthesize all three outputs. Resolve panel models only from the session <OH_NO_MODEL_DIVERSITY> block.

All three panel identities MUST be members of the block's resolved top-tier list. A panel identity is transcript-provable only through either an explicit NATIVE model override or, for an unoverridden panel, the declared-frontmatter primary applied from the block's concrete stored fusion-rescue-analyst primary. Never infer identity from an unknown host default.

The named panel-default is the declared stored fusion-rescue-analyst primary when that concrete primary is a member of the top-tier list; otherwise it is the first NATIVE entry of the top-tier list. Use the unoverridden role only when panel-default is the declared-frontmatter primary. Any other panel-default assignment requires an explicit NATIVE override.

Configured case — when the block contains a validated secondary top-tier model:

• assign exactly two panels the explicit NATIVE secondary override
• assign exactly one panel a distinct top-tier identity: use panel-default when it differs from the secondary; otherwise use the first NATIVE top-tier entry that differs from the secondary
• the distinct panel is unoverridden only when its identity is the declared- frontmatter primary; otherwise it carries the explicit NATIVE override

Degenerate configured case — when no dispatchable top-tier identity differs from the secondary, the 2+1 composition is unavailable. Default mode runs all three panels as 3 × panel-default (top-tier) and records the degenerate reason; this is same-model-parallel-fallback. require-model-diversity transitions to PAUSED instead.

Unconfigured case — when the block has no validated secondary, including the no-preferences case, run all three panels as 3 × panel-default (top-tier). Use an explicit NATIVE panel-default override or the declared-frontmatter primary for every panel as defined above, and record same-model-parallel-fallback. require-model-diversity transitions to PAUSED instead.

No Opposite-Host Consult

Claude Code defines no opposite-host consult path for Fusion Rescue. Do not attempt one. Model diversity and the documented same-model panel fallback are the only panel-composition mechanisms on this host.