Schedules

Schedules make future work visible. They are meant to read like planned actions, not infrastructure configuration.

Read a schedule

Each schedule should show:

• a plain description of the task
• the related project
• the next run time and recurrence
• whether it is active, paused, or limited to a dry run
• the worker or tool lane
• the latest result

Start, pause, or change a schedule

The private system can prepare schedule changes as operator actions. A schedule that can mutate a project needs the same bounded plan and protected action rules as manually started work.

Pausing a schedule stops future starts. It does not erase prior results or evidence.

When a run is missed

A missed or failed run should create a readable result in History and a material notice only when attention is useful. North Star should not silently replay dangerous work or create a large backlog of duplicate tasks.

Capacity remains a limit

Scheduled work respects available model capacity, time, and spend limits. A schedule expresses intent, not a promise to bypass resource safeguards.

Next: Ask North Star