Topolo Voice

Public overview of Topolo Voice in the Topolo application suite.

publicverified 2026-07-28voiceapplication

What It Is

Topolo Voice is the first-party telephony workspace for incoming calls, completed and missed outcomes, provider incidents, recordings, transcripts, and voicemails.

Architecture

The application uses the shared Topolo shell and Topolo Auth boundary. Its API persists organization-scoped call state before publishing typed notification events through Topolo Notify.

Workspace Management

The shared Topolo workspace control reads and manages app-scoped workspace identity through Topolo Auth: authenticated users can list, create, rename, choose a default, and delete an eligible workspace. Workspace IDs and slugs remain stable and exactly one default is explicit. The selected platform workspace scopes this application's app-owned records; the app retains only domain-specific deletion guards for default or non-empty workspaces.

Runtime Surfaces

The production baseline is live at https://voice.topolo.app; the exact notification workflow source is staging-first and awaiting deployment proof.

API Reference

The API exposes authenticated workspace operations plus incoming, completed, missed, provider-failure, recording, transcript, and voicemail transitions under /api/*.

Auth and Permissions

Signed browser and API requests use Topolo Auth through canonical app id app_topolo_voice and service slug topolo-voice.

Data Ownership

Topolo Auth owns Voice workspace identity and lifecycle. Voice owns the calls, provider incidents, recordings, transcripts, and voicemails scoped to those workspaces in D1. Artifact URLs and telephone identifiers are confidential data and remain behind signed workspace access.

Notifications

Voice publishes seven typed notification contracts for incoming, completed, and missed calls; provider failures; ready recordings and transcripts; and received voicemails. Each event is emitted only after its Voice-owned D1 transition is durable, so an unavailable delivery channel cannot roll back telephony state.

Mobile Experience

The checked-in mobile experience contract is approved in native_capability mode. Its fallback route is /dashboard/workspace, its offline policy is read_through_cache, and it requires organization context.

Published permissions: workspace:read.

  • /dashboard/workspace uses /api/widget with the record.detail template and voice.workspace.summary data source.

The native clients consume this manifest as an explicit rendering contract. A web mode record intentionally opens the product web experience; native_capability publishes the listed native routes and actions. Do not infer unlisted native behavior.

Deployments

The scaffold baseline is live at https://voice.topolo.app.

Failure Modes

  • service registration or app routing drifts from canonical identity app_topolo_voice
  • the workflow migration is missing from the deployed D1 database
  • the API service credential cannot write events to Notify

Debugging

  • use the matching internal handbook for operational details
  • verify the system registry entry before deployment or service-registration changes

Use It

Open Topolo Voice for the human product surface. The system handbook records its current hosts, ownership, Auth scopes, storage, deployment, failure modes, and machine artifact.

Discover the credential-scoped automation surface before making an API call:

topolo services --query topolo-voice --json
topolo actions --service topolo-voice --json
topolo actions capabilities --service topolo-voice --json

Choose an action, inspect it with topolo actions get <action-id> --json, then validate and plan a published example. The Agent Actions reference exposes the same public schemas, effects, examples, verification, and recovery guidance.

Example workflow:

  1. Confirm the active identity and organization with topolo whoami --json.
  2. Discover Topolo Voice and select one published action rather than guessing a route.
  3. Inspect its input/output schemas and published example.
  4. Validate and plan the exact payload; obtain confirmation for a mutation.
  5. Execute and perform every published verification step.

Change Log / Verification

  • Reconciled the 2026-07-28 fleet audit closure against the source-pinned action, route, workspace, package, and test evidence; no unrepresented human-facing capability was found.

  • Verified the native_capability mobile experience contract and its 1 published route(s) against apps/TopoloVoice origin/staging a69c1c45d516 on 2026-07-27.

  • Reconciled this page against apps/TopoloVoice origin/staging d99848dbc310 on 2026-07-24 after reviewing every docs-relevant commit since its previous verification watermark. Dependency-only currency commits were checked by the fleet production-dependency gate and did not change this page's product contract.

  • Completed seven published, durable Voice notification workflows on 2026-07-20 at staging commit 41b1838c001c0cfa975864a1f2be1bf3c11f3bdd; source, migration, action, coverage, and registry gates passed. Live staging deployment proof remains pending.

  • Reconciled workspace verification on 2026-06-28 against apps/TopoloVoice commits through a39c377; reviewed 299 commits since 2026-05-14, including a39c377 chore(deps): roll @topolo-io/* pins to latest (fleet currency self-heal); 8387252 chore(deps): refresh @topolo-io/app-shell pins (package.json + lockfile); f593637 Stop blocking startup on i18n readiness; 2556f36 Adopt canonical Topolo typography.

  • Corrected public Voice authorization language on 2026-05-07 so voice profile use is governed by Agent/Auth likeness authorization rather than GDPR-style Consent.

  • Added public synthetic voice-profile ownership coverage on 2026-05-07.

  • Deployed Worker/static-assets baseline to https://voice.topolo.app on 2026-04-23.

  • Scaffold generated on 2026-04-23 from topolo apps scaffold.