Orbit Control Surface
Skills: 37 Capabilities: 24 Last scan: 2026-04-11 03:39 UTC
Orbit status: Operational Last scan: 20260411T033930Z Agents: 4 active Activity: 24 recent
Orbit Autonomous AI OS
thompsons.dev · Orbit control plane

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.

Last scan 2026-04-11 03:39 UTC Latest generated architecture snapshot from the Orbit scanner.
Detected skills 37 Live modules currently indexed from the Orbit workspace.
Capabilities 24 Scanner-derived capability surface exposed across the platform.
Active agents 4 Live registered agents currently represented in the architecture surface.

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.

Layer 01

Activity Memory

4

Persists operational history so Orbit can retain, summarize, and learn from prior work.

Operational history and memory persistence
Upstream
Intelligence
Downstream
None
Layer 02

Execution

5

Transforms approved plans into real system changes, verification, and completion steps.

Structured execution and verification
Upstream
GovernanceProposal Planning
Downstream
Queue
Layer 03

Governance

4

Validates and guards change before execution work is allowed to proceed.

Policy and guarded control
Upstream
None
Downstream
Execution
Layer 04

Intelligence

8

Scans, diagnoses, and interprets the system so Orbit can understand and describe itself.

Diagnostics, scanning, and system reasoning
Upstream
Agents
Downstream
Activity MemoryScanner Publishing
Layer 05

Interface

2

Exposes system activity outward through operator-facing surfaces and relay channels.

Operator-facing relays and surfaces
Upstream
Queue
Downstream
Scanner Publishing
Layer 06

Proposal Planning

6

Creates governed change plans and buildsheet-driven execution pathways.

Governed change planning and buildsheet generation
Upstream
None
Downstream
Execution
Layer 07

Queue

7

Sequences, dispatches, retries, and cancels work as it moves through runtime orchestration.

Task routing and orchestration
Upstream
Execution
Downstream
Interface
Layer 08

Scanner Publishing

1

Converts live system structure into the public system surface and reference views.

Public system-surface publishing
Upstream
IntelligenceInterface
Downstream
None

What the current scan exposes

Scanner-backed structure

This summary is derived directly from the current scanner outputs rather than a manual architecture description.

Skills indexed 37 live skills currently mapped into the Orbit control plane.
Capabilities exposed 24 scanner-derived capabilities currently surfaced.
Tracked runtime units 6 systemd services and timers represented in the scan.
Supporting docs 7 tracked documentation references attached to the current map.

Agent topology

The current architecture includes a live agent layer surfaced from the registry-backed scanner output.

Orbit Sentinel lane: open · mode: both · execution capable
Orbit Navigator lane: open · mode: both · execution capable
Orbit Conductor lane: guarded · mode: automation · proposal only
Orbit Operator lane: open · mode: both · execution capable

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.

Governed by default Execution flows pass through policy-aware control instead of raw direct mutation.
Scanner-backed visibility The site can reflect real system structure because the platform generates its own map.
Release-based publishing The website is updated through deterministic build and release switching rather than live editing.

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.

Operational surfaces System, status, timeline, architecture, and changelog views all stem from the same source of truth.
Composable skills Skills remain visible and categorisable instead of disappearing into a monolithic black box.
Future-ready foundation The same structure can later support agent dashboards, richer metrics, and more advanced autonomous loops.

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.

Layer 01

Activity Memory

4

Operational memory capture, daily summaries, and activity-layer persistence.

Operational history and memory persistence
Upstream
Intelligence
Downstream
None

Captures operational history so Orbit can report and reason over prior work.

Flow focus

Persists operational history so Orbit can retain, summarize, and learn from prior work.

activity_dailyactivity_recorderactivity_socialmemory_ingest_activity
Layer 02

Execution

5

Structured execution, project change, and verification.

Structured execution and verification
Upstream
GovernanceProposal Planning
Downstream
Queue

Turns approved work into concrete system changes and verification steps.

Flow focus

Transforms approved plans into real system changes, verification, and completion steps.

buildsheet_runner_v1patch_and_verifypostchecksproject_executortask_planner_v1
Layer 03

Governance

4

Policy, validation, and guarded mutation control.

Policy and guarded control
Upstream
None
Downstream
Execution

Controls how Orbit validates, routes, and guards change before execution happens.

Flow focus

Validates and guards change before execution work is allowed to proceed.

governor_v1registry_toolsrouter_validatorskill_registry_list
Layer 04

Intelligence

8

Scanner, diagnostics, drift detection, and self-modeling.

Diagnostics, scanning, and system reasoning
Upstream
Agents
Downstream
Activity MemoryScanner Publishing

Provides scanning, diagnostics, drift detection, and self-modeling signals.

Flow focus

Scans, diagnoses, and interprets the system so Orbit can understand and describe itself.

agent_runnercoding-agentdrift_detectorhandover_generatoridea-vaultidea_autobuild_check
Layer 05

Interface

2

Operator-facing surfaces and outward relays.

