Lunar Resources

Packet identity

Packet ID

organizations:entity-lunar-resources

Packet SHA-256 identity

83e9696cad09b152188f48373c67d92c09052bff573b2cd44835849832516105

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-lunar-resources

   Lunar Resources

   Record fingerprint

   f41a7f1951266d8062bd1a3b0dd9025b4460d2cab14edc01e9ee4ebcdb4d031d

   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-lunar-resources

   Legacy ID

   org-company--026

   Slug

   lunar-resources

   Name

   Lunar Resources

   URL

   https://www.lunarresources.space/↗ (opens external site in a new tab)

   Category

   Company and applied technology

   Geography

   Texas, United States

   Relevance

   enabling

   Engagement

   Proposed, not undertaken: define a simulant, mass-balance, energy, purity, maintenance, and by-product test matrix and, if authorized, ask whether a paid independent-data work package is commercially available.

   Capability

   Pulsed-power systems, regolith and ore processing, oxygen and metal extraction, refining, welding, material production, and proposed off-Earth industrial integration.

   Entity Kind

   commercial space industrial technology company

   Link Checked At

   2026-07-25

   Relationship

   indexed only; no formal relationship

   Engagement Status

   proposed; not undertaken

   Profile Summary

   Lunar Resources is a commercial industrial-technology company developing pulsed-power, electrochemical, metallurgical, welding, and manufacturing processes. Its official site describes extraction of oxygen and several metals from regolith simulants or ores and proposed off-Earth material production.

   Potential Fit

   A bounded precursor project could test reagent-free extraction, energy and consumable balances, product purity, maintenance, slag and waste handling, and downstream manufacturing using characterized simulants. It would not establish lunar industrial scale or closed-loop shipboard manufacturing.

   Risks

   1. Company performance and maturity statements are self-reported and may not expose negative results or full process balances.
   2. Commercial terms, intellectual property, export controls, data rights, and system availability are unknown.
   3. Representative regolith composition, vacuum, dust, thermal cycles, gravity, scale, and feed variability may alter performance.
   4. Pulsed-power and resource-processing systems can have defense or other dual-use applications.

   Evidence Boundary

   The official site supports the company's stated processes and ambitions; it does not independently validate lunar deployment, industrial throughput, full resource closure, economics, or readiness for a generation ship.

   Conflicts

   1. GShips could become a customer, test collaborator, investor-facing comparator, or adjacent commercial participant.

   What Would Change

   Third-party replicated test data, disclosed process balances, representative-environment operation, completed deployment, and an authorized scope response would materially change fit and readiness.

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