Skip to content

See who decided a proposal

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.2 on 2026-11-14.

Who said no, and when?

Every yes or no on a proposal leaves a decision receipt. Ask for a proposal's receipts and get who decided, what they decided and why.

What you get: each decision on one proposal: the verdict, the revision and round it applied to, who made it, their role, whether they stepped up, and the reason given.

quox · talking to Quox

For the proposal "Rotate the Kestrel till API key", what decision receipts are there? How many?

▤ AOCL │ L1 identity complete · allowed · 0ms

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

◐ QUOX │ cli ✔ QUOX │ cli │ 0 exit code, 3632 duration ms · 4.6s

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

◐ QUOX │ cli ✔ QUOX │ cli │ 0 exit code, 6056 duration ms · 7.7s

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

⛓ AEE │ envelope opened · stream_success

"Rotate the Kestrel till API key" (prp_mwe6sm687bbec2ae7260abb6) has one decision
receipt.

• Receipt: rcpt_mwe6u6uf5aebd3faa8e60e2d
• Decision: reject, on revision 1, round 1
• Decided by: a human with the admin role (user 01M6NW…), with no step-up
• Reason code: later_window, with no comment
• Action hash: c50c88c6…1effeba, which matches the proposal's hash

The proposal's state is rejected, which fits the receipt. The reason code suggests it
was turned down for now and could come back in a later window. Nothing has been rotated.

22.1s · 2 tools · 0 approvals

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

Quox ran two commands: quox proposals list to find the proposal, then quox proposals receipts. “Rotate the Kestrel till API key” has one decision receipt. It is a reject, on revision 1, round 1, made by a person with the admin role and no step-up. The reason code is later_window, with no comment, and the action hash matches the proposal’s. Quox said the proposal’s state is rejected, which fits, and that nothing was rotated. Quox only read.

proposals list
quox proposals listID                              State       What                                          Risk    Rev    Round    Expires    Assigned to    Deferred untilprp_mwhr3nov57892814bf81e1f6    pending     Photograph and price the spring bike range    low     1      1prp_mwe6sm687bbec2ae7260abb6    rejected    Rotate the Kestrel till API key               low     1      1
From the same scratch workspace (fictional Kestrel Cycles data), run after the turn above. Rows trimmed to two.
proposals receipts
quox proposals receipts prp_mwe6sm687bbec2ae7260abb6Receipt                          Verb      Rev    Round    By         Role     Step-up    Decidedrcpt_mwe6u6uf5aebd3faa8e60e2d    reject    1      1        01M6NW…    admin    0          2026-11-12T23:37:37.572Z
Same workspace. User ID shortened.

Use the ID from the list. Each row is one decision. Rev and Round say which version of the proposal it applied to, By and Role say who decided, and Step-up 0 means no step-up check was recorded.

Quox and the terminal read the same receipt. Reading receipts changes nothing. The proposal was rejected, so, as Quox said, nothing was rotated.