docs: add service README.md files + update AGENTS.md decisions
- Create README.md for 25+ service modules with container info, API surface, storage - Document attestor-tileproxy separation rationale (air-gap network isolation) - Document opsmemory-advisoryai separation rationale (resource isolation, blast radius) - Update Timeline AGENTS.md with merged indexer info Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
This commit is contained in:
17
src/EvidenceLocker/README.md
Normal file
17
src/EvidenceLocker/README.md
Normal file
@@ -0,0 +1,17 @@
|
||||
# EvidenceLocker
|
||||
|
||||
**Container(s):** stellaops-evidence-locker-web, stellaops-evidence-locker-worker
|
||||
**Slot:** 6 | **Port:** 8080 | **Consumer Group:** evidencelocker
|
||||
**Resource Tier:** light
|
||||
|
||||
## Purpose
|
||||
The Evidence Locker provides write-once, tamper-evident storage for release evidence artifacts (scan results, attestations, policy verdicts, approval records). It supports optional cryptographic signing (ES256), quota enforcement, snapshot queries, and multi-material evidence bundles. The worker handles background evidence processing tasks.
|
||||
|
||||
## API Surface
|
||||
- `evidencelocker` (via Router) — evidence material upload (write-once), retrieval, snapshot queries, health checks, observability endpoints
|
||||
|
||||
## Storage
|
||||
PostgreSQL (via `EvidenceLocker:Database:ConnectionString`); file-system object store (`/data/evidence`) or configurable backend; Valkey for cache
|
||||
|
||||
## Background Workers
|
||||
- Evidence Locker worker — background evidence processing, integrity verification
|
||||
Reference in New Issue
Block a user