ThinkOrbital

Packet identity

Packet ID

organizations:entity-thinkorbital

Packet SHA-256 identity

cb8124e5bfba6ce29d11d9e6ea694adac971097e1be390b5a72f4e43b3d0ecc8

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

   ThinkOrbital

   Record fingerprint

   69e8f0961371102deb98c002cb7eca6c32723e0b3a29d4412466b7931bd80f67

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

   Legacy ID

   org-company--011

   Slug

   thinkorbital

   Name

   ThinkOrbital

   URL

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

   Category

   Company and applied technology

   Geography

   Colorado, United States

   Relevance

   enabling

   Engagement

   Proposed only, subject to a future fit check and then-current program access: consider a bounded standards or test-data review after a specific joint, inspection method, material, and relevant environment are defined. No outreach, commitment, or procurement has occurred.

   Capability

   In-space welding, robotic assembly, structural inspection and repair, large-space-structure concepts, and orbital infrastructure design.

   Entity Kind

   private in-space construction company

   Link Checked At

   2026-07-25

   Relationship

   indexed only; no formal relationship

   Engagement Status

   proposed; not undertaken

   Profile Summary

   ThinkOrbital develops concepts and hardware for assembling, welding, inspecting, and repairing large structures in orbit. Official material emphasizes robotic construction and large pressurized or unpressurized platforms assembled after launch rather than constrained to a single fairing.

   Potential Fit

   Could inform orbital construction, weld inspection, modular expansion, structural repair, and assembly testbeds for large Solar System habitats; current demonstrations do not validate pressure-vessel scale or long service life.

   Risks

   1. Large pressurized structures require much stronger evidence than small weld or robotic demonstrations.
   2. Development financing, launch access, schedule, and technical approach may change.
   3. Construction robotics and large structures have civil and defense dual-use implications.

   Evidence Boundary

   Official-link review: the site was reachable and describes in-space construction, welding, inspection, and large-structure ambitions. Demonstration maturity, pressure integrity, repair evidence, costs, availability, and multi-decade lifecycle were not independently verified; independent review pending.

   Conflicts

   Conflicts were not assessed beyond publisher disclosure in this official-link review; investors, government customers, suppliers, patents, and demonstration partners were not independently investigated.

   What Would Change

   Independent weld and nondestructive-evaluation data, relevant-environment demonstrations, pressure testing, repeated repair evidence, and open interface standards would strengthen fit.

Linked records—not review targets here

These records provide dependency or relationship context. Their decisions belong to their single primary packet, preventing double counting.

• autonomous-maintenance-circular-industry · entity-thinkorbital partner-task-match:match-autonomous-maintenance-circular-industry-thinkorbital · 75fda1ab0f329cea0900ce96ac24ef3eba2506899b7dcfc4045f74ea4f261701

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