Declare a conformance level. In writing.
AIP and ATP require implementations to declare which conformance level they meet; ABGS grades governance files Essential / Standard / Hardened. This page walks the actual ladder from each spec’s conformance section — every requirement cites its clause — and produces an attestation JSON you can publish in your repository. It is a self-certification: a precise, reviewable claim, not a badge.
Implementations MUST declare which level they conform to. The challenge-response transcript rules (L2) are byte-pinned by the aip-conformance suite; the rest is self-attested against the spec text.
Level 1: Local Identity
Identity created and managed locally (SDK, CLI). No server required.
Level 2: Managed Identity
Identity managed by an identity provider; adds verification, trust scoring, centralized audit.
Level 3: Federated Identity
Identity verifiable across organizations; DIDs, verifiable credentials, cross-platform trust.
Name the implementation, then check every requirement your implementation actually meets — levels are cumulative, so the attested level is the highest unbroken rung.
Nobody checks a self-certification — that is what makes it honest to publish and worthless to inflate. Where a conformance suite covers a requirement (AIP §5.1 transcripts, ATP trust proofs and tree heads, ATX credentials), run the suite: its byte-pinned fixtures and CI-cosigned manifests outrank any checkbox. The checker verifies individual payloads against the same rules.