26 lines
1.7 KiB
Markdown
26 lines
1.7 KiB
Markdown
## Why
|
|
|
|
The prior Phase 3C-G artifacts measured serialized simulator timing, runtime CPU capacity, and a Darwin test binary rather than the actual deployable gateway candidate. VER-009, VER-010, VER-015, and OPS-009 require observed production traversal, bounded resource evidence, and exact artifact provenance before engineering exit.
|
|
|
|
## What Changes
|
|
|
|
- Drive impairment concurrently through the source-shaped provider UDP, native recovery, bounded queue, production pacer, QUIC, and public decoder.
|
|
- Measure RTT from actual Apollo ENet acknowledgements, one-way latency and jitter from delivery observations, and CPU from isolated process user/system consumption.
|
|
- Remove the unused legacy pacer so qualification and production share one scheduler.
|
|
- Build and inspect reproducible pure-Go Linux amd64 and arm64 gateway artifacts.
|
|
- Report dependency, scanner, architecture, and security evidence only when actually generated.
|
|
|
|
## Capabilities
|
|
|
|
### New Capabilities
|
|
|
|
- `gateway-deployment-artifact`: Reproducible, inspectable Linux gateway build and evidence requirements.
|
|
|
|
### Modified Capabilities
|
|
|
|
- `gateway-qualification`: Replace serialized/synthetic timing and CPU-capacity evidence with actual bounded traversal and process-consumption observations.
|
|
|
|
## Impact
|
|
|
|
This affects only the GPLv3 Data Plane qualification harness, resource evidence, production scheduler inventory, and gateway packaging target. It adds no dependency, cgo, sidecar, codec operation, direct provider route, Server dependency, or proprietary source. Live Apollo, macOS-client, physical-firewall, promotion scanning/signing, and Connection Server Phase 3C-C images remain outside this deterministic gate.
|