Packet identity

Packet ID
opportunities:opp-flight
Packet SHA-256 identity
0fc4d82922644f58b260dec20cf05e73af307a19c60aad5b7bedfa6d6ab70ad1
Corpus SHA-256 identity
8fa944604ca189f5a9216ca59f640ad2ca20972ad512f2f4970764716782e18d
Release ID
public-alpha-2026-07-26-research-visuals-r14
Source commit
3eb036fce3d711336c8c605625895e8a2e799ab0
Frozen corpus date
2026-07-25
Primary records
1
Reference sources
1

Questions and exclusions

Required questions

  1. Required question 1 (exact ID: question-1)
    Does the official source support the opportunity identity, status, timing, eligibility, and access constraints?
  2. Required question 2 (exact ID: question-2)
    Is the proposed fit specific and proportionate without implying availability, invitation, selection, or funding?
  3. Required question 3 (exact ID: question-3)
    What deadline, rule, jurisdiction, cost, conflict, or accessibility fact would change the proposed next action?

Explicit exclusions

  • Review does not submit, register, apply, contact, commit, purchase, or establish eligibility.
  • Provider prestige and apparent fit cannot replace current official terms.

Requested controlled scopes: ecosystem-due-diligence, opportunity-eligibility-access

Frozen-evidence decision window: 30 days from the packet freeze. Not applicable to this packet family.

Complete primary record set

Every record below has one primary packet owner. Decisions must bind to the exact record and packet fingerprints; a changed lesson body, evidence grade, citation, locator, source snapshot, requirement, policy, release, or commit expires the old packet.

  1. opportunity · opp-flight

    NASA Flight Opportunities

    Record fingerprint
    85c625a85f075c90c17a6f87492a4047195339874d3c565eb872688503ebfbf1
    Minimum approvals
    1
    Required scope groups
    bounded-competence: ecosystem-due-diligence, opportunity-eligibility-access
    High-consequence domains
    None under the named two-person rule
    Review state
    pending
    Published human decisions
    0
    Inspect the complete frozen review surface
    ID
    opp-flight
    Name
    NASA Flight Opportunities
    Provider
    NASA
    Kind
    Flight testing
    Timing
    Recurring, call- and challenge-based access. The Robotically Manipulated Payload Challenge is currently open, with registration due July 29 and applications due August 12, 2026; other routes depend on specific solicitations or NASA collaborations.
    Fit
    Parabolic, suborbital, and hosted technology tests
    Status
    active program; current challenge deadline imminent
    Verified At
    2026-07-26
    Eligibility
    NASA describes the current TechLeap challenge as open to qualified commercial businesses, academic institutions, entrepreneurs, and other innovators; the exact challenge rules control eligibility, team, intellectual-property, export, safety, registration, and submission requirements. Other Flight Opportunities routes set their own requirements.
    Access Notes
    The current challenge seeks a real payload that can interact with, be manipulated by, or be reconfigured by a robotic arm in low Earth orbit. NASA says up to three winners may receive up to $500,000 each to develop flight-ready payloads plus an orbital demonstration opportunity. The umbrella program also supports suborbital and hosted-orbital tests through commercial providers; none of these paths is a generic funding entitlement.
    Founder Action
    Review the public TechLeap rules and recorded webinars, but default to no-go unless a genuinely flight-relevant modular payload, capable team, completed ground evidence, development plan, civil-and-defensive review, and separate registration and submission authorization already exist. For other routes, wait for a bounded payload with a flight-specific measurement need.
    Evidence Boundary
    Official NASA Flight Opportunities and TechLeap pages support the current challenge identity, robotic-manipulation scope, July 29 registration and August 12 application dates, broad applicant classes, award ceiling, possible winner count, development purpose, and orbital demonstration opportunity. They do not establish exact rule compliance, eligibility of any team or payload, award, flight, schedule, safety, funding, or relationship.
    Relationship
    indexed only; no formal relationship
    Action Status
    proposed; not undertaken
    Conflicts
    Flight visibility can incentivize premature demonstrations; safety, export control, provider terms, scientific necessity, and opportunity cost require independent review.
    What Would Change
    A challenge amendment or closure, a qualified payload, completed ground validation, exact rules review, and a defensible need for the robotic-orbital environment would change fit.
    Current Until
    2026-08-02
Equivalent record table for this packet
RecordSubjectFingerprintApprovalsScope groups
opportunity:opp-flight NASA Flight Opportunities 85c625a85f075c90c17a6f87492a4047195339874d3c565eb872688503ebfbf1 1 bounded-competence: ecosystem-due-diligence, opportunity-eligibility-access

Linked records—not review targets here

These records provide dependency or relationship context. Their decisions belong to their single primary packet, preventing double counting.

Frozen source snapshots

Source inclusion does not determine the disposition. Reviewers must inspect the cited locator and relation, note inaccessible material, and identify stronger or conflicting evidence.

