evidence: land honey-backbone preflight packets (2026-07-14) - #574
evidence: land honey-backbone preflight packets (2026-07-14)#574Jesssullivan wants to merge 1 commit into
Conversation
…from untracked working tree)
|
[authority and failure hold — 2026-07-30] Exact head remains The red |
|
[source-integrity fence — 2026-07-30] The sole commit Keep this history unmergeable. Preserve the rescued 120-file evidence tree, but replace it through a signed composition path after CI authority is corrected; no force-push or hosted rerun is authorized here. |
Summary
Lands 10 honey-backbone preflight evidence packets generated during the
2026-07-14 honey-backbone preflight runs (
docs/release/evidence/honey-backbone-preflight-20260714T*).These packets were generated on the facet6 primary checkout and sat untracked
in the working tree since; landing them now per the repo's immutable-evidence
convention (docs/release/evidence/README.md) so they don't get lost to a
worktree cleanup.
result.env,summary.md, device list/status transcripts(local + honey via ssh), redacted config TOML, tcfs status output, and
NATS endpoint probes
proof=blocked-g2(neo-side storage/NATS not OK);3 report
proof=honey-backbone-preflight-completematerial (tokens, keys, passwords) before landing — only public
age1...recipient keys and internal tailnet endpoints appear, consistent with the
*-config.redacted.tomlnamingdocs/release/evidence/README.md— the "Current promotedproofs" table is untouched; these are blocker/partial packets per the
ledger's own claim rules, not stronger proofs that would warrant a
promotion
Test plan
(byte-identical)
BEGIN/age1/AKIA/ghp_/github_pat) — only public age recipient keys and one
stack-trace symbol name (
connect_daemon_with_token) matched, no actualsecret material
Not merging — opening for operator review per the immutable-evidence rescue
convention.