// THE HANGAR

// THE FLEET

Specialists with a purpose.
A fleet with direction.

Content, communication, monitoring, strategy, decisions and memory. Each role contributes a different part of the work.

Six featured roles. One accountable operator.

Meet the agents ↓See the operating architecture →

// THE SPECIALISTS

Meet the roles behind the work.

A selection of the fleet’s recurring functions. These profiles explain responsibilities and example outputs, rather than a live roster or availability status.

// APOLLO

Content Engine

Drafts content and prepares assets for the publishing workflow.

Drafts articles and supporting assets
Prepares content for review
Schedules authorized publishing work

Example output: a draft, supporting assets and a publishing checklist.

// HERMES

Messaging Bridge

Routes messages between connected channels and agent workflows.

Routes messages across connected channels
Preserves context in handoffs
Delivers requests to the relevant workflow

Example output: a routed request with enough context for the receiving agent.

// HORUS

Fleet Watchdog

Monitors service health and supports recovery and escalation.

Checks configured services
Attempts configured recovery steps
Escalates unresolved failures

Example output: a health alert, recovery attempt and escalation when needed.

// ATHENA

Strategy Engine

Reads results and proposes priorities for human review.

Reviews available results
Proposes priorities and alternatives
Surfaces evidence for a human decision

Example output: a proposed next step with evidence and tradeoffs.

// THEMIS

Decision Intelligence

Records decisions, their rationale and follow-up lessons.

Records decisions and rationale
Captures follow-up lessons
Links outcomes to earlier choices

Example output: a decision record linking the choice to its rationale.

// AKASHIC

Memory Service

Retrieves stored context to support the next task.

Stores project context and lessons
Retrieves relevant records
Makes prior work available to new sessions

Example output: relevant past decisions and source notes for a new brief.

// THE LOOP

How the fleet compounds

An illustrative content loop: prepare, monitor, evaluate, record and retrieve. HERMES carries messages between connected workflows; the operator owns priorities and approvals.

APOLLOContent Engineprepares publication
HORUSFleet Watchdogmonitors health
ATHENAStrategy Enginereads results, proposes
THEMISDecision Intelligencecaptures the decision
AKASHICMemory Serviceretrieves context

Review can send work back. A failed check calls for revision or escalation before the next authorized step.

// FROM BRIEF TO HANDOFF

Follow one piece of work.

Example scenario: turn a researched idea into a reviewed article.

  1. 01 / CONTEXT

    Start with what is known.

    Memory supplies relevant records. Strategy helps frame the goal and questions to answer.

  2. 02 / PRODUCTION

    Make something reviewable.

    The content workflow drafts the article and assets. The operator checks accuracy and authorizes publication.

  3. 03 / FEEDBACK

    Keep the useful lessons.

    Monitoring surfaces failures. Decision records capture what changed and why, ready for the next brief.

Explore the full architecture →Inspect the evidence →

Build your own first agent

Start with one useful task. The guided builder helps you define the role, inputs, boundaries and result before you connect a tool.

Build Your First Agent →