YOUNIVERSE1 / PILOT DEVELOPMENT PACKAGE
Constellation interlink · baseline condition
Within model target · modeled outcome
Move mission data across representative interlinks. Calculated from a reference configuration and your inputs; this is not a measured acceptance result.
Capacity comparison · percentages may exceed 100%
| Measure | Current state | Growth scenario |
|---|---|---|
| Capacity & headroom | Within target | Within target |
| Window delivery | Within target | Within target |
| Buffer accumulation | Within target | Within target |
| Window continuity | Within target | Within target |
| Evidence completeness | Within target | Within target |
| Path latency | Within target | Within target |
| Gateway aggregation | Within target | Within target |
| Support coverage | Within target | Within target |
Galaxity
80% of required evidence is present; 2 items remain. Source review is still required.
Galaxity
12 → 5 incidents in the supplied comparison. Source: synthetic. This does not prove improvement caused by a solution.
Shared network
Aggregate traffic uses 56% of primary capacity; 880 Mbps headroom. Review threshold: 80%.
Shared network
Modeled one-way link latency is 11.01 ms against a 50 ms target. Queueing and complete route behavior need separate measurement.
Star Jumper
Usable geometry occupies 66.67% of the window; primary time coverage after the availability assumption is 66%.
Star Jumper
504 GB of 504 GB offered can be served in this fluid-flow approximation (100%).
Star Jumper
Unserved data: 0 GB against 200 GB buffer. Primary-contact drain time: 0 min.
Ground networks
Modeled time coverage is 99.83% against 99%. Coverage alone does not guarantee enough delivery capacity.
Ground networks
560 Mbps per gateway; 28% aggregate gateway utilization across 2 gateways.
Ground networks
Configured terminal energy is 1.28 kWh for the test window. Facility and supporting equipment energy is outside this estimate.
Galaxity
32 events/sec; 16% collector utilization; 0.05 GB of event data in this window.
Galaxity
15 dependencies remain outside the declared ready set (25% ready). Compatibility and security testing remain required.
Shared network
8 devices per operator; 20% of the supplied support envelope.
Shared network
16 devices in the growth scenario. Primary utilization changes from 28% to 56%; gateway, collection and support capacity stay fixed.
Coordination
Selected numerical gates are within the reference targets. Review evidence and run representative measurements before rollout.
Devices × average traffic per device.
Offered load against configured aggregate capacity.
Distance divided by light speed, with fiber propagation factor.
Packet size divided by available link rate.
Propagation, serialization and supplied processing delay.
Usable minutes divided by the modeled window.
Effective link capacity over usable contact time.
Unserved offered traffic over the modeled window.
Backlog divided by spare service rate during a usable contact.
Primary loss and fallback contribution with capped delivery.
Primary time coverage combined with independent fallback availability.
Device power × device count × elapsed time.
Projected throughput per gateway and gateway headroom.
Device event rate against collection capacity; event volume.
Available evidence fields against required fields.
Supplied before/after incident counts and source status.
Known dependencies marked ready against inventoried dependencies.
Configured devices per operator against the supplied support limit.
| Input | Current assumption | Growth assumption |
|---|---|---|
| Devices | 8 | 16 |
| Traffic Mbps | 70 | 70 |
| Capacity Mbps | 2000 | 2000 |
| Growth | 2 | 2 |
| Window Min | 60 | 60 |
| Contact Min | 40 | 40 |
| Primary Availability Pct | 99 | 99 |
| Fallback Mbps | 1000 | 1000 |
| Fallback Availability Pct | 99.5 | 99.5 |
| Distance Km | 1800 | 1800 |
| Medium | vacuum | vacuum |
| Processing Ms | 5 | 5 |
| Packet Bytes | 1500 | 1500 |
| Buffer GB | 200 | 200 |
| Power W | 80 | 80 |
| Gateways | 2 | 2 |
| Gateway Capacity Mbps | 2000 | 2000 |
| Events Per Device Sec | 2 | 2 |
| Collector Events Sec | 200 | 200 |
| Event Bytes | 400 | 400 |
| Evidence Available | 8 | 8 |
| Evidence Required | 10 | 10 |
| Incidents Before | 12 | 12 |
| Incidents After | 5 | 5 |
| History Source | synthetic | synthetic |
| Crypto Total | 20 | 20 |
| Crypto Ready | 5 | 5 |
| Operators | 2 | 2 |
| Devices Per Operator | 40 | 40 |
| Target Latency Ms | 50 | 50 |
| Target Continuity Pct | 99 | 99 |
| Target Delivery Pct | 95 | 95 |
| Headroom Pct | 20 | 20 |
Use the flagged measures to choose the next experiment. Agree the customer outcome, collect an authorized baseline, test representative load and recovery, then record a human acceptance decision. The coordinator issues no rollout approval and performs no network changes.
Youniverse1 test-environment report · version 1.0.0 · 2026-09-28T00:00:00.000Z. This is an example of the development package. Detailed client reports use the contracted scope, approved evidence and measured pilot outcomes.