Mark a stream blocked, then back in progress
This stream is stuck. Can Quox flag it?
Say a stream is blocked, or moving again, and Quox sets its status. Then read and set it yourself.
What you get: a roadmap that shows what is stuck and what is moving, kept up to date in one sentence. You need: a stream on your roadmap. About 2 minutes.
Ask Quox
Section titled “Ask Quox”Name the stream and the status you want:
Our Customer onboarding revamp stream is stuck at the moment. Can you set its status to blocked?
▤ AOCL │ L1 identity complete · allowed · 1ms
▤ AOCL │ L3 policy gate complete · proceed · 10ms
◐ PLAN │ search ✔ PLAN │ search │ 1 returned, truncated: false, 1 results · 5.4s
⛓ AEE │ envelope opened · ops.tool · quoxplan_search ok
◐ PLAN │ set status ✔ PLAN │ set status │ proof-seed status set to BLOCKED. · 2.9s
⛓ AEE │ envelope opened · ops.tool · quoxplan_set_status ok
⛓ AEE │ envelope opened · stream_success
"Customer onboarding revamp" (stream proof-seed, in the proof-engine roadmap) is now set to BLOCKED. It was IN_PROGRESS before. I haven't recorded why it's stuck. If you tell me the blocker, I can add it as a note on the stream so the next reader sees the reason.
24.4s · 2 tools · 0 approvals
quox.✔ Machine verified against the CLI on 9 Nov 2026 · test report mw9khi
Quox set the stream to BLOCKED and confirmed the change. When the work starts moving again, say so:
We are moving again on the Customer onboarding revamp stream. Please set its status back to in progress.
▤ AOCL │ L1 identity complete · allowed · 1ms
▤ AOCL │ L3 policy gate complete · proceed · 3ms
◐ PLAN │ search ✔ PLAN │ search │ 1 returned, truncated: false, 1 results · 3.4s
⛓ AEE │ envelope opened · ops.tool · quoxplan_search ok
◐ PLAN │ set status ✔ PLAN │ set status │ proof-seed status set to IN_PROGRESS. · 3.5s
⛓ AEE │ envelope opened · ops.tool · quoxplan_set_status ok
⛓ AEE │ envelope opened · stream_success
Done. The Customer onboarding revamp stream (proof-seed, in the proof-engine roadmap) was blocked, and it is now marked in progress.
19.7s · 2 tools · 0 approvals
quox.✔ Machine verified against the CLI on 9 Nov 2026 · test report mw9kj5
Both runs were on our own install, on a test stream named “Customer onboarding revamp” (id proof-seed).
Do it yourself
Section titled “Do it yourself”1. Read the stream’s status
Section titled “1. Read the stream’s status”quox plan show proof-seed proof-seed Customer onboarding revamp⬗ IN_PROGRESS tier 3 #1 The second line gives the status, the tier and the stream’s position on the roadmap.
2. Set the status
Section titled “2. Set the status”quox plan status proof-seed BLOCKEDquox plan status proof-seed IN_PROGRESSUse your own stream id. A note saying why it is blocked helps whoever reads the stream next: quox plan note proof-seed "waiting on the supplier".
What just happened
Section titled “What just happened”Quox changed the status of one stream on your own Quox, with your permissions. The change is in the stream’s history, so anyone reading the stream sees when it moved.
Check it yourself
Section titled “Check it yourself”quox plan focus lists what is blocked, in flight or waiting on a decision across the roadmap, so a stream you have just blocked shows up there.
Set the status back with quox plan status <streamId> <status>. The one status Quox will not set for you is COMPLETE: quox plan status <streamId> COMPLETE --confirm-owner is the owner’s call.