SIDEREAL / Operations Wiki
Internal Reference — Confidential

Operations
Knowledge Base

The complete operational reference for Sidereal Logistics — covering launch infrastructure, regulatory compliance, physical handling, and client management. This document is the institutional memory of how we operate.

VERSION1.0
SECTIONS23
STATUSActive
LAST UPDATEDApril 2026
A
Orientation

This section is your starting point. Before you touch a playbook or a client file, you need to understand what Sidereal is, what we do, and — equally important — what we don't do. Read this first.

What Sidereal Is

Sidereal Logistics is a space logistics broker. We sit between clients who need to get a satellite to orbit and the complex ecosystem of launch providers, aggregators, regulators, insurers, and test facilities that make that happen.

We are not a launch provider. We do not own rockets. We are not a satellite manufacturer. We do not build hardware. We are not a mission operations company. We do not fly satellites. We are the orchestration layer — the expert guide who knows every part of the system, manages every timeline, and makes sure nothing falls through the cracks between organizations that don't talk to each other.

The One Sentence Version
Sidereal does for satellite launches what a customs broker does for international freight — except the regulatory complexity is higher, the cargo is more valuable, and the consequences of getting it wrong are catastrophic.
Our Position in the Transaction Stack
CLIENT (university lab, startup, small commercial operator) ↓ pays Sidereal a service fee SIDEREAL LOGISTICS ← we are here ↓ books capacity, manages compliance, coordinates partners RIDESHARE AGGREGATOR (Exolaunch, Spaceflight Inc.) ↓ LAUNCH PROVIDER (SpaceX, Rocket Lab) ↓ ORBIT

In addition to the aggregator relationship, Sidereal coordinates in parallel with: regulatory agencies (FAA, FCC, NOAA, DDTC), insurance brokers, legal counsel, environmental test facilities, and freight carriers. The client has one point of contact — us. We manage the rest.

Who We Serve
  • University CubeSat programs — primary early target. Grant-funded, technically capable, logistically inexperienced. High value for discovery conversations and LOIs.
  • Commercial small satellite startups — more budget, higher urgency, value speed and certainty over cost minimization.
  • Established small operators with repeat missions — know the process, want aggregator leverage and reliable execution.
  • Government-adjacent / SBIR-funded programs — structured procurement, longer sales cycle, larger and more predictable contracts.
What We Don't Do — The Service Boundary
Hold This Line — Always
Sidereal facilitates, coordinates, and advises. We do not operate satellites, diagnose spacecraft anomalies, advise on export classification, act as insurance brokers, or provide legal counsel. When clients ask us to cross these lines — and they will — the answer is a referral to the right specialist, not an attempt to do it ourselves.
The OS — Tools You'll Use Daily
ToolPurposeWhen to Use
This WikiOperational knowledge base — the "what" and "why"Reference before any client conversation or regulatory action
Playbook HubSix execution playbooks — the "how"Open during active work. Intake, regulatory, timeline, payload, partners, post-launch.
Mission TrackerAll active missions — status, dates, risk, open itemsCheck at start of every workday. Update after every client interaction.
A2
Roles & Scope

Not every role at Sidereal touches every part of this wiki equally. This section maps the four core roles to their primary scope — what they own, what they need to know cold, and what is useful background versus daily reference. Read this before diving into the operational sections so you know which parts of the OS belong to you.

Early Stage Note
At this stage, roles are not rigid. One person will wear multiple hats. This mapping is not about limiting scope — it is about clarifying primary ownership so nothing falls through the gap between two people's job descriptions.
Mission Coordinator

Primary owner of: client engagement from intake through post-launch, regulatory orchestration, timeline management, playbook execution, partner coordination on active missions.

Wiki AreaDepth Required
Orientation, Operating Standards, Pricing ArchitectureKnow cold
Launch Providers & PUGs, Rideshare Aggregators, Mission TimelineKnow cold
FAA, FCC, NOAA, ITAR/EAR, Debris MitigationKnow cold
Insurance, Ground Transport, Post-Launch OpsKnow cold
Client Intake, AcronymsKnow cold
Knowledge Base — all sectionsActive user — add entries

The Playbook Hub is your primary daily tool. The wiki is your reference layer behind it. Every gate, every escalation trigger, every client communication standard applies to this role in full.

Business Development

Primary owner of: outreach pipeline, discovery calls, LOI process, partner relationship building, conference presence, client qualification before formal intake.

Wiki AreaDepth Required
Orientation, Operating Standards, Pricing ArchitectureKnow cold
Rideshare Aggregators, Mission Timeline overviewConversational fluency
FAA, FCC, NOAA, ITAR/EAR — overview levelConversational fluency
Client Intake — fullKnow cold
AcronymsKnow cold
Launch Providers & PUGs, Insurance, Ground Transport, Post-LaunchBackground awareness
Knowledge Base — Client Patterns, Partner DirectoryActive user

You don't need to know how to file an FCC Part 25 application. You do need to know what it is, why it matters, and why a client who hasn't started it with 10 months to launch is in trouble. Conversational fluency means you can speak to it credibly, ask the right questions, and know when to escalate to a Mission Coordinator.

Operations Generalist

Primary owner of: internal systems hygiene, tracker maintenance, documentation standards execution, partner coordination on non-mission-specific tasks, process improvement, KB maintenance.

Wiki AreaDepth Required
Orientation, Operating StandardsKnow cold
Pricing Architecture — structural onlyAwareness
Mission Timeline — phases and gate structureConversational fluency
Client Intake — process flowConversational fluency
Regulatory stack — overview levelBackground awareness
AcronymsKnow cold
Knowledge Base — all sectionsPrimary steward — maintain and review

Your job is to make sure the OS works. The tracker reflects reality. The KB gets updated when something is learned. Documentation standards are actually followed. You are the connective tissue of the operation — which means you need to understand every process well enough to know when it's breaking down, even if you're not the one executing it.

Founder / Principal

Primary owner of: all four quality gates, all pricing decisions, strategic direction, legal and compliance oversight, final escalation authority, partner agreements.

Wiki AreaDepth Required
EverythingBuilt it — owns it

The founder is the last line of review on every gate. No engagement advances past a gate without founder sign-off. No pricing is communicated to a client without founder approval. No legal or compliance action is taken without founder visibility. This is not a bottleneck — it is the quality control mechanism that protects the company and the client until the team has sufficient depth to operate independently.

Depth Levels Defined
LevelWhat It Means in Practice
Know coldCan explain it without looking it up, answer a client question about it in real time, and identify when something in this area is wrong or at risk.
Conversational fluencyUnderstands what it is, why it matters, and can ask intelligent questions about it. Knows when to escalate to someone who knows it cold.
Background awarenessHas read the section and understands the concept. Can't execute independently but won't be blindsided by a reference to it.
B
Operating Standards

These are the non-negotiable standards that define how Sidereal operates. They apply to everyone on the team on every engagement. They are not guidelines — they are the baseline below which we do not go.

Communication Standards
  • 4-hour response window — all client communications acknowledged within 4 hours during business hours. Acknowledgment is not a full answer — it is confirmation that you received the message and when you'll respond fully.
  • 48-hour follow-up — every intake meeting, client call, or significant interaction gets a written follow-up within 48 hours. Summary of what was discussed, action items, next steps. No exceptions.
  • Proactive updates — clients should never have to ask for a status update. If something changes — timeline, aggregator communication, regulatory development — the client hears it from us before they ask.
  • No verbal-only decisions — anything decided in a call or meeting is confirmed in writing within 24 hours. "As we discussed" is not documentation.
