What the system does in one week, for twelve kinds of business
Each card opens an example week at a made-up business: what happened each day, what the system did (replied to a text, booked an appointment, sent an invoice), which service it used, and the entry it wrote to the Ledger, the system’s record of every request and response. Pick the one closest to yours.
Online stores · Sat 10:00 AMmessage after 60 days away · stops when they reply
Auto shops · Sat 9:00 AMad set created paused · started after your “go” text
Agencies · Sat 10:00 AMAI model changed · same actions · same permissions
Property · Sat 11:00 AMreview asked · 5 stars · Google review link sent
Studios · Sat 9:00 AMmessage after 90 days away · next open dates · stops when they reply
Home services · Sun 6:00 PMrefused · price not on the approved list · passed to you
Realtors · Sun 4:00 PMreply to seller · read: calendar, showings only
Restaurants · Sun 9:00 PMreport written · one row per day · all locations in one spreadsheet
Clinics · Sun 11:00 PMcloud job · overnight · one row per day written to your spreadsheet
Law firms · Sun 7:00 PMrefused · legal advice · conversation passed to you
Salons · Sun 9:00 PMreport written · one row per day
Gyms · Sun 6:00 PMreview asked · 4 stars · Google review link sent
Online stores · Sun 11:00 PMcloud job · overnight · one row per day written to your spreadsheet
Auto shops · Sun 8:00 PMreport written · one row per day
Agencies · Sun 9:00 AMtoken created · one job · expired after 10 minutes
Property · Sun 11:00 PMcloud job · overnight · one row per property per day
Studios · Sun 6:00 PMreview asked · 5 stars · Google review link sent
—entries in this system’s real Ledger. Each one includes a fingerprint (a SHA-256 hash) of the entry before it, so a changed entry is detectable.
Live, read from this site just now.
Twelve example weeks
Pick the business closest to yours
Each card shows three moments from that business’s example week. Open a card for all seven days, the permissions the AI assistant works under, and a setup you can send me by text.
An illustration. The businesses and the people are made up.
The same actions appear in different businesses’ weeks
Each card is one kind of action, made of rows in the Directory, the table of every action the system can run. The icons under each card are the businesses whose example week uses it. No business gets special software: every one uses the same Directory, with different actions switched on.
All twelve businesses use the same Directory, dispatch and Ledger.
Each business switches on different actions, but every action is listed in the same Directory, run through the same dispatch address and written to the same Ledger. Choose how much detail you want: for you, for your team or for your developer.
Every action runs through dispatch
The DirectoryEvery action the system can run
A table with one row for each action the system can run.
The Directory is a table. Each row is one thing the system can do for your business: send a text from your number, book a slot in your calendar, create an ad, read a web page, take a screenshot of your Mac. If an action is not in the table, the system cannot do it.
Each row stores everything needed to run that action: where it runs, what inputs it needs, what it returns, and every way to call it. Changing a setting is typing in a cell. Files added to the system’s folder are added to the table automatically.
One row per action. Each row has one column per way of calling it, and each of those cells holds the complete request (method, address, headers and body) that runs it, followed by the full response from the last run.
Why it matters to a business
Every action a business can use is listed in one place, with where it runs and what it needs. You can see what the system is able to do before it does anything: if an action is not in the Directory, it cannot run.
—actions in the Directory
DispatchOne address that runs any action
One web address runs any action in the Directory.
Dispatch is a single web address. You, your staff, a spreadsheet, an iPhone Shortcut or an AI model send it the name of an action and its inputs. It finds the action in the Directory, checks your permissions, runs it on the right computer, sends back the result, and writes an entry in the Ledger.
Because every request goes through the same address, the same permissions apply whether a request comes from a text message, a link, a spreadsheet cell, a Shortcut, the command line or an AI model, and every request is recorded the same way. One action can be switched off in one place.
Every action is invoked as an HTTP POST of {"key": "<action name>", "args": {…}}. REST, MCP, spreadsheet formulas, text tags and webhooks are different ways of making that same request. Actions run on Cloudflare servers, a Mac, an iPhone, a browser, a virtual machine or a phone.
Why it matters to a business
One connection instead of a separate integration for every tool. Your staff, your AI models, your spreadsheets and your phone all use the same actions under the same permissions. Changing AI model or vendor does not mean rebuilding, and any action can be switched off in one place.
—ways to call each action
The LedgerA record of every request and response
A table with one row for every request and response the system has handled.
The Ledger is a record of everything the system does: every message sent and received, every action run, every change, every AI model’s answer, and every request that was refused. Nothing in it is overwritten. To find out what happened, you read it.
Each entry stores the full request and the full response. Each entry also stores a fingerprint of the entry before it, so if anyone changes an entry later, the change shows up. Refused requests are recorded the same way as completed ones.
Every payload in or out is a Ledger row. Each action appends one row containing a SHA-256 hash of the previous row; nothing is updated in place. An action counts as working only when the declared surface itself ran and five things are stored for that run: why it ran, the exact request written before it ran, the confirmation, the exact response, and the record.
Why it matters to a business
You can see exactly what was sent, to whom, when, and by which AI model, and settle a dispute from the record instead of from memory. You can check what an AI did before trusting it with more, and compare AI models on cost and results. Refused requests are recorded too.
Tell me what kind of business you run and what it misses in a week: calls, follow-ups, reviews. I will reply with the closest example week above and which moment to set up first.