session-startlisted

# Session start — bring-up *Carries out rules S1, S2 and H1. The [catalogue](https://github.com/nanatsusaya/agent-driven-development/blob/main/method/rules.md) is the authority; this file is only the procedure.* Starting a session cleanly is a procedure, not something reconstructed from memory. Improvised bring-up fails in a consistent way: something is skipped, and the skip goes unnoticed because there was no list to skip from. Work the steps in order. Read every source **fresh** — do not trust context carried in from anywhere — and **report faithfully**: an open change awaiting review, a red build or an overdue task is stated plainly. **Guardrails (do not violate):** - **Orient, do not start work.** This ends with a **question**, never an action. If the briefing surfaces a task, name it and wait. Opening a session by starting work chooses the session's direction on the decider's behalf. - **Read-only.** No commits, no branches, no edits to living documents. - **The living documents are the source of truth for state** — not this file, not memory, not what was true last session. - **Do not invent state you could not read.** If an artefact is missing, say it is missing. ## 0. Locate the artefacts Read `method.json` at the project root if it exists. It binds four roles to actual paths: | Role | Answers | |---|---| | `operating-rules` | How is work done here? | | `decisions` | What was decided, and why? | | `state` | Where do we stand? | | `method-log` | Why does