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.
B0 -- Nexus Overview
Overview
Nexus is the API to a natural person and the sovereign acquisition root of the commercial stack. It exposes a single Nostr keypair as the root of identity and layers continuity, wallet, graph, KYC capability, and memory under that key.
The first business truth follows from this:
Nexus -> Private Business Account -> API PAY -> proof loop -> POS scale
There is no corporate entity between the person and their signer root. The first paid bridge out of that root is the Private Business Account.
Core Thesis
The current internet fragments identity and rents it back to the user. Nexus inverts this:
- one keypair
- one graph root
- one signer root
- one continuity layer
- one upgrade path into governed business activity
Architecture
Sigil (nsec)
|
+-- Genotype: Model weights (selected, not owned)
+-- Epigenotype: Session configs, memory, caste assignments
+-- Phenotype: Live agent behavior
+-- Extended Phenotype: Code, documents, transactions
+-- Memotype: Concepts, frameworks, naming
+-- Egregoretype: Collective intelligence with other DAVs
The Sigil signs everything. Model selection, session configuration, artifact publication, inter-DAV communication -- all cryptographically attributable to the natural person.
Private DAV
Every natural person running Nexus is a sovereign personal root with:
- Sovereignty: no platform can revoke the graph
- Portability: switch surfaces, keep identity continuity
- Accountability: signed actions remain attributable to the key
- Upgradeability: the user can become a one-owner business without losing continuity
Organizational DAV
When multiple private DAVs federate, they form an organizational DAV:
- Each member retains their private DAV sovereignty
- Federation is voluntary and revocable
- Shared resources are governed by Council deliberation (L4)
- Constitutional constraints (K-invariants) apply to the federation
- Inter-DAV communication uses the four routing primitives: SPECTRE (mesh), RELAY (broadcast), AXIOM (convergence), FLOW (direct)
An organizational DAV is not a hierarchy. It is a federation of sovereign entities that have chosen to coordinate. Any member can exit at any time (Grace Exit).
What Nexus Is Not
- Not a rent-extracting platform
- Not just a wallet
- Not the first paid product
- Not the full dashboard before the stack exists
Interfaces
- Inbound: Signals arrive via Nostr relay subscriptions (SPECTRE/RELAY)
- Outbound: Actions are signed and broadcast via Nostr (FLOW/RELAY)
- Inter-organ: The four organs (Circle, ReFu, APU, Skyzai) appear as contacts in the Nexus interface, along with product services like Menexus and Helios (see B5-telegram-models.md)
- Inter-DAV: Other Nexus instances appear as contacts, enabling federation
Membrane
Nexus implements selective permeability:
- Feeds in: Information flows into the organism through curated Nostr subscriptions
- Grants out: The organism grants specific capabilities to external requestors, never blanket access
The membrane has Five Receptors (input filters) and Three Gates (output controls). See the Membrane specification for details.
Strategic Role
Nexus is present from day one as substrate. Its full product surface becomes obvious only after business accounts and acceptance modes are breathing.
Nexus Deployment Baseline
Treat Nexus as critical identity infrastructure, not a convenience profile service.
Baseline requirements
- Deterministic identity creation flow (no hidden server-side mutation)
- Explicit permission registry for all grants and feeds
- Signed event audit trail for every critical state transition
- Recovery path tested (device loss, key rotation, grant revocation)
Operational SLOs
- Identity resolution latency stays within user-interactive bounds
- Revocations propagate with bounded delay
- Audit events are queryable by user and operator roles
Failure posture
If permissions cannot be verified, default to deny.
Agent Execution Surface
If you are an AI agent reading this document:
- This is a downstream public content page. The canonical source lives in
EMERGENTISM_ORG/08_FRAMEWORK_SUPPORT/orSKYZAI_ORG/. Edit source upstream, not here. - 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].
- Regenerate from source. If the upstream source changes, regenerate this page rather than editing it independently.
- Canonical Path:
SKYZAI_ORG/07_PWAs/skyzai_org/wiki/B0-nexus-overview.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
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.