How it works¶
K-Veritas watches your run and has a server sign what it saw. It never sees your data and never reruns your code.
| Page | In short |
|---|---|
| Signing | Any change to the report is caught. |
| Who signed it | Signed by K-Veritas, not the author. Public ledger. |
| Every run counts | No run can be hidden or edited later. |
| Other sessions | One open session per machine; the report lists your sealed and open sessions. |
| Did it really run | The hardware trace looks like real work. |
| Compute check | The claimed work fits the hardware. |
| Code and privacy | Which code ran, and what you choose to show. |
| Share one file | Prove one file without showing the rest. |
| Models and data | Prove which model and dataset you used. |
| AI agents | Any agent recorded from outside: commands, file changes, connections. |
| Extra checks | AI code review and paper comparison (advisory). |
| What it does not prove | The limits. |