feat: claim-coupled decay for session_budget (eval 75-77, 77/77) - #19
Open
kindrat86 wants to merge 1 commit into
Open
feat: claim-coupled decay for session_budget (eval 75-77, 77/77)#19kindrat86 wants to merge 1 commit into
kindrat86 wants to merge 1 commit into
Conversation
Port the claim-coupled decay feature (authored 2026-08-12, suggested by @yun520-1 on OpenClaw #42475). When a transaction stamps an unverified_claims count, session_budget decay switches from spend-based to claim-based tightening: per-call cap = max_session * decay_factor ** unverified_claims. Malformed counts fall back to spend-based decay. Adds 3 eval scenarios (75-77), bringing the eval gym to 77/77 across 12 categories. Sweeps the stale 74 -> 77 scenario count across marketing copy (README, PACKAGE_README, core/api.py blog meta + nurture emails, public/*.html, content/*.md, scripts).
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
2 participants
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.
Summary
Rescues the claim-coupled decay feature that was stranded on a stale local branch (authored 2026-08-12, never PR'd). Ports it onto current main.
What it does
When a transaction stamps an
unverified_claimscount, thesession_budgetrule switches from spend-based decay to claim-based tightening:An agent carrying 3 unproven assertions gets a tighter admission threshold than one at 0, regardless of elapsed time or spend. Malformed counts fall back to spend-based decay. Suggested by @yun520-1 on OpenClaw #42475.
Changes
core/engine.py+agentshield/engine.py: claim-coupled decay in_check_session_budgettests/eval_gym.py+agentshield/eval_gym.py: 3 new scenarios (75-77), both copies kept in sync (fixes the twin-drift the original commit introduced by only touchingtests/)74->77scenario count across README, PACKAGE_README,core/api.py(blog meta + nurture emails),public/*.html,content/*.md, scriptsVerification
tests/eval_gym.pyandagentshield/eval_gym.py)