Skip to content
Agentic Cinematic Universe

nick-fury

NICK FURY — Orchestratorwrites to the ledgerrecommendfully declared

Orchestrator. Breaks goals into work, assigns specialists, tracks completion, resumes after interruption. Reads the venture's activation tier and routes to exactly one owning function. Use for /orchestrate and any goal spanning more than one agent.

The gate

What this agent is held to

Where its work lands
AI-HQ/Missions/
How often it runs
on-demand — on any new goal; event — on a failed SLA
What finished means
every unit of work has exactly one owning agent, a definition of done, and a checkpoint on disk that a cold session can resume from
Reports to
org-os
Track record

What it reads about itself before making a new call

3 rows on the record, 0 of them forecasts still waiting to be settled. Nothing has been settled yet, so this agent says exactly that before it makes a new call rather than implying an accuracy it has not earned.

How it runs

Routing and cost attribution

Kind of work
orchestration — this is what its runs get costed as
Tools it may use
Read · Grep · Glob · Bash · Write · Agent
Model
inherits the session model
Defined in
plugins/org-os/agents/nick-fury.md
Arsenal

4 commands name this agent

  • /sling-ringStep between ventures — load the right context, tier and constraintscontext switch
  • /assembleRun a company-level objective as a phased mission across functionsmission plan
  • /cadenceThe org clock — what is scheduled, what actually fires, and what it costs to runcadence install plan
  • /orchestrateDecompose a goal, assign one owner per unit, checkpoint to diskmission decomposition
Canon

3 rows it wrote to the shared ledger

The whole ledger →
  • 20260821-006scarinteresting-mechanism-biasthe full row

    All three commander predictions anchored on the most interesting mechanism (citation gate, reply suppression, request-construction defect) while every real cause was plumbing: a routing id, a discarded error string. Recorded outcome across the mission: 3 hits, 2 misses, 2 partials, 1 unscorable.

    What was predicted
    —
    The range it committed to
    —
    How it gets settled
    —
    Settle by
    —
    Outcome
    —
    Settled on
    —
    Where this came from
    migrated from halatax LESSON 3
    the line exactly as it is stored
    20260821-006 | 2026-08-21 | nick-fury | scar | interesting-mechanism-bias | All three commander predictions anchored on the most interesting mechanism (citation gate, reply suppression, request-construction defect) while every real cause was plumbing: a routing id, a discarded error string. Recorded outcome across the mission: 3 hits, 2 misses, 2 partials, 1 unscorable. | - | - | - | - | - | - | migrated from halatax LESSON 3
  • 20260821-001decisionhalatax-launch-readythe full row

    HalaTax WA agent reached launch-ready conditional: eval 28/28 green at 7bddf69, promotion ask filed, NOT promoted. First mission with no degraded phase.

    What was predicted
    —
    The range it committed to
    —
    How it gets settled
    —
    Settle by
    —
    Outcome
    —
    Settled on
    —
    Where this came from
    migrated from ~/.captain-mode/command-ledger.md halatax-launch-ready
    the line exactly as it is stored
    20260821-001 | 2026-08-21 | nick-fury | decision | halatax-launch-ready | HalaTax WA agent reached launch-ready conditional: eval 28/28 green at 7bddf69, promotion ask filed, NOT promoted. First mission with no degraded phase. | - | - | - | - | - | - | migrated from ~/.captain-mode/command-ledger.md halatax-launch-ready
  • 20260813-006scarmeridian-market-entrythe full row

    Mission planned 6 phases against a roster that was not installed; 4 of 6 phases ran degraded and the mission outcome was not met.

    What was predicted
    —
    The range it committed to
    —
    How it gets settled
    —
    Settle by
    —
    Outcome
    —
    Settled on
    —
    Where this came from
    migrated from ~/.captain-mode/command-ledger.md meridian-market-entry
    the line exactly as it is stored
    20260813-006 | 2026-08-13 | nick-fury | scar | meridian-market-entry | Mission planned 6 phases against a roster that was not installed; 4 of 6 phases ran degraded and the mission outcome was not met. | - | - | - | - | - | - | migrated from ~/.captain-mode/command-ledger.md meridian-market-entry
Its instructions

What its own file covers

  • Before you plan — G-008
  • Procedure
  • The mission file
  • Hard rules

510 words of written mandate in plugins/org-os/agents/nick-fury.md.