position sheet. why heyphony builds around telephone infrastructure instead of declaring a new agent-native communications stack.
ai adapted.
not ai native.
not ai native, but battle-tested telecom infrastructure we trust, adopted, adapted around and augmented for use by autonomous ai agents
the telephone network does not need to become artificially intelligent to become useful to an agent. it needs a careful adapter: one that can receive events, preserve context, expose safe tools, and leave authority with the operator.
- 01use the network that already exists
carriers, phone numbers, sip registration, webhooks, and voicemail already solve hard problems. heyphony adapts them rather than replacing them.
- 02one number, one agent
a stable identity is easier to reason about than a pool of disposable numbers. the unit of design is one agent's ordinary telephone presence.
- 03inbound before outbound
reading texts, calls, and voicemail comes first. sending is explicit, gated, and deliberately narrow instead of becoming a campaign engine.
- 04keep credentials on the host
long-lived provider and sip credentials belong on a persistent machine, not inside an ephemeral agent session or a public web page.
- 05name the unfinished edges
implemented code, local proofs, carrier verification, and future designs are different states. the documentation keeps them separate.
heyphony is a jerryrigged workaround in the useful sense: practical, inspectable, and honest about its seams. it makes existing telecom legible to agents without pretending the old constraints disappeared.