DocumentationChangelog
The fleet

Coordinator & automations

A Coordinator drafts each day from a deterministic leverage scorer and settles the outcomes back into the next morning's prompt — while built-in automations keep the clockwork running on a minute tick.

The Coordinator's day

Each morning the Coordinator drafts the day's plan from a deterministic leverage scorer over the live state of the company — the workboard, the pipeline, the inbox, the objectives. Each evening a recap settles what happened back into the next morning's prompt, so the fleet compounds instead of starting over.

A daily fleet digest synthesizes the day after 18:00: what shipped, what is stuck and on whom, what does not add up, and what needs the founder. Mondays open with a planning pass that reviews every goal against the work under it before planning the day.

The voice stand-up

The day can start as a conversation: a voice-first stand-up where the fleet reports and you steer, hands-free. Saved chapters land in the Brain so the stand-up's decisions are retrievable later, like everything else.

Automations

Automations are a trigger → branch → action graph evaluated on a minute tick. Built-ins ship with the appliance because they describe how Control works: the morning plan and evening recap, the weekly planning day, a monthly librarian pass that checks the stalest notes against reality, and a release checklist raised the moment a GitHub release publishes.

Triggers worth knowing

Schedules — daily, weekly and monthly cadences, evaluated on the tick.
github_push — watch a file path on a default branch; the automation fires with the changed paths. Built for "someone must look at this when it changes" obligations.
github_release — fires on every published release, so per-release process starts itself.