Evidence from your pipelines
Send validation reports, bias tests, model cards and approvals to V77 the moment they're produced, so evidence is never collected by hand before an audit.
Upload
POST /evidence takes multipart/form-data with the file (up to 25 MB) and, optionally, the system and the control it supports.
curl https://v77trust.com/api/v1/evidence -H "Authorization: Bearer $KEY" \
-F file=@reports/fairness-v3.2.html \
-F title="Fairness report v3.2" \
-F systemId=$SYSTEM_ID \
-F controlCode=V77-FAIR-01Tamper evidence
Each file is SHA-256 hashed on upload, and each item records the hash of the one before it (prevSha256), forming a chain. Download a file with GET /evidence/{id}/content: the X-V77-SHA256 header carries the hash recorded at upload, so auditors can check the file hasn't changed.
curl -sS -D headers.txt -o file.bin https://v77trust.com/api/v1/evidence/$EVIDENCE_ID/content -H "Authorization: Bearer $KEY"
grep -i x-v77-sha256 headers.txt
sha256sum file.binCommon evidence by control area
| Area | Artefacts |
|---|---|
| Risk management (Art. 9) | Risk register, risk acceptance sign-off |
| Data governance (Art. 10) | Datasheets, data lineage, bias analysis |
| Technical documentation (Art. 11) | Model card, architecture, training procedure |
| Record-keeping (Art. 12) | Logging configuration, retention policy |
| Human oversight (Art. 14) | Operator procedures, override logs |
| Accuracy & robustness (Art. 15) | Validation reports, red-team results, drift monitoring |