Starfish Space

Packet identity

Packet ID

organizations:entity-starfish-space

Packet SHA-256 identity

ec16b0f295f41c16ff20410907e75cb07da8138e07c6cb27d866e2e39b1420e7

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

   Starfish Space

   Record fingerprint

   9ba0fafe661827cc933de1c2d6580ead085521117f0030f8b71cf5666359713b

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

   Legacy ID

   org-company--020

   Slug

   starfish-space

   Name

   Starfish Space

   URL

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

   Category

   Company and applied technology

   Geography

   Washington, United States

   Relevance

   enabling

   Engagement

   Proposed only, subject to a future fit check and then-current mission access: consider a civil interface study or competitive servicing option after a specific target, cooperative authorization, safety case, and data requirement exist. No outreach, booking, commitment, or procurement has occurred.

   Capability

   Autonomous rendezvous and proximity operations, relative navigation, docking, on-orbit servicing, life extension, and disposal missions.

   Entity Kind

   private on-orbit servicing company

   Link Checked At

   2026-07-25

   Relationship

   indexed only; no formal relationship

   Engagement Status

   proposed; not undertaken

   Profile Summary

   Starfish Space develops autonomous rendezvous, proximity operations, docking, and life-extension services, including the Otter servicing vehicle and Cephalopod relative-navigation software. These technologies target orbital servicing and disposal tasks, not long-duration habitat autonomy as a whole.

   Potential Fit

   Could inform serviceable interfaces, inspection, cooperative docking, life extension, and robotic maintenance for Solar System precursor infrastructure if safety, permissions, and non-cooperative-use boundaries are explicit.

   Risks

   1. Rendezvous and docking capabilities are inherently dual-use and can support counterspace activity.
   2. Demonstrations or announced missions do not establish routine service reliability across targets and orbits.
   3. Licensing, customer authorization, insurance, export controls, interface compatibility, and collision risk constrain use.

   Evidence Boundary

   Official-link review: the company site was reachable and describes Otter, Cephalopod, servicing, and autonomous rendezvous goals. Current flight status, full reliability evidence, service availability, pricing, anomaly data, and specific mission fit were not independently verified; independent review pending.

   Conflicts

   Conflicts were not assessed beyond publisher disclosure in this official-link review; investors, government contracts, customers, insurers, and competitors were not independently investigated.

   What Would Change

   Completed cooperative servicing missions, published safety and anomaly evidence, standard interfaces, clear civil authorization, and acceptable independent data access 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