Morning briefing, 07:00
Reads the north star, yesterday's numbers, overdue tasks and what worked; writes today's briefing before the day starts.
Product · Automations
If you do it more than once, automate it.
An automation is a plain note in your Salana Memory: what to run, when, and what a good run leaves behind. The engine runs it on your machine, logs it and grades the outcome. With the memory holding everything you know, the automations get smarter every day.
How one works
One markdown note per automation, in the Schedules folder. It says when (a cron schedule, or a trigger: a webhook from another system, or another automation going red), what to run (usually a skill), and what a good run leaves behind. The engine runs it, writes the run log, grades the outcome, and alerts you when something fails. Set it up in plain language in a chat; the note is written for you.
How Robert runs his companies on automations
All of these run in the memory today.
Sales data refresh, 06:00
Fetches customers, orders and payouts from the company's API and writes the day's snapshot with 30-day trends.
Receipts to the bookkeeper
Harvests invoice and receipt PDFs from every Gmail account into a monthly folder, sorted by vendor. Nothing to forward by hand.
Finance rollup
Profit across all companies and currencies rolled into one monthly view; the north star updated from the last closed month.
Newsletter draft, every morning
A bilingual email drafted in the brand voice from a topic queue, self-reviewed, waiting as a draft in the email tool for a click.
Email stats sync
Broadcast statistics pulled back into the memory; sent drafts promoted to records.
Vault sync, every two hours
Commits and pushes whatever the sessions left behind, so the memory is never only on one machine.
Exit drill, every Sunday
Clones the folder to a bare path and proves the automations still run there. The ownership promise, tested weekly.
Failure alert (trigger)
Any automation going red writes a line in the daily log, an event in the feed, and a notification on the Mac.
Live signal webhook (trigger)
A trading platform posts a new signal; within seconds it is logged and a social post is drafted.
Ad spend and platform stats, daily
Meta ad spend, cost per new user and platform analytics appended as a daily time series.
Instagram posting, daily
The day's new listings rendered as on-brand cards and posted, once a day, at most two.
Video briefs, weekdays 07:00
Scores every own post from the last days and picks the two video briefs for today.
Social metrics, daily
Views, likes and followers for every own handle, logged so the correlation with sales can be read.
Vault doctor, daily
Dead links, orphan notes and drift, reported in the log before they become a problem.
Smarter every day
Each run writes back into the memory: a snapshot, a log, an outcome. The next run and the next chat read it. The briefing knows what the sales refresh found; the newsletter draft knows what was sent in the last sixty days; the video brief knows which post worked.
Where it runs
On your machine, next to the folder: the engine is part of the Salana Memory, not of the app. The folder names exactly one runner, so ten copies of the same memory never fire the same automation ten times. A hosted runner is on the way for work that should run while the laptop is closed.
Set up a Salana Memory that is specifically yours.
Your files, every model, yours forever.