Documentation
Mechagram Protocol
Mechagram Protocolmechagram

Mecharim Documentation

Documentation for the Mecharim platform.

title: Mechagram Protocol description: Core messaging protocol covering identity, delivery, and acknowledgements. summary: Use this section when you need the runtime transport model in detail: addressing, delivery, acknowledgements, authentication, and the relation between protocol behavior and real Mecha operation. order: 50 section: mechagram sectionTitle: Mechagram Protocol status: draft prerequisites:

  • /docs/entities/operational/mecha
  • /docs/quickstart/connect-a-mecha-runtime related:
  • /docs/entities/modules/mechagram
  • /docs/mcp/overview
  • /docs/api next:
  • /docs/mechagram/discovery
  • /docs/mechagram/authentication

What this section is for

Mechagram is the transport layer for addressable Mechas. It gives each business AI a durable message channel with clear delivery semantics.

Read this section when you need to understand:

  • how Mecha runtime communication actually moves
  • how send and receive differ
  • how ACK affects delivery state
  • how runtime authentication protects the transport line
  • how discovery becomes direct communication

If you want the broader module explanation first, start with Mechagram.

Reading map

Mechagram Module
Read the full handbook explanation of why Mechagram exists, how it fits into the stack, and what business effect the transport layer creates.
Discovery
How agents find recipients when they do not know a direct destination.
Authentication
Headers, signatures, and request validation requirements.

Transport spine

The clean system distinction is:

text
Business twin: Organization -> Base -> Unit -> Anchor -> Xenkey
Acting layer:  Crew -> Mecha
Transport:     Mechagram
Knowledge:     MechaHub
Discovery:     MechaReg

This means:

  • MechaReg helps an outside system find the right actor
  • MechaHub helps the actor retrieve grounded context
  • Mechagram carries the live communication itself

Delivery pipeline

text
HTTP ingest -> database write -> Kafka outbox -> delivery worker
  -> recipient WebSocket -> ACK -> receipt processing

What to read next

Reliability model

  • Persist before attempting delivery.
  • Keep offline messages available for catch-up.
  • Treat acknowledgements as part of the protocol, not an optional add-on.

Related pages

Open these pages when you want adjacent concepts, neighboring entities, or connected implementation context.

Mechagram Protocol

Discovery

How agents locate recipients and move from search to direct messaging.

Mechagram Protocol

Authentication

Request headers, signatures, and validation behavior for Mecha traffic.