01
HUMAN AUTHORITY
You remain the final authority over every permission, action and decision.
A NEBULLYS PROJECT · N—01
AZTEC
Intelligence, under your authority.
Aztec is a personal intelligence designed to unite natural conversation, lasting memory and everyday assistance within one private, continuous experience.
Explore the system01PRIVACYBY DESIGN
02CONTINUITYOVER TIME
03AUTHORITYREMAINS YOURS
01THE PRINCIPLE
The intelligence
assists.
You decide.
Aztec is designed as a complete AI-powered personal assistant — able to converse naturally, understand context, remember what matters and provide meaningful assistance over time. Through memory and continuity, it can build on past interactions instead of treating every conversation as a new beginning.
But intelligence is not authority. AI models can understand, reason and communicate, but they never decide or act on their own. Actions, permissions, tools and memory remain governed by Aztec's secure architecture — and, ultimately, by you.
02
COGNITION, NOT CONTROL
AI can understand and reason, but it cannot govern.
03
LOCAL FIRST
Personal data remains under your control at all times.
04
LEAST EXPOSURE
Every component receives only what it truly needs to perform its task.
02SYSTEM ARCHITECTURE
Built as a system.
Not a black box.
Aztec separates intelligence, memory, identity and capability into distinct layers — each with a clear purpose and a controlled place in the whole.
MODULE / 01GOVERNANCE
Control remains explicit.
Permissions, actions and decisions follow traceable rules instead of model initiative.
MODULE / 02COGNITIVE INTELLIGENCE
Reasoning without command.
Models can understand and communicate without becoming the system that controls them.
MODULE / 03CHRONOS
Continuity over time.
Structured memory allows useful context to endure without becoming an uncontrolled transcript.
MODULE / 04IDENTITY
Recognition with boundaries.
Identity signals establish who may be present; policy decides what follows.
MODULE / 05VOICE
Voice, expression and presence.
Speech, response and expression form one continuous conversational experience.
MODULE / 06TOOLS & ACTIONS
Capability by permission.
Tools remain separate from intelligence and available only after explicit authorization.
MODULE / 07ZEUS & AGENTS
Delegation with limits.
Zeus coordinates specialized agents through defined roles, limited capabilities and reviewed results.
MODULE / 08INTERFACES
One core, multiple interfaces.
Desktop and mobile interfaces connect to one identity, one memory and one source of authority.
03CONTINUITY
A memory with
structure and purpose.
Chronos distinguishes what happened from what deserves to endure. It organizes meaningful context across time, people and relationships, allowing each conversation to build on the last without reducing a person to a transcript.
01HISTORY
What happened.
02MEMORY
What should endure.
03RELATIONSHIPS
Who and what connect.
04TIME
When context matters.
05PROVENANCE
Where knowledge began.
06RELEVANT RECALL
Only what matters now.
CHRONOS STATUS IN ACTIVE DEVELOPMENT
04IDENTITY & TRUST
Recognition is evidence.
Authority is policy.
Knowing who may be speaking is not the same as deciding what they may do. Aztec keeps identity evidence, roles and permissions deliberately separate.
A detected voice can help resolve a speaker as Admin, User or Unknown. Recognition identifies; policy determines what each role may access.
VOICE RECOGNITION
A signal that can support identification — never an automatic grant of permission.
IDENTITY RESOLUTION
Evidence is compared with known context before an identity is considered.
ROLES
Admin, user and unknown states establish clear differences in access and trust.
PERMISSION POLICY
What someone may request remains separate from who the system believes they are.
TRUST STATESADMINUSERUNKNOWNIDENTITY INFORMS · POLICY GOVERNS
05VOICE & PRESENCE
More than a voice.
A presence.
Aztec listens, understands and responds through one continuous conversational core. Synchronized voice, expression and visible states transform that response into a presence you can perceive.
RESPONSIVE STATELISTENING · THINKING · SPEAKING
LISTEN
Receive speech as an intentional input.
UNDERSTAND
Connect language with context and memory.
RESPOND
Form a useful answer through the shared core.
EXPRESS
Return it through text, voice and presence.
SYNCHRONIZED EXPRESSIONSpeech, translated
Speech, translated
into presence.
Each spoken response is translated into precisely timed visemes, allowing the avatar's mouth movements to remain synchronized with Aztec's voice.
VOICE GENERATION
Aztec transforms its response into speech.
VISEME SYNCHRONIZATION
Speech timing drives the avatar's mouth shapes.
EXPRESSIVE PRESENCE
Eyes, face and behavior reflect Aztec's current state.
06COGNITIVE INDEPENDENCE
The intelligence can change.
Aztec remains.
Aztec is not defined by a single model. Cognitive engines can evolve or be replaced while identity, memory, permissions, tools and the system's governing principles remain continuous.
“Aztec is not an LLM with tools. Aztec is a personal system that can use LLMs.”
CHANGEABLECOGNITIVE ENGINE
CONTINUOUSAZTEC COREIDENTITY · MEMORY · AUTHORITY
AUTHORIZED BY AZTECANSWER · TOOL · ACTION
07PRIVACY & BOUNDARIES
Privacy is an architecture.
Not a setting.
Privacy cannot depend on a single switch. It emerges from where information lives, how systems are separated and how little context each component is allowed to receive.
01
LOCAL FIRST
Personal context is kept close to the system you control whenever possible.
02
PROTECTED STORAGE
Sensitive information belongs within deliberate, protected boundaries.
03
SEPARATED SECRETS
Credentials and private configuration remain isolated from cognitive context.
04
CONTROLLED CONTEXT
Only relevant information is retrieved, and only when it serves the current exchange.
08CONTROLLED DELEGATION
Delegation without
surrender.
Specialization expands what Aztec can accomplish without dissolving responsibility. Aztec receives the request, Zeus coordinates the work and each agent contributes within a clearly defined role.
COORDINATION LAYERZEUSTASK ROUTING · AGENT COORDINATION · RESULT ASSEMBLY
SCOPED ROLES
Each agent is assigned a clearly defined area of responsibility.
LIMITED CAPABILITIES
An agent receives only the capabilities required for its current task.
EXPLICIT PERMISSIONS
Every actionable request passes through authorization and system policy.
REVIEWED OUTPUTS
Zeus returns results to Aztec, where they are evaluated before reaching the user.
09PROTOCOLS & RESILIENCE
Prepared for
what matters.
Critical situations should never depend on improvisation. Aztec is designed around deliberate procedures for recovery, containment, diagnosis and emergency response.
PROTECTED ACTIVATIONADMIN VOICE BIOMETRICSSECRET AUTHENTICATIONSYSTEM POLICY
ABSOLUTE OVERRIDE00
EMERGENCY KILL SWITCH
A final safeguard, always within reach.
A dedicated emergency command can stop Aztec at any moment, regardless of the active task. Activation remains bound to a protected phrase and verified administrator voice.
PROTOCOL CLASS / 01
AUTONOMOUS RECOVERY
Restarts the Aztec runtime through a controlled sequence, then verifies that every required service returns to a known state.
PROTOCOL CLASS / 02
COGNITIVE CONTAINMENT
Places Zeus and every specialized agent offline when abnormal behavior requires immediate separation from cognitive activity.
PROTOCOL CLASS / 03
INTEGRITY VERIFICATION
Performs an extended security inspection for signs of intrusion, alteration, unauthorized copying or host compromise.
PROTOCOL CLASS / 04
SYSTEM LOCKDOWN
When a compromise is confirmed, protected assets can be rendered inaccessible, Aztec disabled and the host isolated from every network.
PROTOCOL CLASS / 05
DIAGNOSTIC & RESTORATION
Audits the complete installation, reports affected components and supports a controlled path toward repair and restart.
PROTOCOL CLASS / 06
EMERGENCY ASSISTANCE
A mobile interface can contact emergency services, relay critical information and share the device location when the user cannot respond.
PROTOCOL CLASS / 07
DEVICE RECOVERY
Authorized devices carrying an Aztec interface can be located through a dedicated recovery path.
10SECURE MOBILE INTERFACE
PLANNED COMPANION SURFACEThe same Aztec.
The same Aztec.
Within reach.
The smartphone application is designed as a secure relay to the Aztec instance running on the user's PC. It does not create a second assistant or move the core to the phone: it carries the interface, conversation and authorized controls to a mobile screen.
CONVERSATIONSYSTEM STATEPROTOCOL ACCESSSECURE RELAY
PRIMARY INSTANCEAZTEC
PC · CORE · MEMORY · AUTHORITYAUTHENTICATED
SECURE RELAY
SECURE RELAY
MOBILE INTERFACEACONNECTED
IDENTITY VERIFIEDENCRYPTED TRANSPORTAUTHORIZED CONTROLS
11DEVELOPMENT
One reliable layer
at a time.
Aztec is being built as a long-term system, with each foundation developed, tested and connected before the next is allowed to depend on it. Current work spans the conversational core, structured continuity, the continued refinement of protocol capabilities and more reliable task dispatch across Zeus and the agent network.
Natural dialogue and reliable local operation.
Chronos, memory and context across time.
Identity, permissions, tools and secure boundaries.
New interfaces and knowledge systems built on stable foundations.
THIS PAGE WILL EVOLVE WITH AZTEC