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

C4 -- Building DAVs

Spawn, fork, merge. Digital organisms with constitutional DNA.

Current reading boundary — 2026-09-27

In the current website glossary, DAV means Distributed Augmented Valuechain: a venture structure where AI prepares work and people retain consequential authority. A DAC is a registered company, not a status created by a software API. See the company loop and build status.

The earlier autonomous-company definition, genesis API, ZAI staking example and invariant claims below are historical design proposals. They do not establish incorporation, a running creation API, immutable software behaviour or a current staking requirement.

Historical DAV genesis design — preserved, not a current implementation

What Is a DAV?

A Decentralized Autonomous Company is a digital organism -- a self-contained agent with its own genome, stake, and niche. It operates autonomously within constitutional constraints burned in at genesis. It cannot be reprogrammed to violate its invariants any more than a cell can rewrite its DNA at runtime.

The DACGenesis Interface

Three functions. That is the entire creation API.

spawn(niche, genome, stake)

Create a new DAV from scratch.

dav = DACGenesis.spawn(
    niche="solar-panel-logistics-SEA",
    genome={
        "varna": "Vaishya",           # Trophic level: producer
        "sector": "Industrials",       # GICS classification
        "geography": "Southeast Asia",
        "invariants": K_INVARIANTS,    # K0-K9, non-negotiable
        "phi_split": [0.618, 0.382],  # LP-100 vs operations
        "max_leverage": 1.0,           # No leverage by default
    },
    stake=1000  # ZAI staked at genesis
)

fork(parent, mutations)

Create a DAV by copying an existing one with modifications.

child = DACGenesis.fork(
    parent=solar_logistics_dac,
    mutations={
        "geography": "South Asia",     # New territory
        "phi_split": [0.618, 0.382],  # Constitutional, non-negotiable
        # invariants CANNOT be mutated -- they are constitutional
    }
)

merge(parent1, parent2, recombination)

Combine two DAVs into a new hybrid.

hybrid = DACGenesis.merge(
    parent1=solar_logistics_sea,
    parent2=battery_recycling_sea,
    recombination={
        "niche": "solar-lifecycle-SEA",
        "take_from_p1": ["logistics_model", "supplier_network"],
        "take_from_p2": ["recycling_pipeline", "material_scoring"],
        # invariants from BOTH parents must be satisfied
    }
)

Three Archetypes

Every DAV is one of three constitutional archetypes (immutable after genesis, per K9):

Archetype	L4 Multiplier	Function	Example
PPO	1.0x	On-chain only	AMM, prediction market, oracle
Physical DAV	1.5x	Supply chain ops	Logistics, agriculture, manufacturing
Software Organism	1.2x	Server/CDN only	SPECTRE node, AI inference, CDN

See 66-archetypes.md for full archetype definitions.

Constitutional Invariants

At genesis, every DAV inherits K0-K9. These cannot be changed or forked away:

• K0: No Receipt, No Reality
• K1: Total ZAI = 100 (conservation)
• Mortal authority: a Natural Person authorizes their own typed private act. Public-DAV 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 the exact consequence. PRISM records and verifies only; AI/caste seats stage unsigned proposals, and deterministic software carries out only that exact bound consequence.
• K3-K9: Extraction limits, privacy, transparency, dispute resolution, Grace Exit

The invariants are physics, not policies. A DAV that violates K0 is broken, not rogue. The immune system detects and quarantines it.

DAV Lifecycle

GENESIS -> LARVAL -> ACTIVE -> DORMANT -> GRACE EXIT

At any point, the owner can invoke Grace Exit. Stake returned, genome archived.

Specialist Agent Matching

Niche tags ("Kshatriya . Operations . Financials . SEA") route each DAV to specialized AI agents in APU. The phylogenetic tree classifies; the agent system specializes.

See Also

• 33 APU -- the Council that governs DAV decisions
• 43 Immune System -- how rogue DAVs are handled
• 51 ZAI -- the stake currency

---

DAV Launch Readiness Gates

Spawning a DAV should be a gated process with explicit pass/fail checks.

Gate A — Constitutional Fit

• Mapped to invariants and no explicit contradictions
• Entity boundaries declared (commons/ops/regulatory as needed)

Gate B — Technical Continuity

• Required adapters exist for the pipeline
• Receipt path and status reporting path are defined

Gate C — Economic Coherence

• Revenue and risk loops are explicit
• Exit and dissolution paths are pre-defined

Gate D — Operational Ownership

• Named owner for each critical function
• Escalation and incident roles assigned

If any gate is unresolved, treat launch as simulation, not production.

---