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.

How to Read This Project

Purpose: This page helps new readers understand what SkyZAI is, how the materials are organized, and how to avoid common misreadings.

Read this as: a guide to the corpus, not as a standalone argument.

See also: 00-claim-status-map, 14-evidence-tiers, 19-kill-criteria, D3-status

SkyZAI is not only a product site, and not only a theory document. It is a layered project spanning:

• doctrine
• formalism
• organizational design
• technical architecture
• public documentation
• implementation work
• narrative framing

Because of that, different pages are doing different jobs.

This public wiki is the L5 mirror of a deeper source stack:

1. Framework (L2) — doctrine, core state, formalism, Rosetta canon
2. Organism (L3) — entities, organs, code, receipts, runtime truth
3. Uplink (L4) — compressed routing and synthesis
4. PWA/wiki (L5) — public explanation and documentation

The shortest possible description

SkyZAI is a proposed coordination stack built on a broader emergentist framework.

At a high level, the project claims that:

• coordination is a central bottleneck in civilization
• better systems require better architectures for truth, flow, relay, and agency
• theory, organization, and implementation must be linked rather than treated separately

The project presents these claims across multiple rows, but public readers usually feel them through three upstream source layers:

1. Foundation — worldview, core state, formalism
2. Organism — institutions, entities, code, and execution structure
3. Uplink — compressed protocol, architecture, and route synthesis

See: 22-three-layers

How not to misread the project

Do not assume that every page is making the same kind of claim.

A page may be:

• explanatory
• formal
• interpretive
• strategic
• organizational
• technical
• implemented
• narrative

These differ in certainty and intended use.

See: 00-claim-status-map

The main distinction to keep in mind

1. Worldview is not the same as implementation

Some pages describe the project’s deepest assumptions about emergence, intelligence, ethics, and coordination. These are not the same as claims about what is currently deployed.

2. Formalism is not the same as empirical proof

Some pages state axioms, equations, or structural relations. These may be formalized without being universally accepted empirical results.

3. Narrative is not the same as mechanism

Some pages use mythic, symbolic, or canonical language to orient meaning. This does not automatically make them implementation docs or proofs.

4. Specification is not the same as deployment

Some pages describe how a system is intended to work. That does not necessarily mean every part is already built.

5. Public wiki is not the same as upstream authority

This wiki is designed to help readers navigate the project. It should not be used to silently overrule upstream framework, organism, or runtime-truth sources.

6. Code-only health is not the same as live public proof

Some maturity statements refer to code readiness, some refer to bounded local proof, and some refer to live deployed/runtime truth. Keep those separate.

Recommended reading tracks

Track A — skeptical external reader

1. 01-introduction
2. 02-the-problem
3. 03-the-solution
4. 22-three-layers
5. 14-evidence-tiers
6. 19-kill-criteria
7. D3-status
8. F0-glossary

Track B — technical builder

1. 22-three-layers
2. 35-api-contracts
3. 40-spectre-overview
4. 46-proof-of-relay
5. 47-merkle-bridge
6. 50-soresfi-overview
7. 84-theory-praxis
8. D3-status

Track C — doctrine reader

1. 13-the-axioms
2. 14-evidence-tiers
3. 15-rosetta-stone
4. 18-phi-resolution
5. 68-canon
6. 70-genesis
7. E1-a-brahmanism

Final rule

If you are unsure how to interpret a page, default to this rule:

Read broad claims as layered until the page explicitly tells you whether it is making an ontological, formal, interpretive, technical, or implementation claim.

---

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/00-how-to-read-this-project.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.