Redwire

Packet identity

Packet ID

organizations:entity-redwire

Packet SHA-256 identity

7cb75bb2fc83a9f79e941f813591af4e752e2c9a16ad6aea6dc9a0874242113f

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

   Redwire

   Record fingerprint

   7d6c088b5eca353d49b554a39a46de899dab46e2c9631f016949b3456ba8326b

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

   Legacy ID

   org-company--003

   Slug

   redwire

   Name

   Redwire

   URL

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

   Category

   Company and applied technology

   Geography

   United States / Europe

   Relevance

   enabling

   Engagement

   Proposed only, subject to a future fit check and then-current commercial terms: consider a competitive market-sounding or payload inquiry only after a specific experiment or interface requirement exists. No outreach, eligibility determination, commitment, or procurement has occurred.

   Capability

   Spacecraft components and platforms, deployable structures and solar power, microgravity research and manufacturing, biotechnology payloads, and mission integration.

   Entity Kind

   public space and defense technology company

   Link Checked At

   2026-07-25

   Relationship

   indexed only; no formal relationship

   Engagement Status

   proposed; not undertaken

   Profile Summary

   Redwire describes a civil, commercial, and national-security portfolio spanning spacecraft platforms and components, deployable structures and power systems, microgravity biotechnology and manufacturing payloads, sensors, avionics, and mission services. Its official site now resolves from redwirespace.com to rdw.com.

   Potential Fit

   Could inform modular spacecraft interfaces, deployable power and structures, in-space manufacturing experiments, and qualified component supply for Solar System precursor habitats; portfolio breadth does not establish integrated long-duration habitat capability.

   Risks

   1. The company serves national-security markets, so dual-use, export-control, and controlled-information boundaries may apply.
   2. Corporate acquisitions and portfolio changes can make capability descriptions or points of access stale.
   3. Public product claims do not establish price, availability, anomaly history, reliability, or suitability for autonomous century-scale service.

   Evidence Boundary

   Official-link review: the source URL redirected to Redwire's current rdw.com site, which was reachable and describes civil, commercial, and national-security offerings. Performance, qualification evidence, procurement access, data rights, and current availability were not independently verified; independent review pending.

   Conflicts

   Conflicts were not assessed beyond publisher disclosure in this official-link review; investor, customer, contracting, acquisition, and institutional conflicts were not independently investigated.

   What Would Change

   A defined civil requirement, current product data, independently reviewed qualification and anomaly evidence, transparent interfaces, and acceptable nonexclusive commercial terms would strengthen 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