`orbitforge fleet show`

Synopsis


orbitforge fleet show --id <ID> [--store <PATH>]

Description

Prints a snapshot’s complete state document. Use it to inspect what a snapshot contains, to diff two snapshots, or to recover a superseded configuration.

Options

Parameter	Type	Unit	Default	Required	Description
`--id`	string	n/a	—	Yes	Snapshot identifier. A full identifier or any unambiguous prefix.
`--store`	path	n/a	`fleet-store`	No	Store directory.

Worked example

Using a four-character prefix rather than the full identifier:


orbitforge fleet show --id 8d06


Snapshot 8d063f302793 (2026-01-01T00:00:00Z, fleet `demo-fleet`):
{
  "name": "demo-fleet",
  "slots": [
    {
      "id": "demo-s0-p00-sat00",
      "elements": {
        "semi_major_axis_km": 6928.0,
        "eccentricity": 0.001,
        "inclination_deg": 53.0,
        "raan_deg": 0.0,
        "argument_of_perigee_deg": 0.0,

Output elided. The header line confirms which snapshot the prefix resolved to, followed by the full state document as JSON.

The header always prints the full identifier, even when you supplied a prefix. Check it. A prefix that matches a different snapshot than you intended will still print valid-looking output, and the header is the only place that discrepancy is visible.

Diffing two snapshots

Because the output is JSON, ordinary tools work:


orbitforge fleet show --id 8d06 > before.txt
orbitforge fleet show --id 564f > after.txt
diff before.txt after.txt

That is the practical way to answer what changed between two adopted configurations, which the note alone rarely captures in enough detail.

Recovering a superseded state

The store is append-only and content-addressed, so a superseded snapshot is never lost. To return to an earlier configuration, print it, save it to a file, and re-adopt it with a new snapshot naming the current one as parent:


orbitforge fleet show --id 8d06 > recovered.json
# Strip the header line, leaving only the JSON document.
orbitforge fleet save \
  --state recovered.json \
  --note "reverted to baseline; phasing correction caused a coverage gap" \
  --parent 564f2234b82b

Recording the revert as a new snapshot rather than deleting the intervening one keeps the history honest: it shows that a change was made, evaluated, and undone, which is more useful than a history where the mistake never appears.

The reverted snapshot will have the same identifier as the original baseline, because the content is identical. That is content addressing working correctly, and the --created, --note, and --parent values record that it was re-adopted.

orbitforge fleet show