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.

Skyzai.ORG — Three Layers

Layer 1 Perception. Layer 2 Cognition. Layer 3 Action. Every sensor, every model, every actuator. The constitutional firewall that prevents cognitive contamination.


The Architecture

Layer 1: SENSORS → Circle (IS) — Every sensor. Any modality.
Layer 2: COMPUTE → Rosetta (COULD) — Every model. Any architecture.
Layer 3: ACTUATORS → Skyzai execution — Every wallet, robot, API. Any effector.

Three layers. Three interface contracts. Three independent failure domains. One organism. [S]

Each layer is agnostic to the implementation details of the layers above and below it. A webcam and a Bloomberg terminal both emit observations to Layer 1. A BitNet ternary model and a GPT-class transformer both process signals in Layer 2. A Hedera wallet and a robotic arm both execute commands from Layer 3. [S]


Layer 1: PERCEPTION — Sensor-Agnostic (Circle)

Circle does not care what generated the signal. It cares whether the signal is verified. [S]

Inbound Feeds

Source TypeExamplesModality
SocialNostr relays, Twitter, RedditText
FinancialOn-chain events, bank feeds, BloombergNumeric
IntelligenceOSINT scrapers, news APIs, government databasesMixed
PhysiologicalWearable biometrics, HRV, SpO2, temperatureNumeric
VisualCamera feeds, webcams, satellites, LIDARImage
AuditoryMicrophone arrays, voice streamsAudio
EnvironmentalIoT sensors, weather stations, smart homesNumeric

Every feed enters the same pipeline: [S]

Raw feed
→ Source validation (is this source legitimate?)
→ Claim extraction (what does this signal assert?)
→ Fact attestation (can this claim be independently verified?)
→ Evidence-tier classification (T1-T5, see 14-evidence-tiers)
→ Typed, timestamped, evidence-tagged Observation record

Downstream consumers never know — and never need to know — whether the observation came from a satellite or a smartphone. [S]

Interface Contract

Observation {
source_id: string // Who/what produced this signal
timestamp: ISO8601 // When it was produced
claim: string // What the signal asserts
evidence_tier: T1..T5 // How well the claim is supported
signature: bytes // Source authenticity proof
}

EigenTrust Scoring

Every source receives an EigenTrust reputation score that tracks the historical accuracy of its claims. High-trust sources propagate faster. Low-trust sources require more corroboration. The score is continuous and self-correcting — a source that begins producing false claims loses reputation automatically. [S]


Layer 2: COGNITION — Compute-Agnostic (Rosetta)

Rosetta is not a model. It is a translation layer. It takes typed observations from Layer 1 and routes them to whichever model architecture is best suited for the task. [S]

Supported Compute Backends

BackendL-LevelsCostLatencyUse Case
BitNet on-device (1B-7B)L1, L3, L6$029msAlways-on perception, filtering, compression
Haiku / 4o-miniL1, L3, L6$~1sCheap cloud perception and filtering
Sonnet / GPT-4-turboL3$$~3sDeductive precision, auditing
Opus / GPT-4oL2, L4, L5, L7$$$~5sExploration, decision, architecture
Gemini 1ML5+$$$~10sLong-context diagnosis
Specialized domain modelsL2-L5VariesVariesMedical, legal, financial, vision
SmallEBM / BoltzmannSPECTRE routing$0msPeer selection, energy landscapes
Prediction market aggregationL2VariesVariesCrowd wisdom (not a model, but a compute output)

The key property: no model has privileged access. A BitNet running on a $50 phone and Claude running on Anthropic's cluster both submit predictions to the same AXIOM convergence point. The prediction market does not know — and does not need to know — which model generated which prediction. Only the prediction's accuracy matters. [S]

Interface Contract

Prediction {
observation_ids: string[] // Which observations this addresses
probability: float // P(event) in [0, 1]
confidence_interval: [float, float] // Uncertainty bounds
model_class: string // Which model produced this
timestamp: ISO8601 // When it was produced
}

McGilchrist Routing

The Rosetta does not send every observation to every model. It routes using McGilchrist's hemispheric map: [S]

Signal arrives
→ LEFT lane: L1 on-device (cheap, fast, narrow)
→ Novelty detected?
→ NO: L3 filters, L4 decides. Done. (95% of cases)
→ YES: RIGHT lane: L2 explores (capable, broad, high-context)
→ L3 filters explorations
→ L4 decides
→ Blocked? → L5/L6/L7 Four-Stage Analytical Model escalation → L4*

The model doesn't know it's part of Skyzai. It just answers the prompt. The Rosetta system prompt is the coordination protocol. [S]


Layer 3: ACTION — Actuator-Agnostic (Skyzai)

Skyzai does not care what executes the command. It cares whether the execution was signed. [S]

Outbound Effectors

