> ## Documentation Index
> Fetch the complete documentation index at: https://yellowhammer.dev/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# Run Nights

> Choose how a Project rehearses, schedules, and bounds unattended work.

Each Yellowhammer [Night](https://yellowhammer.dev/docs/reference/statuses-and-glossary.md#night) belongs to one Project, with local tools executing its author, build, and land Acts. Different Projects can run independent Nights concurrently. Prepare the execution settings before leaving a Night unattended.

## Prepare a Night

> [card] [Rehearse before scheduling](https://yellowhammer.dev/docs/run/rehearse-before-scheduling.md)
>
> Exercise the real board and Worktrees without dispatching agents or publishing code.

> [card] [Configure the schedule](https://yellowhammer.dev/docs/run/configure-the-schedule.md)
>
> Set the Night window and install its scheduled jobs.

> [card] [Choose agents and routes](https://yellowhammer.dev/docs/run/choose-agents-and-routes.md)
>
> Choose workers, fallbacks, authoring, and independent Verification.

> [card] [Set limits and protected paths](https://yellowhammer.dev/docs/run/set-limits-and-protected-paths.md)
>
> Bound repeated effort and refuse overlapping declared scopes.

## A Night at a glance

The author Act selects and prepares a Feature. The build Act coordinates its Work Cards and review. The land Act verifies and publishes eligible results as pull requests. A Project has one Feature in flight at a time, but can advance through multiple Features sequentially in the same Night. The Night Summary reports the result, including Nights that produced no work.

The installed LaunchAgents invoke the engine independently of the app. Quitting Yellowhammer does not stop a Night; keeping the Mac available is still necessary. Yellowhammer leaves merging to you.

Planned workflow

**Run a Night safely**

Show the learning path from rehearsal through schedule, Routes, limits, and Protected Paths.

Planned workflow: rehearse, verify local readiness, review the schedule and Routes, then check limits before unattended runs.

## Next steps

[Rehearse before scheduling](https://yellowhammer.dev/docs/run/rehearse-before-scheduling.md) · [The lifecycle of a Night](https://yellowhammer.dev/docs/concepts/lifecycle-of-a-night.md)


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.