Interstellar Lab

Packet identity

Packet ID

organizations:entity-interstellar-lab

Packet SHA-256 identity

d610d6513217c2145c60de7e0062a0966c7588deea28d0a3924c79c4715d198f

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-interstellar-lab

   Interstellar Lab

   Record fingerprint

   25500267f5d5555bc642645f38a732df8376537043343363168eeb9d284a770a

   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-interstellar-lab

   Legacy ID

   org-company--037

   Slug

   interstellar-lab

   Name

   Interstellar Lab

   URL

   https://interstellarlab.com/↗ (opens external site in a new tab)

   Category

   Company and applied technology

   Geography

   France / United States

   Relevance

   enabling

   Engagement

   Proposed, not undertaken: prepare measurable crop, resource, maintenance, and data-interface requirements and, if procurement is authorized, ask through a normal company channel whether a paid nonexclusive test or data study is available.

   Capability

   Controlled-environment cultivation hardware, plant science, automation software, environmental sensing and control, water recirculation, modular growing systems, and planned spaceflight payloads.

   Entity Kind

   commercial controlled-environment biotechnology company

   Link Checked At

   2026-07-25

   Relationship

   indexed only; no formal relationship

   Engagement Status

   proposed; not undertaken

   Profile Summary

   Interstellar Lab is a French-American company developing AI-controlled BioPods and related plant-cultivation systems for terrestrial and space applications. Its official materials describe controlled atmosphere, irrigation, nutrient, lighting, water-recycling, plant-research, and planned orbital or lunar payload work.

   Potential Fit

   A bounded precursor fit could be testing plant-growth recipes, sensor histories, maintenance burdens, crop diversity, water recovery, and failure recovery in a sealed Earthside module. This does not establish a complete or multidecade bioregenerative life-support capability.

   Risks

   1. Performance and schedule statements on the company site are self-reported and planned missions are not equivalent to completed demonstrations.
   2. Commercial access, pricing, intellectual property, export, data rights, and support duration are unknown.
   3. AI-controlled cultivation increases cyber, model-drift, sensor-fault, and offline-operability requirements.
   4. Plant production alone does not close food, nutrient, waste, atmosphere, or ecological loops.

   Evidence Boundary

   Official pages support the existence and claimed scope of BioPod, NuCLEUS, terrestrial cultivation, and planned space work; they do not independently validate yield, reliability, closure, flight schedule, or generation-ship suitability.

   Conflicts

   1. GShips could become a customer, research counterparty, or adjacent commercial participant if a habitat testbed is pursued.

   What Would Change

   Auditable test data, completed representative flight results, disclosed resource and maintenance balances, independent replication, and an authorized commercial scope response would materially change readiness and 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