docs: document readiness and surveillance semantics - #413
Conversation
Move exact-head, hourly commercial, and acquisition-audit procedure out of the product README into CONTRIBUTING and existing docs. Keep MSA: Noema runs alone without Naruon; siblings call /exchange and the review runtime uses the contextual-orchestrator gateway. Co-authored-by: Seongho Bae <seonghobae@users.noreply.github.com>
|
Warning Review limit reached
Next review available in: 29 minutes Limit details: You’ve used all 1 included review currently available under your plan. You've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository. 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. Review details⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (6)
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 |
seonghobae
changed the title
|
Bugbot is not enabled for your account, so this pull request was not reviewed. Enable Bugbot in the Cursor dashboard to get automatic reviews on future PRs. |
2 participants
Summary
Preserves the unique operator/readiness documentation from the earlier buyer-README branch after PR #415 became the canonical customer-facing README implementation.
The branch was non-destructively reconstructed on protected
main58af7cfcb8f171bcef7bf0b7e3d6d9bd3090ef7a; README, CONTRIBUTING and CHANGELOG now come from protected main rather than competing with #415.Current bounded delta
docs/api-spec.mddocuments/healthas liveness-only and adds the publicGET/HEAD /readycontract, including 200 ready, 503ERR_SERVICE_NOT_READY,Retry-After, method and readiness headers while preserving newer protected repository-path validation text.docs/deployment-guide.mdrequires/readybefore/exchangetraffic and includes readiness in smoke verification.docs/onboarding.mdincludes standalone readiness verification and explicitly does not require Naruon.docs/acquisition-readiness-2b.mddistinguishes scheduled acquisition surveillance (NOT_READYevidence) from fail-closed manual/local audit.docs/saleable-program-goal-registry.mddocuments the same surveillance boundary and the security-validation checklist gate.docs/saleable-program-readiness.mdrecords that buyer README procedure moved toCONTRIBUTING.md/docs/.Supersession / ownership
PR #415 already integrated the customer-facing README and relocated agent procedure. This PR no longer modifies README, CONTRIBUTING or CHANGELOG and does not race canonical architecture/documentation PR #71.
No runtime, workflow, release, deployment, legal-rights or acquisition-ready claim is introduced.
Current exact head
ee2b1c1800c0fa7c8b1ede097e76f5ab42bd52a4Fresh exact-head CI/reviewer/Security evidence must pass on this unchanged head before Ready/merge classification. Predecessor evidence does not transfer.