Skip to main content

Module exec_response

Module exec_response 

Source
Expand description

rch exec execution-location contract (bd-session-history-remediation-ocv9i.13.3).

Agents kept inferring where a command ran from log prose. Every explicit rch exec JSON response must instead state it outright: local-or-remote, the selected worker, the classification, a decisive reason code, the admission summary, the proof/fallback policy, and the remediation. This module is that composite contract — ExecResponse — assembled from the pieces already landed: the exec policy (crate::exec_policy), the admission vocabulary + aggregation (crate::admission_rejection), and the next-action recommendations (crate::admission_recommendation).

The cardinal invariant: local_or_remote is always present and definite, and a selected_worker exists iff the location is Remote — never the ambiguity that motivated the bead.

Structs§

ExecResponse
The composite rch exec machine response.

Enums§

ExecutionLocation
Where a command definitively executed.