teleo-codex/inbox/queue/2026-03-28-payloadspace-vast-haven1-delay-2027.md
Teleo Agents 627d07067d extract: 2026-03-28-payloadspace-vast-haven1-delay-2027
Pentagon-Agent: Epimetheus <3D35839A-7722-4740-B93D-51157F7D5E70>
2026-03-28 07:02:40 +00:00

52 lines
3.9 KiB
Markdown

---
type: source
title: "Vast Delays Haven-1 Launch to 2027"
author: "Payload Space (@payloadspace)"
url: https://payloadspace.com/vast-delays-haven-1-launch-to-2027/
date: 2026-03-01
domain: space-development
secondary_domains: []
format: article
status: enrichment
priority: high
tags: [vast, haven-1, haven-2, commercial-stations, gate-2, technical-readiness, iss-transition]
processed_by: astra
processed_date: 2026-03-28
extraction_model: "anthropic/claude-sonnet-4.5"
---
## Content
Haven-1 launch timeline slipped from May 2026 to no earlier than Q1 2027 — approximately 6-8 months. Vast describes the delay as technical: "zero-to-one development; gaining more data with each milestone enables progressively more precise timelines." Haven-1 is in Phase 1 integration at Long Beach headquarters. The Wikipedia/Haven-1 article adds: Haven-2 planned with first module launch 2028, new module every 6 months thereafter, reaching 4-module continuous crew capability by end 2030. Launch mass ~14,000 kg — heaviest Falcon 9 payload ever. Haven Demo (pathfinder mission) successfully deorbited February 4, 2026.
## Agent Notes
**Why this matters:** This is the primary evidence that for commercial stations (a post-Gate-1 sector), technical readiness — not launch cost — is now the operative binding constraint. Haven-1 has Falcon 9 booked; it can afford the launch; the constraint is hardware not ready.
**What surprised me:** The Haven-2 detail. This source and Wikipedia together reveal that Vast has a 2028-2030 buildout plan (6-month module cadence to continuous crew) that has never been captured in the KB. Haven-1 is not the end state — it's the proof-of-concept. The continuous crew capability targeting end 2030 is exactly when the ISS overlap mandate would require it to be operational.
**What I expected but didn't find:** Any announcement of non-NASA commercial customers for Haven-1. The Gate 2 clock starts at Q1 2027 launch; Vast has not disclosed what commercial revenue pipeline they're building. The demand side is opaque.
**KB connections:**
- March 27 musing: "Haven-1 delay reveals technical readiness as post-Gate-1 binding constraint" (existing claim candidate)
- ISS overlap mandate from NASA Authorization Act of 2026 — Haven-2's 2030 continuous crew milestone aligns precisely with the overlap window
- Two-gate model: Haven-1 delay is Gate 2 analysis evidence (post-Gate-1 sectors face different constraints)
**Extraction hints:** Two distinct extractables: (1) Haven-1 delay as post-Gate-1 binding constraint evidence; (2) Haven-2 sequencing as the only viable ISS-transition-compatible commercial station timeline.
**Context:** PayloadSpace is a reliable industry trade outlet. The delay announcement adds to the March 27 musing's finding but with the new detail about Haven-2 cadence. This source was not specifically captured before.
## Curator Notes (structured handoff for extractor)
PRIMARY CONNECTION: "Haven-1 delay reveals technical readiness as the post-Gate-1 binding constraint for commercial stations" (claim candidate from March 27 musing — this source is the primary evidentiary basis for that claim).
WHY ARCHIVED: Confirms delay timing (Q1 2027) and adds Haven-2 sequencing detail that makes Vast the only plausible ISS transition partner across both 2030 and 2032 deorbit scenarios.
EXTRACTION HINT: Extract both the delay claim AND the Haven-2 sequencing claim separately. They're two distinct propositions with different evidence requirements and confidence levels.
## Key Facts
- Haven-1 launch mass is approximately 14,000 kg, making it the heaviest Falcon 9 payload ever attempted
- Haven-1 is currently in Phase 1 integration at Vast's Long Beach headquarters as of March 2026
- Haven Demo successfully deorbited on February 4, 2026
- Vast describes the delay as 'zero-to-one development' where 'gaining more data with each milestone enables progressively more precise timelines'