Documentation Standards
  • Every call gets a summary — written and sent to the client within 24 hours. Who attended, what was discussed, what was decided, what each party owns next.
  • Every handoff gets a transfer receipt — physical custody of hardware is never transferred without a signed, timestamped transfer receipt. No exceptions. See Playbook 04.
  • Every decision gets a written record — if a client makes a decision that affects the mission (orbit change, vehicle change, timeline adjustment), it is documented in writing and acknowledged by the client in writing.
  • Tracker updated same day — the mission tracker reflects current reality. If something changes, the tracker is updated before the end of that business day.
Quality Gates — Founder Sign-Off Required

Four moments in every engagement require explicit founder review before work advances. These are not suggestions. Skipping a gate is not a time-saving measure — it is a liability.

GATE 1 — Post-Intake Before engagement is formally accepted. Founder reviews intake document and risk classification. Conditional or declined engagements communicated within 48 hours. GATE 2 — Before Any Regulatory Filing or Legal Engagement Before Sidereal initiates any filing or legal partner referral on client's behalf. Founder confirms scope and appropriate partner. Prevents mismatched counsel or premature filings. GATE 3 — Before Manifest Confirmation Full documentation package reviewed before anything goes to aggregator. All regulatory authorizations confirmed in hand. Nothing goes to the aggregator without founder sign-off. GATE 4 — Pre-Launch Readiness Final check before launch week. All authorizations confirmed. Insurance in place. Ground station tested. Chain of custody complete. Founder signs off before launch campaign begins.
Escalation Standards
Rule
There is no penalty for over-escalating. There is serious consequence for under-escalating. When in doubt, escalate. A problem raised early is manageable. The same problem raised late is a crisis.
ESCALATE IMMEDIATELY — STOP WORK: Client discloses foreign nationals with controlled tech + no TCP Foreign launch vehicle + no TAA in place Any propulsion system with no ITAR classification Client has signed agreements Sidereal hasn't reviewed Any regulatory deadline within 30 days with no filing started Hardware exceedance on transit data logger No satellite signal 48 hours post-separation ESCALATE BEFORE PROCEEDING: Client asking Sidereal to advise outside our defined scope Partner pushing back unexpectedly on timeline or requirements Client hardware readiness doesn't match what was stated at intake Any situation where you're unsure whether to proceed
First 30 Days — New Team Member Path
WeekFocusMilestone
Week 1Read the full wiki. All sections. Take notes on questions.Pass a verbal knowledge check with the founder on regulatory stack and timeline mechanics.
Week 2Work through all six playbooks in the hub. Run a mock intake using the intake playbook with a hypothetical client scenario.Complete mock intake with correct risk classification and action items.
Week 3Shadow founder on a live client interaction or discovery call. Review all active missions in the tracker and understand current state of each.Can describe every active mission's phase, next critical date, and open items without looking.
Week 4Run a solo intake with founder review. Manage one client communication independently with post-send review.Intake document and output approved by founder. Communication sent without revisions.
C
Pricing Architecture
Confidential — Internal Reference Only
Specific pricing is never quoted by team members without founder approval. This section provides structural context only. All client proposals are issued by the founder.
How Sidereal Makes Money

Three revenue mechanisms operate simultaneously:

  • Service fees — direct billing for defined scopes of work, milestone-based
  • Pass-through margin — markup on third-party costs booked on client's behalf (aggregator, transport, insurance placement)
  • Retainer / ongoing support — monthly fee for post-launch support, regulatory monitoring, mission operations liaison
Service Tiers — Structural Overview
TierWhat It CoversBilling StructureWhen to Recommend
Mission Readiness AssessmentPaid intake deliverable. Written report covering all five assessment areas with action items and risk flags.Flat fee at engagementClient not yet ready for full engagement, unfunded budget, or significant unresolved flags from intake
Mission Planning & Provider SelectionOrbit definition, vehicle matching, preliminary regulatory roadmap, insurance introductionFlat fee, two milestonesClient has confirmed budget and hardware direction but hasn't booked a launch yet
Full Mission ManagementEnd-to-end from contract execution through launch and early orbit. ICD coordination, regulatory management, manifest close, payload delivery, launch support.Milestone billing — 4 gatesStandard full-service engagement for a prepared client
Post-Launch Support RetainerOngoing monthly support — conjunction monitoring, regulatory reporting, ground station liaison, end-of-life planningMonthly, minimum termClient in orbit needing continued compliance and operational support
Milestone Billing — Full Mission Management

Full Mission Management fees are split across four milestones aligned to mission gates. This structure aligns payment to value delivered and keeps the client accountable to the timeline.

25% — At contract execution 25% — At ICD sign-off 25% — At manifest confirmation 25% — At launch / separation confirmation
Pass-Through Margin

On costs Sidereal books and manages on behalf of clients, a margin is applied. This is standard in logistics brokerage. Specific margin rates are set by the founder per engagement and are not disclosed to clients in itemized form unless the client specifically requires cost-plus pricing (government/grant-funded clients may require this for compliance).

Pricing Principles — What Team Members Need to Know
  • Never quote a specific number without founder approval — pricing is engagement-specific and strategically set
  • Never discount to win a client — sets a damaging reference price and attracts the wrong clients
  • Hourly billing is not used — milestone and deliverable pricing only
  • The MRA is the right entry point for uncertain clients — it filters serious from non-serious at low cost to both parties
  • Scope and price for actual effort — a first-time operator with a small team requires more engagement than an experienced one. Price reflects the real cost to deliver.
D
Technology Roadmap

Sidereal is building the operational software layer space logistics has never had. The roadmap is three stages, each building on the last — and each stage is funded by the revenue of the previous one. No stage requires external capital to initiate.

Why This Matters to the Team
The tools you use daily — wiki, tracker, playbooks — are not just internal infrastructure. They are Stage 1 of the platform. Every mission you run stress-tests and refines the system. The institutional knowledge you add to the KB is the data layer the Stage 2 and 3 products are built on. The work you do today is the product.
The Gap We Are Closing

Space logistics currently runs on email, PDFs, and phone calls. Incumbents operate on tribal knowledge and manual processes — no client visibility, no standardized data layer, no structured compliance workflow. Every mission starts from scratch. Documentation is rebuilt on every engagement. Status updates go out by email. Nobody has built the infrastructure layer.

Current state — industry standard: Client → email chain → broker → phone calls → aggregator Compliance docs rebuilt per mission from scratch Status updates: email, whenever someone remembers Regulatory deadlines: tracked in personal spreadsheets No audit trail. No structured data. No institutional memory. Sidereal target state: Structured intake → mission record → phase-gated workflow Compliance checklist auto-populated from mission profile Client portal with real-time phase and regulatory status Every action documented. Every decision logged. Data accumulates across missions — system gets smarter.
Stage 1 — Internal Operations System
Status — Operational
Stage 1 is built and running. The tools you are using right now are Stage 1.

The foundational layer — the internal OS that manages every mission from intake through post-launch. Built before the first client. Stress-tested through early engagements. Refined continuously.

ToolFunctionStatus
Operations WikiFull institutional knowledge base — regulatory stack, partner intel, playbooks, decision log, KB sectionsLive
Mission TrackerPhase-gated mission management — intake through post-launch, risk classification, open items, regulatory status per agencyLive
Playbook HubSix operational playbooks — intake, regulatory, timeline, payload, partners, post-launch — with live mission contextLive
Founder Command CenterCross-workstream task management — urgency-sequenced, workstream-tagged, dependency-awareLive

Stage 1 generates the data, tests the workflows, and validates the service model. Every mission run through Stage 1 produces structured data that feeds Stage 2. The system is not a prototype — it is operational and used on every engagement.

Client Portal — Demonstrable Now