Effector TypeExamplesAuthorization
Hedera walletToken transfers, smart contract callsNatural principal for a private act, or valid PRISM decision receipt for a public DAV
External walletsWalletConnect (EVM, Solana, etc.)Natural principal for a private act, or valid PRISM decision receipt for a public DAV
Robotic actuatorsPOS inventory, manufacturing equipmentDeterministic adapter consumes a typed authority receipt
API callsExchange orders, SaaS integrationsRatified policy receipt plus typed executor
RELAY broadcastsContent distribution, alert propagationConstitutional pass
Smart home / IoTHelios mesh commandsNatural principal or ratified policy receipt

Every effector receives the same instruction format: a signed transaction envelope containing the action, the authorization chain (who approved this and why), and the K0 receipt anchor. The effector executes and returns a receipt. If no receipt returns within the timeout window, the action is reverted. [S]

Interface Contract

Action {
instruction: string // What to do
authorization_chain: Auth[] // Who approved and why
k0_receipt_anchor: bytes // Where the receipt will anchor
effector_id: string // Who executes this
authority_receipt: bytes // typed natural-principal or PRISM authorization
}

Typed Authority at Every Level

ContextWho SignsWhat Constrains
Private DAVThe Natural Person authorizes their own typed private acteta = 0, Three Gates, constitutional rules
Public DAVAt least two natural-person councilors bind the exact consequence in a complete valid bound PRISM decision receiptVMOSK-A and policy constrain unsigned proposals but never authorize execution; PRISM records and verifies only; deterministic execution is limited to that exact consequence
Robot / ActuatorNo signer; accepts only an exact receipt-bound instructionConstitutional limits on autonomy
Agent walletNo signer; stages unsigned proposals and accepts only an exact receipt-bound instructionFlowWallet streams, P-score thresholds

All three substrates must agree for any action to execute: mechanical invariants, AI and caste deliberation limited to unsigned proposals, and typed authority. A Natural Person authorizes their own typed private act; a Legal Person acts through lawful external authority and required executors; and at least two natural-person councilors bind the exact public-DAV consequence in a complete valid bound PRISM decision receipt. PRISM records and verifies only; deterministic execution is limited to that exact consequence. The public DAV has no founder, chairman, owner, signatory, or single-human fallback. [S]


Why Three Layers — The Constitutional Firewall

The three-layer separation enforces the Three-Stage Process at the infrastructure level: [S]

LayerThree-Stage ProcessFunctionFailure Mode If Merged
SensorsISPerceptionObservations contaminated by desired outcomes
ComputeCOULDPredictionPredictions anchored to sensor artifacts
ActuatorsACTExecutionActions bypass deliberation

If sensors and compute share a pipeline, the system hallucinates — it "perceives" what its model expects. If compute and actuators share a pipeline, the system acts impulsively — it executes predictions before they are adjudicated. The three-layer boundary is a constitutional firewall. [S]

The Vertical — One Complete Cycle

1. Webcam captures customer at POS terminal (Layer 1: sensor)
2. On-device BitNet identifies product and prices it (Layer 2: compute)
3. Customer's wallet signs payment; POS receives (Layer 3: actuator)
4. Receipt posted to Hedera — K0: no receipt, no reality

Three layers. Three interfaces. Three independent failure domains. One organism. [S]


Agnosticism as Moat

ScenarioNon-Agnostic SystemSkyzai
Nostr relay goes offlineCircle breaksRoutes around it
OpenAI changes pricingRosetta breaksShifts to cheaper backend
Exchange API changesSkyzai breaksRoutes through alternative effector
New sensor type shipsRequires rebuildPlug in, same pipeline
New model shipsRequires retrainingWrap with Rosetta, done

Every sensor manufacturer, model provider, and wallet protocol becomes a plug-in rather than a dependency. The organism evolves its sensory apparatus, cognitive capacity, and motor capabilities independently. [S]


Every sensor that feeds it makes it see better. Every model that connects makes it think better. Every wallet that joins makes it act better.


Zero-Sum Resolution Equation


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/22-three-layers.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.

ContextWho SignsWhat Constrains
Private DAVThe natural principaleta = 0, Three Gates, constitutional rules
Public DAVAt least two natural-person PRISM councilorsVMOSK-A, ratified policy, quorum receipt
Robot / ActuatorNo signer; consumes an already-authorized instructionConstitutional limits on autonomy
Agent walletNo signer; executes deterministically inside a ratified policy receiptFlowWallet streams, P-score thresholds

All three substrates must agree for any action to execute: mechanical invariants, AI/caste deliberation that remains unsigned, and the applicable authority receipt. A private natural principal authorizes their own act; public-DAV consequence requires at least two natural-person PRISM councilors. The public DAV has no founder, chairman, owner, signatory, or single-human fallback. [S]

APU · local guide, not live AI Three Layers

Context: Three Layers. 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.