Circuit-Forge/harrier
3
0
Fork 0
Code Issues 4 Pull requests Projects Releases Packages Wiki Activity Actions

Voice accessibility: wire falcon phone workflows through linnet #4

New issue
Open
opened 2026-04-06 10:48:37 -07:00 by pyr0ball · 0 comments
pyr0ball commented 2026-04-06 10:48:37 -07:00
Owner
Copy link

Dependency note: linnet voice accessibility layer

When falcon reaches active development, consider wiring its phone-based workflows through linnet (Circuit-Forge/linnet) rather than building a standalone voice layer.

linnet is being designed as shared voice accessibility infrastructure:

  • Notation: real-time tone annotation (Elcor-style) — makes implicit affect explicit for ND/autistic users
  • Navigation: IVR proxy — user types intent, linnet navigates and speaks (nonverbal access)
  • Interaction: full bidirectional voice proxy — user types in their language, linnet speaks; caller speaks, linnet transcribes + annotates
  • Translation: DeepL + LLM layer — real-time translation with contextual flagging of legal/bureaucratic subtext that doesn't survive literal translation; mobile-first PWA

For government forms and benefits, the translation milestone is especially relevant — non-English speakers navigating government forms and benefits phone systems in a second language are a core CF audience.

Why linnet, not inline

These capabilities share an engine (cf_voice.context, cf_voice.telephony, cf_voice.io in circuitforge-core#34). Building them inline per-product creates drift and maintenance burden. linnet owns the voice proxy surface; products call its API.

References

## Dependency note: linnet voice accessibility layer When falcon reaches active development, consider wiring its phone-based workflows through **linnet** (`Circuit-Forge/linnet`) rather than building a standalone voice layer. linnet is being designed as shared voice accessibility infrastructure: - **Notation**: real-time tone annotation (Elcor-style) — makes implicit affect explicit for ND/autistic users - **Navigation**: IVR proxy — user types intent, linnet navigates and speaks (nonverbal access) - **Interaction**: full bidirectional voice proxy — user types in their language, linnet speaks; caller speaks, linnet transcribes + annotates - **Translation**: DeepL + LLM layer — real-time translation with contextual flagging of legal/bureaucratic subtext that doesn't survive literal translation; mobile-first PWA For government forms and benefits, the translation milestone is especially relevant — non-English speakers navigating government forms and benefits phone systems in a second language are a core CF audience. ## Why linnet, not inline These capabilities share an engine (`cf_voice.context`, `cf_voice.telephony`, `cf_voice.io` in circuitforge-core#34). Building them inline per-product creates drift and maintenance burden. linnet owns the voice proxy surface; products call its API. ## References - Circuit-Forge/linnet (placeholder) - Circuit-Forge/roadmap#31 — linnet tracking issue - Circuit-Forge/circuitforge-core#34 — cf_voice module - cf-orch#20 — voice context service endpoint
Sign in to join this conversation.
No Branch/Tag specified
Branches Tags
main
No results found.
Labels
Clear labels
No items
No labels
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: Circuit-Forge/harrier#4
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?