OAS identity
DIDs, documents, local proofs and explicitly trusted authority.
OAS defines identity primitives for the agent ecosystem: identifier parsing, document construction, cryptography, lineage, resolution and attestations. The current Rust workspace has nine packages, all mapped in the catalog.
A DID such as did:oas:example:agent:weather-bot names an entity. It is not a bearer credential and does not grant access. agent:instance is a compound kind; use the actual parser.
Choose the verification level for the action
Use local document/cryptographic checks when that is the required contract. For privileged actions, use the typed authority API with the configured anchor/source and verifier trust policy. Required scope, root, finality, freshness and revocation must be evaluated for the operation.
Sigil is the default/reference anchor policy in the current SDK. Other registered backends, such as EAS, are only trusted when your verifier explicitly permits them. A document cannot choose the verifier's trust roots.
Read the OAS SDK, entity kinds, lineage, and anchors.