A full client portal experience has been designed and built as a proof of concept.

Demonstrates the complete client-facing mission visibility layer — phase and milestone tracking, regulatory status by agency, document management, billing history, team communication. Used in client and investor conversations to show exactly what the Sidereal experience looks like before a single mission has been run. Full deployment with live data integration on first funded engagement.

Current State
POC complete — demonstrable
Full Deployment
First funded engagement
Use In
PI meetings · investor conversations
Sales Approach

Open with the portal before discussing anything else. Show a mock mission that mirrors the prospect's profile. Let them see their satellite tracked through 10 phases with regulatory status per agency and a manifest countdown. Then ask what they currently use to track that. The answer is always email and spreadsheets. The conversation writes itself.

Stage 2 — Client Portal
Horizon — Year 1–2, Post Initial Funding
Initiated when mission volume justifies the development investment. Funded from Stage 1 revenue or initial raise.

Stage 2 is the live deployment of the client portal — connecting the demonstrable POC to real mission data and a production backend. The interface and experience are already built. Stage 2 is the engineering work that makes it live, persistent, and connected to the mission tracker in real time.

FeatureDescription
Phase & Milestone TrackingClient sees exactly where their mission is in the 10-phase lifecycle, with next critical dates and open items requiring their action
Regulatory Status DashboardStatus per agency — FAA, FCC, NOAA, DDTC — green/amber/red with filing dates and action items
Document ManagementAll mission documents in one place — PUG, ICD, insurance certificates, regulatory filings — versioned and accessible
Billing & Milestone InvoicingInvoice history, upcoming milestone payments, pass-through cost visibility
Team CommunicationStructured communication thread tied to mission record — no more email chains

The Stage 2 portal is what converts Sidereal from a managed service into a platform relationship. Clients who can see their mission in real time are more engaged, more prepared, and more likely to return for subsequent missions.

Stage 3 — SaaS Platform
Horizon — Year 2+
Initiated when transaction volume and platform maturity justify unbundling the software from the service.

The platform becomes a standalone subscription product — available to operators who want the tooling without the full-service wrapper, and to other logistics coordinators who want to use Sidereal's compliance infrastructure. The service business becomes the distribution channel for the software business.

Revenue StreamDescription
Operator SubscriptionPayload operators access the compliance workflow, regulatory filing tools, and mission tracking independently — self-serve tier
Managed Service PremiumFull-service wrapper on top of the platform — Sidereal handles everything, client gets platform visibility
API / Data LayerOther logistics companies and government contractors access Sidereal compliance data and workflow infrastructure via API
Supporting Technologies

Two technologies are on the roadmap as supporting infrastructure — both in early stage, both relevant to scalability. Neither is present-tense operational capability. Both are directional.

TechnologyRoleStageHonest Status
Launch Matching Engine Rule-based matching of payload specs, orbital requirements, timeline, and budget against available rideshare windows. Surfaces ranked options. Reduces manual provider research from hours to minutes. Stage 2 Rule-based MVP scoped
Compliance Automation Structured document generation and regulatory checklist automation from mission profile data. Reduces documentation rebuild time per mission. Evolves toward predictive filing timeline recommendations as mission data accumulates. Stage 2 Workflow mapped, not built
Blockchain Audit Trail Immutable record of custody, compliance actions, and milestone confirmations. Relevant for government and grant-funded clients with documentation integrity requirements. Not a payment mechanism — a record layer. Stage 3 Directional — not scoped
Honesty Standard
Do not describe these as current capabilities to clients or investors. The honest framing is: the workflows are mapped, Stage 1 is generating the data layer they will be built on, and they are a defined part of the Stage 2 build. That is a credible, defensible claim. Present-tense claims that do not reflect reality undermine everything else.
Long-Term Technology Vision

The three-stage platform roadmap is the near-term execution path. The longer arc — discussed and decided in the founding vision — points toward Sidereal as infrastructure rather than service. The end state is not a company that helps people get to orbit. It is the operating layer that the space logistics industry runs on.

Phase 1 (now → 3-5 yrs) Service business. Managed missions. Regulatory expertise. Relationships with aggregators, counsel, brokers. Data accumulation. System refinement. Phase 2 (3-7 yrs) Software business emerges from service operations. Compliance workflows become licensable products. Platform serves operators who outgrow full-service. Transition from service to product requires deliberate decision. Phase 3 (7+ yrs) Platform infrastructure. Other logistics operators and government contractors use Sidereal compliance data layer. Standards influence. Deep regulatory relationships. Possible hardware adjacent plays — orbital transfer, depot infrastructure — require corporate restructuring and are not near-term. Flag only, not a plan.

The key risk in this arc is the Phase 1 → Phase 2 transition. Service revenue becomes comfortable and software feels like a distraction. That transition requires a deliberate decision, not drift. The decision log should have an entry when that moment arrives.

00
The Full Operational Stack

Sidereal operates as the orchestration layer between clients and the full complexity of space logistics. The complete service stack spans three domains — regulatory, risk, and physical — all running in parallel across the mission lifecycle.

REGULATORY LAYER FAA — Launch licensing, payload documentation FCC — Spectrum licensing, Part 25 or Experimental NOAA — Remote sensing (Earth observation only) ITAR — Export control, criminal exposure territory EAR — Commerce Dept, most commercial satellites Debris — FCC 5-year rule, passivation, conjunction RISK LAYER Insurance — Pre-launch, launch, in-orbit, TPL (mandatory) Liability — Cross-waivers, chain of custody Export — TAA for foreign vehicles, TCP for foreign teams PHYSICAL LAYER Ground transport — Dedicated carrier, air-ride, climate Handling — Cleanroom, chain of custody, data loggers Integration — Aggregator facility, ICD verification Post-launch — Ground stations, TLE, anomaly support
Sidereal's Core Value
No single agency or process is impossibly complex. Managing all of them simultaneously, on timeline, for a client who is also building a satellite — that is where the value is.
01
Launch Providers & PUGs

Every major launch provider publishes a Payload User's Guide (PUG) — the definitive technical reference governing payload acceptance, interface requirements, and documentation obligations. Treat PUGs as routing guides. Sidereal must know each provider's PUG cold before a client asks.

Version Control Required
PUGs are updated as vehicles and processes evolve. Always verify you have the current version. An outdated PUG is worse than no PUG — it creates false confidence.
PUG Reference Matrix
Provider Vehicle Orbit Form Factors Notes
SpaceX Falcon 9 Transporter SSO ~525km CubeSat, ESPA, custom Via aggregator (Exolaunch, Spaceflight). Frequent cadence.
Rocket Lab Electron LEO, SSO Up to ~300kg Dedicated small sat. CDS standard. Direct customer relationship possible.
ISRO PSLV SSO, LEO CubeSat, microsats Foreign vehicle — TAA required before any technical exchange.
Arianespace Vega-C SSO, LEO Small to medium Foreign vehicle — TAA required. ESA coordination.
RocketLab Neutron (upcoming) LEO Medium class In development. Monitor PUG when published.
What Every PUG Contains
  • Payload envelope — Maximum mass, dimensions, center of gravity limits
  • Interface definition — Mechanical mounting, deployment switch specs
  • RF requirements — Emissions restrictions during ascent, frequency coordination
  • Electrical interface — Kill switches, power inhibits
  • Materials restrictions — Forbidden adhesives, coatings, battery types
  • Environmental test requirements — What tests, to what levels, with what documentation
  • Documentation checklist — Everything required at payload review
  • Integration timeline — Lead times, manifest close dates, delivery windows
02
Rideshare Aggregators

