Your first record
Start the record
Section titled “Start the record”In your own terminal, in your repository:
rb init "<the work's theme>"We ran it in a repository that trains ViT-Tiny with and without label smoothing:
$ rb init "Label smoothing on ViT-Tiny"Project 'label-smoothing-on-vit-tiny' started: ~/vit-smoothing/.rbRabbit Brain YAML files beside the code: commit .rb/ with it, so the record travels with the work.
For the agents here: Claude Code (CLAUDE.md): the skill in .claude/skills/rabbit-brain/SKILL.md; rb's MCP server in a new .mcp.json; rb's session hook in a new .claude/settings.json (SessionStart and Stop run rb journal scan, which looks at the repository and says nothing)
Then paste this line into your agent's chat: Use Rabbit Brain to track this: read rb context, then record where the work stands.Then start a new agent session, so it loads rb’s skill.
Hand it to your agent
Section titled “Hand it to your agent”Paste the line rb init printed into your agent’s chat, and add what you want done:
Track this with Rabbit Brain, and do one piece of work.
Works in any agent that runs terminal commands.
Use Rabbit Brain to track this: read rb context, then record where the work stands. Then find out whether label smoothing is worth keeping on our ViT-Tiny, with seeds 1 to 3.
What the agent did
Section titled “What the agent did”The agent read rb context first:
$ rb context# The record: Label smoothing on ViT-Tiny
## First, record where the work stands
Nothing is recorded yet, and this project holds work already done: 1 commit. Record where the work stands now, in this turn, from the files, and ask the researcher nothing first. How: rb docs --start.
Generated by `rb context` from `.rb/`; read the state from here or `rb status --json`, never from memory or a summary.… (53 more lines)It recorded the question, then the experiment and its settings:
$ rb question add "Is label smoothing worth keeping on our ViT-Tiny?" --id q-smooth --words "find out whether label smoothing is worth keeping on our ViT-Tiny"q-smooth: Is label smoothing worth keeping on our ViT-Tiny?
Next: rb experiment add "<what would answer it>" -q q-smooth --hypothesis "<what you expect>"$ rb spec set smooth --from configs/train.yaml --keys "optim.*,data.*"smooth: 3 settings from configs/train.yaml @234b05955a46 · 3 verifiedBefore any run, it recorded the criterion from docs/plan.md. A criterion is the rule a result must meet:
$ rb criterion add "Label smoothing 0.1 raises top-1 by at least 0.3 points" -e smooth -q q-smooth --metric change.top1 --at-least 0.3 --min-n 3 --why docs/plan.md:3 --id smoothing-helpssmoothing-helps: Label smoothing 0.1 raises top-1 by at least 0.3 points change.top1 ≥ 0.3 (n ≥ 3) · primary · on smooth declared; no evidence recorded yet
Next: rb run add smooth --from <the results file a run wrote> --set seed=<value>It ran each seed through rb journal run and recorded the run with its receipt: what ran and on which commit. After the third seed, the criterion has an interval:
$ rb journal run -- python train.py --seed 3{"metrics": {"plain.top1": 71.55, "smooth.top1": 72.1}}exit 0. The command, its exit code and what it wrote are in the journal.It printed its metrics: plain.top1=71.55, smooth.top1=72.1. rb reconcile proposes the run of smooth that records them.
Since this session last looked: - out/seed3/ holds results no recorded experiment reads yet (rb reconcile) - out/seed3/metrics.json: results landed and are not in the record (rb reconcile)
Next: rb reconcile$ rb run add smooth --from out/seed3/metrics.json --set seed=3 --config out/seed3/config.yaml --command "python train.py --seed 3" --commit 234b05955a4653f6e045af115202ce98dbdb730brunghitef on smooth: plain.top1=71.55, smooth.top1=72.1 · seed=3 Ran with the spec: 4 of its settings found in out/seed3/config.yaml, all matching. Only rb's own files are not committed (.claude/settings.json, .claude/skills/rabbit-brain/SKILL.md, .mcp.json): they are not the run's code, so the receipt finds no changes outside the record. Produced: 2026-11-10 15:32:05 (file) smoothing-helps criterion met · gain: change.top1: +0.54 [+0.4017, +0.6783] % · paired difference, t interval, 3 seeds, 95% (rb)
Next: rb show smoothing-helpsWhat you’ll see
Section titled “What you’ll see”Run rb status in your own terminal:
$ rb statusLabel smoothing on ViT-Tiny · label-smoothing-on-vit-tiny13 record files not committed
Is label smoothing worth keeping on our ViT-Tiny? (open) Label smoothing 0.1 raises top-1 by at least 0.3 points. change.top1: +0.54 [+0.4017, +0.6783] % · paired difference, t interval, 3 seeds, 95% (rb); gain: the interval clear of 0 on the better side (higher is better); criterion met: estimate +0.54 ≥ 0.3; rule and question link declared before the evidence (by production times). units: 3 seeds.
Rules: 1 met
The design of 1 experiment is not confirmed: rb confirm lists it.
rb looks in out/, outputs/, results/, eval-out/ and metrics/ at the top, in folders named for results (results/, eval/, metrics/, reports/, artifacts/ and the like), down to 4 levels from the top, at the files in the repository's top folder, and at .json, .yaml and .toml files git shows as new or changed. It last looked at 2026-11-10 15:32 UTC. It reads what code, configs, docs and database rows say only where the record points to them, and it sees only the commands run through rb journal run.rb checked the record with git at 2026-11-10 15:32 UTC: all 13 record files are new, changed or deleted since commit 234b05955a46, which does not hold the record.Not committed: .rb/.gitattributes (new), .rb/.gitignore (new), .rb/experiments/smooth/criteria/smoothing-helps.yaml (new) and 10 moreTo check it yourself, in your terminal: git -C ~/vit-smoothing status --short --untracked-files=all -- .rb
Rules smoothing-helps Label smoothing 0.1 raises top-1 by at least 0.3 points criterion met · gain · change.top1 ≥ 0.3 (n ≥ 3) reads: change.top1: +0.54 [+0.4017, +0.6783] % · paired difference, t interval, 3 seeds, 95% (rb) result: gain: the interval clear of 0 on the better side (higher is better) rule: criterion met: estimate +0.54 ≥ 0.3 timing: declared before the evidence (by production times) units: 3 seeds
Experiments smooth Label smoothing 0.1 vs none · open · plain (baseline) vs smooth (candidate) · varies label_smoothing · not frozen · settings 5 verified · 0 provisional · 0 unknown · 1 per-run · runs 3 to run again: code ok · environment ok · files ok
Runs: 3 recorded on 1 experiment · every receipt is what rb wrote
Nothing open.
Next: rb confirmThe Rules block shows the criterion’s finding: what rb works out from the runs. Findings explains each line.
Confirm the design
Section titled “Confirm the design”The agent wrote the experiment’s design, so it reads “not confirmed” until you sign off on it with rb confirm:
$ rb confirmDesigns waiting for a confirmation (1): smooth: Label smoothing 0.1 vs none questions: q-smooth hypothesis or purpose: not recorded why: not recorded variants: plain (baseline), smooth (candidate) · varies label_smoothing setting optim.lr: 0.001 from configs/train.yaml#optim.lr setting optim.weight_decay: 0.05 from configs/train.yaml#optim.weight_decay setting data.batch_size: 128 from configs/train.yaml#data.batch_size setting seed: per run setting plain.label_smoothing: 0.0 from configs/plain.yaml#label_smoothing setting smooth.label_smoothing: 0.1 from configs/smooth.yaml#label_smoothing criterion smoothing-helps (primary): change.top1 ≥ 0.3 (n ≥ 3) · for q-smooth confirm: rb confirm smooth@f6b6812a74bdbdfd0c6b1dbf8c1ebd0de7390051d0b73fbfb11624b7e88dc0d3$ rb confirm smooth@f6b6812a74bdbdfd0c6b1dbf8c1ebd0de7390051d0b73fbfb11624b7e88dc0d3smooth's design is confirmed.
Next: rb statusrb confirm runs only in your own terminal. An agent session that runs it is refused.
Rabbit Brainrabbitbrain.ai · GitHub · PyPI · Privacy · Apache-2.0