[codex] add agent eval failure packet#10
Merged
Conversation
5089400 to
b6b70a3
Compare
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.
Summary
Adds a concrete, machine-checkable agent eval data packet to
self-improving-loop:docs/ANNOTATION_GUIDELINE.mddefines failure labels, hard vs soft signals, and routing policy.docs/AI_CODING_TOOL_FAILURE_NOTES.mdmaps Claude Code / Cursor / OpenClaw / Hermes failure modes into labels and guard actions.examples/agent_eval_cases.jsonladds 30 non-authorizing eval cases.examples/verify_agent_eval_cases.pyverifies schema, labels, unique case IDs, and hard no-execution flags.tests/test_agent_eval_cases.pylocks the packet boundary in CI.Why
This turns the project from only a regression-rollback runtime into a clearer reliability data asset: traces can now be mapped into failure labels, eval cases, and conservative routing without granting execution authority.
Safety boundary
The packet is eval data only. The verifier enforces:
Validation
Results: