operational-value-designer

# Operational Value Designer Design the smallest deterministic grader that measures whether one workflow run produced its intended operational outcome. Put domain knowledge in the evaluator, not in generic runtime infrastructure. Operational value is demonstrated progress toward the workflow's intended real-world or repository outcome. It is not agent activity, token usage, output volume, tool usage, or an agent's claim that it succeeded. The core task is semantic translation: ```text workflow title + description + intent + effective instructions -> real goal and applicable subject -> observable evidence -> deterministic per-run metric function ``` The evaluator belongs to one workflow and runs whenever that workflow is graded. It must measure that workflow's goal for the current run. It is not a generic safe-output checker: safe outputs are only one possible evidence source and may be irrelevant, insufficient, or merely an intermediate request. ## Deliverables Choose one evaluator form. For a compact evaluator, embed the complete Bash program in the workflow so it travels with the Markdown: ```yaml graders: operational-value: name: Maintainer Time Saved description: Maintainer effort avoided by the current run's accepted outcome unit: hours direction: higher_is_better script: | #!/usr/bin/env bash set -euo pipefail request=$(cat) # Compute and print the ordered metric array. ``` For a larger evaluator, create one e...