Skip to content

Privacy controls

Choose optional technologies

Necessary technology is always active because it provides security and remembers this choice.

NecessaryConsent record, security, and core site operation.
Always on
Request a demo
PlatformsGovernment & DefenseDAFPulseOperations & ERPCortrovaHaultroManaged ServicesARIAMoreZennvueRealtrAIVortiekCustom SoftwareAll platforms
InnovationsProgramsTrunnion CoreTrunnion VoiceTrunnion LLMTrunnion MeetAll innovations
IndustriesBrowse by industryDefense & National SecurityGovernment ProcurementManufacturing & ERPWaste & Fleet OperationsEvents & MarketplacesMore industriesReal EstateManaged ServicesMarketing & SEOTravel & HospitalityAll industries
How it worksSecurityInsightsAboutRequest a demoView the platforms
Interaction programIn development

Trunnion Voice

Voice, built to the platform's governance standard.

Voice is the interaction layer under development for governed spoken input and output inside Trunnion workflows. The program is being designed to inherit identity, policy, approval, retention, and evidence boundaries from Core rather than operating as an independent voice assistant.

Discuss this capability All innovations
System roleTrunnion Voice
  1. 01Audio input
  2. 02Consent and identity
  3. 03Policy boundary
  4. 04Core orchestration
  5. 05Human review
  6. 06Evidence and retention

Conceptual system view. This is not a live product screen.

Why this layer exists

A technical program with a defined place in the system.

01

Voice inside a governed run

Spoken interaction should enter the same policy and approval path as typed or system-generated work.

02

Context stays bounded

Identity, tenant, retention, and permitted-tool rules remain deployment-specific requirements.

03

No public feature inventory yet

Models, languages, latency, transcription behavior, and release timing are not represented as available on this page.

Trunnion Voice operating pattern

How Trunnion Voice fits into a governed run.

This sequence explains the intended relationship between the capability, the control plane, human authority, and release evidence.

  1. 01
    Input

    Receive authorized audio

    The release defines supported sources, consent, identity, and retention.

  2. 02
    Boundary

    Apply interaction policy

    Tenant, data, and permitted-action rules constrain processing.

  3. 03
    Interpret

    Prepare governed context

    The voice layer structures an input for a Core-managed workflow.

  4. 04
    Decision

    Keep a person in command

    Consequential actions remain subject to the workflow approval boundary.

  5. 05
    Record

    Apply evidence and retention

    The release determines what transcript, action, and decision evidence is retained.

Illustrative workflow. Exact controls, integrations, and evidence are verified for the deployed release.

Where it connects

One innovation layer, connected to product work.

This program is being developed in relation to Core and the platform family. A link below does not establish that the capability is available in that product.

Defense & National SecurityDAFPlatform liveGovernment ProcurementPulsePlatform liveManufacturing & ERPCortrovaPlatform liveWaste & Fleet OperationsHaultroPlatform liveEvents & MarketplacesZennvuePlatform liveReal EstateRealtrAIPlatform live
Current public boundary

What this page establishes.

Trunnion Voice is in development. No public model, supported-language list, latency target, feature set, launch date, or deployment entitlement is claimed.

Program status
In development
Customer entitlement
Confirmed in the written agreement
Control behavior
Verified for the exact release and environment
Certification
No certification is established by this page

Get started

Ready to build on Trunnion AI?

See the governed control plane run against your workflow, in your environment. From cloud to air-gap.

Request a demoAll innovations