F1 -- Disambiguation

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.

First-pass resolution of common naming collisions.

The Skyzai corpus spans philosophy, protocol design, economics, and operations. This page prevents term collision by anchoring context.

High-frequency collisions

1) "Skyzai" (organ vs brand vs domain)

• Organ: ACT layer in the Three-Stage Process
• Brand/ecosystem label: umbrella narrative for organism outputs
• Web property: domain-level product surface

Rule: Always specify layer when ambiguity affects decisions.

2) "Nexus" (product vs concept)

• Product/API layer: specific implementation surface
• Conceptual bridge: personhood/identity coupling boundary

Rule: Use “Nexus product” for shipped features; “nexus layer” for architecture.

3) "P-score" (metaphor vs KPI)

• Narrative shorthand: directional health signal
• Operational metric: requires explicit formula inputs and time window

Rule: never cite P without φ, ν, and timestamp/window.

4) "eta = 0" (absolute vs asymptotic)

• Constitutional intent: eliminate extractive surplus beyond regeneration
• Operational implementation: progressively approach through system constraints

Rule: avoid simplistic “zero fees” interpretation.

5) "Invariant" vs "derived heuristic"

• Invariant: constitutional/non-negotiable
• Derived heuristic: useful operational pattern, revisable with evidence

Rule: label each claim explicitly as constitutional or derived.

---

Writing protocol

When adding a term that may collide:

1. Declare scope (math / protocol / product / legal / narrative)
2. Add one-sentence canonical definition
3. Provide one “do-not-confuse-with” sentence
4. Link to source pages

Related pages

• F0-glossary.md
• 60-invariants-overview.md
• 35-api-contracts.md

---

Implementation Notes

• This page is maintained as part of the Skyzai wiki extraction pass.
• Claims should remain aligned with canonical source files and evidence tiers.
• Operational use should distinguish between constitutional invariants and derived heuristics.

Validation Checks

1. Definitions are internally consistent with adjacent sections.
2. Any quantitative claim is paired with context and measurement window.
3. Cross-links to related pages remain valid after edits.
4. Status-oriented language reflects current verifiable state.

Related pages

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

---

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/F1-disambiguation.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.