OneSay Platform
Realtime Playground
Private local M1 candidate. Hosting and external acceptance remain open.
Status: PARTIAL / LOCAL METADATA-ONLY CANONICAL PROJECTION
The interactive Playground projects the exact onesay.realtime.v1 flow:
signal.open → signal.opened → OSAF frame → audio.ack → artifact.delta → signal.end → signal.ended → artifact.finalized → task.completed.
Client messages, server events, the 32-byte OSAF header and audio profile metadata come from generated canonical registries. The projection explains contiguous ACK/release semantics without opening a WebSocket, generating PCM, requesting microphone permission or persisting audio. MCP is never an audio transport. Required CI must execute the control and verify all nine steps in Gecko and WebKit before browser proof is accepted.
RTC#
This route is the Task protocol playground; it opens no RTC session. The RTC
playground is the installed browser example in Examples: run
node tools/rtc/run-public-example.mjs from the repository, open the printed
loopback page and drive connect, publication, subscription, data, RPC and
Agent operations with an existing short-lived credential. It uses only the
installed OneSay SDK and needs no native SDK configuration. A static,
credential-free page cannot exercise RTC authority, so the Portal does not
simulate one (decision of 2026-10-20, recorded in the GX10 developer handoff).
Source and provenance
View original Markdown
# Realtime Playground Status: `PARTIAL / LOCAL METADATA-ONLY CANONICAL PROJECTION` The interactive Playground projects the exact `onesay.realtime.v1` flow: `signal.open → signal.opened → OSAF frame → audio.ack → artifact.delta → signal.end → signal.ended → artifact.finalized → task.completed`. Client messages, server events, the 32-byte OSAF header and audio profile metadata come from generated canonical registries. The projection explains contiguous ACK/release semantics without opening a WebSocket, generating PCM, requesting microphone permission or persisting audio. MCP is never an audio transport. Required CI must execute the control and verify all nine steps in Gecko and WebKit before browser proof is accepted. ## RTC This route is the Task protocol playground; it opens no RTC session. The RTC playground is the installed browser example in [Examples](EXAMPLES.md): run `node tools/rtc/run-public-example.mjs` from the repository, open the printed loopback page and drive connect, publication, subscription, data, RPC and Agent operations with an existing short-lived credential. It uses only the installed OneSay SDK and needs no native SDK configuration. A static, credential-free page cannot exercise RTC authority, so the Portal does not simulate one (decision of 2026-10-20, recorded in the GX10 developer handoff).