The narrative above explains; the sections below are authoritative — the rules, scenarios and tests this document binds.
| # | Surface | Action | Capability | Expected | Provenance |
|---|---|---|---|---|---|
| 1 | getHqTenantLlmUsage | Inspect the organization’s usage position. | CAP-PFM-LLM-011 | The organization is stopped with its allowance committed. | test services-platform:modules/llm/tests/integration/services/usage-reports/tenant-usage.integration.spec.js#answers a hard stopped status at all of the allowance |
| 2 | previewHqTenantLlmUsageOverride | Preview a dated capacity grant. | CAP-PFM-LLM-014 | The preview computes the resulting position without saving or auditing a grant. | test services-platform:modules/llm/tests/e2e/llm-overrides.e2e.spec.js#previews the position with the override in force, writing and auditing nothing |
| 3 | grantHqTenantLlmUsageOverride | Submit the grant with its reason, ticket and requested notice. | CAP-PFM-LLM-014 | The service saves the grant and sends the restoration notice when applicable. | test services-platform:modules/llm/tests/integration/services/overrides/allowance-overrides.integration.spec.js#tells the organization’s administrators, saying until when |
| 4 | /console/{tenantId}/queries/new | Submit an AI request from the organization. | CAP-PFM-LLM-007 | Admission uses the additional capacity. | test services-platform:modules/llm/tests/integration/services/overrides/allowance-overrides.integration.spec.js#lets the ledger admit a call the base alone would refuse |
| 5 | revokeHqTenantLlmUsageOverride | Revoke the grant with a reason. | CAP-PFM-LLM-014 | The saved grant records revocation and ceases to provide capacity. | test services-platform:modules/llm/tests/e2e/llm-overrides.e2e.spec.js#revokes it, answering it as revoked with who and why |
| 6 | listHqTenantLlmUsageAudit | Read the AI control audit history. | CAP-PFM-LLM-011 | The grant and revocation appear with their reasons. | test services-platform:modules/llm/tests/e2e/llm-overrides.e2e.spec.js#audits the revocation as a non-widening action beside the grant |
| Path | From step | Condition | Path taken | Outcome | Provenance |
|---|---|---|---|---|---|
| alternate | 3 | The organization already has room for AI requests. | Save the grant without a restoration notice. | Capacity increases without an unnecessary restoration message. | test services-platform:modules/llm/tests/integration/services/overrides/allowance-overrides.integration.spec.js#sends nothing when the organization still had room, even if asked |
| failure | 3 | The combined allowance would exceed the ceiling. | Reject the proposed grant without saving it. | The administrator must propose a smaller grant or wait for reset. | test services-platform:modules/llm/tests/integration/services/overrides/allowance-overrides.integration.spec.js#refuses a grant that would take the allowance past the ceiling together with the override in force |
| failure | 3 | The same grant is submitted twice. | Each submission creates and audits a grant. | An administrator must revoke unintended duplicate capacity. | documented services-platform:docs/llm.md#Overrides |
| Id | Statement | Provenance |
|---|---|---|
01 | A grant admits a request that the base allowance would refuse. | test services-platform:modules/llm/tests/integration/services/overrides/allowance-overrides.integration.spec.js#lets the ledger admit a call the base alone would refuse |
02 | After revocation, admission no longer counts that grant. | test services-platform:modules/llm/tests/integration/services/overrides/allowance-overrides.integration.spec.js#stops the override applying to the next call |
03 | The audit history retains both control actions and their reasons. | test services-platform:modules/llm/tests/e2e/llm-overrides.e2e.spec.js#audits the revocation as a non-widening action beside the grant |
End-to-end policy: required: The service walkthrough has API evidence. A browser walkthrough is required when grant and revoke controls are enabled, including protection against duplicate submission.