Orbit System Specifications
System Specifications are Blackstar Systems' public behavior and boundary documents for Orbit. They explain what Orbit is allowed to do, what must be verified first, and what happens when a request cannot be completed safely. They are not internal architecture documentation.
For an integration-specific view, see Orbit for Open Dental. The broader integrations index shows current system coverage, and security documents platform-wide controls.
The controls behind every action.
Each specification describes a visible operating boundary: how a request is identified, what checks happen before action, which outcomes can be confirmed, and where Orbit stops instead of guessing.
Tool Gateway
How Orbit turns a caller request into a checked, client-scoped action before anything reaches a practice system.
Read Tool GatewayBounded Client Scope
How Orbit limits every workflow to the active practice's approved configuration and resources.
Read Bounded Client ScopeApproved Workflows
Why every action follows a defined, approved workflow, not an improvised path.
Read Approved WorkflowsIdentity, Availability, and Booking
How Orbit requires a resolved patient and system-returned availability before a scheduling workflow can continue.
Read Identity, Availability, and BookingConfirmation Boundary
Why a booking is only confirmed after the connected system verifies it.
Read Confirmation BoundaryFailure and Safe Recovery
How Orbit handles missing inputs, unresolved patient context, unavailable slots, and system failures without turning them into false success.
Read Failure and Safe RecoveryCall Routing and Transfers
How Orbit handles requests for a person or department during supported hours and after hours.
Read Call Routing and TransfersOffice Messages
How a request the practice needs to see reaches the right person, without exposing patient details in the process.
Read Office MessagesMultilingual Conversations
How Orbit supports conversations across configured languages while preserving the same approved workflows, client boundaries, and booking safeguards.
Read Multilingual ConversationsReview an integration-specific workflow.
See how these system specifications apply to the live Open Dental integration.