All businesses/Studios
A website inquiry becomes a booked shoot. The deposit invoice is sent in the client’s conversation, and overnight the video is cut into every ad size.
Live, read from this site just now.
An illustration. The business and the people are made up.
Mon 10:00 AMSomeone fills in the form on your website asking about a shoot.Example week
Fieldnote Studio is a made-up studio. 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: Dispatch
Website forms arrive in the same place as your text messages, so the AI assistant handles them the same way. It replies from your number and books the shoot on a date you made available: Saturday at 4:00.
The service this usesiMessage lineWritten to the LedgerMon 10:00 AM
website form · reply sent from your number · shoot booked Sat 4:00
········→········matches
1:00 PMPart of the system: Where actions run
Instead of reaching voicemail, the caller gets a text from your number within a minute.
The service this usesiMessage lineWritten to the LedgerTue 1:00 PM
missed call 1:00 PM · text sent from your number
········→········matches
9:00 AMPart of the system: Permissions and limits
The system creates a Stripe invoice and sends it in the client’s conversation. Invoices up to $5,000 go out without asking you.
No extra service · included in every setupPermissions and limitsWritten to the LedgerWed 9:00 AM
Stripe invoice sent in the conversation · under the $5,000 limit
········→········matches
11:00 PMPart of the system: Where actions run
A job on a cloud server makes tall (9:16), 4:5 and square (1:1) versions from the master file. Your own computer can stay off.
The service this usesAutomation on your devicesWritten to the LedgerThu 11:00 PM
cloud job · overnight · cut to 9:16, 4:5, 1:1
········→········matches
5:00 PMPart of the system: Where actions run
The time, the place and what to wear, from your number, in the same conversation.
The service this usesiMessage lineWritten to the LedgerFri 5:00 PM
reminder sent · shoot Sat 4:00 · from your number
········→········matches
9:00 AMPart of the system: The Directory
Each one gets one text with your next open dates. The texts stop when they reply.
The service this usesiMessage lineWritten to the LedgerSat 9:00 AM
message after 90 days away · next open dates · stops when they reply
········→········matches
6:00 PMPart of the system: The Directory
They get one text. Five-star answers get your Google review link. Anything under four stars comes to you first and is not posted.
No extra service · included in every setupThe DirectoryWritten to the LedgerSun 6:00 PM
review asked · 5 stars · Google review link sent
········→········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 Thursday’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.
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.
Automation on your devices
Each thing it can do on those devices is an action in the Directory, run through one address, and recorded in the Ledger.
Creative
AI makes the images and videos, a person chooses them, and they are uploaded to your ad account switched off until you approve.
Meta ads
What each step of an ad costs and returns — impressions, clicks, leads, booked jobs — and which step the system improves.
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.
Inquiries are booked only into the dates you made available. A request for any other date is passed to you.
Each card shows an action a studio 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
1 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 studio 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 · Studios
Your setup · Studios
iMessage line · Automation on your devices · Your own number · Customers and leads