Framework
Framework 01 — Capability Transfer
Programs can change. Capabilities can persist.
Major space programs are built around specific objectives, architectures, and timelines. However, the value they create is rarely limited to the spacecraft, station, or mission they were originally designed to deliver.
Over years of development, these programs generate technologies, engineering knowledge, specialized supply chains, manufacturing capacity, testing infrastructure, operational experience, and institutional expertise. When a program is redesigned, reduced, redirected, or cancelled, these capabilities do not necessarily disappear with it.
The Capability Transfer Framework provides a structured method for evaluating what happens to this accumulated capability when its original program changes.
The Framework follows four stages:
Dependency → Transferability → Repurposing → Retained Value
⸻
1. Dependency
The first stage examines how dependent a capability is on the program for which it was originally developed.
Some capabilities are highly specialized. Their design, interfaces, infrastructure, operating conditions, or mission requirements may make them difficult to use outside the original architecture.
Other capabilities are more modular and adaptable. They may be compatible with different systems, missions, or commercial applications.
Dependency determines the starting conditions for capability transfer:
The greater the dependency on the original program, the more difficult and costly the transfer is likely to be.
Assessing dependency prevents the assumption that every technology or industrial asset created by a program can automatically survive its restructuring.
⸻
2. Transferability
The second stage determines which parts of the accumulated capability can move beyond the original program.
Transferability is not limited to physical hardware. It may include:
engineering knowledge and technical expertise;
software and control systems;
manufacturing methods and production processes;
robotics and communications technologies;
specialized suppliers and industrial relationships;
testing facilities and research infrastructure;
operational procedures and mission experience;
standards, interfaces, and technical data.
A program may therefore lose its original mission while retaining considerable technological and industrial capability.
However, transferability represents only potential. A capability may technically be reusable without having a credible destination, sufficient funding, or an organization prepared to adopt it.
⸻
3. Repurposing
Repurposing examines whether transferable capability is actually applied in a new context.
The central question becomes:
Where can the capability go next?
A capability may be:
incorporated into another government program;
adapted for a different mission architecture;
transferred to a commercial application;
used in a future exploration system;
integrated into another spacecraft or platform;
or developed into an entirely new capability.
This distinction is essential:
A transferable capability has potential value. A successfully repurposed capability has found a new path through which that value can be realized.
Repurposing therefore marks the transition from theoretical adaptability to actual continued use.
⸻
4. Retained Value
The final stage evaluates how much of the value created during the original development survives the transition.
Retained value may be:
technological;
scientific;
operational;
industrial;
economic;
institutional;
or strategic.
A program-level change can produce very different outcomes.
At one extreme, highly specialized development may become stranded because it cannot be separated from its original mission or architecture.
At the other, technologies, expertise, suppliers, facilities, and operational knowledge created for one program may migrate into new missions and continue producing value for years.
The important question is therefore not only:
How much was invested in the original program?
It is also:
How much of the capability created by that investment remains useful after the original objective changes?
This distinction provides a more complete understanding of program value. Cancellation or restructuring may reduce the value of the original mission while preserving part of the capability accumulated around it.
⸻
Observable Signals
Retained value should not be assumed merely because a capability appears transferable. Evidence must show that the capability has moved beyond theoretical potential.
Observable signals may include:
integration into another government or commercial program;
new funding for adaptation, continued development, or deployment;
reuse of engineering teams, suppliers, facilities, or production capacity;
commercialization or licensing of the underlying technology;
incorporation into a new mission architecture;
continued testing or technology development;
operational deployment in a different system or market.
These signals distinguish potential transfer from realized transfer.
Without observable evidence, a capability may remain technically reusable while producing no continuing technological, industrial, or economic value.
⸻
The Gateway Example
The logic of Capability Transfer can be observed in developments surrounding NASA’s Gateway architecture.
As Artemis plans and program requirements evolve, capabilities originally developed for particular Gateway contributions may be evaluated for modified applications or new destinations rather than viewed only through the objectives for which they were initially created.
The important signal is therefore larger than the fate of any individual Gateway component.
It demonstrates a broader principle:
Program change does not necessarily equal capability loss.
The more transferable the technology, knowledge, infrastructure, and industrial capacity created by a program are, the greater the possibility that part of its accumulated value can survive a change in architecture.
However, retained value should only be recognized when a credible path for repurposing—and observable evidence of continued use—exists.
⸻
How to Use the Capability Transfer Framework
When evaluating the restructuring, redirection, reduction, or cancellation of a major space program, ask five questions:
1. Dependency
How dependent is the capability on its original program, interfaces, infrastructure, and mission architecture?
2. Transferability
Which technologies, knowledge, facilities, suppliers, processes, or operational capabilities can move elsewhere?
3. Repurposing
Has a credible new application, program, customer, mission, or destination been identified?
4. Retained Value
What technological, scientific, industrial, economic, operational, or strategic value could survive the transition?
5. Evidence
What observable activity demonstrates that the transfer has actually occurred?
These questions help distinguish between a capability that merely appears reusable and one that has genuinely found a new economic, technological, or operational path.
⸻
Relationship to the SEI
SEI Relevance — Structural
Capability Transfer does not directly belong to any single SEI DataPool. It is a structural mechanism through which changes in major programs may later produce measurable signals elsewhere in the space economy.
Its effects may become visible through:
Research, when transferred knowledge or technology continues through meaningful development;
Investment, when new capital is committed to adaptation, commercialization, or deployment;
Competition, when the transferred capability changes the position of government or commercial actors;
Launch, only when the capability eventually contributes to qualifying orbital launch activity.
Transferability alone does not affect the SEI. Only observable activity that meets the criteria of a relevant DataPool can enter the index.
The Framework therefore provides structural context for interpreting how program-level change may later translate into measurable economic activity.
Capability Transfer is not itself an SEI signal.
It is a mechanism through which program change may later generate observable SEI signals.
⸻
Core Principle
Programs can change. Capabilities can persist.
The economic consequences of a program change cannot be understood solely by measuring the budget reduced, the contract altered, or the mission cancelled.
A more complete assessment must also examine whether the technologies, knowledge, infrastructure, supply chains, and industrial capacity created by that program can move elsewhere—and whether that transfer produces observable value.