Harmony | Project Memo | Alec Maliwanag

Animated Harmony Operator Cockpit tour moving through the fleet DAG, review packet, preview-first action, and audit ledger on fictional Demo Lab data.

available

Operator Cockpit demo tour

Fictional Demo Lab replay; the interaction pattern is grounded in 900+ private fleet runs.

Bounded claim

The operator layer for AI-assisted engineering — operate the fleet with Harmony, verify its work with NLFR. Public demo data is fictional and credential-free; the interaction pattern is grounded in 900+ private fleet runs spanning business, product, and development work.

RoleFounder / builder

StatusOpen-source operator system; public-safe demo media shipped

Available proof7 / 7

Sourceoperator-recorded

Stack

Launch surface

Repo

Project

Local-first operator system for AI-agent fleets

The operate half of running fleets of coding agents: Fleet, a typed Go control plane (its CLI is named symphony), runs and records agent work, while Operator Cockpit, an Electron/React surface, makes that work visible, reviewable, and controllable — with preview-first actions that keep mutation authority behind Fleet-owned gates.

Problem

Operating context

AI-agent work gets hard to trust when the truth is scattered across chat threads, issues, pull requests, logs, and local databases. One person running a fleet of coding agents needs a single surface that shows what is running, what is blocked, what an action will do before it happens, and what actually happened afterward.

Ownership

What I owned

Designed and built both halves: Fleet, the typed Go control plane that owns scheduling, policy, durable state, and side effects, and Operator Cockpit, the Electron/React surface that owns visibility, review framing, and preview-first control — then extracted them into one public, fixture-safe repo.