---
id: TST-PFM-LLM-002
title: HQ browser Hq Ai Usage
kind: browser-lifecycle
product_area: platform
module: llm
revision: 1
status: draft
source_sha:
  react-console: baf6dae382d6f41dce976c7f848667ccc37e076f
repository: react-console
files:
  - e2e/mock/hq-ai-usage.mock.spec.ts
implements:
  - ATS-PFM-LLM-011-06
  - ATS-PFM-LLM-011-08
environment: mock
implementation_state: implemented
latest_result: not-run
latest_run_at: null
latest_run_ref: null
conformance: not-verified
estimated_minutes: 5
isolation: A browser context with fixture-backed HQ reads and independently configured staff role.
evidence:
  - provenance: test
    source: 'react-console:e2e/mock/hq-ai-usage.mock.spec.ts'
source_boundary:
  provenance: observed
  source: 'react-console:e2e/mock/hq-ai-usage.mock.spec.ts'
---

# HQ browser Hq Ai Usage

## Verification Boundary

The browser exercises HQ screens against fixture-backed responses.

## What This Suite Proves

Routine request reads keep content private. Console role controls remain distinct. Combined bindings require every named suite; a component assertion alone does not establish the full experiment.

## What It Does Not Prove

Mocked responses do not establish ledger agreement, model execution, delivered notices or customer isolation.

## Real Dependencies and Test Doubles

The browser and console rendering are real; HQ service responses and identities are fixtures.

## Must Not Be Doubled

Retain actual navigation, permission-driven controls and the displayed states under test. A deployed run must retain its real API reads.