Account boundaries
Authenticated tenant isolation and account-scoped governance data.
Orbit Authority · Enterprise
Directional · scoped engagements only
ORBIT has real account, rule, decision, and receipt primitives. Organization-wide delegation, connector coverage, deployment, and key custody must be scoped for the customer; they are not implied self-serve features.
Current foundation
Authenticated tenant isolation and account-scoped governance data.
Versioned policy, held actions, human decisions, and bounded standing authority.
Decision artifacts, readback, activity, export, and public internal-proof verification.
Requires explicit scope
Team, vendor, environment, and data-class delegation need an explicit contract.
Each runtime and external system needs a declared enforcing, observe-only, or uncovered path.
Customer-controlled deployment or signing-key models require a reviewed availability and trust design.
Multi-team administration, recovery, reporting, and support are not presented as a self-serve console today.