CosmosExplore 環宇探索

Review kit

Sprint 001 review kit

A public-safe review kit for Sprint 001: reviewer categories, receive-only evidence packet components, and hosted-payload category filters for the North Star verified-message mission.

確認日: 2026-06-11次回確認期限: 2026-09-10started

既定の境界: This kit organizes review questions and evidence categories. It is not legal advice, RF guidance, station setup, launch booking, partner outreach, or mission authorization.

North Star

Current decision

One compliant, authenticated, logged, verifiable message from LEO, with authority, integration, disposal, and post-mission records attached.

First go/no-go: Go for reviewer-category mapping, receive-only evidence packet definition, and hosted-payload category screening; no-go for named outreach, legal conclusions, operational RF details, hardware readiness, launch booking, or integration commitment.

Review kit

2026-06-18

既定の境界: This kit organizes review questions and evidence categories. It is not legal advice, RF guidance, station setup, launch booking, partner outreach, or mission authorization.

Reviewer categories

Reviewer categories

FocusPurposeReview questionsExpected outputStop triggerNodes
scope-steward
Scope steward
Keep the mission personal, non-commercial, message-only, and evidence-first before any authority route is interpreted.
  • Does the current mission statement still avoid commercial service, public connectivity, remote sensing, and launch-service claims?
  • Does every public claim map to evidence, no-go status, or a source-backed gate?
  • Has the not-goal list been reviewed beside the authority matrix?
A current not-goal list and a public-claims boundary note.Any service, remote-sensing, launch-service, or hardware-build claim enters the mission wording.
qualified-regulatory-counsel
Qualified regulatory counsel
Distinguish amateur-satellite, experimental, Part 25-style, payload-review, remote-sensing, and debris/disposal questions without treating public source reading as legal advice.
  • Which communications authority path is a candidate, and which paths are ruled out?
  • What filing, responsibility, stop-transmission, and evidence questions must be answered before any commitment?
  • Does a remote-sensing negative check remain valid for the current payload definition?
A written path-mapping memo with open questions and no-go triggers.A candidate path is treated as selected before qualified review.
amateur-satellite-mentor
Amateur-satellite mentor or coordinator
Test whether the mission can remain compatible with amateur-satellite purpose, operator responsibility, coordination expectations, and non-commercial boundaries.
  • Can the verified-message goal fit amateur-satellite purpose without becoming a service?
  • What operator-responsibility and coordination questions must be answered before any technical planning?
  • What would make the amateur path inappropriate?
A suitability note that either preserves the amateur path as candidate or explicitly rules it out.The amateur path is used as a shortcut around other duties or for any pecuniary / service purpose.
payload-integrator-reviewer
Payload and integrator reviewer
Translate the verified-message objective into payload boundaries, interface responsibilities, evidence handoff, and hosted-payload feasibility.
  • Can the message objective be hosted without full spacecraft ownership?
  • Which roles own payload definition, integration evidence, operations evidence, and post-mission records?
  • What information is needed before any payload-review or integration conversation is meaningful?
A payload-minimum memo and role / responsibility map.Integration is discussed as commitment before payload minimums, roles, evidence, and authority dependencies are mapped.
disposal-evidence-reviewer
Disposal and evidence reviewer
Keep disposal, debris mitigation, stored-energy questions, and post-mission records attached to the verified-message success criterion.
  • What disposal and post-mission records would be required before any orbit choice is credible?
  • Which debris and stored-energy questions are blockers rather than later paperwork?
  • What evidence would be needed after success or no-go?
A disposal-evidence checklist and stop-condition map.Orbit, integration, or success is discussed without disposal and post-mission evidence context.
public-claims-reviewer
Public-claims reviewer
Ensure public pages never overclaim authorization, safety, commercial readiness, or mission success.
  • Does the public page say only what the evidence packet supports?
  • Are no-go outcomes presented as valid progress rather than failure to hide?
  • Are private details, partner terms, and operational data absent?
A public-claims note before each public North Star update.A received signal, partner discussion, or review step is framed as proof of authorization, safety, or readiness.

Receive-only evidence packet

Receive-only evidence packet

