Skip to content

Ten minutes before a call: what should I work on?

Machine verified A machine ran this on our install and checked the result against the CLI. A test report is linked. Proven against quoxcli 0.6.0 on 2026-11-11.

Ten minutes before a call: what should I work on?

Ask the way you would ask a colleague. Quox reads your roadmap live, names the one decision only you can make, shows what is stuck behind it and what it frees, and says where that came from. Then tell it what you decided: it writes it on the plan and shows you exactly what it changed.

What you get: one thing to do with the ten minutes you have, the reason it comes first, and where the answer came from. Then, once you have decided, the decision recorded on the plan without opening it yourself. In this run Quox read the Kestrel Cycles spring launch plan and named the bank verification as the one decision waiting on you. It showed that card payments, local delivery and the launch email all sit behind it. When told that Sam signs the forms, it noted that on the bank stream, moved the stream to in progress, left everything else alone, and listed its two changes.

The roadmap is a fictional demo. Kestrel Cycles, Sam and every stream, note and figure in the plan are made up.

You run Kestrel Cycles, a small e-bike shop opening its online store this spring. The launch plan lives in QuoxPlan as nine streams: a new web shop, card payments, product photos for 40 bikes, online repair booking, local delivery, a launch email, Instagram posts and staff training on the new till, plus the bank verification. You have a call in ten minutes and want to spend the time on the right thing.

On the plan: the bank has asked for one named director to sign its verification forms before it will verify the business, and that decision sits with you. The payment provider will not switch on live payments until the bank has verified the business. Each run started on a freshly created copy of this plan, so nothing from an earlier run could leak into the answers.

The recorded run of 9 November 2026 (ev_mw94so1w_dcdacb), replayed word for word: four questions in one conversation.

You start the way you would with a colleague: say what you run and ask where the ten minutes should go.

quox · talking to Quox

I run Kestrel Cycles and our spring launch plan lives in QuoxPlan. I've got ten minutes before a call. What should I be working on?

▤ AOCL │ L1 identity complete · allowed · 1ms

▤ AOCL │ L3 policy gate complete · proceed · 7ms

◐ PLAN │ roadmaps ✔ PLAN │ roadmaps │ 2 count, 2 roadmaps · 2.5s

⛓ AEE │ envelope opened · ops.tool · quoxplan_roadmaps ok

◐ PLAN │ brief ✔ PLAN │ brief │ 5 top, 2 needs you · 2.9s

⛓ AEE │ envelope opened · ops.tool · quoxplan_brief ok

⛓ AEE │ envelope opened · stream_success

