North Star

Personal communications satellite ten-year roadmap

A decade-scale, source-backed route from receive-only literacy to one verified message from low Earth orbit. It is a review plan, not a license, launch booking, build recipe, or safety assessment.

已評審: 2026-06-10評審到期: 2026-12-10

範圍: Personal or small-team learning path for a compliant small communications payload or spacecraft. Commercial communications service, remote-sensing service, self-developed orbital launch, and launch-service provision are out of scope.

預設邊界: No transmission, launch integration, payload operation, or public service claim proceeds without a documented authority path and qualified review.

Sprint 001 triage 打開任務階梯 LEO message 圖譜

North Star

North Star: one compliant verified message from LEO

CosmosExplore treats the first personal communications-satellite milestone as a public evidence event: one small authenticated, logged, verifiable message from low Earth orbit, with authority, integration, disposal, and post-mission records attached.

This is small enough to be inspectable, but hard enough to force the real gates: spectrum authority, payload scope, spacecraft minimums, launch integration, orbital-debris responsibility, operations evidence, and truthful post-mission accounting.

Knowledge base posture: CosmosExplore is built as a strong knowledge base, but its knowledge graph is biased toward the North Star: facts are prioritized when they clarify gates, reduce payload scope, expose authority or integration blockers, improve evidence, or create an honest no-go record.

Not the goal

commercial communications service
public connectivity product
remote-sensing service
self-developed orbital launch
hardware build recipe
legal or safety shortcut

Success: The first public success criterion is a small authenticated, logged, verifiable message from LEO, paired with documented authority, integration, disposal, and post-mission records.

Three-year aggressive path

A 36-month path is possible only as a gate-bound stretch target: reduce the mission to the smallest verified-message payload, prefer hosted payload or partner/integrator paths, and run authority, funding, team, payload, and evidence work in parallel. A from-scratch full communications satellite or any self-developed launch path is outside this three-year claim.

Success: By month 36, either produce a compliant LEO verified-message evidence packet, or produce a clear no-go record explaining which gate blocked the mission.

Assumptions

The mission remains personal, non-commercial, and evidence-first.
Qualified regulatory and legal review is available before any transmission or launch commitment.
Hosted payload, education/non-profit, or experienced integrator paths are investigated before full spacecraft ownership.
Funding and team responsibility are treated as gates, not optimism.
A slip is acceptable; an unsafe shortcut is not.

Window36months

Gate5hard gates

SuccessLEOverified message or audited no-go

Window	Focus	Objective	Deliverables	Gate	Nodes
0-3 months	Mission ledger and hard boundary lock	Write the private mission ledger, freeze the North Star success criterion, and make the not-goal list explicit.	private mission ledger initialized verified-message definition public-claims boundary first go/no-go gate	No hardware, transmission, or launch path is discussed as real until the ledger can state the authority questions and stop rules.	Mission review ledger LEO verified message Personal, not commercial boundary
3-6 months	Authority-path triage	Identify whether the mission belongs near amateur-satellite, experimental, or Part 25 review, and record the qualified-review path.	authority-path matrix qualified-review contact list stop-transmission responsibility question remote-sensing negative check	If no credible authority path exists, stop the 36-month attempt and preserve the no-go record.	Frequency authorization Amateur-radio satellite service Command uplink boundary Remote sensing boundary
6-12 months	Hosted-payload and partner search	Try to collapse the mission into a hosted payload, education/non-profit program, or experienced integrator path.	hosted-payload decision memo partner/integrator shortlist payload minimum definition budget envelope	If the message goal requires full spacecraft ownership, explicitly accept the longer safety, funding, and integration path before continuing.	Hosted payload Payload definition Payload integration review Rideshare deployer
12-18 months	Non-flight engineering evidence	Build evidence around the non-flight model: power, thermal, avionics, data integrity, safe mode, and operations rehearsal boundaries.	non-flight engineering-model log power/thermal review notes data-integrity test log safe-mode rationale	No bench artifact is called flight-ready; evidence only supports the next review.	Power budget Thermal budget Onboard computer Data integrity check Safe mode
18-24 months	Authority and integration package	Prepare the authority, payload-review, integrator, disposal, and evidence package with qualified support.	authority package outline payload review information map integration checklist disposal case draft	No launch/integration commitment proceeds if the authority path, disposal case, or responsibility map is unresolved.	Frequency authorization Payload integration review Orbit selection Orbital debris mitigation Deorbit / disposal plan
24-30 months	Manifest readiness or no-go	If partner and authority paths hold, move toward manifest readiness; otherwise record no-go and preserve the learning.	manifest-readiness review operations rehearsal record go/no-go decision public claims review	The mission can still stop without shame; stopping with evidence is better than flying a weak case.	Rideshare deployer Mission review ledger Ground station Data integrity check
30-36 months	Verified message or audited stop	Either reach the verified LEO message evidence packet or close the attempt with a precise blocker map.	verified-message packet or blocker map authority/evidence index post-attempt report next-mission decision	A message without authority, context, and disposal record is not a success.	LEO verified message Telemetry beacon Payload recovery Mission review ledger