Operator-facing relays and surfaces
Upstream
Queue
Downstream
Scanner Publishing

Connects Orbit to outward operator surfaces and relay channels.

Flow focus

Exposes system activity outward through operator-facing surfaces and relay channels.

discord-opsorbit-event-relay
Layer 06

Proposal Planning

6

Buildsheet generation, proposal ranking, handoff building, and change planning.

Governed change planning and buildsheet generation
Upstream
None
Downstream
Execution

Builds proposals, ranked options, and governed execution plans.

Flow focus

Creates governed change plans and buildsheet-driven execution pathways.

buildsheet_generatorbuildsheet_notifygoverned_handoff_builderproposal_maintenanceproposal_plannerproposal_ranker
Layer 07

Queue

7

Task intake, retries, cancellation, and orchestration.

Task routing and orchestration
Upstream
Execution
Downstream
Interface

Handles intake, retries, cancellation, and queued orchestration of work.

Flow focus

Sequences, dispatches, retries, and cancels work as it moves through runtime orchestration.

orbitloop_drainqueue_cancelqueue_enqueuequeue_enqueue_executorqueue_enqueue_shellqueue_list
Layer 08

Scanner Publishing

1

Scanner-generated structural outputs that power the public system surface.

Public system-surface publishing
Upstream
IntelligenceInterface
Downstream
None

Generates the scanner-backed outputs used by the public Orbit website.

Flow focus

Converts live system structure into the public system surface and reference views.

system_scanner

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.

Live layers

8

Scanner-derived architecture groups currently exposed through the public system surface.

Active agents

4

Enabled agents currently represented in the registry-backed architecture model.

Capabilities

24

Detected platform capabilities available across Orbit’s control plane.

Runtime units

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.

Governed execution path

Governance → Execution → Queue → Interface

Policy-aware control routes work into structured execution, queueing, and outward operator surfaces.

GovernanceExecutionQueueInterface
Agent intelligence loop

Agent Layer → Intelligence → Activity Memory

Agents inspect, reason, and persist operational history into Orbit’s memory surface.

AgentsIntelligenceActivity Memory
Proposal path

Proposal Planning → Execution

Structured proposals and buildsheets are turned into governed execution work.

Proposal PlanningExecution
Publishing path

Scanner Publishing → Public Surface

Scanner outputs generate the public system interface, including architecture, system, timeline, and activity surfaces.

Scanner PublishingWebsite Surface

Scanner-complete graph

Full structural reference generated from SYSTEM_GRAPH.mmd for deep inspection.

Topology reference map

Graph source: SYSTEM_GRAPH.mmd Last scan: 2026-04-11 03:39 UTC Skills: 37 Agents: 4

Use this view as a scanner-complete reference. The architecture console and critical flows above are the primary reading model for Orbit’s structure.

