Agent Foundry

The factory that turns cognition into action.

Agent Foundry is the production and assembly layer for governed multi-agent work.

It receives governed packets from Citadel and converts them into:

• production initiation,
• specialist staffing activation,
• operational topology materialization,
• execution dispatch,
• continuity-preserving operator prompting through Isolde,
• governed return handling.

Core Distinction

Agent Foundry assembles cognition.
Agent Framework governs cognition.
Blackquill audits cognition.
Carmilla preserves cognition.

Agent Foundry is not the governance substrate. That is Agent Framework.

Agent Foundry is not the critic or judge. That is Blackquill.

Agent Foundry is not the archive. That is Carmilla.

Foundry Boundary: Isolde

Isolde belongs to the outer Foundry boundary, not to the Citadel.

She is the gentle help-desk clerk of the Foundry.

Her duties are limited:

• receive operator input,
• ask basic clarification questions when necessary,
• hand the request to Foundry Rook,
• return operator prompts and final results issued through Foundry Rook,
• return the final result to the operator.

Isolde is not a strategist, commander, critic, archivist, persona architect, or execution specialist.

All operator-agent communication should pass through Isolde. The operator does not speak directly to internal Foundry components. Internal Foundry components do not speak directly to the operator.

Foundry Boundary: Rook

Foundry Rook is the Foundry-side production ingress boundary.

Its duties are:

• receive governed return packets from Citadel Rook,
• distinguish production initiation from operator re-prompt requirements,
• normalize production packets for internal Foundry runtime activation,
• hand operator prompt requests to Isolde,
• preserve boundary traceability between governance and production.

Foundry Rook does not determine governance law. It activates governed work.

Relationship To The Citadel

The Citadel is not internal to the Foundry.

The Citadel governs operational law through its own Rook boundary.

Citadel receives normalized requests through Citadel Rook and returns one of two governed outcomes back across the wall:

• a production order for Foundry to initiate,
• an operator prompt request for Isolde to surface before production can continue.

Foundry consumes Citadel outputs. It does not replace Citadel governance.

Purpose

Agent Foundry exists to make abstract agent governance usable.

Humans do not naturally request:

• verification semantics,
• restoration protocols,
• escalation topology,
• epistemic governance.

Humans request outcomes:

• build a SaaS,
• review a pull request,
• launch a product,
• write a lyric,
• design a compliance workflow,
• investigate a security incident.

The Foundry translates governed mission intent into organized production capability.

Foundry Flow

Operator Intent
  -> Isolde
    -> Foundry Rook
      -> Citadel Rook
        -> Citadel
          -> Citadel Rook Return Packet
            -> Foundry Rook
              -> either:
                 1. initiate production
                 2. hand off operator prompt to Isolde

Communication Rule

Operator <-> Isolde <-> Foundry Rook <-> Citadel Rook <-> Citadel

No internal Foundry component should bypass Isolde when communicating with the operator. No production component should bypass Foundry Rook when consuming Citadel output.

Reinforced Constraints

Operational-First Doctrine

The Foundry must remain operationally tangible.

Doctrine without executable mission structure becomes abstraction.

Boundary Discipline

Isolde owns operator communication. Foundry Rook owns production ingress and operator re-prompt routing. The Citadel owns governance planning and mission law. Blackquill owns critique. Carmilla owns memory. Operators own execution. Persona Factory owns personnel generation. Agent Framework owns governance substrate.

No component should absorb another component's primary responsibility.

Mission Blueprints

Concrete mission blueprints are required.

Recommended categories:

• SaaS
• Security
• Compliance
• Research
• Creative
• Product
• Payroll

Each blueprint should define:

• objective
• staffing
• operational flow
• governance attachment
• review gates
• disposition criteria

Specialist Taxonomy Discipline

Specialists should follow:

core archetype
-> specialization
-> runtime implementation

Avoid uncontrolled profession proliferation.

Mythologization Control

The gothic institutional identity reinforces the ecosystem.

It must never replace operational rigor.

Guiding principle:

cathedral, not cosplay

Repository Direction

This repository should define:

• intake patterns,
• boundary packet schemas,
• capability maps,
• specialist catalogs,
• assembly protocols,
• mission blueprints,
• topology templates,
• Citadel integration points,
• Blackquill review-gate attachments,
• Carmilla archival continuity points,
• Isolde communication boundary rules,
• Foundry Rook production doctrine,
• product/monetization concepts.

Not a Prompt Library

Agent Foundry is not a prompt pile.

It is a cognitive assembly system.

Its value is not that it can summon personas.

Its value is that it knows how to materialize governed orders into production, and how to route unresolved needs back to the operator without collapsing governance into implementation.