Differentiated local body

Use the differentiated local body view when you need to understand what a BMO instance is, what state it is in, what it can do, and which transition explains its current authority. The lifecycle inspector turns those answers into one operator-facing readout so you do not have to cross-check agent kinds, worker rows, and substrate artifacts by hand.

Internally this capability is called the differentiated local body (DLB).

Operator-visible surfaces

• Lifecycle inspector — TUI command lifecycle_inspector (aliases lifecycle, dlb-lifecycle) or the get_lifecycle_inspector tool: a read-only composed view of class, lifecycle, and related advisory fields. Payloads are versioned; treat fields as evolving with the product.
• Autonomic posture — Explore vs consolidate precedence where posture is wired. See Adaptive Orchestration.
• Workspace drill-ins — Spatial / trail context complements DLB but does not replace class/state/authority; see Workspace trail and Workflow map.

Fleet and external metrics

Cross-session push health signals are opt-in and scoped to individual instances — they do not aggregate into fleet-wide shared metabolism. Read Fleet and external metrics before product copy or integrations that mention fleet-scale inputs.

Optional supporting capabilities

Beyond the foundational contract, BMO may expose optional mechanisms (for example signed transfer bundles, arena-linked promotion flows, inspector advisory fields, or habitability-style aggregates). What is on by default and what is opt-in can vary by configuration and build; prefer the inspector and Configuration over memorizing milestone IDs.

For contributors: See the differentiated local body maintainer topic and the lifecycle inspector maintainer topic.

Where to go deeper

Use this guide as the field orientation for DLB-shaped behavior: what to inspect, which surfaces matter, and where the boundaries are. For day-to-day use, start with the lifecycle inspector and configuration reference. For implementation sequencing and edge-case matrices, use the contributor references in the maintainer reference profile.