Project · 02 · Rust · Tauri · MCP · MMXXVIIn progress

Aentic Kronos.

Time-modeling subsystem for the Aentic stack — Rust core, Tauri shell, MCP for the model, capability tokens for everything else. The human UI is the audit console; the LLM runs the day.

Agentic systems don't need a face. They need a ledger.

In brief

Aentic Kronos is a calendar and scheduling subsystem designed to be driven mainly by a local LLM. Agents and pipelines submit proposals through MCP, JSON-RPC or REST tools; a person reviews each one in an Approval Inbox and approves or rejects it before it is committed. It is built with a Rust engine (SQLite, RRULE recurrence, event journal) inside a Tauri 2 desktop app with a React/TypeScript interface.

Month view with mini-calendar, calendars sidebar and view tabs
Month view with mini-calendar, calendars sidebar and view tabs
Approval Inbox, where AI and pipeline proposals wait for human review (empty state)
Approval Inbox, where AI and pipeline proposals wait for human review (empty state)
Year view: twelve-month activity heatmap with drill-down
Year view: twelve-month activity heatmap with drill-down

Specification

Runs as
aentic-kronos.exe (Tauri app, full UI, Axum REST, system tray) · kronos-svc.exe (headless sidecar)
Transports
Tauri IPC · HTTP REST :7701 · JSON-RPC named pipe · MCP stdio
Storage
SQLite, WAL, FTS5 — kronos-v2.db; event-sourced journal, proposals, capability tokens
Actors
ai (proposes only) · pipeline · human (full)
Version
1.0.0 · last commit 2026-05-13
Source
Private

From the README

Time-modeling subsystem for the Aentic ecosystem. Calendar, scheduling, and time-bound work — designed to be driven primarily by a local LLM, with the desktop UI as the audit console.

Built on

Rust 2021 · Tauri 2 · rusqlite + r2d2 · Axum · rrule 0.12 · chrono-tz · schemars · tracing. React 19 · Vite · TypeScript · Zustand · Framer Motion · Tailwind 3 (v4 migration deferred) · Radix UI primitives (via shadcn) · class-variance-authority · lucide-react.

Open seams

Open seams (clearly marked in ARCHITECTURE.md § 10):

  • UKLG Python kronos_client package (lifecycle owner + typed methods).
  • Mobile transport.
  • Small-LLM eval harness.
  • Provenance badges in the calendar grid (the inbox already differentiates).
  • HTTP REST route for proposals.commit (today, commit is Tauri-only; the LLM tool surface uses proposals.commit via MCP / JSON-RPC).