What the system can doLedger and tasks
One family of actions
The Ledger and tasks
Read the record of every request and response, replay or repair one, and run tasks, schedules and saved sequences.
The Ledger is a database table that stores every request and every response the system handles, in order, in full. Tasks and schedules sit next to it, because each run adds to it.
Live, read from this site just now.
The groups in this family, counted just now: — actions
This family among all — actions in the Directory, one square each
Each action is one row in the Directory, sorted into this family by the start of its name.
What it can do
What the actions in this family do, group by group.
Each card is a group of actions that do similar work. The number on each card is how many actions are in that group right now.
Switch to “For your developer” to see the real name of every action.
The real name of every action, read from the Directory just now. Names that contain a supplier’s name are left out of the lists, and still counted.
Read the Ledger
—Read the most recent entries, every entry for one request, the latest errors, and one request with its full input and output.
Query the Ledger’s database
—Run database queries directly against the Ledger’s table, for reports the other rows do not cover.
Check the record
—Add new entries to the public chain of fingerprints (SHA-256 hashes), give someone read-only access to one record, and run the checks that compare what the system says with what it does.
Replay and repair
—Run a past request again with the same input, or correct a failed one and run it again; the new entry points back to the old one.
Saved sequences
—Save a sequence of past requests under a name and run it again as one action. Sequences that keep succeeding can become new rows; those that send or change something start switched off until approved.
Schedules and triggers
—Run any row every so many minutes, at a set hour each day, or when an event arrives; pause or switch off a schedule; and send matching events to another address as they happen.
Tasks
—Add, edit, assign, group, complete and delete tasks, keep a shared work thread that every AI agent reads first, and run the next open task.
Uses
What a business uses these actions for.
Examples of the work these actions do. They describe uses, not results.
See exactly what was sent, to whom, when, and by which AI model.
Settle a disagreement with the record instead of memory.
Run a morning report at 8 every day.
How it is run
How any of these actions is run.
The same way as every other action in the Directory: one request, the same permissions, one record.
You don’t have to pick an action yourself. You text what you want; the AI assistant picks the action and runs it within the permissions you set. The result comes back to you, and the request, the result and who asked are written to the Ledger, the record of everything the system has done.
Every action is one row in the Directory, and each row can be run — ways: a text, a link, a spreadsheet cell, an iPhone Shortcut, a command, or an AI model’s request. Every way goes through dispatch: one web address that looks the action up, checks the permissions, runs it on the right computer, sends back the result and writes a Ledger entry. The same action answers every way, under the same limits.
Dispatch takes an HTTP POST (a standard web request) of {"key": "<action name>", "args": {…}}. The same key works over the API (the web address your software calls), MCP (Model Context Protocol, the standard way AI apps connect to outside tools), the command line (CLI), a webhook (an address another program posts to), a spreadsheet cell or a Shortcut. A token (a key or a link) can be limited to exactly the actions you allow; every call, and every refusal, is a Ledger entry.
// One action from this family, as dispatch receives it
{ "key": "…", "args": { … } }Ask for this.
The text below opens ready to send. Add a line about your business, and I’ll reply with what this family of actions would do for it.
Every family
Everything else the system can do.
Every family of actions, with how many actions it has right now.