Concept Map
BMO has many feature pages, but the fastest way to understand the system is to start from the same concept families used by the primary navigation. Use this page when you know the kind of problem you are solving but not the exact feature name yet.
| Concept family | Start with | Then use |
|---|---|---|
| Core Concepts | How BMO Thinks and Acts, Stigmergic Delivery, Work Convergence | Agent Mesh, Nanites, Decision Posture, Goal Contracts |
| Sessions & Continuity | Sessions | Session Modes, Session Compaction, Auto-Checkpoint, Length Recovery |
| Workflows & Decision Forums | Workflow Map, Staged Workflow | Adaptive Orchestration, Typed topology, Arena, Patch Proposals, Change synthesis, Decision-guided software synthesis, Teams |
| Context & Workspace Intelligence | Adaptive Context, Workspace Intelligence | Workspace Trail, Workspace Observer, Persistent Memory, Semantic Code Search |
| Trust, Evidence & Recovery | Agent Debugger, Run Observability | Verdict Grades, Independent verification, Parent outcome, Quality Gates |
| Editing & Code Change Tools | Smart Apply, Apply Patch | Mutation aftercare, Edit Quality, Ripple Edits, Format on Save |
How to choose
Section titled “How to choose”Start with Sessions & Continuity when the question is about conversation state: switching, restoring, checkpointing, resuming, compacting, or recovering a long-running thread.
Start with Workflows & Decision Forums when the question is about how work moves: staging, comparing alternatives, running teams, repeating a workstream, or choosing between candidate answers.
Start with Stigmergic Delivery when the question is about indirect coordination: work leaving signals in the workspace, pressure building in zones, and operators reading what deserves attention next.
Start with Work Convergence when the question is whether a task-bearing run is actually closing: pre-write reads, verification recovery, repeated read-only turns, durable writes, and terminal verdicts.
Start with Trust, Evidence & Recovery when the question is “what happened, can I prove it, and how do I recover?”
Start with Editing & Code Change Tools when you are focused on file mutation mechanics, patch application, edit validation, or rollback envelopes.
Important boundaries
Section titled “Important boundaries”Some concepts happen inside the same runtime but answer different questions. Arena runs inside a session, but it is a decision forum for comparing candidate answers, not a session-continuity primitive. Use Sessions for conversation lifecycle and Arena for during-turn comparison.
Auto-Checkpoint covers git micro-commits and session checkpoint operations. Use the Sessions hub to choose between a new session, a branch, a session checkpoint, or a git undo. Mutation aftercare is the change-contract reservation for a file effect. It is a third record, beside git commits and session checkpoints.
Change synthesis retains a reviewable proposal from a declared specification. Decision-guided software synthesis traces that ranking through apply, aftercare, and the parent check. Independent verification and Parent outcome remain separate decisions.
Stigmergic Delivery and Work Convergence overlap but do not replace each other. Stigmergy asks what the workspace should help future actors notice; work convergence asks whether the current task frontier has reached an observable outcome.