Specification · Conformance

Conformance
Levels

Three progressive layers of identity maturity, like geological strata — deeper foundations support stronger guarantees. Adopt incrementally: basic identity first, accountability next, anchored attestation when it matters.

Document
OAS Specification
Clause
§ 11
Levels
3 · strict supersets
Verification
Offline
§ 01
Progression

Each level adds.
None repeat.

Levels are strict supersets: an entity at L2 satisfies every L1 and L0 requirement. Read each column as the delta it introduces.

Normative definitions follow in §02.

Fig. 01Conformance progression, L0 → L2
L0

Basic Identity

Minimum viable identity

Globally unique identity
Cryptographic document integrity
Basic entity metadata
L1⊇ L0

Accountable Identity

Cryptographic human accountability

Lineage terminating at a human-root keyholder
Transitive trust and distrust
Independent lineage verification
L2⊇ L1

Full Identity

Anchored and independently attested

Tamper-evident identity anchoring
Independent third-party verification
Full audit trail
§ 02
Normative requirements

What each level
demands.

Every requirement below is testable offline against public keys and the identity document alone. Conformance test vectors with known-good cryptographic material ship with the SDKs.

L0

Basic Identity

Minimum viable identity

The foundation layer. A valid OAS Identity Document with at least one Ed25519 verification method, signed by a key the document lists. Globally unique and integrity-checked — but self-contained, with no proof of origin.

Globally unique identity
Cryptographic document integrity
Basic entity metadata
Human accountability
Lineage verification
Attestation anchoring

Requirements — 4

L0.1Valid OAS Identity DocumentThe document conforms to the OAS schema, including a valid did:oas URI.
L0.2Ed25519 verification methodAt least one Ed25519 verification method is present in the document.
L0.3Valid entity kindThe kind field is one of the 12 kinds in the entity taxonomy.
L0.4Self-signed documentThe document is signed by a key listed in the document itself.
L1⊇ L0

Accountable Identity

Cryptographic human accountability

Builds on L0 with a complete lineage section: a chain of AgentLineageProof2025 proofs from the entity back to an active human root. Every link is verified through typed authorizing APIs against resolved documents and verifier trust policy.

Everything in L0
Lineage terminating at a human-root keyholder
Transitive trust and distrust
Independent lineage verification

Requirements — 5

L1.1All L0 requirementsL1 is a strict superset of L0.
L1.2Valid humanRootDidThe lineage section points to an active HMR or MHR root entity.
L1.3Derivation proof at every linkA valid AgentLineageProof2025 binds each child key to its parent via HKDF-SHA256.
L1.4Complete humanRootChainThe chain from entity to human root is complete, with no missing links.
L1.5Independent verifiabilityEvery lineage proof in the chain verifies independently, offline.
L2⊇ L1

Full Identity

Anchored and independently attested

The highest level. The identity document hash is anchored on an immutable, publicly auditable ledger, and at least one independent third party has issued a W3C Verifiable Credential about the entity — anchored the same way.

Everything in L1
Tamper-evident identity anchoring
Independent third-party verification
Full audit trail

Requirements — 4

L2.1All L1 requirementsL2 is a strict superset of L1.
L2.2Ledger-anchored document hashThe identity document hash is anchored on at least one immutable, publicly auditable ledger.
L2.3Third-party attestationAt least one W3C Verifiable Credential issued by a party outside the entity's own lineage tree.
L2.4Anchored attestationThe attestation is anchored on the same or a compatible immutable ledger.
§ 03
At a glance

What each level
guarantees.

PropertyL0L1L2
OAS Identity DocumentRequiredRequiredRequired
Ed25519 verification methodRequiredRequiredRequired
Lineage chain (AgentLineageProof2025)—RequiredRequired
Ledger-anchored document hash——Required
Third-party attestation (W3C VC)——Required
Human accountability—YesYes
Offline verificationYesYesYes

1·Levels are strict supersets: an L2 entity satisfies every L1 and L0 requirement. Conformance test vectors with known-good cryptographic material ship with the SDKs.