Scheduled work

Scheduled work lets North Star continue at a useful time without requiring an open chat window.

Examples include:

• check whether a release or dependency changed
• review a project for stale public information
• run a maintenance check during a quiet period
• continue a bounded improvement task after capacity resets
• prepare a report before a regular review

What a schedule contains

A readable schedule answers:

• what will happen
• which project supplies the context
• when it will start or repeat
• which AI worker or tool lane it will use
• what limits and stop conditions apply
• where the result will appear

The schedule points to the task. It does not hide the task inside a timer expression.

From schedule to result

When the time arrives, North Star prepares the same proof loop used for manually started work. It loads current context, checks capacity and safety conditions, runs inside the allowed boundary, reviews what happened, and records a result.

If a protected decision appears, the schedule does not grant permission by itself. The task waits for your judgment.

Quiet by design

Scheduled systems become noisy when every heartbeat, retry, and empty check looks urgent. North Star separates normal operation from material attention. Briefing shows the useful consequence: a task is running, a result is ready, a decision is needed, or nothing important changed.

Next: Memory and evidence