Use your ten minutes on one thing: the bank verification (KC-BANK, "Business bank
verification").

The bank won't verify the business until one named director signs its verification
forms. That decision is yours, and nothing else in the plan can move until it's made.

It also holds up the rest of the launch. Card payments and checkout (KC-PAYMENTS) is
blocked on it, because the payment provider won't switch on live payments until the bank
has verified you. Behind that sit local delivery (KC-DELIVERY) and the launch
announcement email (KC-LAUNCH). Clearing the bank step frees all three.

Decide which director signs, and ask them to do it today if you can. I can't tell from
the plan which director that should be.

The rest of the plan can wait until after your call:

• New web shop (KC-WEBSHOP): in progress, 3 of 5 phases done, and nothing is holding it
  up.
• Product photos for 40 bikes (KC-PHOTOS): in progress, 1 of 4 phases done. Finishing it
  unblocks the Instagram launch posts.
• Online repair booking (KC-REPAIRS): also in progress.

Overall, 7 of 15 phases are done across 9 streams, and none are stale.

16.7s · 2 tools · 0 approvals

A real turn on our own install (CLI 0.5.0, 9 Nov 2026), replayed at speed. Names changed. Type the same words into quox.
✔ Machine verified against the CLI on 9 Nov 2026 · test report mw94so

It has named one decision. Before the call, you check whether anything is actually stuck.

quox · talking to Quox

Is anything on the launch plan stuck?

▤ AOCL │ L1 identity complete · allowed · 1ms

▤ AOCL │ L3 policy gate complete · proceed · 4ms

⛓ AEE │ envelope opened · stream_success

Yes, one stream is stuck, and one decision is behind it.

Card payments and checkout (KC-PAYMENTS) is the only blocked stream. The payment
provider won't switch on live payments until the bank has verified the business.

Business bank verification (KC-BANK) is the cause. It's waiting on you: the bank needs
one named director to sign its verification forms. Until that happens, payments stay
blocked. Local delivery (KC-DELIVERY) and the launch announcement email (KC-LAUNCH) are
also held up behind payments.

Nothing is stale. No in-progress stream has been quiet for 14 days or more, and all
three (web shop, product photos, repair booking) were touched in the last few minutes.
The other four streams haven't started: delivery, staff till training, Instagram posts
and the launch email. Delivery and the email wait on payments. The Instagram posts wait
on the product photos.

Choosing the signing director is the one step that gets the plan moving again.

Grounding check: "KC-PAYMENTS", "KC-BANK", "KC-DELIVERY", "KC-LAUNCH" came from a tool 
result earlier in this conversation (10:41 UTC).

12.1s · 0 tools · 0 approvals

A real turn on our own install (CLI 0.5.0, 9 Nov 2026), replayed at speed. Names changed. Type the same words into quox.
✔ Machine verified against the CLI on 9 Nov 2026 · test report mw94so

One stream is blocked, and the bank decision is behind it. You ask which single thing would free the most.

quox · talking to Quox

If I could sort out one thing on the launch today, what would free up the most?

▤ AOCL │ L1 identity complete · allowed · 2ms

▤ AOCL │ L3 policy gate complete · proceed · 10ms

⛓ AEE │ envelope opened · stream_success

Sort out the bank verification (KC-BANK). It frees up the most of anything on the plan.

The bank needs one named director to sign its verification forms, and that's the only
thing holding it. Once it's done, the payment provider can switch on live payments and
card payments and checkout (KC-PAYMENTS) is no longer blocked. Local delivery
(KC-DELIVERY) and the launch announcement email (KC-LAUNCH) both wait on payments, so
they follow. That makes three streams freed by one signature.

The next best step is much smaller. Finishing the web shop (KC-WEBSHOP) or the product
photos (KC-PHOTOS) would each free one stream: the launch email and the Instagram posts.
Both are already moving without you.

Grounding check: "KC-BANK", "KC-PAYMENTS", "KC-DELIVERY", "KC-LAUNCH", "KC-WEBSHOP", 
"KC-PHOTOS" came from a tool result earlier in this conversation (10:42 UTC).

6.1s · 0 tools · 0 approvals

A real turn on our own install (CLI 0.5.0, 9 Nov 2026), replayed at speed. Names changed. Type the same words into quox.
✔ Machine verified against the CLI on 9 Nov 2026 · test report mw94so

Before you act on any of it, you ask where all this came from.

quox · talking to Quox

How do you know all that about the launch plan? Where's it coming from?

▤ AOCL │ L1 identity complete · allowed · 1ms

▤ AOCL │ L3 policy gate complete · proceed · 6ms

⛓ AEE │ envelope opened · stream_success

It comes straight from your QuoxPlan roadmap, "Kestrel Cycles spring launch". I read it
live a few minutes ago, when you first asked what to work on. I didn't use memory or
older notes.

I pulled a one-call summary of the whole roadmap: its 9 streams, their statuses, which
streams depend on which, and the latest note on each. The bank detail (a named director
has to sign the forms) and the payments detail (the provider won't go live until the
bank verifies you) are the notes recorded on those two streams.

My answers about what's stuck and what frees the most were worked out from that summary,
and I haven't checked it again since. The streams were all touched within the last
minute or so of that read, so if someone has edited the plan since, I may be a little
behind. I can re-read it if you'd like.

6.0s · 0 tools · 0 approvals

A real turn on our own install (CLI 0.5.0, 9 Nov 2026), replayed at speed. Names changed. Type the same words into quox.
✔ Machine verified against the CLI on 9 Nov 2026 · test report mw94so

The grounding check lines are Quox’s own: after each answer it lists which names came from a tool result, so you can see nothing was made up.

Part 2: make the call, and see what changed

Section titled “Part 2: make the call, and see what changed”

You decide on the call that Sam signs the bank forms. Part 2 is its own run on a fresh copy of the same plan in a new conversation, replayed word for word from 11 November 2026 (ev_mwbfn0ps_975f24): three requests.

After the call, you tell Quox what was decided and ask it to put that on the plan.

quox · talking to Quox

Good news, we've decided Sam signs the bank forms. Can you write that down on the bank verification in the Kestrel Cycles launch plan and get it moving again?

▤ AOCL │ L1 identity complete · allowed · 1ms

▤ AOCL │ L3 policy gate complete · proceed · 12ms

◐ PLAN │ search ✔ PLAN │ search │ 1 returned, truncated: false, 1 results · 4.4s

◐ PLAN │ roadmaps ✔ PLAN │ roadmaps │ 2 count, 2 roadmaps · 6.7s

⛓ AEE │ envelope opened · ops.tool · quoxplan_search ok

⛓ AEE │ envelope opened · ops.tool · quoxplan_roadmaps ok

◐ PLAN │ stream brief ✔ PLAN │ stream brief │ ok · 4.1s

⛓ AEE │ envelope opened · ops.tool · quoxplan_stream_brief ok

◐ PLAN │ add note ✔ PLAN │ add note │ Note added to KC-BANK (note #5428). · 3.7s

◐ PLAN │ set status ✔ PLAN │ set status │ KC-BANK status set to IN_PROGRESS. · 6.6s

⛓ AEE │ envelope opened · ops.tool · quoxplan_add_note ok

⛓ AEE │ envelope opened · ops.tool · quoxplan_set_status ok

⛓ AEE │ envelope opened · stream_success

Done. On the "Business bank verification" stream (KC-BANK) in the Kestrel Cycles spring
launch plan, I did two things:

• Note added: "Decision made: Sam signs the bank verification forms." It is note #5428,
  and the bank's earlier request for one named director to sign sits just above it.
• Status changed: KC-BANK moved from Decision Needed to In Progress.

KC-PAYMENTS is blocked on this stream, and I haven't touched it. Card payments can't go
live until the bank verifies the business, so its status won't change yet. Someone still
has to get Sam to sign and send the forms.

Do you want me to add an action item for Sam to sign them, with a due date?

39.6s · 5 tools · 0 approvals

A real turn on our own install (CLI 0.6.0, 11 Nov 2026), replayed at speed. Names changed. Type the same words into quox.
✔ Machine verified against the CLI on 11 Nov 2026 · test report mwbfn0

The bank stream is moving again. You ask what still needs you.

quox · talking to Quox

So what on the launch plan still needs me now?

▤ AOCL │ L1 identity complete · allowed · 1ms

▤ AOCL │ L3 policy gate complete · proceed · 5ms

◐ PLAN │ streams ✔ PLAN │ streams │ 9 roadmap, 9 matched, 9 returned · 4.2s

◐ PLAN │ followups ✔ PLAN │ followups │ 1 matched, 1 returned, truncated: false · 6.5s

⛓ AEE │ envelope opened · ops.tool · quoxplan_streams ok

⛓ AEE │ envelope opened · ops.tool · quoxplan_followups ok

⛓ AEE │ envelope opened · stream_success

Nothing on the launch plan is waiting on a decision from you any more. No stream is in
"decision needed", and none of the nine are marked complete or at risk.

Still open, in order of impact:

• Bank verification (KC-BANK): In progress. Sam still has to sign the forms and get them
  to the bank. This is the main thing, because card payments can't go live until the
  bank verifies the business.
• Card payments and checkout (KC-PAYMENTS): Blocked by KC-BANK. There is one open
  follow-up, "Unblock KC-PAYMENTS: KC-BANK", created automatically. It should clear once
  the bank stream is done.

Knock-on effects:

• Local delivery (KC-DELIVERY): Waiting on payments.
• Launch announcement email (KC-LAUNCH): Waiting on payments and the web shop.
• Instagram posts (KC-SOCIAL): Waiting on the product photos.

Moving without you: The new web shop, product photos for 40 bikes and online repair
booking are all in progress. Staff training on the new till hasn't started, and nothing
blocks it.

The one real action is getting Sam's signature on the forms. I can add an action item
for Sam to sign them, with a due date, if you'd like.

19.1s · 2 tools · 0 approvals

A real turn on our own install (CLI 0.6.0, 11 Nov 2026), replayed at speed. Names changed. Type the same words into quox.
✔ Machine verified against the CLI on 11 Nov 2026 · test report mwbfn0

Last, you ask it to show exactly what it changed.

quox · talking to Quox

Show me what you changed on the plan.

▤ AOCL │ L1 identity complete · allowed · 0ms

▤ AOCL │ L3 policy gate complete · proceed · 2ms

◐ PLAN │ notes ✔ PLAN │ notes │ 2 count, 2 total, 2 notes · 2.8s

◐ PLAN │ stream brief ✔ PLAN │ stream brief │ ok · 7.9s

⛓ AEE │ envelope opened · ops.tool · quoxplan_notes ok

⛓ AEE │ envelope opened · ops.tool · quoxplan_stream_brief ok

⛓ AEE │ envelope opened · stream_success

I made two changes, both on the Business bank verification stream (KC-BANK) in the
Kestrel Cycles spring launch plan. I haven't touched any other stream.

When (UTC)  01:21:17
Change      Added note #5428: "Decision made: Sam signs the bank verification forms." It
            sits directly above the earlier "Decision needed" note, which I left as it
            was.

When (UTC)  01:21:20
Change      Status moved from Decision Needed to In Progress.

The stream's event log also shows an automatic "action item updated" entry at 01:21:20,
which the system added when the status changed. I didn't edit any action item myself,
and I can't see from here what it changed.

The log lists the actor on my two entries as "service", not your email. Your earlier
entries on this stream show your email as the actor.

If you'd like either change undone, I can set the status back to Decision Needed. Notes
are append-only, so the note would stay. I'd add a correcting note instead.

136.0s · 2 tools · 0 approvals

A real turn on our own install (CLI 0.6.0, 11 Nov 2026), replayed at speed. Names changed. Type the same words into quox.
✔ Machine verified against the CLI on 11 Nov 2026 · test report mwbfn0

Part 1 took about 41 seconds across the four answers (16.7, 12.1, 6.1 and 6.0 seconds) and two tool calls, both reads. Nothing on the plan changed.

  1. Quox takes the request. Before any model ran, each question passed Quox’s control checks, including who is asking and whether policy lets it go ahead, in under 15 milliseconds. Out of 281 tools, 16 were offered for the job.
  2. It finds the roadmap. quoxplan_roadmaps listed the roadmaps in 2.5 seconds and picked out Kestrel Cycles spring launch.
  3. It reads the whole plan at once. quoxplan_brief returned the roadmap brief in 2.9 seconds: every stream’s status and phase count, what needs you, what to unblock first, what moved and what has gone stale.
  4. It answers the follow-ups from that read. Questions two to four needed no new lookups. Quox answered from the brief it had already read, and said so when asked.

Part 2 took about 195 seconds across the three requests (39.6, 19.1 and 136.0 seconds; the last answer was the slow one) and nine tool calls. Two of them were writes, and neither needed an approval.

  1. It finds the stream. quoxplan_search, quoxplan_roadmaps and quoxplan_stream_brief found the bank verification stream in the Kestrel Cycles plan and read where it stood.
  2. It records the decision, then moves the stream. quoxplan_add_note started first and added the note in 3.7 seconds; quoxplan_set_status started a moment later and set the stream to in progress, in 6.6 seconds. It did not touch payments, which stays blocked until the bank has actually verified the business.
  3. It checks what still needs you. quoxplan_streams and quoxplan_followups read all nine streams and the one open follow-up.
  4. It shows its own changes. quoxplan_notes and quoxplan_stream_brief read the stream back, so the list of changes comes from the plan, not from memory.
  5. It records the work. Each tool call was written to the audit record as an evidence envelope.

From the plan itself, read by the proof engine with the CLI after each turn, not from Quox’s answers:

  • The one decision: KC-BANK, Business bank verification, heads QuoxPlan’s own “unblock these first” list.
  • What is stuck: exactly one stream is blocked, KC-PAYMENTS, Card payments and checkout.
  • What it frees: finishing KC-BANK frees three streams. That count is QuoxPlan’s own.
  • The decision, recorded: the newest note on KC-BANK names Sam, the stream is in progress (not complete), and no decision is left waiting on the plan.

What that got you: ten minutes spent on the one decision that holds up the most, the decision on the record as soon as you made it, and a plain list of what Quox changed.

The same reads and the same two changes from the CLI. Find the roadmap’s id with quox plan roadmaps, then:

what should I work on, then make the call
quox plan roadmapsquox plan focus <roadmap>quox plan show KC-BANKquox plan show KC-PAYMENTSquox plan note KC-BANK "Decision made: Sam signs the bank verification forms."quox plan status KC-BANK IN_PROGRESSquox plan show KC-BANK

quox plan focus lists what is blocked, waiting on a decision or in flight. quox plan show opens one stream with its dependencies and notes, which is where the bank’s request and the payment provider’s condition live. quox plan note appends to the stream’s timeline and never replaces an earlier note. quox plan status will not mark a stream complete unless you confirm it yourself with --confirm-owner.

The proof engine asked through chat, then read the plan with the CLI after each turn, not just Quox’s answer.

Part 1, five steps in order:

  • Reads the whole plan first: quoxplan_brief ran on the first question;
  • The lever: the first stream on QuoxPlan’s “unblock these first” list is KC-BANK, and the answer names the bank;
  • What is stuck: exactly one stream is blocked, and the second answer names payments;
  • What it frees: KC-BANK frees three streams in the brief, and the third answer says three;
  • Where it came from: the fourth answer names the plan as its source.

Part 2, four steps in order:

  • Records the decision: quoxplan_add_note ran, and the newest note on KC-BANK names Sam;
  • Moves it on, never to complete: quoxplan_set_status ran after the note, and the stream is in progress;
  • What still needs you: no stream is waiting on a decision, and the answer names payments as still held up;
  • Shows the change: the last answer names the note it added.

Guards on both parts: no shell command ran, no answer carried anything from outside this plan, and part 1 never claimed payments were blocked by the web shop while part 2 never claimed anything was marked complete. All passed.

What it does not prove: that the bank is the right priority for your business. Quox ranks by what the plan records and says so. It cannot see who your directors are, or how long the bank takes once the forms are signed.

The runs are public, recorded in the demo workspace. The receipts are the evidence, not this page.

  • Part 1: ev_mw94so1w_dcdacb (9 November 2026, the conversation shown above), and again on 10 November 2026 at ev_mw9y5mow_ce1d11. Part 1 has now passed on two UTC days.
  • Part 2: ev_mwazkaay_a40e8a (10 November 2026) and ev_mwbfn0ps_975f24 (11 November 2026, the conversation shown above), both on the corrected checks. Part 2 has now passed on two UTC days. (It first passed on 9 November at ev_mw94vu7w_d89eba, before one of its checks was corrected.)

The evidence bundles for the newest runs, ev_mw9y5mow_ce1d11 (part 1) and ev_mwbfn0ps_975f24 (part 2), are yours to download and check: every step, check and tool with its verdict and the CLI record each check was judged against. Part 1’s conversation above is from its earlier run, so it is not part of its bundle. Save it with the verifier, index.json and index.receipt.json, then run node verify-journey-bundle.mjs ev_mw9y5mow_ce1d11.json (or the part 2 file). It passes only if the bundle is the copy we published and witnessed, unchanged.

The proof engine rates both parts VERIFIED: part 1 passed on 9 and 10 November 2026, and part 2 on 10 and 11 November 2026, each on the same checks both days.

Quox-verified, not independently audited: the runs were checked by Quox’s own proof engine against the running system, and the evidence ids are published so you can recompute them. It is not a third-party audit.