Readiness level: 2
藍圖
Personal communications satellite blueprint
A clickable readiness map from a personal message-satellite idea to the first qualified trial path. It shows what is ready, what is blocked, and which evidence must exist before a launch or altitude test can even be discussed.
預設邊界: This blueprint is a public-safe readiness map. It is not legal advice, RF guidance, station setup, launch instruction, rocket manufacturing guidance, range procedure, integration instruction, site approval, mission authorization, or flight-readiness claim.
Completion rule: All steps being marked ready means only that a qualified trial path can be reviewed. It does not mean launch, RF transmission, altitude test, safety, legality, funding, site use, or mission success is approved.
North Star / BP review
Aligned if implemented as evidence gatework; conflicting if implemented as a self-developed launch or hardware manufacturing program.
Raw launch-test language can overstate authority, safety, and readiness.
Constraint: Use 'first qualified trial path' until authority, integration, disposal, and evidence gates are closed by qualified review.
Merge adjustment
verified message or audited no-go
Treat the personal journey as evidence storytelling: blueprint -> readiness gates -> private qualified review -> hosted or partner-first trial path -> verified LEO message or precise no-go.
Source pack: docs/personal_satellite_blueprint_source_pack_20260614.md
Current decision
First go/no-go
Go for public-safe blueprint, source indexing, simulation learning, receive-only evidence practice, and non-flight evidence discipline. No-go for self-developed orbital launch, public RF parameters, motor or propellant work, named site planning, launch booking, hardware flight-readiness claims, or sponsor claims that outrun evidence.
Blueprint steps
Readiness gates
Readiness level: 1
Readiness level: 2
Readiness level: 2
Readiness level: 1
Readiness level: 1
Readiness level: 1
Readiness level: 1
Readiness level: 1
Readiness level: 2
Readiness level: 0
Step details
藍圖
01 · Scope, story, and mission ledger
Reduce the journey to a message-only personal mission with a visible no-go list, private ledger, sponsor boundary, and public-claims rule.
Current preparation
- North Star and operating protocol exist.
- Blank private ledger template exists.
- Public claims matrix and no-go template exist.
Missing evidence
- Owner-filled private mission ledger.
- One-paragraph mission-specific success statement.
- Sponsor / video narrative boundary reviewed against public claims.
Next safe action: Fill the private ledger outside committed git and attach the blueprint as the public map.
停止條件: Stop if the mission becomes a commercial communications service, launch service, remote-sensing service, hardware guide, or authorization shortcut.
Nodes
來源
02 · Authority and qualified review map
Map communications authority, payload review, remote-sensing applicability, airspace, and launch operator boundaries before any test is treated as real.
Current preparation
- Authority source matrix exists.
- FCC, FAA, NOAA / CRSRA, IARU, and eCFR source pointers are registered.
- FCC current-access caveat is recorded.
Missing evidence
- Mission-specific authority memo.
- Qualified counsel / agency or experienced reviewer route.
- Private record of which paths are ruled out.
Next safe action: Convert the source matrix into a private authority memo before any RF, launch, or outreach commitment.
停止條件: Stop before transmission planning, launch commitment, or success claim if no credible authority path exists.
Nodes
來源
03 · Cheap-to-formal communicator ladder
Start with cheap evidence practice and move toward formal communication hardware only when authority, integration, and evidence gates support it.
Current preparation
- Receive-only evidence packet template exists.
- NASA SmallSat communications and open receive-network sources are indexed.
- SatNOGS / TinyGS are treated as receive-learning examples only.
Missing evidence
- Private non-radiating bench test log.
- Authority review before any RF transmission.
- Integrator-provided or qualified-reviewed formal communicator path.
Next safe action: Use simulator, wired loopback, stored-data replay, and receive-only observation logs before any transmitter is discussed.
停止條件: Stop if the next step requires publishing frequencies, power, antennas, modulation, commands, uplink, or station setup.
Nodes
來源
04 · Simulation and open-project learning
Use simulation and open projects to learn documentation, tests, interfaces, and failure posture before buying or building flight hardware.
Current preparation
- External project lessons extraction exists for F Prime, cFS, NOS3, and OpenC3.
- OpenRocket is indexed as a model-rocketry simulation learning tool.
- Open-source CubeSat projects are indexed as documentation examples.
Missing evidence
- No technology adoption scorecard for any upstream tool.
- No mission-specific simulation validation record.
- No qualified review of any software or hardware stack.
Next safe action: Create a private tabletop / simulation log that records assumptions, outputs, and why it is not readiness evidence.
停止條件: Stop if a simulator, GitHub repo, or example project is treated as proof of safety, legality, or flight readiness.
Nodes
來源
05 · Non-flight prototype and materials evidence
Build only non-flight evidence: requirements, interface assumptions, material provenance, assembly records, inspection records, and environmental-test questions.
Current preparation
- NASA CSLI and CubeSat.org standards / test indices are available.
- PROVES, OreSat, and PyCubed provide open-source caution and documentation examples.
- Payload-minimum memo skeleton exists.
Missing evidence
- Mission-specific requirements document.
- Non-flight prototype bill of evidence.
- Materials and process review by a qualified reviewer or integrator.
- Environmental verification plan.
Next safe action: Define a non-flight prototype evidence packet without publishing schematics, RF details, or flight integration assumptions.
停止條件: Stop if educational or cheap hardware is treated as spaceflight-ready, or if material choices become a manufacturing recipe.
Nodes
來源
06 · Balloon altitude-test path
Use ballooning as a regulated altitude-test category for payload evidence and storytelling, not as a shortcut to spaceflight.
Current preparation
- 14 CFR Part 101 Subpart D and NASA balloon lifecycle documents are indexed.
- Balloon path is separated from orbital mission readiness.
- No launch location or operational plan is recorded.
Missing evidence
- Local legal / airspace review.
- Landowner or site permission.
- Payload, marking, termination, tracking, recovery, weather, insurance, and hazard records.
- Private launch-day go/no-go checklist.
Next safe action: Create a private balloon-readiness memo with source pointers and stop rules, not a launch procedure.
停止條件: Stop if tracking, recovery, airspace, hazardous payload, land permission, or local law is unresolved.
Nodes
來源
07 · Model and high-power rocketry learning path
Study rocketry only through certified motors, club ranges, safety codes, simulation, insurance, site permission, and FAA / local gates.
Current preparation
- NAR, Tripoli, eCFR Part 101, and OpenRocket sources are indexed.
- Model rocketry and high-power rocketry are separated from orbital launch.
- No launch operation, motor, or range procedure is recorded.
Missing evidence
- Local club / certification route.
- Site owner permission and insurance evidence.
- FAA / local airspace and fire authority review, if applicable.
- Safe payload and recovery boundary review.
Next safe action: Treat rocketry as an external supervised learning path; use OpenRocket only for simulation literacy and club discussion.
停止條件: Stop if the path requires motor making, propellant work, ignition detail, launch procedure, private range operation, or payload hazards.
Nodes
來源
08 · Hosted payload and launch integration path
Test whether the verified-message objective can be reduced to a hosted payload or partner payload before full spacecraft ownership.
Current preparation
- Hosted-payload-first gate exists.
- NASA CSLI, SpaceX rideshare, D-Orbit hosted payload, and CubeSat.org standards sources are indexed.
- No provider, quote, schedule, or integration commitment is public.
Missing evidence
- Private category shortlist.
- Integrator / provider screening questions.
- Responsibility split for authority, testing, operations, disposal, and evidence.
- Qualified review of any named option.
Next safe action: Prepare private hosted-payload screening notes using category questions only.
停止條件: Stop if full spacecraft ownership, launch booking, or provider commitment is assumed before hosted / partner paths are reviewed.
Nodes
來源
09 · Production and test evidence packet
Turn production into a bill of evidence: requirements, versioned artifacts, materials/process review, inspection, environmental testing, anomaly log, and public redaction status.
Current preparation
- Receive-only evidence template exists.
- Gate evidence map exists.
- NASA and CubeSat.org source indices point to standards, testing, and materials/process references.
Missing evidence
- Prototype configuration record.
- Materials / process compliance review.
- Environmental and functional test reports.
- Anomaly and waiver log.
- Public redaction review.
Next safe action: Draft a blank production evidence packet that lists fields without publishing build instructions.
停止條件: Stop if a bill of materials, supplier list, or assembly note becomes a public flight-hardware recipe.
Nodes
來源
10 · Funding, sponsor, and video record
Record the journey as evidence, blockers, learning, and no-go discipline without implying launch readiness or investment certainty.
Current preparation
- BP v0.1 says CosmosExplore can become a gatework / evidence venture, not a rocket maker.
- Public claims matrix exists.
- This blueprint can become a sponsor-safe progress surface after review.
Missing evidence
- Sponsor boundary note.
- Investor / sponsor deck claims review.
- Private budget and responsibility memo.
- Qualified reviewer feedback before any fundraising claim is strengthened.
Next safe action: Create a public-safe video / sponsor claims checklist that says what can be shown and what stays private.
停止條件: Stop if sponsor copy claims authorization, safety, launch date, test readiness, or orbital success before evidence exists.
Nodes
來源
11 · First qualified trial decision
Decide whether a first qualified trial path exists: receive-only practice, balloon test, supervised club test, hosted payload, partner payload, or precise no-go.
Current preparation
- Public blueprint exists after this batch.
- Review #1 public packet and gate evidence map exist.
- No trial path is approved.
Missing evidence
- Private ledger complete enough for review.
- Authority memo and qualified review.
- Site / partner / integrator / disposal / evidence responsibilities closed.
- Public claims review before any announcement.
Next safe action: After private evidence is filled, run a gate review that can choose one of: continue, balloon-only, supervised rocketry-only, hosted-payload review, partner review, or no-go.
停止條件: Stop and record no-go if any earlier gate remains unresolved or if the only available path depends on unsafe or unauthorized shortcuts.
Nodes
來源
Allowed next actions
Go
- Use the blueprint to update the private mission ledger.
- Run receive-only and non-radiating evidence practice.
- Study balloon, rocketry, and hosted-payload paths as separate regulated categories.
- Collect sponsor-facing evidence only after public-claims review.
Blocked actions
No-go
- No public RF configuration, frequency, power, antenna, modulation, command, or uplink detail.
- No propellant, motor, ignition, launch, recovery, or range operation instructions.
- No named private site, sponsor, reviewer, provider quote, or partner term in public git.
- No claim that a cheap communicator, open-source kit, balloon, or club rocket path proves orbital readiness.
來源