24 lines
1.2 KiB
Markdown
24 lines
1.2 KiB
Markdown
# Phase 1.0CZ: inactive launch-canary one-shot runner
|
|
|
|
Status: `INACTIVE_ARTIFACT_SPECIFIC_HARDWARE_GATE`
|
|
|
|
Date: 2026-07-30
|
|
|
|
CZ binds the reproducible 1,845,240-byte launch-canary ELF and adds no free
|
|
protocol selector. Only an exact active CZ manifest can select `CHD10AV1`; D14
|
|
is the sole accepted terminal. The runner also requires exactly one ordered
|
|
D07, D04 and D14, exact RAW semantics for D07/D04, zero cleanup-error fields
|
|
in D14, at most one D12 and no bytes after terminal. The inherited raw-ELF route remains one connect,
|
|
one send, one write-half-close, bounded receive, consumed receipt before the
|
|
socket and exclusive trace creation.
|
|
|
|
The tracked manifest and approval template are inactive. They contain no
|
|
target, port or run ID, all hardware authorizations are false, and artifact
|
|
eligibility is false. Editing the tracked template is not an approval. A real
|
|
attempt requires a new active-task statement from Jens naming this exact
|
|
artifact and scope, plus a separately matching untracked approval.
|
|
|
|
This gate covers only the raw-elfldr baseline arm. It does not use shsrv/hbldr
|
|
and cannot prove the BigApp launch-context hypothesis. Work on a bounded
|
|
nonpersistent BigApp launcher remains a separate offline track.
|