OAS is the identity layer underneath OpenAgent ID. It defines the did:oas method, the entity model, and the verifier contract consumed by the OpenAgent SDK, AEGIS, Arsenal, L1feID, wallets, and OATS reputation flows.

​
What OAS owns

  • did:oas:<namespace>:<kind>:<identifier> DID syntax.
  • Entity kinds for humans, collectives, organizations, agents, agent instances, tools, skills, workflows, models, datasets, and services.
  • Ed25519 identity material and local signature verification.
  • DID documents, verification methods, service endpoints, and authentication relationships.
  • Lineage proofs that bind child identities to parents.
  • Privileged authority verification through finalized Sigil GAL lineage state.

​
Portable vs privileged verification

A local DID signature proves key possession. It does not by itself authorize privileged OpenAgent access. Privileged actions must fail closed unless the OAS verifier can reconstruct the required anchored lineage path - Sigil is the reference backend, and any LineageAnchor backend can stand in via the verifier’s anchor policy.

​
DID shape

​
Downstream contract

Downstream systems do not define their own lineage semantics. They consume the OAS verifier result and add product-specific policy:
  • OpenAgent SDK creates sessions and contexts from OAS verification.
  • Arsenal issues ACTs only after required authority is valid.
  • AEGIS applies policy to the OAS result.
  • L1feID maps verified DIDs to stable platform records.
  • Registry adapters store service endpoints and resolver metadata for OAS identities.

AEGIS

Learn how OAS results become trust tiers and policy decisions.

Wallets

Learn how DID keys derive Sigil, Solana, and EVM wallet addresses.