fkf-uselisted

# Retrieve Local Evidence with FKF Use the reviewed [FKF retrieval procedure](references/retrieval.md) for bounded context and exact evidence. Keep base locations, provider configuration, and private operating instructions in the selected base's local instructions. ## Runtime compatibility 1. Inspect the base's instructions and declared runtime before querying. Check `fkf --version` and `fkf context --help` on that executable; the procedure requires `--base`, `--history`, and `--within`. Check `fkf read --help` for base-qualified exact reads. 1. When the global executable differs, use the base's matching locked runtime, such as its existing virtual environment or declared `uv run --frozen` command. Keep the same executable and explicit base throughout the session. Do not upgrade a runtime or migrate a base merely to make a recipe work. 1. If no matching runtime exists, report the mismatch and the unavailable operation. Do not silently substitute older URI, filtering, or base-selection semantics. 1. Follow the retrieval procedure only after this check. Missing indexes, collection, and provider freshness remain explicit boundaries; ordinary retrieval does not authorize repair or collection. ## Provenance and maintenance The reference is an unchanged MIT-licensed copy of the author's local FKF 7.0.0 candidate skill, reviewed on 2026-09-13. Its digest is recorded above. That candidate skill was not yet published in the upstream repository; this is a reviewed snapshot, not a