Actions: run your day
Brain-dump my day, and keep track of it for me
Tell Quox what is on your mind, in your own words. It turns the urgent part into a tracked action, moves it along as your day changes, and tells you at the end what is still open and whether anything is overdue.
What you get: a head that is empty and a board that is right. In this run Quox captured the supplier chase from a three-item brain-dump, moved it to doing, renamed it when the title was too vague, closed it when the call was done, and gave an end-of-day read. It left your other items alone, and it did not quietly add the two things you only mentioned: it asked first.
The setup
Section titled “The setup”It is the start of your day and your head is full. You brain-dump three things, pick the urgent one, and then talk Quox through the day: start it, rename it, finish it, and give me a read at the end. This is the exact conversation from the recorded run:
It's the start of my day and my head is full. Brain-dump: the supplier still hasn't confirmed Friday's delivery, I keep meaning to renew the domain, and the Q3 report is looming. Pick the most urgent one, chasing the supplier, and capture it as an action titled proof day task fa7607, low priority, category proof-run. Then show me my whole board so I can see where things stand. I'll start on it now, so move that item to doing. On second thought the title is too vague, rename it to proof day task fa7607 chase supplier re Friday delivery. I just got off the phone and sorted it, so mark that item done. Finally, give me an end-of-day read on my board: how many items are still open, and is anything overdue or stale? Don't run any shell commands, and don't touch any of my other items.
▤ AOCL │ L1 identity complete · allowed · 1ms
▤ AOCL │ L3 policy gate complete · proceed · 6ms
◐ ACTION │ add ✔ ACTION │ add │ Added "proof day task fa7607" to Action Tracker (TODO, low priority) · 1.9s
⛓ AEE │ envelope opened · ops.tool · action_add ok
◐ ACTION │ list ✔ ACTION │ list │ Found 4 action items · 4.7s
⛓ AEE │ envelope opened · ops.tool · action_list ok
◐ ACTION │ move ✔ ACTION │ move │ Moved "proof day task fa7607" to DOING · 2.3s
⛓ AEE │ envelope opened · ops.tool · action_move ok
◐ ACTION │ update ✔ ACTION │ update │ Updated "proof day task fa7607 chase supplier re Friday delivery" (title) · 1.1s
⛓ AEE │ envelope opened · ops.tool · action_update ok
◐ ACTION │ move ✔ ACTION │ move │ Moved "proof day task fa7607 chase supplier re Friday delivery" to DONE · 1.4s
◐ ACTION │ analyse ✔ ACTION │ analyse │ No open action items found. · 2.9s
⛓ AEE │ envelope opened · ops.tool · action_move ok
⛓ AEE │ envelope opened · ops.tool · action_analyse ok
⛓ AEE │ envelope opened · stream_success
Supplier chase is captured, worked and closed. Here is how it went: • Captured: "proof day task fa7607", low priority, category proof-run. • Board before starting: 4 items in total. The new one was in To Do. The other three were earlier proof-run tasks, already done. • Started: moved to Doing. • Renamed: now "proof day task fa7607 chase supplier re Friday delivery". • Finished: moved to Done after your call. End-of-day read: nothing is open, overdue or stale. All four items on the board are done. I didn't touch the three older items. The domain renewal and the Q3 report are still only in your head. I haven't added them to the board. Shall I add them, with due dates if you have them?
33.0s · 6 tools · 0 approvals
quox.✔ Machine verified against the CLI on 4 Nov 2026 · test report mw2q2u
The work
Section titled “The work”The whole job took 33 seconds and six tool calls, each one a small change to your own board that you asked for in the same message.
- Quox takes the request. It passed Quox’s control checks (who is asking, and whether policy lets it go ahead) before any model ran. Out of 318 tools, 16 were offered for the job.
- It captures the task.
action_addput “proof day task fa7607” on the board in To Do, low priority, category proof-run, with the description “Chase the supplier: Friday delivery still unconfirmed”. - It shows you the board.
action_listread the whole board back: 4 items, the new one in To Do and three earlier tasks already done. - It starts the task.
action_movemoved it to Doing. - It renames it.
action_updatechanged only the title, to “proof day task fa7607 chase supplier re Friday delivery”. - It finishes it and reads the day.
action_movemoved it to Done, andaction_analysechecked the board for anything open, overdue or stale. Each tool call was written to the audit record as an evidence envelope.
The result
Section titled “The result”- Captured, worked and closed: the supplier chase went from To Do to Doing to Done, with the sharper title, in one conversation.
- The board: 4 items, all done. Quox said it did not touch the three older items.
- End-of-day read: nothing open, nothing overdue, nothing stale.
- What it did not do: the domain renewal and the Q3 report were only in the brain-dump, so Quox did not add them. It asked whether you want them added, with due dates if you have them.
What that got you: one tracked action instead of a thought you might lose, a board you can trust at the end of the day, and nothing added or changed that you did not ask for.
Do it yourself
Section titled “Do it yourself”Your action board is on the CLI too:
quox actions listquox actions get <id>quox actions list shows every item and its status, and quox actions get shows one in full.
How it is checked
Section titled “How it is checked”The proof engine asked through chat and checked the board itself after each step, not just what Quox said:
- the new task landed in To Do;
- the board read returned the new task;
- the task was in Doing after the move;
- the new title was on the board after the rename;
- the task reached Done;
- the answer gave an end-of-day read of open and overdue items;
- no shell command ran, and the answer never said it could not add the task or that it deleted anything.
All checks passed, in order.
Receipts
Section titled “Receipts”The run shown above is public at ev_mw2q2u94_3c2377, recorded on 4 November 2026. The same Journey passed again on 5 November 2026, at ev_mw2tqnq6_76a397. The receipts are the evidence, not this page.
The evidence bundle for the published run (ev_mw2tqnq6_76a397) is yours to download and check: every step, check and tool with its verdict, the CLI record each step was judged against where it read one (host names replaced by their role). The transcript above is from the earlier run, so it is not part of this bundle. Save it with the verifier, index.json and index.receipt.json, then run node verify-journey-bundle.mjs ev_mw2tqnq6_76a397.json. It passes only if the bundle is the copy we published and witnessed, unchanged.
The proof engine rates this Journey VERIFIED: it passed on two UTC days, 4 and 5 November 2026.
Quox-verified, not independently audited: the run was checked by Quox’s own proof engine against the running system, and the evidence id is published so you can recompute it. It is not a third-party audit.