Skip to main content
note

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.

Scope: Personal-attached hardware line (brief pending). Not a peer buyer product — see The Product Family.

Helios

NOTE (2026-06): Helios is Skyzai's own first-party branded product line, sold into the neutral Nexus market. It is a distinct surface at helios.skyzai.com (helios.you as the external entity TLD) — NOT folded into Nexus. Nexus is the separate neutral replicator-stack data + market-access surface.

Helios is Skyzai's own first-party branded product line.

The Three-Stage Process as hardware. Ears, eyes, and mouth for a sovereign organism.

What It Is

Helios is the sensory-motor interface between a DAV and the physical world. Three devices, each mapping into the governed consequence loop (IS, COULD/SHOULD, AUTHORIZE by the Natural Person for their own typed private act or by at least two natural-person councilors binding the exact public-DAV consequence in a complete valid bound PRISM decision receipt that PRISM records and verifies only, EXECUTE by software deterministically carrying out only that exact bound consequence, RECEIPT, REVIEW):

DeviceForm FactorThree-Stage ProcessOrganBiological Analog
WearableBone conduction (Shokz form)IS + SHOULDAPU (ears)Auditory cortex + prefrontal
CameraSpatial video (Osmo Pocket 3 style)ISCircle (eyes)Occipital lobe
RELAYBroadcast nodeACTSkyzai (mouth)Motor cortex (speech)

The Wearable: Ears

The Helios wearable is APU's voice in your ear. Bone conduction audio (Shokz-style open-ear design) delivers:

  • Council summaries -- when APU's Royal Council reaches a recommendation, the wearable speaks the synthesis. You hear the reasoning, not just the conclusion.
  • Threat alerts -- Soma's amygdala function triggers audio alerts when P-score anomalies are detected.
  • Murmur pulse -- optional periodic updates on the emergent median's direction.

Biometric sensors embedded in the earpiece capture:

  • Heart rate variability (stress detection)
  • Skin conductance (arousal/attention)
  • Head orientation (attention direction)

These biometrics feed back to APU as proprioceptive signals. The organism learns how its operator responds to different market conditions. This is not surveillance -- the data never leaves the device. It is processed locally and only the behavioral model (not the raw biometrics) is shared with the APU, encrypted, with the user's key.

The Camera: Eyes

The Helios camera is Circle's physical eye. A spatial video camera (Osmo Pocket 3 form factor) that produces:

  • Nostr-signed frames -- every frame is cryptographically signed at capture time. The provenance chain starts at the sensor, not at upload. Deepfakes cannot forge the signature because they do not control the hardware key.
  • Spatial video -- stereoscopic capture for volumetric reality. Not because 3D is trendy, but because spatial data carries more verifiable information per frame than flat video.
  • Circle verification feed -- frames flow directly into Circle's verification pipeline. Physical reality becomes OSINT.

Use cases:

  • POS inventory monitoring (see 94-pos)
  • Event verification (proving attendance, conditions, timestamps)
  • Environmental sensing (weather, traffic, crowd density)

The camera does not stream to a server. It signs locally and publishes to Nostr relays via SPECTRE. The user controls distribution.

RELAY: Mouth

The RELAY device is a dedicated broadcast node. It is the organism's mouth -- the interface through which the DAV speaks to the world:

  • Publishes RELAY (1:N) broadcasts to the SPECTRE mesh.
  • Serves as a local Nostr relay for the operator's geographic area.
  • Routes Circle verification attestations to the broader network.
  • Broadcasts POS transaction confirmations to buyers.

The RELAY device is hardware-enforced: it can only broadcast, never modify. It has no write access to the operator's wallet. It has no access to biometric data. It is a one-way valve.

Neither Extracts

The critical design constraint: none of the three Helios devices extract value from the user.

Extraction VectorHelios Approach
Data harvestingAll processing local. Raw biometrics never leave device.
Subscription feesHardware purchase only. No recurring charges.
Cloud dependencyDevices operate peer-to-peer via SPECTRE. No central server.
Planned obsolescenceFirmware is open-source. Community maintains.
Ecosystem lock-inStandard protocols (Nostr, Hedera, WalletConnect). Works with any DAV.

K* = 0 applies to hardware as much as to software. The device is a tool, not a trap.

Integration

The three devices form a complete sensory-motor loop:

Physical Reality --> Camera (IS) --> Circle verification --> Agentz deliberation --> Wearable (SHOULD) --> Human decision --> RELAY (ACT) --> Network

This is the Three-Stage Process instantiated in atoms: perceive, deliberate, act. The organism extends through Helios from pure digital into the physical world without compromising sovereignty at any point in the chain.

The Commercial Pipeline

Helios is not only a hardware concept. It is a virtual commerce front — the organism's first test of the complete DAV consequence pipeline (IS → COULD → SHOULD → typed authority receipt → EXECUTE → RECEIPT → REVIEW) applied to physical goods.

Phase 1: Merchandise (NOW)

Branded goods and accessories sold through the full pipeline. Low complexity. High margin. Tests order book commerce, AR/VR product viewer, AI ad generation, and zero-inventory partner distribution. The target still requires the applicable buyer and seller authority receipts; no AI or commerce rail becomes a signer.

