feat: VoiceFrame SSE wire format — shared type definition for cf-voice consumers #40
Labels
No labels
architecture
backlog
enhancement
module:documents
module:hardware
module:manage
module:pipeline
module:voice
priority:backlog
priority:high
priority:medium
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: Circuit-Forge/circuitforge-core#40
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Context
Linnet consumes
VoiceFramefromcf-voiceand re-emitsToneEventover SSE to the frontend. Osprey will consumeVoiceFramefor its own telephony annotation path.The SSE wire format (JSON serialisation of
ToneEvent) should be documented as part of cf-voice so Osprey and future consumers know what to expect from a Linnet-compatible annotation stream.Deliverable
ToneEventJSON shape incf-voiceREADME alongsideVoiceFramelabel,confidence,speaker_id,shift_magnitude,timestamp,session_idRationale
When
<LinnetWidget />is embedded in Osprey or Falcon, the host app subscribes totone-eventemissions. Locking the wire format early prevents a breaking change when the widget ships in v1.0.Related
Circuit-Forge/circuitforge-core#39(cf-voice stub repo)Circuit-Forge/linnet#14(LinnetWidget isolation)