Perjury

PERJURYEvery claim about the footage takes the stand. Say or type a sentence about a traffic video. PERJURY splits it into atomic claims and sends each one to the cheapest witness that can settle it. Each claim is ruled SUPPORTED, CONTRADICTED or "the pixels can't tell", with the evidence. The Cosmos jurors never see the claim, and code computes the verdict, not an LLM. It is a verify(claim) tool for any person or agent that has to sign off on what footage shows. How it uses the stack:VastDB: the records witness. Pushdown queries settle classes, counts and metadata across every segment before any GPU call. S3: keyframes and 4K evidence crops. DataEngine + VSS: reads the ingest pipeline's output, and evidence reels go back in via videos/upload. The stock agent is the A/B baseline. Cosmos3 Reasoner: jurors answer fixed questions on keyframe grids and put a box around each "yes". Cosmos-Embed1: picks the most claim-like moment per camera. YOLO11: its detections feed the records, and a zoom check must confirm every Cosmos "yes". Canary-1B: speech-to-text for spoken claims. Nemotron on W&B Inference: splits sentences into claims and labels captions. Weave: traces every verdict, logs 👍/👎 feedback, and runs the 47-claim bench. CoreWeave: GPU host. Each verdict shows its GPU-seconds. K8s + FastAPI: live at /app. Cursor: ships a perjury-verify skill.