1.9 KiB
1.9 KiB
Findings Ledger Implementation Plan
Purpose
Define the delivery plan for the Findings Ledger service, replay harness, observability, and air-gap provenance so audits can verify deterministic state reconstruction.
Active work
- No active sprint tracked here yet. Use
docs/modules/findings-ledger/gaps-FL1-FL10.mdfor remediation tracking.
Near-term deliverables
- Observability baselines: metrics, logs, traces, dashboards, and alert rules per
docs/modules/findings-ledger/observability.md. - Determinism harness: replay CLI, fixtures, and signed reports per
docs/modules/findings-ledger/replay-harness.md. - Deployment collateral: Compose/Helm overlays, migrations, and backup/restore runbooks per
docs/modules/findings-ledger/deployment.md. - Provenance extensions: air-gap bundle metadata, staleness enforcement, and sealed-mode timeline entries per
docs/modules/findings-ledger/airgap-provenance.md.
Dependencies
- Observability schema approval for metrics and dashboards.
- Orchestrator export schema freeze for provenance linkage.
- QA lab capacity for >=5M findings/tenant replay harness.
- DevOps review of Compose/Helm overlays and offline kit packaging.
Evidence of completion
src/Findings/StellaOps.Findings.Ledgerandsrc/Findings/tools/LedgerReplayHarnessupdated with deterministic behavior and tests.- Replay harness reports (
harness-report.json+ DSSE) stored under approved offline kit locations. - Dashboard JSON and alert rules committed under
offline/telemetry/dashboards/ledgerorops/devops/findings-ledger/**. - Deployment and backup guidance validated against
docs/modules/findings-ledger/deployment.md.
Reference docs
docs/modules/findings-ledger/schema.mddocs/modules/findings-ledger/replay-harness.mddocs/modules/findings-ledger/observability.mddocs/modules/findings-ledger/deployment.mddocs/modules/findings-ledger/airgap-provenance.mddocs/modules/findings-ledger/workflow-inference.md