Skip to content

aideon-ai/aideon-desktop

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

364 Commits
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 

Aideon

Aideon

Aideon is a desktop-first, local-first, time-first digital-twin application, built with Tauri v2 (Rust core) and Next.js (React renderer). It separates meaning, storage, and runtime so the UI stays stable while the engines evolve behind typed boundaries.

What makes it different

  • Time-first facts — valid time + asserted time, Plan/Actual layers, scenario overlays.
  • Workspace is canonical — the portable workspace folder (append-only ops + schema-as-data
    • content-addressed blobs) is the source of truth; the runtime database is a derived, rebuildable cache.
  • Artefact-driven UX — views, catalogues, matrices, maps, reports, and pages, executed at an explicit time and scenario.
  • Host is the security boundary — the renderer is untrusted; all side effects flow through typed Tauri IPC. No renderer filesystem access, no local HTTP server.

Quickstart

pnpm install
pnpm tauri dev      # run the app (starts the Next dev server, then the Tauri shell)
pnpm tauri build    # build a distributable

Frontend-only and Rust-only workflows:

pnpm dev            # Next dev server on :1420
pnpm build          # static export to ./out
pnpm typecheck      # tsc --noEmit
pnpm test           # vitest
pnpm run host:check # cargo check (Rust workspace)
pnpm run host:test  # cargo test

Project structure

.
├── app/            # Next.js routes (App Router)
├── src/            # renderer source — design system, workspaces, adapters, DTOs
├── public/         # static assets (brand logos; fonts are self-hosted via @fontsource)
├── src-tauri/      # Tauri host crate — IPC, capabilities, window/jobs, tauri.conf.json
├── crates/         # Rust engine crates (Cargo workspace members)
├── docs/           # numbered documentation tree (see below)
└── tests/          # unit (vitest) + e2e / webdriver

The Tauri CLI runs zero-config from the repo root: src-tauri/ is the default crate location, and the frontend is wired through frontendDist / devUrl / beforeDevCommand in src-tauri/tauri.conf.json.

Modules

Module Path Responsibility
Renderer app/, src/ React renderer, design system, workspace surfaces, IPC adapters, DTOs.
Host src-tauri/ Tauri runtime, IPC, capabilities, jobs, workspace lifecycle.
Praxis crates/praxis Metamodel, task APIs, artefact execution, integrity, analytics orchestration.
Mneme crates/mneme, crates/mneme_core, crates/mneme_store Op log, bi-temporal facts, schema-as-data, projections, embedded store.
Metis crates/metis Analytics algorithms and ranking jobs.
Chrona crates/chrona Time/scenario interpretation and temporal UX primitives.
Continuum crates/continuum Orchestration, scheduling, connectors (local durable executor).

Tauri is confined to src-tauri/; the engine crates are host-agnostic and depend only on each other and shared contracts (src-tauri → crates/*, one direction).

Documentation

Docs use a numbered tree — start at docs/00-index/README.md.

See docs/02-standards/GETTING-STARTED.md for setup and CONTRIBUTING.md for contribution guidelines.

About

The temporal enterprise twin platform that turns design insight into action.

Resources

License

Code of conduct

Contributing

Security policy

Stars

Watchers

Forks

Packages

 
 
 

Contributors