Skip to content

Check one promise

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-16.

Where am I with that promise?

Ask about one promise in plain words and get its status, its due date and where it came from. Then read the record yourself.

What you get: one promise’s status, due date and source, with a plain note of what the record can and cannot show.

Name the promise the way you would say it:

quox · talking to Quox

Where am I with sending Priya the servicing plan pricing sheet? When did I say it would be done?

▤ AOCL │ L1 identity complete · allowed · 1ms

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

◐ DELEGATE │ delegate_to_agent agent_id=ladon ✔ DELEGATE │ delegate_to_agent agent_id=ladon │ 3 tools used, 3 tool outcomes · 28.9s

◐ Ladon › COMMITMENTS │ list ✔ Ladon › COMMITMENTS │ list │ 15ms

◐ Ladon › COMMITMENTS │ show ✔ Ladon › COMMITMENTS │ show │ 13ms

◐ Ladon › INBOX │ accounts ✔ Ladon › INBOX │ accounts │ 27ms

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

⛓ AEE │ envelope opened · stream_success

The commitment is still open. I can't tell whether you've already sent the sheet.

• What you promised: "Send Priya the servicing plan pricing sheet" (commitment
  cmt_0mwdn1gu9b4622f2a3f396e598e07). You logged it yourself on 12 November at 14:23
  UTC, linked to the Kestrel Cycles servicing review that day.
• When you said it would be done: 20 November 2026, which the ledger records as a date
  you stated. It's stored as midnight UTC at the start of Friday the 20th. I'd treat
  Thursday the 19th as the real deadline, so you have three to four days.
• Whether it's been sent: Ladon couldn't check. No mailboxes are connected, so there was
  no sent mail to search.

If you've already sent it, tell me and Ladon can ask to mark it done. That files an
approval card for you, and nothing changes until you approve it.

39.7s · 4 tools · 0 approvals

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

Quox handed the question to Ladon, which found the commitment in your list, read its record, and checked whether a mailbox was connected. It said the promise is still open and that you logged it yourself on 12 November at 14:23 UTC, linked to the Kestrel Cycles servicing review. The due date is 20 November 2026, which the ledger records as a date you stated. Because it is stored as midnight UTC at the start of the 20th, Quox suggested treating the 19th as the real deadline. With no mailbox connected, it said plainly that it could not tell whether the sheet was sent. It only read; nothing changed.

quox commitments list shows each open commitment with its ID. --with "Priya Shah" narrows it to one contact.

commitment
quox commitments show cmt_0mwdn1gu9b4622f2a3f396e598e07Commitment────────────────────commitment_id             cmt_0mwdn1gu9b4622f2a3f396e598e07direction                 i_owecounterparty_label        Priya Shahwhat                      Send Priya the servicing plan pricing sheetdue_at                    2026-11-20T00:00:00.000Zdue_basis                 statedstatus                    opencapture_mode              explicit_usersource_kind               chatsource_ref                meeting: Kestrel Cycles servicing review 2026-11-12source_quote              Send Priya the servicing plan pricing sheetquote_verified            0created_by_kind           humanconfirmed_at              2026-11-12T14:23:24.801Zclosed_at                 -created_at                2026-11-12T14:23:24.801Zupdated_at                2026-11-12T14:23:24.801ZSaid: "Send Priya the servicing plan pricing sheet"Source: chat meeting: Kestrel Cycles servicing review 2026-11-12
From a real run in our proof org, on a sample commitment. Trimmed: the org, user, link, hash and redaction rows are cut.

created_by_kind and capture_mode say who recorded the promise: here a person, entering it directly. due_basis says where the date came from, and quote_verified is 0 when nobody has checked the quote against the original words. Add --history to see each change the commitment has been through.

Both Quox and the command only read the record. Closing a promise is a separate step: quox commitments done <id> or quox commitments drop <id> --reason "...", and only a person can run them. An agent asks through an approval card instead.

Run quox commitments show <id> --history. Each change is a row with when, who and what. On the sample above there is one row, the create, so nothing has happened to it since it was recorded.