audit-core/SCOPE.md
tegwick 5d46723d4e
All checks were successful
CI Smoke / host-smoke (push) Successful in 0s
CI Smoke / container-smoke (push) Successful in 0s
Cut over AUDIT-WP-0006 image and add AUDIT-WP-0007.
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.
2026-08-16 00:57:59 +02:00

1.4 KiB

SCOPE

This file was generated by statehub register. Refine it as the repository boundaries become clearer.

One-liner

Reliable multi-tenant auto setup audit capability.

Core Idea

audit-core exists to provide the capability described in INTENT.md.

In Scope

  • Maintain the repository's primary implementation.
  • Keep docs, tests, and operational metadata current.
  • Operational audit custody (operations.audit) and its declared recovery bound.

Out of Scope

  • Own unrelated adjacent systems.
  • Make irreversible operational decisions without human approval.
  • Procuring or operating S3 / Barman / WAL.
  • Booked cost or a second usage stream for platform:audit-storage.
  • A rapp.yaml in this repo (schema requires rapp-*).
  • Public ingest.

Current State

  • Status: production
  • 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). 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. tamper_evidence is still false.
  • Open workplan: workplans/AUDIT-WP-0007-integrity-verification.md.

Getting Oriented

  • Start with: INTENT.md
  • Agent instructions: AGENTS.md
  • Workplans: workplans/