Packet Schema

Packet Philosophy

Packets provide a stable envelope for route, auth, and payload semantics so policy and service modules can interpret integration intent consistently.

JSON Schema

IntegrationPacket includes required fields version, packetId, packetType, createdAt, route, auth, and payload.

Route fields include scale/state/domain/facility/mission with typed route.orbit values (LEO/MEO/GEO).

Binary Schema

Framed transports use a minimal binary header contract: version, packetType, payloadLengthBytes, and flags.

Required Fields

• Route identity fields and packet metadata
• Credential token and scope list in auth
• Payload object matching packet type contract

Optional Fields

• auth.requiredOrbit for strict orbit requirements
• auth.compatibleOrbits for allowed orbit sets
• Packet-type-specific optional payload extensions

Versioning

Current packet version is 1.0. Additive changes are preferred; incompatible shape changes should increment packet and consumer contract versions together.

Orbit-Aware Timing Windows

Orbit-aware checks align packet authorization with requiredOrbit/compatibleOrbits hooks and expected latency/coordination windows across LEO, MEO, and GEO paths.

Guided Links

• Telemetry Layer
• Credential Token Format (Security page)