ultraindexlisted

# ultraindex — the verified knowledge layer over codeindex For engine evidence and coverage limits, read [engine-evidence](references/engine-evidence.md). For a handoff that claims **every** answer claim was checked, use `verify --complete --answer <file> --repo <dir>`. Read and adjudicate the current batch files listed in VERIFY.md (default 40 pairs each; `--batch-size` changes that). Fold the comma-separated verdict paths with `verify --apply`, then gate with `check --answer <file> --semantic --complete`. Default verification is sampled; do not describe it as complete when pairs remain uncovered. Generation is only a worklist, and support still requires reading the excerpts. The mechanical work is not ours. `ultraindex` vendors **[codeindex](https://github.com/maxgfr/codeindex)** — a deterministic, zero-dependency, keyless engine — and *it* does the scanning, symbol extraction, import resolution and link-graph (`node scripts/ultraindex.mjs <command>` — no `npm install`, no API keys, run `--help` for the full surface). Everything ultraindex adds exists only because **you** are in the loop: the encyclopedia is your durable memory of this repo — it outlives the session and the context window — and the gates exist so nothing you write into it can be unfounded. **If the user only needs to find code fast, say so and point them at codeindex; they do not need this skill for that.** > **The core rules:** > 1. The **codeindex engine** owns the *code view* and the *graph* (`ui:ge