/DECK 09 · GMAIL VAULT AUTOMATION
LABEL · SYNC · REPLY

Talk to the vault. Through your inbox.

The whole system runs on email. Label a message Amplio Updates, Claude syncs it to the vault, then replies to tell you what changed. No new app, no new interface. Just a label.

1labelAmplio Updates
0appsNo new interface
24/7Always on sync
100%Inbox driven
Gmail & vault automation · the inbox is the UI
01 / 10 · → next
/01 · WHY EMAIL
/THE INTERFACE PROBLEM

Email is the input. The vault is the memory.

A client says yes. A contractor sends a signed contract. A prospect asks a question. All of it lives in email. Instead of copy-pasting into Notion, we label it. Claude reads, extracts, updates.

INTERFACE
Gmail
Labels + filters, nothing new
TRIGGER
update_
Subject prefix = command
TARGET
Vault
Client files, index, pipeline

Why it works: –90% data back-and-forth. The inbox you already check becomes the work queue. Labelled = waiting. Unlabelled = done.

Email-as-input · Vault-as-memory
02 / 10
/02 · SUBJECT GRAMMAR

One line. Three parts. Every time.

The subject is a mini-command. Claude reads it to know who sent the update and where it belongs. The em-dash splits the client from the description.

update_[person]: [client or topic] — [description]
PART 01

update_[person]

The author, not the client. update_walter, update_daragh, update_amplio. Tells Claude who is speaking.

PART 02

[client or topic]

The subject of the update. Client name, project, internal area. Triage fuzzy-matches _Client-Index.md.

PART 03

[description]

A short human summary of what changed. Claude reads the body and attachments for full detail.

Example: update_walter: Odisei — Q2 dashboard scope confirmed
03 / 10
/03 · THE FILTER

One Gmail filter. One label.

Every update_ email lands under a single label, Amplio Updates. Claude polls that label, processes unread threads, strips the label once committed. Your inbox is the queue.

FILTER SETUP

Auto-apply Amplio Updates

  • Match: subject:(update_) OR from @ampliodata.io
  • Apply label: Amplio Updates
  • Skip inbox only if desired. Most keep it visible
  • Manual labelling works for forwarded threads
LIFECYCLE

Label on, label off

  • Labelled = waiting for Claude
  • Claude polls 4x daily per email-sync task
  • Reply confirms the diff, label removed
  • Thread marked read, proof in your inbox
One label · one filter · one queue
04 / 10
/04 · THE FIVE-STEP SYNC

Every email takes the same path.

Triage, classify, scaffold or stage, commit, log. Five steps, always auditable. Every decision is written to email-routing-decisions regardless of outcome.

STEP 01
Triage
→
STEP 02
Classify
→
STEP 03
Scaffold / Stage
→
STEP 04
Commit
→
STEP 05
Log
WHAT CLAUDE TOUCHES
  • 06-Clients/[name]/_overview.md
  • recommendations-tracker.md + Client Signals
  • _Pipeline-Dashboard.md, _Client-Index.md
THE GUARANTEE
  • Every edit replies with a diff
  • Every decision gets a row in the ledger
  • No silent writes, ever
Triage → Classify → Scaffold / Stage → Commit → Log
05 / 10
/05 · TRIAGE & CLASSIFIER

Match, scaffold, or stage.

The Triage step extracts the client token and fuzzy-matches the index. If there's no match, it classifies the email as new-client, new-prospect, internal, or ambiguous with a confidence score. Above threshold auto-scaffolds. Below threshold stages a proposal.

ABOVE THRESHOLD

Auto-scaffold

  • Client or prospect space built from template
  • _Client-Index.md or Pipeline Dashboard updated
  • Data-context seeded, onboarding intel pre-loaded
  • Reply confirms what was created
BELOW THRESHOLD

Stage a proposal

  • Checkbox entry in Brain-Dump.md
  • Section: Proposed Client Spaces
  • Walter ticks [x] to approve
  • 9AM vault-autoresearch Phase 8 reconciles

