Resources / Course / Chapter 11

Schedule the Workflow with Automations

10 min read

Hand the recurring work — weekly news scans, thesis monitors, regime checks — to scheduled jobs that run on Zo and deliver results to your inbox.

What you will leave with
  • What a Zo automation is, in one sentence
  • Which parts of the Clarion workflow are worth automating, and which are not
  • How to schedule a weekly thesis monitor and have it email you the result
  • How to set up a weekly news brief for the names on your watchlist
  • Why a once-a-quarter Living Letter is best left manual

11.1 What an automation is

An automation on Zo is a scheduled job: a prompt that runs on its own cadence — daily, weekly, monthly — with the result delivered to you by email, by Telegram, or just saved to your workspace. You write it once. It runs forever, until you turn it off.

For investment work, this is the difference between a workflow you actually keep up with and one you abandon after a busy month. The regime read, the weekly monitor, and the news scan are exactly the kind of recurring chores a person skips when life gets in the way. Automations remove the “will I remember on Sunday?” from the loop.

Where this lives on Zo
Read the Zo Computer documentation for the full feature set. The shortcut: in the Zo app, every running conversation can be saved as an automation with a schedule and a delivery target.

11.2 What to automate

Not everything should run on a schedule. The right test is: does this task produce a useful answer when nothing has happened? If yes, automate it. If no, leave it manual.

  • Worth automating. Weekly regime check, weekly thesis monitor, weekly news scan over open positions and watchlist, monthly value screener run.
  • Leave manual. Writing a new thesis, sizing a new position, the quarterly Living Letter. These need your hands on them.

11.3 The weekly thesis monitor automation

The single highest-leverage automation. Every Monday morning, the Portfolio Manager persona re-scores every open thesis and emails you the four-bucket action list.

In Zo chat
>Create an automation: every Monday at 7am ET, run the weekly thesis monitor across all open positions. Email the result to me.
Automation created: weekly-thesis-monitor.
Schedule: Monday 07:00 America/New_York.
Persona: Clarion Portfolio Manager.
Skill: clarion-thesis-monitor.
Delivery: email to your registered address.

First run scheduled for next Monday. You will receive a sample output on Sunday at 7am as a dry-run.

Two details worth noting. First, the automation re-uses the same persona and skill you would invoke in a live conversation — nothing about the analysis changes because it is running on a schedule. Second, the result is delivered to you. You still read it, you still decide. The automation does the bookkeeping, not the judgement.

11.4 The weekly news brief

The second automation worth setting up. Every Friday afternoon, scan the news for anything material about your open positions and your watchlist names. Summarize in three lines per name.

In Zo chat
>Create an automation: every Friday at 4pm ET, scan the past week's news for my open positions (read ~/clarion/active-positions.md) and my watchlist (read ~/clarion/watchlists/latest.md). Email me a one-page summary, three lines per name, with citations to the original articles.
Automation created: weekly-news-brief.
Schedule: Friday 16:00 America/New_York.
Inputs: ~/clarion/active-positions.md, ~/clarion/watchlists/latest.md.
Delivery: email.

The brief will skip names with no material news that week and flag any item that potentially intersects a kill condition from the underlying thesis.
Cite, always
Make sure the prompt asks for citations to the original articles. Without that constraint, the news brief drifts toward summarizing chatter. With it, you get a piece of evidence you can re-read.

11.5 The monthly screener run

Schedule the value screener to run once a month on the S&P 500. Diff the watchlist against last month’s — new names appearing on the list are the most interesting output, because something changed in the last 30 days that put them there.

In Zo chat
>Create an automation: on the first business day of every month at 8am ET, run the S&P 500 value screener, save the watchlist with a dated filename, and email me a one-page summary that highlights names new to the list versus last month.
Automation created: monthly-value-screen.
Schedule: first business day of month, 08:00 America/New_York.
Persona: Clarion Value Screener.
Skill: clarion-value-screener.
Delivery: email + write to ~/clarion/watchlists/sp500-YYYY-MM.md.
Summary will diff against the prior month and call out additions and removals.

11.6 What not to automate

Three workflows stay on your hands.

  • Writing a new thesis. A thesis is a deliberate act of writing things down. Automating it would defeat the purpose. The system can prepare the materials, but you write the verdict.
  • Sizing a position. Sizing involves looking across the rest of the portfolio at the moment of the trade — existing exposures, the regime, recent moves. That judgement belongs in a live conversation, not on a schedule.
  • The quarterly Living Letter. The letter is a forcing function: a person sits down, reads the journal, and writes honestly. Automating it would turn it into a status report. You can use the LP Voice persona to draft it — but the decision to publish should be a deliberate human one.
Automation versus delegation
Automation removes a chore. It does not remove a decision. Any time an automation produces a recommendation, you are still the one who acts. If you find yourself rubber-stamping the output without reading it, narrow the automation — do not widen it.

11.7 Where the audit trail lives

Every automation writes its output to your workspace before delivering it to your inbox. If an email gets lost, the file is in ~/clarion/automations/. If you want to know what the monitor said three months ago, the file is there. The journal does not depend on email retention.

Key takeaways

  • Automations on Zo turn a recurring prompt into a scheduled job with a delivery target. Write it once, it runs forever.
  • Automate the chores: weekly thesis monitor, weekly news brief, monthly screener.
  • Leave the judgement calls manual: new theses, sizing, the quarterly Living Letter.
  • Every automated output also lands in ~/clarion/ as a file you can re-read months later.
  • If you start ignoring an automation’s output, narrow it or turn it off. An unread email is worse than no email.
That is the loop
Regime → ideas → shortlist → thesis → manage → automate. Six chapters, one continuous workflow. From here, every week is a smaller version of the same loop, and every quarter is a written summary of how it went.