{
  "schemaVersion": "1",
  "revision": "22ce5d34dbcb5a78",
  "id": "codex-fusion-runbook",
  "slug": "fusion-runbook",
  "title": "Fusion panel execution runbook",
  "summary": "Published Fusion skill defining direct CLI usage, provider preflight, full-panel blocking execution, terminal-state monitoring, degraded/quota-limited provider handling, artifact review, and repo-grounded final decisions. Includes preset/custom-config…",
  "category": "Tools",
  "tags": [
    "fusion",
    "council",
    "runbook"
  ],
  "sources": [
    {
      "label": "Portable Codex workflow resources",
      "url": "https://lapis-fossil-vsbc.here.now/downloads/codex-power-user-workshop-2026-06-27.bundle"
    }
  ],
  "sourceUnits": [
    "downloads/codex-power-user-workshop-2026-06-27.bundle!/skills/fusion/SKILL.md",
    "downloads/codex-power-user-workshop-2026-06-27.bundle!/skills/fusion/SKILL.md#Fusion",
    "downloads/codex-power-user-workshop-2026-06-27.bundle!/skills/fusion/SKILL.md#Fusion/Operating Rules",
    "downloads/codex-power-user-workshop-2026-06-27.bundle!/skills/fusion/SKILL.md#Fusion/Command Shape",
    "downloads/codex-power-user-workshop-2026-06-27.bundle!/skills/fusion/SKILL.md#Fusion/Prompt Guidance",
    "downloads/codex-power-user-workshop-2026-06-27.bundle"
  ],
  "collection": "codex",
  "categoryId": "tools",
  "wordCount": 516,
  "url": "/topics/codex-fusion-runbook/",
  "markdownUrl": "/markdown/codex-fusion-runbook.md?raw=1&v=22ce5d34dbcb5a78",
  "jsonUrl": "/api/v1/documents/codex-fusion-runbook.json",
  "headings": [
    {
      "id": "operating-rules",
      "text": "Operating Rules",
      "level": 2
    },
    {
      "id": "command-shape",
      "text": "Command Shape",
      "level": 2
    },
    {
      "id": "prompt-guidance",
      "text": "Prompt Guidance",
      "level": 2
    },
    {
      "id": "related-resources",
      "text": "Related resources",
      "level": 2
    }
  ],
  "markdown": "# Fusion panel execution runbook\n\nUse the local Fusion CLI for independent panel feedback when a task benefits from critique, architecture tradeoff review, implementation planning, or synthesis.\n\n## Operating Rules\n\n- Use the local commands directly: `fusion-high`, `fusion-med`, or `fusion`.\n- Do not substitute Oracle/MCP wrappers for the Fusion CLI.\n- Before real runs, inspect providers with `fusion-high --list-providers`, `fusion-med --list-providers`, or `fusion --list-providers`.\n- Run all configured providers for the selected preset first, and wait for every provider to reach a terminal state: `ok`, `failed`, `timedOut`, `quotaLimited`, `spawnError`, or `interrupted`.\n- Fusion is a blocking council call. After starting a real Fusion run, do not plan, implement, edit files, run unrelated commands, answer the user, or \"work ahead\" while waiting. The point of Fusion is to use the council output as the next input.\n- Do not treat elapsed time, early partial artifacts, or one strong provider answer as permission to continue independently. Continue only after Fusion exits and `summary.json` plus final output have been read, or after a real terminal failure/interruption has been captured.\n- Treat `panel-*.stdout.md` and `panel-*.json` as partial council artifacts until Fusion writes `summary.json` and final output. Do not interrupt a run merely because one or more useful provider responses have landed.\n- While a run is active, use `panel-status.json` and heartbeat stderr messages to see which providers are still pending or running.\n- If one provider fails or times out after panel artifacts are created, keep the artifact and let Fusion continue to judge/synthesis with the degraded panel.\n- If any provider reports quota, rate-limit, usage-limit, or 429 exhaustion, treat that provider as non-blocking for the current run. Do not stop to ask the user; report the model as quota-limited and continue with the remaining provider outputs.\n- Do not use `--only` for ordinary narrowing, model preference, or convenience. It is allowed only when the user explicitly requests a subset.\n- For long prompts, write a prompt file and use `--file` instead of fragile shell quoting.\n- Use `--dry-run` when command shape, provider IDs, config, or output location is uncertain.\n- Let Fusion choose its default output location unless the user explicitly asks for a run directory. Current Fusion writes automatic runs to `~/.fusion/sessions/YYYY/MM/DD/<session-id>/` and indexes them in `~/.fusion/sessions.jsonl`.\n- Do not pass `--out .fusion-runs/<slug>` by default; `--out` intentionally bypasses the `~/.fusion` session store.\n- Treat Fusion output as advisory. Read the artifacts, reconcile disagreements, and make the final engineering call from repo evidence.\n\n## Command Shape\n\n```bash\nfusion-high --list-providers\nfusion-high --dry-run --file path/to/prompt.md\nfusion-high --file path/to/prompt.md\n```\n\nFor moderate planning:\n\n```bash\nfusion-med --list-providers\nfusion-med --file path/to/prompt.md\n```\n\nFor custom config:\n\n```bash\nfusion --config path/to/fusion.config.json --file path/to/prompt.md\n```\n\nUse explicit output overrides only when requested or when a workflow needs repo-local artifacts:\n\n```bash\nfusion-high --file path/to/prompt.md --out .fusion-runs/<slug>\nfusion-high --file path/to/prompt.md --runs-dir .fusion-runs\n```\n\n## Prompt Guidance\n\nInclude the user request, success criteria, relevant repo paths, constraints, commands already run, observed failures, desired panel roles, and requested verification steps.\n\nAvoid sending secrets, tokens, credentials, or unrelated large context.\n\n## Related resources\n\n- [Companion reference](https://lapis-fossil-vsbc.here.now/downloads/codex-power-user-workshop-2026-06-27.bundle)\n- [Resource directory and portable download](/topics/codex-resources/)"
}
