Operator Runbook¶
What you’re proving¶
You can classify failures by layer (toolchain, environment, capability tests, FI).
You can map proof summaries to actionable follow-ups.
You can interpret “pass/fail/not run” without over-claiming capability coverage.
Prereqs¶
Repo root:
<repo-root>Latest generated captures under
docs/_generated/test-outputs/
Steps¶
Regenerate evidence artifacts.
GOCACHE=/tmp/go-build FI_TARGET= make docs-gen
Inspect proof-oriented outputs.
sed -n '1,200p' docs/_generated/test-outputs/demo-output.txt
sed -n '1,220p' docs/_generated/test-outputs/fi-traceability-output.txt
Build docs strictly before release.
GOCACHE=/tmp/go-build FI_TARGET= make docs
Expected outputs (from real run)¶
VALIDATION PASS (checks=32, assurance=full (cgroup v2 ok), ...)
...
transport socket tests unavailable in this environment; running deterministic transport unit subset
...
=== Edge FI Test Summary ===
Pass: 2
Fail: 0
Not run: 1
...
- Overall: **PASS**
Verification¶
make docs-genexits0and refreshes generated outputs.make docsexits0(sphinx-build -W).docs/_generated/tbd-report.mdremains empty of unresolved items.
Common failure patterns and debug actions¶
Go cache permission denied:
Symptom:
open /home/ubuntu/.cache/go-build/... permission deniedAction: set
GOCACHE=/tmp/go-build.
Wrong Go toolchain in shell FI scripts:
Symptom:
invalid go version '1.23.0'/unknown directive: toolchainAction: prepend pinned Go bindir to
PATH.
Socket-restricted environment:
Symptom: transport tests report
socket: operation not permittedAction: rely on deterministic transport unit subset and document fallback evidence.
Integration prereq unavailable (registry/cosign):
Symptom: integrity tamper tests show
SKIPwith registry/cosign guidance.Action: start prereqs (
make demo-up/make demo-registry-test) before rerun.
Interpreting proof summaries¶
PASS: all executed checks passed.NOT RUN: intentionally excluded (e.g., root-required FI), not equivalent to failure.SKIP: prereq-gated test acknowledged by framework; evaluate if prereqs are required for your release gate.
Non-goals¶
This runbook does not authorize remote execution from control plane.
This runbook does not imply orchestration, leader election, or convergence.
Evidence¶
docs/_generated/test-outputs/demo-output.txtdocs/_generated/test-outputs/fi-traceability-output.txtdocs/_generated/test-outputs/policy-deny-output.txtdocs/_generated/test-outputs/offline-drain-output.txtdocs/_generated/tbd-report.mdMakefile(docs-gen,docs)