# Item 13 — restore proven end to end

Work record: architecture-cleanup `RAILIANCE-WP-0016` item 13
Date: 2026-08-15
Status: **done** (unblocked by `RESOURCE-WP-0002` finish)

The blocker was decision `9c21c0e0` / `RESOURCE-WP-0002`. That workplan is
finished. The restore this item asked for was executed as
`RESOURCE-WP-0002-T05` on 2026-08-14 and is still true on the live cluster.

## Production path (railiance01 `platform-pg`)

| Fact | Value |
| --- | --- |
| Destination | `s3://railiance-platform-pg-backup/platform-pg/` |
| Endpoint | `https://s3.nl-ams.scw.cloud` |
| Credential Secret | `databases/platform-pg-backup-s3` (keys present, values not read) |
| ScheduledBackup | `platform-pg-daily` (02:15 UTC) |
| Completed Backups | `platform-pg-daily-20260814181421`, `platform-pg-daily-20260815021500` |

Full restore 65s (`audit_core.events` 30=30). PITR 65s (`keep` present,
`destroy` absent). Evidence:
`resource-control/docs/evidence/RESOURCE-WP-0002-T05-restore-2026-08-14.md`.
Logical offsite copy: `RESOURCE-WP-0002-T06`.

This item is the S3-owned *proof*, not a second restore program. `apps-pg`
is still local-path only (RAILIANCE-WP-0016 apps-pg evidence T02). Covering
that cluster is a later consumer of the same bucket, not a re-opening of
item 13.