# HyperTwist Phase 6R-AB first-party provider usage/cost history/export shell implementation packet

Created on `2026-05-25`

## Status

- first-party HyperTwist packet
- bounded `Phase 6R-AB` implementation slice

## Purpose

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

The landed slice is:

- first-party provider usage/cost history/export shell

It is not:

- a provider receipt review packet
- an actual billing settlement packet
- an invoice reconciliation 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 broad assistant-platform packet

## Current authority basis

This implementation packet stands on:

- `docs/ops/HYPERTWIST_PROVIDER_NEUTRALITY_AND_BYOK_DOCTRINE_2026-05-21.md`
- `docs/arch/HYPERTWIST_PHASE6R_AB_FIRST_PARTY_PROVIDER_USAGE_COST_HISTORY_EXPORT_SHELL_PREPARATION_PACKET_2026-05-25.md`
- `docs/arch/HYPERTWIST_PHASE6R_AA_FIRST_PARTY_OPERATOR_FACING_PROVIDER_USAGE_COST_DASHBOARD_SHELL_IMPLEMENTATION_PACKET_2026-05-25.md`

The preserved owners do not change:

- 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

## Landed scope

The current code now owns a bounded history/export seam through:

- retained recognition contract types for:
  - `FHyperTwistSpeechUsageCostHistoryExportShellProfile`
  - `FHyperTwistSpeechUsageCostHistoryEntry`
  - `FHyperTwistSpeechUsageCostHistoryExportIssue`
  - `FHyperTwistSpeechUsageCostHistoryExportShellState`
  - expanded `FHyperTwistSpeechSessionConfig`
  - expanded `FHyperTwistTrainingCompanionSpeechSessionState`
- contract-library defaults for:
  - history/export shell profile ids and definitions
  - history/export panel ids and action bindings
  - service-health capability exposure
- active companion session-config, service-health, and rolling history/export
  shell composition in:
  - `UHyperTwistTrainingSubsystem`
- direct speech-client health capability exposure in:
  - `UHyperTwistHttpSpeechClient`
  - `UHyperTwistMockSpeechClient`
- focused automation coverage in:
  - `HyperTwistWhisperCppPhase6RABUsageCostHistoryExportShellContractTest.cpp`

## Why this is still intentionally bounded

This packet lands the operator-facing history/export shell family only.

Still deferred:

- provider receipt review and posted-charge inspection shell surfaces
- actual billing settlement or invoice reconciliation
- actual downloadable model/payload shipping
- real device-permission workflow
- native audio-device route ownership beyond bounded shell posture
- broad assistant-platform scope

## Validation

Build validation:

- `UnrealHyperTwistEditor Win64 Development`

Focused automation validation:

- `HyperTwist.Permissive.WhisperCpp.Phase6R.AB` `3/3`

Regression automation validation:

- `HyperTwist.Permissive.WhisperCpp.Phase6R.AA` `3/3`
- `HyperTwist.Permissive.WhisperCpp.Phase6R.Z` `3/3`
- `HyperTwist.Permissive.WhisperCpp.Phase6R.Y` `3/3`
- `HyperTwist.Permissive.WhisperCpp.Phase6R.X` `3/3`
- `HyperTwist.Permissive.WhisperCpp.Phase6R.W` `3/3`
- `HyperTwist.Permissive.WhisperCpp.Phase6R.V` `3/3`
- `HyperTwist.Permissive.WhisperCpp.Phase6R.U` `3/3`
- `HyperTwist.Permissive.WhisperCpp.Phase6R.E` `3/3`
- `HyperTwist.Permissive.FasterWhisper.Phase6R.F` `3/3`
- `HyperTwist.Permissive.Piper.Phase6R.G` `3/3`
- `HyperTwist.Permissive.Coqui.Phase6R.H` `3/3`
- `HyperTwist.CleanRoom.CubeDesk` `14/14`

Non-blocking warnings stayed limited to the existing Unreal headless/editor
noise, the pre-existing plugin dependency warning on `UnrealMCP`, and the
known `http:/speech/health` and `http:/vision/health` hostname-resolution
warnings in provider-backed automation.

## Queue effect

This packet consumes the current `Phase 6R-AB` implementation slice.

`ggml-org/whisper.cpp` remains only partially incorporated:

- landed now:
  - speech transcript session boundary
  - live microphone shell boundary
  - device-permission and capture-route readiness shell posture
  - downloadable model and payload custody boundary
  - first-party provider-profile and BYOK custody boundary
  - first-party provider routing and workflow-policy boundary
  - first-party normalized usage/cost event-model boundary
  - first-party operator-facing provider usage/cost dashboard shell boundary
  - first-party provider usage/cost history/export shell boundary for:
    - history/export shell profile ids and definitions
    - rolling history entry and export issue/state posture
    - companion-session history/export composition
    - capability exposure for:
      - `providerUsageCostHistoryShell`
      - `providerUsageCostExportPreview`
      - `providerUsageCostSummaryCopy`
- still deferred:
  - provider receipt review and posted-charge inspection shell surfaces
  - actual billing settlement or invoice reconciliation
  - actual downloadable model/payload shipping
  - real device-permission workflow
  - native audio-device route ownership beyond bounded shell posture
  - broad assistant-platform scope

The next clean move is:

- a source-backed `Phase 6R-AC` first-party provider receipt review and
  posted-charge inspection preparation/control pass

Keep the future sequencing guards visible:

- first-party HyperTwist
  - keep the top-level provider/session contract, routing/policy lane,
    usage/cost governance lane, dashboard shell lane, and history/export shell
    lane first-party
- `ggml-org/whisper.cpp`
  - keep code-license judgments separate from actual model or payload shipping
    review in any follow-on packet
- `SYSTRAN/faster-whisper`
  - keep the row complementary to the landed provider/session, custody,
    routing, usage/cost, dashboard, and history/export seams rather than
    widening it into receipt review or billing ownership
