# HyperTwist Phase 6R-AA first-party operator-facing provider usage/cost dashboard shell preparation packet

Created on `2026-05-25`

## Status

- first-party HyperTwist packet
- source-backed `Phase 6R-AA` preparation/control slice

## Purpose

This packet scopes the next bounded first-party slice above the landed speech
session, microphone-shell, payload-custody, provider-custody,
provider-routing, and normalized usage/cost event seams.

The granted slice is:

- first-party operator-facing provider usage/cost dashboard shell only

It is not:

- an actual billing or charge-settlement packet
- a usage/cost history export packet
- an actual payload-shipping packet
- a real device-permission workflow packet
- a native audio-device route ownership packet
- a provider-specific overlay packet
- a voice-output packet
- a broad assistant-platform packet

## Current authority basis

This control pass stands on:

- `docs/ops/HYPERTWIST_PROVIDER_NEUTRALITY_AND_BYOK_DOCTRINE_2026-05-21.md`
- `docs/arch/HYPERTWIST_PHASE6R_Z_FIRST_PARTY_NORMALIZED_USAGE_COST_EVENT_MODEL_IMPLEMENTATION_PACKET_2026-05-25.md`
- `docs/v6_5_deep_manual_pack/HyperTwist/ROADMAP.md`

The preserved owners do not change here:

- first-party HyperTwist remains the top-level provider/session owner
- first-party HyperTwist remains the usage/cost governance owner
- `ggml-org/whisper.cpp` remains bounded to offline STT donor seams
- `SYSTRAN/faster-whisper` remains bounded to complementary Python
  orchestration/service-lane seams

## Granted family

The bounded `Phase 6R-AA` slice may land:

1. first-party operator-facing usage/cost dashboard shell profile ids and
   definitions
2. dashboard issue and shell-state record shapes
3. session-config and companion-session-state expansion for those shapes
4. bounded capability exposure for:
   - `providerUsageCostDashboardShell`
   - `providerQuotaEscalationBanner`
   - `providerRouteCostDiagnostics`
5. focused automation for mock healthy posture and provider-backed fallback
   posture

The packet must stay out of:

- actual billing export, settlement, or invoice reconciliation
- actual payload download or redistribution ownership
- real device-permission workflow ownership
- native audio-device route ownership
- provider-specific dashboard skinning

## Proposed implementation shape

Land the narrower first-party boundary through:

- retained recognition contract types for:
  - usage/cost dashboard shell profile
  - dashboard issue
  - dashboard shell state
  - expanded speech session config
  - expanded companion speech session state
- contract-library defaults for:
  - dashboard shell profile ids and definitions
  - dashboard action bindings and panel ids
  - service-health capability exposure
- training-subsystem composition for:
  - provider summary posture
  - route diagnostics posture
  - usage and cost summary cards
  - quota escalation banner posture
  - provider-backed fallback issue posture
- direct speech-client health capability exposure for:
  - `providerUsageCostDashboardShell`
  - `providerQuotaEscalationBanner`
  - `providerRouteCostDiagnostics`

## Validation target

Validate with:

- Unreal build for `UnrealHyperTwistEditor Win64 Development`
- focused automation:
  - `HyperTwist.Permissive.WhisperCpp.Phase6R.AA`
- regressions:
  - `HyperTwist.Permissive.WhisperCpp.Phase6R.Z`
  - `HyperTwist.Permissive.WhisperCpp.Phase6R.Y`
  - `HyperTwist.Permissive.WhisperCpp.Phase6R.X`
  - `HyperTwist.Permissive.WhisperCpp.Phase6R.W`
  - `HyperTwist.Permissive.WhisperCpp.Phase6R.V`
  - `HyperTwist.Permissive.WhisperCpp.Phase6R.U`
  - `HyperTwist.Permissive.WhisperCpp.Phase6R.E`
  - `HyperTwist.Permissive.FasterWhisper.Phase6R.F`
  - `HyperTwist.Permissive.Piper.Phase6R.G`
  - `HyperTwist.Permissive.Coqui.Phase6R.H`
  - `HyperTwist.CleanRoom.CubeDesk`

## Queue effect

If this packet lands cleanly, the next bounded move becomes:

- a source-backed `Phase 6R-AB` first-party provider usage/cost history/export
  shell preparation/control pass

Keep the narrow sequencing guards visible:

- keep actual billing and settlement separate from dashboard shell ownership
- keep actual payload shipping separate from usage/cost governance
- keep real device-permission workflow and native capture-route ownership
  outside this packet
