Get started
Security & GovernanceEvidenceApprovalsJourneys

Quox turned on an email alert only after a person said yes

Asked to switch on email alerts, Quox held the change until a person approved it. The proof engine read the setting before and after the yes, on two separate days. The Evidence Explorer now lists 220 verified cases.

Adam Cowles15 November 20263 min read
A glowing blue envelope paused before a translucent violet gate with a seal on it, and beyond the gate an unlit ring waiting to switch on, over near-black

Today a new journey went live: Turn on email alerts, with a person's yes.

Someone asks Quox to switch on email notifications. Changing a setting needs approval, so Quox does not just do it. It holds the change, says it is waiting, and only makes the change after a person says yes.

The proof engine ran this twice, on 14 and 15 November, and it passed both times. That makes it verified on the Evidence Explorer.

What happened in the run

The run used a test org. Email alerts for the person asking were switched off first, so the change had a known starting point. The address was a reserved example address that cannot receive mail.

  1. Quox took the request. It prepared the change to switch on the email channel.
  2. The change was held. Quox raised an approval card and told the person it was waiting, and how to approve it.
  3. Nothing changed yet. While the card was open, the proof engine read the channel list. Email was still off.
  4. A person approved. The proof engine never approves anything itself. It waited for a human.
  5. The change ran. After the yes, the proof engine read the channel list again. Email was on, and every other channel was as it was before.

The before and after come from reads of the stored setting, not from Quox's answer. Quox's answer was honest about that too: it said the change ran, and said plainly that it had not read the channel list back itself.

220 verified cases on the Explorer

Yesterday the Evidence Explorer listed 176 proof cases, 175 of them verified. It now lists 221 proof cases, and 220 of them are verified. The one that is not yet verified has passed on one day and needs a second.

The rule has not changed. A case is listed as verified only when its newest run on the current checks passed, and it has passing runs on two or more separate UTC days.

Eighteen of the new cases were already proven and simply missing. The Explorer looked each case up by the name of the file it was defined in. Some files hold cases for a different area, so those cases were never found. We fixed the lookup today, and those 18 now show, each with its own runs.

The email journey was one of the cases this affected: it now lists both of its passing runs, not just the newest.

Four new guides

Four CLI guides went live today. Each shows how to ask Quox, then how to do it yourself, and each carries the receipt of the run it was proven on.

What this does not prove

  • This is Quox checking itself. Every item on the Explorer says so: checked by Quox's own proof engine, not an independent audit.
  • The journey ran in a test org. The address could not receive mail, so the run shows the setting changed, not that an email arrived.
  • A pass shows the checks held on those runs. It does not promise every future run will pass. If a newer run fails, the case comes off the verified list.

You can check the journey's evidence yourself. Its page links a signed evidence bundle and the small verifier that checks it, and you can see every published journey on the journeys page.