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.

Four Routing Primitives — SPECTRE, RELAY, AXIOM, FLOW

This page describes the routing grammar of the organism. Read the implementation examples below as target protocol patterns unless a narrower runtime proof has explicitly closed a given lane.

Every communication pattern in the organism reduces to one of four topological primitives. These are not protocol names — they are mathematical categories of information routing. In the target architecture, these patterns run on the SPECTRE substrate.

The Hierarchy

SPECTRE (N:N) ── the substrate. Target architecture routes through this.
  |
  |-- RELAY (1:N)  ── broadcast ON SPECTRE
  |-- AXIOM (N:1)  ── convergence ON SPECTRE
  |-- FLOW  (1:1)  ── streaming ON SPECTRE

SPECTRE is not one of four equal primitives. In the architecture, SPECTRE names the hashgraph-shaped substrate. The other three are communication patterns that exist on that substrate.

SPECTRE — N:N Mesh (The Substrate)

Topology: Every node connected to every other node. Full mesh. Implementation: Target design: a self-myelinating hashgraph. Each edge in the mesh would be a gossip channel. Nodes that communicate frequently would develop thicker connections (myelination). Nodes that communicate rarely would atrophy. Function: SPECTRE is the nervous-system substrate. It is meant to carry all signals. Without SPECTRE, nothing routes. Folder: 3.1 SPECTRE/

In the target design, SPECTRE is hashgraph, not blockchain. No miners. No proof-of-work. No block times. Gossip about gossip. Asynchronous Byzantine Fault Tolerant (aBFT). Finality in seconds.

RELAY — 1:N Broadcast (On SPECTRE)

Topology: One sender, N receivers. Broadcast. Implementation: Target pattern: a node publishes a signed message. SPECTRE gossips it to all subscribers. Subscribers verify the signature against the sender's Nostr public key. Function: Announcements, price feeds, OSINT alerts, oracle data. Anything where one source needs to reach many consumers. Example: In the target pattern, Circle publishes a Watchman Score update. Every subscribed DAV receives it via RELAY on SPECTRE.

RELAY is the broadcast pattern of the organism. In the target design, it is built on Nostr event kinds, gossiped through the SPECTRE hashgraph. One message, N recipients, cryptographic authenticity.

AXIOM — N:1 Convergence (On SPECTRE)

Topology: N senders, one receiver. Convergence. Implementation: Multiple sources submit observations, predictions, or votes. A convergence function (median, LMSR, weighted average) reduces N inputs to one output. Function: Settled prediction market outcomes. Consensus. Aggregation.

AXIOM = settled ReFu bets. This is the critical definition. In the target design, when a ReFu prediction market resolves, the N bets converge into one truth value (the outcome). That settled truth is an AXIOM — a fact established by convergence of skin-in-the-game predictions. AXIOMs are the organism's knowledge base. They are not assertions. They are settled bets.

Example: ReFu market "Will ETH exceed $5000 by Q3?" resolves YES. The N:1 convergence of all bets produces an AXIOM. In the target design, this AXIOM feeds into Circle's intelligence graph and APU's decision inputs.

FLOW — 1:1 Streaming (On SPECTRE)

Topology: One sender, one receiver. Direct stream. Implementation: Target pattern: a continuous, conditioned payment channel between two parties. Tokens stream per-second from sender to receiver, conditioned on state (see Flow-Axiom). Function: Salary streaming, service payments, conditional transfers. Anything where value flows continuously between two parties. Example: A DAV streams payment to a service provider at 0.001 ZAI/second, conditioned on an AXIOM that the service is operational.

Why Exactly Four

These four patterns exhaust the topological possibilities:

• N:N (mesh) = SPECTRE
• 1:N (broadcast) = RELAY
• N:1 (convergence) = AXIOM
• 1:1 (direct) = FLOW

There is no 0:N (no sender) or N:0 (no receiver) because communication requires at least one of each. There is no M:N where M != 1 and M != N because M:N decomposes into combinations of the four primitives. Four is necessary and sufficient.

The Composition Rule

Complex communication patterns are composed from primitives:

• Circle 7-agent cascade: RELAY (publish query) -> SPECTRE (agents gossip) -> AXIOM (agents converge on reliability score)
• APU Court Deliberation: RELAY (broadcast signal to directorates) -> FLOW (each directorate reports to Chief of Staff) -> AXIOM (Chief synthesizes PROCEED/HOLD)
• Algorithmic TRO settlement: FLOW (streaming payment) conditioned on AXIOM (market resolution)

At the grammar level, every pattern in the organism decomposes into these four. No exceptions.

---

In the routing grammar, SPECTRE is the substrate. RELAY broadcasts on it. AXIOM converges on it. FLOW streams on it.

---

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/49-four-primitives.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.