Thresholds learn. Floor 0.70, ceiling 0.95, initial 0.85. Minimum 20 decisions per class before the threshold moves. Walter's user_override annotations are the training signal.

No email falls through silently
06 / 10
/06 · SCHEDULED FLEET

Ten tasks keep this alive.

The email-sync tasks don't run alone. A ten-task fleet runs on cron. Each one touches the vault for a different reason. Two poll the Amplio Updates label.

EMAIL + VAULT
  • employee-update-email-sync — 4x daily from 08:45. Polls update_walter, update_alana.
  • daragh-update-email-sync — 4x daily from 09:15. Skill-curation updates.
  • vault-autoresearch — daily 09:00. Seven-phase loop, compile and lint.
DATA + LEARNING
  • daily-client-data-pull — 08:00. API data into each data-context.
  • daily-access-tracker-sweep — 08:30. Platform access audit.
  • daily-client-learning-sync — 10:00. T+7 / T+30 recommendation measurement.
CLIENT DELIVERY
  • weekly-executive-briefing — Mon 07:30. State-of-the-world digest.
  • certify-education-monthly-ads-report — 1st of month 09:40.
  • certify-ads-experimentation — Wed 10:30. Weekly Ads experimentation loop.
FLEET HYGIENE
  • sync-scheduled-tasks-export — daily 11:00. Keeps the portable recreation pack in sync.
  • Full reference in scheduled-tasks-reference.md.
  • Both email-sync tasks write to email-routing-decisions every run.
10 active scheduled tasks · all cron-driven
07 / 10
/07 · PREFIX VOCABULARY

Prefixes are commands.

The subject prefix is a mini-command. These are the ones Claude recognises today. Email prefixes trigger vault writes. Conversational commands trigger reads and reports.

EMAIL PREFIXES · WRITE
  • update_walter: founder reports, routed by body
  • update_daragh: skill curation, routes to Skills/
  • update_alana: briefs, routed to client or project
  • update_amplio: automated internal update
  • newclient_[name]:, newprospect_[name]:
  • meeting_[client]:, graduate_[name]:
CHAT COMMANDS · READ
  • Process inbox. Routes Brain-Dump items.
  • Client brief: [name]. Summarises status.
  • Client health. Scores all active clients.
  • Pipeline review. All prospects, next actions.
  • Test patterns. Contradiction testing.
  • Learning report. Pattern and signal digest.
Write through Gmail · Read through chat
08 / 10
/08 · SAFETY RULES

Eight rules this system obeys.

Guardrails, not guidelines. Every email-sync run checks them. If a rule would be violated, Claude stops.

  • 01 · No silent writes. Every edit replies with a diff. No reply, nothing happened.
  • 02 · Amplio addresses only. Trusts @ampliodata.io. Forwarded client threads need a manual label.
  • 03 · Never delete. Only edits and appends. Removals need explicit confirmation.
  • 04 · Every edit is traceable. Source note logs the email thread ID and timestamp.
  • 05 · Ambiguity stops the loop. Unclear routing stages a proposal in Brain-Dump.
  • 06 · Label off when done. Inbox becomes a queue. Labelled = waiting.
  • 07 · Dashboard is read-only. The Vault Dashboard reads. Writes flow only through email.
  • 08 · No sensitive data in replies. No revenue, tax IDs, contracts, contact details, pipeline scores.
CLAUDE.md Rules · 8, 14, 15, 17 and the full set
09 / 10
/09 · STATUS & NEXT
/WHERE WE ARE · Q2 2026

Gmail writes. Dashboard reads. Vault remembers.

Two paths into the vault, one clean boundary. The Vault Dashboard answers questions. Gmail makes changes. Nothing crosses the line.

BACK-AND-FORTH
–90%
Data questions answered in-inbox
FULL SETUP
48h
From first email to live sync
TEAMS SERVED
100+
Cumulative Amplio book
GMAIL WRITE PATH DASHBOARD READ PATH 10-TASK FLEET ON CRON

Up next, Deck 10: the Skill Library. How Amplio packages repeatable work into skills the vault can call on demand.

Better Data. Smarter Campaigns. Proven ROI.
10 / 10