Fast Queries

Start with supplied evidence, not a fixed diagnostic script.

1. Read the injected dispatch kernel: # Your Contract (goal, project, your can_read menu) and # Project context, the dispatch project's can_read sections, whole when they fit, else one get-contract pointer per section, else a single count line. A component the goal names that the block does not carry is fetched first (investigation, evidence ladder step 1).
2. Pull the rest of what the goal needs from the persistent substrate, narrowly scoped. The read vocabulary -- which verb opens which coordinate, what each returns, and the workspace rule -- is in agent-protocol/read-map.md.
3. Run the smallest authoritative read-only CLI query for the surfaced domain. Use native output/filter flags and one command per call.
4. Record the query, result, and uncertainty in the contract checkpoint.
5. Deep-dive only where the evidence identifies a gap or inconsistency.

Do not invoke helpers from .claude/; that tree is an installed/protected surface, not Gaia source. Do not treat a broad health command's exit code as proof of a specific desired state. If investigation forecasts mutation, switch to investigation and collect predictable exact T3 commands before requesting consent.