# Video handoff — Orbital Foundry

The teammate owns the video. This is a research handoff, not a replacement for their creative work.

## Core story

A valuable material can be difficult to manufacture because its internal structure depends on how it forms. Microgravity offers another process environment. A foundry could let researchers use shared orbital services while retaining specialized cartridges, then coordinate capacity across capsules.

## Three visual beats

1. **Materials:** show the published formulation-specific flight/Earth comparison in the research workspace. Keep its source and uncertainty labels visible. The project has not performed a new flight experiment.
2. **Foundry:** show shared services, isolated cartridges, and the compatibility matrix. NASA EXPRESS/MSRR provide precedents for shared infrastructure; our capsule resource loads are illustrative. Switching a pair to two thermal stages demonstrates a failed power/heat screen.
3. **Fleet:** show the same jobs sent through four policies, then change a sensitivity scenario. The initial coordinator does not win universally. The question is which processes should share, specialize or wait.

## Claims that are ready to show

- The original concept, supported by the source catalogue and its stated boundaries.
- A recalculation of published measurements, labeled as published evidence.
- A NASA raw-data access/QC pilot, labeled as pipeline verification.
- A sourced rack power-budget example, clearly separated from our capsule design.
- Reproducible synthetic scheduling results, including unfavorable scenarios.

## Claims that still need evidence

Do not imply measured capsule cost savings, qualified flight hardware, proven cooling-material improvement, clinical benefits, commercial customer commitments or an optimal scheduler. Structural images alone do not establish useful product performance.

## Demo capture path

Start the site with `npm run dev`. Use the original story's Present button for the concept. Open Research workspace for the published comparison, pair screen, sensitivity selector and execution plan. Keep the source labels in frame. Export browser notes separately when handing off decisions; those notes are not shared automatically.