docs: encode agent lane partition; point consumer examples at sluice.phoenixvc.tech#130
Conversation
…phoenixvc.tech Lane partition ratified 2026-07-03: Codex owns release/prod, Claude owns backend/security/infra. Merge authority follows the lane owner; cross-lane coordination via PR comments. Consumer base-URL examples now use the custom domain bound in PR #129 — the raw azurecontainerapps.io FQDN still works but changes if the CAE is rebuilt. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Qodo reviews are paused for this user.Troubleshooting steps vary by plan Learn more → On a Teams plan? Using GitHub Enterprise Server, GitLab Self-Managed, or Bitbucket Data Center? |
|
Warning Review limit reached
Next review available in: 41 minutes Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available. How can I continue?After more reviews become available, a review can be triggered using the 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. ✨ 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 |
There was a problem hiding this comment.
Pull request overview
Updates repository guidance docs to (1) codify an org-wide lane partition for autonomous agents and (2) switch consumer endpoint examples to the stable sluice.phoenixvc.tech custom domain instead of the ephemeral azurecontainerapps.io FQDN.
Changes:
- Added a “Lane Partition (ratified 2026-07-03)” section defining agent ownership and merge authority rules.
- Updated OpenAI/Anthropic/Claude Code consumer examples to use
https://sluice.phoenixvc.techand documented why.
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
|
|
||
| ## Lane Partition (ratified 2026-07-03) | ||
|
|
||
| Multiple autonomous agents (Claude, Codex) work phoenixvc repos concurrently. Seven documented collisions through 2026-07-03 led to this org-wide partition: |
Summary
Two related doc updates:
Lane partition (ratified 2026-07-03) — org-wide rule for the two autonomous agents working phoenixvc repos: Codex owns release/prod, Claude owns backend/security/infra. Either may open PRs anywhere; merge authority follows the lane owner; cross-lane coordination via PR comments. Matching section landing in mystira-workspace AGENTS.md (phoenixvc/mystira-workspace#2786).
Consumer endpoint examples → custom domain — the OpenAI/Anthropic/Claude-Code examples now use
https://sluice.phoenixvc.tech(bound + Terraform-managed since feat(infra): manage sluice.phoenixvc.tech custom domain in Terraform #129) instead of the rawazurecontainerapps.ioFQDN, which changes if the CAE is ever rebuilt. Raw FQDN noted as still valid.Docs-only.
🤖 Generated with Claude Code