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

Created on `2026-05-24`

## Status

- historical same-day preparation authority
- bounded post-`Phase 6R-W` control slice
- the first bounded implementation slice now lands separately under:
  - `docs/arch/HYPERTWIST_PHASE6R_X_FIRST_PARTY_PROVIDER_PROFILE_AND_BYOK_CUSTODY_IMPLEMENTATION_PACKET_2026-05-24.md`

## Purpose

This packet freezes the next widening order after the landed `Phase 6R-W`
`whisper.cpp` downloadable model and payload custody slice.

The open task was:

- define the next bounded source-backed widening packet above the landed speech
  session, shell, and payload-custody seams as the retained `Phase 6R-X`
  first-party provider-profile and BYOK custody seam

It is not:

- a full `whisper.cpp` 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 voice-output packet
- a broad assistant-platform packet

## Current authority basis

This preparation packet stands on already-closed authority:

- `docs/REPO_LICENSE_TRACKING.md`
- `docs/ops/HYPERTWIST_PROVIDER_NEUTRALITY_AND_BYOK_DOCTRINE_2026-05-21.md`
- `docs/v6_5_deep_manual_pack/HyperTwist/ROADMAP.md`
- `docs/arch/HYPERTWIST_PHASE6R_W_WHISPER_CPP_DOWNLOADABLE_MODEL_AND_PAYLOAD_CUSTODY_IMPLEMENTATION_PACKET_2026-05-24.md`

The key accepted routing facts are:

- first-party HyperTwist already owns the top-level provider/session contract
- the landed `Phase 6R-W` packet already owns payload-custody metadata above
  the current speech seams
- the correct next implementation order is now:
  - provider-profile and BYOK custody surfaces
  - then routing/policy
  - then normalized usage/cost events
- the retained donor value strongest for the next narrow widening is:
  - first-party provider-profile ids and definitions
  - first-party BYOK custody ids and definitions
  - per-profile model lists or capability maps
  - auth-reference wording that preserves out-of-band secret custody
  - session-config and service-health exposure for the bounded custody seam
- ownership denied here is:
  - do not widen into routing/policy ownership
  - do not widen into actual downloadable payload shipping
  - do not widen into normalized usage/cost event ownership
  - do not widen into real device-permission workflow ownership
  - do not let `whisper.cpp` or `faster-whisper` inherit the top-level
    provider/session or provider-profile lane

## Required result

The source-backed control pass for this packet is now complete.

The first actual `6R-X` implementation packet should:

- define one bounded first-party provider-profile and BYOK custody slice above
  the landed speech session, shell, and payload-custody seams
- land first-party provider-profile ids/definitions for explicit provider
  class, endpoint class, model-map, capability-map, and auth-reference wording
- land first-party BYOK custody ids/definitions for explicit supported-provider
  class, user-label, enable/disable, and out-of-band secret-custody wording
- sync those surfaces into active speech session-config composition and mock /
  HTTP speech service-health composition
- add bounded capability exposure and focused automation
- explicitly state which neighboring retained families stay closed

## Source-backed retained basis

Inspected retained / doctrine basis:

- `C:\visual_studio_solutions\multi_project\GPT 5.4 HyperTwist parse\49-ggml-org-whisper-cpp-upstream-dossier.md`
- `C:\visual_studio_solutions\multi_project\GPT 5.4 HyperTwist parse\50-systran-faster-whisper-upstream-dossier.md`
- `C:\HyperTwist\docs\ops\HYPERTWIST_PROVIDER_NEUTRALITY_AND_BYOK_DOCTRINE_2026-05-21.md`
- `C:\Workspaces\HyperTwist\mirrors\permissive\ggml-org\whisper.cpp\README.md`
- `C:\Workspaces\HyperTwist\mirrors\permissive\SYSTRAN\faster-whisper\README.md`

Inspected first-party receiving basis:

- `UnrealHyperTwist/Source/UnrealHyperTwist/Public/HyperTwistRecognition/HyperTwistRecognitionTypes.h`
- `UnrealHyperTwist/Source/UnrealHyperTwist/Public/HyperTwistRecognition/HyperTwistSpeechClient.h`
- `UnrealHyperTwist/Source/UnrealHyperTwist/Public/HyperTwistTraining/HyperTwistTrainingTypes.h`
- `UnrealHyperTwist/Source/UnrealHyperTwist/Public/HyperTwistTraining/HyperTwistTrainingSubsystem.h`
- `UnrealHyperTwist/Source/UnrealHyperTwist/Private/HyperTwistBootstrap/HyperTwistContractLibrary.cpp`
- `UnrealHyperTwist/Source/UnrealHyperTwist/Private/HyperTwistTraining/HyperTwistTrainingSubsystem.cpp`
- `UnrealHyperTwist/Source/UnrealHyperTwist/Private/HyperTwistRecognition/HyperTwistMockSpeechClient.cpp`
- `UnrealHyperTwist/Source/UnrealHyperTwist/Private/HyperTwistRecognition/HyperTwistHttpSpeechClient.cpp`

## Narrowed 6R-X slice decision

The next widening slice is fixed as:

1. first-party provider-profile and BYOK custody metadata

That narrowed slice covers:

- first-party speech contract expansion for:
  - provider-profile ids
  - provider-profile definitions
  - BYOK custody ids
  - BYOK custody definitions
  - supported provider-class wording
  - per-profile model maps
  - per-profile capability maps
  - auth-reference wording that keeps secrets out-of-band
  - per-profile enable/disable wording
- lifecycle sync for:
  - active session-config composition
  - mock and HTTP service-health exposure
  - provider-backed fallback health posture
- bounded capability exposure for:
  - `providerProfileCustody`
  - `byokCustody`
  - `openAiCompatibleCustomEndpointProfile`
  - `userLabeledByokProfiles`
- focused automation coverage

## Deferred neighboring families

The first `6R-X` implementation packet must keep these capability families
closed:

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

## Acceptance criteria

- the packet records why the queue advanced from landed `Phase 6R-W` to
  `Phase 6R-X`
- the packet records that the first `6R-X` widening slice is first-party
  provider-profile and BYOK custody metadata only
- the packet states exact out-of-scope families for the first `6R-X` pass
- the packet preserves first-party provider-neutrality and out-of-band secret
  custody explicitly
- the packet leaves routing/policy and normalized usage/cost widening deferred

## Validation checklist

1. confirm the landed `Phase 6R-W` packet is the consumed prior queue head
2. confirm the retained speech seam narrows cleanly to first-party
   provider-profile and BYOK custody metadata rather than routing/policy or
   payload-shipping ownership
3. confirm the next implementation packet is framed as bounded first-party
   widening rather than a broad provider-platform transplant

That is the packet.

## Queue effect

This preparation packet is now consumed by the landed bounded `Phase 6R-X`
implementation slice.

Once that slice lands, the next clean move should stay narrow inside the
first-party provider lane at:

- a source-backed `Phase 6R-Y` first-party provider routing and policy
  preparation/control pass, while keeping normalized usage/cost events, actual
  payload shipping, and real device workflow ownership separately deferred
