The Apeiris fabric, analyzed.
A live, evidence-grounded view of the fabric — pick an analysis.
Decision tools
AI Assurance Advisor →
Tell it what you actually operate and how far along you are; get your maturity, framework coverage, the candidate controls worth examining with owners and evidence, and a four-week plan.
Evidence Proof Map →
Pick a framework obligation and see the controls that address it, the exact evidence each needs, the verdict, and the partial-coverage gap. Mapped is not satisfied.
The fabric
Federation graph →
How the 12 domains compose into one authorization verdict.
Dependency & blast-radius →
Which domains carry the most downstream weight.
For adopters
Framework combination →
Which frameworks to combine, and which are redundant.
Regulatory posture →
How mandatory each area is — binding law vs voluntary — by jurisdiction.
Implementation planner →
The fewest control-groups to cover a framework you must satisfy.
Coverage heat map →
Which sources most strongly ground each domain.
Source value & strengths →
Which sources carry the most weight and what each is strongest at.
Threat landscape & coverage →
Which controls address which threats, and where coverage is thin.
Corpus health (Apeiris roadmap)
Depth guide & research priorities →
Where the corpus is deep, and where Apeiris will source more deeply next.
Risk-weighted coverage →
Whether depth tracks capability risk.
Where control strength is thin →
Read across the whole corpus: the ranked, computed opportunities where AI-assurance controls most need depth.
Attestation-dependency graph
Twelve domains, drawn in attestation order. Each arrow points from a domain whose attestation is consumed to the domain that consumes it. The federation composes left to right, and every path resolves into the compliance dossier.
Attestation groups
Reading the graph
The intended federation comprises 24 attestation dependencies across the 12 domains. Compliance sits last by design — the AU-08 dossier packages evidence from every other domain into a single audit-ready record. This is the model Apeiris defines; the platform layer evaluates action context against it at runtime.
Dependency & blast radius
The federation is now backed by real cross-domain edges — each domain's attestation feeds the domains that consume it. Apeiris reads those edges to show which domains carry the most downstream weight: change one, and its blast radius is the set of domains that must re-attest. This view names the keystones and the individual controls that carry the most of that weight — an operational map, framed as insight into where the fabric is most load-bearing.
Keystone domains · widest blast radius first
Loading dependency map…
Load-bearing controls
The individual attestations whose cross-domain feeds carry downstream weight — each shown with the domains its evidence flows into. These are the controls the federation leans on most.
Method: blast radius counts the transitive downstream domains that re-attest when a domain changes; load-bearing controls are those whose cross-domain feeds drive downstream attestations, read from the federation graph and control matrices. Apeiris defines these edges; the platform layer evaluates action context against them at runtime.