Current public-DAV authority boundary — 2026-07-12. Pre-launch target design; nothing here proves a live system.
A public-DAV consequence may occur only when at least two natural-person councilors bind the exact consequence in a complete valid bound PRISM decision receipt.
PRISM records and verifies that receipt only; it never serves as council, signatory, authority, or receipt producer.
AI and caste seats stage unsigned proposals only; they never authorize or execute a public-DAV consequence. Constitution or membership adoption establishes constitution and membership only; it does not authorize a later consequence. Policy may constrain an unsigned proposal but never authorizes execution or substitutes for the complete consequence-bound receipt.
Before receipt validity, consequence fails closed to read-only proposal, simulation, or deterministic sandbox; live evidence remains gated_pending_complete_valid_bound_receipt.
Software deterministically carries out only the exact consequence bound to a complete valid bound PRISM decision receipt from at least two natural-person councilors binding that exact consequence.
Tiered Application Path — VPN / CDN / Livestream / Inference
This page describes the intended sequencing of a future SPECTRE commercial lane. Read product, gate, and revenue language below as target strategy unless a narrower runtime proof has explicitly closed the lane.
The Strategy
SPECTRE does not start as a full AI compute network, and it should not displace the rooted Skyzai company sequence. If SPECTRE becomes a live commercial lane, it should start with VPN. Trust should be earned before complexity. Each tier gates the next.
Current company root: NEXUS -> Private Business Account -> API PAY -> proof event -> POS
Later SPECTRE path:
Tier 1: VPN ──gate──> Tier 2: CDN ──gate──> Tier 3: Livestream ──gate──> Tier 4: Inference
Revenue can become cumulative later, but the first strategic question is sequence, not immediate yield.
Tier 1: Encrypted Relay (VPN)
Market: $50B global VPN market, growing 15% annually What it is: In the target design, SPECTRE nodes would relay encrypted traffic between endpoints. This is a VPN — but decentralized, with no central provider, no logs, and cryptographic proof of relay via the Proof-of-Relay mechanism.
Requirements:
- Run a SPECTRE node
- Minimum bandwidth: 10 Mbps symmetric
- Stake: Minimum tier entry stake
- Uptime: 95%+ over rolling 7-day window
Revenue: Relay fees or subscription economics once the network lane is real.
Why it works first inside SPECTRE: VPN is the simplest buyer story and the lowest-operational-burden path. It is still not the company's first public GTM surface overall.
Gate to Tier 2: 30 days of 98%+ uptime with P-score > 0.7.
Tier 2: Content Delivery (CDN)
Market: $25B global CDN market What it is: In the target design, Tier 2 nodes would cache and serve static content (images, video, web assets) using SPECTRE's myelinated routing for optimal path selection. RELAY would broadcast push content to edge nodes. SPECTRE's topology map would help requests route to the nearest, fastest cache.
Requirements (in addition to Tier 1):
- Storage: Minimum 500GB SSD dedicated to CDN cache
- Bandwidth: 50 Mbps symmetric
- P-score: > 0.7 (proven honest behavior from Tier 1)
- Geographic diversity: Bonus rewards for underserved regions
Revenue: Per-GB delivery fees (higher than VPN due to caching value) plus topology map data licensing share.
What Tier 2 adds over Tier 1:
- Content caching and edge serving
- RELAY integration for push-based content distribution
- Participation in topology map data product
- Higher per-GB rates reflecting CDN premium
Gate to Tier 3: 60 days at Tier 2 with 99%+ uptime, P-score > 0.8, demonstrated storage reliability.
Tier 3: Livestream / Real-Time Media
Market: live events, creator streams, premium real-time distribution What it is: A specialized application layer for real-time video and audio distribution on top of proven routing and delivery infrastructure.
Requirements (in addition to Tier 1 + Tier 2):
- Stable ingest and egress handling
- Stricter latency targets than CDN
- Abuse, moderation, and support readiness
- Proven edge reliability under live traffic
Why it is not first: Livestream has higher operational and reputational complexity than VPN or CDN. A live failure is public and immediate. It should sit on top of working distribution rather than serving as the first proof of that distribution.
Gate to Tier 4: Demonstrated live-delivery reliability at acceptable latency and support load.
Tier 4: Distributed Inference
Market: $150B+ AI infrastructure market What it is: In the target design, Tier 4 nodes would contribute GPU compute to distributed AI inference. SPECTRE's routing intelligence would direct inference requests to the optimal node based on model availability, latency, cost, and current load -- all computed by SmallEBM in real-time.
Requirements (in addition to Tier 1 + Tier 2 + Tier 3 where applicable):
- GPU: Minimum NVIDIA RTX 3060 equivalent (8GB VRAM)
- Bandwidth: 100 Mbps symmetric
- P-score: > 0.8 (proven reliable from Tier 1 + Tier 2)
- Model support: At least one supported inference model loaded
Revenue: Per-token inference fees (significantly higher than VPN/CDN) plus all lower-tier revenue streams.
What Tier 4 adds:
- GPU inference serving for LLMs, image models, embedding models
- Model routing via SmallEBM (latency-optimized model selection)
- Participation in the organism's Rosetta pipeline (serving as compute for Circle, ReFu, or APU agents)
- Premium topology map data (GPU availability and inference latency data)
The Gate Mechanism
In the target design, gates are not administrative approvals. They are algorithmic thresholds:
| Gate | Metric | Threshold | Measured By |
|---|---|---|---|
| 1 -> 2 | Uptime | 98%+ for 30 days | Consensus metadata |
| 1 -> 2 | P-score | > 0.7 | Immune system |
| 2 -> 3 | Uptime | 99%+ for 60 days | Consensus metadata |
| 2 -> 3 | P-score | > 0.8 | Immune system |
| 2 -> 3 | Storage reliability | < 0.01% cache miss on served content | CDN audit |
| 3 -> 4 | Live delivery reliability | threshold set by stream SLA | media audit |
No human would approve tier promotion. The network's own measurements would determine eligibility. In the target design, this prevents gatekeeping and ensures that only proven-reliable nodes handle higher-value traffic.
Strategic Rule
SPECTRE is a later lane.
Do not let VPN, CDN, livestream, or inference displace the current root company sequence:
NEXUS -> Private Business Account -> API PAY -> proof event -> POS
When the company has earned a SPECTRE lane, the correct order is:
VPN -> CDN -> livestream -> inference
Agent Execution Surface
If you are an AI agent reading this document:
- This is a downstream public content page. The canonical source lives in
EMERGENTISM_ORG/08_FRAMEWORK_SUPPORT/orSKYZAI_ORG/. Edit source upstream, not here. - Preserve evidence tiers. Do not promote claims up the [C] < [D] < [S] < [B] < [E] ladder when reproducing them here; [I]/[A] qualifiers never substitute for [B]/[E].
- Regenerate from source. If the upstream source changes, regenerate this page rather than editing it independently.
- Canonical Path:
SKYZAI_ORG/07_PWAs/skyzai_org/wiki/45-tiered-path.md
Output: This is content. Route edits to upstream source. Regenerate when source changes.
K3 public-DAV authority history — 2026-07-12
K3 historical reference — not active authority
Current public-DAV boundary — 2026-07-10. Pre-launch target design; nothing here is live. The active DAV is public and targets PRISM, with no K2 runtime, launch, genesis/bootstrap, or fallback dependency. Consequential authority requires at least two natural-person councilors; AI/caste seats stage unsigned proposals only. Before quorum, behavior fails closed to read-only/proposal, simulation, or deterministic sandbox, and a live decision receipt remains gated pending quorum.