Closed
Add operational-value grader for daily-caveman-optimizer#58557
Conversation
Co-authored-by: mnkiefer <8320933+mnkiefer@users.noreply.github.com>
Co-authored-by: mnkiefer <8320933+mnkiefer@users.noreply.github.com>
Copilot
AI
changed the title
[WIP] Design operational-value grader for daily caveman optimizer
Add operational-value grader for daily-caveman-optimizer
Sep 4, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
daily-caveman-optimizerhad no deterministic operational-value grader. This adds one, following.github/skills/operational-value-designer/SKILL.md, measuring whether the workflow's conciseness edits actually stick in the repository rather than counting activity or trusting agent self-assessment.Design
9b89368509...) — trim.github/aw/.github/agentsinstruction files for conciseness without losing accuracy, in daily batches of 5.pr-description-caveman) rewrites merged PR bodies on every merge, wiping out the usualgh-aw-workflow-id/run-id footer marker (confirmed against real PRs [caveman] Optimize instruction verbosity — network.md (2026-09-01) #57777, [caveman] Optimize instruction verbosity — evals.md (2026-08-28) #56727). Assignment instead searches for the run's PR by title prefix, labels, author, and a bounded time window after run start — classifiedbounded-ambiguityrather than fully deterministic.pr-reduction-durability, direct,[0,1]): fraction of the PR's own claimed line reduction (from its files API) still present at the evidence cutoff. This avoids inventing an arbitrary target-lines threshold (no such convention exists for markdown, unlike Go source), and directly penalizes reverted or regrown trims:attainment-only— no prior automated/manual instruction-trimming activity existed before adoption.batch-size-ratio(files touched / 5), reported separately from the primary value.Changes
.github/graders/daily-caveman-optimizer-operational-value.sh— new evaluator (--definition/--metric/--grade-run).github/graders/daily-caveman-optimizer-operational-value-study.json— study record (designOutcome: accepted) documenting the design decisions and uncertainties above.github/workflows/daily-caveman-optimizer.md— wires ingraders.operational-value.github/workflows/daily-caveman-optimizer.lock.yml— recompiledOriginal prompt