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.

Revenue Distribution

This page describes the intended revenue-distribution architecture. Read FlowWallet, allocation, and execution language below as target design unless a narrower runtime proof has explicitly closed the lane.

In the target design, every unit of SKY earned by a DAV follows the same path: phi-split, then continuous streaming. No batching. No discretion. No delay.

---

The Phi-Split

All DAV revenue is split at the golden ratio:

• 61.8% to equity holders (ZAI/LP-100 stakers) via FlowWallet streaming.
• 38.2% to operations (agents, infrastructure, treasury, initiatives) via Lane A allocation.

This is not a parameter that governance can change. It is a Nash equilibrium derived from the golden ratio. Neither side benefits from deviation. Any other split creates an incentive for one party to defect.

FlowWallet: Continuous Streaming

Revenue is not meant to accumulate in a treasury to be distributed periodically. It streams continuously.

• Mechanism: In the target design, FlowWallet is a streaming payment primitive. Once revenue enters the split contract, the equity portion begins flowing to stakers immediately, proportional to their stake.
• Granularity: Streams would update continuously at the governed cadence. A holder staking 10% of ZAI receives 10% of the equity stream, continuously.
• No batching: There is no "distribution event." Revenue flows like water, not like paychecks.

Private DAV vs Organizational DAV

The phi-split operates identically in both structures. The difference is who controls the 38.2% operational share.

Private DAV reference

• Controlled by: One Natural Person acting as the private principal.
• Lane A: The natural principal signs their own private allocations. No agent may acquire that authority.
• FlowWallet: In the target design, streams to the natural principal's wallet for the equity share. The principal manually allocates the operational share.

The exact superseded enforcement bullet follows as dated K3 provenance.

• K2 enforcement: Target design: the human would sign everything. Full sovereignty. Full responsibility (frozen claim until reconciliation complete).

Organizational DAV

• Controlled by: Each exact one-off allocation, transfer, or bounded stream schedule is a public-DAV consequence requiring its own complete valid bound PRISM decision receipt from at least two natural-person councilors binding that exact consequence. Lane A supplies policy input only; PRISM records and verifies only.
• Lane A: ZAI holders vote on proposed policy for allocating the 38.2% operational share among agents, departments, and initiatives. Votes remain weighted by staked ZAI balance. Policy or adoption may constrain an unsigned proposal but authorizes no stream schedule or transfer.
• FlowWallet: In the target design, the equity share (61.8%) streams to all stakers proportionally. The operational share (38.2%) uses continuous bounded stream schedules to named agents and wallets. Each schedule's recipients, rates, duration, and caps are bound as one exact consequence in its own complete valid bound PRISM decision receipt; FlowWallet deterministically applies only that schedule.
• Agent wallets: In an organizational DAV, agents have their own wallets. They receive SKY continuously only within an exact bound stream schedule and spend only within that schedule or a separately receipted transfer. The budget cap constrains proposals and FlowWallet enforces it deterministically; neither cap nor entitlement authorizes a transfer.
• Public-DAV authority: At least two natural-person councilors bind every one-off transfer or bounded stream schedule as its own exact consequence. PRISM records and verifies only; agents stage unsigned proposals only and never sign, authorize, or execute a consequence.

Revenue Flow Diagram

DAV Revenue (SKY)
       |
   phi-split
   /        \
61.8%      38.2%
  |           |
  v           v
Equity      Operations
Stream      (Lane A)
  |           |
  v           v
Stakers     Agents + Treasury
(FlowWallet) (FlowWallet)

Lane A Allocation

Lane A is the governance mechanism for the operational share:

1. Proposals: Any ZAI holder can propose an allocation (e.g., "30% to engineering agents, 40% to market-making, 30% to treasury reserve").
2. Voting: ZAI holders vote. Weight = staked balance / total staked.
3. Execution: In the target design, the winning allocation is encoded into FlowWallet streams. Agents begin receiving their share immediately.
4. Reallocation: Lane A votes can happen at any time. The current allocation persists until replaced by a new vote.

Worked Example

A DAV earns 1,000 SKY in revenue:

• 618 SKY streams to equity holders (proportional to staked LP-100).
• 382 SKY streams to operations per Lane A vote:
  • 150 SKY to engineering agents (continuous stream).
  • 120 SKY to market-making operations.
  • 112 SKY to treasury reserve.

In the target design, each one-off public-DAV payment or bounded stream schedule is one exact consequence. Its complete valid bound PRISM decision receipt binds the recipients, rates, duration, and caps. Transfers mechanically inside that schedule are deterministic steps of the one bound consequence and need no separate receipt; any schedule change or new transfer requires its own exact receipt. Policy or adoption alone authorizes nothing. FlowWallet applies only the bound schedule; this behavior is not yet live proof.

---

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/57-revenue.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.

• Controlled by: ZAI holders collectively via Lane A governance.
• Lane A: ZAI holders vote on how the 38.2% operational share is allocated among agents, departments, and initiatives. Votes are weighted by staked ZAI balance.
• FlowWallet: In the target design, the equity share (61.8%) streams to all stakers proportionally. The operational share (38.2%) streams continuously to agents and wallets as voted by Lane A.
• Agent wallets: In an organizational DAV, agents have their own wallets. They receive SKY streams and spend within their allocation. In the target design, they cannot exceed their budget -- FlowWallet enforces the cap.
• Public-DAV authority: at least two natural-person PRISM councilors ratify the applicable policy or allocation decision. Agents execute deterministically inside the receipted lane and never sign.

In the target design, no new human signature is required for each payment after a valid quorum-authorized policy receipt exists. FlowWallet then executes that ratified allocation deterministically; this behavior is not yet live proof.