DAY 1 START

The people. Day one at Kestrel Orbital. You work with Theo Lindgren, senior controller in the Satellite Operations Center, who flies this platform every pass, and Dana Whitfield, systems engineer in Satellite Design & Engineering, who built it. Between them they know this platform better than anyone at Kestrel Orbital, and they have never written it down the same way.

The mandates. Executive Order 14144 sets the command-and-control protections civil space systems are held to: encrypt the commands, protect their integrity, authenticate the source, and reject unauthorized commands. The NIS2 Directive puts the ground-based infrastructure that carries it under mandatory cybersecurity risk-management and reporting duties. Kestrel Orbital’s own executive memorandum adds the third: machine-to-machine sharing with the Space ISAC.

The scope. Why the telecommand path first? Because the mandates land on it. The path that keeps the satellite under control is the path you must be able to show is protected, so that is where your decomposition starts.

Data Model

One standard data model for Kestrel Orbital's platform. Every part you enumerate resolves to a single element in one of four layers (PCE, SEG, SVC, AST), so the three departments describe the same platform the same way. You learn the model's two halves, the taxonomy and the ontology, then the two forms every element is written in: the published type name you read, and the enumerated name you apply to one real instance.

CONOPS

The Concept of Operations: the platform decomposed into its four layers, root first. You walk Environment, then Segment, Service, and Asset; at each layer you meet the enumerated elements the departments produced with the eight-step process, and a checkpoint closes the layer. By the last one the Day-1 CONOPS holds all 44 elements, every parent link populated below the root.

ENVIRONMENT LAYER

Where a space system operates: Terrestrial, Aquatic, Aerial, Orbital, and Deep Space. Naming the environment first is what an inventory that starts at the asset cannot give you: it records the where, never the things inside it, and every element below inherits that context, the zone, jurisdiction, and physics a finding lives in. On the telecommand path you enumerate four environments: two terrestrial sites and two orbital regimes.

SEGMENT LAYER

The enclaves that compose the platform. The published taxonomy defines ten segment types: Launch, Link, Ground, User, Aquatic, Low Altitude, High Altitude, Near Space, Space, and Deep Space. Naming the segment tells all three departments which enclave a finding lives in, and every segment links up to one or more environments. Kestrel’s telecommand scope enumerates four segments across three TAGs: Space, Link, and two Ground.

SERVICE LAYER

What runs on the platform: Control Plane, Data Plane, and Hybrid. A service is a functional responsibility, what the platform does, not the box it runs on, which is why the Security Operations Center writes detection rules here: a detection written against a service stays valid as the assets implementing it change, so it survives a hardware refresh. The telecommand scope enumerates fifteen services across the Space, Link, and Ground segments.

ASSET LAYER

The individual parts: Hardware, Firmware, Software, Data, Signal, and Hybrid. This is where the three departments converge and the work happens: patches land on assets, detections fire on assets, anomalies surface on assets, and each asset links up to every service it carries, so its full chain reads straight up and a shared box shows every service that falls with it. The telecommand scope enumerates twenty-one assets.

CONOPS Presentation

You present the validated telecommand decomposition to the three departments: every asset traces to a service, a segment, and an environment, with no orphans. An unbroken parent chain is what makes the decomposition usable as evidence, enrichment on any element carries its full structural context, and the elements the three mandates concern can be produced on demand.

THEORY TO TOOLING

What you built today does not stay in the classroom. The METEORSTORM data model is a published taxonomy and ontology, and the moment the shift ends your work ships as machine tags readable by any operator running the same published taxonomy.