Paragon Space Development

Packet identity

Packet ID

organizations:entity-paragon-space-development

Packet SHA-256 identity

a412d15fef059bbbce9161e7de134848734604b86834f12494e94c2d9efa6125

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-paragon-space-development

   Paragon Space Development

   Record fingerprint

   7d72233e19e3ebe7cf66b429a6aca724692c2ba325af55e59ff82105cb110f31

   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-paragon-space-development

   Legacy ID

   org-company--001

   Slug

   paragon-space-development

   Name

   Paragon Space Development

   URL

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

   Category

   Company and applied technology

   Geography

   Arizona, United States

   Relevance

   enabling

   Engagement

   Proposed, not undertaken: prepare mass, energy, contaminant, reliability, maintainability, interface, and test requirements and, if procurement is authorized, ask whether a paid nonexclusive study or hardware test is available.

   Capability

   Life-support and environmental-control systems, thermal control, systems engineering and integration, ISRU, suit systems, analysis, manufacturing, testing, and product licensing.

   Entity Kind

   privately held commercial aerospace company

   Link Checked At

   2026-07-25

   Relationship

   indexed only; no formal relationship

   Engagement Status

   proposed; not undertaken

   Profile Summary

   Paragon Space Development Corporation is a commercial aerospace company developing life-support, environmental-control, thermal-control, suit, in-situ resource-utilization, systems-integration, manufacturing, and test solutions for space, defense, and extreme environments.

   Potential Fit

   Paragon experience could support a bounded ECLSS architecture study, environmental-control test article, thermal analysis, sensor package, or maintainability review for an Earthside or orbital habitat precursor. Flight and project heritage does not establish century-scale closure.

   Risks

   1. Human-life-support claims are high consequence and require contract- and configuration-specific evidence.
   2. Commercial price, availability, intellectual property, data rights, export status, and support duration are unknown.
   3. Defense work creates dual-use and export-control boundaries.
   4. Existing systems depend on resupply, ground expertise, and finite mission durations.

   Evidence Boundary

   The official site establishes Paragon's product and engineering areas and selected project descriptions; it does not independently validate every claim or establish generation-ship suitability, availability, or endorsement.

   Conflicts

   1. GShips could become a customer or study sponsor and use contractor heritage in future habitat-assurance claims.

   What Would Change

   An authorized technical response, transparent representative test data, independent ECLSS review, long-duration failure recovery, and closed-loop balance evidence would change readiness.

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