SPECTRE · 1 : N communication
Broadcasts, signed milestones and feeds, sent to a public or a permissioned audience.
1 : N
One publisher sends an event to an audience whose membership and delivery rules are explicit.
RELAY can describe public announcements, permissioned group updates, creator posts and signed milestones. A milestone should carry its author, version, time, source and intended audience so receivers can understand what they are seeing.
A Nostr-inspired social feed could combine one-publisher events distributed by RELAY, personalised selection by AXIOM and media cached near its audience by a CDN. Each answers a different question. Many-publisher public-post discovery and interaction are a proposed MESH application style. Cache availability does not prove the publisher is trustworthy, and forwarding does not prove every subscriber received the event.
Public events can be readable by anyone. Permissioned broadcasts need audience membership, key rotation and removal rules. Retention differs too: a live-only update, an expiring ciphertext and a lasting public milestone make different promises.
Research needs to settle fan-out strategy, offline delivery, moderation, replay protection, content availability, cache eviction and how publishers correct or supersede an earlier milestone.
Research target: no broadcast network, public feed, CDN or delivery guarantee is live.
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.