Adoption: move the OVOS specifications out of Draft status #5

Adoption — move the OVOS specifications out of Draft

Tracking issue for the official adoption of the OVOS specifications — the point at which the family of specs stops being Draft and becomes a stable, adopted contract.

Today every spec header reads Status: Draft, and the README carries a notice that the documents may still change. Adoption flips that: each spec's Status field moves from Draft to a stable status, and the draft notice is removed.

This issue MUST NOT be closed until all of the following hold

• Community feedback. The community has been given the opportunity to review and respond, and the feedback has been gathered and addressed (or explicitly dispositioned).
• Core team consensus. Every member of the OVOS core team agrees the specifications are ready to be adopted.
• Implementation conformance. Every existing OVOS repository that these specifications govern has been brought into compliance — see migration epic Epic: migrate OVOS repos onto ovos-spec-tools #7.

Only when all three are satisfied may a maintainer flip each spec's Status to a stable value, remove the draft notice from the README, and close this issue.

Specs in dev (merged, awaiting adoption)

• OVOS-INTENT-1 — Sentence Template Grammar
• OVOS-INTENT-2 — Locale Resource Formats
• OVOS-INTENT-3 — Intent Definition
• OVOS-MSG-1 — Bus Message Specification
• OVOS-SESSION-1 — Session Carrier Wire Shape (PR OVOS-SESSION-1: Session carrier wire shape (draft) #22)
• OVOS-SESSION-2 — Session Lifecycle and State Ownership (PR OVOS-SESSION-2: Session Lifecycle and State Ownership (draft) #27, SESSION-2: add ovos.session.sync and session mutation discipline #36)
• OVOS-PIPELINE-1 — Utterance Lifecycle and Pipeline (PR OVOS-PIPELINE-1 — utterance lifecycle and pipeline (draft) #11)
• OVOS-INTENT-4 — Intent and Entity Registration Bus Contract (PR OVOS-INTENT-4 — intent and entity registration bus contract #9)
• OVOS-CONTEXT-1 — Intent Context (PR OVOS-CONTEXT-1: Intent Context Specification #18)
• OVOS-TRANSFORM-1 — Transformer Plugins (PR OVOS-TRANSFORM-1: Transformer Plugins Specification #20)
• OVOS-STOP-1 — Stop Pipeline Plugin (PR OVOS-STOP-1 v1 — stop pipeline plugin specification #33)

Specs still under proposal (open PRs)

• OVOS-INTENT-2 v3 — .prompt resource role (PR INTENT-2: the .prompt resource role #4, issue Add a .prompt resource role for language-model prompts (OVOS-INTENT-2 V3) #6)
• OVOS-CONVERSE-1 — Active Handlers and Interactive Response (PR CONVERSE-1: active handlers and interactive response specification #25)
• OVOS-PERSONA-1 — Persona Pipeline Plugin (PR PERSONA-1: persona pipeline plugin specification #37)
• OVOS-AUDIO-1 — Audio Output Service (PR AUDIO-1: audio output service specification #38)
• OVOS-FALLBACK-1 — Fallback Pipeline Plugin (PR FALLBACK-1: fallback pipeline plugin specification #39)
• OVOS-COMMON-QUERY-1 — Common Query Pipeline Plugin (PR COMMON-QUERY-1: common query pipeline plugin specification #40)
• OVOS-BRIDGE-1 — Bus Bridge and Opaque Relay (PR BRIDGE-1: bus bridge and opaque relay specification #43)
• OVOS-INTENT-4 §11 — Session-scoped Intent Registration (PR INTENT-4: session-scoped registration + required_slots #45)
• OVOS-AUDIO-IN-1 — Audio Input Service (PR OVOS-AUDIO-IN-1: Audio Input Service Specification #51)
• OVOS-USER-ID-1 — User Identity Resolution (PR spec: [proposal] USER-ID-1 — participant identity resolution specification #54, issue USER-ID-1: user identity resolution and authentication level specification #53)

Specs under proposal are not in the adoption set until merged; they leave Draft on their own timeline once per-spec adoption criteria are met.

After adoption

Adoption does not freeze the specifications. Changes continue through the normal process — a pull request that bumps the affected spec's Version and adds a CHANGELOG entry. Versioning follows semantic versioning in spirit: breaking changes are identified as such.