docs: codify Hive thin-adapter vision and guardrails - #50
Conversation
|
Warning Review limit reachedYou’ve reached a temporary PR review limit under our Fair Usage Limits Policy. Next review available in: 54 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. Review details⚙️ Run configurationConfiguration used: Organization UI Review profile: ASSERTIVE Plan: Pro Plus Run ID: 📒 Files selected for processing (2)
📝 WalkthroughWalkthroughThis documentation-only change adds Hive’s fork-specific vision, thin-adapter runbook, authority boundaries, isolation rules, review gates, and contributor-document routing. No exported entities or runtime behavior change. Confidence: 99%. ChangesHive thin-adapter governance
Estimated code review effort: 2 (Simple) | ~10 minutes Possibly related issues
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ Finishing Touches🧪 Generate unit tests (beta)
Comment |
|
@coderabbitai review |
✅ Action performedReview finished.
|
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 2
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Inline comments:
In `@docs/hive-thin-adapter-runbook.md`:
- Around line 102-108: Update the relay and tenant-selection rules in the
runbook to state that the URL host is authoritative for community binding; OAuth
or token claims may authenticate or narrow access but must never override the
host-derived community. Require rejecting any host/claim mismatch before
admission, while preserving the existing server-side selection and fail-closed
behavior.
In `@VISION_HIVE.md`:
- Around line 30-32: Update the signed Hive update-channel requirements in
VISION_HIVE.md and its authority table to assign ownership for the signer, key
custody, rotation, and revocation; identify the artifact-verification gate and
required release/install verification evidence; and document failure behavior
when signature verification fails. Ensure the documented ownership and evidence
prove the signed-updates invariant.
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: Organization UI
Review profile: ASSERTIVE
Plan: Pro Plus
Run ID: 68cce660-4966-411c-8455-de4e3a43a3d1
📒 Files selected for processing (3)
AGENTS.mdVISION_HIVE.mddocs/hive-thin-adapter-runbook.md
📜 Review details
⏰ Context from checks skipped due to timeout. (10)
- GitHub Check: Desktop E2E Integration (2/2)
- GitHub Check: Desktop E2E Integration (1/2)
- GitHub Check: Desktop Smoke E2E (4)
- GitHub Check: Desktop Core
- GitHub Check: Desktop Build (macOS)
- GitHub Check: Desktop Smoke E2E (3)
- GitHub Check: Desktop Smoke E2E (1)
- GitHub Check: Desktop Smoke E2E (2)
- GitHub Check: Analyze (javascript-typescript)
- GitHub Check: Analyze (rust)
🧰 Additional context used
📓 Path-based instructions (1)
**/AGENTS.md
📄 CodeRabbit inference engine (CLAUDE.md)
Follow the instructions documented in each
AGENTS.mdfile for the corresponding directory and its descendants.
Files:
AGENTS.md
🧠 Learnings (1)
📓 Common learnings
Learnt from: CR
Repo: electricsheephq/evaOS-Hive
Timestamp: 2026-07-27T07:55:51.194Z
Learning: Run `just ci` before every pull request; run `just test` for integration changes to `buzz-relay`, `buzz-db`, or `buzz-auth`.
Learnt from: CR
Repo: electricsheephq/evaOS-Hive
Timestamp: 2026-07-27T07:55:51.194Z
Learning: Prefer modeling new feature operations as Nostr events rather than adding HTTP endpoints; add HTTP only for explicitly HTTP-only surfaces such as media, webhooks, git smart HTTP, metadata, health checks, or generic Nostr bridge endpoints.
🪛 LanguageTool
VISION_HIVE.md
[style] ~167-~167: To elevate your writing, try using more formal phrasing here.
Context: ...ails. The proof is that native features keep working, the Electric patch stack stays small a...
(CONTINUE_TO_VB)
🔇 Additional comments (1)
AGENTS.md (1)
7-11: LGTM!
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: f791e26345
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
| The signed-update gate is the exact-tag release workflow in | ||
| [`release.yml`](.github/workflows/release.yml). Release evidence must bind the |
There was a problem hiding this comment.
When a Hive release candidate follows this mandatory guide, the linked workflow cannot act as its release gate: .github/workflows/release.yml restricts its setup and platform jobs to github.repository == 'block/buzz' and publishes to block/buzz's buzz-desktop-latest, while the Hive client expects electricsheephq/evaOS-Hive's hive-desktop-latest. Tagging this fork therefore skips the release jobs rather than producing the asserted Hive artifact and signature evidence; point this section to a Hive-capable workflow or implement that gate before declaring it authoritative.
AGENTS.md reference: AGENTS.md:L7-L10
Useful? React with 👍 / 👎.
1 participant
Summary
VISION.mdand add a fork-specificVISION_HIVE.mdAGENTS.mdpointer so Electric-only coding agents must read the guardrailsArchitecture decisions
Validation
git diff --cached --checkVISION.md,VISION_HIVE.md, anddocs/hive-thin-adapter-runbook.mdexist and resolve through their relative linksProof boundary
This is a documentation-only change. It does not prove current source conformance, relay isolation, artifact/release readiness, VM-agent behavior, installed parity, or customer readiness. It changes no source behavior, schema, runtime, VM, Supabase, release, or customer state.
Closes #49