The evidence so far
A product that lets software send email should have to prove itself before anyone trusts it. This page holds what we can show today, and lists what we can't show yet.
The 90-day clock
Not started. It starts with the first completed read-only pass over our own team mailbox. That connection is built and has not been switched on.
When it runs, this section will show the day, the days with a completed pass, the longest gap, and every policy breach or leak between personas, counted from the ledger.
Agent mail on our own domains Live
- 25 domains with an agent mailbox
- 25 of 25 test deliveries arrived, authenticated
- 0 of 25 Agent Seal signatures survived the provider
- 0 messages answered
An operator sends one labelled test message from each domain to the next and checks that it arrived with SPF, DKIM and DMARC passing. The records behind each mailbox are looked up again every day without sending anything, and a lookup that fails counts as unknown. Measured November 17, 2026.
Release receipts
Every release runs through a gated lane, on staging before production, and leaves a receipt. These are the most recent ones.
Latest service release
November 19, 2026 · commit 9bcc1d0974d1
- ✓ 1,576 automated tests passed
- ✓ Full test suite
- ✓ Security gate tests
- ✓ Bundle leak scan
- ✓ Domain settings match the recorded posture
- ✓ Database migration tests
- ✓ Staging smoke checks, including live attack samples
- ✓ Production health verified
Latest verified website release
November 18, 2026 · commit 70502818c5b8
- ✓ Site build
- ✓ Site leak scan
- ✓ Site tests
- ✓ Visual review receipt
- ✓ Staging, then production, verified page by page
- ✓ Home page Largest Contentful Paint (LCP) 1,052 ms against a 1,800 ms target; other pages 1,152 ms or less. Layout shift 0. Measured on emulated slow 4G.
A receipt is written after a release is verified live, so this is usually the release before the page you are reading.
Daily ledger anchors Running in staging
Every day the ledger of each tenant is sealed: the day's events are combined into one Merkle root, and that anchor points at the previous one (“Linked”). These are the latest anchors of a synthetic test tenant on staging, read November 19, 2026. Its chain verified end to end when it was read.
| Day | Events | Merkle root | Linked |
|---|---|---|---|
| 1 | 1d154930… | ✓ Yes | |
| 1 | 9273fe98… | ✓ Yes | |
| 1 | 5b0782f6… | ✓ Yes | |
| 1 | e2044933… | ✓ Yes | |
| 1 | 95d2cc5e… | ✓ Yes | |
| 1 | d8cae4f8… | ✓ Yes | |
| 1 | 60a04a01… | ✓ Yes |
Synthetic mail only; no real tenant is shown. Download every anchor in this snapshot to check the links yourself: each prev_anchor_hash equals the event_hash of the anchor before it.
What isn't proven yet
- The 90-day clock has not started. Until it does, nothing here has been tested on a person's real mail.
- The Agent Seal does not survive our sending provider. The provider rewrites one header the signature covers. Test messages arrive labelled and authenticated, but their seal can't be verified end to end yet.
- No real model has read real mail. The reader has only been measured against a no-cost synthetic stand-in.
- No outside security test has been done. Our own red-team corpus runs on every release; nobody independent has attacked it.
- Nobody outside our team has used it. Setup time, acceptance and service levels are unmeasured for that reason.
What runs today, capability by capability: status. What must be true before outside teams join: the eight gates. Try to break the real code yourself: the Lab.