MIT AeroAstro

Packet identity

Packet ID

organizations:entity-mit-aeroastro

Packet SHA-256 identity

d81d8ec6f82d95d9428814e71608f771bf8d34d67d8c065faac33939bc391e94

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-mit-aeroastro

   MIT AeroAstro

   Record fingerprint

   e7c24daee522058d7131011f2cac1ce99b8ec5931bec35e9099fa6ff2d457863

   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-mit-aeroastro

   Legacy ID

   org-universi-023

   Slug

   mit-aeroastro

   Name

   MIT AeroAstro

   URL

   https://aeroastro.mit.edu/↗ (opens external site in a new tab)

   Category

   University and national laboratory

   Geography

   Massachusetts, United States

   Relevance

   enabling

   Engagement

   Proposed, not undertaken: identify a named laboratory only after matching a public research programme to one falsifiable work package; any sponsored research, capstone, data exchange, or review requires the appropriate MIT process and separate authorization.

   Capability

   Aerospace education and research, space-system architecture, autonomy and controls, human factors, propulsion, communications, computation, and experimental engineering.

   Entity Kind

   university academic department

   Link Checked At

   2026-07-25

   Relationship

   indexed only; no formal relationship

   Engagement Status

   proposed; not undertaken

   Profile Summary

   MIT's Department of Aeronautics and Astronautics conducts education and research across aerospace systems, autonomy, controls, propulsion, communications, human systems, space architecture, computation, and related engineering fields.

   Potential Fit

   Individual laboratories or student teams could be relevant to a tightly bounded architecture, autonomy, human-systems, controls, or assurance question. Department breadth is not a single capability, and no investigator availability or institutional commitment is implied.

   Risks

   1. Research interests, principal-investigator capacity, student timelines, funding, and sponsored-research terms vary.
   2. Prototype and publication results may be low-readiness or optimized for different missions.
   3. Intellectual property, publication, export, human-subject, and conflict rules may constrain a project.

   Evidence Boundary

   The official department site supports broad education and research capability; it does not establish a department-wide generation-ship programme, availability of a specific lab, endorsement, or engineering validation.

   Conflicts

   1. GShips could sponsor research, recruit talent, license work, or gain credibility from MIT association.

   What Would Change

   A named investigator's authorized interest, executed sponsored-research scope, completed student project, or independently reviewed representative experiment would make the fit specific.

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