Jane remains Jane
Products extend what she can perceive and do. They do not redefine her identity.
The full architecture
Jane is one intelligence.
The ecosystem extends her reach.
Each product has one clear responsibility. No duplicated cognition. No application-specific version of Jane.
Persistent identity
JANE
Autonomous · Flexible · Independent
Cognitive operating system
JaneOS
JaneOS is the independent cognitive foundation of the ecosystem: a persistent runtime for memory economy, attention, curiosity, novelty recognition, reflection and investigations.
Explore → Autonomous intelligenceJane Agent
Jane Agent gives the cognitive core a voice, plans, tools and practical agency. She interprets observations, chooses functions, prepares work and remains supervised where actions carry real consequences.
Explore → Developer interfaceJane CLI
Jane CLI is the focused interface for developers, operators and researchers. It exposes conversation, diagnostics, projects, observations and cognitive services without duplicating intelligence in the client.
Explore → Everyday companionJane Mobile
Jane Mobile brings Jane into daily life through chat, voice, camera, OCR, translation, projects and observations. The phone remains an interface; Jane’s cognition and memory stay in Jane Agent and JaneOS.
Explore → Human-supervised ERPNXDOne
NXDOne combines a Symfony transactional platform with specialist worker services for pricing, sales, warehouse, HR/payroll and customer support. Jane can observe, analyse and prepare actions, while authorised people approve consequential changes.
Explore →Design laws
Cognition stays in JaneOS
Memory, attention, novelty, reflection and investigations belong in the cognitive core.
Interfaces stay thin
Mobile and CLI deliver access. They do not duplicate reasoning or memory.
Systems expose capabilities
Connectors let Jane manage external applications through stable, auditable boundaries.
Humans supervise stakes
Jane may act autonomously in thought and preparation; consequential execution remains controlled.
Boundaries remain explicit
Separate deployments, permissions and memories prevent accidental cross-project leakage.