mrwulf 5b0158ecef Machine protection: route all pacta Lean compiles through lean-guard ... pacta's replay invoked `lake env lean` bare - on the reference machine that is exactly the pattern that once OOM-crashed the host (see the corpus' POSTMORTEM). New RepoConfig.lean_guard (set for all five repos in examples/repos.yaml: verification/lean-guard): when configured, every compile and axiom audit runs `lake env <guard> <file> --root=...` instead of bare lean - hard memory cap via systemd scope + lean -M, core pinning, timeout, single-flight lock, free-RAM preflight with the Guard-3a retry ladder, all tuned via LEAN_MEM_MB / LEAN_MIN_FREE_MB / LEAN_MEM_WAIT_SEC / LEAN_TIMEOUT / LEAN_MAX_CORES. Provider attestations now record a machine_protection block naming the guard (or "UNGUARDED"). Smoke-tested live on the real dalek repo: clamping trace visible, compile green. 49/49 tests green. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>		2026-07-06 10:42:59 +02:00
..
__init__.py	add nested proof check provider	2026-07-03 13:03:58 +02:00
__main__.py	add nested proof check provider	2026-07-03 13:03:58 +02:00
cli.py	Log accountability: STH pinning, consistency enforcement, freshness, monitor	2026-07-06 10:08:34 +02:00
discovery.py	add nested proof check provider	2026-07-03 13:03:58 +02:00
service.py	Machine protection: route all pacta Lean compiles through lean-guard	2026-07-06 10:42:59 +02:00
transparency_log.py	Log accountability: STH pinning, consistency enforcement, freshness, monitor	2026-07-06 10:08:34 +02:00