---
id: SCR-PFM-LLM-005
title: Rhythm HQ AI request detail
route: '/hq/aiUsage/requests/{tenantId}/{invocationId}'
surface: console
product_area: platform
module: llm
revision: 1
status: draft
design_intent: proposed
implementation_evidence: observed
inference: []
source_sha:
  react-console: baf6dae382d6f41dce976c7f848667ccc37e076f
  services-platform: ad3f6a6582843008ed0f5a17b131878d15829af1
purpose: 'Inspect a request’s routing, attempts, outcome, charge and explanation without opening its captured text.'
supports:
  - JNY-PFM-LLM-002
  - CAP-PFM-LLM-011
  - CAP-PFM-LLM-012
  - CAP-PFM-LLM-016
  - CAP-PFM-LLM-018
permission: >-
  hq.llm-usage.read; reading content would also need hq.llm-usage.read-evidence and an active staff access
  grant
entry_from:
  - SCR-PFM-LLM-004
  - SCR-PFM-LLM-007 (recent refusals and failures)
  - SCR-PFM-LLM-006 (a task's requests)
exits_to:
  - SCR-PFM-LLM-004
  - SCR-PFM-LLM-006
displays:
  - field: Request and caller attribution
    source: getHqTenantLlmUsageInvocation
  - field: 'Requested routing, prompt and pricing-version metadata'
    source: getHqTenantLlmUsageInvocation
  - field: Reported units and settlement charges
    source: getHqTenantLlmUsageInvocation
  - field: Ordered provider attempts and truncation indication
    source: getHqTenantLlmUsageInvocation
  - field: Readable outcome and failure classification
    source: getHqTenantLlmUsageInvocation
  - field: Retained refusal explanation or failed-attempt analysis
    source: explainHqTenantLlmUsageInvocation
  - field: Console presentation of request and response capture availability
    source: getHqTenantLlmUsageInvocation
actions:
  - label: Read request / Read response
    operation_id: getHqTenantLlmUsageInvocationEvidence (not wired; the buttons are disabled)
    permission: hq.llm-usage.read-evidence
    confirm: false
  - label: Back to AI Usage Requests
    operation_id: 'none: navigation'
    permission: hq.llm-usage.read
    confirm: false
states:
  - 'loading: request detail is pending'
  - 'not found: organization or scoped request is unavailable'
  - 'error: detail and explanation offer their respective retry'
  - 'read-only: capture inspection is available but body controls remain disabled'
  - 'permission denied: request data is withheld'
validation:
  - BR-CAP-PFM-LLM-011-06
  - BR-CAP-PFM-LLM-011-07
  - BR-CAP-PFM-LLM-012-01
  - BR-CAP-PFM-LLM-016-06
  - BR-CAP-PFM-LLM-016-07
  - BR-CAP-PFM-LLM-018-10
patterns:
  - Standard layout with page header and back link
  - HQ cards with card headers and card states
  - 'Explanation blocks (policy, state, changes) in product words'
component: components/console/hq/ai-usage/ai-usage-request-detail.tsx and request/*
evidence:
  - >-
    react-console at baf6dae: app/(console)/hq/aiUsage/requests/[tenantId]/[invocationId]/page.tsx;
    components/console/hq/ai-usage/ai-usage-request-detail.tsx; request/identity-card.tsx, routing-card.tsx,
    usage-card.tsx, attempts-card.tsx, outcome-card.tsx, explain-panel.tsx, evidence-card.tsx;
    lib/hq/ai-usage.ts, ai-usage-format.ts, permissions.ts, staff-roles.ts.
controls: [TC-AI-006, TC-AI-007, TC-AVL-001, TC-AVL-004, TC-AVL-005, TC-AZ-001, TC-AZ-002, TC-AZ-003, TC-AZ-004, TC-AZ-005, TC-AZ-006, TC-CRY-001, TC-CRY-002, TC-CRY-003, TC-CRY-004, TC-DAT-001, TC-DAT-002, TC-DAT-003, TC-DAT-004, TC-IAM-001, TC-IAM-002, TC-IAM-003, TC-IAM-004, TC-IAM-005, TC-IAM-006, TC-LOG-001, TC-LOG-002, TC-LOG-003, TC-LOG-004, TC-LOG-005, TC-MON-001, TC-PI-001, TC-PI-002, TC-PI-003, TC-PI-004, TC-PI-005, TC-PRV-001, TC-PRV-002, TC-TEN-001, TC-TEN-002, TC-TEN-003, TC-VEN-001, TC-VEN-002, TC-VEN-003]
---

# 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.