NASA Space Apps 2026 Local Lead

Packet identity

Packet ID

opportunities:opp-nasa-space-apps-local-lead-2026

Packet SHA-256 identity

ebf8b9464629dbb0402cd08013cbe894661db0eefb8baddb4622cf0c71a79ebc

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-nasa-space-apps-local-lead-2026

   NASA Space Apps 2026 Local Lead

   Record fingerprint

   54fa85f753cd0ff75522e5af08caf90df002a0802f651daad5dc475fb84462c9

   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-nasa-space-apps-local-lead-2026

   Name

   NASA Space Apps 2026 Local Lead

   URL

   https://www.spaceappschallenge.org/host-an-event/↗ (opens external site in a new tab)

   Provider

   NASA Space Apps Challenge

   Kind

   Community event leadership

   Timing

   The official 2026 Local Lead form is active for the November 14–15 NASA Space Apps Challenge. The reviewed page does not state an application deadline.

   Fit

   Public-benefit institution building, accessible community prototyping, and science communication

   Status

   active application; deadline not stated

   Verified At

   2026-07-26

   Current Until

   2026-08-02

   Eligibility

   Applicants must be at least 18. NASA Space Apps reviews individuals and approves only one Local Lead per location. Approved leads attend virtual monthly trainings and organize the local team, venue and supplies, participant recruitment, fundraising, collaborators, speakers, judges, branding, participant support, and local judging.

   Access Notes

   Local events must be free to participants. The official terms include publicity and likeness consent, model-release duties for submitted imagery, branding and logo restrictions, local-law and contest responsibility, risk and indemnity language, a prohibition on implying NASA authorization, employment, sponsorship, or representation, and a stated China-affiliation restriction. Venue, safeguarding, insurance, accessibility, privacy, intellectual property, sponsorship, taxes, export/sanctions, and local capacity need independent review.

   Founder Action

   First produce a no-application host-readiness memo covering the intended city, location availability, organizing team, no-fee budget, venue, accessibility, safeguarding, insurance, emergency plan, judges, collaborators, media and likeness consent, privacy, intellectual property, branding, export/sanctions, legal duties, and a truthful non-affiliation statement. Seek separate authorization before applying, recruiting, fundraising, contacting collaborators, or using protected branding.

   Evidence Boundary

   The official 2026 Local Lead page and terms support the active application route, adult and one-lead-per-location rules, training and operating responsibilities, free-participation rule, publicity and branding provisions, non-affiliation boundary, and stated China-affiliation restriction. They do not establish location availability, approval, sufficient capacity, legal or insurance compliance, accessibility, sponsor support, participant safety, application deadline, or any NASA relationship.

   Relationship

   indexed only; no formal relationship

   Action Status

   proposed; not undertaken

   Conflicts

   Founder visibility, NASA name proximity, sponsor recruitment, event funds, participant safety, judging power, media rights, branding, privacy, intellectual property, export and sanctions, and community representation require independent review.

   What Would Change

   An application deadline, location decision, changed terms, a complete host-readiness memo, approved budget and team, independent legal and accessibility review, or an organizer approval or denial would change this assessment.

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 · opp-nasa-space-apps-local-lead-2026 opportunity-task-match:opportunity-match-commons-space-apps-local-lead-2026 · 2c0230a1adb26d2bc14cccfaac5fc56daf4391a8927f066ce5e7a8365d665db9

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