These examples show the type of proof object institutional reviewers may request in protected diligence. They are illustrative redacted templates, not live commitments, certifications, operational logs or deployment-specific artefacts.
Shows how a deployment-specific SLA may define availability, support, maintenance and escalation bands.
| Availability band | Deployment-specific target to be contractually agreed. |
| Support response | Severity-based response windows with named escalation route. |
| Maintenance | Scheduled maintenance with prior notice and change log. |
Shows the minimum evidence a reviewer would expect from backup and restore testing.
| Test date | Redacted. |
| Restore scope | Application, storage, audit and evidence records where applicable. |
| RPO/RTO result | Compared against deployment-specific contractual bands. |
Shows how a committee pack should preserve state at time of export.
| Snapshot ID | Versioned export reference. |
| Evidence basis | Linked evidence objects, reviewer actions, conditions and unresolved risks. |
| Reproducibility | Snapshot remains reconstructable after later record changes. |
Public proof-object examples are not reliance evidence. Formal reliance requires protected, deployment-specific artefacts, contractual commitments and independent evidence where required by the institutional review route.