DAV Genesis

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.

This page describes the target genesis architecture for DAV birth. Read deployment, activation, and reproduction-threshold language below as target design unless a narrower runtime proof has explicitly closed the lane.

How a Decentralized Autonomous Company is born.

Overview

Genesis is the target state of a new DAV on Hedera. It is not incorporation -- it is fertilization. Pre-genesis editors may stage an unsigned genome proposal (Vision, niche, archetype). Constitution or membership adoption establishes those terms only and does not authorize deployment. A founder or owner acting alone cannot adopt or deploy it; AI and rails stage unsigned proposals only. Any deployment consequence requires a complete valid bound PRISM decision receipt from at least two natural-person councilors binding that exact deployment; PRISM records and verifies only, and deterministic software carries out only that exact bound consequence. The intended result is an entity with constitutional constraints baked into the ledger from block zero.

What Gets Deployed

In the target design, DACGenesis.deploy() produces four artifacts in a single atomic transaction:

Artifact	Purpose
100 LP-100 tokens	Conservation-law shares. Total supply is immutable (K1).
4 organ scaffolds	Circle (IS), RealityFutures (COULD), Agentz (SHOULD), Skyzai execution. Each scaffold is a Hedera topic + token association awaiting operator activation.
Constitutional invariants	K0-K9 encoded as immutable contract state. No subsequent transaction can violate them.
Genesis allocation	LP-100 distribution defined in the adopted quorum decision receipt. Remaining float enters the Distillation schedule.

Quorum-Adopted Genesis Declaration

Constitution or membership adoption establishes the following three parameters but does not authorize deploy(). Before deploy() executes, at least two natural-person councilors must bind that exact deployment consequence in a complete valid bound PRISM decision receipt, which PRISM records and verifies only:

1. Vision -- a UTF-8 string (max 1024 bytes) stored in the DAV's root topic. Immutable after genesis.
2. Niche -- the trophic-level tag from the Phylogenetic Tree (e.g., Kshatriya.Operations.Financials.SEA).
3. Archetype -- one of three constitutional archetypes (PPO, Physical DAV, or Software Organism) that determines the organism's risk profile and L4 multiplier.

These three values become the DAV's genotype. They cannot be amended -- only expressed differently as the phenotype evolves.

Agent-Staged Genesis Proposal

In the target design, an AI agent with a P-score >= 0.50 may stage an unsigned genesis proposal. It may not invoke DACGenesis.deploy() autonomously. Constraints:

• The agent must have accumulated sufficient P-score across at least 30 days of continuous operation.
• At least two natural-person councilors must adopt the proposal; adoption does not authorize deployment.
• If no complete valid bound PRISM decision receipt binds the exact deployment consequence before the receipt window expires, behavior remains fail-closed and the agent's cooldown resets to 90 days. PRISM records and verifies only.
• A deterministic executor may deploy only that exact bound consequence after validating the complete receipt. The staging agent is neither signer nor owner.

This target keeps proposal origination open while keeping consequence typed: machine-verifiable coherence and viability may inform the proposal, but natural persons adopt public-DAV genesis by quorum. No singleton or species claim substitutes for that authority receipt.

Post-Genesis State

After a successful genesis in the target design:

• The DAV's heartbeat (SA node) begins emitting 10-second consensus rounds.
• All four organ scaffolds are in DORMANT state, awaiting their first operator registration.
• The Metabolic Loop (see 71-metabolic-loop) is paused until at least one organ reaches ACTIVE.
• The DAV appears in the global Phylogenetic Tree and begins accruing P-score history.

Reproduction Threshold

A DAV cannot reproduce (see 72-dac-mating) in the target design until it achieves:

• P > 0.70 (requiring Phi >= 0.85 AND V >= 0.83)
• Minimum 180 days of continuous heartbeat
• At least two organs in ACTIVE state

Genesis creates one organism. Only proven organisms earn the right to create the next.

---

Implementation Notes

• This page is maintained as part of the Skyzai wiki extraction pass.
• Claims should remain aligned with canonical source files and evidence tiers.
• Operational use should distinguish between constitutional invariants and derived heuristics.

Validation Checks

1. Definitions are internally consistent with adjacent sections.
2. Any quantitative claim is paired with context and measurement window.
3. Cross-links to related pages remain valid after edits.
4. Status-oriented language reflects current verifiable state.

Related pages

• SUMMARY.md
• D3-status.md
• C5-uplink.md

---

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/70-genesis.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.

Genesis is the target act of deploying a new DAV onto Hedera after adoption by at least two natural-person PRISM councilors. It is not incorporation -- it is fertilization. Pre-genesis editors may stage an unsigned genome proposal (Vision, niche, archetype). A founder cannot adopt or deploy it alone. An owner, AI, or rail cannot adopt or deploy it alone. The intended result is an entity with constitutional constraints baked into the ledger from block zero.

Before deploy() executes, at least two natural-person PRISM councilors must adopt three parameters in a valid genesis decision receipt:

• The agent must have accumulated sufficient P-score across at least 30 days of continuous operation.
• At least two natural-person PRISM councilors must adopt the proposal before any deployment transaction exists.
• If the quorum window expires without a valid decision receipt, behavior remains fail-closed and the agent's cooldown resets to 90 days.
• A deterministic executor may deploy only after validating that receipt. The staging agent is neither signer nor owner.