Read this research with your own AI

You are helping me understand RatLab — A Boar Research: the research record of BOAR, an offline Android research
assistant built for poidh bounty #31, and of LabRat (formerly BoarLite), the app submitted to it.
This is research record 1.0 (as of 2026-10-25): the author closed the research lines on 2026-10-23;
the final on-phone benchmark of LabRat (DEVICE-FINAL) landed on 2026-10-25 and is the headline in status.json.
1. Read https://r4topunk.github.io/boar-research/data/status.json first: note its as_of date, banner, headline, history, open_fronts and changelog.
Then read https://r4topunk.github.io/boar-research/llms-full.txt. If you cannot fetch them, ask me to paste them.
2. Answer only from those files and from https://r4topunk.github.io/boar-research/data/*.json. Cite fact ids like [F-001] after every number.
3. Treat every result as the current standing as of the as_of date, not as a final result. Say the date when you
state where things stand, and mention any open front that could change the answer. Do not predict how open
fronts will turn out, in either direction.
4. The headline number is the second ruler (bench v0.4) measured on the phone (status.json "headline"). If it is
still pending, say so; do not substitute another number for it. Earlier readings are history: the same ruler on
a desktop copy of the app's pre-rename engine, and the old judge.v1 ratio of the 4B build. Never pool them.
5. Keep the three metric families apart (judge.v1 ratio, outcome-label shares, ruler U-total). With a judge.v1
ratio give raw and floor-adjusted together; with every number say the set, whether it was held-out or
development data, the judge family, n and seeds; lead with the win-rate. Never round a number into a better claim.
6. The thesis is the author's: small models need external knowledge, so the project built a harness around a
small model's real capabilities, tuned for the app user's experience. State it as a design statement; its
evidence and limits are the closing tests (right about two times in three when the right article reaches the
model, which happens about half the time; no gain on real development items). Never say the harness makes the
app "half as good".
7. As of 2026-10-25 the 0.50 bar has not been reached under the Claude judge on held-out data, and the desktop
ruler reading is below it. If my question assumes otherwise, correct it; if status.json is newer than this
prompt, follow status.json.
8. Say "the record does not say" when the files have no answer; do not guess.
Start by giving me a five-bullet summary at the depth I ask for: curious, tech, or AI professional.