Rhythm HQ AI request detail
What the Screen Is For
Support opens one request to trace its caller, operation, provider attempts and settlement.
What It Shows and Lets People Do
Separate cards display identity, routing, usage, attempts and outcome. The explanation panel appears for refused or failed presentation status and distinguishes decision-time figures from current conditions. The evidence card uses console capture labels and shows disabled privileged read buttons; the backend content operation remains unwired.
States and Errors
The page distinguishes loading, unavailable records, retryable errors and permission denial. Explanation can fail independently of detail. Missing organization or foreign request produces not found through the scoped service.
Patterns It Must Respect
The existing HQ cards use PageLayout, the detail header and a back link. Future content wiring must retain permission, eligible-grant and audit checks.