stella-ops.org/git.stella-ops.org
1
0
Fork 0
Code Issues Pull Requests Actions 16 Releases Wiki Activity
Files
d519782a8f0b30f425c9b6ae0f316b19259972a2
git.stella-ops.org/docs/modules/evidence-locker/prep/2025-11-20-replay-delivery-sync.md
master d519782a8f
Some checks failed
Docs CI / lint-and-preview (push) Has been cancelled
Details
prep docs and service updates
2025-11-21 06:56:36 +00:00

2.1 KiB
Raw Blame History

Replay Delivery Coordination Prep — PREP-EVIDENCE-LOCKER-GUILD-REPLAY-DELIVERY-GU

Status: Draft (2025-11-20) Owners: Planning · Evidence Locker Guild · Replay Delivery Guild · CLI Guild Scope: Define minimum contract notes for replay delivery so EVID-REPLAY-187-001/002 and RUNBOOK-REPLAY-187-004 can move once schemas freeze.

Ledger & delivery contract (draft)

  • Ingress API stub: POST /replay/records (internal) accepting NDJSON of replay record envelopes (see docs/modules/evidence-locker/replay-payload-contract.md).
  • Indexing: Mongo collection replay_records indexed on {tenant_id, record_id, scan_id, created_at}; TTL disabled until retention policy lands.
  • Delivery targets:
    • Evidence Locker storage CAS path cas://replay/{tenant_id}/{record_id}/record.ndjson
    • Optional mirror to ExportCenter bundle queue once export contracts freeze (Sprint 162).
  • Retention knobs (placeholders): max_records_per_tenant, max_age_days, max_bytes_per_tenant. Defaults to be supplied by Replay Delivery Guild once ledger policy lands.

Coordination points

  • Replay Delivery Guild to publish retention defaults + eviction order alongside ledger spec; reference back here once available.
  • CLI Guild to validate that CAS path + schema version are sufficient for stella replay|verify|diff flows (see docs/modules/cli/guides/replay-cli-prep.md).
  • Ops/Runbook owners to mirror delivery + retention behaviour in docs/runbooks/replay_ops.md when promoted.

Open questions to close before DOING

  • Final subject keys for CAS path (include source or keep tenant/record only?).
  • Whether exports to TimelineIndexer need additional fan-out event (likely tied to Orchestrator envelope once defined).
  • Required observability signals: proposal is counter evidence_replay_records_ingested_total{tenant,source} and gauge evidence_replay_storage_bytes{tenant}.

Handoff

Treat this as the PREP artefact for PREP-EVIDENCE-LOCKER-GUILD-REPLAY-DELIVERY-GU. Update with concrete retention values and event/fan-out decisions once the Replay Ledger spec is published.