Princeton Satellite Systems

Packet identity

Packet ID

organizations:entity-princeton-satellite-systems

Packet SHA-256 identity

30c9468a2e56452a6ac6fa40b3cfe4c15d032327fa4f0842e4177d5e708580b1

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-princeton-satellite-systems

   Princeton Satellite Systems

   Record fingerprint

   bc6024f4014e07392b0c4fe41b3f2fcddb5c7ec1929e8e71782f21f915ae0b0d

   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-princeton-satellite-systems

   Legacy ID

   org-company--041

   Slug

   princeton-satellite-systems

   Name

   Princeton Satellite Systems

   URL

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

   Category

   Company and applied technology

   Geography

   New Jersey, United States

   Relevance

   enabling

   Engagement

   Proposed, not undertaken: benchmark public or licensed software on an open reference case, or commission a civil assumption-sensitive study only after procurement, licensing, export, and separate authorization review.

   Capability

   Spacecraft guidance, navigation and control software, simulation and embedded-system tools, aerospace studies, fusion-system modeling, and Direct Fusion Drive concept development.

   Entity Kind

   privately held commercial aerospace, software, and energy company

   Link Checked At

   2026-07-25

   Relationship

   indexed only; no formal relationship

   Engagement Status

   proposed; not undertaken

   Profile Summary

   Princeton Satellite Systems is a small commercial company developing spacecraft control and simulation software, aerospace engineering tools, and fusion-energy concepts including the early-stage Direct Fusion Drive. It is not part of Princeton University.

   Potential Fit

   Its control toolboxes and concept studies could support bounded spacecraft simulation, guidance and control, architecture comparison, and explicit evaluation of fusion-propulsion assumptions. Company concept work does not validate Direct Fusion Drive hardware or performance.

   Risks

   1. Direct Fusion Drive remains a proposed concept without an operational flight or power demonstration.
   2. Company publications and performance projections require independent physics and engineering review.
   3. Software licensing, source access, verification, support lifetime, and export terms may constrain long-term use.
   4. Control, fusion, and propulsion technologies have dual-use implications.

   Evidence Boundary

   The official company site and publications establish software products and fusion concept work; they do not establish Princeton University affiliation, generation-ship feasibility, or independently validated propulsion performance.

   Conflicts

   1. GShips could become a software customer or study sponsor and could benefit from optimistic fusion-propulsion results.

   What Would Change

   Independent code verification, open benchmark results, experimentally validated fusion subsystems, credible integrated balances, and an authorized commercial scope response would change 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