Rhythm 2.0 Specifications

Appearance

ATS-PFM-LLM-016Inspect captured AI content with a live access grant: Capability Test Specification

Markdown

ATS-PFM-LLM-016

Inspect captured AI content with a live access grant: Capability Test Specification

Markdown
  • DocumentProposed

Planning

Proves capability
CAP-PFM-LLM-016

Design

Executed by
TST-PFM-LLM-024, TST-PFM-LLM-054, TST-PFM-LLM-073

KindAcceptance test setProduct areaPlatformModuleAI Requests, Usage and the Jazz AI TeammateRevision2

Read atservices-platform ad3f6a65react-console baf6dae3

Inspect captured AI content with a live access grant: Capability Test Specification ​

Coverage ​

RuleScenario
BR-CAP-PFM-LLM-016-01ATS-PFM-LLM-016-01
BR-CAP-PFM-LLM-016-02ATS-PFM-LLM-016-01
BR-CAP-PFM-LLM-016-03ATS-PFM-LLM-016-02
BR-CAP-PFM-LLM-016-04ATS-PFM-LLM-016-03
BR-CAP-PFM-LLM-016-05ATS-PFM-LLM-016-04
BR-CAP-PFM-LLM-016-06ATS-PFM-LLM-016-05

The interaction register links concrete experiments with retain redacted ai evidence and remove it safely; inspect an organization’s ai account and request history. Each experiment checks the outcome at the shared boundary; an unbound experiment remains proposed.

Route authorization, invalid body kinds, failed audit, malformed stored content and access revocation during storage reads need explicit HTTP and timing proof. Console content reads remain disabled.

Coverage

  • Rule gap: FND-PFM-LLM-075
  • Transition not-applicable
  • Validation gap: FND-PFM-LLM-075
  • Permission covered
  • Edge covered
  • Failure gap: FND-PFM-LLM-075
  • Boundary covered
  • Concurrency gap: FND-PFM-LLM-075
  • Invariant gap: FND-PFM-LLM-075
  • Interaction covered

Test Scenarios

6 scenarios proving CAP-PFM-LLM-016; 6 bound to an existing test.

01 Content access requires a live eligible grantpermissionapinegativetest
Proves
BR-CAP-PFM-LLM-016-01 BR-CAP-PFM-LLM-016-02
Preconditions
Staff have the content key with either no eligible grant or a grant that later expires.
Steps
Read before and after the grant window.
Expected
Eligible access returns inside the window, while missing and expired grants produce audited refusals.
Data
Fixtures representing staff have the content key with either no eligible grant or a grant that later expires.
Bound to
Source
services-platform:modules/llm/tests/integration/services/evidence/evidence-access.integration.spec.js#refuses a staff member holding no grant into the tenant, 403
02 Handled content reads have content-free audit eventsinvariantapitest
Proves
BR-CAP-PFM-LLM-016-03
Preconditions
A staff reader has a grant for successful reads and none for a refusal.
Steps
Read a body twice and perform the missing-grant attempt.
Expected
Three events retain caller, request, body kind, grant where eligible and outcome without the body.
Data
Fixtures representing a staff reader has a grant for successful reads and none for a refusal.
Bound to
Source
services-platform:modules/llm/tests/integration/services/evidence/evidence-access.integration.spec.js#writes one audit row for a read, saying who read which body of which invocation under which grant
03 Unavailable bodies return their statusedgeapitest
Proves
BR-CAP-PFM-LLM-016-04
Preconditions
Bodies are skipped, failed or purged, with another captured object missing from storage.
Steps
Read each body.
Expected
The statuses are skipped, failed and purged as applicable, and noncaptured statuses avoid storage reads.
Data
Fixtures representing bodies are skipped, failed or purged, with another captured object missing from storage.
Bound to
Source
services-platform:modules/llm/tests/integration/services/evidence/evidence-access.integration.spec.js#answers the status of a body that was skipped without touching the bucket
04 Not-found content follows eligible accessboundaryapinegativetest
Proves
BR-CAP-PFM-LLM-016-05
Preconditions
A reader has a valid grant for a foreign request and separately requests a nonexistent organization.
Steps
Read both references.
Expected
Not-found responses create no content-read audit event.
Data
Fixtures representing a reader has a valid grant for a foreign request and separately requests a nonexistent organization.
Bound to
Source
services-platform:modules/llm/tests/integration/services/evidence/evidence-access.integration.spec.js#answers 404 for an invocation the tenant does not have, and writes no row for it
05 Reader policies omit content authoritypermissionunittest
Proves
BR-CAP-PFM-LLM-016-06
Preconditions
The HQ reader policy and evidence route declaration are available.
Steps
Inspect their requirements.
Expected
The reader has no management or evidence key and the route requires the sensitive content key.
Data
Fixtures representing the HQ reader policy and evidence route declaration are available.
Bound to
Source
services-platform:modules/llm/tests/unit/aws/api/llm-usage-permissions.spec.ts#gives the HQ reader policy neither the manage key nor the evidence key
06 Standing access cannot authorize contentpermissionunitnegativetest
Proves
BR-CAP-PFM-LLM-016-01
Preconditions
The suite owns isolated fixtures representing the valid control and the contrasting case described by its steps.
Steps
Evaluate active approved, emergency and standing access grants.
Expected
Only the two eligible grant kinds authorize captured content inside their windows.
Data
Suite-owned fixtures, with a fixed clock where dates or grant windows matter.
Bound to
Source
services-platform:modules/llm/tests/unit/services/evidence/evidence-access.spec.ts#does not admit standing access, which is broad access for Rhythm’s administrators and not a reason to read a prompt

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.

Rhythm Software