readouts knowledge an agent can check.

Waves of sourced research

Each wave runs one research lane per domain. Every entry cites its sources as url-and-claim pairs and records the wave that produced it.

A verifier that never saw the reasoning

A second agent checks each entry against the pages it cites and returns a verdict. It only sees the claims and the citations.

One definition of verified

verified = 1 only when an external verdict says so. With no verdict, an entry stays unverified: a lead, not a fact.

A compiler where there is code

Every code check in rust-knowledge is compiled, and where it says so run, by rustc 1.98.1. A recipe whose own example fails is never verified.

Provenance you can open

Each wave's dispatch, raw research and verification record sit next to the database, so any verdict can be traced to its evidence.

A floor that runs in CI

verify.py checks that the indexes, counts and links are true about the databases, with a stable code and a hint for every failure.

Search one knowledge base

-- sqlite3 rust-knowledge/rust.db
SELECT r.name, r.verified
FROM recipes_fts f
JOIN recipes r ON r.id = f.rowid
WHERE recipes_fts MATCH 'rapier'
  AND r.verified = 1
LIMIT 5;

Check the corpus

python verify.py
# exit 0 clean, 1 FAIL, 2 crashed

python verify.py --json
# code, message, hint per check

Route an agent to one slice

npx @mcptoolshop/loadout-os \
  resolve --project .

Read the map

index.md    # the map, for agents
index.json  # the same, for programs