Aggregators sit between launch providers and end customers. They consolidate multiple small payloads, own the aggregator-to-launcher relationship, and handle integration at their facilities. Sidereal's commercial leverage increases as we bring volume to aggregators.

TRANSACTION STACK Client (payload owner) ↓ Sidereal (logistics broker) ← our position ↓ Rideshare Aggregator (Exolaunch / Spaceflight / D-Orbit) ↓ Launch Provider (SpaceX / Rocket Lab) ↓ Orbit
Major Aggregators
Company HQ Primary Vehicle Dispenser Differentiator
Exolaunch Berlin, DE SpaceX Transporter CarboNIX, eXopod Dominant on Transporter missions. Very process-driven. Strong track record.
Spaceflight Inc. Seattle, US Multi-vehicle Sherpa tug Vehicle agnostic. US customer base. Own dispenser manufacturing.
D-Orbit Como, IT SpaceX, others ION carrier In-orbit transport to precise orbit post-launch. Different value prop.
NanoAvionics Vilnius, LT Multi-vehicle Various Also builds satellites. Blurred aggregator/manufacturer line.
Critical Aggregator Dynamics
Manifest Close Is Absolute
Once an aggregator closes the manifest, there are no exceptions and no extensions. Missing manifest close — for any reason — means the client is off the mission, deposit forfeited. Sidereal sets internal gates 2–3 weeks ahead of every aggregator deadline.
  • Client contracts with aggregator, not launch provider — SpaceX schedule changes flow through the aggregator. Maintain direct mission manager relationships to get real-time information.
  • Dispensers add requirements — Client must comply with both vehicle PUG AND aggregator dispenser spec. Interface mismatch discovered late means redesign and potential mission delay.
  • Pricing is negotiable — Aggregators don't publish fixed rates. Volume = leverage. Multiple clients on a single aggregator relationship changes the commercial dynamic significantly.
  • Payload maturity matters — Aggregators prefer payloads with demonstrated design maturity. Presenting an immature payload damages Sidereal's relationship with the aggregator — our long-term asset.
03
Mission Timeline — Contract to Orbit

Most first-time clients wildly underestimate how long this takes. The realistic window for a prepared client is 12–18 months from serious engagement to launch. An unprepared client can miss their window entirely and slip a year.

Prepared Client
12–18 mo
Contract to orbit
First-Time Operator
18–24 mo
Typical realistic window
FCC Lead Time
6–12 mo
Part 25 standard
Launch Deposit
25–30%
Non-refundable at booking
Month 1–3
Phase 1 — Mission Definition & Provider Selection
Establish orbit, mass/volume, timeline driver, budget ceiling. Match to vehicle and aggregator. Sidereal earns early fees here. Getting this wrong cascades into every subsequent phase.
Month 2–4
Phase 2 — Booking & Contract Execution
Engage aggregator, negotiate terms, execute Launch Services Agreement. Deposit paid (25–30%, non-refundable). ICD initiated. FCC filing must start here — do not wait.
Month 4–8
Phase 3 — Design Conformance & ICD Finalization
Client engineering team demonstrates compliance with dispenser interface. Mechanical, electrical, mass properties, materials review. ICD signed. Hard gate — nothing advances without it.
Month 6–10
Phase 4 — Environmental Testing
Vibration, thermal vacuum, EMI/EMC, fit check. Must be at a qualified test facility. Test facility scheduling is a hidden bottleneck — book early. Sidereal's knowledge of facility availability is genuine value.
Month 9–11
Phase 5 — Documentation Package & Manifest Close
Final mass properties, completed ICD, test reports, payload safety approval, all regulatory licenses, export control docs. Manifest close is absolute. Miss it and you're off the mission.
Month 10–12
Phase 6 — Payload Delivery & Integration
Ship satellite to integration facility. Final inspection, integration into dispenser, electrical checks. Chain of custody transfers here. Liability questions become real. Insurance must be in place before this moment.
Month 12+
Phase 7 — Launch Campaign
Vehicle to pad. Final checkouts. Launch window opens. Scrubs and holds are normal — manage client expectations proactively.
T+0 to T+72hr
Phase 8 — Early Orbit Operations
Separation confirmation, first AOS attempt, TLE identification, initial health checks. Highest-risk period of the mission. Sidereal present throughout.
Ongoing
Phase 9–10 — Mission Support & End of Life
Conjunction monitoring, regulatory reporting, end-of-life deorbit planning, license closeout with FCC and NOAA.
Sidereal's Core Timeline Value
We know where the schedule gets eaten. We set internal gates 2–3 weeks ahead of every hard deadline. We're on the phone with the aggregator mission manager monthly. We flag risks before they become problems. That is the difference between making orbit and not.
04
FAA — Office of Commercial Space Transportation

The FAA's Office of Commercial Space Transportation (AST) is the primary US federal authority licensing commercial launch and reentry operations. No commercial launch from US soil — or by a US company from anywhere — happens without them.

What FAA Regulates
  • Launch vehicles (rockets)
  • Launch and reentry sites (spaceports)
  • The payload indirectly — the launch operator holds the license, which covers the mission including client payloads
Sidereal's Role in FAA Process

Sidereal is not the launch operator. SpaceX, Rocket Lab, etc. hold the launch license. Our client-facing obligations:

  • Ensure client payload information feeds correctly into the launch operator's FAA filings
  • If payload has any propulsion, flag immediately — complexity increases significantly
  • Manage the Payload Review process — launch operator confirms payload doesn't endanger vehicle or mission
  • Know the payload review checklist cold: mass, CoG, material safety data, RF emissions during ascent
Primary Document: Payload User's Guide
Every launch provider publishes a PUG. It dictates exactly what must be submitted and in what format. Sidereal knows every active PUG. See Section 01.
05
FCC — Spectrum & Satellite Licensing

Any US person or company operating a satellite with radio frequency emissions needs FCC authorization. Almost every satellite has some RF emission — even a simple beacon. FCC licensing must start at Phase 1, not Phase 4.

The Two License Types
LicenseWhat It CoversKey Requirement
Space Station License The satellite's transmission from orbit — frequencies, orbital params, power levels, operational lifetime Part 25 filing, International Bureau
Earth Station License The ground station communicating with the satellite Sometimes combined with space station application
License Paths & Timeline
PathTimelineUse CaseRestriction
Part 25 — Full 6–12+ months Commercial operations None on commercial use
Experimental License 3–6 months R&D, university CubeSats No commercial data services. 2-year limit.
Amateur (Part 97) Varies via IARU Non-commercial only Strict non-commercial. Any data monetization = violation.
Amateur Frequency Warning
University clients frequently consider amateur frequencies for speed. If their business model involves selling or commercializing data, amateur is not an option. Have this conversation at intake, not six months in. The FCC enforces this.
Frequency Bands — Client Reference
BandFrequencyTypical UseLicensing Complexity
UHF 300 MHz – 3 GHz CubeSat TT&C, amateur sats Low
S-band 2–4 GHz Telemetry, command Low–Medium
X-band 8–12 GHz EO data downlink Medium
Ka-band 26–40 GHz High throughput, constellations High
ITU Coordination

Every satellite in orbit operates internationally. ITU coordination runs in parallel with the FCC process — filed through the FCC on behalf of US operators. Key points:

  • Formal ITU coordination can take years for complex cases
  • CubeSats may qualify for simplified process under Resolution 32
  • Some frequency bands carry heavy coordination burden — know these before recommending bands to clients
  • Most small operators don't know ITU coordination exists. Telling them early is immediate value.
Sidereal Owns
  • Early identification — Part 25 vs. Experimental vs. Amateur determination at intake
  • Application preparation — Template and format knowledge for FCC filings
  • Timeline management — FCC authorization on the critical path from day one
