Repository navigation
Record claim-edit policy transitions omitted from cost reports - #10579
Merged
Merged
Conversation
gunbai-bot
Bot
changed the title
added 2 commits
September 5, 2026 16:00
…wt-660/roster-transition-failure-mode # Conflicts: # dag/gunbc/recurring_failure_mode/roster.dag
Contributor
Author
|
Addressed review 60984 in 397bc9a. DESIGN.md §6 explicitly prohibits the numeric receipt transcriptions: removed step totals, percentages, CPU observations, population counts and log-counter values from the authority row. Retained run/artifact references and qualitative consequences, and named the claim_executor entry point plus write_required_floor_claim_cost_tsv / write_required_floor_disposition_tsv. The row explicitly distinguishes the manual reconciliation from a repository-enforced producer that does not yet exist. Formatting and diff checks pass. Fresh review, generated-document regeneration and final-head CI are pending; this is not merge-ready. — sent from still-newt-660 |
added 4 commits
September 5, 2026 16:41
…-transition-failure-mode # Conflicts: # dag/gunbc/recurring_failure_mode/roster.dag
Ledger-Repair-Judged: docs/design-failure-modes.md Ledger-Rows-Repaired: docs/design-failure-modes.md claim_edit_changes_execution_policy_outside_reported_cost_delta Ledger-Repair-Judged: docs/design-rung-drops.md
…-transition-failure-mode # Conflicts: # dag/gunbc/recurring_failure_mode/roster.dag # docs/design-failure-modes.md
Ledger-Repair-Judged: docs/design-failure-modes.md Ledger-Rows-Repaired: docs/design-failure-modes.md claim_edit_changes_execution_policy_outside_reported_cost_delta Ledger-Repair-Judged: docs/design-rung-drops.md
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
1 participant
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.
Cost-reduction reports in #10538 and #10530 omitted executions admitted by incidental claim-body edits. #10538 reported real savings on six claims while its full corpus grew 547,358 eval_steps. Add the failure-mode authority row
claim_edit_changes_execution_policy_outside_reported_cost_deltaand append it to the roster without reordering existing entries.The row separates two mechanisms: cost-debt admission invokes an explicitly announced verdict-only cost policy; #10542 instead changed the adjudication of already-executing route-gap claims and CI correctly blocked. It does not describe route-gap or expected-red rosters as skip lists, claim every edited witness loses its CPU deadline, or confuse the 100ms optimization objective with the enforced 500ms line.
This is a distinct class from
non_execution_undifferentiated_by_what_it_silenced: that row lacks purpose ranking for non-verdicts, whereas this one requires complete execution and policy transition accounting between run subjects.selection_view_read_as_populationis also distinguished explicitly. The new row carries invalid state, harm, measured receipts, recognition rule, current mitigation, attainable ceiling and a next trigger requiring an actual reporting consumer with discriminating controls. No enforcement change is claimed.Validation:
cargo fmt --all,git diff --check, receipt-string syntax and required-field checks, and strict append verification for the roster.docs/design-failure-modes.mdis not hand-edited:DesignFailureModesArtifactdelegates regeneration toheal-generated-artifacts; its generated output and final-head checks remain required before landing.