Status & Scope

This page consolidates publication posture, intent, and scope boundaries for readers evaluating what OSAI is — and what it is not.

Release-cycle notice

This site reflects the current public posture as of June 8, 2026. The OSAI Framework Layer 2 White Paper was publicly issued on June 8, 2026, and the Namespace and Vocabulary Posture Note was issued June 6, 2026 as a companion posture note.

Document-family identifiers and revision references are maintained in Document Control & Revision History.

Status & intent

OSAI is issued as a conceptual reference framework and document family. It does not propose a binding technical standard, governance model, or production implementation, nor does it seek formal adoption, endorsement, or control over software or AI systems.

The publication series is intended to support analysis, critique, comparison, and downstream development by providing a neutral, non-operational point of reference for canonical reference identity.

Scope and non-scope boundaries

Scope

Canonical reference identity for software and AI agents; identifier grammar; linked record structures; lookup-only resolver posture; narrow demonstration of stable identity with changing authority; namespace and vocabulary posture; issuer-scoped reference; collision handling; boundary definitions and terminology clarity.

Non-scope

Authentication, authorization, IAM, runtime enforcement, credential issuance, certification, trust scoring, governance execution, security controls, agent orchestration, live central registry operation, or claims of authority over AI systems.

Publication logic

The issued white paper is the conceptual root of the Layer 2 document family. The issued bridge package and Namespace and Vocabulary Posture Note remain supporting companion materials and do not imply implementation maturity beyond the materials actually issued.

Current issued reference materials

White paper plus companion artifacts

The OSAI Framework Layer 2 White Paper was publicly issued on June 8, 2026. The framework remains conceptual, non-operational, and non-normative. It does not define an implementation, registry, IAM system, authorization layer, certification process, governance platform, or runtime control system. The companion artifacts remain supporting materials for controlled context and interpretation.

Read the Layer 2 White Paper Open posture note Open document shelf Read bridge sequence