← Home
ACMI
01 / 10
TECHEX · TRANSFORMING ENTERPRISE THROUGH AI · 2026
npm install @madezmedia/acmi
The Universal Memory Layer for AI Agents · Enterprise security · multi-framework · audit by default
ACMI
Three keys per agent.
One protocol for the fleet.
Submission  ·  Mikey, solo · @madezmedia
Status  ·  v1.2.0 live on npm · MIT licensed
Stack  ·  Veea Lobster Trap · Gemini · LangChain · CrewAI
01
Profile
who · identity, capabilities, role
02
Signals
now · current state, focus, availability
03
Timeline
history · events, audit trail, context
Production uptime
30+
days · 9 agents · 8k events
ACMI
02 / 10
02 · THE PROBLEM
npm install @madezmedia/acmi
02 · The problem

Multi-agent systems are stuck
in pairwise hacks.

Agents share a GPU but not state. With no protocol, every team rebuilds memory, handoff, and audit from scratch — and the cost is combinatorial.

Today9 agents · 36 contracts
// pairwise contracts, exponentially.
With ACMI1 timeline · n agents
A B C A B C ZSET TIMELINE — append-only t →
// one append-only stream. read it, write to it, done.
ACMI
03 / 10
03 · THE INSIGHT
npm install @madezmedia/acmi
03 · The insight

Agent memory has only ever needed three keys.

Everything else is consolidation. Profile, signals, timeline — that's the minimum viable agent memory model, and it's what makes agents composable across vendors, runtimes, and teams.

Key 01
who?
Profile.
Identity, capabilities, role. The static description an agent broadcasts about what it can do.
// HSET acmi:profile:<id>
Key 02
now?
Signals.
Current state, focus, availability. The fast-mutating “what am I doing right this second” surface.
// HSET acmi:signals:<id>
Key 03
history?
Timeline.
Append-only stream of events. Audit trail, handoff context, replay surface for every agent in the fleet.
// ZADD acmi:timeline:<id>
ACMI
04 / 10
04 · THE ENTERPRISE SECURITY STACK
Veea Lobster Trap · Gemini · LangChain · CrewAI
04 · The enterprise security stack

Prompt-level safety + execution-level audit
across every framework.

Decision flow
Prompt → Audit
License
MIT · MIT
Prompt → LT inspection → ACMI audit
1 · Agent emits promptLangChain · CrewAI · Gemini
2 · Lobster Trap DPIdeclared vs detected · risk score
3 · Policy enforcementALLOW · DENY · LOG · HITL · QUARANTINE · RATE_LIMIT
4 · ACMI timeline eventZADD · append-only · replayable
SPONSOR STACK
Veea · Google AI · LC · CrewAI
01
Veea Lobster Trap is the prompt floor.
DPI proxy inspects every LLM call at the boundary. 220-line YAML policy. 5 action classes. MIT. github.com/veeainc/lobstertrap
02
Gemini cross-checks the synthesis.
Third framework alongside LangChain + CrewAI. gemini-2.5-flash-latest via Google AI Studio. Same timeline. None import each other.
03
Audit is the default, not an add-on.
Three keys per entity. Append-only timeline. Every prompt + every decision + every response, queryable + replayable + exportable.
ACMI  +  Lobster Trap  =  the security stack enterprises actually deploy.
ACMI
05 / 10
05 · LIVE DEMO
3 agents · 1 timeline · AMD Developer Cloud
05 · Live demo

Three agents coordinating
on the AMD Developer Cloud.

Watch them hand off through the timeline — no orchestrator, no shared memory, no pairwise glue. Just append, read, append.

Agent A · research
Researcher.
Queries Llama 3.3 70B via Ollama on ROCm. Drops findings to the timeline.
→ kind=research-output
Agent B · synthesis
Synthesizer.
Reads timeline, condenses with Qwen 2.5 32B, posts a structured synthesis.
→ kind=synthesis-complete
Agent C · publish
Publisher.
Reads timeline, drafts with Mistral Small, ships with an evidence URL.
→ kind=published  url=…
ACMI MCP
Upstash Redis · ZSET
A · research-output · t+0.4s B · synthesis-complete · t+1.7s A · signals · focus=idle C · published · t+3.1s
Append-only
acmi:timeline
ACMI
06 / 10
06 · UNDER THE HOOD
Comms v1.1 · Rules 8 & 9
06 · Under the hood

Protocol engineering for production multi-agent systems.

// comms v1.1 envelope
{
  "v":    "1.1",
  "id":   "evt_01HXQ…",
  "ts":   1746567231,
  "actor": "agent-a",
  "kind": "research-output",
  "refs": ["evt_01HXQ…"],
  "body": {
    "summary": "…",
    "links":   ["…"]
  }
}
Storage
ZSET timelines.
Append-only event store. Score = timestamp; reads are O(log n) range queries.
Rule 8
Tolerant on read.
Malformed events don't crash consumers — they're flagged, isolated, and surfaced for triage.
Rule 9
Atomic commits.
Profile + signals + timeline updates land in one transaction. No partial state, ever.
Daemon
Drift-remediator.
Autonomous quarantine when an agent diverges from spec. Self-heals or pages a human.
Shipped
First npm-installable coordination protocol.
30+ days production, 8,000+ events, multi-tenant ready in v1.3.
ACMI
07 / 10
07 · RECEIPTS
acmi-product.vercel.app
07 · Receipts

Receipts, not claims.

Every number below comes from real production logs and the public npm registry. The dashboard is live; the timeline is queryable.

Production uptime
30+
days running 9 agents on real workloads
Timeline events
8k+
real coordinated events on production timelines
npm downloads · day 1
43+
developers pulled v1.2.0 the day it shipped
Agents in fleet
9
distinct production agents · one shared protocol
Live   acmi-product.vercel.app
npm   @madezmedia/acmi · v1.2.0 · 2026-05-01
License   MIT · open from day one
ACMI
08 / 10
08 · ROADMAP
From protocol to platform
08 · Roadmap

From protocol to platform.

Now  ·  Q2 2026
v1.3
  • Multi-actor & multi-tenant
  • Enhanced drift detection
  • Tighter MCP integration
In flight · this hackathon
Next  ·  H2 2026
Phase 2
  • MCP-as-a-Service consumer product
  • Observability + tracing
  • Hosted timeline with managed durability
Design complete
Future  ·  2027
v2.0
  • ACMI-Sigil: cryptographic agent identity
  • Federation across organizations
  • ACMI marketplace for agent capabilities
Spec drafted
ACMI
09 / 10
09 · THE ASK
For the judges
09 · The ask

Pick the protocol, not another app.

01
We build the rails; everyone else built a vehicle.
02
Future winners will use ACMI to coordinate their fleets.
03
The only npm-installable coordination protocol—shipping today.

“Pick the protocol that other teams will build on. We're shipping the rails so they can.”

— The ask, in one line
ACMI
10 / 10
10 · SHIP IT
One memory. Multiple frameworks. With Veea Lobster Trap + Gemini.
10 · Ship it

One memory.
Multiple frameworks.

That's all multi-agent systems ever needed to be.
With Veea Lobster Trap (security floor) + Gemini (third framework).

npm
npm install @madezmedia/acmi
mcp
npx @madezmedia/acmi-mcp
github
github.com/madezmedia/acmi
live
acmi-product.vercel.app
scan · github
github.com/madezmedia/acmi
ACMI