Covered · enforcing
An installed adapter or wrapper pauses the exact supported action before the side effect and waits for ORBIT’s execution-safe result.
Orbit Authority · Guardian
Available now · coverage depends on the installed adapter
Govern the tool paths your agents actually route through ORBIT.
Guardian applies policy before a consequential action only where an installed path can enforce. Observe-only and unsupported paths stay visible as different facts.
Coverage truth
Enforcing, observed, and uncovered never collapse into one green badge.
Covered · observe-only
ORBIT records what the adapter reports, but does not claim it prevented or caused the downstream action.
Uncovered
No adapter signal means no governance claim. Empty activity is never translated into an all-clear.
Illustrative scenarios · not live telemetry
One decision shape across covered tools.
git push --force main
- Why
- A covered repository wrapper requires owner authority for history rewrites.
- Proof boundary
- Decision receipt pending; execution is still paused.
read protected secret path
- Why
- The installed enforcing path matches a protected-secret rule.
- Proof boundary
- The example denial records ORBIT’s decision, not activity on an uncovered path.
run repository-local tests
- Why
- The exact action is inside the active workspace rule and other gates pass.
- Proof boundary
- Authorization does not assert that the runtime later completed the command.
Coverage is declared per installed path
- OpenClaw / Hermes · Available with installed adapter · Coverage is declared per runtime path.
- Claude Code / Codex · Available with hook or wrapper · Only routed tool calls are covered.
- Deploy tools · Wrapper-dependent · Enforcing versus observe-only stays explicit.
- Stripe · Reviewed integration required · Not a packaged self-serve connector.
- Broker path · Integration pattern · The order path must route through the boundary.
- App mutations · Integration pattern · Application code owns the enforcement seam.