audit-core/SCOPE.md
tegwick 91860cc609
All checks were successful
CI Smoke / host-smoke (push) Successful in 0s
CI Smoke / container-smoke (push) Successful in 2s
Clarify SCOPE current-state status line for C-30.
The status field cannot contain the word finished while an open
workplan exists.
2026-08-15 20:46:18 +02:00

38 lines
1 KiB
Markdown

# 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.
## Out of Scope
- Own unrelated adjacent systems.
- Make irreversible operational decisions without human approval.
## Current State
- Status: active
- Production receiver on railiance01 (`namespace audit-core`), Postgres
append-only store on `platform-pg`, sender `user-engine`.
- Recovery is the platform `data.backup` window (30 days, RESOURCE-WP-0002
live), not an audit-core deletion window. Production still reports
`custody_class=archive`; AUDIT-WP-0006 is the honesty/canon-join pass.
- Open workplan: `workplans/AUDIT-WP-0006-honest-custody-and-canon-join.md`.
## Getting Oriented
- Start with: INTENT.md
- Agent instructions: AGENTS.md
- Workplans: workplans/