Amplio internal · Deck 13 · Routine engine
Cron · four cycles · zero hands

The engine that runs Amplio.

Four sister cycles fire on a clock. They refresh every dashboard, route every email, learn from every client, find every prospect — without anyone pressing a button. This deck is the map.

4
Sister orchestrators
9
Fires a day, on the clock
30+
Sub phases dispatched
0
Touch · default operating mode

/ Amplio internal · 2026 · use → to advance

Internal · share with the team · do not forward
Amplio internal · Deck 13 · Routine engine

/ 01 — The promise

Three guarantees. Every working day.

Walter wakes up to a vault that is up to date, a client roster that just got smarter, and a pipeline that is six prospects deeper than yesterday. The four cycles split the work cleanly so each guarantee has one owner.

1

Every dashboard, every 4h

Six fires a day (00 / 04 / 08 / 12 / 16 / 20) redeploy every Cloudflare dashboard, refresh access state, sweep the inbox, route every update_ email. No LLM, no quota anxiety, idempotent.

Always freshdeploy-cycle
2

One heavy run at 08:00

Dashboard feedback flips statuses, client data lands fresh, vault autoresearch compiles raw into Galaxy, learning sync grades last week's recommendations, memory and hygiene tidy up. Four Opus sub agents on Mondays.

Always learningdaily-intelligence
3

11:00 prospecting, 12:00 reports

Outreach cycle hunts new agencies daily across LinkedIn, job boards, and eight ATS providers. Weekly reports stays quiet most days, fires the Wednesday Certify experiment, ships the monthly report on the 1st.

Always reachingoutreach-cycle + weekly-reports

5 dashboards refreshed every 4h · 4 Opus sub agents on Mondays · 8 ATS crawled daily, UK + DACH · 1 email per cycle, never more

Sister cycles · each owns its lane · failure of one never cascades
Amplio internal · Deck 13 · Routine engine

/ 02 — The 24 hour clock

One day, five clean moments.

The cycles stagger so the heavy work runs after the light work. By the time outreach fires at 11:00, the morning data pull is already in the vault. By the time reports fire at noon, outreach has already snapshotted Attio.

SlotMomentCycle
00 / 04Quiet refresh — deploy cycle fires twice before sunrise. Access scan, comms refresh, every dashboard redeployed. No one notices, which is the point.deploy-cycle
08:00Daily intelligence — the heavy run. Feedback, client data pull, vault autoresearch, learning sync, backup, memory organise, hygiene. Mondays add the executive briefing.daily-intelligence
11:00Outreach cycle — top of funnel hunts. LinkedIn + job boards, ATS careers across eight providers, stub enrichment, Attio snapshot, one consolidated email lands at 11:15.outreach-cycle
12:00Weekly reports — day gated. Quiet most days. Wednesday fires the Certify ads experimentation. The 1st of the month ships the Certify monthly report.weekly-reports
12 / 16 / 20Three more deploys — deploy cycle keeps cadencing. The 20:00 slot adds the daily vault dashboard tarball backup. Nothing on the dashboards drifts more than four hours behind reality.deploy-cycle
AISix slots a day for deploy-cycle, one each for the other three, a three hour stagger between 08 / 11 / 12 — so maximum dashboard staleness stays at 4h.
cron: deploy-cycle 0 */4 * * * · daily-intelligence 0 8 * * * · outreach-cycle 0 11 * * * · weekly-reports 0 12 * * *
Amplio internal · Deck 13 · Routine engine

/ 03 — deploy-cycle · every 4h

Lightweight. Relentless. The heartbeat.

Three lanes — access, mail, dashboards. Each fire takes minutes. Failures isolate row by row; dashboards.md is where new surfaces get added.

/ 01

Access tracker sweep

Reads every client's access state from data-context.md, regenerates the access dashboard, redeploys it to Cloudflare KV, reconciles the Cloudflare Access policy. End to end in one phase.

every slotPhase A
6
fires a day
on the hour
/ 02

Inbox routing, four times a day

M1 routes employee update_ emails. M2 routes Daragh's update_ emails. M3 sweeps the rest of the inbox for vault and dashboard signals. Triage step auto scaffolds new client and prospect spaces above 0.85 confidence.

slots 08 · 12 · 16 · 20Phases M1 · M2 · M3
3
mail lanes
label gated
/ 03

Refresh + deploy every dashboard

B pulls fresh comms.json from Gmail. D iterates the dashboard registry and ships vault, certify, odisei, access, lupo-test to Cloudflare KV. H snapshots the vault dashboard tarball at 20:00. Client share dashboards run an isolation guard.

every slot · H at 20:00Phases B · C · D · H
5
dashboards shipped
vault · access · certify · odisei · lupo

Phases A · B · C · D · H run with no LLM — idempotent, no quota risk · Sonnet orchestrates the rest

Registry: deploy-cycle/dashboards.md · add a row to add a dashboard · next fire picks it up
Amplio internal · Deck 13 · Routine engine

/ 04 — daily-intelligence · 08:00

The heavy run. Strict order.

Each phase waits for the previous one. Feedback flips statuses, data pull reads them, autoresearch sees fresh state, learning sync grades T+7 and T+30 outcomes, then backups and hygiene tidy the trail. Tier 3 and Tier 4 phases dispatch as Opus sub agents — Sonnet orchestrator, Opus quality.

