Explanation

Understand why. The conceptual spine — architecture, rationale, and the trade-offs behind BoB’s design. (Back to docs home.)

Note	Explains
The Minimal BOB_HOME Core	The #1132 demotion audit — the invariance test, keep/demote classification of every universal item, dependency floor, and context-tax measurement.
BoB Identity	What "BoB" is — the identity definition behind the tooling.
DESIGN.md in BoB	How Google Labs’ DESIGN.md format fits BoB provisioning — placement, opt-in, the design-skill family, Stitch as upstream.
Doc-Bootstrap	Why doc-bootstrap is shaped this way — one-target/three-verbs, the convergence + fixpoint invariants, tiers, code-grounding.
Orchestration (section)	The single home for orchestration — the handbook (narrative) and the orchestrator (recommendation engine).
Prime Directive	Declarative, version-controlled, idempotent, one-owner-per-fact.
Project Monitor Exposure Posture	Why the Project Monitor is tailnet-only — what it would take to justify a public URL, and the bind guarantees that enforce the decision in code.
A Day in the Life of a BoB Workday	One realistic developer day end-to-end — bug fix, feature, docs, parallel, farm — narrated around the seams between commands, with L1/L3 variants.

See also the product Vision (the living strategy doc, kept at the docs/ root by convention).