Visible on the public site now and safe to cite as current truth.
A public roadmap that separates current truth from work still underway.
This page is not a delivery guarantee. It exists so buyers can distinguish shipped public surfaces from programmes in progress, planned transparency work, and areas we are still researching.
What the status labels mean
Only shipped items should be treated as current public capability or current public trust artefact.
Publicly stated as underway, but not safe to present as complete.
A direction we are comfortable stating publicly today, without treating it as delivered.
Under evaluation only. Do not sell it as a public commitment or current feature.
Shipped
Current public trust artefacts and status surfaces.
Product status and read-only assurance
The public site already distinguishes MRI as the public starting point, Core as controlled rollout, and Enhanced and AISF as private beta.
Read-only guarantee language
The public trust surface already states that assessment-led engagements are read-only and that governed write paths require named human approval.
Connector maturity disclosure
The public integrations surface already separates connector maturity instead of implying blanket compatibility.
Evidence and attestation surfaces
The public site already includes an evidence register, an evidence explainer, and an attestation register that stay inside the current published boundary.
In progress
Publicly stated programmes that are underway but not complete.
SOC 2 Type II programme
Publicly stated as in progress. It is not presented as completed certification.
ISO/IEC 27001 ISMS
Publicly stated as underway on the trust surface. It is not presented as certified today.
Cyber Essentials Plus
Publicly stated as underway following Cyber Essentials certification. It is not presented as complete.
Planned
Public transparency work we are comfortable stating as direction, not delivery.
Dated public updates when statuses change
This roadmap is intended to move when a public status genuinely changes, not on a marketing cadence.
More attestation detail when there is something real to disclose
We plan to expand public detail only when a milestone can be evidenced on the site, not while it is still speculative.
Stronger linking between trust surfaces
The direction is a clearer chain between trust, about, roadmap, and evidence surfaces so buyers can verify claims with fewer jumps.
Researching
Areas under evaluation that should not be treated as commitments.
Broader runtime-backed public trust surfaces
We are still evaluating how much deployment-level trust data can be exposed publicly without overstating what every deployment supports.
Additional public evidence routes for case studies
We are still assessing how much more evidence framing can be shown publicly without breaching customer confidentiality.
Future disclosure pattern for later-stage capabilities
We are still refining how to talk about later-stage capabilities before they move beyond controlled rollout or private beta.
If it is not marked shipped here, do not treat it as current public truth.
That is the operating rule behind this page. It exists to make the public boundary easier to inspect, not to widen it.