Brookhaven National Laboratory

Packet identity

Packet ID

organizations:entity-brookhaven-national-laboratory

Packet SHA-256 identity

d0da093759e7a36cdf76547cd6145e23bbdcb1842bbbca1681262ad3987339e2

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-brookhaven-national-laboratory

   Brookhaven National Laboratory

   Record fingerprint

   07d7fdf719dea21ae6ce4f2752ef0ec2c27b27b2f5d68cd3c3ab0fc73a2a2a12

   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-brookhaven-national-laboratory

   Legacy ID

   org-universi-045

   Slug

   brookhaven-national-laboratory

   Name

   Brookhaven National Laboratory

   URL

   https://www.bnl.gov/↗ (opens external site in a new tab)

   Category

   University and national laboratory

   Geography

   New York, United States

   Relevance

   enabling

   Engagement

   Proposed only, subject to a future fit check and then-current access rules: identify a specific beamline or user program and assess a proposal only with radiation-health experts, institutional approvals, and a defined open-data plan. No outreach, eligibility determination, commitment, or procurement has occurred.

   Capability

   Accelerator-based space-radiation simulation, radiation biology, materials characterization, isotopes, nanoscience, and scientific computing.

   Entity Kind

   U.S. Department of Energy national laboratory

   Link Checked At

   2026-07-25

   Relationship

   indexed only; no formal relationship

   Engagement Status

   proposed; not undertaken

   Profile Summary

   Brookhaven National Laboratory is a DOE national laboratory operating accelerator and materials facilities, including capabilities for simulated space-radiation biology, radiation damage, isotope production, nanoscience, and computation.

   Potential Fit

   Could support bounded studies of radiation effects on biology, electronics, or structural materials if a qualified research team and an appropriate user-facility mechanism exist.

   Risks

   1. Facility access is competitive, scheduled, and subject to safety, mission, and user-agreement requirements.
   2. Accelerator exposure is an imperfect proxy for the mixed, chronic radiation environment of deep space.
   3. Biological studies may involve high-consequence claims, animal or human-derived materials, and strict ethics requirements.

   Evidence Boundary

   Official-link review: the official Brookhaven site and accelerator pages were reachable and describe the laboratory mission and relevant irradiation capabilities. 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

   A facility scientist confirming an appropriate exposure protocol, accepted proposal terms, and independent validation of environmental equivalence would change the 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