Earliest credible path

The fastest serious route is to reduce the mission before building it: prove the message objective through a hosted payload or education/non-profit partnership if possible; move to a full CubeSat-class spacecraft only if the payload cannot be hosted.

0-12 monthsDefine the message and authority pathLock the success criterion, receive-only evidence practice, mission ledger, and candidate authority routes before any transmitting system is treated as a plan.

LEO verified message Mission review ledger Frequency authorization

12-24 monthsReduce to hosted payload if possibleAsk whether the message objective can ride on another platform, program, or integrator path so the first milestone is evidence and compliance, not full spacecraft ownership.

Hosted payload Payload definition Payload integration review

24-48 monthsParallel qualified reviewsRun spectrum, payload, remote-sensing applicability, funding, team roles, and non-flight engineering-model evidence in parallel, but make each one a stop gate.

Amateur-radio satellite service Remote sensing boundary Power budget Thermal budget Safe mode

48-72 monthsFull spacecraft only if still necessaryIf hosting cannot satisfy the North Star, enter a full spacecraft path through integrator and rideshare review, with disposal and operations evidence visible before commitment.

Rideshare deployer Orbit selection Orbital debris mitigation Deorbit / disposal plan

Compression levers

ConstraintParallelize review, not shortcutsAuthority-path research, receive-only evidence practice, payload reduction, engineering-model testing, and team/funding discovery can start in parallel.

Constraint: Transmission, launch integration, and public service claims still wait for qualified review.

ConstraintShrink the mission before buying hardwareA hosted payload or partner program can preserve the North Star while removing some full-spacecraft burden.

Constraint: If the project needs operator control of a spacecraft, it must accept the full safety and regulatory surface.

ConstraintMake funding a gate earlyLaunch price is only one line item; counsel, integration, testing, documentation, operations, and failure handling need budget room.

Constraint: A public rideshare price cannot be treated as total mission cost.

ConstraintTreat evidence as the productLogs, review packets, source links, anomaly records, and post-mission reports are the asset that makes a personal mission credible.

Constraint: A received message without authority and context is not a CosmosExplore success.

10-year plan table

