Reference

Look things up. Contracts, tables, flags, and exhaustive lookups — read between doing, not end-to-end. (Back to docs home.)

Start with the bob CLI reference. It covers every bob command, grouped by job, with every flag, the exit codes, and the slash command that does the same job inside a Claude session.

Reference	Covers
Actions budget	actions-budget.js: each repo owner’s GitHub Actions minutes against the included quota — ok / warn / over / unknown / unavailable, the scope a token needs, the 6-hour cache, and where the figure is shown: the fleet snapshot, the audit view’s Actions budget table and the /what-next –report health line (#1695).
Applicability	bob-applicability/1 — every registry item graded by applicability before usage (bob tour –applicability): not-applicable-anywhere, applicable-unused, applicable-used or unscoped, from applies_to against each portfolio project’s declared or inferred stack and type, then fleet usage; missing or implausible metadata is flagged for a fix, not graded (#2900).
Automation Behavior	What each automation level (supervised / trusted / autonomous) permits.
Autonomous PM Front-End	The vision-only → approved-queue backbone (pm-frontend.js) — check-vision, scaffold, the queue gate, and blocker→TODO handoff.
bob asks	The one list of everything waiting on the operator (#3801): what counts as an open ask, which projects bob asks reads, what each ask unblocks and the order that gives, the text line, the bob-asks/1 document, how a project that could not be read is reported, and the exit codes.
bob do	The bob do machine: phases, events and their payloads, the closed artifact set with the evidence each type requires to land, the recording link check, and the bob-do/1 state fields.
bob ready	The one command for starting or resuming a project: a new or existing directory, or an owner/repo it clones, to warp-ready and on bob viz, with a READY / NOT READY verdict.
bob-reap	The declarative working-tree residue reaper — reap.json manifest, keep-list floor, liveness guards, TTL, and session-end integration (#1664).
bob secrets	The presence check for the operator’s declared secrets (#2286) — the present_at locator on secrets[] in operator.json, bob secrets check and its bob-secrets/1 document, the four states and their fixes, how each kind is probed for existence and metadata only, the exit codes, the secrets line in bob doctor and the fleet snapshot, the shared probe distribute-secret.sh uses, and the canary test that proves no value is ever printed.
bob status	The front door — every scope’s verdict and one next: command with no arguments (#2641) — and one health verdict per scope as one bob-status/1 document that embeds each composed engine’s own v1 document unchanged (#2080).
bob viz Design Checklist	The rules every region on the bob viz console is held to — data-ink, small multiples, colour for state only, the sparkline spec, tokens for type and spacing, both themes — as checkboxes a new pane copies into its requirement.
bob viz Dashboard Service	The always-on dashboard server behind bob viz: bob viz –install-service installs a launchd agent (macOS) or a systemd user unit (Linux) that starts it at login and restarts it on exit; file locations, the launcher’s reuse rule, the self-update hand-over, the bob doctor line, the dispatch endpoint (the operations table and its trust boundary) and the chat input on every project card.
Branch Config	Branch detection and the single-source-of-truth resolver.
Branch Protection	The protection a project’s main branch carries on GitHub as a declared _meta.branch_protection setting: the required checks and whether the rule binds admins, the report in bob provision status against what GitHub holds, the check that each route to the branch still gets there under the rule, and reconcile, which writes to GitHub only with –apply, refuses while a route would be cut off, and never overwrites a setting the declaration cannot carry (#3624).
Briefing	The briefing/1 contract and the bob brief collector (#2243) — Needs you / Done / Doing / Will do across every project since the previous briefing, assembled from source data with links, every unreadable source a named gap — the /briefings page on the Project Monitor that renders the latest one and its history (#2244), and bob brief –send, the Telegram headline of at most five lines with the link to that briefing, delivered through bob notify (#2245).
Checkpoint dirt rules	What the segmentation checkpoint counts as dirt, what it does about each class and why — the one statement of the rule, pinned by tests/fixtures/checkpoint-dirt.json (#2037).
CI health and refusal baseline	ci-health.js report: per-workflow CI outcomes, per-job queue time and wall clock, burst-collapse cancellations kept apart from failures, and live-session refusals per day — with the baselines later changes are judged against (#2745).
CI Locus	A project’s CI execution locus (farm = fleet self-hosted runner, hosted = GitHub) as a declared _meta.ci setting — the resolver chain and its reasons, the projection into CI_RUNNER_LABEL, reconcile (idempotent, refuses a public repo to farm), the drift report in bob provision status and the fleet snapshot (#1728), and the runner-availability preflight: online-runner probe, fallback to hosted within one job, one no-viable-runner report when hosted is dead too, idempotent restore, and the queued-job alarm that tells offline from busy (#1731).
CI rollout	ci-rollout.js: roll the farm runner out to every private, active repo with CI in the declared accounts. Inventory from gh at run time, farm / hosted / excluded / skipped with the reason, an idempotent apply (declare → register → reconcile), a green-run verify and one-command rollback (#1730).
CLI Safety	The non-project guard (project-guard.sh) — hard-denied targets, the override, and the destructive-command inventory.
bob CLI reference	Every bob command on one page — grouped by job, each with its usage, every flag, exit codes and the doc to read next, plus the slash commands that do the same job; rendered from scripts/bob/commands.json by help.js –reference (#2059, #2607).
Cloudflare Tokens	The Cloudflare root and working tokens, where each lives, how a project resolves to its account and its token, the bob cloudflare verify and mint commands, and what full access excludes (#3583).
Control actions table	bob-control-actions/1 — the table of bob commands a project’s page in BoB Control offers: its fields, how to add an action, the rules for a command that changes something and for a placeholder, the run route’s rules, the check that guards it, and where the stuck threshold and an ask’s unblocks are defined.
The decide() seam	One contract for asking a small model a typed question about a state (decide.js, #2817) — the backends, the declared caller registry, the egress allow-list, fail-open vs fail-visible, routing on confidence, and stakes derived from reversibility.
Design-Brief Schema	The generic brief format /design-brief emits — front matter, the seven sections, provenance states, validity rules.
Design-Generator Catalog	The AI design generators a brief can target (v0, Lovable, Bolt, Figma Make) — input conventions, strengths, limits, fidelity, constraint→tool chooser.
Dev Lifecycle	The dev.json manifest and the /dev-up lifecycle contract.
Dispositions	Bob University’s disposition record — registry/dispositions.json, one record per BoB item saying certified, needs-work, not-applicable or retire, with the date, evidence and rationale: the fields, the rules check-dispositions enforces (certified needs an improved, dated exam with a positive delta for its named model, so no-signal never certifies; retire is completed by a retired-items.json record; every record names a real item), the history a re-disposition keeps, how a model change re-opens a certification (#2904), and why an item with no record is counted, not failed (#2901).
Doc-Bootstrap	The tier rubric, the scripts/doc-bootstrap/ script + CLI surface, and the JSON contracts (inventory, triage, coverage, source_evidence).
Documentation Standard	The spec every BoB doc obeys — Diátaxis modes, taxonomy, frontmatter, severity model.
Fleet Feed	bob-fleet-feed/1 — every project on every fleet machine in one document: this machine read live, the rest from their published snapshots, each with its age, staleness, and null for anything not measured.
Fleet Snapshot Timer	audit.js snapshot on a timer on every fleet machine — a launchd agent on macOS, a systemd user timer on Linux — publishing where audit.js view reads.
Forge Health	The classified forge-availability signal every gh-dependent path can read, the durable read cache and write-ahead queue that keep a run alive through a degradation, and the quota budget that keeps a caller from meeting a rate limit — the gh PATH shim, the classifier, the TTL cache, the read fallback, the write spool and its replay, and the shared budget with its pacing and backoff (#1748, #1749, #1750, #3190).
gh Adapter Contract	The gh surface BoB depends on, derived from the tree: every gh command, flag and –json field, split into executable and prompt-text call sites, read by scripts/forge/gh-inventory.js — the contract a second forge backend behind bin/gh must satisfy (#1753, part of #1746).
Glossary	Skill, agent, slash-command, and shell-command glossaries (extracted from handbook §10–13).
Hooks Reference	Every BoB hook, by event (extracted from handbook §14).
iBoB kit	The iBoB terminal kit (#2291, cap #2289): config/ibob-kit.json in the operator repo and its schema, bob ibob check (declaration rows, per-machine tailnet / ssh / key / mosh / tmux checks, sessions listed, every failure with its fix, ibob-kit/1, exit 0/1/2), bob ibob attach (ibob-attach/1) and the Claude Remote Control route.
Kickoff Flags	Warp-drive run options set at kickoff (-f/--timeout/--ceiling/--budget/--area/--dry-run) — the kickoff.js parser, floor-safe validation, and how they surface in bob warp status/config.
Launchpad Links Index	The bob-launchpad-links/1 schema and generator (scripts/launchpad/links-index.js) — per-project link map derived from declared state only — plus the bob-launchpad-layout/1 contract (#2139), the one owned place for user arrangement state, served at /layout.json and applied after paint.
Loop Primitive	The declarative "do X until Y" construct and its manifest schema.
Memory Recall	On-demand query over the file-based memory store (recall.js) — the relevance signal (keyword×recency + type-prior + usage), scope bounds, and CLI flags. Complements memory-audit.
Mirror Remote	The declared second git host every managed repo publishes to — mirrors.json topology, idempotent reconcile, dual-remote publish, and staleness reporting (#1747).
Model Routes	The –route flag on claude and bob groom, the bob route mint, status and check commands, where each OpenRouter key lives, what the session ledger records, what a client project is refused (#3590), and the model roles with their failover order (#1231).
Narrative-from-Git Engine	The shared deterministic core behind /update-story and /update-journey (scripts/narrative/engine.sh) — config schema, count types, new-surface detection, the JSON output contract, and /update-story’s per-project config and first generation.
Natural-Language Guide	The phrasings that trigger BoB commands and skills.
Notices	bob-notices/1 — everything that needs Paul across the fleet (todos awaiting completed, blocked runs, pending decisions, a stable release to update to), each with its exact command or link, plus one daily did-you-know from bob tour, and a status per source so an empty list is never a failed read.
Port Allocation	Dev-port band convention and the two-tier source-of-truth model.
Project Detail	bob-project-detail/1 — one project on one machine, everything an expanded bob viz card shows beyond the fleet feed: the run, recent commits and PRs, the queue, health, cost, reports and links. It is read live on this machine and from the snapshot for any other, and every gap is named.
Release Content Gate	The release content gate (#2290): release.sh refuses to tag a tree that carries operator data, a client identifier or a credential. The three rules (path, tenant, credential), where each reads its input (release-content.json, the operator profile’s tenants[], the shared secret-patterns.json), the release-content/1 output and exit codes, masked credential output, the allow-list and its burn-down, and the fail-closed exit when no operator resolves.
Reports	bob-reports/1 — the fleet’s last 14 days of tick digests, session reports and status reports as one list, newest first, each with its project, machine and link, and a status per source so gh being down never empties the digests.
Retired Items	The declared retirement record — scripts/lib/retired-items.json, one entry per hook, command, agent or skill that no longer exists at its path (removed, superseded-by, moved-to-registry, moved-to-universal, with the retiring issue): the record fields and identity rule, how it was seeded from git history, what derives from it (the dangling-link pruner that bob provision refresh and bob ready run, the removed-hook pruner), the check-retired-items gate that refuses an archive without a record, and the retirement step every archive, demotion or promotion must take (#2314); scheduled retirements (retires_on), the retirement banner on a page’s subject, the Retired section of the generated references and the check-retired-mentions docs gate (#2623).
Reversibility Decision Engine	The L4 one-way/two-way classifier (decision-engine.js) — categories, the never-guess safety bias, and the CLI exit-code contract.
Rituals	The fixed ritual vocabulary and each ritual’s cadence, kit and farm-eligibility (registry/rituals.json), the one home for a project’s schedule (its manifest’s _meta.rituals), liveness-scaled defaults for a project that declares none, the portfolio review held once for every project with its per-project decisions, BoB’s drills and the versioned checklist a ritual walks (the security review’s attack-surface checklist, recorded per run with the items not assessed — #2241), run history derived from ritual-run issues, ritual.js due and the check-rituals gate (#2230, #2231, #2235).
Credential Inventory	The declared inventory of every credential BoB and its managed projects depend on — secrets-inventory.json at the repo root, names and references only, never a value: the entry fields, the location kinds and their ref notation, how it was seeded, the check-secrets-inventory gate that refuses any secret-shaped string, the cred-check presence check that compares the inventory to what each store holds by name (missing / undeclared / expired / rotation-overdue, unknown never missing, carried per machine in the fleet snapshot — #2238), the rotation schedule (cred-check.js due: one deduplicated, contract-conforming todo per credential due within P14D, bob-rotation-due/1 as the briefing source, rotated recording last_rotated on a branch for the PR — #2239), the environment axis (an entry set separately per environment declares environments[] and tags each copy with its env; presence, rotation and rotation todos are per env — #3082), and why the file is not called credentials (#2237).
Cost and Churn Series	bob-series/1 — tokens and USD per project, per run and per merged requirement, plus fix-to-feat, harness-defect recurrences, flaky reruns, CI duration and releases, over a 30-day window, each series with its source, as_of and a status so a missing source is never a line of zeros.
Session Kits	The one declared home for session kits — registry/kits.json, its schema, the six kits (review, vision-planning, security, release, incident, bugfix) and the check-kits gate that keeps every named item real (#2225).
Session Evidence Ledger	The per-project append-only record of what tooling sessions actually used — skills, agents, commands (#1131); the substrate gap detection and orchestrator feedback read.
Site Publish	The one publisher to the operator’s site (#3103): the site-publish/1 bundle a producer hands over, the operator’s config/site-publish.json that declares the site and its sections, and bob site publish — section confinement, the every-host Access gate (#2895), the declared Cloudflare account (#2984), the live-site guard (#4418), the clean-checkout guard, commit, push and deploy.
Skill evals	The skill eval gate (#2390, part of #2387): one eval suite per skill, command or agent, a directory named for it under evals/ in BOB_SOURCE, run through claude plugin eval with a with/without ablation by bob eval run (scripts/evals/run.js), which prints a skill-eval/1 result; bob eval gate (scripts/evals/gate.js) accepts a change only when its score is strictly higher than the best recorded per model in baseline.json, higher than without the item, and its trigger rate does not drop. Suite layout, authoring a case, the trigger graders every suite carries, the result and baseline formats, cost ceilings, make evals, and the known limitations.
Task Command	/task — file maintenance work (dependency bumps, CVE updates, upgrades, migrations, cleanups) as a task issue whose definition of done is a Verification checklist, with an optional trigger reference and no parent capability.
Test-Environment Mirror	Provision a test environment mirroring prod and sync prod data into it with mandatory redaction (#451).
Test policy (e2e-first)	What kind of test an agent writes: the seven e2e-first rules, what _workflow.test_policy: balanced relaxes, the drift-check exemption, and examples of tautological, change-detector and good e2e tests (#3200).
tmux Cheatsheet	tmux keybindings for warp-drive / cdfork sessions.
TODO Format Contract	The body contract a todo issue must satisfy (summary, numbered steps, #NN link) and the completed done-signal.
Token Monitoring	Token-usage capture, reporting, and cost estimation.
Tracker labels	What the GitHub issue tracker holds, which label means what, and how a discovered note becomes an issue and later expires — the one definition of the label set bootstrap-labels.sh ships and check-report-labels.js guards (#2062).
Verification System	make check / test targets and what each verifies.
Warp-drive state-machine flags	Every state-machine.js subcommand and flag — type, default, parser and meaning — generated from state-machine.js –help –json (warp-flags/1) by gen-reference.js (#2085).
Warp-Drive State Reference	State file, state-machine CLI, and the full phase-transition table.
Wiki Store	The skill-evolution wiki (#2388, part of #2387): a git-tracked wiki/ in BOB_SOURCE with pattern pages, a derived index, an evolution log and a skill-impact ledger. The page frontmatter (schemas/wiki-page.schema.json), the evidence ref forms, the lint make check runs, the row formats of the two tables, retirement by closed defect and staleness, the client-data rule, and the rule that nothing a running session loads may read the wiki.
Work attribution	The agent labor meter (#4420, cap #3135): bob labor report turns the Claude Code transcripts on this machine into active-hours per project per day by three rules — the gap rule (events closer than G form one span), the tool rule (a tool_use to its tool_result is never idle) and the union rule (every session on a project counts once per wall-clock hour) — with G from the operator’s config/billing.json, the bob-labor/1 document, the fixtures the test pins, job attribution (#4423: _meta.billing {job, billable} in the project manifest, bob labor report –by job with its unbilled (unmapped) block, the overhead rule for BoB’s own projects, the bob provision status billing line), the fleet roll-up (#4422: labor and cogs per project in every machine’s snapshot, the view’s Labor table and bob labor report –fleet with its stale / never / partial markers), and what the meter is not.
Workflow Authoring (GitHub Actions)	The conventions every GitHub Actions workflow BoB ships or scaffolds follows — the CI locus runner seam (runs-on from CI_RUNNER_LABEL, hosted as the unset default), the explicit # pinned: <reason> form for a job that cannot run on the farm, the toolchain-assertion pattern, GitHub-held secrets — and the make check-workflow-runs-on gate that holds a new workflow to them (#1729).
Workflow config (_workflow)	The _workflow config table — every key BoB reads, its default, its comment and every file that reads it; generated from WORKFLOW_DEFAULTS by check-workflow-keys.js (#2041).
Writing Styleguide	Prose rules (WS-N) for all authored artifacts — issues, commits, PRs, comments, docs — and the web-read rules for todos, reports and briefings.