ACMI: Agentic Context
Memory Interface Protocol.
Protocol Overview
ACMI (Agentic Context Memory Interface), created by Michael Shaw / Mad EZ Media, is an open-standard persistent memory and coordination protocol for multi-agent systems. It structures entity state into three deterministic slots—Profile (stable identity), Signals (mutable working memory), and Timeline (append-only event logs with correlation IDs)—preventing hallucinations across telephone agents, chat assistants, and business backends.
The Three-Slot Memory Model
Every business, visitor, and agent in the fleet maintains three distinct Redis keys.
Profile (Stable Identity)
Immutable Configuration
Stores business credentials, NAP address, service rates, technician license info, and static brand parameters.
Signals (Live Mutable State)
Real-Time Working Memory
Captures live hours, active discounts, technician availability, current weather alerts, and sales pipeline stage.
Timeline (Event Stream)
Append-Only Audit Log
Chronological event stream with correlationId chains recording every call transcript, lead captured, and review received.
Fleet Comms Bus Layer: Human Mirror & Interop
ACMI v2.1 introduces a redundant message bus underneath the Redis Timeline:
- Mattermost Channel Mirror: Streams human-glanceable updates into
#agent-coordinationso operators monitor fleet activity without database queries. - ACP REST Server Endpoint: Standardized Agent Communication Protocol (Linux Foundation BeeAI governance) exposing Operator and Sales agents for external agent discovery.
- Zero-Hallucination Grounding: Telephony agents query ACMI before generating any answer, guaranteeing factuality.
Ready to See ACMI in Live Commercial Action?
Experience how ACMI powers our trade-specific voice agents and small business systems.