AstroAccess

Packet identity

Packet ID

organizations:entity-astroaccess

Packet SHA-256 identity

779b013d5392fe83f9b27d1fc6abe1e5912a5db595e97ab0e9d0ca895a466bdd

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 establish the entity, current program, and bounded capability described?
2. Required question 2 (exact ID: question-2)
   Are potential fit, risks, access, geography, and engagement boundaries current and proportionate?
3. Required question 3 (exact ID: question-3)
   Could any wording imply partnership, endorsement, availability, procurement, authority, or affiliation that does not exist?

Explicit exclusions

• Indexing is not endorsement, due diligence completion, outreach, procurement, or a relationship.
• No aggregate organization score or sponsor-purchased ranking is permitted.

Requested controlled scopes: ecosystem-due-diligence, information-science

Frozen-evidence decision window: 90 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. ecosystem-organization · entity-astroaccess

   AstroAccess

   Record fingerprint

   49a0864f99b1e75c6d90eb9ac404129c385f857c2d29dc669fafe5397d7d6b37

   Minimum approvals

   1

   Required scope groups

   bounded-competence: ecosystem-due-diligence

   High-consequence domains

   None under the named two-person rule

   Review state

   pending

   Published human decisions

   0

   Inspect the complete frozen review surface

   ID

   entity-astroaccess

   Legacy ID

   org-universi-035

   Slug

   astroaccess

   Name

   AstroAccess

   URL

   https://astroaccess.org/↗ (opens external site in a new tab)

   Category

   University and national laboratory

   Geography

   United States / international

   Relevance

   enabling

   Engagement

   Proposed only, subject to a future fit check and then-current access rules: consider compensating disabled experts for a bounded requirements critique or accessible-design workshop only through a mutually agreed process and without treating participants as symbolic validation. No outreach, eligibility determination, commitment, or procurement has occurred.

   Capability

   Disability-led microgravity demonstrations, universal design, accessible communications, emergency procedures, and inclusive spaceflight advocacy.

   Entity Kind

   nonprofit disability-led space-access program

   Link Checked At

   2026-07-25

   Relationship

   indexed only; no formal relationship

   Engagement Status

   proposed; not undertaken

   Profile Summary

   AstroAccess is a SciAccess nonprofit program that conducts parabolic-flight demonstrations with disabled participants and advocates universal design, accessible safety procedures, and disability inclusion in space vehicles and habitats.

   Potential Fit

   Could help GShips test whether habitat requirements, alarms, emergency procedures, tools, and leadership models are accessible by design, provided disabled experts retain meaningful decision authority.

   Risks

   1. Parabolic demonstrations are short-duration analogs and do not validate long-duration habitat performance.
   2. Extractive consultation or tokenism would be a material governance and ethics failure.
   3. Flight participation, research capacity, accessibility needs, and organizational availability cannot be assumed.

   Evidence Boundary

   Official-link review: the official site and about pages were reachable and describe SciAccess nonprofit governance, disability-led missions, test questions, and advocacy; they do not independently validate design effectiveness. Public descriptions, performance, maturity, access, procurement, and current availability were not independently verified; independent review pending.

   Conflicts

   Conflicts were not assessed beyond publisher disclosure in this official-link review; financial, contracting, leadership, and institutional conflicts were not independently investigated.

   What Would Change

   Published protocols, accessible datasets, participant-led findings, long-duration follow-up, and a mutually defined review mechanism would strengthen fit.

Linked records—not review targets here

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

• accessible-human-habitat · entity-astroaccess partner-task-match:match-accessible-human-habitat-astroaccess · a797462366fce86eb9678866e5c148c1f12f881284cc44de0ac16dc33b8c59df

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