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
Every page is the same width
Each screen used to choose its own width, and a hundred and eighty of them chose differently. Every page now fills the window with the same margins; a form keeps one readable width under its heading rather than stretching across a large monitor.
Every pageThe first numbered release: sign-up, Messages and the phone app, rebuilt
A company, a DPCO firm and an independent DPO each take their own path. A company is created at the review step; a firm or a DPO applies, and is admitted once a person has checked the application. A practitioner is admitted only when the certificate they uploaded has been verified.
Sign-upDirect chats, channels, reply threads and marketplace enquiries in one place, with quotes, reactions, voice notes, read receipts, pinned messages and groups. On a phone it is one column with a fixed reply bar.
MessagesA new design across the app, in light and dark. Sign up on the phone, work through My work, answer an audit as a respondent from the invitation to the submission, and run a practice from the same screens the web has. Links to app.asiri.ng open in the app.
Phone appProgrammes are immutable and their private content versioned; departments own them; NDPA response work attaches to both. A connected systems catalogue, and an enterprise risk register connected to security reviews and treatment.
Programmes · RiskTicking the box at sign-up records your consent, with the wording you saw and when, in the same transaction as the application. It makes nobody a member: that happens when you choose a name.
CommunityA date in a register is read as a day in the zone your workspace keeps, and nothing on screen formats one without naming the zone it is shown in.
RegistersHow 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. A change you have to do something about is never something you learn about from a failure.
Regressions stay in the record
A regression we ship is entered here as a Fix release carrying its warning, and stays once it is fixed. Deleting it 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.