Reference
Who this section is for. Engineers who already know what they want to do and need to know exactly how the software behaves. It is information-oriented and deliberately dry. For task recipes, use the guides; for background, use Learn.
Every parameter states its unit. Every model states its assumptions, validity range, accuracy, and reference publication. If a page here omits either, that is a defect worth reporting.
Available now
Propagate a constellation and export the timeline. Representative CLI page.
POST /simulateThe HTTP equivalent, including the request contract and error shapes.
GlossaryDomain terminology, used consistently across the site.
Coverage status
The reference is authored in Phase 2. Completeness is tracked mechanically against a manifest generated from the source repository, so the gap is measured rather than estimated.
| Surface | Shipped | Documented |
|---|---|---|
| CLI commands | 25 | 1 |
| HTTP API endpoints | 46 | 1 |
| Workspace crates | 21 | 0 |
A page is not considered done until its command or endpoint has been executed and its output captured. No example output on this site is fabricated.
Conventions
| Convention | Rule |
|---|---|
| Units | Stated on every quantity. Angles state degrees or radians explicitly |
| Times | UTC unless stated otherwise. Epochs are RFC 3339 |
| Defaults | The value the software uses when the option is omitted, not a recommendation |
| Required | A missing required option is an error, never a silent default |
| Examples | Executed against the documented version; output is real, elided where long |
main (pre-release)