Skip to content

TriOS macOS: Internet calls between TriOS users through the TRI-NET call stack #2053

Open

Description

@dmitrii-f-t27

Owner decision 2026-10-21: Internet calls between TriOS users on Mac and phone (no PSTN). The TriOS macOS app (apps/trios-macos) has no calling code, no user accounts and no LiveKit; its Mesh tab peers are numeric node IDs on clade-meshd (UDP to manually added peers, no NAT traversal).

The only working call stack is TRI-NET (gHashTag/tri-net #90, LAN-verified only): signed P-256 device identity, exact nickname directory, services/call-api signalling with first-answer-wins, LiveKit media, and shared Swift (phone/shared/CallIdentity.swift, InternetCall.swift, NicknameDirectory.swift) that the iOS app and the macOS TriNetMonitor compile directly. A second stack must not be written.

Goal

TriOS on macOS joins the TRI-NET account system as its own device, links explicitly to the user's account, resolves people by exact nickname over the Internet route only, and places and receives one-to-one audio calls through the existing call API and LiveKit, built through a real link/embed seam.

Done when

  1. Spec apps/trios-macos/.trinity/specs/internet-calls.md lands first.
  2. The app build (clade-build, rings/RUST-01) compiles the TRI-NET shared calling files from a checkout pinned in apps/trios-macos/TRINET_PIN, links a SwiftPM-built LiveKit (apps/trios-macos/packages/TriOSLiveKit, LiveKit 2.15.2 as pinned by TRI-NET) and embeds its frameworks in trios.app; a CI job builds this on a macOS runner.
  3. A Calls segment in the Mesh tab: account binding (claim a nickname or join an existing account with a link code from the phone), exact-nickname contact lookup, call button on a resolved contact only, incoming call with caller nickname and Answer/Decline, Calling/Ringing/Connecting/Connected/Reconnecting/Ended/Failed states, mute and hang up, error and retry. Mesh node IDs never imply an account and never get a call button.
  4. TriOS has its own TRI-NET device identity (TRINET_IDENTITY_KEYCHAIN_SERVICE, shared: per-app device identity Keychain service for apps that embed the calling code tri-net#415) and microphone usage text in Info.plist.
  5. Pure policy in rings/SR-00 with XCTests in Trios Swift CI.

Live acceptance (not claimed by this issue's PR alone): Mac -> phone and phone -> Mac on two networks with audible two-way audio, accept/decline/cancel/end convergence, reconnect, TURN with UDP blocked. Needs a public HTTPS call API, public LiveKit and TURN (none exist today).

Dmitrii Fedorov (@dmitrii-f-t27)

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions