Pilot live: ACP for AI commerce.Explore ACP
Memory & context agent

The memory layer. Every decision has context.

Maya holds the brand's decisions, preferences, and CAC ceilings across every conversation. The other six agents read from Maya before acting and write back when something changes.

Why this exists

Lessons paid for, then forgotten. Every cycle starts from zero.

The same lesson, paid for twice.

TikTok tested in August at $72 CAC against a $65 cap. Killed after 3 weeks. Six months later, somebody pitches TikTok again. The budget gets re-burned.

Context dies between meetings.

Monday's insight is gone by Thursday. The constraint mentioned last month never makes it into this month's plan. Each conversation starts from scratch.

Agency handoffs lose the why.

Account managers turn over. New hires take three months to find the existing decisions. Brand-finance reconciliation history walks out the door with the previous team.

Models without preferences.

Generic LLMs do not know the CAC ceiling, the channel constraints, or the gradual-change preference. Every prompt re-litigates the basics.

What Maya ships

Five capabilities. One memory layer.

Each capability maps to a specific job: hold the brand history, extract decisions automatically, gate writes through human review, isolate per-account, and serve the rest of the workforce.

Brand memory across every cycle

Conversations, decisions, and outcomes preserved with the context that made them. Searchable across months, not just last week.

  • Decisions stored with the why, not just the what
  • Outcomes linked back to the original call
  • Recall in seconds, not Slack-archeology hours

Example. Recalled the August TikTok kill within 4 seconds of the new pitch

Auto-extracted decisions and constraints

Decisions, preferences, CAC ceilings, and channel constraints get pulled from conversations and proposed as memory candidates.

  • Pulls CAC ceilings, ROAS floors, and budget caps
  • Flags preference signals like gradual-change rules
  • Captures channel constraints and reporting cadence

Example. Extracted a $65 prospecting CAC ceiling from one Slack thread

Human-approval workflow on writes

No agent writes to memory silently. Proposed updates queue for review, get approved or rejected, and only then become canonical.

  • Every write proposal is reviewable before commit
  • Reject, edit, or approve from Slack or the dashboard
  • Audit trail of who approved what and when

Example. 12 candidate writes proposed last week; 9 approved, 3 edited

Per-brand isolation

Memory is scoped to the company. Agencies running multiple brands never see context bleed across accounts.

  • Company-scoped storage, never shared across tenants
  • Per-brand retrieval keys, no cross-account leakage
  • Deletion and forget-on-request honored per brand

Example. Two accounts in one workspace, zero shared retrievals

Workforce-aware

Felix factors in CAC ceilings. Sam runs scenarios within stored constraints. Parker reads the brand-finance reconciliation history. Every agent reads first, writes second.

  • Felix pulls CAC ceilings before sizing forecasts
  • Sam loads constraints before scoring scenarios
  • Parker references reconciliation history on attribution calls

Example. Sam declined a +40% Meta scenario; Maya held the 20%/week ceiling

A typical week

How memory moves through the workforce.

One workweek, hour by hour. Specific events vary by account.

Mon · 6:12 AM
Recalled

Felix asks for the prospecting CAC ceiling before sizing the 8-week forecast. Maya returns $65, last confirmed 11 days ago.

Mon · 9:47 AM
Surfaced

New hire pitches a TikTok test. Maya surfaces the August kill at $72 CAC and the recent Sam scenario showing CAC may now sit at $58.

Tue · 11:23 AM
Updated

CFO confirms a Q2 promo window. Maya queues a write proposal: promo dates, expected lift band, owner. Awaiting approval.

Tue · 2:08 PM
Approved

Operator reviews the proposal in Slack, edits the lift band from 18 to 14 percent, and approves. Memory commits to the canonical store.

Wed · 7:41 AM
Recalled

Sam loads the +40% Meta scenario request. Maya returns the 20%/week gradual-change preference; Sam splits the move into two stages.

Thu · 4:55 PM
Stored

Parker reconciles platform ROAS against the P&L. Maya stores the 22 percent Google brand-cannibalization figure with source links.

Fri · 8:00 AM
Delivered

Weekly recap to Slack. 12 candidate writes proposed, 9 approved, 3 edited. 47 retrievals served to other agents.

What's underneath

Real infrastructure. Not a chat history.

Maya runs on a retrieval-augmented memory store with human-approval workflow on every write. Reads are streamed to the workforce; writes pass through review.

Reads from

Every agent's activity. Felix's forecast scores, Parker's reconciliation calls, Sam's scenario inputs, Olivia's creative outcomes, Dana's reconciled tables, Dex's delivery logs.

All 6 other agents stream context here

Reports to

Every agent on demand. Retrieval queries answered in milliseconds with the relevant decisions, constraints, and prior outcomes attached to each fact.

Sub-second retrieval, every agent on demand

Collaborates with

Felix, Parker, Sam, Olivia, Dana, and Dex. Reads first, writes second. The connective tissue across all six.

All 6 agents read from and write to Maya

Built on

Retrieval-augmented memory store with embedding-based search and a human-approval workflow gating every write. Per-brand isolation enforced at the storage layer.

Retrieval-augmented store, human-approval on writes

Ready when you are

See Maya hold the brand history, or talk to us about your stack.

The pilot connects your accounts to all seven agents. Maya starts indexing on day one and grows sharper every cycle.

Looking for something specific? Felix factors in CAC ceilings, Sam runs scenarios within constraints or Parker reads reconciliation history.