06
NOAA — Remote Sensing Licensing

NOAA's Commercial Remote Sensing Regulatory Affairs (CRSRA) office licenses US operators collecting Earth observation data from space. The rationale is national security — Earth observation satellites can image sensitive locations. Applies to optical, SAR, hyperspectral, and multispectral Earth observation.

Intake Trigger Question
"Does your satellite collect any imagery or data about Earth's surface?" If yes, NOAA is in the picture. Start in parallel with FCC.
License Tiers (Post-2020 Framework)
TierCapabilityTimelineReview
Tier 1 — Standard Lower resolution, standard capabilities 60–120 days Streamlined. Most small operators.
Tier 2 — Enhanced Higher resolution or sensitive capabilities 120+ days Detailed review. More conditions.
Tier 3 — Novel New sensor types, unusual methods Unpredictable Case-by-case. Most uncertainty.
Key Operational Conditions
  • Shutter control — NOAA can order you not to image specific areas during specific periods. This is a real constraint on business models promising continuous coverage of specific regions.
  • Data distribution — How and to whom you distribute data is regulated under the license
  • Foreign access — Sharing data with foreign entities intersects directly with ITAR/EAR
  • Archiving — May require maintaining records of what was collected and when
07
ITAR / EAR — Export Control
Criminal Exposure — Highest Stakes Regulatory Area
ITAR violations are federal criminal offenses. Fines up to $1M per violation. Prison time. This is not a compliance checkbox — it is the single highest-stakes regulatory area Sidereal operates in. Treat it accordingly from day one.
The Two Regimes
RegimeAuthorityGovernsList
ITAR State Dept DDTC Military satellites, defense items, certain high-performance sensors, classified tech USML — US Munitions List
EAR Commerce BIS Most commercial satellites, CubeSat components, commercial ground systems CCL — Commerce Control List

The 2014 Export Control Reform moved most commercial satellites from USML to CCL. EAR is less restrictive than ITAR. Most clients operate under EAR. Never assume — always verify with qualified counsel.

What Constitutes an Export
Deemed Exports — Where Universities Get Into Trouble
Sharing technical data with a foreign national inside the United States is still an export. An international graduate student working on controlled hardware = potential daily export violation. Flag this at intake for every university client.
  • Physically shipping hardware overseas
  • Sharing technical data with a foreign national — anywhere, including inside the US
  • Emailing a CAD drawing to a foreign colleague
  • Discussing controlled technical details with a foreign person by phone
  • Allowing foreign national access to controlled software or systems
Key Documents & Requirements
DocumentRequired WhenTimeline
CJ / Classification Request Determining USML vs. CCL for hardware or technology Varies, submit early
TAA — Technical Assistance Agreement Any technical exchange with foreign launch provider or partner 60–90 days minimum, often longer
TCP — Technology Control Plan Orgs with foreign nationals accessing controlled technology Before any access occurs
Foreign Launch Vehicle — Hard Stop
Launching on ISRO, Vega, H3 or any foreign vehicle requires a TAA approved by DDTC before any technical exchange — before engineers are on a phone call with the foreign team. Before the ICD process begins. If no TAA is in place, stop the process and get legal counsel immediately.
Sidereal's Obligations

Sidereal is not an export control attorney. Never position as one. But we must:

  • Identify risk at intake — Ask every client about defense applications, foreign nationals, foreign launch vehicles, encryption, and whether they have a classification determination
  • Maintain qualified legal partners — Space-specific export control firms, not general counsel
  • Build into standard onboarding — Export control assessment is not optional and not deferred
  • Protect Sidereal itself — Client service agreements must include export compliance representations. Our own contracts need export control legal review.
08
Debris Mitigation

Debris mitigation has moved from best practice to hard regulatory requirement. The FCC 2022 rule change was significant. These requirements must be addressed at design stage — they cannot be retrofitted.

Key Rules
RuleRequirementOrbitEffective
FCC 5-Year Rule Satellites must deorbit within 5 years of mission completion LEO (<2000km) 2022 (updated from 25yr)
GEO Graveyard Move to disposal orbit ~300km above GEO at end of life GEO (35,786km) Longstanding requirement
Passivation All stored energy depleted at end of life — batteries, propellant, pressurized vessels All Required, design-stage
The Propulsion Problem

Collision avoidance requires the ability to maneuver. Most basic CubeSats have no propulsion. Implications:

  • FCC increasingly scrutinizes whether satellites can maneuver in license applications
  • Some launch providers beginning to require propulsion capability at higher orbits
  • Clients without propulsion cannot actively avoid conjunctions — orbit selection must account for this
  • Orbit selection advice at Phase 1 must reflect debris mitigation reality
Conjunction Analysis Resources
  • Space Force 18th Space Control Squadron — Provides free conjunction data messages (CDMs) to US operators via Space-Track.org
  • LeoLabs — Commercial tracking, more detailed analysis
  • ExoAnalytic — Commercial optical tracking network
Regulatory Watch Items
  • FCC bond proposal — $1M per satellite bond to incentivize deorbit compliance. Not yet final. Monitor closely — significant cost impact for constellation operators.
  • Active debris removal — Astroscale and others developing commercial removal services. Not yet routine but regulatory requirements may eventually mandate it.
  • ITU framework — Beginning to incorporate debris mitigation. International standards tightening.
09
Insurance

Space insurance is a thin, specialized market dominated by Lloyd's of London syndicates. A handful of brokers — Marsh, Aon, and boutique firms — hold the key relationships. Sidereal maintains referral relationships with specialist brokers. We are not insurance brokers.

Coverage Types
CoveragePeriodStatusTypical Premium
Pre-Launch Manufacturing through ignition Optional Varies by satellite value
Launch Ignition through T+30 days Recommended 5–15% of insured value
In-Orbit Operational life, annual Optional Annual premium, varies
Third-Party Liability Full mission MANDATORY $20K–$100K typical
Third-Party Liability Is Non-Negotiable
Required by the launch operator as a condition of manifest. No coverage = no launch. Minimum coverage typically $500M–$1.5B. Premiums are modest ($20K–$100K) because the probability of catastrophic third-party damage is extremely low. No client launches without this in place.
Rideshare Specific — Cross-Waiver of Liability

Standard in all rideshare agreements. Every party — launch provider, aggregator, all payload customers — waives the right to sue each other for losses arising from the launch. Client's recourse in a launch failure is against their own insurer, not SpaceX. Make sure every client understands this before they sign.

Ground Transportation Insurance

Standard freight insurance is insufficient for space hardware. Requires:

  • All-risk coverage specifically endorsed for space hardware
  • No exclusions for electronic or mechanical breakdown
  • Full replacement value — not depreciated value
  • Specific handling requirements written into the policy
Insurance as a Critical Path Item
INSURANCE GATES BY PHASE Phase 1: Budget for premiums — surface early Phase 2: Engage specialist broker Third-party liability quote obtained Phase 5: Third-party liability in place before manifest close Phase 6: Ground transit coverage active before payload ships Post-sep: Insurance notification if anomaly occurs Most policies require prompt notification
10
Ground Transport & Physical Handling

A satellite is the most expensive, least replaceable, most environmentally sensitive piece of cargo you will ever move. Sidereal's brand is built or damaged most visibly in physical operations. The standard of care must reflect that reality.

The Physical Journey
Client facility (final assembly & testing) ↓ Environmental test facility (if not on-site) ↓ Integration facility (aggregator or launch provider) ↓ Launch site (vehicle integration) ↓ Launch pad

Each transition is a handoff. Each handoff is a risk point. Sidereal manages every one.

