- scripts/threat_traces.py: enforces the mechanical rules of the 2026-10-28
threat-trace pre-registration: required # meta keys; eval families first
reported 2025-07-01..2026-10-28 with a new-family/new-variant bucket and
write-up sources only; training families before the cutoff with every
fifth family (first-report order) in dev; no family in both files;
RFC 5737 addresses and .example domains only; size caps; and that every
file compiles with replay's parser. --sha256 prints the freeze digest.
- tests/trace_check.cpp: strawberry-trace-check dev tool (replay's parser).
- strawberry.gate: optional gate.warmup_hours (unset = the pre-registered
12 h; TEST pillars only).
- deploy/salt/test/fleet_run.sh: gate phase - tops sensor history past the
10 min injection floor, runs orch.strawberry_gate, asserts 3 gate models
were published, 9 pooled cells over 3 sensors with positives, sensors keep
their reports, and still no promoted model anywhere.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Round-1 bundles are not a fair baseline: the 120 s cursor overlap is a large
share of a few-minute test history. Verified on the live fleet: incremental
192/206/194 windows vs full 230/244/232.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
deploy/salt/test/: builds a release tarball from HEAD in ubuntu:24.04 (CI path),
boots systemd containers (rootless, no --privileged), master==central + 3
sensors with the host's Salt onedir mounted read-only, applies the real states,
runs a workload with planted YARA detections, then two orchestrated cycles.
43 checks (install/config/idempotence, real daemons + telemetry, R2 cache
miss/hit, cp.push collect, 3-seed cycle, canary hold then fleet rollout, no
promoted model anywhere, fleet bits in round 2, --since cursor, dedup).
State fixes found by running them for real:
- init.sls no longer includes strawberry.distribute: a plain state.apply on
sensors shipped models fleet-wide and bypassed the canary; only the
orchestration distributes now.
- install.sls: CI tarballs carry a +g<sha> suffix that 'strawberry version'
does not print, so install.sh re-ran on every apply; record the installed
release and compare base version + marker.
- orch collect: mv -f (re-collected bundles must not be skipped).
- central cycle: builds the overlay first; a training refusal for too few
teacher labels (normal on a young fleet) publishes the overlay only and
keeps the sensors' shadow, any other error still fails.
- distribute.sls: serves only what the cycle published (cp.hash_file; the
cp.list_master file-list cache can miss a just-published file).
Render check gains overlay-only and full publish cases (20 checks).
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>