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

Cut over AUDIT-WP-0006 image and add AUDIT-WP-0007.
All checks were successful
CI Smoke / host-smoke (push) Successful in 0s
Details
CI Smoke / container-smoke (push) Successful in 0s
Details

Browse source 
Live receiver now reports custody_class=operational with a cited
30-day recoverable window (sha256:05fe1c06). Next workplan is
integrity verification so tamper_evidence can become honest.
This commit is contained in:
tegwick 2026-08-16 00:57:59 +02:00
parent 40dcaddbf4
commit 5d46723d4e
6 changed files with 196 additions and 7 deletions
Download patch file Download diff file Expand all files Collapse all files

8
SCOPE.md
View file

@ -32,11 +32,11 @@ audit-core exists to provide the capability described in INTENT.md.
- Production receiver on railiance01 (`namespace audit-core`), Postgres
operational custody on `platform-pg`, sender `user-engine`.
- Recovery is the platform `data.backup` window (30 days, RESOURCE-WP-0002
live). Manifest `/readyz` reports `custody_class=operational` and
`recoverable_days=30` once the AUDIT-WP-0006 image is pinned.
live). Live `/readyz` reports `custody_class=operational` and
`recoverable_days=30` (image `sha256:05fe1c06…`, 2026-08-16 cutover).
- ITC-CAP case: `data/capability/audit-core-operational.json`.
`data.archive` is an unmet requirement.
- AUDIT-WP-0001…0006 closed. No open workplan.
`data.archive` is an unmet requirement. `tamper_evidence` is still false.
- Open workplan: `workplans/AUDIT-WP-0007-integrity-verification.md`.
## Getting Oriented