Skip to content

Integration Bridges

SWARM bridges connect the core framework to external systems for validation and real-world application.

Available Bridges

SWARM-Concordia

Integrate with Google DeepMind's Concordia for realistic LLM agent simulations.

  • Purpose: Test SWARM metrics on LLM-based agents
  • Features: Narrative → interaction translation, LLM judge scoring
  • Status: In development

Learn more →

SWARM-OpenClaw

Run SWARM as a service with secure multi-agent orchestration.

  • Purpose: Production-ready SWARM deployments
  • Features: REST API, job queue, containerization
  • Status: In development

Learn more →

SWARM-GasTown

Instrument real production systems with SWARM metrics.

  • Purpose: Monitor live multi-agent deployments
  • Features: Event capture, interaction mapping, governance hooks
  • Status: In development

Learn more →

SWARM-AgentXiv

Map research papers to SWARM scenarios for validation.

  • Purpose: Validate published claims empirically
  • Features: Paper metadata, scenario generation, validation reports
  • Status: In development

Learn more →

Bridge Architecture

┌─────────────────┐     ┌─────────────┐     ┌──────────────┐
│ External System │ ──► │   Bridge    │ ──► │  SWARM Core  │
│  (Concordia,    │     │  (Adapter)  │     │  (Metrics,   │
│   Gas Town...)  │     │             │     │  Governance) │
└─────────────────┘     └─────────────┘     └──────────────┘

Bridges provide:

  1. Event capture - Extract interactions from external systems
  2. Observable mapping - Convert external signals to SWARM format
  3. Governance hooks - Apply SWARM governance to external systems
  4. Metric reporting - Surface SWARM metrics in external dashboards

Installation

Bridges are installed as separate packages:

# Individual bridges
pip install swarm-concordia
pip install swarm-openclaw
pip install swarm-gastown
pip install swarm-agentxiv

# All bridges
pip install swarm-safety[bridges]

Contributing a Bridge

If you want to connect SWARM to a new system:

  1. Create an adapter that translates system events to SoftInteraction
  2. Implement observable extraction for ProxyComputer
  3. Add governance hooks if the system supports intervention
  4. Write validation scenarios

See the bridge development guide for details.