Space Resources Week

Packet identity

Packet ID

events:series-space-resources-week

Packet SHA-256 identity

c003154c95a57de7c9ca3fda02abd757f0da431a0f25379e1385cfdd19b780a8

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

2

Reference sources

1

Questions and exclusions

Required questions

1. Required question 1 (exact ID: question-1)
   Do the official sources support the series identity and every current occurrence, date, deadline, access rule, and eligibility statement?
2. Required question 2 (exact ID: question-2)
   Are location, remote access, accommodations, cost, travel, visa, and participation uncertainty represented without invention?
3. Required question 3 (exact ID: question-3)
   Does the founder action remain proposed and separately authorized rather than implied as registration or attendance?

Explicit exclusions

• A listed event is not endorsed, sponsored, attended, booked, or affiliated with GShips.
• A current occurrence can expire; historical packet approval cannot establish a future event date.

Requested controlled scopes: accessibility-disability-justice, event-access-freshness

Frozen-evidence decision window: 14 days from the packet freeze. A current-occurrence approval must be decided no later than the frozen occurrence end date; a later review requires a refreshed record and packet.

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. event-series · series-space-resources-week

   Space Resources Week

   Record fingerprint

   b453ab780f4a44732df842c94d4159e379cb67751dd6577932980028029dedc2

   Minimum approvals

   1

   Required scope groups

   bounded-competence: event-access-freshness

   High-consequence domains

   None under the named two-person rule

   Review state

   pending

   Published human decisions

   0

   Inspect the complete frozen review surface

   ID

   series-space-resources-week

   Slug

   space-resources-week

   Name

   Space Resources Week

   Occurrence IDs

   1. event-space-resources-week-2027

   Organizer Organization IDs

   None recorded

   Relationship

   indexed only; no formal relationship

2. event-occurrence · event-space-resources-week-2027

   Space Resources Week 2027

   Record fingerprint

   d42df695449d6c3fa4046d225da9f1bce2cf814d4a628847ff6acc126d656e6d

   Minimum approvals

   1

   Required scope groups

   bounded-competence: accessibility-disability-justice, event-access-freshness

   High-consequence domains

   None under the named two-person rule

   Review state

   pending

   Published human decisions

   0

   Inspect the complete frozen review surface

   ID

   event-space-resources-week-2027

   Slug

   space-resources-week-2027

   Name

   Space Resources Week 2027

   URL

   https://www.spaceresourcesweek.lu/↗ (opens external site in a new tab)

   Start Date

   2027-05-10

   End Date

   2027-05-13

   Location

   Luxembourg

   Focus

   ISRU, mining, circular economy, infrastructure, and regulation

   Founder Action

   Hold the dates and map resource-to-feedstock learning questions; do not seek relationships, submit, register, or travel until the organizer publishes the 2027 program and participation terms.

   Access Notes

   The official homepage, still presenting the completed 2026 edition, gives a save-the-date for the ninth edition from May 10–13, 2027 in Luxembourg. It does not yet publish the 2027 venue, program, submission process, registration, fees, accessibility, capacity, or format.

   Eligibility

   The 2027 attendee and presenter rules are not announced on the reviewed organizer page. No submission, registration, attendance, partnership approach, or organizer relationship has been undertaken.

   Action Status

   proposed; not undertaken

   Status

   monitor

   Verified At

   2026-07-25

   Conflicts

   Publisher intends to explore a commercial venture based on some GShips work; no event registration, submission, sponsorship, attendance commitment, or organizer relationship exists.

   Evidence Boundary

   The organizer's transitional series homepage supports only the May 10–13, 2027 save-the-date and Luxembourg location; it does not establish the 2027 venue, program, quality, GShips fit, registration, eligibility, accessibility, capacity, cost, or participant availability.

   What Would Change

   Publication of the organizer's dedicated 2027 occurrence page, venue, call, program, registration, eligibility, pricing, format, or access details would change this profile.

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