One architecture, read four ways.
Solutions is how this site is organised, not a separate product. The platform underneath is the same one in every case. What changes is who is asking, and what they have to answer for.
Four readers, one platform.
Each of these pages was written for somebody with a different thing to answer for. They are not four editions of the product and they are not four tiers. They are four routes into the same architecture.
- Enterprise
- An estate of AI systems, and three people asking the same question in three vocabularies: an executive, an auditor and the engineer who has to answer both.
- Government
- A perimeter that the evidence may not leave, and an assessor who has to be able to check it without contacting the vendor.
- Developers and AI builders
- A coding agent that acts on a repository, and the need to show afterwards what it was allowed to do and what it actually did.
- Individuals
- One person's own assistants, and a record of the interaction that belongs to them rather than to a provider.
The same platform, in every one of them.
One evidence layer, seven products written against it, and the same guarantees in all four routes above. An audience page selects what to explain first; it does not select what is installed.
If two of these audiences produced different records for the same operation, reconciling them would be somebody's job forever. They produce one record, because there is one place records are written.
Evidence EngineFlight RecorderMemory ReceiptsAgent PassportTrust IntelligenceSentinel RuntimeVerifAIer Me
Local-first, in every route
The platform runs inside the environment being governed. That is the same sentence for an enterprise estate, a sovereign perimeter, an editor and one person's laptop.
One evidence format
Every surface reads the same attested records, and those records can be checked without the product that wrote them.
The same refusals
No composite score, no stored trend and no invented ranking, in all four routes. An audience never unlocks a claim the architecture will not make.
Adopt them in any order. Nothing above is a prerequisite for anything else, and the products page is where each one states its own maturity beside its own name.
Solutions is a category, not a thing you buy.
No product carries this name. Nothing here is sold separately, versioned separately or installed separately, and no maturity chip belongs to this page. The chips live on the capability pages, beside the capability.
The seven products are named once above, each as a link. Everything that describes what one of them does lives on its own page, so there is only ever one account of it to keep true.
There is no healthcare edition and no financial-services edition. The four rows are audiences with different accountabilities, not markets with different software.
Adopting an audience does not select a set of capabilities. Every audience reaches the same platform; what differs is which of its properties the reader came for.
Pick the reader you are, or skip the question entirely.
The four pages above are written to be read. The assessment is written to be run, and it answers the same question with output instead of prose, including the parts it cannot answer.