Year	Focus	Objective	Deliverables	Exit gate	Key difficulty	Nodes
Year 1	Receive-only literacy and mission ledger	Learn satellite identity, public pass prediction, reception provenance, and evidence logging without transmitting.	mission review ledger receive-only observation log source and boundary register first risk list	No transmission or hardware flight claims. The ledger can explain what the mission is, what it is not, who would have authority, and which questions are unanswered.	The hard part is discipline: avoid turning early excitement into unreviewed transmission, public service claims, or hardware promises.	Mission review ledger Ground pass window TLE tracking Data integrity check Personal, not commercial boundary
Year 2	Authority path and ground segment boundary	Decide whether the communications objective belongs to amateur-satellite, experimental, or Part 25 space-station authorization review, and keep the ground segment conceptual.	authority-path matrix ground segment concept non-commercial scope statement stop-transmission responsibility record	A qualified review path is identified before any transmission plan exists. The project can stop if no lawful spectrum path fits the mission.	Spectrum is not a technical afterthought; it is a blocking authorization and coordination problem.	Frequency authorization Ground station Network handoff Amateur-radio satellite service Command uplink boundary
Year 3	Payload reduction and hosted-payload test	Reduce the mission to the smallest payload that can prove the message objective, and test whether a hosted payload avoids full spacecraft responsibility.	payload definition hosted-payload decision record remote-sensing applicability check public claims review	If the objective becomes commercial service, remote sensing, or operator control of a full spacecraft, rescope before continuing.	Scope creep can quietly turn a personal message mission into a regulated service or sensing mission.	Payload definition Hosted payload Payload integration review Remote sensing boundary Personal, not commercial boundary
Year 4	Engineering model and test culture	Build a non-flight engineering model and verification culture around power, thermal, avionics, safe mode, data integrity, and recovery boundaries.	engineering-model test log power and thermal review notes fault and safe-mode rationale data integrity evidence path	The engineering model is not treated as flight hardware. Every subsystem has a review question and a failure mode before integration talk begins.	Small spacecraft fail through ordinary subsystem gaps: power, thermal, avionics, deployment, and recovery assumptions.	Power budget Thermal budget Onboard computer Safe mode Watchdog reset Antenna deployment
Year 5	Mission definition review	Run a preliminary mission definition review: cost envelope, team roles, legal counsel need, integrator fit, and go/no-go criteria.	mission definition review packet budget range and funding plan responsibility map integrator requirement checklist	A credible path exists only if funding, responsibility, authority, and integration constraints are all represented in the same review packet.	The project stops being a hobby exercise when money, liability, and third-party integration enter the plan.	Mission review ledger Rideshare deployer Payload integration review Launch price per kg Deorbit / disposal plan
Year 6	Formal authorization and coordination package	With qualified support, prepare the applicable authorization, coordination, payload-review, and scope-determination package.	licensing counsel engagement record spectrum coordination package outline payload review information map remote-sensing negative or determination path	No launch slot, integration commitment, or transmission capability is treated as real unless the authority path is documented and current.	Regulatory lead time and interagency review can dominate the schedule; shortcuts are project-killing risk.	Frequency authorization Amateur-radio satellite service Payload definition Remote sensing boundary Mission review ledger
Year 7	Flight-unit readiness and disposal case	Move from engineering model to flight-unit readiness only after integration, debris mitigation, disposal, stored-energy, and safe-mode questions are reviewable.	flight-readiness evidence index orbital debris and disposal case stored-energy risk review safe-mode and recovery review	No orbit is acceptable only because it improves contact opportunities. Disposal and stored-energy questions must be visible before manifest commitment.	A long-lived failed object is the clearest way a small mission can create public harm after launch.	Orbit selection Orbital debris mitigation Deorbit / disposal plan Battery safety Safe mode
Year 8	Manifest, launch integration, and rehearsal	Enter manifest and integration only through the launch provider or integrator process, with mission operations rehearsed as evidence rather than improvisation.	launch-integration document index operations rehearsal log day-in-the-life test evidence go/no-go decision record	The mission can still stop if authority, integration, test evidence, or disposal case changes.	Schedule pressure near integration is where weak documentation turns into irreversible commitments.	Rideshare deployer Payload integration review Ground station Data integrity check Mission review ledger
Year 9	Launch, early operations, and verified message	After launch, preserve identity, logs, received data, and authorization evidence around the first verified LEO message.	launch and deployment evidence record first-message verification packet operations anomaly log public claim review	A message is not treated as proof of legal authorization, mission safety, or commercial readiness. It is only the first evidence milestone.	The mission can succeed publicly and still fail legally, operationally, or ethically if evidence and claims are sloppy.	LEO verified message Telemetry beacon Data integrity check Payload recovery Mission review ledger
Year 10	Post-mission disposal, archive, and second-mission decision	Close the mission record: disposal status, anomalies, public lessons, source updates, and a decision on whether a second mission is justified.	post-mission report disposal or status record source and cost re-baseline second-mission decision memo	Do not start a second mission unless the first mission's failures, costs, authority path, and debris/disposal record are public enough to survive hostile review.	The final hard step is truthfulness: preserving failures and costs instead of turning the mission into a victory story.	Deorbit / disposal plan Orbital debris mitigation Payload recovery Mission review ledger Launch price per kg

Readiness gates

gate-authorityAuthority and spectrum gateIs the mission's communications path covered by the correct authorization and coordination route?

停止條件: Stop before transmission planning if the authority path is absent, stale, or mismatched to the mission scope.

Frequency authorization Amateur-radio satellite service Command uplink boundary

FCC Space Stations FCC Small Satellite and Small Spacecraft Licensing Process IARU Amateur Radio Satellite Frequency Coordination

gate-scopePayload scope gateIs the payload still a personal learning mission rather than a communications, remote-sensing, or launch service?

停止條件: Rescope when public claims, data products, or customers appear.

Payload definition Remote sensing boundary Personal, not commercial boundary

