NASA Space Apps Challenge

Packet identity

Packet ID

events:series-nasa-space-apps-challenge

Packet SHA-256 identity

f2b53263759cb4dfeea5abe4b0da4d0e132916ac08f807db481fb000bec97a52

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

2

Reference sources

1

Questions and exclusions

Required questions

1. Required question 1 (exact ID: question-1)
   Do the official sources support the series identity and every current occurrence, date, deadline, access rule, and eligibility statement?
2. Required question 2 (exact ID: question-2)
   Are location, remote access, accommodations, cost, travel, visa, and participation uncertainty represented without invention?
3. Required question 3 (exact ID: question-3)
   Does the founder action remain proposed and separately authorized rather than implied as registration or attendance?

Explicit exclusions

• A listed event is not endorsed, sponsored, attended, booked, or affiliated with GShips.
• A current occurrence can expire; historical packet approval cannot establish a future event date.

Requested controlled scopes: accessibility-disability-justice, event-access-freshness

Frozen-evidence decision window: 14 days from the packet freeze. A current-occurrence approval must be decided no later than the frozen occurrence end date; a later review requires a refreshed record and packet.

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. event-series · series-nasa-space-apps-challenge

   NASA Space Apps Challenge

   Record fingerprint

   5a22affff184d279475f88328fcf959cbfb21c1451b8115b17e82f1342bc123b

   Minimum approvals

   1

   Required scope groups

   bounded-competence: event-access-freshness

   High-consequence domains

   None under the named two-person rule

   Review state

   pending

   Published human decisions

   0

   Inspect the complete frozen review surface

   ID

   series-nasa-space-apps-challenge

   Slug

   nasa-space-apps-challenge

   Name

   NASA Space Apps Challenge

   Occurrence IDs

   1. event-nasa-space-apps-challenge-2026

   Organizer Organization IDs

   None recorded

   Relationship

   indexed only; no formal relationship

2. event-occurrence · event-nasa-space-apps-challenge-2026

   NASA Space Apps Challenge 2026

   Record fingerprint

   78227cf566cb9d1da57158cef20daced4e598546787304e0fb65992ce3507eed

   Minimum approvals

   1

   Required scope groups

   bounded-competence: accessibility-disability-justice, event-access-freshness

   High-consequence domains

   None under the named two-person rule

   Review state

   pending

   Published human decisions

   0

   Inspect the complete frozen review surface

   ID

   event-nasa-space-apps-challenge-2026

   Slug

   nasa-space-apps-challenge-2026

   Name

   NASA Space Apps Challenge 2026

   URL

   https://www.spaceappschallenge.org/about/↗ (opens external site in a new tab)

   Start Date

   2026-11-14

   End Date

   2026-11-15

   Location

   Global; local and virtual events

   Focus

   Open-data prototyping, public participation, interdisciplinary teams, and science communication

   Founder Action

   Monitor publication of local-event, challenge, and participant details; evaluate one bounded Earth-first prototype as a participant route. The 2026 Local Lead application is active, but evaluate it only after city availability, team, venue, no-fee budget, accessibility, safeguarding, insurance, sponsor, media, privacy, intellectual-property, export/sanctions, branding, and legal review. Do not register, apply to host, recruit, fundraise, or imply NASA affiliation without separate authorization.

   Access Notes

   The official event page confirms a two-day global hackathon on November 14–15, 2026 through local in-person and virtual events using open NASA and partner-agency data. The active Local Lead page says one adult Local Lead is approved per location and is responsible for logistics, a local team, participant recruitment, fundraising, collaborators, speakers, judges, branding, monthly training, and local judging. Local events must be free to participants. The terms include publicity and likeness consent, branding restrictions, local-law and risk obligations, a prohibition on implying NASA authorization or representation, and a China-affiliation restriction. Local availability, participant registration, challenges, accessibility, capacity, judging, data, intellectual property, safeguarding, insurance, and location-specific rules still require review.

   Eligibility

   The organizer describes broad participant access across skills and backgrounds subject to registration and the official participant and local-event rules. A Local Lead must be at least 18, is individually reviewed, and only one is approved per location; the role carries material operational and legal responsibilities and is not NASA employment or representation. No participant registration, Local Lead application, hosting commitment, recruitment, sponsorship, award, or NASA relationship has been undertaken.

   Action Status

   proposed; not undertaken

   Status

   monitor

   Verified At

   2026-07-26

   Conflicts

   Publisher intends to explore a commercial venture based on some GShips work; no event registration, host application, submission, sponsorship, award, attendance commitment, or organizer relationship exists.

   Evidence Boundary

   The official NASA Space Apps event, Local Lead, and 2026 terms pages support the dates, global local-and-virtual format, use of open data, active Local Lead form, adult and one-lead-per-location rules, role responsibilities, free-participation requirement, publicity and branding terms, non-affiliation boundary, and stated China-affiliation restriction. They do not establish a particular location's availability, application approval, challenge fit, participant registration availability, admission, accessibility, capacity, judging outcome, intellectual-property consequence, award, insurance sufficiency, legal compliance, or affiliation.

   What Would Change

   Publication of the 2026 locations, challenges, registration, participant guide, application close, host decision, revised terms, accessibility information, or a date or format revision would change this profile.

Linked records—not review targets here

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

• commons-standards-workforce · event-nasa-space-apps-challenge-2026 event-task-match:event-match-commons-space-apps-2026 · 3bf779a18f7ca6fa034e48c04e193f7f561957b571455e871b24efe957a441f7

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.

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.

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.

• Bundle finalizer
• Validator command
• Decision policy module
• Fingerprint and packet-integrity module
• Review-domain policy module
• Canonical synthesis and interactive review specs