gather-contextlisted

# gather-context Load the ground truth a task needs before touching it — and again whenever the work has moved the ground. Context decays over a long session and drifts as the work changes state; the slice of truth that matters before writing a plan is not the same one that mattered before the brainstorm. So this is a recurring ritual, not a one-time setup. The failure this prevents: an agent re-deriving facts that already exist (in the manifest's oracles), or asking the human to re-feed context the project already records. ## Procedure 1. **Read the manifest.** `.servo/manifest.yaml` lists the project's `oracles` (where ground truth lives) and `experts` (the domains). If there is no manifest, run `scan-project` first. 2. **Pull only the relevant slices.** For the task at hand, decide which oracles matter (scope of the work, invariants it could break, prior art that already exists, known footguns) and read those sources — and only those. Do not ingest everything; pull the slice the task needs. 3. **Write a short context brief.** A few lines: what the task is, what it must not break (invariants), what already exists (prior art), which footguns apply, which experts are relevant. Cite the oracle each fact came from. 4. **Confirm in one batch — not one question at a time.** Where the brief has gaps or assumptions, ask the human all the open questions at once, with proposed answers pre-filled from the context. The human is the CEO/client seat here: they own the intent. Thei