FocusPurposeMinimum fieldsExcluded fieldsNodes
source-provenance
Source and provenance record
Record which public source or public dataset was used and why it is relevant.
  • source title
  • source URL
  • access date
  • what question it supports
  • review expiry
  • private account credentials
  • API keys
  • private logs
object-identity
Object identity context
Preserve public identity context for a space object or reference object without claiming control or authorization.
  • public object identifier or catalog context
  • public element-set source
  • time the identity context was checked
  • uncertainty note
  • tracking instructions
  • station pointing instructions
  • private sensor details
receive-only-boundary
Receive-only boundary note
Make clear that the evidence practice does not transmit, command, or imply mission operation.
  • no-transmit statement
  • no-command statement
  • public-claim boundary
  • responsible reviewer
  • transmit settings
  • uplink procedures
  • command strings
observation-log
Observation log shell
Create a repeatable place to record non-sensitive observation context and whether the evidence was sufficient.
  • date and time
  • public object identity context
  • source used
  • result summary
  • uncertainty or failure note
  • precise station configuration
  • private location
  • receiver settings
  • hardware instructions
data-integrity-record
Data-integrity record
Separate evidence from interpretation by preserving what was observed, what was derived, and what remains uncertain.
  • artifact identifier
  • artifact description
  • derived claim
  • confidence / uncertainty note
  • reviewer
  • credentials
  • private raw captures
  • private partner data
public-claims-link
Public-claims link
Tie each public statement to the evidence packet and prevent unsupported claims.
  • public statement
  • supporting evidence item
  • claim boundary
  • next review date
  • legal conclusions
  • safety conclusions
  • commercial readiness claims

Hosted-payload category shortlist

Hosted-payload category shortlist

education-nonprofit-programEducation or non-profit smallsat programMay already have review discipline, educational scope, and non-commercial framing compatible with the North Star.

Screening questions:

  • Can the program support a message-only payload objective?
  • Can it preserve authority, integration, disposal, and evidence records?
  • Can it avoid commercial service framing?

Advance signal: Program category can support learning mission boundaries and reviewer access.

Stop signal: Program category requires public service claims, opaque evidence ownership, or private terms that cannot be summarized safely.

university-cubesat-collaborationUniversity CubeSat collaboration categoryUniversity CubeSat environments may understand mission review, student learning goals, and documentation discipline.

Screening questions:

  • Would the collaboration keep the payload message-only and non-commercial?
  • Can roles, evidence ownership, and public claims be documented?
  • Can the project avoid turning into a hardware build recipe?

Advance signal: The category supports documented roles and evidence-first learning.

Stop signal: The category requires uncontrolled hardware disclosure or unclear authority ownership.

hosted-payload-integratorHosted-payload or mission integrator categoryThis category may reduce full spacecraft ownership while preserving integration and post-mission evidence responsibilities.

Screening questions:

  • Can the category host a minimal message objective?
  • Can it document authority, payload-review, disposal, and evidence responsibilities before commitment?
  • Can costs be represented as categories rather than launch price only?

Advance signal: The category can map roles, review gates, evidence handoff, and post-mission records.

Stop signal: The category treats rideshare price as total mission cost or hides owner/operator responsibility.

amateur-satellite-education-categoryAmateur-satellite education categoryThis category may be relevant only if the mission remains non-commercial and compatible with amateur-satellite purpose.

Screening questions:

  • Can the category explain non-commercial purpose and operator responsibility?
  • Can it explain coordination expectations without treating them as authorization bypass?
  • Can it rule itself out if mission scope drifts?

Advance signal: The category can identify suitability and stop triggers before any technical planning.

Stop signal: The category encourages use of amateur service for commercial, service, or shortcut purposes.

receive-only-practice-categoryReceive-only evidence practice categoryThis category builds evidence discipline before the project has any authority path or payload commitment.

Screening questions:

  • Can the practice produce source-backed logs without transmitting?
  • Can it preserve object identity, provenance, uncertainty, and public-claim boundaries?
  • Can it avoid station configuration or operational disclosure?

Advance signal: The category strengthens the evidence packet without creating authorization or safety claims.

Stop signal: The practice drifts into transmit planning, station setup instructions, or operational claims.

出典

出典