Two ways to test Paperclip. Follow each program from a test case to its evidence, results, and run history.
Does the runner use tools correctly, respect permissions, and preserve its execution contract?
Can a user complete work through Paperclip, from the first request to a usable result?
Snapshot refreshed $refreshed. History pages may contain newer runs. A partial campaign covers only its selected cases. These programs measure different boundaries; their pass rates are not combined.
The eval guide explains which program to use, how to add a case, and how to distinguish a product defect from model behavior, a grading error, or a setup failure. Evalbook is a report framework used to present evidence; it is not an execution boundary.