fdf95e0f46
- API_CLI_REFERENCE.md, INSTALL_GUIDE.md, quickstart.md, architecture/integrations.md, dev/DEV_ENVIRONMENT_SETUP.md, integrations/LOCAL_SERVICES.md: reflect real-service wiring. - docs/modules/**: module dossier updates across the modules touched by SPRINT_20260415_001..007 + SPRINT_20260416_003..017 + SPRINT_20260417_018..024 + SPRINT_20260418_025 + SPRINT_20260419_026. - docs/features/checked/web/**: update feature notes where UI changed. - docs/qa/feature-checks/runs/web/evidence-presentation-ux/: QA evidence artifacts. - docs/setup/**, docs/technical/**: align with setup wizard contracts. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Timeline
Unified event timeline service with HLC-ordered queries, critical path analysis, and deterministic replay.
Purpose
Timeline is the query and presentation layer for cross-service event correlation and auditing. It provides Hybrid Logical Clock (HLC)-ordered event queries, critical path analysis for latency diagnosis, and deterministic replay capabilities. Timeline reads events that have been indexed by the separate TimelineIndexer module, serving as the read-side of the event timeline infrastructure.
Quick Links
Status
| Attribute | Value |
|---|---|
| Maturity | Production |
| Source | src/Timeline/ |
Key Features
- HLC-based causal event ordering
- Correlation ID queries
- Critical path analysis (latency stages)
- Service-filtered timeline views
- Event export and deterministic replay
Dependencies
Upstream
- Eventing infrastructure (StellaOps.Eventing) - event storage and indexing
- HybridLogicalClock library - causal timestamp generation and comparison
Downstream
- Platform - timeline views for operator dashboards
- CLI - event query commands
- Web - timeline UI components
- Replay - deterministic replay of event sequences
Note: Timeline is the query/presentation service. TimelineIndexer (separate module) handles event ingestion and indexing. They are independently deployable services.
Runtime Contract
- Outside
Testing, Timeline ingestion must have at least one real transport enabled:Ingestion:Nats:Enabled=trueorIngestion:Redis:Enabled=true. - The null ingestion subscriber is reserved for explicit test harnesses and is not a live fallback.