Analyze SATCOM Artifacts
Keep this workflow passive and offline. Never transmit RF, send a telecommand, contact a ground
station, or infer authorization from this card. Active work belongs only in an explicitly
authorized simulator with a separately enforced execution policy.
Workflow
- Identify the artifact type and record its digest before interpretation.
- Use
ravage satcom inspect for supported TLE or CCSDS Space Packet inputs.
- Preserve spacecraft catalog identities, APIDs, packet direction, sequence flags and counts,
declared lengths, offsets, digests, and evidence references in the SATCOM surface artifact.
- Correlate repeated identities and counters only after preserving per-record evidence refs.
- Retain the complete inventory and anomalies even when there is no flag or confirmed finding.
Evidence Gate
Malformed lengths, invalid TLE checksums, unsupported versions, and truncated records are strict
input errors, not partial findings. Treat repeated packets and sequence-counter reuse only as
observations or candidates. A packet header cannot prove missing authentication, replay acceptance,
command execution, or impact. Promote nothing without target-origin evidence from an authorized
simulator or another trusted validator.
Stop Conditions
Stop on oversized, truncated, ambiguous, special-device, or unsupported artifacts. Do not guess
payload semantics, fabricate ground stations or radio links, or include packet payload bytes in
the prompt-facing surface graph.
1---2name: analyze-satcom3description: Inspect authorized offline satellite and SATCOM artifacts without transmitting. Use for TLE sets, CCSDS Space Packet streams, telemetry or telecommand captures, sequence-counter anomalies, spacecraft identifiers, packet-length validation, or passive mission-data triage.4---56# Analyze SATCOM Artifacts78Keep this workflow passive and offline. Never transmit RF, send a telecommand, contact a ground9station, or infer authorization from this card. Active work belongs only in an explicitly10authorized simulator with a separately enforced execution policy.1112## Workflow13141. Identify the artifact type and record its digest before interpretation.152. Use `ravage satcom inspect` for supported TLE or CCSDS Space Packet inputs.163. Preserve spacecraft catalog identities, APIDs, packet direction, sequence flags and counts,17 declared lengths, offsets, digests, and evidence references in the SATCOM surface artifact.184. Correlate repeated identities and counters only after preserving per-record evidence refs.195. Retain the complete inventory and anomalies even when there is no flag or confirmed finding.2021## Evidence Gate2223Malformed lengths, invalid TLE checksums, unsupported versions, and truncated records are strict24input errors, not partial findings. Treat repeated packets and sequence-counter reuse only as25observations or candidates. A packet header cannot prove missing authentication, replay acceptance,26command execution, or impact. Promote nothing without target-origin evidence from an authorized27simulator or another trusted validator.2829## Stop Conditions3031Stop on oversized, truncated, ambiguous, special-device, or unsupported artifacts. Do not guess32payload semantics, fabricate ground stations or radio links, or include packet payload bytes in33the prompt-facing surface graph.
duriantaco