coulomb/audit-core
4
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

Finish AUDIT-WP-0005: walk restore and close T06
All checks were successful
CI Smoke / host-smoke (push) Successful in 0s
Details
CI Smoke / container-smoke (push) Successful in 1s
Details

Browse source 
Logical dump of live audit_core restored locally in 4.1s; counts and
sample triples match the rapp-postgres drill. Retention is platform
backup, not an audit-core deletion window. Workplan finished.
This commit is contained in:
tegwick 2026-08-13 14:14:22 +02:00
parent f30faec660
commit c4dbb92a8a
4 changed files with 85 additions and 48 deletions
Download patch file Download diff file Expand all files Collapse all files

21
workplans/AUDIT-WP-0005-postgres-store-and-production-deployment.md
View file

@ -4,7 +4,7 @@ type: workplan
title: "Deploy audit-core on Railiance with durable Postgres custody"
domain: infotech
repo: audit-core
status: active
status: finished
owner: codex
topic_slug: netkingdom
created: "2026-08-10"
@ -469,7 +469,7 @@ locked in migration 0005. That JSON is the NK-WP-0024 hand-back.
```task
id: AUDIT-WP-0005-T06
status: progress
status: done
priority: medium
state_hub_task_id: "0856c80d-abe1-4bff-ba8d-87295cf76819"
```
@ -492,9 +492,14 @@ rotation, `/readyz` vs `/healthz` vs `/v1/stats`, and rollback.
`python -m audit_core replay` is the operator surface that WP-0004
deliberately left off HTTP.
Restore is written down and is **not** walked. rapp-postgres T06 is `wait`
on an S3 Barman target; the Nextcloud logical-dump lane cannot provide WAL
or PITR; physical restore is instance-wide. audit-core currently declares
no finite `retention_days`, so it does not outrun a platform window that
does not yet exist — but it also cannot promise an RPO until the platform
drills land. The walk listed in the runbook is what closes this task.
Closed 2026-08-13. rapp-postgres T06 is done. Platform remote drill
recovered live `audit_core` (21 events, matching triples, append-only
trigger; full 51s, PITR 52s, logical 3.5s). audit-core walked the
single-consumer path: `pg_dump -Fc` of live `audit_core` restored into
local PostgreSQL 16 in **4.1s**; counts 21/3/1, five triples match the
platform sample, trigger present.
`evidence/restore-walk-20260813T121200Z.json`.
Retention check: audit-core does not delete events. Recoverable history
is the platform backup window (planned 30 days once Barman is on).
Production Barman is still fail-closed — no off-host RPO is claimed.