NOAA Commercial Remote Sensing Regulatory Affairs: Licensing 15 CFR Part 960 Licensing of Private Remote Sensing Space Systems FAA Payload Reviews

gate-spacecraftSpacecraft minimums gateAre power, thermal, avionics, deployment, safe-mode, and recovery questions reviewable before flight-unit commitment?

停止條件: Do not call hardware flight-ready from a parts list or bench demo.

Power budget Thermal budget Onboard computer Antenna deployment Safe mode

NASA SmallSat Institute: State-of-the-Art of Small Spacecraft Technology NASA CubeSat 101: Basic Concepts and Processes for First-Time CubeSat Developers

gate-disposalOrbit and disposal gateDoes orbit selection come with debris mitigation, disposal, and stored-energy review?

停止條件: Do not select orbit solely for convenient contact windows.

Orbit selection Orbital debris mitigation Deorbit / disposal plan Battery safety

NASA Orbital Debris Program Office: Debris Mitigation U.S. Government Orbital Debris Mitigation Standard Practices, November 2019 Update

gate-integrationIntegration and evidence gateCan the mission satisfy the integrator's document, test, and responsibility expectations?

停止條件: If evidence changes after manifest, reopen the go/no-go record instead of improvising.

Rideshare deployer Payload integration review Mission review ledger

NASA CubeSat 101: Basic Concepts and Processes for First-Time CubeSat Developers NASA SmallSat Institute: Integration, Launch, and Deployment SpaceX Smallsat Rideshare Program

Critical difficulties

blockingAuthorization is the first real blockerA satellite that communicates is not only a device; it is a regulated space and radio operation.

Failure pattern: Building the signal path first and trying to legalize it later.

Frequency authorization Ground station Telemetry beacon

FCC Space Stations 47 CFR § 25.122 Applications for streamlined small space station authorization 47 CFR § 97.207 Space station

blockingScope creep changes the regulatorA camera, a data service, a paying user, or public connectivity language can move the project into a different duty set.

Failure pattern: Calling a mission personal while it behaves like a service.

Personal, not commercial boundary Remote sensing boundary Payload definition

NOAA Commercial Remote Sensing Regulatory Affairs: Licensing 15 CFR Part 960 Licensing of Private Remote Sensing Space Systems FCC Small Satellite and Small Spacecraft Licensing Process

hardFlight assurance is not a parts problemThe hard work is evidence across power, thermal, avionics, deployment, safe mode, and operations.

Failure pattern: Treating COTS availability as flight readiness.

Power budget Thermal budget Onboard computer Safe mode Antenna deployment

NASA SmallSat Institute: State-of-the-Art of Small Spacecraft Technology NASA CubeSat 101: Basic Concepts and Processes for First-Time CubeSat Developers

hardLaunch price is not total mission costA public rideshare price is only the launch anchor; integration, testing, documentation, reviews, and operations can dominate the practical path.

Failure pattern: Budgeting the mission from the launch-price line alone.

Launch price per kg Rideshare deployer Payload integration review Mission review ledger

SpaceX Smallsat Rideshare Program NASA CubeSat 101: Basic Concepts and Processes for First-Time CubeSat Developers NASA SmallSat Institute: Integration, Launch, and Deployment

blockingA failed object remains your missionThe public risk can continue after the message is sent or after the satellite fails.

Failure pattern: Treating disposal as an end-of-plan detail instead of an entry condition.

Orbital debris mitigation Deorbit / disposal plan Battery safety

NASA Orbital Debris Program Office: Debris Mitigation U.S. Government Orbital Debris Mitigation Standard Practices, November 2019 Update

來源

NASA CubeSat 101: Basic Concepts and Processes for First-Time CubeSat Developers NASA SmallSat Institute: State-of-the-Art of Small Spacecraft Technology FCC Space Stations FCC Small Satellite and Small Spacecraft Licensing Process FCC Part 5 Experimental Licensing 47 CFR § 25.122 Applications for streamlined small space station authorization 47 CFR § 97.207 Space station 47 CFR § 97.3 Definitions IARU Amateur Radio Satellite Frequency Coordination FAA Payload Reviews 14 CFR § 450.43 Payload review and determination NOAA Commercial Remote Sensing Regulatory Affairs: Licensing 15 CFR Part 960 Licensing of Private Remote Sensing Space Systems NASA Orbital Debris Program Office: Debris Mitigation U.S. Government Orbital Debris Mitigation Standard Practices, November 2019 Update SpaceX Smallsat Rideshare Program