Repository navigation
Exercise the attested publication authority boundary - #22
Conversation
|
Caution Review failedThe pull request is closed. ℹ️ Recent review info⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (9)
📝 WalkthroughWalkthroughAdds a sandboxed Lean publication smoke test, integrates it into CI and a protected main-branch workflow, attests the generated report, retains evidence, and documents the publication-boundary status. ChangesPublication boundary validation
Estimated code review effort: 4 (Complex) | ~45 minutes Possibly related issues
✨ 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 |
|
Adversarial CI found the runner did not contain Retry tree: |
Outcome
Adds the first real publication-profile boundary for proof authority. A pinned Lean toolchain checks a committed theorem in a clean Linux job, the verifier runs inside a network-isolated Bubblewrap namespace with an enforced address-space limit, and the workflow retains a hashed candidate report plus diagnostics and an OIDC-backed GitHub artifact attestation.
The report remains explicitly non-authoritative. Canonical promotion is intentionally deferred until the engine independently verifies the attestation and all policy bindings.
Closes part of #21.
Controls
prlimitmemory enforcementValidation
bash -n scripts/publication-smoke.shgit diff --checkThe pull request stays draft until the GitHub-hosted Linux boundary passes.
Summary by CodeRabbit
New Features
Documentation