Statement
Unprepared legacy interfaces and proprietary standards can lock an architecture to fragile vendors.
Evidence dimensions
- Basis
- observed
- Readiness
- major scale up
- Confidence
- supported
Assessment rationale
The OSAM-1 record directly links an unprepared client and loss of a committed transition partner to a costly cancellation context, while GAO finds serviceability requirements and standards incomplete. A universal claim about all proprietary interfaces would be too strong, but lock-in and vendor fragility are credible architecture risks.
Citations and locators
- On-orbit Servicing, Assembly, and Manufacturing 1 (OSAM-1) (opens external site in a new tab)
NASA Headquarters announcement: cancellation followed technical, cost, schedule, integration and test risk, low return, lack of a transition partner, and a community shift away from refueling unprepared spacecraft. · direct observation - In-Space Servicing, Assembly, and Manufacturing: Benefits, Challenges, and Policy Options (opens external site in a new tab)
Highlights and pp. 17–23: operators generally do not require serviceable spacecraft; demand is circular; power, data, fluid-transfer, rendezvous, and servicing standards remain incomplete or emerging. · direct observation - International Docking System Standard Interface Definition Document, Revision F (opens external site in a new tab)
Revision F purpose and configuration-management process show the bounded interoperability enabled by a jointly maintained, public docking interface. · context only
Assumptions and limits
The assessment applies to this bounded statement and the cited source scopes. A source can support one relationship without validating a generation ship, and an editorial grade does not substitute for independent review or representative demonstration.
What would change this conclusion?
Longitudinal evidence that proprietary or unprepared interfaces produce equal or better interoperability, competition, repair, and continuity than prepared open interfaces would narrow the claim. Multi-vendor demonstrations, escrowed specifications, qualified alternates, and successful vendor-exit exercises would show that a particular architecture controls the risk.
Editorial record
- Prepared by: GShips Project
- Last reviewed: 2026-07-25
- Review status: substantive editorial review
- Reviewer: GShips Project editorial synthesis
- Independent review: pending two person required
- Conflicts: A future assurance venture could sell interface and supplier-risk analysis; this record does not characterize any named current vendor as fragile, malicious, noncompliant, or unsuitable.
- High-consequence domains: supply-chain, spacecraft-safety, dual-use