The May 2026 bridge package makes OSAI’s canonical reference identity posture concrete without turning the framework into a product, registry, authorization system, certification program, or runtime-control layer. The Namespace and Vocabulary Posture Note was issued June 6, 2026, and the Layer 2 White Paper was publicly issued June 8, 2026.
The Technical Concept Note should be read with its companion technical artifacts. The sequence below moves from concept, to identifier grammar, to schema, to lookup posture, to narrow demonstration, and then to differentiation. The Namespace and Vocabulary Posture Note follows as a separate boundary/posture note for the issued Layer 2 White Paper.
For the package-level index and citation guidance, see OSAI-FW-REL-01.
Defines the bridge concept for canonical reference identity and explains why the companion artifacts are required.
Locks the OSAI ID structure and prevents authority, attestation, policy, or runtime state from being embedded into the identifier.
Defines the Canonical Identity Record, Authority Binding Record, and Attestation Record as linked but distinct structures.
Shows a lookup-only posture for returning linked records without implying authentication, authorization, or enforcement.
Shows one worked example: the same OSAI identity reference remains stable while authority bindings vary.
Clarifies what OSAI does not claim and distinguishes it from downstream auth, protocol, certification, and runtime-control systems.
The Namespace and Vocabulary Posture Note clarifies how OSAI identifiers, issuer context, controlled vocabulary, collision handling, and registry non-operation should be interpreted across the Layer 2 document family.
The package demonstrates that a software or AI agent can be named and referenced consistently while downstream authority relationships and attestation records remain separate, bounded, and independently reviewable.
The Layer 2 White Paper was publicly issued on June 8, 2026. The issued bridge package and the Namespace and Vocabulary Posture Note remain companion materials that support interpretation without retroactively altering the white paper’s scope, non-scope, interpretive boundaries, or non-operational posture.