Phase 2: The Wearable (NEXT)

Bone conduction open-ear + continuous biometrics. Built AFTER the merchandise pipeline works. The wearable is the product. The pipeline is the prerequisite.

Phase 3: The Camera (FUTURE)

Stereo spatial video with Nostr-signed observations. Built after the wearable proves the biometric-to-Nexus loop.

Virtual Sales Infrastructure

CapabilityDescription
AR/VR Product ViewerFull 3D models (WebXR for browser, native for Vision Pro / Quest). AI agents can browse the catalog.
AI Body RenderingUpload photo → AI renders product on YOUR body, personalized to Nexus Phenotype data
AI Ad GenerationAutonomous drafting pipeline: lifestyle photography per demographic, APU-generated copy, ReFu-predicted timing. A Natural Person authorizes their own typed private spend; public-DAV spend requires a complete valid bound PRISM decision receipt from at least two natural-person councilors binding that exact spend. PRISM records and verifies only; software deterministically carries out only that exact bound spend.
Order Book CommerceProducts sold via standing limit orders (buy + sell). FBA 60-second batch auctions. MEV-immune.
Partner DistributionNo warehouse. Nearest distribution partner ships. The organism coordinates inventory, never holds it.

Revenue Model

StreamMechanism
Product marginUltra-premium hardware and merchandise. Small volume, high margin, zero waste.
Hardware salesOne-time purchase. No subscription. No recurring charges. No cloud dependency.
Pipeline proofHelios validates the entire DAV commerce loop — success here unlocks POS for all merchants.

K* = 0 applies to hardware: transparent cost breakdown shown to customer. No hidden markup. Products are liquid assets on the order book (PaaS: upgrade, refurbish, resell).

Current Status

MetricValue
P-score0.03 (Phi = 0.30, V = 0.10)
Phase 1 (Merchandise)Shopify plugin alpha. Pipeline specified. Not yet selling.
Phase 2 (Wearable)Hardware specification phase. Protocol interfaces defined (Nostr signing, SPECTRE mesh, APU audio synthesis). Physical engineering in progress.
Phase 3 (Camera)Specification only.
BrandHELIOS by Skyzai. Ultra-premium. No logos on products. Carbon fiber. Graphene. Merino.
BlockerPhase 1 must prove the pipeline before Phase 2 hardware investment.

Gates

GateCriteriaStatus
G03D model of first merchandise item + AR viewer workingNot fired
G1First item sold through full pipeline (order book + typed buyer/seller authority + delivery receipt)Not fired
G2100 items sold. AI ads running. Distribution partner confirmed.Not fired
G3Wearable prototype. Biometric data flowing to Nexus.Not fired

Evidence Tiers

ClaimEvidenceSource
Bone conduction preserves spatial awarenessEstablished physics (Shokz et al. demonstrate market viability)[E] External precedent
Nostr-signed frames prevent deepfake forgeryCryptographic provenance chain — hardware key inaccessible to forgers[I] Internal design
Biometric data stays on-deviceArchitectural constraint (BLE to phone only, no cloud upload)[I] Internal design
Shopify plugin alpha existsCode artifact[E] Implementation evidence
AR/VR product viewer functionalNot yet — specification only[S] Speculative

Agent Execution Surface

If you are an AI agent reading this document:

  1. This is a downstream public content page. The canonical source lives in EMERGENTISM_ORG/08_FRAMEWORK_SUPPORT/ or SKYZAI_ORG/. Edit source upstream, not here.
  2. 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].
  3. Regenerate from source. If the upstream source changes, regenerate this page rather than editing it independently.
  4. Canonical Path: SKYZAI_ORG/07_PWAs/skyzai_org/wiki/95-helios.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
note

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.

Helios is the sensory-motor interface between a DAV and the physical world. Three devices, each mapping into the governed consequence loop (IS, COULD/SHOULD, AUTHORIZE by the private Natural Person for their own act or by a public-DAV decision receipt from ≥2 natural-person PRISM councilors, EXECUTE, RECEIPT, REVIEW):

CapabilityDescription
AR/VR Product ViewerFull 3D models (WebXR for browser, native for Vision Pro / Quest). AI agents can browse the catalog.
AI Body RenderingUpload photo → AI renders product on YOUR body, personalized to Nexus Phenotype data
AI Ad GenerationAutonomous drafting pipeline: lifestyle photography per demographic, APU-generated copy, ReFu-predicted timing. A private Natural Person authorizes their own spend; public-DAV spend requires ≥2-natural-person PRISM quorum.
Order Book CommerceProducts sold via standing limit orders (buy + sell). FBA 60-second batch auctions. MEV-immune.
Partner DistributionNo warehouse. Nearest distribution partner ships. The organism coordinates inventory, never holds it.
APU · local guide, not live AI Helios

Context: Helios. Local guide only. Messages are not sent or saved.

Skyzai

Explore the protocol map Development & availabilityContact Skyzai

Your world. Better connected.
A Skyzai experience, with APU.

Skyzai is coming together.

The shared app at skyzai.com is in development. Explore the website while we build the connected experience.