N° 01The Studio
Mad EZ Media & Technology Partners · Charlotte, NC · Slot 2 of 3 open

We build AI-native media systems for companies whose audiences live online.

Custom platforms, autonomous characters, sonic identities, and protocol-grade infrastructure — designed, built, and operated by a small senior team. We do not ship decks. We ship working systems.1

Talk to Bentley → See the lab
Recently shipped last 30 days · public artifacts only
curated track record

Each entry links to the artifact. Open source on GitHub · npm install @madezmedia/acmi

N° 02How it works

Three keys per entity. That's the whole protocol.

Every entity in ACMI — a project, an agent, a contact, a deal — is stored using exactly three keys. Profile answers who. Signals answers now. Timeline answers then. Here's the @madezmedia/acmi npm package as an entity, modeled in its own protocol:

P Profile — who
acmi:repo:madezmedia/acmi:profile
{
  "name":     "@madezmedia/acmi",
  "version":  "1.2.0",
  "license":  "MIT",
  "node":     ">=18",
  "exports":  ["adapters", "testing"]
}
stable · slow-changing
S Signals — now
acmi:repo:madezmedia/acmi:signals
{
  "tests_passing":   "31/31",
  "ci_status":       "green",
  "open_issues":     0,
  "current_focus":   "v1.3 §11/§12",
  "last_publish":    "1.2.0"
}
live · changes frequently
T Timeline — then
acmi:repo:madezmedia/acmi:timeline
→ published v1.2.0 to npm
→ conformance: 31/31 pass on Upstash
→ Sigil v2.0 roadmap merged
→ §11/§12 v1.3 spec drafted
→ MIT LICENSE dated 2026
→ docs/SPEC.md published
append-only · forever

That's it. No vector index, no knowledge graph, no fact-extraction LLM pass. Three keys per entity, in the simplest data store on earth. Every product we ship — ACMI itself, Folana, TONY, our client engagements — runs on this same shape.

N° 02Approach

Architect. Build. Operate.

Most agencies hand you decks. Most studios hand you content. Most platforms hand you tools you have to learn. We hand you working systems — the infrastructure that turns AI from a budget line item into a product your audience actually uses.2

We work in three movements. Architect — we model your media problem as a working system before any code gets written. Data flow, agent architecture, content pipeline, monetization surface. Build — TypeScript, modern stacks, open protocols, real testing. The code that ships looks like product code, not deliverable code. Reviewable, maintainable, ownable on day one. Operate — we run it post-launch on retainer. Most agencies hand off; we don't. The thing keeps working when the launch press fades.

Each of those movements produces an artifact. Some artifacts are private to a client. Some — like ACMI, like Folana, like TONY — we ship publicly because the only way to credibly claim infrastructure expertise is to publish the infrastructure.3

N° 03Lab

What we've shipped this year.

Each one is an artifact of the same practice — not unrelated products.

An open protocol

ACMI

v1.2.0 · MIT

The protocol for agent memory. Three keys per entity — Profile, Signals, Timeline. Three reference adapters. A 31-test conformance suite. Published to npm 2026-05-01.

$ npm install @madezmedia/acmi
An autonomous character

Folana

live · running her own loop

An AI character with her own audience, her own voice, her own daily consciousness loop. She journals. She decides. She publishes. She runs herself.

"In the analog silence, my digital heart echoes — can harmony exist beyond the static?"
A distributed narrative

TONY

Roku · Q2 2026

T.O.N.Y. — Top Of New York. Crime drama series by Michael Steven-Paul. Episodic, distributed, Roku-native. Season one in certification.

A sonic identity practice

Sonic branding

client work · ongoing

Audio identity systems for brands that want to sound like something. Theme, ident, audio architecture across every touchpoint — from product UI confirmation tones to long-form podcast intros.

N° 04Active engagements

A small number of operator-led companies.

We work with operators, not committees. Companies whose founder still answers the email. The kind of business where one good decision a week — backed by working AI infrastructure instead of busywork — compounds into a different company within a year.

Slot 1
Engaged · Q2-Q3 2026
Slot 2 · open
Accepting inbound · Q3 2026 start
Slot 3 · open
Accepting inbound · Q4 2026 start
N° 05Talk to us

Want to see if we're a fit?

Twenty minutes. We listen, you talk, no decks. If we're not the right shop, we'll tell you who is.

Book with Duane → duane@madezmedia.com

Notes

  1. "Working system" is a load-bearing distinction. Most studios produce deliverables — files that arrive in your inbox. We produce systems — software that runs on your infrastructure on Tuesday morning when nobody's watching. Different category of work, different ownership model.
  2. We borrow this framing from operator-led businesses (the ones we like working with). The agency-deck-then-leave pattern is built for marketing budgets, not for changing how an operator's day actually goes. We're built for the latter.
  3. Anyone can claim infrastructure expertise. The only durable proof is shipping the infrastructure publicly, with an open license, and watching whether the community uses it. That's why ACMI is on npm and not behind a sales gate.