coulomb/audit-core
4
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions
audit-core/SCOPE.md
tegwick ded432a63f
All checks were successful
CI Smoke / host-smoke (push) Successful in 0s
Details
CI Smoke / container-smoke (push) Successful in 2s
Details
Implement AUDIT-WP-0006 honest operational custody. 
Postgres now reports custody_class=operational with a cited 30-day
recoverable window. Join ITC-CAP operations.audit at D4, publish the
interface card, and overlay user-engine tenants [*] from Git so an
ExternalSecret refresh cannot shrink it.
2026-08-16 00:24:33 +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, RESOURCE-WP-0002 live). Manifest /readyz reports custody_class=operational and recoverable_days=30 once the AUDIT-WP-0006 image is pinned.
  • ITC-CAP case: data/capability/audit-core-operational.json. data.archive is an unmet requirement.
  • AUDIT-WP-0001…0006 closed. No open workplan.

Getting Oriented

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