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.

DAV Dissolution

This page describes the target dissolution architecture. Read trigger, sequence, and archival language below as target design unless a narrower runtime proof has explicitly closed the lane.

Death is not failure. Death is information.

Overview

Every living organism dies. A DAV that cannot die cannot evolve, because immortal failures occupy ecological niches that healthier organisms need. Dissolution is the protocol's intended immune response: deterministic, transparent, and instructive.

The Five Mortality Triggers

ID	Trigger	Condition	Grace Period
M1	Stasis	Metabolic loop stalled at any stage	7 days
M2	Truth Failure	Circle Phi below 0.60 continuously	30 days
M3	Viability Collapse	V-score below 0.30 continuously	14 days
M4	Market Rejection	Zero external transaction volume	90 days
M5	Constitutional Violation	Any K-invariant breached	Immediate

M1-M4 have grace periods: in the target design, the trigger condition must persist continuously for the stated duration before dissolution initiates. A single block of recovery resets the clock.

M5 is immediate in the target design. A constitutional violation (e.g., LP-100 supply != 100, unsigned transaction executed) triggers dissolution in the same consensus round. There is no appeal.

The 60-Day Deterministic Sequence

Once any trigger fires in the target design, the dissolution clock starts. Every step is on-chain, automatic, and irreversible.

Day 0: Halt

• All organ state transitions to DISSOLVING.
• The metabolic loop halts. No new FLOW streams open.
• The heartbeat continues (it must, to execute the remaining sequence).
• A DISSOLUTION_INITIATED event is broadcast on RELAY with the trigger ID.

Days 1-29: Settlement Period

• All open prediction markets in RealityFutures enter forced settlement.
• All awaiting FLOW transactions complete or revert.
• APU Council is disbanded. No new allocations.
• Organ operators have 29 days to export any off-chain state they wish to preserve.

Day 30: ZAI Distribution

• The treasury's remaining ZAI balance is distributed to LP-100 holders pro-rata.
• distribute(holder) = treasury_balance * (holder_LP100 / 100)
• LP-100 tokens are burned in the same transaction. K1 conservation holds: 100 tokens existed, 100 tokens are destroyed.
• After this block, the DAV has no capital and no shares.

Days 31-59: Archival Period

• Target design: the DAV's full state -- genome, P-score history, organ configurations, metabolic records -- is designed to be serialized and written to the target external anchor (Arweave via Irys in current doctrine).
• The receipt hash is designed to be posted to the DAV's root Hedera topic; local proof lanes may use append-only evidence until the external anchoring path is fully wired.
• This is the organism's fossil record. In the target design it is permanent and publicly readable (frozen claim until reconciliation complete).

Day 60: Sunset

• The heartbeat emits its final consensus round.
• All Hedera topics associated with the DAV are marked CLOSED.
• The DAV's entry in the Phylogenetic Tree transitions from ACTIVE to EXTINCT.
• The process is complete. The organism is dead.

The SporePool

Failed genotypes are not wasted. They are preserved.

The SporePool is a public registry of dissolved DAVs, indexed by:

• Trigger type (which failure mode killed it)
• Genotype (Vision, niche, archetype)
• P-score trajectory (the full history, not just the final value)
• Organ-level diagnostics (which organ's P-score was the Liebig minimum)
• Metabolic records (where the loop stalled)

Any entity contemplating genesis can query the SporePool to learn what has already been tried and why it failed. Evolution requires death not because death is good, but because death produces information that life cannot.

Cannot Be Gamed

• In the target design, no wallet can pause the 60-day clock once initiated.
• No governance vote can override a constitutional violation (M5).
• The Foundation has no special authority over dissolution.
• A wallet holding 100% of LP-100 does not alter the dissolution sequence or its typed authority requirements.

Dissolution is the one process in the system that has zero discretionary surface. It is as mechanical as gravity.

Related

• 70-genesis -- how DAVs are born
• 71-metabolic-loop -- the loop whose failure triggers M1
• 74-sovereignty-trigger -- the opposite of dissolution

---

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/73-dissolution.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.