Orbit topology canvas
Scanner-complete Mermaid reference for the current Orbit architecture snapshot.
Zoom 100% Offset 24, 24 Reference map Deep-dive only
flowchart TB ORBIT["Orbit Control Plane"] GOV["Governance Layer"] EXEC["Execution Layer"] QUEUE["Runtime Queue"] IFACE["Interface Layer"] AGENTS["Agent Layer"] INTEL["Intelligence Layer"] ACT["Activity Layer"] PROP["Proposal Layer"] SURFACE["Public Surface"] ORBIT --> GOV ORBIT --> EXEC ORBIT --> QUEUE ORBIT --> IFACE ORBIT --> AGENTS ORBIT --> INTEL ORBIT --> ACT ORBIT --> PROP ORBIT --> SURFACE GOV --> EXEC EXEC --> QUEUE QUEUE --> IFACE IFACE --> SURFACE AGENTS --> INTEL INTEL --> ACT PROP --> EXEC ACT --> SURFACE INTEL --> SURFACE subgraph agent_registry["Registered Agents"] orbit_sentinel["orbit_sentinel"] orbit_navigator["orbit_navigator"] orbit_conductor["orbit_conductor"] orbit_update_system_config_specialist["orbit_update_system_config_specialist"] orbit_operator["orbit_operator"] end subgraph governance["Governance"] governor_v1["governor_v1"] registry_tools["registry_tools"] router_validator["router_validator"] skill_registry_list["skill_registry_list"] end subgraph execution["Execution"] buildsheet_runner_v1["buildsheet_runner_v1"] patch_and_verify["patch_and_verify"] postchecks["postchecks"] project_executor["project_executor"] task_planner_v1["task_planner_v1"] end subgraph queue_runtime["Queue Runtime"] orbitloop_drain["orbitloop_drain"] queue_cancel["queue_cancel"] queue_enqueue["queue_enqueue"] queue_enqueue_executor["queue_enqueue_executor"] queue_enqueue_shell["queue_enqueue_shell"] queue_list["queue_list"] queue_retry["queue_retry"] end subgraph interfaces["Interfaces"] discord_ops["discord-ops"] orbit_event_relay["orbit-event-relay"] end subgraph agents["Agents"] agent_runner["agent_runner"] end subgraph intelligence["Intelligence"] coding_agent["coding-agent"] drift_detector["drift_detector"] handover_generator["handover_generator"] idea_vault["idea-vault"] idea_autobuild_check["idea_autobuild_check"] pattern_detector["pattern_detector"] system_diagnostics["system_diagnostics"] end subgraph activity_memory["Activity Memory"] activity_daily["activity_daily"] activity_recorder["activity_recorder"] activity_social["activity_social"] memory_ingest_activity["memory_ingest_activity"] end subgraph proposal_planning["Proposal Planning"] buildsheet_generator["buildsheet_generator"] buildsheet_notify["buildsheet_notify"] governed_handoff_builder["governed_handoff_builder"] proposal_maintenance["proposal_maintenance"] proposal_planner["proposal_planner"] proposal_ranker["proposal_ranker"] end subgraph scanner_publishing["Scanner Publishing"] system_scanner["system_scanner"] end governor_v1 --> project_executor project_executor --> patch_and_verify task_planner_v1 --> project_executor queue_enqueue --> queue_list queue_list --> queue_retry queue_list --> queue_cancel queue_enqueue_executor --> orbitloop_drain orbitloop_drain --> orbit_event_relay discord_ops --> queue_enqueue system_scanner --> orbit_event_relay drift_detector --> handover_generator idea_vault --> idea_autobuild_check agent_runner --> system_diagnostics agent_runner --> project_executor agent_runner --> router_validator GOV --> governance EXEC --> execution QUEUE --> queue_runtime IFACE --> interfaces AGENTS --> agents AGENTS --> agent_registry agent_runner --> orbit_sentinel agent_runner --> orbit_navigator agent_runner --> orbit_conductor agent_runner --> orbit_update_system_config_specialist agent_runner --> orbit_operator INTEL --> intelligence ACT --> activity_memory PROP --> proposal_planning INTEL --> scanner_publishing SURFACE --> scanner_publishing class orbit_sentinel,orbit_navigator,orbit_conductor,orbit_update_system_config_specialist,orbit_operator regagent; class governor_v1,registry_tools,router_validator,skill_registry_list governance_node; class buildsheet_runner_v1,patch_and_verify,postchecks,project_executor,task_planner_v1 execution_node; class orbitloop_drain,queue_cancel,queue_enqueue,queue_enqueue_executor,queue_enqueue_shell,queue_list,queue_retry queue_node; class discord_ops,orbit_event_relay interface_node; class agent_runner agent_node; class coding_agent,drift_detector,handover_generator,idea_vault,idea_autobuild_check,pattern_detector,system_diagnostics intel_node; class activity_daily,activity_recorder,activity_social,memory_ingest_activity activity_node; class buildsheet_generator,buildsheet_notify,governed_handoff_builder,proposal_maintenance,proposal_planner,proposal_ranker proposal_node; class system_scanner surface_node; class ORBIT control_node; class GOV,EXEC,QUEUE,IFACE,AGENTS,INTEL,ACT,PROP,SURFACE layer_node; classDef control_node fill:#1a1426,stroke:#ffb86a,stroke-width:2px,color:#fff4de; classDef layer_node fill:#0f1724,stroke:#8dc7ff,stroke-width:1.5px,color:#eef6ff; classDef governance_node fill:#141826,stroke:#7dd3fc,stroke-width:1.2px,color:#eef6ff; classDef execution_node fill:#1b1a24,stroke:#ffc86a,stroke-width:1.2px,color:#fff8ea; classDef queue_node fill:#171827,stroke:#c084fc,stroke-width:1.2px,color:#f6ecff; classDef interface_node fill:#151d23,stroke:#5eead4,stroke-width:1.2px,color:#ecfffb; classDef agent_node fill:#201523,stroke:#f472b6,stroke-width:1.2px,color:#fff0f7; classDef regagent fill:#221726,stroke:#fb7185,stroke-width:1.2px,color:#fff1f2; classDef intel_node fill:#161d2b,stroke:#60a5fa,stroke-width:1.2px,color:#eef6ff; classDef activity_node fill:#15211e,stroke:#34d399,stroke-width:1.2px,color:#effff8; classDef proposal_node fill:#211a17,stroke:#f59e0b,stroke-width:1.2px,color:#fff7ed; classDef surface_node fill:#1b1623,stroke:#a78bfa,stroke-width:1.2px,color:#f5f3ff; classDef other_node fill:#1a1a1a,stroke:#94a3b8,stroke-width:1.1px,color:#f3f4f6;
This graph is preserved as a full structural reference. Use the architecture console and critical flow cards above for the primary reading experience.

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.

What this architecture communicates

Orbit is an operating layer It is not just a site or script collection. It is a structured system for governed AI workflows running on real infrastructure.
Orbit can represent itself The website reflects generated intelligence from the system, making the platform legible both operationally and externally.
Orbit is built to evolve The architecture is designed so new modules, automations, and agents can be added without collapsing the platform into chaos.