Authoritative materials are maintained below in controlled reading order. Status, version, and release posture are shown to support citation, archival reference, and interpretation.
Read this as the conceptual root for the Layer 2 document family before using the companion artifacts for controlled context.
Primary conceptual reference white paper defining identity and naming primitives for artificial intelligence systems as a conceptual, upstream, non-operational, and non-normative reference framework.
Read these first for scope, orientation, and publication-control context.
Concise framing of intent, boundaries, and interpretive posture for the publication series.
Interpretive guidance for the OSAI materials, including scope and non-scope clarification.
Publication-control record, identifiers, supersession status, and revision history for the Layer 2 publication series and companion artifacts.
Public, citable memo positioning OSAI as a non-operational, model-agnostic naming/reference substrate for software and AI agent identity discussions.
These documents make the canonical reference identity posture concrete without asserting production implementation, authorization, certification, or runtime-control capability. Begin with the Technical Concept Note, then use the Release Note as a package index before reading the companion technical artifacts.
Bridge artifact connecting the standards-facing memo to the companion technical artifacts. It should be read with the Grammar, Schema, Resolver Illustration, Narrow Demonstration, Differentiation Note, and Release Note.
Package-level index and reader guidance for the issued May 2026 bridge artifacts. It identifies the release package without adding implementation, governance, certification, or runtime-control claims.
Defines the OSAI ID grammar and the interpretive limits of the canonical identifier.
Defines the Canonical Identity Record, Authority Binding Record, and Attestation Record as linked but distinct structures.
Shows lookup-only resolver posture for surfacing linked records without making downstream control decisions.
Demonstrates one narrow point: stable canonical identity can remain unchanged while authority bindings vary.
Clarifies how OSAI differs from IAM, OAuth/OIDC, workload identity, agent-tool protocols, certification, procurement artifacts, and runtime-control systems.
Read this as a companion posture note for interpreting namespace, vocabulary, issuer scope, collision handling, and registry non-operation across the Layer 2 document family.
Clarifies OSAI’s namespace and vocabulary posture, including issuer-scoped interpretation, controlled vocabulary, collision handling, jurisdictional and sector context, and registry non-operation.