Skip to content
quoxcli

Record a promise, then close it

Machine verified A machine ran this on our install and checked the result against the CLI. A test report is linked. CLI 0.3.1, checked 2026-10-15.

Can I record a promise?

Record a commitment with an owner and a due date, close it on the record, then list what is still open.

What you get: promises that live on the record. Each one has an owner, a due date and a status, so nothing said in passing gets lost.

Ask Quox

Section titled “Ask Quox”

Say what the promise is, who owns it and when it is due. This test records one and cancels it straight away:

quox · talking to Quox

As a test, record a commitment with the promise "proof resolve e28c4b", owned by me and due 2027-01-31, then straight away mark it cancelled with the note "proof engine test".

▤ AOCL │ L1 identity complete · allowed · 1ms

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

◐ COMMITMENT │ create ✔ COMMITMENT │ create │ ok · 2.5s

◐ COMMITMENT │ resolve ✔ COMMITMENT │ resolve │ ok: true, escalation filed: false · 1.4s

⛓ AEE │ envelope opened · stream_success

Both steps went through.

• Recorded: the commitment "proof resolve e28c4b" (ID  ART_MV8Y870W_9FCDE97D2038 ) was
  created with you as owner and a due date of 2027-01-31. It was signed and the
  signature verified.
• Cancelled: I then marked it cancelled with the note "proof engine test". It went from
  open to cancelled, and no escalation was filed.

21.7s · 2 tools · 0 approvals

A real turn on our own install (CLI 0.3.0, 15 Oct 2026), replayed at speed. Names changed. Type the same words into quox.
✔ Machine verified against the CLI on 15 Oct 2026 · test report mv8y7y

Quox recorded the commitment, which was signed and its signature checked, then closed it as cancelled with a note. Both steps are on the record.

Do it yourself

Section titled “Do it yourself”

1. List commitments

Section titled “1. List commitments”
commitments 
quox tool exec commitment_list --args '{"filter":"cancelled"}' | jq -r '.commitments[] | [.promise, .status, .due_at] | @tsv'proof resolve c70baa	cancelled	2027-01-31T00:00:00.000Zproof resolve 033cc1	cancelled	2027-01-31T00:00:00.000Zproof resolve e28c4b	cancelled	2027-01-31T00:00:00.000Z
From a real run on our own install, on its test commitments.

filter takes open (the default), overdue, all, or one status: fulfilled, escalated or cancelled. Use overdue to find promises that need chasing.

2. Record a commitment

Section titled “2. Record a commitment”

quox tool exec commitment_create --args '{"promise":"send the release notes","owner":"user","due_at":"2027-01-31"}' records one. promise and owner are required, and the due date is optional.

3. Close it

Section titled “3. Close it”

quox tool exec commitment_resolve --args '{"commitment_id":"<id>","status":"fulfilled","note":"sent"}' closes it. The status is fulfilled, escalated or cancelled. Escalating puts a card in a person’s inbox.

What just happened

Section titled “What just happened”

Quox made two changes on your own Quox, with your permissions: it created a commitment and then resolved it. Only an open commitment can be resolved, so a closed promise stays closed.

Check it yourself

Section titled “Check it yourself”

Run step 1 with "filter":"all" to see every commitment and the status each one ended in.

Undo

Section titled “Undo”

A resolved commitment is not reopened. If a promise was closed by mistake, record it again as a new commitment.

Next

Section titled “Next”