Phase G: verifier-derived training rewards with kernel-observed divergence penalty - #65
Merged
Merged
Conversation
…divergence penalty
Contributor
Author
|
@droid review |
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.
What
diverged_observed) intoexport_verifiers.py:rollout_vectorcontext during training rollouts.context.get("diverged_observed")inLumenVerifierandwrap.pyverifier generator: when engine info lacks a divergence channel, non-finite tags observed across full episode steps correctly markdiverged = True.divergedmetric toTrue, driving declarative projection to 0.0 without manual reward shaping.tests/test_eval_run.pycovering verifier divergence gate failure underdiverged_observed.docs/NEXT_STATUS.mdledger reflecting D5 cloud parity (feat: Phase D5 explicit cohort subgroup validation, head-covered trial bindings, and clustered continuous bootstrap #64, vector-cloud Phase 5: decision rule and contestation #5) and Phase G training reward adoption.Why
Phase G requires that verifier-derived training rewards reflect authoritative vectors rather than fabricated physics or unobserved convergence. Wiring kernel-observed divergence ensures diverged solver rollouts penalize training rewards directly.
Verify
uv run ruff check --fix && uv run ruff format --check && uv run mypyclean.