Limitations and maturity map
Evaluators should read this before assuming every feature page is daily-use product. BMO ships a large surface; maturity labels distinguish regular workflows from measurement-only and research paths. They are navigation guidance, not a guarantee of suitability for a particular deployment.
Release compatibility and versioning
Section titled “Release compatibility and versioning”- Release tags identify the supported CLI and on-disk behavior for that release line.
- Pin a release tag when stability matters more than latest features.
- Local builds report
develorgit describe— see Versioning.
Maturity labels
Section titled “Maturity labels”From About This Book:
| Label | Meaning |
|---|---|
| Daily-use | Starting point for regular coding and review |
| Advanced | After you understand the main workflow, or for scripts/teams |
| Maintainer-facing | Contributors, support, source-level diagnosis |
| Eval-only | Measurement; does not grant runtime authority by itself |
| Reference | Dense contracts — consult when you know what you need |
Should I care? (top surfaces)
Section titled “Should I care? (top surfaces)”| Surface | Label | Day one? | Link |
|---|---|---|---|
TUI / bmo run | Daily-use | Yes | Quickstart |
| Session modes | Daily-use | Yes | Session modes |
| Patch proposals | Daily-use | When reviewing agent edits | Patch proposals |
bmo synthesize | Advanced | Only with a declared specification | Change synthesis |
| Parent outcome | Advanced | Provisioned controller only | Parent outcome |
| Staged workflow | Advanced | Optional plan gate | Staged workflow |
| Automation / autopilot | Advanced | CI and background | Automation |
| Multi-agent / claims | Advanced | Only when parallelizing | Multi-Agent Workflows |
| Agent mesh / A2A | Advanced | Remote delegation | Agent mesh |
| Arena | Advanced | Model comparison | Arena |
| Agent debugger | Maintainer-facing | After something breaks | Agent debugger |
| Shadow evals | Eval-only | Quality programs | Shadow evals |
| Stigmergic delivery | Advanced (research preview on feature page) | Not day one | Stigmergic delivery |
*-parity reference pages | Reference | Integrators | Reference |
Product boundaries
Section titled “Product boundaries”- Not a hosted IDE — terminal and integration surfaces; no turnkey web IDE.
- Not default fully autonomous — approval and visibility are intentional.
- No first-party private MCP tunnel — operator supplies network path; see Enterprise networking.
- Workspace claims are process-local — not filesystem locks across machines.
- Release compatibility — plan for format and CLI evolution between release lines.
Concept, recorded evidence and current qualification
Section titled “Concept, recorded evidence and current qualification”The homepage’s synthesis map is a proposed integration. A feature’s presence in
that map does not establish that the full loop is accepted. The
proof gallery labels conceptual scenes, the bounded
bmo synthesize command, historical fixture evidence, and the narrower
qualified delegation envelope separately.
Change synthesis retains a reviewable proposal
from a declared specification. It does not apply that proposal or accept a
parent objective. The executed penalty example and the failed parent check
are on Decision-guided software synthesis.
Check the revision, configuration and stated limits of a
receipt before using it to support a deployment decision.
Related
Section titled “Related”- Why BMO — workflow fit
- Decision guide — what to ignore initially
- Proof gallery — scenario evidence