Commit to a signed plan, then check what you did against it
Did we stick to the plan?
Write the plan down as a signed record before you start. Afterwards, Quox can tell you exactly where you went off it.
What you get: a plan saved as a signed, tamper-evident record, a check that its signature is valid, and a step-by-step comparison of what you did against what you planned.
Ask Quox
Section titled “Ask Quox”Before we start the office move, commit to a signed plan called 'Office move c6417f' with three steps: s1 book the van, s2 pack the IT kit, s3 update our address with the bank. It does not need approval and changes are fine. Then fetch that plan back and tell me whether its signature is valid. Finally: we did s1 and s3 but skipped s2. Did we deviate from the plan?
▤ AOCL │ L1 identity complete · allowed · 1ms
▤ AOCL │ L3 policy gate complete · proceed · 8ms
◐ PLAN │ artifact create ✔ PLAN │ artifact create │ approval filed: false · 1.6s
⛓ AEE │ envelope opened · ops.tool · plan_artifact_create ok
◐ PLAN │ artifact get ✔ PLAN │ artifact get │ ok · 1.3s
◐ PLAN │ artifact diff ✔ PLAN │ artifact diff │ 0 matched, 3 missing, 0 extra · 3.3s
⛓ AEE │ envelope opened · ops.tool · plan_artifact_get ok
⛓ AEE │ envelope opened · ops.tool · plan_artifact_diff ok
◐ PLAN │ artifact diff ✔ PLAN │ artifact diff │ 2 matched, 1 missing, 0 extra · 1.6s
⛓ AEE │ envelope opened · ops.tool · plan_artifact_diff ok
⛓ AEE │ envelope opened · stream_success
The plan is signed and verified, and skipping s2 counts as a deviation. Because you said changes are fine, it doesn't need re-approval. Plan. "Office move c6417f" is saved as artifact ART_MW7QAFDZ_AF220022D148 with three steps: • s1: book the van • s2: pack the IT kit • s3: update our address with the bank I set it to need no approval and to allow free deviation, as you asked. Signature. It is valid. When I fetched the plan back, I re-checked it. The ed25519 signature is correct, the signing key is pinned and trust-anchored, and the schema is fine. Deviation. Yes. s1 and s3 matched the plan, s2 (pack the IT kit) is missing, and there are no extra or changed steps. The tool reports deviated: true , reapproval_required: false and reapproval_filed: false . My first diff attempt passed the steps as plain text and marked all three as missing. I reran it with the step ids, and the result above is from that rerun. Since s2 was skipped, the IT kit is still unpacked. Do you want me to add a reminder for it?
38.9s · 4 tools · 0 approvals
quox.✔ Machine verified against the CLI on 8 Nov 2026 · test report mw7q9v
Quox saved the three steps as a signed plan, fetched it back and checked the signature (valid, with a pinned and trust-anchored key), then compared what you did with the plan: s1 and s3 matched, s2 was missing, so you deviated. Because you said changes were fine, no re-approval was needed. It also said its first comparison used the wrong input and that the answer comes from the rerun. Quox did not book, pack or update anything: it only recorded the plan and compared.
Do it yourself
Section titled “Do it yourself”There is no quox plan verb for signed plans yet. The closest read-only command runs the same read tool Quox used, by the plan’s id:
quox tool exec plan_artifact_get --args '{"artifact_id":"ART_MW7QAFDZ_AF220022D148"}' --reason "read back a signed plan" --select 'artifact.body.title,artifact.body.steps[*].description,artifact.signature.sig_type,verify.valid,verify.keySource,verify.trustAnchored'{"artifact.body.title": "Office move c6417f","artifact.body.steps[*].description": [ "s1 book the van", "s2 pack the IT kit", "s3 update our address with the bank"],"artifact.signature.sig_type": "ed25519","verify.valid": true,"verify.keySource": "pinned","verify.trustAnchored": true} The verify fields are the signature check made on this read. The comparison against what you did is a chat step.
What just happened
Section titled “What just happened”The plan became a signed record the moment Quox saved it. Reading it back and comparing against it change nothing, so you can check the same plan as often as you like.