Sources, verification dates, scope notes, and exact fingerprints
Source IDSourceCheckedScope boundaryFingerprint
official-opportunity-opp-flight NASA Flight Opportunities (opens external site in a new tab) 2026-07-26 Official NASA Flight Opportunities and TechLeap pages support the current challenge identity, robotic-manipulation scope, July 29 registration and August 12 application dates, broad applicant classes, award ceiling, possible winner count, development purpose, and orbital demonstration opportunity. They do not establish exact rule compliance, eligibility of any team or payload, award, flight, schedule, safety, funding, or relationship. 523755d206ef84c48a10cbeec07032016cf9b8c3f2f069824fdcef6124d42a74

Offline packet and worksheet

Downloads contain no reviewer contact details. Downloading does not create an account or store a review response in the GShips application. Ordinary provider request or analytics logs may record the download request. Work locally: the public site has no review account, upload endpoint, or decision-submission API.

Frozen packet · JSON

14.7 KB · packet identity 0fc4d82922644f58…

Download packet

Blank decision worksheet · JSON

3.0 KB · template identity c55bab2c03af2c39…

Download blank JSON

Review-notes worksheet · Markdown

Readable notes companion only—not a decision-bundle equivalent. Use the closed JSON template for structural validation.

Download notes worksheet

Do not paste a completed decision, identity documents, private contact data, confidential conflict evidence, medical information, controlled material, or exploit details into a public form. Until a separately authorized private handoff exists, retain the completed worksheet locally.

Packet schema · JSON · Decision-bundle schema · JSON

Validate offline

Use Node.js 22.13.0 or later. Keep the packet, worksheet, completed decision, and all six kit files together in a local directory.

  1. Download the six kit files below. Complete a copy of the JSON template offline and preserve its templateFingerprint.
  2. Finalize a separate output file.
    node finalize-review-decision.mjs \
      --input DRAFT.json \
      --output COMPLETED.json

    This marks the copy complete and calculates an unkeyed canonical bundle fingerprint. A fingerprint detects changes; it is not a reviewer signature.

  3. Validate the packet and completed copy.
    node check-review-decisions.mjs \
      --packet PACKET.json \
      --decision COMPLETED.json

    Add another --decision for each independent reviewer.

  4. Interpret the result narrowly. A zero exit proves structural consistency only. Neither command appoints or qualifies a reviewer, establishes independence, accepts a decision, or authorizes publication.

Completion criteria

Every primary record must receive the required number of valid, current-fingerprint approvals; every complementary scope group and required domain must be covered; any unresolved revise, contest, or reject disposition blocks publication.

Named medical, reproductive, nuclear, radiation, cybersecurity, governance, and dual-use conclusions require two distinct qualified independent humans covering complementary domain-method and rights/public-interest scopes.

  • Reviewer identity, qualification, independence, conflicts, and compensation must be assessed by accountable human governance; local validation can only report structural validity.
  • Approve, revise, contest, reject, and recuse remain visible. A negative finding cannot be hidden by an aggregate approval percentage.
  • Revision creates a new record and packet fingerprint. Prior approvals do not carry forward automatically.
  • AI may assist with clerical comparison but cannot count as an independent reviewer, identity attestor, appeal authority, or second person.

Prepared review packet · 0 published human decisions · Independent review pending · Suggest a correction

Accountability record

How to inspect this page

Scope: Prepared review packet opportunities:opp-flight · 0fc4d82922644f58b260dec20cf05e73af307a19c60aad5b7bedfa6d6ab70ad1

Page citations and accountability links

  • Exact frozen packet
    Complete packet payload; SHA-256 0fc4d82922644f58b260dec20cf05e73af307a19c60aad5b7bedfa6d6ab70ad1 · fingerprint-bound review artifact
  • Blank closed decision template
    Offline structured-decision starting point · unsubmitted local artifact
  • Review-notes worksheet
    Human-readable notes companion; not validator input · offline notes aid
  • Review corpus index
    Corpus SHA-256 8fa944604ca189f5a9216ca59f640ad2ca20972ad512f2f4970764716782e18d · release and ownership index

Assumptions and limits

  • The exact packet, record, source, policy, release, and source-commit fingerprints bound this prepared page; human review has not started.
  • Downloading, local structural validation, or completing notes does not appoint or qualify a reviewer, establish independence, accept a decision, authorize publication, or create a relationship.

What would change this page?

Staffed governance, appointed qualified reviewers, completed record-level decisions, published conflicts, minority findings, corrections, or changed review policy would change this page.

People, review, and conflicts

Prepared by
GShips Project
Editorial status
public-alpha accountability pass
Editorial reviewer
GShips Project AI-assisted editorial synthesis
Last editorial review
2026-07-26
Independent review
pending
Independent reviewer
No independent reviewer assigned
Last independent review
No independent-review date exists
Last content edit
2026-07-25

Declared conflicts

  • The maintainer intends to explore a commercial venture based on some GShips work. No entity, outside funding, customer, sponsor, or indexed-organization relationship currently exists.

Suggest a correction to this page