# HyperTwist Phase 6R-AE first-party provider settlement exception and external-portal handoff preparation packet

Created on `2026-05-25`

## Status

- first-party HyperTwist packet
- source-backed `Phase 6R-AE` 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, normalized usage/cost event, operator-facing
usage/cost dashboard, provider usage/cost history/export, provider
receipt-review, and provider billing-settlement seams.

The granted slice is:

- first-party provider settlement exception and external-portal handoff shell only

It is not:

- an actual payment execution packet
- a provider-portal ownership packet
- an external billing settlement packet
- an external invoice remittance packet
- an actual payload-shipping packet
- a real device-permission workflow packet
- a native audio-device route ownership 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_AD_FIRST_PARTY_PROVIDER_BILLING_SETTLEMENT_AND_INVOICE_RECONCILIATION_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
- first-party HyperTwist remains the settlement exception and handoff shell 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-AE` slice may land:

1. first-party settlement-exception shell profile ids and definitions
2. derived exception entry, issue, and shell-state record shapes
3. session-config and companion-session-state expansion for those shapes
4. bounded capability exposure for:
   - `providerSettlementExceptionShell`
   - `providerExternalPortalHandoff`
   - `providerSettlementExceptionReview`
5. focused automation for pending-charge exception posture and provider-backed
   route-degraded handoff posture

The packet must stay out of:

- actual payment execution
- provider-portal ownership
- external settlement ownership
- external invoice-remittance ownership
- actual payload download or redistribution ownership
- real device-permission workflow ownership
- native audio-device route ownership

## Proposed implementation shape

Land the narrower first-party boundary through:

- retained recognition contract types for:
  - provider settlement-exception shell profile
  - provider settlement-exception entry
  - provider settlement-exception issue
  - provider settlement-exception shell state
  - expanded speech session config
  - expanded companion speech session state
- contract-library defaults for:
  - exception shell profile ids and definitions
  - exception action bindings and panel ids
  - service-health capability exposure
- training-subsystem composition for:
  - bounded exception posture derived from retained settlement snapshots
  - reference-only external-portal handoff readiness posture
  - pending-charge and route-degraded exception posture
  - explicit separation between first-party handoff surfaces and actual
    payment execution
- direct speech-client health capability exposure for:
  - `providerSettlementExceptionShell`
  - `providerExternalPortalHandoff`
  - `providerSettlementExceptionReview`

## Validation target

Validate with:

- Unreal build for `UnrealHyperTwistEditor Win64 Development`
- focused automation:
  - `HyperTwist.Permissive.WhisperCpp.Phase6R.AE`
- regressions:
  - `HyperTwist.Permissive.WhisperCpp.Phase6R.AD`
  - `HyperTwist.Permissive.WhisperCpp.Phase6R.AC`
  - `HyperTwist.Permissive.WhisperCpp.Phase6R.AB`
  - `HyperTwist.Permissive.WhisperCpp.Phase6R.AA`
  - `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-AF` first-party real device-permission workflow
  preparation/control pass

Keep the narrow sequencing guards visible:

- keep real device-permission workflow separate from native capture-route
  ownership
- keep actual payment execution and provider-portal ownership separate from
  this packet
- keep actual payload shipping separate from usage/cost governance
- keep broad assistant-platform widening outside this packet
