Skip to content

CAP-PFM-LLM-011Inspect an organization’s AI account and request history

Markdown

CAP-PFM-LLM-011

Inspect an organization’s AI account and request history

Markdown
  • DocumentDraft
  • Product intentProposed
  • ImplementationObserved

KindCapabilityProduct areaPlatformModuleAI Requests, Usage and the Jazz AI TeammateRevision1

Read atservices-platform ad3f6a65react-console baf6dae3

The Formal Contract

The narrative above explains; the sections below are authoritative — the rules, scenarios and tests this document binds.

Outcomes
Support inspects an organization’s AI position from HQ.Request details expose metadata and attempts separately from captured bodies.Control history retains limits, grants, corrections and notices.
Surfaces
consoleapi
Preconditions
An existing organization is selected.
Intent sources
services-platform:docs/milestones/plans/PLAT-M1-plan.md#4. Assumptions

Controls

35 controls apply, from the corpus control catalogue.

TC-AI-006 TC-AI-007 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-IAM-001 TC-IAM-003 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-003 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

Permissions

KeyChecked atScope
hq.llm-usage.readapiglobal
hq.llm-usage.readconsoleglobal
hq.llm-usage.manageconsoleglobal

Business Rules

12 rules, 8 to be proved before approval. A rule's product intent is derived from its origin: 0 confirmed by a product decision, the rest inheriting this capability's proposed.

IdRuleKindEnforced atProvenance
01must prove
Proposed
The HQ usage read key authorizes organization usage inspection for Rhythm staff, while a customer administrator cannot use that surface even for their own organization.
permissionapitest
services-platform:modules/llm/tests/e2e/llm-usage.e2e.spec.js#refuses a customer’s administrator a tenant’s usage even in their own tenant
02must prove
Proposed
Reads first resolve the named organization and scope its records accordingly, returning not found for nonexistent organizations or foreign requests and executions.
validationservice, databasetest
services-platform:modules/llm/tests/e2e/llm-usage.e2e.spec.js#answers 404 for a request of another tenant, the tenant policy binding the read
03must prove
Proposed
The overview independently reports the current allowance position, configured or default limits, active capacity, six recent periods, operation and model totals and twenty recent problem requests.
calculationserviceobserved
04must prove
Proposed
Historical periods evaluate capacity at their last instant and the current period evaluates it now; ended and revoked grants do not count as currently active.
calculationserviceobserved
05must prove
Proposed
The request directory is newest-first and supports period or date windows and operation, model, status, execution and caller filters, with at most one hundred rows per page and rejection of invalid filters or cursors.
validationapiobserved
06must prove
Proposed
Usage lists and details withhold captured bodies and storage references, exposing only their capture status.
invariantapi, service, consoleobserved
07
Proposed
Request detail identifies the caller, feature, routing, charge, ordered attempts, pricing versions, execution and any retained refusal figures.
policyapi, consoleobserved
08
Proposed
Organization execution lists include running tasks, and each detail pairs the task totals with its associated requests.
policyapiobserved
09must prove
Proposed
Grant lists order by newest start and derive scheduled, active, expired or revoked state at read time, optionally showing active grants only.
calculationservicetest
10
Proposed
Limit reads distinguish defaults from configuration and show ceilings, correction reads preserve signed values, and crossing reads expose delivery time, attempt count and recipient count.
policyapiobserved
11
Proposed
The AI audit trail filters this organization’s limit, grant, revocation, correction and content-read events and orders them newest-first.
policyserviceobserved
12must prove
Proposed
Support readers receive no usage action menu or write controls, while staff with management authority receive the action menu.
permissionconsoletest
react-console:e2e/mock/hq-ai-usage.mock.spec.ts#a Support Representative reads the card but has no action menu and no write controls

Scenarios

IdGivenWhenThenProvenance
01A limited organization is opened in HQ.Support reads its usage card.The card renders allowance and reset figures, default limits, history and refusals.test
react-console:e2e/mock/hq-ai-usage.mock.spec.ts#reads the limited organization: the warning band, the limits, the history and the refusals

The Markdown files under specs/ in rhythmsoftware/rhythm-v2-docs are the canonical source of truth. This reader is a generated, read-only projection of them.