First instrument · published organization catalog

Reframe-owned Codex Auth Instrument

A host-owned capability for carrying a writer-initiated Codex sign-in through a governed MIDI2 lifecycle and a provider-authorized handoff.

Executable Risk-managed Security review pending

Reframe Codex authentication instrument design projection showing Copilot intent entering a MIDI2 lifecycle boundary, a provider-approved browser handoff, and a MIDI2 Monitor receipt sequence — Principal Reframe instrument illustration. This is the canonical Chapter 89 design projection; a live verification snapshot is not yet established for this executable scenario.

Instrument identity

Capability: codex.auth.instrument
Operation: codex/auth.login.start
Scenario: codex-auth-instrument
Manufacturer: Fountain Coach
MIDI Association identity: Pending assignment; no Manufacturer SysEx ID is invented here
Distribution: Published organization catalog entry; instrument release not established

The instrument journey

Copilot intent
→ Reframe admission
→ MIDI2 discovery / readiness / lifecycle
→ provider-authorized browser or WebKit projection
→ redacted authenticated-state result
→ FountainStore receipt + AX-visible Copilot and Monitor projection

Evidence and risk

Observed boundary

Credentials remain outside the Reframe UI and Store projection. The instrument owns lifecycle semantics; provider authentication owns credential exchange.

Risk decision

Fountain Coach may publish this sanitized contract under explicit risk management while the external security review remains pending.

Not established

Independent security review, full live acceptance, MIDI Association logo permission, and a released named build.

Governing references

MIDI 2.0 Logo Licensing Program · SysEx ID policy · MIDI 2.0 product submission

Read across the publication graph

Instrument Catalog · The Book of Reframe: behavior and evidence · Reframe Governance: doctrine and acceptance