Make is the developer-facing command surface. Cargo is the default backend. BuildBuddy/Bazel is an opt-in acceleration backend for machines with access to the GCP-backed runner pool.Documentation Index
Fetch the complete documentation index at: https://docs.rkat.ai/llms.txt
Use this file to discover all available pages before exploring further.
Local Commands
Use these commands for normal development:cargo for normal repo work. When you need targeted Cargo commands,
use ./scripts/repo-cargo so output roots and multi-agent work stay isolated.
BuildBuddy Opt-In
SetMEERKAT_BUILDBUDDY=1 to route the same Make lanes through the BuildBuddy
backend:
BUILDBUDDY_DRY_RUN=1 with explicit BuildBuddy Make targets to inspect the
selected command without running it.
The Make targets delegate through scripts/run-build-backend-lane; when
BuildBuddy is enabled, that switch calls scripts/buildbuddy-dev.
Test Lanes
| Lane | Scope |
|---|---|
make test-unit | Fast unit coverage. |
make test-int | Integration-fast coverage without e2e scenarios. |
make e2e-fast | Deterministic end-to-end lane. |
make e2e-system | Local real-resource scenarios. |
make e2e-live | Targeted live-provider checks when credentials are configured. |
make e2e-smoke | Compound live-provider smoke scenarios. |
tests/integration/src/e2e_lanes.rs. Scripts and BuildBuddy targets route to
that taxonomy rather than inventing separate lane names.
Architecture Gates
Machine and surface contracts have direct Make targets:CI Shape
GitHub Actions selects one backend for a run:- default Cargo lanes for normal contributors
- owner-gated GCP BuildBuddy lanes when the secret-backed runner pool is available
Doctor
Run:bb CLI, generated Bazel files, selector
behavior, lane isolation, and docs wiring without printing secrets.
Multi-Agent Work
Separate Git worktrees are already isolated by path hash. If multiple agents share one checkout, set a distinctRUST_LANE_ID per agent when you want stable
warm local output roots.
