session-openlisted

# Session Open Absorb a handover the right way: descend from cheap-and-ambient to authoritative, verify what's load-bearing, translate the state for the user, recommend a next step, then wait for their call. ## CONFIGURATION (adapt to your project) Name your project's canonical files here. Defaults that work well: - **ROADMAP.md** — the plan: sequence, status, gates, pending decisions - **TASKS.md** — current actionable items - **Latest HANDOVER** — the previous session's delta (written by session-close) - *(optional)* an operating-model or conventions doc, a decision log, a ledger of shipped work, style/process guides your project follows If your project has a second execution environment (a CLI agent, a build server, a separate machine) whose disk is the ground truth, name it too — it is "the implementation channel" below. If you have none, skip the probe step; the canonical files are your highest tier. ## The trust ladder (read in increasing order of authority) 1. **Ambient memory / chat context** — what this conversation already believes. A summary; possibly stale. Baseline only. 2. **Canonical files** — the durable record. Overrides memory wherever they differ. 3. **Ground truth** — the implementation channel's disk (real file state, hashes, test results), if one exists. The final authority; everything else is a claim. When tiers disagree, the higher tier wins. Never act on a tier-1 belief as if it were tier-3 verified. **A report is a claim; the artifact