# 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.
- Tenancy posture: `tenancy.yaml` (NetKingdom Tenancy Posture v0.1 draft-8,
  Decision 5.4). Declared `I1 A2 E1 P1 R1`, target `E3` and `R2`. E is quoted
  at 1 although the E2 mechanism is in place on both paths — the §13 E2
  artifact is adversarial and does not exist yet (AUDIT-WP-0008-T05).

## Getting Oriented

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