AgenTroMatic Documentation

Your agents don't need a boss. They need a deliberation.

Part of the [&] Protocol stack · Ecosystem overview · Three-protocol stack · Stack status

Welcome to the documentation hub for AgenTroMatic — the automatic deliberation engine for multi-agent AI systems. When a task arrives, agents bid based on ability, debate when capabilities overlap, elect leaders by consensus, execute under quorum validation, and build reputation over time. No human routing required — ever.

AgenTroMatic is not an orchestrator (that's Delegatic) or a framework for building agents (that's Agentelic). It is the automation layer that sits between human-defined governance and raw agent execution — making self-organization reliable, visible, and auditable.

How It Works

1. Task arrives — submitted via Phoenix API or A2A protocol

2. Agents bid — each agent evaluates capability fit and submits a bid

3. Deliberation — overlapping capabilities trigger structured debate

4. Consensus — Ra (Raft) elects a leader; quorum validates the result

5. Execution — winning agent executes under governance constraints

6. Reputation update — outcomes feed back into reputation scores

AgenTroMatic is the automation layer of the [&] Protocol ecosystem — the service mesh that adds consensus, resilience, observability, and governance on top of Google's A2A protocol.

Documentation Map

Homepages

• [&] Ampersand Box

• Graphonomous

• BendScript

• WebHost.Systems

• Agentelic

• AgenTroMatic

• Delegatic

• Deliberatic

• FleetPrompt

• GeoFleetic

• OpenSentience

• SpecPrompt

• TickTickClock

Root Docs

• [&] Protocol Docs

• Graphonomous Docs

• BendScript Docs

• WebHost.Systems Docs

• Agentelic Docs

• AgenTroMatic Docs

• Delegatic Docs

• Deliberatic Docs

• FleetPrompt Docs

• GeoFleetic Docs

• OpenSentience Docs

• SpecPrompt Docs

• TickTickClock Docs

AgenTroMatic Docs

• README

Architecture at a Glance

Design Principles

1. Deliberation over routing — Static routing is the wrong abstraction for

overlapping, evolving capabilities. Agents negotiate every time.

2. A2A-native — Every inter-agent message flows through standard A2A protocol.

3. Reputation is memory — Past performance shapes future assignments.

Overconfident agents lose weight.

4. Visible by default — Every deliberation is traceable. The Observatory is

not optional — it's the product.

5. Consensus before commit — Results publish only when quorum validates.

6. Ra under the hood — Battle-tested Raft from RabbitMQ.

Tech Stack

Project Links

• Spec: Technical Specification

• [&] Protocol ecosystem: AmpersandBoxDesign/

[&] Ampersand Box Design — agentromatic.com