DLR EDEN LUNA

Packet identity

Packet ID

organizations:entity-dlr-eden-luna

Packet SHA-256 identity

bab74e66d564de8f9ee3a837f174c009d475a9870354fb0f31c239498911c40d

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-dlr-eden-luna

   DLR EDEN LUNA

   Record fingerprint

   576256425e3b24daa43ca02db2c5d5da2138b7d5423e92bcc6b247cf32003661

   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-dlr-eden-luna

   Legacy ID

   org-universi-015

   Slug

   dlr-eden-luna

   Name

   DLR EDEN LUNA

   URL

   https://www.dlr.de/en/irs/research-transfer/missions-and-projects/eden-luna↗ (opens external site in a new tab)

   Category

   University and national laboratory

   Geography

   Germany

   Relevance

   enabling

   Engagement

   Proposed only, subject to a future fit check and then-current access rules: follow published results and, if an open research mechanism exists, propose one narrowly defined reliability or data-interoperability study through DLR channels. No outreach, eligibility determination, commitment, or procurement has occurred.

   Capability

   Controlled-environment agriculture, bioregenerative life support, greenhouse robotics, remote operations, microbiome characterization, and analog training.

   Entity Kind

   government research program and analog greenhouse facility

   Link Checked At

   2026-07-25

   Relationship

   indexed only; no formal relationship

   Engagement Status

   proposed; not undertaken

   Profile Summary

   EDEN LUNA is a DLR research program converting the Antarctic-tested EDEN ISS greenhouse for integration with the DLR–ESA LUNA analog facility, focusing on nutrient cycling, energy efficiency, robotics, microbiomes, fault detection, and closed bioregenerative support.

   Potential Fit

   Could provide unusually relevant lessons for crop operations, autonomy, crew workload, urine-derived nutrients, microbial monitoring, and fault recovery in a bounded analog.

   Risks

   1. The official project duration is currently bounded and future extension is not guaranteed.
   2. A lunar analog with periodic external support does not reproduce generation-ship isolation or ecological closure.
   3. Biological performance, food adequacy, contamination, and energy balances require independent full-system review.

   Evidence Boundary

   Official-link review: the official DLR project pages were reachable and give current 2024–2026 scope, facility integration, technical focus, and planned operations. 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 integrated-loop data, anomaly logs, mass and energy balances, confirmed post-2026 operations, and external research rules would change the assessment.

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