wikipedia.pikelet is a 648.5 MB static file — 456,153 Simple English Wikipedia articles, an embedded query encoder, and a search index, sealed into one file on a plain HTTP host. There is no application server behind it. Every answer below comes from byte-range reads against that one file, visible in the log as they happen.
bytes=X-Y against one URL.
The badge on each answer is match quality, not a fact-check: it measures how well the
retrieved passage matches your question, not whether that passage actually contains the
specific claim you asked about. At Wikipedia's scale almost every question has some
topically related article, so strong mostly means "an article about this
exists" — it can be confidently wrong on a specific detail the article doesn't cover. The
one place this file reliably withholds is when the topic itself is missing, which is what
the fact-removal tab shows.
You just searched this file yourself, with the network log open. Watch Claude use this exact file over MCP →
Same artifact, same read path, restricted to search / list_packs / get_record — no web tool, no filesystem tool.
bytes=X-Y against each of these files.
Two identical .pikelet files, compiled from the same fictional research-station
corpus. The right-hand file is missing a single record — pick which one. Same model, same
code path, no other change — the answer is a function of the file's contents, nothing else.
Press "Run query on both files" above.
Press "Run query on both files" above.
A third file for the fact selected above: identical to the full pack except that this one record was edited to state a different, still-plausible value. The model answers confidently either way — confidence measures how well the passage matches the question, not whether the file's facts are internally consistent.
Press "Run query on the contradicted file" above.