Module temporal Roadmap

Navigation: Home > Modules

Temporal Module Roadmap

Current Status

Production-capable temporal runtime exists for temporal/bitemporal querying, system-versioned behavior, retention/snapshot lifecycle, and temporal indexing/CDC/compression paths.

In Progress

• [~] hardening edge-case behavior under concurrent bitemporal write/query pressure (Target: Q3 2026)
• [~] improving diagnostics consistency across query/lifecycle/conflict stages (Target: Q3 2026)
• [~] stabilizing benchmark-backed release guardrails for temporal hot paths (Target: Q3 2026)

Planned Features

Short-term (3-6 months)

• tighten deterministic behavior under retention and snapshot stress conditions (Target: Q4 2026) — evidence: tests/temporal/test_temporal_highcardinality_stress.cpp (TSTR-01)
• expand stress coverage for conflict-resolution and CDC edge scenarios (Target: Q4 2026) — evidence: tests/temporal/test_temporal_highcardinality_stress.cpp (TSTR-02..03)
• improve operator-facing diagnostics for temporal lifecycle incidents (Target: Q4 2026) — evidence: docs/operability/RUNBOOK_TEMPORAL_STORE.md

Mid-term (6-12 months)

• [~] re-baseline p95/p99 envelopes for temporal query and history retrieval paths (Target: Q1 2027)
• broaden benchmark depth for advanced temporal workload shapes (Target: Q1 2027) — evidence: benchmarks/temporal/bench_temporal_dedicated_gates.cpp (TMP-BM-01..04)
• harden long-run reliability under sustained temporal mutation/query traffic (Target: Q1 2027) — evidence: tests/integration/test_temporal_store_soak.cpp (TemporalSoak_HistoryQueryThroughput, TemporalSoak_SnapshotStability, TemporalSoak_CDCReliability)

Implementation Phases

Phase 1: Design / API Contract

• freeze temporal query/version contracts for current major line (Completed 2026-07-29)
• define explicit error taxonomy for temporal lifecycle incident classes (Completed 2026-07-29)

Phase 2: Core Implementation

• complete hardening for bitemporal/query and lifecycle internals (Target: Q4 2026) — evidence: tests/temporal/test_temporal_highcardinality_stress.cpp
• align CDC/compression/tiering behavior to bounded runtime contracts (Target: Q4 2026) — evidence: TSTR-03 CDC edge-case stress

Phase 3: Error Handling and Edge Cases

• standardize fail-safe behavior for snapshot, retention, and conflict faults (Target: Q4 2026) — evidence: docs/operability/RUNBOOK_TEMPORAL_STORE.md
• unify diagnostics across query, lifecycle, and CDC incident classes (Target: Q4 2026) — evidence: RUNBOOK_TEMPORAL_STORE.md alert→runbook mapping

Phase 4: Tests

• expand focused regressions for temporal query, snapshot, and retention edge scenarios (Completed 2026-07-29 — test_temporal_contract_hardening_focused.cpp, TCH-01..TCH-16)
• extend deterministic stress fixtures for concurrent temporal workloads (Completed 2026-07-29)

Phase 5: Performance and Hardening

• lock benchmark-backed release gates for temporal hot paths (Completed 2026-07-29 — bench_temporal_release_gates.cpp, TRG-01..TRG-06)
• validate p95/p99 and throughput behavior against release baselines (Target: Q4 2026) — evidence: benchmarks/temporal/bench_temporal_dedicated_gates.cpp (TMP-BM-01..04)

Phase 6: Documentation and Acceptance

• core temporal module docs aligned to source-verifiable behavior
• roadmap/future planning separated from historical changelog entries
• temporal_api_contract.h frozen contract header published (Completed 2026-07-29)

Production Readiness Checklist

• core temporal surfaces documented and source-verified
• module-level security and failure behavior documented
• benchmark mapping documented in performance expectations
• temporal_api_contract.h frozen contract header (Phase 1 closure, 2026-07-29)
• test_temporal_contract_hardening_focused.cpp — TCH-01..TCH-16 (Phase 4 closure, 2026-07-29)
• bench_temporal_release_gates.cpp — TRG-01..TRG-06 gate benchmarks (Phase 5 closure, 2026-07-29)
• remaining hardening tasks closed for temporal lifecycle edge paths — evidence: tests/temporal/test_temporal_highcardinality_stress.cpp
• release benchmark stabilization complete — evidence: benchmarks/temporal/bench_temporal_dedicated_gates.cpp

Known Issues and Limitations

• runtime behavior depends on temporal workload shape and retention/snapshot configuration.
• selected lifecycle and conflict edge scenarios need continued hardening.
• benchmark depth should continue expanding for advanced temporal workloads.

Breaking Changes

No breaking temporal contract planned. Any contract-breaking change requires migration notes and changelog entry before merge.

Program Execution Model — Wave Context

This module is a contributing module in the program-level Wave A → B → C → D execution model. It does not own a primary wave deliverable but must remain release_critical-green throughout all waves and must deliver Wave D operability improvements in Q1 2027. See ../../ROADMAP.md for the full wave model and exit criteria.

Wave D Contribution for temporal

• Deliver or validate distributed tracing, high-cardinality stress coverage, exporter reliability, and operator remediation hints as applicable to this module (Target: Q1 2027) — evidence: tests/temporal/test_temporal_highcardinality_stress.cpp, docs/operability/RUNBOOK_TEMPORAL_STORE.md
• Contribute to or validate long-duration soak test coverage for this module's primary paths (Target: Q1 2027) — evidence: tests/integration/test_temporal_store_soak.cpp (TemporalSoak_HistoryQueryThroughput, TemporalSoak_SnapshotStability, TemporalSoak_CDCReliability)
• Ensure runbook coverage for operator-critical scenarios in this module (Target: Q1 2027) — evidence: docs/operability/RUNBOOK_TEMPORAL_STORE.md (5 scenarios, log patterns [TEMPORAL:SnapshotFailed], [TEMPORAL:RetentionViolation], [TEMPORAL:CDCLag], [TEMPORAL:ConflictStorm])

Cross-Wave Requirements

• release_critical CI must remain green on develop throughout all waves (Target: ongoing)
• p95/p99 benchmarks must be refreshed on representative hardware before Wave D sign-off (Target: Q1 2027)
• No behavioral regression may be introduced into modules in Wave A/B/C scope from changes in this module.

Program-Level Success Criteria (contribution)

• This module's distributed/acceleration paths fail closed (Target: Q1 2027) — evidence: snapshot fail-closed, retention sweep bounded
• [~] Benchmark-backed p95/p99 baselines exist on representative hardware (Target: Q1 2027)
• Operator-critical paths have diagnostics, alerts, and runbooks (Target: Q1 2027) — evidence: docs/operability/RUNBOOK_TEMPORAL_STORE.md

---

ThemisDB 1.9.0-beta · Home · Module-Index · GitHub · Issues