Quick
6 of 16 capabilities
Capabilities that compose over nothing, so no dependency expansion is needed.
An assessment is the way into the platform. It reads the governance capabilities you already run, reports findings and limitations, and shows where every fact came from. It produces no score and no compliance verdict.
VerifAIer is deep infrastructure, and an assessment is how that depth arrives as one reading. It orchestrates the governance capabilities registered in your deployment, reads what they have already produced, by reference, never copied, and returns a single result. An executive summary and an engineer’s trace are two projections of that one result, which is why they cannot disagree.
A mode selects scope. It never changes what a capability reports, and a mode name is not a verdict.
6 of 16 capabilities
Capabilities that compose over nothing, so no dependency expansion is needed.
13 of 16 capabilities
The default organization assessment, with declared dependencies expanded.
16 of 16 capabilities
The complete registered surface, including capabilities that cannot execute.
13 of 16 capabilities
One explicit repeated-intent assessment using the Standard selection.
Nothing about your environment is guessed, and no capability is included because it sounds relevant.
For every registered capability, discovery asks only what it can observe: does your context carry what this capability answers for, and does the capability’s own readiness check answer? Anything beyond that would be an opinion about a capability the assessment does not own.
Before anything executes, preflight reports what the request would cover: the mode, its selection, and any context a capability still needs. It calls no capability and produces no evidence.
A capability that cannot answer in your environment becomes a named limitation. It does not quietly drop out of the scope, and it does not fail the assessment. Everything else still runs.
Read straight from the capability registry and the mode selection policy in the running product. Nothing here is a picture of the product; it is the product’s own answer.
6 of 16 capabilities
13 of 16 capabilities
16 of 16 capabilities
13 of 16 capabilities
Solid: in scope for this mode.Dashed: deliberately out of scope, and named as a limitation in the result rather than hidden.
A COMPLETE result means every capability the mode selected succeeded. Quick selects six of sixteen, so its result always names the capabilities it did not cover.
If one capability fails, the rest still run. A partial assessment is a working assessment reporting honestly, not a system failure.
What could not be assessed is reported alongside what was: capabilities without a listing surface, unresolved dependencies, and scope the mode excluded.
The Continuous mode records repeated intent and performs one explicit assessment. It does not schedule anything and does not activate background monitoring.
VerifAIer is local-first: the product runs inside your own environment, so an assessment runs there too, not on this website.
/app/assessment, choose a mode, review the preflight, and run it.A result is not a dead end. Findings carry provenance references back to the capability that produced them, so the next step happens in the capability that owns the fact, not in a report about it.
The deterministic record every capability derives from: envelope, receipt and provenance, verifiable offline.
ExploreEvidence coverage mapped to EU AI Act, NIST AI RMF and ISO/IEC 42001 control packs.
ExploreOne agent-scope trust posture composing compliance, risk and quality.
ExploreDeploy VerifAIer and run your first assessment, or talk to us about enterprise rollout.