Request Correlation Hardening

Status: Draft Date: 2026-03-07

Problem

Request correlation IDs are not consistently propagated across API handlers, wallet flows, ingestion, and usage logging.

Goal

Use one request correlation identifier end-to-end for backend observability and auditability.

Scope

• Middleware-to-handler propagation
• Downstream persistence in backend tables
• Response/error exposure
• Regression coverage

Open Questions

• Canonical field type for persisted request identifiers
• Correlation behavior for background jobs spawned from requests