Contested Reliability Tutorial

What you’re proving

  • FI retry exhaustion does not reactivate beyond window (FI-C4-03).

  • Quota enforcement under authorized flood rejects excess traffic but keeps session semantics (FI-C3-03).

  • Seeded contested scenario distribution remains stable and verifiable.

Prereqs

  • From repo root

  • Go + Python available

Steps

  1. Build and run broad edge quality + FI suite:

cd <repo-root>
make edge-build
make edge-test
make edge-scan
make fi

  1. Run focused FI checks:

cd edge
GOWORK=off go test -v ./retry -run '^TestFI_C4_03_NoPeriodicReactivation$'
GOWORK=off go test -v ./quota -run '^TestFI_C3_03_AuthorizedPeerFlood$'

  1. Run contested seed verification:

cd <repo-root>
make demo-seed-contested
make demo-verify-contested

Expected outputs (real patterns):

--- PASS: TestFI_C4_03_NoPeriodicReactivation
--- PASS: TestFI_C3_03_AuthorizedPeerFlood

[verify] All assertions PASSED.

=== Proof Summary ===
Build: PASS
Unit/race: PASS
Prohibited scan: PASS

How to verify

  • make fi exits 0 and writes /tmp/edge-fi-report/traceability.md.

  • Focused tests above are PASS.

  • demo-verify-contested reports all assertions passed.

Common failure modes + debugging

  • Root-required FI not run in non-root mode: run sudo make fi-root separately when needed.

  • go version mismatch during root runs: ensure the same toolchain is available to root shell.

  • Contested verify failure: re-seed DB via make demo-seed-contested and rerun verify.

Do Not Do / Non-goals

  • Do not describe these checks as fleet orchestration validation.

  • Do not infer any push command authority from control-plane side outputs.

Evidence

  • Makefile targets: fi, fi-root, demo-seed-contested, demo-verify-contested

  • edge/retry/retry_test.go (TestFI_C4_03_NoPeriodicReactivation)

  • edge/quota/localquota_test.go (TestFI_C3_03_AuthorizedPeerFlood)

  • edge/ci/tests/print_proof_summary.py

  • demo/scripts/verify_contested.py