16 lines
1.3 KiB
Markdown
16 lines
1.3 KiB
Markdown
## ADDED Requirements
|
|
|
|
### Requirement: Reproducible pure-Go Linux gateway artifacts
|
|
The candidate SHALL build the gateway with the normal immutable Protocol module boundary for Linux amd64 and arm64 using `CGO_ENABLED=0`, deterministic path/VCS/build-ID settings, and no sidecar. Two independent builds of each architecture MUST be byte-identical.
|
|
|
|
#### Scenario: Both Linux architectures are built
|
|
- **WHEN** the canonical gateway Linux target runs twice from the same frozen source and dependency inputs
|
|
- **THEN** both amd64 and arm64 outputs are byte-identical pure-Go ELF executables with matching embedded GOOS, GOARCH, and cgo settings
|
|
|
|
### Requirement: Artifact evidence is inspected and truthful
|
|
Candidate evidence SHALL record exact source and Protocol revisions, artifact hashes, architecture, embedded dependency inventory, container configuration when built, and the actual scanner/signing status. It MUST NOT claim an SBOM, vulnerability result, signature, image architecture, or deployment that was not produced and inspected.
|
|
|
|
#### Scenario: Supplemental scanner is unavailable
|
|
- **WHEN** no qualifying vulnerability scanner is available in the frozen environment
|
|
- **THEN** the artifact remains explicitly unscanned, deterministic compiler/dependency/boundary evidence is retained, and no zero-finding security claim is emitted
|