Creator of the Jane Project

Simona D. Thrussell, PhD

AI researcher, software and cloud architect, and creator of the Jane Cognitive Architecture.

Founder’s note

Jane began with a systems question.

What would artificial intelligence look like if identity, memory, attention and curiosity were treated as first-class architectural concerns rather than additions to a conversational model?

The Jane Project applies systems architecture to persistent cognition: breaking a difficult problem into coherent layers, defining responsibilities, managing resources and preserving continuity as the system grows.

Current state

Working MVP

Jane has reached a working MVP state with all core ecosystem components connected and functioning together.

  • JaneOS provides the persistent cognitive foundation.
  • Jane Agent coordinates reasoning, planning and execution.
  • Jane Mobile provides capture and mobile interaction.
  • Jane CLI provides the developer and operational interface.
  • NXDOne and worker integrations connect operational execution.
  • Shared identity, memory, observation and orchestration flows are functioning across the ecosystem.

Research focus

Persistent cognitionIdentity and continuity beyond isolated sessions.
Memory economyLarge-capacity memory allocation, compression, promotion and decay.
Edge detectionRecognition of novelty, contradictions, uncertainty and opportunity.
Cognitive schedulingDynamic attention and resource allocation across competing processes.

From research to company

Jane is being built as a product company, not a conceptual exercise.

What exists now

  • A working, connected MVP spanning all principal Jane components.
  • A persistent cognitive core with memory, identity, attention, novelty and reflection concepts implemented across the ecosystem.
  • Product interfaces for mobile, command-line, agent and operational use.
  • A commercial web platform with product pages, lead capture, authentication and administration.
  • A defined path toward SaaS, enterprise licensing, private deployments, APIs and implementation services.

What comes next

  • Hardening the MVP for reliability, security and repeatable deployment.
  • Expanding infrastructure for models, memory, observability and resilient operation.
  • Running structured pilots with early users and business partners.
  • Building marketing, sales and partnership capabilities around the product.
  • Converting the current technical foundation into a scalable commercial platform.