All businesses/Restaurants
A call missed during Friday service gets a text back and a booked table. Tonight’s reservations get a reminder, guests are asked for a review the next morning, and regulars who stopped coming get a message.
Live, read from this site just now.
An illustration. The business and the people are made up.
Fri 7:10 PMThe phone rings during Friday service and nobody can answer.Example week
Lucia’s is a made-up restaurant. For each moment, Monday to Sunday: what happened, what the system did, which service it used, and the entry it wrote to the Ledger, the system’s record of every request and response.
An illustration. The business and the people are made up.
10:00 AMPart of the system: The Directory
They came every other Thursday for a year, then stopped in spring. The system texts them about their usual dish and offers a table on their usual night. The texts stop when they reply.
The service this usesFor restaurantsWritten to the LedgerMon 10:00 AM
message after 60 days away · “your Thursday table” · stops when they reply
········→········matches
4:00 PMPart of the system: Permissions and limits
The AI assistant answers straight away, using only the menu you uploaded. If the answer is not on the menu, it passes the question to the host.
The service this usesFor restaurantsWritten to the LedgerTue 4:00 PM
reply sent 4:01 PM · answered from the uploaded menu
········→········matches
No moment is shown for this day in the example.
3:30 PMPart of the system: Dispatch
The AI assistant reads the email and replies within the hour. Writing the price quote is passed to you.
The service this usesFor restaurantsWritten to the LedgerThu 3:30 PM
catering inquiry · email read · replied 3:42 PM · quote passed to you
········→········matches
5:00 PMPart of the system: Where actions run
At 5 PM each party booked for tonight gets a text from your number: “Text back if you’re running late.”
The service this usesFor restaurantsWritten to the LedgerFri 5:00 PM
reminders sent · tonight’s reservations · from your number
········→········matches
7:10 PMPart of the system: Where actions run
The caller gets a text from your number: “Sorry we missed you, it’s busy in here.” 7:30 is full, so the AI assistant offers 7:50 by the window, from the tables you made available, and books it.
The service this usesFor restaurantsWritten to the LedgerFri 7:10 PM
missed call 7:10 PM · text sent from your number · table for 4 booked at 7:50
········→········matches
10:00 AMPart of the system: Permissions and limits
Each guest who paid gets one text. Five-star answers get your Google review link. One table gave two stars after waiting for water; that answer came to you and was not posted.
The service this usesFor restaurantsWritten to the LedgerSat 10:00 AM
review asked · 2 stars · sent to you, not posted to Google
········→········matches
9:00 PMPart of the system: The Ledger
The system writes one row per day: calls missed, calls texted back and tables booked. Every location goes in the same spreadsheet.
No extra service · included in every setupThe LedgerWritten to the LedgerSun 9:00 PM
report written · one row per day · all locations in one spreadsheet
········→········matches
The two codes under each entry above are the first characters of real SHA-256 fingerprints, calculated in your browser: the fingerprint of the entry before, then this entry’s own, which is calculated from its text plus the one before. Press “Change one word” to edit Friday’s entry, then “Check every entry”: the check fails at that entry, because its text no longer matches its fingerprint. This is how a changed Ledger entry is detected.
Calculating fingerprints
Services used
Each card is one service. A service is a set of actions from the Directory (the table of every action the system can run), set up for your business. The days on each card are the moments above that use it. The number on each card is how many actions in the Directory that service includes.
For restaurants
Missed calls become tables. Reviews asked after the meal. Regulars won back.
iMessage line
Customers text your existing business number and get iMessage replies (blue bubbles on iPhones) from an AI assistant that follows the permissions you set.
Meta ads
What each step of an ad costs and returns — impressions, clicks, leads, booked jobs — and which step the system improves.
Creative
AI makes the images and videos, a person chooses them, and they are uploaded to your ad account switched off until you approve.
Permissions
For each action you decide what information the AI assistant may read, what it may do, whom it may reply to, and limits such as an amount or a time window. A request outside the limits is refused, and the refusal is written to the Ledger.
What the AI assistant may read, what it may do, and whom it may reply to. Anything not listed here is switched off.
The AI assistant books only into the tables you made available and answers only from the menu you uploaded. Anything else is passed to the host.
Each card shows an action a restaurant would use, the limit on it, and what came back, as it appears in the Ledger. A refused request is recorded the same way.
sent from your number
invite sent
uploaded, paused
2 of the 7 moments above were decided by a permission or a limit. Each one is an entry in the Ledger, including any refusal.
How the system carries out the week
The Directory is a table of every action the system can run. Dispatch is one web address that runs any of those actions. The Ledger records every request and response. The actions run on real computers and phones. Choose how much detail you want: for you, for your team or for your developer.
Numbers are live, read from this site just now.
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.
Every action your 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.
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.
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.
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.
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.
Depending on the action, the work happens on Cloudflare’s servers (always on), on your Mac, on your iPhone, in a web browser signed in to your accounts, or on Android phones rented in a data centre for apps that only run on a phone.
A website or app with no way to connect to it can be recorded once — the steps a person clicks — and saved as a new action in the Directory that can be run again at any time. The browser uses your own signed-in sessions, not fake accounts.
Executors: Cloudflare Workers and containers, a Mac bridge program, iPhone Shortcuts and App Intents, persistent browser profiles, cloud Android phones and Mac virtual machines. Recording steps and compiling them turns any website into a Directory row callable through dispatch.
Choose your setup
Pick the services and which phone number to use. The button opens a text message to me with your choices already written in, so my reply can be about your setup.
Other businesses
The same system, with different actions switched on.
Tell me what your restaurant misses in a week: calls, follow-ups, reviews. I will reply with which moment above to set up first, and the entry it would write to the Ledger.
Your setup · Restaurants
Your setup · Restaurants
For restaurants · iMessage line · Your own number · Customers and leads