Available with installed adapter
OpenClaw / Hermes
Coverage is declared per runtime path; only routed actions can be enforced or observed.
Orbit Authority · Integrations
Mixed capability · check each boundary
Put authority checks only where an installed path can enforce them.
ORBIT is not a generic plugin directory. Each runtime, tool, or external API path is labeled as available, integration-required, observe-only, or uncovered instead of inheriting a universal governance claim.
Capability register
Know what is current before you design the enforcement boundary.
Available with hook or wrapper
Claude Code / Codex
The hook or wrapper must submit the exact supported tool action before an enforcing decision is possible.
Reviewed integration required
Stripe
There is no packaged customer-action connector. The owning application must route the Stripe mutation through ORBIT.
Private pilot · provisioning required
GitHub Actions deploy gate
An internally proven reusable gate, not a packaged public integration. Each workflow needs reviewed identity and mutation-seam binding.
Integration patterns
Payments, trading, and app mutations
The authority contract is reusable, but each external API or mutation path needs its own enforcing seam.
Current · internal package proof
Public Verify
Verify checks the uploaded .orbitproof package within its stated boundary. It does not establish downstream execution.
Need another path?
Start with the exact action and where its side effect occurs.
A useful integration review identifies the actor, typed request, enforcement point, execution report, and proof boundary without assuming any of them.