Space Tango

Packet identity

Packet ID

organizations:entity-space-tango

Packet SHA-256 identity

e7bdb6b00c959cc2fe1806dec31e5e0af7bc4d654447b98b6b2459185f520535

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-space-tango

   Space Tango

   Record fingerprint

   f6e82c1b274d5009b0ade8f6ec4c522bcc499c8a033e8f53d7b9ccb157a0bce4

   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-space-tango

   Legacy ID

   org-company--035

   Slug

   space-tango

   Name

   Space Tango

   URL

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

   Category

   Company and applied technology

   Geography

   Kentucky, United States

   Relevance

   enabling

   Engagement

   Proposed only, subject to a future fit check and then-current flight opportunities: consider a competitive payload study only after a hypothesis, controls, safety case, budget, sample plan, and data-rights requirement are defined. No outreach, payload booking, commitment, or procurement has occurred.

   Capability

   Automated microgravity payloads, experiment integration, flight operations, data handling, biotechnology and materials research, and in-space manufacturing.

   Entity Kind

   private microgravity research and manufacturing company

   Link Checked At

   2026-07-25

   Relationship

   indexed only; no formal relationship

   Engagement Status

   proposed; not undertaken

   Profile Summary

   Space Tango develops automated research and manufacturing payload systems for microgravity, including modular hardware and mission services associated with the International Space Station and other platforms. It supports experiments from integration through operations and data return.

   Potential Fit

   Could support bounded precursor experiments in biology, materials, autonomous payload operations, or maintenance workflows where microgravity is a genuine variable and Earthside scientific value is clear.

   Risks

   1. Flight access, payload volume, crew time, schedule, launch, and return logistics are constrained and volatile.
   2. Microgravity experiments can be underpowered or confounded and require independent scientific review.
   3. Commercial and customer confidentiality may restrict anomaly, protocol, and raw-data transparency.

   Evidence Boundary

   Official-link review: the company site was reachable and describes automated research, manufacturing, payload hardware, and mission services. Current platform access, flight record, experiment outcomes, prices, failure data, and suitability for a specific study were not independently verified; independent review pending.

   Conflicts

   Conflicts were not assessed beyond publisher disclosure in this official-link review; customers, platform operators, launch providers, investors, and intellectual-property interests were not independently investigated.

   What Would Change

   A preregistered experiment, confirmed flight opportunity, transparent integration terms, independent peer review, and access to raw results and anomalies would determine 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