Supervision Telemetry
Prevention log
Every event below represents a failure that was caught before it landed — a commit blocked, a destructive command denied, a vulnerable dependency flagged. The lines are produced bypipeline/supervision/logger.py, which appends one JSON object per prevented event to a date-stamped JSONL file. This page reads /prevention_log_sample.jsonl (a committed demo slice); production runs read your local.saica/prevention_log/ directory.
How to wire your own log
The supervisor writes to~/.saica/prevention_log/<YYYY-MM-DD>.jsonl(gitignored). To inspect today's events from a shell:
cat ~/.saica/prevention_log/$(date -u +%Y-%m-%d).jsonl | jq .
ls -la ~/.saica/prevention_log/ # one file per UTC dayTo preview your local log on this page during development, drop a symlink or copy atsite/public/prevention_log_sample.jsonl and reload — the fetch is plain HTTP. The path stays gitignored outside that one symlink.
| When ▾ | Tool | Failure mode | Mechanism | Detail | Invoked by |
|---|---|---|---|---|---|
| Loading… | |||||
What "prevention" means here
A prevented event is one a supervision tool stopped before it could cause harm — a commit rejected, a tool call denied, a PR opened to patch a CVE. Detection-only events (a scanner that warns but doesn't block) are out of scope; this log is deliberately narrow so the headline number is meaningful. The producer module ispipeline/supervision/logger.py; see also/tool-coverage for which tools cover which failure modes in the KG.