PhaseWhat runsModel
FFeedback sync — Walter's [x] ticks in Brain Dump and dashboards flip recommendation statuses across every client tracker.08:00
GClient data pull — reads the new statuses, pulls today's metrics from every connected platform, writes _overview.md, data-context.md, and per client snapshot.json. Phase 4F fans out the PostHog UX pull too.Opus · the data spine
IVault autoresearch — compiles raw sources into Galaxy notes, lints orphans (target 0/0/0), runs the email classifier, processes Brain Dump proposals, deep cross link pass.Opus
JLearning sync — three advisor gates. Grades last week's recommendations against fresh data. Moves cross client patterns up, down, or hold. Fires health score alerts.Opus
K · L · R · S · NBackup + tidy + Monday brief — tarball, scheduled tasks export, memory organise, vault hygiene. Mondays add Phase N — the weekly executive briefing email.Mondays add N
AINine phases — F · G · I · J · K · L · R · S · N. Four Opus sub agents on Mondays, three advisor gates inside Phase J, one run per business day, never more.
Sub agent brief shell: read SKILL.md → execute end to end → append log line · failure logs and continues
Amplio internal · Deck 13 · Routine engine

/ 05 — outreach-cycle · 11:00

Discovery to send, in one daily run.

A and B crawl in parallel as Opus sub agents. C enriches yesterday's stubs, D finds the humans inside each company, E scrubs and sends Touch 1 from a warmed cold domain. V verifies Attio against the dashboard and Z drafts one consolidated email by 11:15. Deck 11 covers the full funnel — this is just the engine view.

/ A

LinkedIn + job boards

Profile snippets plus Indeed, Glassdoor, LinkedIn Jobs, WTTJ. Tags linkedin_websearch or job_board. Opus sub agent.

/ B

ATS careers crawl

8 applicant systems direct. UK + DACH. EN + DE. Hiring is the strongest intent signal we have. Opus sub agent.

/ C

Stub enrichment

Three idempotent scripts backfill empty Companies so the Leads modal never shows a dash. Runs inline.

/ D

Find the humans

Five persona searches per company. Names, titles, verified email guesses. Clay style, vault native.

/ E

Scrub + send — the send layer

Five gate checks, then Touch 1 as Daragh or Jule from send.ampliodata.io.

/ V·Z

Verify + email, the tail

Seven audit checks, refresh leads.json, append run-stats.csv, draft one summary.

7 phases · A · B · C · D · E · V · Z6 markets · UK · DACH · IE · NL · ES · Other3 strategy scoped lists in Attio0% bounce · verified cold sends
Phase registry: outreach-cycle/phases.md · adding a phase = one row + an execution order entry
Amplio internal · Deck 13 · Routine engine

/ 06 — weekly-reports · 12:00

Quiet most days. Loud on the right ones.

The cron fires every day at noon, but the cycle is gated by weekday and day of month. Wednesdays run the Certify ads experimentation. The 1st of every month ships the Certify monthly report. Every other day logs a no op summary and exits.

/ O

Certify ads experimentation

Reads the morning's data pull, evaluates the active ad experiments, writes recommendations to the Certify tracker. Sets up the next week's hypothesis.

WednesdayTier 3 · Opus
1
experiment review
a week
/ P

Certify monthly ads report

Reads the cumulative month to date data, drafts the client facing report, ships it via Gmail. When the 1st falls on a Wednesday, O runs first so the freshest verdict is folded in.

1st of monthTier 3+ · Opus
1
client facing report
a month
/ —

Logged no op, by design

On any other day the cycle logs weekday=tue dom=12 phases=- ok=0 fail=0 (no-op) and exits. Adding a new day gated report is one new row, no new cron, no new orchestrator.

5 days a week
5
no ops per typical week
on purpose
Outreach phases do NOT belong here · they live under outreach-cycle · sister, not parent
Amplio internal · Deck 13 · Routine engine

/ 07 — What you see

The engine writes everywhere the team looks.

You don't read SKILL.md to know what happened. You open the dashboard, scan the morning email, or check Brain Dump for the day's staged proposals. The cycles produce surfaces, not logs you need to babysit.

/ 01

Five dashboards on Cloudflare Workers + KV

ops.ampliodata.io is the team home — client health, MRR, pipeline, tracking plan, performance, the Leads tab. Plus certify.ampliodata.io, odisei.ampliodata.io, the access dashboard, the lupo test. All gated by Cloudflare Access.

refreshed every 4h
5
URLs bookmarked
on ampliodata.io
/ 02

Daily summaries, drafted not sent

Outreach drafts the 11:15 consolidated summary. Daily intelligence drafts the Monday executive briefing. Weekly reports drafts the Certify monthly. You review and send — the cycle never sends client mail without you.

hello@ + daragh@ + jule@
3
drafts a week, max
in your inbox
/ 03

Brain Dump + client overviews

Email triage staged proposals, dashboard feedback applications, recommendation status flips, signal extractions, scheduled task exports. Every write logs one line to vault-autoresearch-log.md — the audit trail.

graph stays linted, 0/0/0
1
append only log
one line per phase
Audit trail: 00-Inbox/vault-autoresearch-log.md · every phase, every run, one line
Amplio internal · Deck 13 · Routine engine

/ Your part

Trust the engine. Tick the boxes.

Brain Dump for the staged proposals. ops.ampliodata.io for the day's state. The Gmail drafts for the outbound. That is the entire team interaction surface. Everything else runs on the clock.

5 min
Morning Brain Dump review
1 tab
ops.ampliodata.io · all day
3
Drafts a week, you press send
Phases — new rows, never new orchestrators
01 · Read the email 02 · Tick the box 03 · Send the draft
Open ops.ampliodata.io
Questions → Walter · Source → scheduled-tasks/{deploy-cycle,daily-intelligence,outreach-cycle,weekly-reports}/SKILL.md · Map → scheduled-tasks-reference.md