GuardRail

Both of us used IBM Bob as a continuous engineering partner across the entire build of GuardRail, our canary deployment verifier. Bob's contribution was not a single feature — it was four recurring roles, all inside the ibm-bob-2.0 workspace, with full-repository context on every task (up to 166k of a 270k context window). 1. Onboarding and orientation. Early on, we handed Bob the whole monorepo plus docs/TEAM.md and asked it to read both the plan and the code, then report: the full scope of our track, its dependencies on other tracks, deadlines and sequencing, what was already built, what was missing, the patterns and architecture decisions to follow, and any blockers. We then asked for a concrete, prioritized starting plan — one specific file or module to begin with, plus the next 3–5 steps. Bob cross-referenced the docs against reality and returned exactly that. That plan became our working order for the sprint. 2. Spec-driven implementation. We treated CONTEXT.md — our own glossary of 12 domain terms with explicitly forbidden synonyms — as the source of truth, and instructed Bob to implement the required dashboard functionality against it: install shadcn/ui through its CLI, design a professional-looking UI, and build a modular code approach with composable components rather than giant monoliths — asking us questions instead of guessing whenever anything was unclear. Bob wrote the pages, route handlers, hooks, and component modules that make up the operator UI. 3. Review and audit before every test cycle. We asked Bob to conduct a thorough review of the monorepo and judge whether it was ready to be exercised through the dashboard once the stack came up via docker compose. Bob cross-checked implementation against spec, flagged contract drift, and surfaced defects we would otherwise have discovered mid-demo. 4. Documentation, domain modelling, and safety. Bob drafted our ADRs, the operational run guide, the long platform reference, and a visual end-to-end walkthrough artifact. It also produced the doc-ingest output behind our criticality map. We used .bobignore to keep credential-shaped strings out of Bob's session history.