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.

Skyzai.ORG -- Evidence Tiers

Five rungs, two qualifiers. Every claim is marked. No claim may be presented at a higher tier than its actual status.

Why Tier Discipline Matters

Most whitepapers and technical documents make claims without distinguishing between what they have proven and what they believe. A reader cannot tell whether a statement rests on a written design, a simulated run, a reproducible local receipt, or an independently verified measurement.

Skyzai marks every claim with an evidence tier. This is not stylistic -- it is a constitutional requirement (A7: self-correction). If you cannot label the evidence behind a claim, you do not understand the claim well enough to make it. [D]

Violating tier discipline triggers A7 self-correction. [D]

The Ladder (canonical)

The maturity ladder is strictly ordered: [C] < [D] < [S] < [B] < [E]. A claim earns a rung; it is never granted one.

Rung	Name	Meaning	What it takes
[C]	Conjecture	An idea, a thesis	Stated with reasoning
[D]	Doc / spec	A written, buildable design	The artifact exists and is internally coherent
[S]	Simulated	A mocked/fixture run, or a scaffolded contract	A run/scaffold exists, honestly labeled SIMULATED/scaffold
[B]	Observed	A real local/prototype run with an exported artifact and reproducible steps	A dated receipt plus the generator/steps to reproduce it
[E]	Measured	Independently verified in an authorized/live environment	Third-party or production measurement plus the applicable typed authority and receipt

Cross-cutting qualifiers (not rungs)

• [I] — inferred / architectural reasoning. Marks how a claim is known, not how proven it is.
• [A] — non-permutable structural invariant.

[I] and [A] qualify claims; they never substitute for [B]/[E] on a runtime claim. A design argued from architecture is at most [D] with an [I] qualifier.

Promotion Requirements

No artifact advances a tier without (i) a named, reproducible proof artifact, (ii) the exact run/scope it proves, and (iii) a Proof-steward seal — and the promotion applies only to that specific loop, never to the whole system.

From → To	Required proof	Non-upgrade clause
[C] → [D]	The written spec, coherent, tiers marked	A doc is not a run
[D] → [S]	A mock/fixture run or scaffolded contract, labeled	A sim is not a real event
[S] → [B]	A dated real run + exported artifact + reproducible steps	A receipt proves only its own loop
[B] → [E]	Independent/authorized measurement plus the applicable typed authority receipt	One org's run is not the network

A7 Correction Triggers

Open an A7 correction before proceeding if any surface says or implies, beyond its earned tier: live product · live wallet · live network · live settlement · live SoResFi · live Layer-1 · live 6G · production signing · verified identity · health / financial / legal advice.

Rules

1. Never cite a lower rung as support for a higher one. A conjecture [C] cannot support a spec claim [D]; a spec cannot support an observed-run claim [B]. Evidence flows down, not up.
2. Always mark the tier. Every non-trivial claim in Skyzai documentation carries a tier label. Unmarked claims are treated as [C] by default.
3. Promote and demote actively. When new evidence arrives, re-tier the affected claims. This is A7 in action. Demotion needs no ceremony; promotion needs a receipt.
4. Scope every promotion. A receipt proves only the loop it recorded. A working local run promotes that loop to [B]; it does not promote the system.
5. Conjectures are welcome. The [C] rung is not a mark of shame. It is a mark of honesty. Better to label a speculation as speculation than to present it as proven.

Historical Note

Earlier versions of this page defined a four-tier epistemic alphabet ([E]stablished / [S]tructural / [I]nterpretive / [C]onjecture). That alphabet was merged into the maturity ladder above (02_SKYZAI/TIER_MERGE_GATE.md): the rungs now measure how proven an artifact is, and the epistemic dimensions survive as the [I]/[A] qualifiers. When reading older pages, treat legacy "[E] established math" style labels as claims to re-tier, not as ladder rungs.

Sources

• 02_SKYZAI/TIER_MERGE_GATE.md -- Tier Merge-Gate (canonical ladder, promotion table, A7 triggers)
• EMERGENTISM_ORG/11_UPLINK/02_FRAMEWORK.md -- The Framework (section: "Evidence Tiers", historical)

---

Zero-Sum Resolution Equation

---

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/14-evidence-tiers.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.