Operator Cognition Parity
Operator cognition parity
Section titled “Operator cognition parity”Operator cognition readout exposes a read-only, ledger-bound summary of recommendation follow-through over the calibration window. It does not infer operator psychology from chat and does not grade operators.
Maturity: Maintainer-facing reference surface. Use it for remote inspection, automation, and parity checks across HTTP, CLI, agent, and MCP access.
Surfaces
Section titled “Surfaces”The same payload is available through:
- HTTP:
GET /v1/operator-cognition - CLI:
bmo stigmergy cognition --json - In-agent tool:
operator_cognition_readout - MCP:
bmo_operator_cognition_readout(when stigmergy read tools are enabled) - TUI:
/cognitionand zone drill-ins (see maintainer topic)
The HTTP route and in-agent tool both call App.OperatorCognitionReadout in
internal/app/operator_cognition_readout.go.
Request controls
Section titled “Request controls”Optional zone filter (exact signal zone):
- HTTP query param:
zone - CLI flag:
--zone - Tool / MCP param:
zone
Omitted or empty zone returns a global readout across zones in the window.
Authentication
Section titled “Authentication”GET /v1/operator-cognition is a protected route. Send Authorization: Bearer <token>
when the server is configured with an auth token (same as other /v1/ parity routes).
Availability
Section titled “Availability”Returns 503 when the recommendation outcome ledger is unavailable (for example
no bmo.db on the server app). This route is not gated on
options.workspace_observer.enabled.
Canonical fields
Section titled “Canonical fields”See operator-cognition-readout.md
for schema_version, patterns, warnings, and evidence-bound semantics.
Relationship to runtime features
Section titled “Relationship to runtime features”runtime_features distinguishes the two access paths:
operator_cognition_apioperator_cognition_tool