Product family · in development
Menexus
Three named products for connection, machine-oriented memory and human-facing conversation: Nexus, Cortex and the new Menexus AIA. Their boundaries are specified here; this page does not claim a live integrated service.
Nexus · connections and permissions
Nexus manages relationships, permissioned context and scoped disclosure. A connection is not blanket access; permission to read context is not authority to act, sign or move value.
identity + connection → purpose-bound grant → scoped context
Cortex · memory built for machine intelligence
Cortex is the machine-intelligence memory product: source-bound records, revisions and history are the durable base; derived relationships and retrieval should make that knowledge more useful over time. It is not merely a folder tree, and no vector database or model has yet been selected.
The architecture candidate is hybrid: canonical source/provenance records plus rebuildable typed links and semantic/vector indexes; retrieval and workflow policies may improve from separately evaluated outcomes. Indexing does not make a source true, grant permission or erase the source owner's control. Nexus governs what context may be disclosed to a particular purpose.
source-owned record → provenance + revisions → scoped graph/vector retrieval → evaluated adaptation
Inspect the Cortex memory contract · View the Cortex brand guide
Menexus AIA · the new voice and text interface
The new Menexus AIA is the human-facing conversation interface, designed for voice and text access to permitted context. Its intended interaction is conversational; it does not inherit unlimited permission from the person it represents and cannot authorize consequential actions.
This is a new product identity. The retired former name that became apu.bot is not the new Menexus AIA, whose membership in Menexus is settled; its placement in the applied-level/runtime map and integration details remain under design. Voice service availability is not claimed.
person ↔ new Menexus AIA ↔ Nexus-scoped context ↔ Cortex records
A family, not a collapsed role
Nexus controls connection and disclosure boundaries. Cortex organizes and retrieves durable machine-oriented memory. Menexus AIA provides the human-facing voice and text interface. These are named subproducts of Menexus, not synonyms for one another.
apu.bot is separate: its role is to order and defend intake and support bounded reasoning. Agentz is a connected ecosystem product for proposals. Neither product's name or role is transferred into Menexus by integration.
Scoped, time-aware views
Skyzai is exploring read views that let people move from an overview into inspectable sources, changes, uncertainty and disagreement. A view is a projection over owner-controlled records—not a second source of truth, universal digital twin, public copy of private data, or command surface.
Observed claims, possible futures, unsigned proposals, recorded effects and independently evaluated outcomes must remain distinct. Missing data stays unknown. This is an architecture proposal, not an integrated feature.
Availability and boundaries
Menexus and its subproducts are in development. This website is an explanatory design surface; it does not provide live Menexus AIA voice chat, persistent Cortex storage, Nexus account management or an operational connected runtime. Product capability, data handling and deployment must be verified separately before any availability claim.