docs(policy): clarify non-Rust allowlist rollout status (#201, rollout PR 1/12)#213
Conversation
Rewrites the rollout-status sections in FILE_POLICY.md and POLICY_ALLOWLISTS.md to reflect that the 0.4.0 file-policy work is decomposed into a 12-PR ladder of small, separately reviewable changes rather than one large policy-infrastructure PR. Adds explicit "receipts, not burn-down" language: - The allowlists mean "known surface, owner, reason, and current disposition." They do not mean "approved forever." - A valid `reason` may include "scheduled to be converted to Rust/xtask" when the file exists for legacy compatibility or migration staging, paired with an `expires` date. Adds a new tracker doc, docs/policy/NON_RUST_ROLLOUT.md, with: - The operating rules (receipts not burn-down; advisory before blocking; no blocking-strict in this rollout). - The full 12-PR ladder with issue numbers, status, and dependencies. - The receipt schema with durable and transitional examples. - The definition of done for the ladder. Closes #201.
|
Warning You have reached your daily quota limit. Please wait up to 24 hours and I will start processing your requests again! |
|
You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard. |
|
Droid finished @EffortlessSteven's task —— View job Validation Complete ✓PR #213 — docs(policy): clarify non-Rust allowlist rollout status 2 comments posted, 0 rejected, 0 security items.
Both are minor consistency issues. No correctness bugs or security issues found — this is a docs-only structural change. |
|
Warning Rate limit exceeded
You’ve run out of usage credits. Purchase more in the billing tab. ⌛ How to resolve this issue?After the wait time has elapsed, a review can be triggered using the We recommend that you space out your commits to avoid hitting the rate limit. 🚦 How do rate limits work?CodeRabbit enforces hourly rate limits for each developer per organization. Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout. Please see our FAQ for further information. ℹ️ Review info⚙️ Run configurationConfiguration used: Organization UI Review profile: ASSERTIVE Plan: Pro Run ID: 📒 Files selected for processing (3)
✨ Finishing Touches🧪 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 |
Summary
First PR in the 12-PR file-policy rollout decomposition. Docs-only — no policy files yet, no code changes, no enforcement.
Rewrites the rollout-status sections in
docs/FILE_POLICY.mdanddocs/POLICY_ALLOWLISTS.mdto reflect the 12-PR ladder rather than the old single-PR view. Adds explicit "receipts, not burn-down" language so future receipts can legitimately carryreason = "scheduled to be converted to Rust/xtask"paired with anexpiresdate.Adds a new tracker
docs/policy/NON_RUST_ROLLOUT.mdwith:blocking-strictin this rollout).Issue
Closes #201. Refines #180 (umbrella). Tracks #109.
Decisions
docs/policy/as a new subdirectory rather than putting the tracker indocs/ci/or atdocs/root.docs/NON_RUST_ROLLOUT.md— works for one file but doesn't scale.FILE_POLICY.mdand the tracker.expires).Validation
cargo check --workspace --lockedpasses (no source code touched).policy/directory created in this PR (that's PR 2 / chore(policy): add non-Rust policy allowlist ledgers (rollout PR 2/12) #202).xtask/directory created (PR 4 / feat(xtask): add non-Rust inventory command (rollout PR 4/12) #212).Follow-ups
PR 2 (issue #202) — add the policy TOML ledger files with first-pass receipts. No checker, no behavior change.