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.

The Three Gates

Every DAV in the Skyzai ecosystem must pass through three gates continuously. These are not periodic audits. They are persistent conditions. Fail any gate and the corresponding mechanism shuts down. Read the gate descriptions below as constitutional target design unless a separate runtime proof has explicitly closed the loop.

---

Gate A: Receipt-Bound

No receipt, no reality.

Every state change in the protocol is supposed to produce a cryptographic receipt. This is K0 -- the zeroth invariant, the foundation of all others.

• Scope: Every token transfer, every vote, every agent action, every revenue split, every liquidation. All of it.
• Format: Target path: immutable, timestamped receipts with governed ordering and external archival. Current local/runtime proofs may satisfy K0 with append-only local receipts before full external anchoring is wired.
• Enforcement: Target path: any transaction that fails to produce a valid receipt would revert. Current local proof lanes may fail closed with append-only local evidence before full external anchoring is wired.
• Implication: Within protocol-governed lanes, there is no unreceipted reality. If it is not receipted, it did not happen. An agent claiming to have performed work without a receipt chain is making a claim the protocol cannot verify and will not honor.

What Gate A Prevents

• Invisible fund movements.
• Unaccountable agent behavior.
• Disputed transaction histories.
• "I thought I sent it" failures.

Gate B: Truth-Gated

Transparency below 90% closes the Faucet.

Gate B ties a DAV's ability to raise new capital to its willingness to be transparent.

• Metric: Target path: Transparency Score would be computed from verifiable financial disclosures, agent activity logs, treasury positions, and audit-trail completeness.
• Threshold: 90%. This is a hard cutoff, not a gradient.
• Consequence: Target path: when Transparency < 90%:
  • The Faucet closes (no new LP-100 can be issued).
  • Event Tenders are suspended.
  • The DAV can still operate, trade, and distribute revenue -- but it cannot grow.
• Recovery: Restore Transparency >= 90% and the Faucet reopens. In the target design, no governance vote is needed; the gate is mechanical.

What Gate B Prevents

• Opaque organizations diluting equity holders.
• Capital raises by entities hiding material information.
• Growth without accountability.

Gate C: Exit-Safe

Grace Exit at NAV is a target design (frozen claim until reconciliation complete).

Target design: Gate C would guarantee that any LP-100 holder can leave receiving their proportional share of Net Asset Value (frozen claim until reconciliation complete).

• Mechanism: Grace Exit (see K4). The protocol calculates NAV, divides by total LP-100, and pays the exiting holder their share.
• Unconditional: Target design: no lock-up period, no governance approval, no waiting list, no penalty (frozen claim until reconciliation complete).
• Atomic: Target design: the exit would complete in a single transaction. LP-100 would be returned, NAV share paid in SKY (frozen claim until reconciliation complete).
• Data export: The exiting holder receives all their data. The organism retains nothing.

What Gate C Prevents

• Equity traps (tokens you cannot sell or redeem).
• Governance capture (majority blocks minority from leaving).
• Information asymmetry on exit (holder does not know what their share is worth).

---

Three Survival Laws

The Three Gates encode three survival laws for any organism:

Law	Gate	Statement
Accountability	A (Receipt)	Every action leaves a trace.
Transparency	B (Truth)	Growth requires openness.
Freedom	C (Exit)	Target design: the door would always be open (frozen claim until reconciliation complete).

An organism that violates any of these laws is not sovereign -- it is a trap. SoResFi is designed to make traps structurally impossible.

Gate Interactions

The gates reinforce each other:

• Gate A (receipts) makes Gate B (transparency) measurable. You cannot score transparency without receipted data.
• Gate B (transparency) makes Gate C (exit) informed. You cannot exit at fair value without knowing what the organism is worth.
• Gate C (exit) makes Gate A (receipts) honest. If holders can always leave, the protocol cannot afford to hide unfavorable data.

The three gates form a closed loop. Remove any one and the other two collapse.

---

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/58-three-gates.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.