Understanding Plans
When you create a plan viaPOST /v1/plan, the response contains a complete execution plan computed from real orbital mechanics. This page walks through each section.
Response Structure
Satellite
Orbital parameters computed from real TLE data at plan creation time.Orbital Environment
The physical context the planner works within: eclipse fraction, satellite bus capabilities, orbital windows (sunlit/eclipse periods with resource envelopes), and predicted ground station passes.Placement Decisions
For each step, the planner decides whether it runs on-board or on the ground. Steps withlocation: "either" are automatically placed based on data reduction ratio and transfer cost.
Transfer Schedule
The planner auto-inserts transfer segments at space-ground boundaries. This section shows all data transfers with FEC overhead, encryption expansion, and ground station assignments.Error Budget
Quantifies data integrity: worst-case bit error rate, FEC overhead, retransmission reserves, and the resulting delivery confidence.delivery_confidence is the probability that all data is delivered correctly within the deadline, accounting for link errors and retransmissions.
Security Summary
Encryption overhead and key exchange details.Plan Segments
The scheduled execution timeline. Each segment is a step assigned to an orbital window with a start time.The plan may contain more segments than your original step count — the planner auto-inserts transfer segments at every space-ground boundary.
Event Stream
A simulated execution trace showing every significant moment. Retrieve via the plan response or separately viaGET /v1/plan/:id/events.

