coulomb/audit-core
4
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions
audit-core/SCOPE.md
tegwick 61214bc24a
All checks were successful
CI Smoke / host-smoke (push) Successful in 0s
Details
CI Smoke / container-smoke (push) Successful in 1s
Details
Close AUDIT-WP-0007 after live chain attestation. 
Migration 0006 applied on railiance01. Verify-against the dated
chain-head evidence is intact for 30 events.
2026-08-16 01:23:54 +02:00

1.4 KiB
Raw Blame History

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). Live /readyz reports custody_class=operational, tamper_evidence=true, recoverable_days=30 (image sha256:7febc28e…).
  • Hash chain verified on 30 live events (docs/evidence/chain-head-20260816.json).
  • ITC-CAP case: data/capability/audit-core-operational.json at D4. data.archive is an unmet requirement.

Getting Oriented

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