CosmosExplore 環宇探索

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.

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

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
WindowFocusObjectiveDeliverablesGateNodes
0-3 monthsMission ledger and hard boundary lockWrite 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.
3-6 monthsAuthority-path triageIdentify 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.
6-12 monthsHosted-payload and partner searchTry 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.
12-18 monthsNon-flight engineering evidenceBuild 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.
18-24 monthsAuthority and integration packagePrepare 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.
24-30 monthsManifest readiness or no-goIf 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.
30-36 monthsVerified message or audited stopEither 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.

Earliest credible path

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.

Compression levers

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

10-year plan table

YearFocusObjectiveDeliverablesExit gateKey difficultyNodes
Year 1Receive-only literacy and mission ledgerLearn 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.
Year 2Authority path and ground segment boundaryDecide 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.
Year 3Payload reduction and hosted-payload testReduce 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.
Year 4Engineering model and test cultureBuild 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.
Year 5Mission definition reviewRun 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.
Year 6Formal authorization and coordination packageWith 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.
Year 7Flight-unit readiness and disposal caseMove 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.
Year 8Manifest, launch integration, and rehearsalEnter 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.
Year 9Launch, early operations, and verified messageAfter 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.
Year 10Post-mission disposal, archive, and second-mission decisionClose 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.

Readiness gates

Readiness gates

Critical difficulties

Critical difficulties

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.

出典

出典