DOE Lab Partnering Service

Packet identity

Packet ID

organizations:entity-doe-lab-partnering-service

Packet SHA-256 identity

f0c5af782626882a65b9a45c671aaab32cd28b4d064a13fbfe41d6c4e23fd0d7

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-doe-lab-partnering-service

   DOE Lab Partnering Service

   Record fingerprint

   20285e60f9721dc2550ec7097088423ee6525ecdc2d4bc7df00fc5e00f907389

   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-doe-lab-partnering-service

   Legacy ID

   org-agency-s-028

   Slug

   doe-lab-partnering-service

   Name

   DOE Lab Partnering Service

   URL

   https://www.energy.gov/technologycommercialization/lab-partnering-service↗ (opens external site in a new tab)

   Category

   Agency, standards, and public research infrastructure

   Geography

   United States

   Relevance

   enabling

   Engagement

   Proposed only, subject to a future fit check and then-current access rules: use the portal to compare named capabilities and agreement types only after preparing a bounded statement of work, budget, IP position, and publication requirements. No outreach, eligibility determination, commitment, or procurement has occurred.

   Capability

   National-lab capability discovery, expert and facility search, licensable technology discovery, and partnership-mechanism guidance.

   Entity Kind

   federal technology-transfer and facility-discovery portal

   Link Checked At

   2026-07-25

   Relationship

   indexed only; no formal relationship

   Engagement Status

   proposed; not undertaken

   Profile Summary

   The DOE Lab Partnering Service is an official portal for finding national-laboratory experts, facilities, patents, and technologies and for understanding mechanisms such as CRADAs, strategic partnership projects, licensing, material transfer, and user agreements.

   Potential Fit

   Could help route specific Earthside energy, materials, computing, manufacturing, or biology work packages to an appropriate laboratory after needs are technically defined.

   Risks

   1. The portal is a discovery service, not a guarantee that a lab will accept or fund work.
   2. Agreement negotiation can require full-cost recovery, background-IP review, indemnity, and long lead times.
   3. DOE mission fit, competition with private industry, export control, and national-security restrictions may apply.

   Evidence Boundary

   Official-link review: the official DOE page was reachable and gives current portal functions, facility and expert counts, and agreement categories. 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 specific matched laboratory, confirmed mission fit, preliminary cost and schedule, and acceptable IP/data terms would change this from general routing to actionable 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