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.
/ Amplio internal onboarding · use → to advance
/ 01 — Why email
A client says yes. A contractor sends a signed contract. A prospect asks a question. All of it lives in email. Instead of pasting it into Notion by hand, we label it. Claude reads, extracts, updates.
Labels and filters, nothing new. The inbox you already check becomes the work queue.
The subject prefix is the command. It tells Claude who is speaking and where the update belongs.
Client files, the index, the pipeline. Every labelled email ends as a verified vault edit.
Why it works: –90% data back and forth · labelled = waiting · unlabelled = done
/ 02 — Subject grammar
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.
| Part | Token | What it carries |
|---|---|---|
| / 01 | update_[person]: | The author, not the client. update_walter, update_daragh, update_amplio. Tells Claude who is speaking. |
| / 02 | [client or topic] | The subject of the update — client name, project, internal area. Triage fuzzy matches it against _Client-Index.md. |
| / 03 | [description] | A short human summary of what changed. Claude reads the body and attachments for full detail. |
/ 03 — The filter
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.
subject:(update_) OR from @ampliodata.io — the filter auto applies the label.
Claude polls 4x daily per email-sync task and processes the unread threads.
Skip the inbox only if desired — most keep it visible.
The label comes off once the change is committed. The reply is the receipt.
Forwarded threads get the label by hand and take the same path.
Proof of processing stays in your inbox.
/ 04 — The five step sync
Triage, classify, scaffold or stage, commit, log. Five steps, always auditable — every decision is written to email-routing-decisions regardless of outcome.
Extract the client token from the subject and fuzzy match it against _Client-Index.md.
No match → new-client, new-prospect, internal, or ambiguous — each with a confidence score.
Above threshold the space is auto scaffolded; below threshold a checkbox proposal lands in Brain-Dump.
Claude touches 06-Clients/[name]/_overview.md, recommendations-tracker.md and Client Signals, _Pipeline-Dashboard.md and _Client-Index.md.
Every edit replies with a diff, every decision gets a row in the ledger. No silent writes, ever.
/ 05 — Triage and classifier
Triage extracts the client token and fuzzy matches the index. No match → new-client, new-prospect, internal, or ambiguous, each with a confidence score.
Client or prospect space built from template, _Client-Index.md or the Pipeline Dashboard updated, data-context seeded, onboarding intel preloaded. The reply confirms what was created.
Walter ticks the box to approve. The 9AM vault-autoresearch Phase 8 reconciles approved rows.
No threshold moves before 20 decisions land in its class. Walter's user_override annotations are the training signal.
/ 06 — Scheduled fleet
The email syncs don't run alone. Four cron orchestrators touch the vault — the M phases of deploy-cycle poll the Amplio Updates label on every fire.
M1 routes employee update_ emails, M2 routes Daragh's (skill curation included), M3 triages inbound work requests — inbox passes ride deploy-cycle, and every routing decision is logged.
Feedback sync, client data pull into each data-context, vault-autoresearch (Phase I), learning sync with the T+7 / T+30 recommendation measurement, backup and hygiene — one run, strict order.
Day gated at noon: Wednesday runs the Certify ads experimentation, the 1st of the month ships the Certify monthly report. The Monday executive briefing rides daily-intelligence.
The registry sync keeps scheduled-tasks-reference.md and the portable export pack aligned with the live fleet — and every email-sync phase writes to email-routing-decisions on every run.
/ 07 — Prefix vocabulary
These are the ones Claude recognises today. Email prefixes trigger vault writes — the left column. Conversational commands trigger reads and reports — the right.
Founder reports, routed by body · briefs, routed to client or project.
Routes Brain-Dump items · summarises a client's status.
Skill curation, routes to Skills/ · automated internal updates.
Scores all active clients · all prospects, next actions.
newclient_[name]: · newprospect_[name]: · meeting_[client]: · graduate_[name]:
Contradiction testing · pattern and signal digest.
/ 08 — Safety rules
Guardrails, not guidelines. Every email-sync run checks them — if a rule would be violated, Claude stops.
Every edit replies with a diff. No reply, nothing happened.
Unclear routing stages a proposal in Brain-Dump.
Trusts @ampliodata.io. Forwarded client threads need a manual label.
Inbox becomes a queue. Labelled = waiting.
Only edits and appends. Removals need explicit confirmation.
The Vault Dashboard reads. Writes flow only through email.
Source note logs the email thread ID and timestamp.
No revenue, tax IDs, contracts, contact details, pipeline scores.
/ 09 — Status and next
Two paths into the vault, one clean boundary. The Vault Dashboard answers questions, Gmail makes changes — nothing crosses the line.
/ Up next — Deck 10 · The Skill Library: how Amplio packages repeatable work into skills the vault can call on demand