Product · Release notes
Everything we shipped, including what we broke.
A register of changes, written the way we ask you to write yours. Breaking changes are named as breaking, regressions stay in the record after they are fixed, and nothing is quietly edited out.
Releases, newest first
Newest first · nothing removed from this record once published
Readers say when they last actually read
A number now carries the moment it was read, not the moment it was written. Nine days of a register describing itself from memory is the failure this closes.
Every registerAn expired API key used to fail silently and leave the last figures on screen. It now opens an action against the integration with the date it stopped.
IntegrationsRead from a system, attested by a person, or evidenced by a document — stated first, because it changes how the number should be read.
Registers · trust pageBadge wording is derived, not typed
You can no longer type what a badge says. Wording is derived from the assurance behind it, which is the whole argument of the product and was never enforceable while the field stayed editable.
Trust pageWhen a claim is refused, the page states which assurance would be required to make it true, rather than only saying no.
Trust pageA report past twelve months from its report date now stops the badge showing as current on the same day, instead of at the next review.
FrameworksBreaking. Four customers had typed labels that no longer resolve — each was contacted individually before release, and the old strings are retained on the audit trail rather than deleted.
Scoped credentials for external reviewers
A reviewer reaches only the registers their engagement covers — five of eighteen, in the reference workspace — and every read inside that scope is logged to your trail rather than only theirs.
EngagementsReported through the disclosure programme. Asiri support sessions now expire automatically and appear on your audit trail under our own name.
Audit trailPreviously optional on non-significant edits. Reasoning reconstructed later is a defence; captured at the time it is evidence.
Audit trailThe regression we shipped in 4.5, and the fix
An off-by-one meant records due for deletion on the last day of a schedule survived until the next run. 41,000 records were affected across nine workspaces, all deleted on correction.
RetentionWhat was deleted, when, and under which rule — kept for the audit return so the run itself is evidence.
RetentionA period you inherit from a regulator is a fact. A period you chose is a decision you will have to defend, and the register now says which is which.
RetentionThis is our regression, disclosed here rather than in a private note. Every affected workspace was told within 24 hours, and the incident is on their audit trail as well as ours.
Eri appears on the trail under its own name
Every action Eri takes carries a name, a reason and a proof, on the same trail as any person. An assistant that acts without leaving a record is not an assistant.
Audit trailSix of eight things Eri did last month were observations rather than changes, and the trail now says so rather than flattening both into activity.
Audit trailIt holds every register needed to generate one. A trust page is a statement a company chooses to make, so the assistant proposes and a person publishes.
Ask EriHow we ship
A register that reads your systems cannot break quietly
If a reader stops working, your register starts describing your company from memory — and looks current while doing it. That failure mode decides how we release.
Readers are versioned separately from the product
A change to how we read Postgres does not ride along with a change to how a page looks. They fail differently and they ship differently.
Ninety days for anything breaking
In writing, to the named administrator, before it reaches production. Four customers were contacted individually before 4.8.
Regressions stay in the record
The 4.6 entry describes a bug we shipped in 4.5. Deleting it once fixed would make this page a marketing document rather than a register.
Security fixes ship first and are named
Including the ones reported to us from outside. The disclosure programme is credited in the entry rather than thanked privately.
Nothing here is edited after publishing
A correction is a new line, dated. The same rule the audit trail applies to your registers applies to our own record of changes.
Breaking changes reach you before they reach production
Ninety days' notice, in writing, to the named administrator on your workspace. If you integrate with the API, subscribe to the release list and you will never learn about a change from a failure.