SPECTRE · 1 : 1 communication
A direct channel between two parties. Its first use would be direct messaging; settlement is a separate capability.
1 : 1
One sender and one recipient share a direct conversation or request. The route may still cross several network nodes.
The first product direction is a voice-first messenger for direct conversations between people, AI models and agents, with the destination always visible. Two voice modes are different things: a voice note is a recording that is stored and delivered like any message, while live push-to-talk is a real-time audio stream that a recipient who is offline would miss. Which mode comes first is still open.
Direct messages should use an established end-to-end protocol, such as the Signal protocol’s PQXDH and Double Ratchet, rather than new cryptography. Relays could still see timing, size and routing metadata. A conversation with an AI endpoint would say that the endpoint can process its content.
APU can propose turning addressed material into a note, task or reminder. Your permitted application and chosen store—not APU by default—would retain it under explicit consent and retention terms. A change should record who requested it and support the applicable revision or undo path. Transient delivery does not guarantee deletion from every recipient or provider. APU reads only what you address or hand to it; it is not a party to conversations between people by default.
FLOW names the one-to-one pattern. Direct messaging is its first use; settlement is a separate capability with its own keys, records and audits. Still to specify: the encryption protocol, device sessions, offline delivery, how long each copy lasts and what deleting can and cannot reach. The Communicator plan uses Nostr as a bootstrap until SPECTRE is operational; a Nostr messenger would not prove MESH routing.
Research target: no live Skyzai messenger, encryption service or message-deletion guarantee is claimed.
The relationship shown here is logical: it says who communicates with whom. SPECTRE’s physical routes may cross multiple peers. Permission, retention and ledger agreement keep their own rules.
This page applies SPECTRE’s VMOSK-A delivery direction; it is not a new product charter or evidence of a running service. Specify the interface, replay a bounded interaction and test missing participants, failure and correction before adopting a changed design.
Context: Skyzai.