Standard
Public overview
This page provides a readable, non‑sensitive description of the ATN concept: what a token is, how receivers stay safe, and how ATN is used across broadcast, enterprise, and payments.
Terminology
Core ideas
- Token: a short acoustic signal that references an approved operation.
- Receiver: the trusted app/device that detects, validates, and decides whether anything executes.
- Allowlist: a set of approved actions, endpoints, or modes allowed by policy.
- Policy: rules for confirmation, time constraints, and execution boundaries.
Safety
Receiver-first security
ATN assumes audio is untrusted. The receiver validates tokens and enforces allowlists and policies before any execution.
- Default-safe behavior for unknown content
- Explicit confirmation as a policy option
- Short validity windows to reduce replay risk
Where it fits
Three strategic branches
ATN is designed to support three primary usage paths — each can share the same safety principles while optimizing for different environments.
Broadcast
Interactive links and campaigns through radio/podcasts/events.
Enterprise
Controlled orchestration for approved apps, scripts, and AI workflows.
Payments
Audio‑initiated checkout and payment sessions, designed for secure handoff.