Ian Provencher
Listen to the podcast

Command Center · the ops console

The console I run everything from

The console is the bridge; Claude Code is the engine room.

A local-first operations console where the UI and the AI work the same files. It has grown to a dozen-plus modules — projects, a task board, agent assignments with live headless dispatch, tools, architectures, a sanitized vault graph, an ops log, and a real-time "Bridge" of gauges — the source that several sections of this very site are exported from. It installs as a PWA on the desktop and rides in a native app on my phone.

Local-first

No database — the truth is plain JSON files, one per record. Anything that can read files can read (and audit) the whole operation.

Live

A file watcher pushes changes to the browser over SSE. The screen moves the instant either the UI or an agent touches anything.

Self-briefing

A nightly headless agent sweeps every source and writes the morning briefing before I am awake — current without being tended.

Human-gated

Agents dispatch, claim, and finish work — but only I move it to done. That gate is enforced in code, not convention.

The modules

dashboard — the at-a-glance state of the whole operation
projects — the ventures and builds in motion
task board — the kanban of what moves each forward
assignments — work dispatched to agents — RUN NOW fires a headless agent with a per-assignment model + effort (inbox → active → review → done)
skill library — the house skills, versioned and synced to every AI surface
tool registry — the registry behind the Tools page
architectures — the diagrams behind the Architectures page
goals / horizon — now / this-year / multi-year
learning — what I am actively getting fluent in
knowledge — an index into the vault
briefings — the nightly self-written summaries
brain — a sanitized graph of the vault — 803 notes, 1,871 links
ops log — the running record of what the machinery did
the bridge — live gauges, a module constellation, and real-time SSE readouts

How it ties in here

This public site never connects to the command center live — it's gated and private by design. Instead, a reviewed public-safe snapshot is exported from it: the 32 builds and 10 architectures you can browse here were published through an opt-in gate that strips anything sensitive before it ever reaches the web.

The safe-export pipeline — private infrastructure → reviewed public snapshot