_output-protocol

Use a canonical output protocol with a single-line verdict, emoji dimension table, and conditional next-steps to standardize fleet skill outputs. This fixed formatting makes operational results scannable within seconds and reduces signal drift across multiple hosts.

A standard fleet reporting format includes a single-line verdict, an emoji dimension table, and conditional next-steps. It enforces dedicated safety states for refused and paused operations to prevent unsafe actions and clearly flag blocked execution.

Format next steps using deterministic rules that conditionally render the section only when action is needed. This approach provides exact command and copy guidance, preventing clutter when fleet operations report standard OK statuses.

Yes, the output protocol enforces Spanish reporting rules, fixed emoji semantics, and strict formatting and length constraints. These rules ensure deterministic output generation and reduce signal drift across repeated fleet runs on multiple hosts.

Use dedicated refused and paused states when fleet operations encounter unsafe conditions or manual blocks. These safety-aware states prevent unsafe execution and clearly distinguish blocked outcomes from standard errors or warnings in the operational output.

Reduce signal drift by applying a strict output protocol with fixed emoji semantics and a canonical verdict line across all repeated runs. Standardizing the final operational output format ensures consistent status reporting across every host and project.