UAB MELiSSA Pilot Plant

Packet identity

Packet ID

organizations:entity-uab-melissa-pilot-plant

Packet SHA-256 identity

6bed75c3643fadd788eefb0cdc7968444f3be2d5b44aa2ad90f29039595ef4f1

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-uab-melissa-pilot-plant

   UAB MELiSSA Pilot Plant

   Record fingerprint

   2d06915f186dafa2e5c72d9cf9a373cbd6a027378676d93df31a9853a84e91d9

   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-uab-melissa-pilot-plant

   Legacy ID

   org-universi-014

   Slug

   uab-melissa-pilot-plant

   Name

   UAB MELiSSA Pilot Plant

   URL

   https://webs.uab.cat/melissapilotplant/en/↗ (opens external site in a new tab)

   Category

   University and national laboratory

   Geography

   Barcelona, Spain

   Relevance

   enabling

   Engagement

   Proposed only, subject to a future fit check and then-current UAB and ESA access rules: study public results, then consider a scoped research visit or experiment only around a defined loop-closure or assurance question. No outreach, facility access, commitment, or funding has occurred.

   Capability

   Regenerative life-support integration, bioreactors, plant cultivation, water and waste processing, gas-loop control, microbial ecology, sensors, and pilot-scale operations.

   Entity Kind

   university-operated regenerative life-support pilot plant

   Link Checked At

   2026-07-25

   Relationship

   indexed only; no formal relationship

   Engagement Status

   proposed; not undertaken

   Profile Summary

   The MELiSSA Pilot Plant at Universitat Autònoma de Barcelona is an ESA-linked facility integrating biological and physicochemical processes for regenerative life support. It tests compartments of the MELiSSA loop, including waste conversion, microbial and plant production, gas exchange, water processing, sensors, control, and crew-relevant food-system questions.

   Potential Fit

   Could provide unusually relevant integrated-loop methods, failure data, controls research, and training for closed habitats, while remaining an Earth-supported pilot rather than evidence of centuries-long closure.

   Risks

   1. The pilot plant operates with Earth maintenance, replacement inputs, expert intervention, and limited duration.
   2. Biological loops face contamination, drift, food-safety, stability, and human-health risks at larger scale.
   3. Facility access, intellectual property, ESA program priorities, biosafety, and research capacity constrain participation.

   Evidence Boundary

   Official-link review: the UAB site was reachable and describes the pilot plant, MELiSSA compartments, infrastructure, research, education, and ESA context. Closure performance, anomaly history, current experiment access, and transfer to multigenerational habitation were not independently verified; independent review pending.

   Conflicts

   Conflicts were not assessed beyond publisher disclosure in this official-link review; ESA priorities, university researchers, suppliers, commercial partners, and intellectual-property interests were not independently investigated.

   What Would Change

   Long-duration integrated mass balances, openly published interventions and failures, independent replication, current access terms, and progressively reduced external support would materially strengthen 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