docs(governance): validate policy/eval repo assumptions for MWS planning

[BrianCLong]

Motivation

• Validate and capture the real repository state for the proposed policy-gated agent execution Minimal Winning Slice (MWS) to avoid duplicating existing governance/eval infrastructure.
• Surface concrete CI and evidence artifact contracts so follow-on implementation PRs target existing policy and eval lanes rather than introducing parallel systems.

Description

• Replaced and expanded docs/repo_assumptions.md with a scoped validation ledger (scope: src/, .github/workflows/, docs/) that enumerates verified agent execution entrypoints, CI workflow surfaces, and evidence artifact conventions.
• Marked three intake assumptions as invalid because the repo already contains a governance policy engine, evaluation harnesses in CI, and runtime safety gates, and recommended extending those components instead of duplicating them.
• Added explicit next-slice guidance: emit deterministic policy_decision.json alongside report.json/metrics.json, wire CI assertions into existing eval workflows, and keep runtime enforcement behind a feature flag (default OFF).

Testing

• Ran repository discovery and evidence checks via rg searches for policy, workflow, and evidence artifacts which returned expected matches (success).
• Verified the new doc file exists and is non-empty with test -s docs/repo_assumptions.md (success).
• No code paths or unit tests were modified by this change; no server or client tests were required for this docs-only update.

---

Codex Task

[gemini-code-assist]

Warning

You have reached your daily quota limit. Please wait up to 24 hours and I will start processing your requests again!

[coderabbitai]

Warning

Rate limit exceeded

@BrianCLong has exceeded the limit for the number of commits that can be reviewed per hour. Please wait 18 minutes and 42 seconds before requesting another review.

Your organization is not enrolled in usage-based pricing. Contact your admin to enable usage-based pricing to continue reviews beyond the rate limit, or try again in 18 minutes and 42 seconds.

⌛ How to resolve this issue?

After the wait time has elapsed, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

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 configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: 2ab05dd4-1318-4245-89ed-1bfc28da5513

📥 Commits

Reviewing files that changed from the base of the PR and between cc1a6a7 and 4756a26.

📒 Files selected for processing (1)

• docs/repo_assumptions.md

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch codex/add-policy-gated-agent-execution-layer

---

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

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}