Guides

Adopting the gate, reading its output, and extending it.

• Quickstart

  the one-screen version.

• Onboard the complete BCE stack

  preferred current-agent authoring path with no second model account.

• First win — choose the boundary that must hold

  install v0.3.1, run npx --no-install bce demo --list, then a real GREEN/named-RED proof for extension contracts, tenant route guards, governed egress, TypeScript or Python module layering, or configuration allowlists.

• AI-first blueprint proposal and review

  optional provider-backed proposal with bounded disclosure and one immutable review packet.

• Adopt bce on an existing repository

  the ladder — advisory → baseline → graduate → enforced; the honest brownfield story.

• Solo-steward ratification

• Adoption lifecycle

• Running bce inside an agent loop

  per-harness (Claude Code / Cursor / generic MCP); the violation→fix→re-gate loop.

• Visual guide to C1–C4

  diagram-led explanation of required components, required edges, forbidden imports, and forbidden component paths.

• TypeScript module graph — enforce direct architecture boundaries

  direct-boundary selectors, deterministic resolution, unresolved-import behavior, and explicit non-goals.

• Python module graph — enforce direct architecture boundaries

  structured direct imports, explicit roots, fail-closed uncertainty, and explicit non-goals.

• Live self-adoption

  read the GitHub-backed main-commit pipeline, its refresh behavior, authenticated records, and evidence boundaries.

• Self-hosting: the engine gates its own tree

  bce gates its own tree; Lane A/B, the bootstrap-0 exception, the Lane-A pin ceremony, the admin-override incident policy.

• Accelerated dogfooding

• The agent estate: what happens when the PR author is not a person

• Exit codes

  0 = command success (advisory may still be RED), 1 = violation/user-error, 2 = fail-closed refusal; read the structured verdict.

• The report contract

  the deterministic compliance report; determinism and canonical serialization.

• The bce evidence format — hash-chained, re-derivable, tamper-evident

  the hash-chained evidence record + the zero-dependency verifier.

• bce-engine@0.2.0 release verification

• bce-engine@0.3.0 release verification

• bce-engine@0.3.1 release verification

  exact npm/source identities, signed release assets, installed consumer checks, and explicit limits.

• MCP compatibility contract

• Portability contract

• Scale and detection evidence

• Extending the engine to a new language

• The Lane-A pin ceremony

• How bce compares

• Governance enforcement

• Maintainer operations — one human, one visible queue

  intent-shaped intake, canonical queue labels, the read-only 168-hour response audit, and the no-phantom-review boundary.

• BCE credibility hardening plan — 2026-09-02

• Credibility hardening closeout — 2026-09-02

• FAQ

  why baseline is not a bypass; why there is no skip flag.