Transportation Modes
ModeUse CaseRequirementsKey Risk
Dedicated Ground (truck) Primary domestic mode Dedicated vehicle, air-ride suspension, climate controlled, GPS tracked Vibration, temperature exceedance
Air Freight International or time-critical IATA DG compliance, export docs, customs clearance Documentation delays, handling standards vary by carrier
Hand Carry Small CubeSats, short distances FAA battery approval, export docs, airline pre-approval Personnel continuity, baggage handling
Environmental Monitoring

Every shipment requires calibrated data loggers inside the container recording:

  • Temperature — Continuous log, typically ±1°C resolution
  • Humidity — Relative humidity throughout transit
  • Shock and vibration — Accelerometer data, records any exceedances
  • Pressure — For pressurized containers

Logger data is reviewed immediately upon arrival. Any exceedance triggers a review process before integration proceeds. Sidereal escalates — does not proceed silently.

Chain of Custody
Transfer Receipt Required on Every Handoff
Every physical handoff is documented: who released, who received, condition at transfer, container integrity, data logger status, time and location. Sidereal maintains a standard transfer receipt template used on every mission.
Dangerous Goods

Identify at intake. Do not discover at the shipping dock.

  • Lithium batteries — IATA Class 9 for air shipment
  • Propellant — Classification varies by type
  • Compressed gases — Cold gas propulsion systems
  • Radioactive materials — Rare but used in some scientific payloads
Integration Facility Evaluation Criteria
  • Cleanroom class and capacity (ISO 5, 7, or 8)
  • Handling equipment appropriate for payload size and mass
  • Technical expertise of integration staff and handling certification
  • Aggregator relationship and location relative to launch site
  • Physical security and access controls
  • Track record — missions integrated successfully
11
Post-Launch Operations

Launch day is the finish line in a client's mind. It is not. The first 72 hours post-separation are statistically the highest-risk period of the entire mission. Sidereal is present throughout.

Early Orbit Checklist
EARLY ORBIT — 72 HOUR REFERENCE Hour 0–1: Confirm separation via launch provider / aggregator Hour 1–6: Await first AOS window Monitor ground station for signal Hour 6–24: First contact attempt on multiple passes Pull TLE from Space-Track when published Begin satellite identification (rideshare) Hour 24–48: Establish stable comms link Confirm attitude control Confirm power generation (solar panels) Confirm thermal within limits Hour 48–72: Begin payload commissioning if bus is healthy Confirm all deployables deployed Initial telemetry health report
Rideshare ID Process
When 30 satellites separate from a dispenser in a short period, the Space Force takes days to assign TLEs to individual objects. Brief clients on this before launch. Silence on the first pass is not catastrophic — it is common.
Ground Station Networks
ProviderModelStrengthBest For
AWS Ground Station Pay-per-pass Global coverage, AWS cloud integration EO clients with data processing needs
KSAT Subscription / per-pass Largest network, agency-grade High-reliability, high-volume missions
Leaf Space Per-pass Small sat focus, European base Small commercial operators
Atlas Space Ops Subscription Growing US network US domestic missions
SatNOGS Open source, free Low cost, community-run University / amateur, limited capability
Common Early Orbit Anomalies
AnomalyLikely CauseSidereal Role
No signal on first pass Antenna deployment, software, power, or ground station pointing error Rule out ground station first. Calm, methodical triage support.
Partial / degraded signal Antenna or radio issue Facilitate access to higher-gain ground station options
Incorrect orbit Launch vehicle delivery error Notify insurer immediately. Coordinate with aggregator. Insurance claim support.
Power anomaly Solar panel deployment failure, pointing issue, cell damage Critical — escalate immediately. Client engineering team leads diagnosis.
Service Boundary — Critical
Sidereal Facilitates. The Client's Team Operates.
Sidereal is not a mission operations company. We do not run satellites. The risk of scope creep is real — a distressed client will ask for more than we can deliver. Stay in the lane: coordinate, advise, connect to resources. Do not overextend into spacecraft operations.
12
Client Intake Process

Intake is not a sales call. It is a diagnostic. The goal is to assess whether Sidereal can serve this client, what their risk profile looks like, and what the engagement will require. Done correctly it protects Sidereal from bad engagements and sets the client up for a successful mission.

Area 1 — Mission Profile
Mission Profile Questions
1.1What is the primary mission objective?
1.2What orbit do you need — altitude, inclination, and why?
1.3What is your target launch date and what is driving that date?
1.4What is your payload mass and volume — measured, not estimated?
1.5What form factor — CubeSat standard, ESPA, custom?
1.6Have you identified a target launch vehicle or are you open to recommendations?
1.7Is this a one-time launch or are you planning multiple missions?

Listen for: "As soon as possible" with no real constraint = not ready. "Approximately" for mass/volume = hasn't been measured = readiness flag.

Area 2 — Hardware Readiness
Hardware Readiness Questions
2.1What is your current development stage — concept, PDR, CDR, engineering model, flight model?
2.2Have you completed or scheduled environmental testing — vibration, TVAC, EMC?
2.3Do you have a qualified test facility identified?
2.4Have you reviewed the PUG for your target launch vehicle?
2.5Does your satellite have propulsion? If so, what type and propellant?
2.6Do you have deployables — antennas, solar panels, booms?
2.7What is your end of life disposal approach?

Listen for: Propulsion = immediate ITAR/safety flag. No disposal plan = regulatory flag. Early design stage with aggressive timeline = capacity mismatch.

Area 3 — Regulatory Status
Regulatory Status Questions
3.1Have you completed an export control classification determination?
3.2Are there any foreign nationals on your development team or foreign investors?
3.3Are you planning to launch on a foreign vehicle?
3.4What frequency bands does your satellite use?
3.5Have you filed or begun an FCC license application?
3.6Does your satellite collect Earth observation data?
3.7Do you have export control counsel engaged?

Hard stops: Foreign nationals + controlled technology + no TCP or counsel = stop until resolved. Foreign vehicle + no TAA = stop immediately.

Area 4 — Commercial Readiness
Commercial Readiness Questions
4.1What is your budget for launch and logistics services?
4.2Is that budget secured and funded, or contingent on future fundraising?
4.3Do you have a signed contract with a launch provider or aggregator already?
4.4Do you have launch insurance or third-party liability coverage?
4.5Who is your legal counsel for the mission?
4.6Are you aware of the non-refundable deposit structure at booking?

Listen for: Unfunded budget = do not commit Sidereal resources yet. Already-signed launch agreement = review immediately before proceeding.

Area 5 — Team Assessment
Team Assessment Questions
5.1Who is the mission lead and single point of contact for Sidereal?
5.2Does that person have authority to approve documents and make decisions?
5.3What is the size of your technical team?
5.4Have any team members launched a satellite before?
5.5Who will operate the satellite post-launch?
5.6What is your ground station plan?

Listen for: No single decision-maker = operational chaos ahead. Small team with aggressive timeline = scope the engagement accordingly and price for higher support burden.

Intake Risk Classification
ClassificationCriteriaAction
Hard Stop Foreign nationals + controlled tech + no TCP/counsel; foreign vehicle + no TAA; unfunded budget + sub-12mo timeline; propulsion + no ITAR classification Do not proceed until resolved. Specify exactly what is needed.
Elevated Risk First-time operator + aggressive timeline; early design stage; no FCC filing; no legal counsel; team under 5 people Proceed with higher engagement level. Scope and price accordingly.
Standard 18+ month timeline; hardware in CDR or later; regulatory awareness present; funded budget; prior launch experience on team Proceed with standard intake process.
Intake Meeting Structure
First 10 minutes
Client Presents
Let them tell you what they're building. Don't interrupt. What they skip is often more revealing than what they cover.
Next 30 minutes
Structured Discovery
Work through all five areas methodically. Frame as helping you serve them better — which is true.
Final 20 minutes
Preliminary Feedback
Give honest preliminary assessment: what looks strong, what concerns you, and three specific immediate action items. Walking out with three action items you've identified — before they've paid you — demonstrates expertise and builds trust.
Post-Intake — 48 Hour Standard
  • Send intake document summary to client for confirmation
  • Issue preliminary risk assessment if flags were identified
  • If proceeding — send scoping questionnaire for any gaps
  • If conditional — specify exactly what needs resolution and by when
  • If declining — do it professionally with a brief explanation

