DAV Genesis

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

Current reading — 2026-09-27

DAV means Distributed Augmented Valuechain; DAC refers to a constituted legal-company context. The retained recipe proves neither incorporation, issuance nor deployment. Instrument identity, supply/denominator, rights, entity form and activation gates remain separately owned decisions. Constitution or membership adoption does not authorize deployment. [I]

This reader boundary does not migrate interfaces, choose unresolved terms or prove deployment. See current status.

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.

A proposed DAV configuration and activation lifecycle; it does not itself constitute a legal DAC.

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 the signer(s) required by applicable law, the entity's governing instrument, or a valid competent mandate 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.

Historical genesis and activation recipe — unresolved research, not current implementation

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, the signer(s) required by applicable law, the entity's governing instrument, or a valid competent mandate 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.
• the signer(s) required by applicable law, the entity's governing instrument, or a valid competent mandate 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 the signer(s), threshold, and procedure required by applicable law, the DAV's governing instrument, or a valid competent mandate govern public-DAV genesis adoption. 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.

---

Related pages

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

---

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

Predecessor passage 1

How a Decentralized Autonomous Company is born.