# HyperTwist Phase 6R-X first-party provider profile and BYOK custody implementation packet

Created on `2026-05-24`

## Status

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

## Purpose

This packet lands the next narrower bounded slice above the retained
`ggml-org/whisper.cpp` and `SYSTRAN/faster-whisper` speech-input seams.

The landed slice is:

- first-party provider-profile and BYOK custody metadata above the existing
  speech session, microphone-shell, permission/readiness, and payload-custody
  seams

It is not:

- a full donor-row transplant
- an actual downloadable payload-shipping packet
- a routing/policy layer packet
- a normalized usage/cost event-model packet
- a real device-permission workflow packet
- a native audio-device route ownership packet
- a top-level provider/session contract packet
- a voice-output packet
- a broad assistant-platform packet

## Current authority basis

This implementation packet stands on:

- `docs/REPO_LICENSE_TRACKING.md`
- `docs/ops/HYPERTWIST_PROVIDER_NEUTRALITY_AND_BYOK_DOCTRINE_2026-05-21.md`
- `docs/arch/HYPERTWIST_PHASE6R_X_FIRST_PARTY_PROVIDER_PROFILE_AND_BYOK_CUSTODY_PREPARATION_PACKET_2026-05-24.md`

The top-level provider/session contract owner does not change here:

- first-party HyperTwist remains the provider-neutral owner for the speech
  provider/session lane
- first-party HyperTwist now lands the first bounded provider-profile and
  BYOK custody boundary for that lane
- `ggml-org/whisper.cpp` remains bounded to retained offline STT donor seams
- `SYSTRAN/faster-whisper` remains bounded to complementary Python
  orchestration/service-lane seams

The granted family remains bounded to:

- explicit provider-profile contract shaping
- explicit BYOK custody contract shaping
- per-profile model-map and capability-map wording
- out-of-band auth-reference wording
- bounded speech-health capability exposure for the narrower provider-custody
  seam

This packet lands only the next narrower family in that granted set.

## Landed scope

The current code now owns a retained provider-profile / BYOK custody contract
through:

- retained recognition contract types for:
  - `FHyperTwistSpeechProviderProfile`
  - `FHyperTwistSpeechByokCustodyProfile`
  - expanded `FHyperTwistSpeechSessionConfig`
  - expanded `FHyperTwistSpeechServiceHealth`
- sample session-config and service-health outputs in:
  - `UHyperTwistContractLibrary`
- direct-donor speech client seam capability exposure in:
  - `UHyperTwistHttpSpeechClient`
- active companion session-config and service-health normalization in:
  - `UHyperTwistTrainingSubsystem`
- focused automation coverage in:
  - `HyperTwistWhisperCppPhase6RXProviderProfileByokContractTest.cpp`

## Why this is still intentionally bounded

This packet lands the next first-party provider-custody seam, but it does not
widen into neighboring retained families.

Still deferred:

- first-party provider routing and policy
- normalized usage/cost events
- actual downloadable payload shipping
- real device-permission workflow
- native audio-device route ownership beyond bounded shell posture
- voice-output ownership
- broad assistant-platform scope

## Validation

Build validation:

- `C:\Program Files\Epic Games\UE_5.7\Engine\Build\BatchFiles\Build.bat UnrealHyperTwistEditor Win64 Development -Project='C:\HyperTwist\UnrealHyperTwist\UnrealHyperTwist.uproject' -WaitMutex -NoHotReloadFromIDE -NoUba`

Focused automation validation:

- `C:\Program Files\Epic Games\UE_5.7\Engine\Binaries\Win64\UnrealEditor-Cmd.exe C:\HyperTwist\UnrealHyperTwist\UnrealHyperTwist.uproject -unattended -nop4 -nosplash -NullRHI -log -stdout -FullStdOutLogOutput -AbsLog=C:\HyperTwist\UnrealHyperTwist\Saved\Logs\Phase6R-X-ProviderProfileByok-Verify.log -ReportExportPath=C:\HyperTwist\UnrealHyperTwist\Saved\AutomationReports\Phase6R-X-ProviderProfileByok-Verify -ExecCmds="Automation RunTests HyperTwist.Permissive.WhisperCpp.Phase6R.X; Quit" -TestExit="Automation Test Queue Empty"`

Regression automation validation:

- `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`

Expected covered tests:

- `ProviderProfileSessionConfig`
- `ProviderProfileServiceHealth`
- `ProviderBackedByokFallback`
- existing `Phase 6R-W`, `Phase 6R-V`, `Phase 6R-U`, `Phase 6R-E`,
  `Phase 6R-F`, `Phase 6R-G`, `Phase 6R-H`, and `CubeDesk` regression suites

## Queue effect

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

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

- landed now:
  - speech transcript session boundary
  - VAD-aware session config and utterance envelope
  - transcript segment and transcript result
  - sidecar health and speech client boundary
  - live microphone shell profile and shell-state boundary
  - device-permission and capture-route readiness shell posture
  - downloadable model and payload custody boundary
  - first-party provider-profile and BYOK custody boundary for:
    - provider-profile ids and definitions
    - BYOK custody ids and definitions
    - supported provider-class wording
    - per-profile model / capability maps
    - out-of-band auth-reference wording
    - capability exposure for:
      - `providerProfileCustody`
      - `byokCustody`
      - `openAiCompatibleCustomEndpointProfile`
      - `userLabeledByokProfiles`
- still deferred:
  - first-party provider routing and policy
  - normalized usage/cost events
  - actual downloadable 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-Y` first-party provider routing and policy
  preparation/control pass

Keep the future sequencing guards visible:

- first-party HyperTwist
  - keep the top-level provider/session contract and provider routing/policy
    lane first-party
  - keep normalized usage/cost events separate from the landed provider-profile
    and BYOK custody boundary
- `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 shell, payload-custody, and
    provider-profile seams and bounded to Python orchestration/service-lane
    ownership rather than provider routing ownership
