Local-first project intelligence

CyberPM

Project management should be an auditable state machine, not a ritual of duplicated clicks and optimistic dashboards.

PythonFastAPIJinjaSQLiteGitGitHub CLIsystemd --userVanilla JavaScript
Status
Six-phase implementation complete
Code
CPM-07
Domain
Local-first project intelligence
Owner
Pomegranate Interactive
CyberPM operational dashboard interface visualization
Operational interface visualization derived from the implemented dashboard architecture. It is a presentation study, not a literal live capture.

A deterministic local command layer that observes repositories, imports GitHub Project state, reconciles drift and preserves human-authored decisions.

6Implemented phases
168Offline tests
0LLMs in decision core

Mission profile

  • Discover and inspect local Git repositories without surrendering operational control to a cloud service.
  • Capture complete GitHub Project snapshots and expose meaningful state drift.
  • Group commits into deterministic work units rather than fabricating one issue per commit.
  • Reconcile desired and live project state while preserving human-authored overrides.
  • Run safely in dry-run, shadow and AFK daemon modes with backups and explicit policy tiers.

Architecture

An operational memory, not another dashboard

CyberPM was built because repository state, GitHub planning and actual work inevitably diverge. It consolidates those realities without inventing decorative health scores or pretending that every commit deserves its own bureaucratic monument.

Manual changes are sacred

The reconciliation engine distinguishes values CyberPM verified writing from values most likely authored by a human. Unattributed divergence is preserved, classified and carried forward instead of silently overwritten. The first three reconcile runs remain forced dry-runs, and unattended live mutation stays disabled unless a project explicitly opts in.

Verified boundaries

The six phases are implemented and covered by 168 offline tests. Local scans, snapshots, dashboard routes, daemon locking and real dry-runs were exercised against the Pomegranate environment. Live production mutation was deliberately verified against a fake GitHub server rather than imposed on real project data merely to create a triumphant screenshot.