Status: pre-launch. This page describes target design; this document does not establish a deployed service.
B0 -- Nexus Overview
Current owner boundary — 13 October 2026: Nexus is Agentz's purpose-scoped connection capability, not a separate buyer product or the Menexus insurance/assurance product. It transmits a permitted, provenance-bound view with purpose, expiry, and revocation; it does not expose raw Cortex memory or inherit the principal's authority. APU presents the permitted view. A business account or commerce intent is a separate route, and an economic consequence requires its own OFN receipt after applicable authorization and execution. See The Product Family and Disambiguation.
Historical Nexus personal-acquisition and federation model
The earlier architecture is preserved below as design history. Its standalone product, Menexus-as-context, and automatic upgrade implications are not the current product map.
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 through the actual applicable council or mandate; dispatch L4 is not a council seat and does not confer authority.
- Constitutional constraints (K-invariants) apply to the federation
- Research working patterns FLOW, RELAY, AXIOM and MESH sit over proposed SPECTRE transport; neither pattern nor transport creates authority
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 proposed interface distinguishes Circle IS, RealityFutures COULD, Agentz unsigned SHOULD and exact-bound execution; apu.bot is an independent connected utility, 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.
Historical predecessor wording — retained on 2026-09-27, not active rules
The displaced passages are preserved verbatim for lineage. This retention date is not their original authorship date.
Predecessor passage 1
- Shared resources are governed by Council deliberation (L4)