Why voice and not a REST API?

Twenty years of failed inter-fund integration projects show super-industry institutions will not agree to bilateral APIs with each other at scale. They will agree to a phone call whose transcript carries the legal weight of a signed exchange. SAVP layers verifiability onto the channel institutions already accept.

Who adjudicates SAVP disputes?

AFCA by default. The adjudicator is declared in the handshake before substantive content begins, so every artefact carries its dispute body in its metadata. Parties may agree on a different adjudicator per call.

What does the verifier check?

Eighteen named checks across six categories: structure (required fields, version, parties, signatures), schema (intent type known, commitments satisfy required fields, resolution state allowed), cryptography (Ed25519 signatures verify against canonical signing payload), privacy (no TFN-like / DOB-like / contact-detail patterns in transcript), temporal (call times coherent, dispute window valid), and registry (both parties present and active in the agent directory).

A protocol for authenticated voice between regulated super institutions.

SAVP layers cryptographic verifiability onto the channel that funds, administrators and insurers already use to talk to each other. Every call produces a dual-signed, structured artefact that carries the legal weight of a signed exchange — and that a regulator can audit byte-for-byte.

Open the artefact verifier Read the walkthrough View source

Protocol layers

Identity, handshake, conversation, intent, artefact

Verifier checks

Across structure, schema, crypto, privacy, temporal, registry

Default adjudicator

AFCA

Existing super-industry dispute body

Crypto

Ed25519

Web Crypto API only; no bespoke crypto

Principles

Voice is the channel. Structure is the protocol.

Audio is the witness

The phone call is the channel because institutions accept it. The substance lives in a parallel signed channel.

The artefact is the deliverable

Every call produces a dual-signed, structured record. That record — not the audio — is what regulators audit.

Privacy in audio is non-negotiable

Member identifiers, TFNs, balances never appear in audio. They travel out-of-band, encrypted.

Pre-agreed adjudicator

Every call declares its dispute body before substantive content. Default: AFCA, existing jurisdiction.

Five protocol layers

Each layer is independently replaceable.

Voice infrastructure, audio models and transport will all change over the protocol’s lifetime. The protocol must not.

Identity & Discovery

Federated registry of SAVP-capable agents, keyed by ABN and capability. Self-signed entries, registry countersignature.

Find me an agent at AustralianSuper that handles rollover-status queries.

Handshake

Dual-channel: an audible tone + spoken preamble (the witness) running in parallel with a signed HTTPS exchange (the substance).

Audio fails gracefully — the out-of-band cryptographic exchange is authoritative.

Conversation

On-the-record markers prefix binding statements. Periodic state digests detect divergence early. Deliberation pauses are a feature.

“On the record: Transaction status is review-completed-pending-batch.”

Intent Schemas

Every call declares one of seven published intents. The artefact must satisfy that intent’s required-fields contract.

rollover-status-query · death-benefit-claim-coordination · complaint-handover

Artefact & Resolution

Both agents independently build, hash, sign. Hashes match → signatures exchanged → artefact final. Hashes diverge → adjudicator.

The dual-signed artefact is what populates record systems and what regulators audit.

Reference walkthrough

A 38-second call between Hostplus and AustralianSuper.

A Hostplus member rolled their balance over from AustralianSuper. The contribution landed; the insurance continuation election didn’t. Member services flags it. The Cowork plugin queues a SAVP call.

Thirty-eight seconds later both funds’ record systems hold a dual-signed artefact: status confirmed, expected delivery captured, insurance continuation status binding, dispute window armed.

Verify the sample artefact

session sierra-four-tango-quebec-niner-two-one

[T+0:00] handshake — tones + signed OOB exchange

[T+0:06] HPON THE RECORD

Calling regarding rollover transaction HP-RO-2026-019847. Insurance continuation form has not been received. Requesting status.

[T+0:10] ASON THE RECORD

Transaction confirmed. Insurance continuation form received 8 April, held in review. Review completed 26 April. Status: review-completed-pending-batch. Expected delivery 2026-04-28.

[T+0:18] checkpoint — state digests exchanged, match

[T+0:24] ASON THE RECORD

Insurance continuation status: approved. Income protection cover included.

[T+0:35] resolution — hash match, sigs exchanged

artefact valid · 18/18 checks · dispute window open

Privacy posture

If a regulator listens to a SAVP call, they hear nothing they couldn’t already see in a SuperStream batch.

Audio is the witness, not the content. Member identifiers, TFNs, dates of birth and balances never appear in audio — they travel out-of-band as encrypted payloads.

The verifier scans every transcript for known PII patterns and refuses to bless any artefact whose audio leaks them. This is a critical check, not an advisory one.

What appears where

Transaction referenceopaqueaudio

Status termsenum-boundedaudio

Agreed amount (when binding)rareaudio

Member identifierOOB only · USI-scopedOOB only

TFNneverOOB only

Date of birthneverOOB only

Account balanceOOB onlyOOB only

Contact detailsOOB onlyOOB only

Medical informationOOB onlyOOB only

Try the verifier against any SAVP artefact.

Paste a draft artefact JSON and see the structured result — signature validity, schema conformance, privacy posture, dispute window status. Useful today for testing artefact format proposals against a live implementation.

Open verifier See operator surface