Define Vibe Deploy proof chain for open Runtime

[squaeragent]

Summary

• document Vibe Deploy as the optional proof-chain ceremony connecting an operator-owned Runtime to the ZERO control plane
• clarify that public Runtime remains paper-first, self-hosted/operator-owned, and useful without app/control-plane connection
• link the proof-chain doc from README, Railway deploy/template docs, and open-core boundary
• regenerate docs/llms-full.txt

Safety

• documentation-only
• no runtime behavior changes
• no live execution changes
• no custody or Builder Code defaults introduced

Verification

• just docs-check — passed
• just public-readiness — passed
• just public-proof — passed

Summary by CodeRabbit

• Documentation
  • Added comprehensive Vibe Deploy Proof Chain documentation for operator Runtime connection to the control plane
  • Updated operator onboarding checklist with Runtime claim and heartbeat verification steps
  • Enhanced deployment guidance with Vibe Deploy procedures and verification commands
  • Clarified platform boundary rules for optional Vibe Deploy integration and operator code authority requirements

[coderabbitai]

Warning

Rate limit exceeded

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

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 @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: defaults

Review profile: CHILL

Plan: Pro

Run ID: ef6a2be0-450d-4650-8df0-f65f837694eb

📥 Commits

Reviewing files that changed from the base of the PR and between 0942132 and 23375de.

📒 Files selected for processing (11)

• README.md
• docs/autonomous-os-plan.md
• docs/llms-full.txt
• docs/open-core-boundary.md
• docs/private-engine-capability-gap-audit.md
• docs/railway-deploy.md
• docs/railway-template.md
• docs/releases/v0.1.1.md
• docs/vibe-deploy.md
• scripts/generate_llms_full.py
• scripts/public_readiness_gate.sh

📝 Walkthrough

Walkthrough

This PR introduces documentation for the Vibe Deploy Proof Chain, an optional trust ceremony connecting operator-owned ZERO Runtimes to the control plane. Changes span the core specification, architectural boundaries, operator workflow integration, and Railway deployment guidance, with synchronized updates to bundled LLM-context files.

Changes

Vibe Deploy Documentation

Layer / File(s)	Summary
Vibe Deploy Proof Chain Specification docs/vibe-deploy.md	New guide defining the proof-chain steps (claim, heartbeat, paper acceptance, control-plane recording, authority approvals, revenue grants), safety rules, responsibility boundaries, and verification/gating commands; specifies that /live/preflight is refused by default in the public Runtime until authority ceremony completes.
Architectural Boundaries and Security Rules docs/open-core-boundary.md, docs/llms-full.txt	Adds boundary rules requiring Vibe Deploy to be optional and receipt-backed with separate proof steps for ownership, liveness, paper capability, authority, and execution lease; specifies Builder Codes as explicit operator-approved revenue authority, not a hidden default.
Operator Proof Path Integration README.md, docs/llms-full.txt	Integrates Vibe Deploy into the Operator Proof Path checklist as a required first step (claim Runtime + verify heartbeat before treating as owned), renumbers subsequent steps, and adds documentation links to docs/vibe-deploy.md in both Deployment and Documentation index sections.
Railway Deployment Guidance docs/railway-deploy.md, docs/railway-template.md, docs/llms-full.txt	Adds Vibe Deploy ceremony instructions (claim-token + heartbeat liveness proof) for connecting Railway Runtime to control plane; includes post-deployment verification flow and warning against adding private keys or fee settings to public template; syncs guidance across Railway hosting copy and Marketplace overview sections.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~12 minutes

Possibly related PRs

• zero-intel/zero#41: Both PRs modify the README and docs "Operator Proof Path" checklist; this PR adds the optional Vibe Deploy proof-chain step and renumbers the proof sequence.

Poem

🐰✨ A proof chain hops through the clover,
Claiming runtime, heartbeats hover,
Vibe Deploy weaves trust so true,
Paper trails mark boundaries too! 🌟

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title accurately reflects the main change: defining and documenting the Vibe Deploy proof chain for open Runtime deployments.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch codex/open-runtime-release-readiness

---

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.}

[coderabbitai]

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/llms-full.txt`:
- Line 647: The bundled full-context document is missing the referenced source
file; update the "## Sources" block and the embedded source sections in the
full-context doc to include the contents of vibe-deploy.md so retrieval has the
actual proof text instead of just backlinks; locate the "## Sources" section and
the embedded source markers in the full-context doc (search for the reference to
vibe-deploy.md) and append or regenerate the embedded content for vibe-deploy.md
so it appears inline with the other sources.

In `@docs/vibe-deploy.md`:
- Around line 65-71: Remove the stateful /deployment/claim curl from the generic
verification snippet shown (the block with curl -fsS "$ZERO_RUNTIME_URL/...")
and replace it with the remaining idempotent checks (health, heartbeat,
audit/export, live/preflight); additionally add a short note that
/deployment/claim is a single-use operation and must be executed only once via
the dedicated claim ceremony flow rather than included in repeatable health
verification commands.

🪄 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: defaults

Review profile: CHILL

Plan: Pro

Run ID: 1ff4e760-0831-4473-9230-841f9089b22a

📥 Commits

Reviewing files that changed from the base of the PR and between 2dcae2d and 0942132.

📒 Files selected for processing (6)

• README.md
• docs/llms-full.txt
• docs/open-core-boundary.md
• docs/railway-deploy.md
• docs/railway-template.md
• docs/vibe-deploy.md