Repository navigation
Phase 6c: leakage-aware RL and evaluation export - #58
Merged
Merged
Conversation
📝 WalkthroughWalkthroughAdds a deterministic, leakage-aware RL evaluation export pipeline with schemas, domain validation, CLI commands, offline verification, Pilot A publication integration, documentation, and tests. ChangesRL evaluation export
Sequence Diagram(s)sequenceDiagram
participant ReleaseCLI
participant RLExporter
participant FrozenReleases
participant PublishedExport
ReleaseCLI->>RLExporter: export-rl with plan and source root
RLExporter->>FrozenReleases: load manifests, receipts, records, and evidence
RLExporter->>RLExporter: derive leakage components and task projections
RLExporter->>PublishedExport: publish manifest and export members
ReleaseCLI->>RLExporter: verify-rl-export with expected manifest hash
RLExporter->>PublishedExport: verify inventory and member hashes
RLExporter->>FrozenReleases: reproject from independent plan and sources
RLExporter-->>ReleaseCLI: return verification report
Possibly related issues
🚥 Pre-merge checks | ✅ 3 | ❌ 2❌ Failed checks (2 warnings)
✅ Passed checks (3 passed)
✨ Finishing Touches📝 Generate docstrings
🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
6 tasks done
Mnehmos
marked this pull request as ready for review
July 22, 2026 03:32
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: e1901c75e5
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
This was referenced Jul 22, 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.
Advances #57; keep the issue open through protected execution and independent artifact audit.
Summary
rl_export_plan/1,rl_task/1,rl_leakage_report/1, andrl_export_manifest/1contracts with committed offline schemasheld_out_evaluationand require already-public licensed releases for train, validation, or public testrelease export-rlandverify-rl-export, trusted-hash verification, exact inventory/schema/task/evidence policy checks, and byte-identical reprojectionLocal evidence
cargo fmt --checkcargo clippy --workspace --all-targets --all-features -- -D warningscargo test --workspace(167 library tests plus all integration suites)python -m compileall -q src testspython -m unittest discover -s tests -v(39 passed)bash -n scripts/release-pilot-a.sh91fa7a720c9ed0d530742c9c519cdb6f9944aa8545339d00e15e02f6846aac78, 30 members, 10 tasks, one held-out component, six emitted families, all tasks private, zero cross-claim fidelity variants, zero member mismatches, zero forbidden reasoning fieldsReview focus