TransAstra

Packet identity

Packet ID

organizations:entity-transastra

Packet SHA-256 identity

2461ac5c816f125aab5aa40878a8c81d72846922d3e997912424cdecd93a2740

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-transastra

   TransAstra

   Record fingerprint

   49c578e84b4a91481aecafbd94b58a0099a579f130b41f2dffee4361401ddc8d

   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-transastra

   Legacy ID

   org-company--025

   Slug

   transastra

   Name

   TransAstra

   URL

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

   Category

   Company and applied technology

   Geography

   California, United States

   Relevance

   enabling

   Engagement

   Proposed only, subject to a future fit check and then-current data and commercial access: evaluate one published subsystem or test result against a defined precursor requirement before considering a paid study or experiment. No outreach, commitment, or procurement has occurred.

   Capability

   Solar-thermal propulsion and processing, small-body detection, resource capture concepts, optical systems, and in-space logistics research.

   Entity Kind

   private space resources and propulsion company

   Link Checked At

   2026-07-25

   Relationship

   indexed only; no formal relationship

   Engagement Status

   proposed; not undertaken

   Profile Summary

   TransAstra develops solar-thermal propulsion and processing, asteroid detection and characterization, and concepts for capturing, moving, or extracting resources from small bodies. Its portfolio combines funded prototypes and ambitious resource-logistics proposals at differing readiness levels.

   Potential Fit

   Could inform resource prospecting, optical tracking, solar-thermal processing, capture mechanics, and logistics trade studies for Solar System precursor infrastructure, without assuming asteroid mining economics or generation-ship propulsion.

   Risks

   1. Asteroid resource markets, legal rights, logistics economics, and system-scale feasibility remain uncertain.
   2. Performance and readiness vary across detection, capture, propulsion, and processing concepts.
   3. Propulsion, tracking, and object-moving capabilities have dual-use and planetary-defense implications.

   Evidence Boundary

   Official-link review: the site was reachable and presents solar-thermal, asteroid-resource, detection, and logistics projects. Current project status, independent performance replication, commercial availability, costs, legal feasibility, and system integration were not independently verified; independent review pending.

   Conflicts

   Conflicts were not assessed beyond publisher disclosure in this official-link review; investors, government awards, customers, patents, and advocacy interests were not independently investigated.

   What Would Change

   Peer-reviewed current test data, a relevant flight demonstration, transparent energy and mass balances, lawful resource rights, and a credible Earthside or precursor customer would refine 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