# What Is Not in Our Data: Private Space Logistics Routes, Carrier Contracts, and Non-Public Manifests

- **Site:** bcesg.org
- **Program:** FRAME-300-BCESG — Freight, Rail & the Valley
- **Pillar:** Space Hardware
- **Evidence Basis:** Missing / Not-In-Our-Data Boundary
- **Primary Agency / Source:** BC ESG Evidence-Only Standard
- **As-Of / Repair Horizon:** 2026-11-16
- **2-Page Reference PDF:** https://bcesg.org/wp-content/uploads/2026/11/wa-space-hardware-not-in-our-data-private-routes.pdf
- **Infographic:** https://bcesg.org/wp-content/uploads/2026/11/wa-space-hardware-not-in-our-data-private-routes-infographic.png

> *Explicit Stop-and-Report transparency page: never reconstruct or guess private company logistics routes.*

## Summary

Public agency records document the Green River Valley's levees, SR 167, I-5, BNSF, NWSA, and SEA/BFI/PAE—but individual private space companies' exact truck routes, carrier contracts, and shipment schedules are not in our data.

## Documented Corridor Facts & Continuity Record

- Per William's reader-first and evidence-only standard, BC ESG documents only what primary public sources (USACE, King County, WSDOT, BNSF/NWSA, Port of Seattle) actually publish.
- Public records establish where space facilities sit (Census #1382–#1565) and which shared corridors serve those cities (SR 167, I-5, I-90, BNSF, NWSA, SEA/BFI/PAE).
- NOT IN OUR DATA: Exact carrier names, private truck schedules, barge/rail manifests, and proprietary routing for Blue Origin, Stoke Space, SpaceX Redmond, Amazon Leo, or any other private operator.

## Publicly Documented vs. Not-In-Our-Data Logistics Boundary

| Category | Status | What We Publish |
| --- | --- | --- |
| Facility Cities & Addresses | Documented (Census) | Publicly enumerable locations (Kent, Tukwila, Redmond, etc.) |
| Flood, Dam & Levee Events | Documented (USACE / KC) | Dec 2025 breaches, 2009 seepage, 2031 repair horizon |
| 737 Rail & NWSA/SEA Volumes | Documented (BNSF / NWSA) | 1,700–1,800 mi rail, 2014 crash, 3.16M TEUs, 69% air |
| Private Company Truck Routes | NOT IN OUR DATA | Explicitly withheld rather than reconstructed |

## Operational Exposure & Facility Playbook

- Facilities and logistics leads should apply our corridor and flood-exposure baselines against their own confidential carrier routing.
- When prime customers ask for sub-tier route resilience, disclose the shared valley corridor facts without fabricating private-carrier data.
- Any future primary-source disclosure (e.g., public NEPA/FAA environmental transport filings) will be added only with dated receipts.

## Connected Valley Cities, Segments & Role Briefs

- [WA Space Cluster Hub (#1382)](https://bcesg.org/washington-space-cluster-census/)
- [Blue Origin WA Profile](https://bcesg.org/blue-origin-washington-space-cluster-profile/)
- [Stoke Space WA Profile](https://bcesg.org/stoke-space-washington-space-cluster-profile/)
- [Supply-Chain & Procurement Desk Brief](https://bcesg.org/wa-space-role-procurement-lead-desk-brief/)
- [Program Manager Desk Brief](https://bcesg.org/wa-space-role-program-manager-desk-brief/)

## Primary Sources & Agency References

- [King County Flood Services](https://kingcounty.gov/en/dept/dnrp/nature-recreation/environment-ecology-conservation/flood-services)
- [WSDOT Commercial Vehicles & OSOW](https://wsdot.wa.gov/travel/commercial-vehicles)
- [NWSA Cargo Statistics (2025 TEUs)](https://www.nwseaportalliance.com/about-us/cargo-statistics)
