Documentation / Advanced
Separate hot state and retained history
Committed-transition accounting, regional event streams, analytics and archives serve different purposes.
Trace a committed transition
CDC captures authoritative committed transitions. Regional stream capacity mode, deduplication and ordering affect delivery and cost. An emitted event alone is not a second billable transition.
rippflow analytics watermarks --jsonCheck projection freshness
Rollups and sparse indexes are projections. Compare their watermarks with execution truth before using them for operations. Provisioned and on-demand Kinesis are different deployment/cost contracts.
rippflow analytics rollups --granularity 1h --json
rippflow analytics freshness --jsonReview retention before deleting
Parquet/S3 cohorts need verified manifests/receipts and restart-safe compaction. Active waits, approvals, legal holds, replay tombstones and restore requirements can block expiry. A retention proposal or eligibility result is not deletion authorization; approved owning-stack execution is separate.
rippflow retention get --jsonReconcile instead of guessing
Committed-transition identities prevent duplicate billing across retries/recovery. Scope accounting to the installation/team/project and compare authoritative, projected and billable quantities.
rippflow accounting report --scope installation --id INSTALLATION_ID --json
rippflow accounting reconcile --scope installation --id INSTALLATION_ID --jsonUnmerged endurance changes
Controller PR 53 proposes preserving waiting human approvals in the sparse index and a 72-hour exit report. It is not pinned-main behavior or a contractual uptime guarantee.
Verified sources
Checked 2026-11-05.
- transition_capture.rs 04cb082 · main
- regional_streaming.rs 04cb082 · main
- analytics.rs f6c7970 · main
- retention.rs f6c7970 · main
- transition_accounting.rs 04cb082 · main