Status: pre-launch. This page describes target design; this document does not establish a deployed service.

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.

Economic allocation examples below remain unreconciled alternatives. A policy vote constrains a proposal but does not authorize a payment. Exact authorization must bind recipients, asset, rates, duration and caps before a rail applies a schedule; changes need new exact authorization.

---

Historical fixed split and streaming proposal — unresolved research, not current implementation

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.

Historical private allocation profile — unresolved research, not current implementation

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: Under applicable law, the natural principal signs each exact private allocation. 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.

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 the signer(s) required by applicable law, the entity's governing instrument, or a valid competent mandate binding that exact consequence. Lane A supplies policy input only; PRISM records and verifies only.
• Policy input: Eligibility, voting denominators and proposed allocation rates require separate owner reconciliation. A vote may constrain a proposal but authorizes no schedule or transfer.
• Bound schedule: Deterministic software applies only the separately authorized recipients, asset, rates, duration and caps; this page selects no equity percentage or distribution rule.
• Agent budgets: Named recipient accounts and budget caps constrain unsigned spending proposals. Deterministic software may apply only the separately authorized exact transfer or stream schedule; an agent does not acquire custody or consequence-execution authority from a budget.
• Public-DAV authority: the signer(s) required by applicable law, the entity's governing instrument, or a valid competent mandate 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.

Historical distribution diagram — unresolved research, not current implementation

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: Eligibility follows the separately adopted instrument and governance terms; this page does not select eligible holders or allocation percentages.
2. Voting: Eligibility and the voting denominator remain owner-reconciled policy inputs; this page selects neither.
3. Authorization: A winning vote is policy input, not permission to move funds. A separate exact consequence-bound mandate must specify recipients, asset, rates, duration and caps.
4. Reallocation: Changing a schedule requires a new applicable exact authorization, not merely a replacement vote.

Historical distribution arithmetic example — unresolved research, not current implementation

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.

---

Historical predecessor wording — retained on 2026-09-27, not active rules

The displaced passages are preserved verbatim for lineage. This retention date is not their original authorship date.

Predecessor passage 1

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.

Predecessor passage 2

• 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.

Predecessor passage 3

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.

Historical follow-up wording — retained on 2026-09-27, not active rules

Follow-up predecessor passage 1

• 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.

Follow-up predecessor passage 2

1. Proposals: Any ZAI holder can propose an allocation (e.g., "30% to engineering agents, 40% to market-making, 30% to treasury reserve").

Follow-up predecessor passage 3

2. Voting: ZAI holders vote. Weight = staked balance / total staked.