The 48-hour turnaround is a signal of operational discipline. A logistics company that takes two weeks to follow up after an intake meeting is telling you something about how they'll manage your launch timeline.

Mission Readiness Assessment — Paid Service Option
Revenue Opportunity
For clients not yet ready to commit to a full engagement, offer a paid Mission Readiness Assessment covering all five intake areas. Deliverable: written report with specific recommendations and action items. Price point: $2,500–$5,000 depending on complexity. Filters serious clients from tire-kickers. Builds the relationship before the launch engagement begins.
13
Acronyms & Terminology

Quick reference for acronyms and terms used across Sidereal operations. Organized by domain. Everyone on the team should be fluent in all entries — clients and partners use these without defining them.

Regulatory Bodies & Frameworks
AcronymFull TermContext
FAA ASTFAA Office of Commercial Space TransportationIssues commercial launch licenses. Launch operators must hold this — not Sidereal, but clients feed documentation into it.
FCCFederal Communications CommissionLicenses satellite radio frequency use. Part 25 for commercial, Experimental for R&D, Part 97 for amateur.
NOAA CRSRACommercial Remote Sensing Regulatory AffairsNOAA office that licenses Earth observation satellites. Tier 1–3 based on sensor capability.
DDTCDirectorate of Defense Trade ControlsState Dept office administering ITAR. Issues TAAs and export licenses for USML items.
BISBureau of Industry and SecurityCommerce Dept office administering EAR. Manages CCL items — most commercial satellites.
ITARInternational Traffic in Arms RegulationsControls export of defense articles on USML. Criminal penalties. Violations = federal prosecution, $1M per count, prison.
EARExport Administration RegulationsControls export of commercial/dual-use items on CCL. Less restrictive than ITAR. Most commercial satellites.
USMLUnited States Munitions ListList of defense articles controlled under ITAR. Military satellites, certain sensors, propulsion systems.
CCLCommerce Control ListList of items controlled under EAR. Most commercial satellites moved here from USML in 2014.
ITUInternational Telecommunication UnionUN agency managing global radio frequency coordination. Every satellite operating internationally requires ITU filing.
IADCInter-Agency Space Debris Coordination CommitteeInternational body setting debris mitigation guidelines that inform national regulations including FCC rules.
IARUInternational Amateur Radio UnionCoordinates amateur satellite frequency coordination internationally. Part 97 path runs through them.
Export Control Documents
AcronymFull TermWhen Required
TAATechnical Assistance AgreementRequired before any technical exchange with a foreign launch provider or foreign partner. DDTC approval: 60–90+ days minimum. Must precede ICD process.
TCPTechnology Control PlanRequired when foreign nationals have access to controlled technology. Documents who has access, what they can see, and physical/cyber controls in place.
CJCommodity Jurisdiction RequestRequest to State Dept DDTC to determine if an item falls under ITAR (USML) or EAR (CCL). Required when classification is unclear.
ELExport LicenseLicense required for controlled exports when no exemption applies. Issued by DDTC (ITAR) or BIS (EAR).
Mission & Launch Operations
AcronymFull TermContext
PUGPayload User's GuideLaunch provider's bible for payload requirements. Mass limits, interface specs, RF restrictions, documentation checklist. Treat as a routing guide — know every major provider's PUG cold.
ICDInterface Control DocumentTechnical document defining exactly how payload connects to dispenser. Signed by client and aggregator. Hard gate — nothing advances without it.
LSALaunch Services AgreementContract between payload customer and launch provider or aggregator. Deposit 25–30% non-refundable at execution.
AOSAcquisition of SignalFirst successful contact between ground station and satellite post-separation. The critical moment in early orbit operations.
LOSLoss of SignalEnd of a ground station contact window as satellite passes below horizon.
TLETwo-Line Element SetStandardized orbital parameter format published by US Space Force via Space-Track.org. Used to predict satellite passes for ground station scheduling.
CDMConjunction Data MessageWarning from US Space Force's 18th Space Control Squadron flagging predicted close approach between space objects.
TT&CTelemetry, Tracking and CommandThe communications system for monitoring (telemetry) and controlling (command) a satellite from the ground.
LEOPLaunch and Early Orbit PhaseThe critical period from separation through initial satellite commissioning. Statistically highest-risk period of the mission.
PDRPreliminary Design ReviewEarly design milestone — concept validated, requirements baselined. Concept and PDR stage with aggressive timeline = readiness flag.
CDRCritical Design ReviewDesign finalized and frozen. Ready to build flight hardware. CDR or later with 12+ months to launch = manageable.
TVACThermal Vacuum TestingEnvironmental test simulating space's thermal and vacuum conditions. Queue can be 3–4 months — book early.
EMCElectromagnetic CompatibilityTest confirming satellite does not interfere with launch vehicle or other payloads electromagnetically.
EMIElectromagnetic InterferenceUnwanted electromagnetic energy that disrupts satellite or vehicle systems. Tested during EMC campaign.
BOMBill of MaterialsComplete list of satellite materials and components. Reviewed against PUG prohibited materials list.
CoGCenter of GravityBalance point of the satellite. Must be within limits defined in PUG — measured, not estimated.
Orbits & Space Environment
AcronymFull TermContext
LEOLow Earth OrbitBelow ~2,000km. Most small satellites operate here. FCC 5-year deorbit rule applies.
SSOSun-Synchronous OrbitNear-polar LEO where satellite passes over any point at the same local solar time. Standard for Earth observation. SpaceX Transporter missions deploy here (~525km).
MEOMedium Earth Orbit~2,000–35,786km. GPS satellites operate here. Less regulated for debris but increasing scrutiny.
GEOGeostationary Orbit35,786km. Satellite appears stationary relative to Earth. End-of-life: must move to graveyard orbit ~300km above GEO.
GTOGeostationary Transfer OrbitElliptical transfer orbit from LEO to GEO.
ISSInternational Space StationOrbits at ~400km. Deployment point for some CubeSats via cargo resupply missions.
Satellite Hardware
AcronymFull TermContext
CubeSatCube SatelliteStandardized form factor. 1U = 10×10×10cm, ~1.33kg max. Common sizes: 3U, 6U, 12U. CDS defines the standard.
CDSCubeSat Design SpecificationCal Poly standard defining CubeSat mechanical interface. Referenced in most launch provider PUGs.
ESPAEELV Secondary Payload AdapterStandard interface ring for medium-class secondary payloads up to ~180kg.
ADCSAttitude Determination and Control SystemSubsystem determining and controlling satellite pointing. Critical for EO payloads and power generation.
EPSElectrical Power SystemManages solar power generation, battery storage, and distribution across satellite subsystems.
OBCOn-Board ComputerCentral processor managing all satellite subsystems autonomously.
SARSynthetic Aperture RadarActive radar imaging system. Triggers NOAA remote sensing license requirement.
Frequency Bands
BandRangeTypical UseLicensing Complexity
UHF300 MHz – 3 GHzCubeSat TT&C, amateur satellites. Low data rate, simple hardware.Low
S-band2 – 4 GHzTelemetry and command. Common for small satellites.Low–Medium
X-band8 – 12 GHzHigh-rate EO data downlink. Requires more complex ground infrastructure.Medium
Ka-band26 – 40 GHzHigh-throughput comms. Large constellations (Starlink). Rare for small operators.High
Insurance & Risk
AcronymFull TermContext
TPLThird-Party LiabilityMandatory insurance. Covers damage to third parties (other satellites, foreign property, people). $500M–$1.5B minimum. Required by launch operator before manifest confirmation.
E&OErrors and OmissionsProfessional liability insurance. Covers Sidereal's own service delivery liability — required for a company handling high-value hardware and regulated transactions.
RAGRed / Amber / GreenStatus classification system used in tracker regulatory status fields. Red = at risk, Amber = needs attention, Green = on track.
LOILetter of IntentNon-binding expression of intent to engage. Precursor to a formal contract. Used in early customer traction / credibility-building strategy.
Sidereal Internal Shorthand
TermDefinition
MRAMission Readiness Assessment — paid pre-engagement deliverable. $3,000–$5,000. Filters tire-kickers, builds relationship before formal engagement.
FMMFull Mission Management — core Sidereal service. $25,000–$75,000 depending on mission complexity. Milestone-billed across 4 gates.
Hard StopIntake flag requiring immediate resolution before any engagement activity proceeds. No exceptions, no workarounds.
ElevatedIntake flag requiring heightened engagement level and higher support pricing. Not disqualifying — scope and price accordingly.
GateQuality checkpoint requiring founder review and sign-off before work advances. Four gates per full engagement: intake, ICD, manifest, launch.
Manifest CloseAggregator's hard deadline for final payload documentation package. Miss it = off the mission, deposit forfeited. No exceptions.
Pass-Through MarginMarkup (8–20%) applied to third-party costs (aggregator booking, transport, insurance) billed to client. Standard in logistics brokerage.
Deemed ExportSharing controlled technology with a foreign national inside the US — still constitutes an export under ITAR/EAR. Most common unintentional violation at universities.
PUG Routing GuideSidereal's internal reference of all major launch provider and aggregator PUGs, organized as a lookup by vehicle, orbit, form factor, and timeline.
14
Launch Provider Notes

