docs: open-core boundary + multi-machine pattern

[frankxai]

Summary

• Document Agentic Ops open-core split: this hub = public system; private agentic-ops = live control plane.
• Add docs/OPEN_CORE_BOUNDARY.md and sanitized docs/MULTI_MACHINE_AGENTIC_OPS.md.
• README: open-core table + private ops layer in ecosystem map.

Rule

Share the system. Keep queues, tokens, and real envelopes private.

Test plan

• Docs-only; gitleaks clean
• Review for accidental private paths/tokens (none intended)
• Pair with private agentic-ops multi-machine PR

[coderabbitai]

Important

Review skipped

Draft detected.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: 6e974595-5f4d-47a4-99a4-532e676ba2c6

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• 🔍 Trigger review

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch agent/hermes/open-core-boundary

---

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

[gemini-code-assist]

Code Review

This pull request establishes the open-core boundary for Agentic Ops by updating the README and adding two new documentation files: docs/MULTI_MACHINE_AGENTIC_OPS.md and docs/OPEN_CORE_BOUNDARY.md. These files outline the sanitized multi-machine architecture patterns and define what information remains private versus what is shared publicly. The review feedback suggests a minor improvement in docs/OPEN_CORE_BOUNDARY.md to remove redundant docs/ prefixes from internal document links to ensure consistency and avoid confusion.

Important

The consumer version of Gemini Code Assist on GitHub is being sunset. Starting June 18, 2026, new organization installations will be blocked, and all code review activity will officially cease on July 17, 2026.
For more details on the timeline and next steps, please review the Help Documentation.

[gemini-code-assist]

Since this document is located inside the docs/ directory, the link text prefixing docs/ is redundant and potentially misleading (as it might imply a nested docs/docs/ path). Removing the docs/ prefix from the link text makes it consistent with the ECOSYSTEM.md link text on line 96.

Suggested change

	- [`docs/AGENT-OPERATING-SYSTEM-STACK.md`](AGENT-OPERATING-SYSTEM-STACK.md)
	- [`docs/PROTECTION-LAYERS.md`](PROTECTION-LAYERS.md)
	- [`docs/MULTI_MACHINE_AGENTIC_OPS.md`](MULTI_MACHINE_AGENTIC_OPS.md) — expanded multi-machine pattern
	- [`AGENT-OPERATING-SYSTEM-STACK.md`](AGENT-OPERATING-SYSTEM-STACK.md)
	- [`PROTECTION-LAYERS.md`](PROTECTION-LAYERS.md)
	- [`MULTI_MACHINE_AGENTIC_OPS.md`](MULTI_MACHINE_AGENTIC_OPS.md) — expanded multi-machine pattern

[frankxai]

PR hospital triage 2026-08-07 — PARK (draft)

Disposition: leave draft. Docs (open-core boundary) — low urgency; confirm still accurate vs main before promoting.

• Label suggestion: park · ship-candidate-docs