Zeno Power

Packet identity

Packet ID

organizations:entity-zeno-power

Packet SHA-256 identity

e632925e892b0cef82610359542d1694160ba285b3605196390bc40dd6ba10ef

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-zeno-power

   Zeno Power

   Record fingerprint

   4bc509e088af2e6bbb5bbf484c248a0304f8421ba002f13b0600c4be1876c4a5

   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-zeno-power

   Legacy ID

   org-company--045

   Slug

   zeno-power

   Name

   Zeno Power

   URL

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

   Category

   Company and applied technology

   Geography

   Washington, DC, United States

   Relevance

   enabling

   Engagement

   Proposed only, subject to a future fit check and all nuclear, launch, export, safeguards, security, and procurement rules: evaluate only a defined civil precursor need after non-nuclear alternatives and lifecycle risks are compared. No outreach, commitment, procurement, or nuclear activity has occurred.

   Capability

   Radioisotope power-system design, strontium-90 heat-source integration, power conversion, remote-energy applications, nuclear safety work, and government program execution.

   Entity Kind

   private radioisotope power-system company

   Link Checked At

   2026-07-25

   Relationship

   indexed only; no formal relationship

   Engagement Status

   proposed; not undertaken

   Profile Summary

   Zeno Power develops compact radioisotope power systems, described as nuclear batteries, using strontium-90 heat sources for long-duration power in remote terrestrial, maritime, lunar, and space applications. The systems are under development and subject to nuclear material, launch, safety, and government controls.

   Potential Fit

   Could inform low-power, long-life backup energy for remote sensors, precursor probes, dark environments, and safety systems where solar or maintenance access is inadequate.

   Risks

   1. Radioisotope systems carry launch-accident, contamination, security, safeguards, disposal, and intergenerational stewardship risks.
   2. Fuel availability, specific power, conversion lifetime, licensing, and program schedule may constrain use.
   3. Government and defense-linked applications create export-control, dual-use, and controlled-information boundaries.

   Evidence Boundary

   Official-link review: the company site was reachable and describes strontium-90 radioisotope power systems and target applications. Operational readiness, qualification, fuel access, safety cases, availability, costs, complete lifecycle impacts, and mission fit were not independently verified; independent review pending.

   Conflicts

   The company has a commercial interest in radioisotope power; government awards, fuel suppliers, customers, investors, and regulatory interests were not independently investigated.

   What Would Change

   Independent safety and qualification evidence, demonstrated long-duration operation, a lawful fuel and disposal pathway, transparent lifecycle analysis, and a need unmet by safer alternatives would be required.

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