NNoPM

AI-native · governance-grade · lite

Project governance your AI agent can actually operate.

NoPM is a lite, API-first project-management tool — like the aws or supabase CLIs, but for project governance. Your own agent drives it over a documented REST API. Immutable audit, scoped tokens, and four-eyes approval are enforced in the data layer — not bolted onto the UI.

an agent drives NoPM
$ nopm tasks rm task_8f3a --reason "superseded by revised cutover plan"
⏸ delete requested — pending a checker's approval (four-eyes)

$ nopm approve req_2c91          # a different token: task:delete:approve
✓ approved & committed           # one immutable audit row written

$ nopm audit --limit 1
created_at            actor_label     action        target
2026-06-08T…          checker (agent) task.delete   task 8f3a

The same surface a human uses — 33 documented endpoints, OpenAPI, an llms.txt index, and scoped Bearer tokens.

Agent-operable

Every action is a documented REST endpoint with a stable JSON shape. Scoped resource:action tokens, an OpenAPI spec, an llms.txt index, and a nopm CLI — so any agent drives it over plain HTTP.

Institutional governance

Every mutation writes exactly one append-only audit row. Destructive actions need four-eyes: a maker requests, a different checker approves. Enforced by Postgres triggers & constraints — even a service key can't rewrite history.

The whole triangle

Timeline, resource and budget in one governed model — the gap most PM tools miss. Over-allocation surfaces as a clash; spend rolls up to variance and burn; a locked timeline forces a rebaseline sign-off.