8000 Record protected corpus export evidence by Mnehmos · Pull Request #56 · Mnehmos/MathOS · GitHub
[go: up one dir, main page]
Skip to content

Record protected corpus export evidence - #56

Merged
Mnehmos merged 1 commit into
mainfrom
docs/54-protected-corpus-evidence
Jul 22, 2026
Merged

Record protected corpus export evidence#56
Mnehmos merged 1 commit into
mainfrom
docs/54-protected-corpus-evidence

Conversation

@Mnehmos
@Mnehmos Mnehmos commented Jul 22, 2026
Copy link
Copy Markdown
Owner

Summary

  • record PR Phase 6b: deterministic MathCorpus and MCIP export #55 merge, exact-head and merged-tree CI, and protected publication identities
  • record the downloaded artifact digest, source release, corpus manifest, packet, inventory, and independent validator results
  • advance the implementation ledger to leakage-aware RL/evaluation export as the next Phase 6 slice

Validation

  • downloaded protected artifact 8516235885 with gh
  • matched all 12 corpus files and all 11 member hashes/sizes; found zero symlinks
  • confirmed byte-identical source manifest and Lean module
  • MathOS offline deterministic reprojection passed from a nonexistent instance root
  • pinned upstream packet and MCIP validators reported zero errors and zero warnings
  • git diff --check

Documentation follow-up to #54 and #55.

@coderabbitai
coderabbitai Bot commented Jul 22, 2026 •
edited
Loading
Copy link
Copy Markdown

Warning

Review limit reached

@Mnehmos, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 11 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details
⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: 279f550a-4b4c-4070-bc4a-9d15717ab775

📥 Commits

Reviewing files that changed from the base of the PR and between e977d7e and 81f7944.

📒 Files selected for processing (2)
  • docs/implementation/RELEASE_CHECKLIST.md
  • docs/implementation/STATUS.md
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch docs/54-protected-corpus-evidence

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.

❤️ Share

Comment @coderabbitai help to get the list of available commands.

@Mnehmos
Mnehmos marked this pull request as ready for review July 22, 2026 02:21
@Mnehmos
Mnehmos merged commit bd9985e into main Jul 22, 2026
6 checks passed
This was referenced Jul 22, 2026
Closed
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

No reviews

Assignees

No one assigned

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

1 participant

@Mnehmos
0