User products
- Voice-first messengerDirect conversations between people, AI models and agents.
- RELAY broadcasts and milestonesWith content delivery (CDN) for their media.
- InferenceModel results for a person, an organisation or an agent.
SPECTRE · research design
Transport, optional egress, content delivery and inference have different operating obligations. Node count alone establishes neither useful work nor rewards.
SPECTRE overview Two proposed sequences are kept apart. Each step follows only when the one before it has been demonstrated. Running a node could become an operator business, but only if each service is optional, measurable and paid for under clear terms; neither sequence is an operating offer. Every node would also carry MESH traffic. Additional node services are separate operator choices; a node does not become a VPN exit by default. Third-party internet egress needs explicit opt-in, security controls, exit policies and abuse handling. Service receipts can record work; they do not by themselves prove quality, customer demand or operator profit. A task-adapted model listing would also need its exact model/version, rights, hardware and evaluation disclosure. The proposed They access plane would route a request only to an eligible model endpoint; SPECTRE route telemetry cannot qualify a model or grant access to Cortex memory. World-model and robotics workloads would be later classes within the inference step. These chapters explain a research design. An animation, source specification or local website test does not establish a running network.Two roadmaps, one node network
User products
Node services
Continue through SPECTRE.
Context: Nodes & services.