What problem does it solve? When the repository owner leaves and asks for unattended work, an AI session can drift: branches created from the wrong base, silent decisions mistaken for knowledge, tasks half-taken, and nothing pushed or recorded by morning. This rule defines how an autonomous session runs so the owner returns to a clean chain of branches and a complete list of what was done. ## Core Features & Use Cases - Session startup via /night command: The command takes a time boundary as an argument, raises this rule and the autonomous-work-run pattern, and creates the morning list file; called without a boundary it asks the owner and starts nothing. - Branch chaining: Each new piece of work branches from the previous branch, not from main, so the owner merges PRs bottom-up in order. - Defaults instead of questions: Decisions that would need the owner's word are written as a "Decisions" line in the task grill with the reason and cost of a mistake; tasks that truly need the owner are postponed untouched. - Morning list written along the way: Each closed piece of work appends a line with the work, the branch, what backs it, and what it waits for. - Use Case: The owner runs /night 6h before leaving; the session works through the board queue, commits per stage, fixes red runs in the same branch, and by morning the owner finds a chain of mergeable branches and a complete handoff list. ## Quick Start Start an unattended work session by invoking the /night command with a time boundary and let it work through the task queue until morning.
