F1 -- Disambiguation
Status: pre-launch. This page describes target design; this document does not establish a deployed service.
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: historical ACT/execution label in the pipeline; deterministic execution requires its applicable exact external authorization and never creates authority
- Brand/ecosystem label: umbrella narrative for organism outputs
- Web property: domain-level product surface
Rule: Always specify layer when ambiguity affects decisions.
2) "Nexus" (capability vs concept)
- Agentz capability/API layer: intended purpose-scoped connections and existing compatibility coordinates; a name in source does not prove a deployed service
- Conceptual bridge: personhood/identity coupling boundary
Rule: Name the exact Nexus interface or connection contract. Do not call Nexus an independent shipped product; its current product home is Agentz.
3) "Menexus" (product vs legal/source name)
- Current product: proposed ensurance, insurance and assurance
Menexus-GmbH/menexus-core: legal/repository and historical case-carrier names; local case-retention receipts do not establish coverage
Rule: Name the product only for protection or assurance claims. Preserve historical wire IDs and receipt attribution without reassigning their owner.
4) "APU" and "Agentz" (interface vs Cloud Computer)
- APU: voice/text interaction, navigation and presentation of permitted views
- Agentz: specialist work, Cortex memory, Nexus connections and intended redundant storage; its decisions remain unsigned proposals
Rule: A screen presenting a case does not own the durable memory or gain authority to act. See The Product Family.
5) "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.
6) "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.
7) "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:
- Declare scope (math / protocol / product / legal / narrative)
- Add one-sentence canonical definition
- Provide one “do-not-confuse-with” sentence
- Link to source pages