Architecture
Orbit is structured as an AI operating system with layered control, governed execution, orchestration, intelligence, and outward-facing presentation surfaces. This page combines a clear product-level architecture with the live generated graph from the scanner.
Navigate Orbit by operational layer
This scanner-backed view turns the architecture surface into a fast navigation map. Each layer shows its role in system flow, its immediate relationships, and the main places to inspect that part of Orbit in more detail.
Activity Memory
Persists operational history so Orbit can retain, summarize, and learn from prior work.
Execution
Transforms approved plans into real system changes, verification, and completion steps.
Governance
Validates and guards change before execution work is allowed to proceed.
Intelligence
Scans, diagnoses, and interprets the system so Orbit can understand and describe itself.
Interface
Exposes system activity outward through operator-facing surfaces and relay channels.
Proposal Planning
Creates governed change plans and buildsheet-driven execution pathways.
Queue
Sequences, dispatches, retries, and cancels work as it moves through runtime orchestration.
Scanner Publishing
Converts live system structure into the public system surface and reference views.
What the current scan exposes
Scanner-backed structure
This summary is derived directly from the current scanner outputs rather than a manual architecture description.
Agent topology
The current architecture includes a live agent layer surfaced from the registry-backed scanner output.
Why this structure matters
Built for controlled growth
Orbit is designed so the system can expand in capability without losing clarity. New modules slot into visible layers rather than becoming hidden one-off automations.
What the platform enables
This layered architecture gives Orbit room to become a broader AI control plane with richer dashboards, more agents, deeper operator interfaces, and stronger system memory over time.
Live operational layers
This is the primary scanner-backed architecture surface for Orbit. It presents the system as live operational layers rather than forcing the full topology graph to carry the entire explanation on its own.
Activity Memory
Operational memory capture, daily summaries, and activity-layer persistence.
Captures operational history so Orbit can report and reason over prior work.
Persists operational history so Orbit can retain, summarize, and learn from prior work.
Execution
Structured execution, project change, and verification.
Turns approved work into concrete system changes and verification steps.
Transforms approved plans into real system changes, verification, and completion steps.
Governance
Policy, validation, and guarded mutation control.
Controls how Orbit validates, routes, and guards change before execution happens.
Validates and guards change before execution work is allowed to proceed.
Intelligence
Scanner, diagnostics, drift detection, and self-modeling.
Provides scanning, diagnostics, drift detection, and self-modeling signals.
Scans, diagnoses, and interprets the system so Orbit can understand and describe itself.
Interface
Operator-facing surfaces and outward relays.
Connects Orbit to outward operator surfaces and relay channels.
Exposes system activity outward through operator-facing surfaces and relay channels.
Proposal Planning
Buildsheet generation, proposal ranking, handoff building, and change planning.
Builds proposals, ranked options, and governed execution plans.
Creates governed change plans and buildsheet-driven execution pathways.
Queue
Task intake, retries, cancellation, and orchestration.
Handles intake, retries, cancellation, and queued orchestration of work.
Sequences, dispatches, retries, and cancels work as it moves through runtime orchestration.
Scanner Publishing
Scanner-generated structural outputs that power the public system surface.
Generates the scanner-backed outputs used by the public Orbit website.
Converts live system structure into the public system surface and reference views.
Live structural highlights
These highlights are generated from the current scanner-backed architecture metadata and provide a compact operational readout of the public system surface.
8
Scanner-derived architecture groups currently exposed through the public system surface.
4
Enabled agents currently represented in the registry-backed architecture model.
24
Detected platform capabilities available across Orbit’s control plane.
6
Scanned services and timers visible to the public operational surface.
How Orbit moves work through the system
These flows are the readable operational model of Orbit. They explain the most important movement paths through the control plane without requiring the full topology reference.
Governance → Execution → Queue → Interface
Policy-aware control routes work into structured execution, queueing, and outward operator surfaces.
Agent Layer → Intelligence → Activity Memory
Agents inspect, reason, and persist operational history into Orbit’s memory surface.
Proposal Planning → Execution
Structured proposals and buildsheets are turned into governed execution work.
Scanner Publishing → Public Surface
Scanner outputs generate the public system interface, including architecture, system, timeline, and activity surfaces.
Scanner-complete graph
Full structural reference generated from SYSTEM_GRAPH.mmd for deep inspection.
Topology reference map
Use this view as a scanner-complete reference. The architecture console and critical flows above are the primary reading model for Orbit’s structure.
Follow the architecture into the rest of Orbit
The architecture map is the connective tissue of the site. Use it alongside the system, skills, agents, and status pages to move from structure to runtime behaviour.