Operational intelligence on launch providers and rideshare aggregators — PUG version tracking, manifest cadence, quirks, contact intelligence, and lessons from direct engagement. Add entries as relationships develop.

What Belongs Here
PUG version numbers and last-verified dates, manifest close lead times, pricing intelligence, contact names at aggregators, payload review process nuances, anything not in the published PUG that you learned through direct engagement.
No provider notes yet
Add the first entry when you engage with an aggregator or launch provider directly.
New Provider Entry
Provider / Aggregator Name *
Primary Contact
Pricing Intel
Operational Notes
PUG Reference
PUG Version
Last Verified
PUG File Link
Max Mass (kg)
Form Factors Accepted
Orbits Available
Manifest Lead Time
RF Restrictions (Ascent)
Prohibited Materials / Key Restrictions
PUG Notes — Things Not in the Document
Added By *
Status
15
Aggregator Intelligence

Proprietary intelligence on rideshare aggregators — pricing dynamics, relationship status, mission history, volume leverage, and anything that gives Sidereal an edge in negotiation and client matching.

No aggregator intelligence yet
Add the first entry after initial outreach to Exolaunch or Spaceflight.
New Aggregator Entry
Aggregator Name *
Relationship Status
Mission Manager Contact
Volume Pricing Threshold
Missions Completed via Sidereal
Pricing Intelligence
Relationship Notes
Added By *
Status
16
Partner Directory

Live contact directory for all active Sidereal partners — legal, insurance, test facilities, freight carriers, ground stations, technical consultants. One entry per partner. Update as relationships develop.

No partners added yet
Add the first entry when export counsel or insurance broker relationship is established.
New Partner Entry
Partner / Firm Name *
Category
Primary Contact
Agreement Type
Referral / Commission Terms
Missions Used On
Notes
Added By *
Status
17
Lessons Learned

Post-mission and post-engagement debriefs. What happened, what caused it, and what changes as a result. Every entry here makes the next mission better. This section compounds in value over time.

Anonymization Rule
Client-specific details should be anonymized before entry. Use mission type and complexity profile rather than client name. The lesson is what matters, not the attribution.
No lessons recorded yet
Add the first entry after completing a discovery call, intake, or any engagement where something unexpected occurred.
New Lesson Entry
Title / What Happened *
Phase Where This Occurred
Category
What Caused It
What Changes as a Result
Playbook / Wiki Update Required?
Added By *
Status
18
Regulatory Updates

Tracked changes to the regulatory environment — new rules, proposed rulemakings, enforcement actions, ITU updates, and anything that affects client obligations or Sidereal's compliance posture. Log here and update affected wiki sections.

No regulatory updates logged yet
Add entries when rule changes are published, proposed rulemakings are issued, or enforcement actions occur that affect space logistics operations.
New Regulatory Update
Update Title *
Agency
Rule Type
Effective Date
What Changed
Impact on Sidereal Clients
Wiki Section to Update
Added By *
Status
19
Client Patterns

Anonymized patterns from intake conversations and client engagements. Not client-specific records — those live in the tracker. This is pattern recognition: what types of clients tend to have which problems, what questions reveal the most, what assumptions are consistently wrong.

How to Use This Section
After every intake or discovery call, ask: did anything surprise me? Did a pattern repeat? Did a client reveal something that changes how I ask questions? That goes here. Over time this becomes your most valuable intake intelligence.
No client patterns recorded yet
Add the first entry after completing a discovery call or intake — even a failed one.
New Client Pattern
Pattern Title *
Client Segment
Intake Area Where Observed
What the Pattern Is
How It Affects the Engagement
How to Surface It Earlier
Times Observed
Added By *
20
Custom Additions

Freeform entries for knowledge that doesn't fit sections 14–19. Tag it, date it, attribute it. If a topic accumulates three or more entries it probably warrants its own section — flag it for review.

No custom entries yet
Add anything that belongs in the institutional knowledge base but doesn't fit the structured sections above.
New Custom Entry
Title *
Tag / Category
Source / Basis
Content *
Why It Matters / How to Use It
Added By *
Warrants Own Section?
Status
21
Decision Log

A permanent record of significant decisions — what was decided, why, what alternatives were considered, and what it unlocks or closes off. This is institutional memory. Six months from now, a hire should be able to read this log and understand not just what Sidereal does but why it does it that way.

What Belongs Here
Significant directional decisions — name, entity structure, pricing model, service scope, first hire, partner commitments, market focus. Not every small operational call. The test: would a new hire reading this six months from now say "I understand why we do it this way"? If yes, log it.
One-Way Door vs. Two-Way Door
A one-way door decision is hard to reverse — entity structure, equity agreements, key hires, major partner commitments. A two-way door is easy to undo — pricing experiment, outreach approach, tool choice. One-way doors warrant more deliberation and more detailed logging. Two-way doors can move fast.
No decisions logged yet
Start with the decisions already made — rebrand to Sidereal, university CubeSat programs as beachhead, OS-first service model. Log decisions as they happen going forward.
Log a Decision
Decision — One Clear Sentence *
Decision Type
Door Type
Context — What Drove This Decision
Options Considered
Rationale — Why This Option
What This Unlocks or Closes Off
Owner *
Status
↑ Back to top
Wiki Tracker Playbooks Command Center
Brand & Supporting
↳ Brand Assets ↳ Email Signature ↳ Card Generator ↳ Values