AI Project Navigator
Hadley drops into any project, reads the signals you already generate — mail, notes, the board, deadlines — and runs quiet governance cycles that surface what's drifting and draft the next moves. You see it all in Mission Control.
The cycle
Every cycle, Hadley gathers what's true about the project, judges its health, and hands you a ranked set of drafted actions — nothing acts until you say so.
Unread mail by project, the notes' next-list, the task board, and every looming deadline — pulled, not asked for.
It computes health — overdue, due-soon, stalled — then reasons about what actually moves the project forward.
A ranked queue of concrete next actions, each classified by your policy — ask, auto, or blocked.
Approve and it executes; reject and it's gone. Hadley learns from the call for next time.
Mission Control
One self-contained page — no server, openable anywhere. Workstream strips, a completion gauge, open dependencies, and a cue sheet, all read straight from project state.
Trust, ramped
Hadley defaults to suggesting and drafting. Flip an action type to autonomous when you trust it, one at a time — and a hard guardrail still stands in the way of anything that matters.
Every action type starts on Ask. When you're ready, switch it to Auto and Hadley executes that type within guardrails — no gate, no babysitting.
Anything touching the things you can't undo is forced to blocked, overridable only with an explicit review — no matter how much autonomy you've granted.
Early access