University of Michigan PEPL

Packet identity

Packet ID

organizations:entity-university-of-michigan-pepl

Packet SHA-256 identity

7e73d63f48ad03afe0f7d2db7306ee42dee692a8069618e6b1a0c550a1c52b73

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-university-of-michigan-pepl

   University of Michigan PEPL

   Record fingerprint

   6fec339500d43aa1fe161a9a85b44dc0b5eaebfe66deee54c7106f27e26b5c7d

   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-university-of-michigan-pepl

   Legacy ID

   org-universi-028

   Slug

   university-of-michigan-pepl

   Name

   University of Michigan PEPL

   URL

   https://pepl.engin.umich.edu/↗ (opens external site in a new tab)

   Category

   University and national laboratory

   Geography

   Michigan, United States

   Relevance

   enabling

   Engagement

   Proposed only, subject to a future fit check and university laboratory rules: use peer-reviewed results first, then consider a bounded technical review or sponsored test around a named thruster or lifetime question. No outreach, facility access, commitment, or funding has occurred.

   Capability

   Electric and plasma propulsion research, Hall thrusters, vacuum testing, plasma diagnostics, lifetime and erosion studies, and propulsion education.

   Entity Kind

   university electric-propulsion research laboratory

   Link Checked At

   2026-07-25

   Relationship

   indexed only; no formal relationship

   Engagement Status

   proposed; not undertaken

   Profile Summary

   The University of Michigan's Plasmadynamics and Electric Propulsion Laboratory researches Hall thrusters, ion and plasma propulsion, diagnostics, plasma-material interactions, and high-power electric-propulsion systems using vacuum facilities and university collaborations.

   Potential Fit

   Could inform high-specific-impulse propulsion, lifetime limits, erosion, plume interactions, diagnostics, power coupling, and realistic scaling for robotic and Solar System precursor missions.

   Risks

   1. Electric propulsion is constrained by power generation, heat rejection, propellant, erosion, and thrust; it does not establish worldship feasibility.
   2. Laboratory vacuum chambers cannot fully reproduce long-duration space plasma, contamination, or full spacecraft interactions.
   3. Defense funding, export controls, facility schedules, and proprietary thruster data may constrain access.

   Evidence Boundary

   Official-link review: the source site returned an automated-access barrier to the checker; official university-domain indexed material supports the laboratory and electric-propulsion scope. Current facilities, researchers, access, data, and any fit with GShips were not independently verified; independent review pending.

   Conflicts

   Conflicts were not assessed beyond publisher disclosure in this official-link review; government sponsors, manufacturers, patents, facility users, and researcher interests were not independently investigated.

   What Would Change

   Current peer-reviewed lifetime data, independent replication, full power and thermal accounting, a named civil test need, and an accessible unclassified facility route would refine fit.

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