1. Build a plan
Paste two-line element sets, for example from CelesTrak (the sample is the ISS on 1 January 2024; use fresh elements for real planning). Up to 50 satellites and 7 days.
Or start from a mission scenario in the open repository:
2. Sign the plan
Your operator key signs one record: a fingerprint of the plan, of each compiled file, the version and when it is in force. Your private key never leaves this device.
3. Check a signed plan
A customer, partner or auditor checks a plan against the operator's public key. Files are read on this device only.
Why sign a contact plan?
When a pass brings down nothing, the first question is whether that contact was scheduled at all. A signed plan answers it with the operator's own word, given when the plan was issued rather than after the dispute started. Pair it with custody receipts and gap records from the open reference implementation, and every missing bundle can be placed against a contact that was, or was not, in force.