Skip to content

Calls

A call is a decision on the work. rb records it with your reason and the finding it was made on, meaning what rb read from the runs at that time. There are two kinds:

  • accept, reject or investigate a criterion (a rule a result must meet), an experiment, a question or a setting.
  • continue, park, stop, pivot or ship an experiment or a question, to steer the line of work.
Terminal window
rb decide <subject> <action> --why "<the reason>"

A finding never makes a call, and a call never changes a finding. An experiment’s state, such as parked or shipped, comes from its latest call.

An agent records a call only when you ask, with your words in --words. The call is “proposed, not made” until you approve it with rb confirm in your own terminal:

Terminal window
$ rb decide stricter-warmup-bar reject --why "docs/plan.md:3 sets the bar at 0.02 nats" --words "Reject the 0.03 bar. The plan says 0.02."
dkk6sym: proposed, not made: reject stricter-warmup-bar · note: docs/plan.md:3 sets the bar at 0.02 nats · words (as given): "Reject the 0.03 bar. The plan says 0.02."
It changes nothing until it is confirmed: rb confirm dkk6sym, in your own terminal.
Since this session last looked:
- stricter-warmup-bar misses its rule and the call recorded on it is not made yet: it waits for a confirmation: Warmup lowers final validation loss by at least 0.03 nats (rb decide stricter-warmup-bar accept|reject|investigate --why "...")
- warmup amended (new criterion stricter-warmup-bar: change.val_loss ≤ -0.03 (n ≥ 3)): a stricter bar, set after seeing the runs
- criterion stricter-warmup-bar added on warmup (change.val_loss ≤ -0.03 (n ≥ 3)): Warmup lowers final validation loss by at least 0.03 nats
Next: rb status

rb status lists it:

Terminal window
$ rb status
…
Proposed, not made (1)
- reject stricter-warmup-bar · note: docs/plan.md:3 sets the bar at 0.02 nats · words (as given): "Reject the 0.03 bar. The plan says 0.02." · confirm: rb confirm dkk6sym
…

You confirm it:

Terminal window
$ rb confirm dkk6sym
d7tsyb3: rejected stricter-warmup-bar · note: docs/plan.md:3 sets the bar at 0.02 nats · your words: "Reject the 0.03 bar. The plan says 0.02." (confirms dkk6sym)
made on stricter-warmup-bar: -0.02767 [-0.03484, -0.0205], n 3 (rb): gain, criterion not met
Next: rb status

rb confirm is refused inside an agent session. On its own, it lists everything waiting, and ends with one command that confirms it all as listed.

An experiment’s design is how it tests its question: its questions, hypothesis or purpose, variants, settings, criteria, gate and freeze. If an agent wrote any part, the experiment shows “design not confirmed” until you confirm it:

Terminal window
rb confirm <experiment> # lists the design, every part of it
rb confirm <experiment>@<hash> # confirms it exactly as listed

A call made before rb was in the repository is recorded as a past call:

Terminal window
rb decide int8 park --why "..." --past --when "2026-05-07" --source docs/calls.md:3 --quote "We park INT8 for now"

rb checks that the quote is in the file, and shows when git says the line was committed and whether that was before the record began.

rb retract <id> --why "..." takes back anything, such as a run, a criterion, a note or a call. It stays on the record with who took it back and why, but stops counting. An agent session cannot take back your call, only propose another.

Rabbit Brainrabbitbrain.ai · GitHub · PyPI · Privacy · Apache-2.0