Canonical Architecture — v1.1.0

System Architecture & Pipeline

DevMemory AI v1.1.0 is built on a single Runtime orchestrator. Learn how file changes move from Watcher to Engineering Compiler to SQLite Index.

Watcher (Chokidar)

Observes filesystem events without altering code

Transaction Manager

Groups edits with adaptive cooldown (default 20000ms)

Engineering Compiler

Sole writer of Engineering Memory & AST symbols

SQLite Index

Single source of truth (.devmemory/index.db)

Embedded Dashboard

Renders UI on port 31415 via Runtime API

CLI & Agents

Queries memory via dmai ask and dmai summary

Local-First Architecture Rules

DevMemory AI v1.1.0 operates completely offline. No cloud dependencies, no remote telemetries, no data leaving your machine.

ONE Runtime orchestrator — central management

ONE Engineering Compiler — sole writer of Engineering Memory

ONE SQLite Index — .devmemory/index.db single source of truth

ONE query engine — powering dmai ask & dashboard

Transaction & Build Lifecycle

Instead of building on every keystroke, file save events are grouped into transactions with adaptive cooldown timers.

File Saves → Chokidar Watcher → Transaction (Cooldown)

Transaction Closed → Engineering Compiler AST Scan

Write Build #N to SQLite Index (.devmemory/index.db)

System Component Boundaries

Watcher (Chokidar)  → Observes filesystem changes (No Writes)
       ↓
Transaction Manager → Groups file events with adaptive cooldown (No Writes)
       ↓
Engineering Compiler→ Sole writer of Engineering Memory (AST extraction)
       ↓
SQLite Database     → .devmemory/index.db (Nodes, Edges, Builds, Prompts)
       ↓
Runtime API Engine  → Serves CLI (dmai ask) & Embedded Dashboard (:31415)