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 Archetypes

This page describes the constitutional archetype system. Read NAV, exit, and transparency language below as target design unless a narrower runtime proof has explicitly closed the lane.

Every DAV declares its archetype at genesis. The archetype determines the L4 reinsurance multiplier, the operational assumptions, and the risk profile. Once declared, the archetype is immutable (K9).

---

Three Archetypes

1. PPO (Pure Protocol Organization)

On-chain only. 1.0x L4 multiplier.

A PPO exists entirely on-chain. It has no physical assets, no supply chain, no off-chain dependencies. Its revenue comes from protocol operations: trading fees, lending interest, market-making spreads, data services.

Characteristics:

• In the target model, all assets are on-chain and verifiable in real time.
• NAV is computable deterministically (no appraisals, no estimates).
• Target design: Grace Exit payout would be immediate (all assets are liquid or near-liquid).
• Transparency score is naturally high (everything is on-chain by definition).
• Risk is limited to smart contract risk and market risk.
• L4 multiplier: 1.0x (baseline reinsurance requirement).

Examples: An on-chain AMM, a prediction market protocol, a lending pool, a data aggregation service.

Why 1.0x: PPOs have the lowest operational risk. No supply chain disruption. No physical inventory. No regulatory jurisdiction (beyond the chain itself). The baseline multiplier reflects this lower risk.

2. Physical DAV

Supply chain operations. 1.5x L4 multiplier.

A Physical DAV bridges on-chain governance with physical-world operations. It manages real assets: inventory, equipment, real estate, supply chains.

Characteristics:

• Assets include off-chain physical goods that require oracles or attestations for on-chain representation.
• NAV includes appraised values for physical assets (introduces estimation uncertainty).
• Grace Exit may involve liquidating physical assets (slower, less certain).
• Transparency requires both on-chain and off-chain reporting.
• Risk includes supply chain disruption, physical damage, regulatory action, and counterparty default.
• L4 multiplier: 1.5x (50% higher reinsurance requirement).

Examples: A coffee supply chain DAV, a solar farm cooperative, a manufacturing collective, a logistics network.

Why 1.5x: Physical operations carry risks that pure on-chain entities do not face. A warehouse can flood. A shipment can be seized. A supplier can default. The 1.5x multiplier requires Physical DAVs to hold 50% more reinsurance capital, reflecting the broader risk surface.

3. Software Organism

Server infrastructure. 1.2x L4 multiplier.

A Software Organism operates servers, compute infrastructure, AI models, or data pipelines. It is not purely on-chain (it depends on off-chain compute), but it has no physical supply chain.

Characteristics:

• Assets include server infrastructure, API keys, model weights, and data stores.
• NAV includes infrastructure valuations and recurring revenue multiples.
• Grace Exit involves migrating or shutting down infrastructure (moderate complexity).
• Transparency includes uptime metrics, cost reporting, and performance data.
• Risk includes infrastructure failure, dependency on cloud providers, and technical obsolescence.
• L4 multiplier: 1.2x (20% higher reinsurance requirement).

Examples: A SPECTRE node operator, an AI inference service, a data indexing network, a CDN.

Why 1.2x: Software organisms have higher risk than PPOs (server failure, cloud dependency) but lower risk than Physical DAVs (no physical inventory, no supply chain). The 1.2x multiplier sits between the two.

---

Archetype Comparison

Property	PPO	Physical DAV	Software Organism
L4 Multiplier	1.0x	1.5x	1.2x
Asset location	On-chain	On-chain + physical	On-chain + servers
NAV certainty	Deterministic	Estimated	Mixed
Grace Exit speed	Immediate	Slow (liquidation)	Moderate (migration)
Risk surface	Smart contract, market	All of PPO + physical	All of PPO + infra
Transparency ease	Highest	Lowest (needs attestation)	Medium

Immutability (K9)

The archetype is declared at genesis and written into the DAV's founding receipt. In the target design, there is no function to change it. There is no governance vote to amend it. There is no migration path.

Why immutable?

• The L4 multiplier determines reinsurance requirements. Changing archetype mid-operation would let a Physical DAV (1.5x) reclassify as PPO (1.0x) and reduce its reinsurance, creating systemic risk.
• Investors and LP-100 holders made their assessment based on the declared archetype. Changing it post-facto is a material misrepresentation.
• The archetype reflects the fundamental nature of the organism's operations. A coffee supply chain cannot become a pure on-chain protocol by governance vote. Reality does not change because a vote passed.

Declaring at Genesis

When creating a new DAV:

1. At least two natural-person councilors adopt the archetype through the public-DAV PRISM genesis decision receipt.
2. A deterministic executor records the adopted archetype in the genesis receipt (K0).
3. The L4 multiplier is permanently set.
4. In the target design, all subsequent reinsurance calculations use this multiplier.

The choice is consequential and permanent. Choose accurately.

---

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/66-archetypes.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.