tegwick
5433562d7a
Review of info-tech-canon 0.6.0, resource-control, fin-hub, and railiance-master found production still claims archive custody after the platform backup and ITC-CAP catalog made that claim false.
38 lines
1.1 KiB
Markdown
38 lines
1.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. AUDIT-WP-0001…0005 finished.
|
|
- 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/
|