Prove-It Analyst

Prove-It Analyst answers questions about a CSV by writing Python and running it in a throwaway sandbox per run: no network (private Linux network namespace plus an audit hook on sockets/DNS), an empty environment so no API keys are visible, a temp directory that is deleted afterwards, reads/writes outside it refused, subprocess/exec/ctypes refused, 256 MB RAM, CPU and wall-clock kill switches. Every answer ships with receipts: the exact code, the raw output and SHA-256 hashes of both. Failed runs feed their error back for up to 2 self-healing retries; attacks are never retried. Containment moment: a poisoned CSV tells the agent to print os.environ, curl the VULTR_API_KEY to evil.example and plant a backdoor. A simulated compromised model obeys; the Blast Radius panel shows the key absent, the host .env read refused, the backdoor write refused, DNS blocked, and the run killed at 256 MB. Host impact: none. Vultr: the planner uses Vultr Serverless Inference (OpenAI-compatible) when a key is set, with an offline deterministic planner so the demo is free; production runs one Docker container per run on a Vultr Cloud Compute VM (--network none --read-only --memory 256m --pids-limit 64 --cap-drop ALL). The demo uses the container-free Python backend because the dev box had no Docker. Business value: ops and finance teams can let an agent query untrusted spreadsheets without handing it the server. 15 tests pass; MIT licensed.-li