# HyperTwist Phase 6R-W whisper.cpp downloadable model and payload custody preparation packet

Created on `2026-05-24`

## Status

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

## Purpose

This packet freezes the next widening order after the landed `Phase 6R-V`
`whisper.cpp` device-permission and capture-route readiness shell slice.

The open task was:

- define the next bounded source-backed widening packet for
  `ggml-org/whisper.cpp` as the retained `Phase 6R-W`
  downloadable model and payload custody seam

It is not:

- a full `whisper.cpp` row transplant
- an actual downloadable payload shipping packet
- a provider-profile or BYOK custody packet
- a real device-permission workflow packet
- a native audio-device route ownership packet
- a `SYSTRAN/faster-whisper` provider/service rewrite 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/v6_5_deep_manual_pack/HyperTwist/ROADMAP.md`
- `docs/arch/HYPERTWIST_PHASE6R_V_WHISPER_CPP_DEVICE_PERMISSION_AND_CAPTURE_ROUTE_READINESS_SHELL_IMPLEMENTATION_PACKET_2026-05-24.md`

The key accepted routing facts are:

- `ggml-org/whisper.cpp` remains the retained offline STT donor after the
  landed `Phase 6R-E`, `Phase 6R-U`, and `Phase 6R-V` slices
- upstream source already separates code posture from model/payload acquisition
  and loading surfaces
- first-party HyperTwist already owns the top-level provider/session contract
  and the future provider-profile / BYOK lane
- the retained donor value strongest for the next narrow widening is:
  - explicit model/payload descriptors
  - documented acquisition-path hints
  - integrity-check metadata
  - session-config and service-health custody exposure
- ownership denied here is:
  - do not widen into actual runtime download or shipping ownership
  - do not widen into provider-profile or BYOK custody ownership
  - do not widen into real device-permission workflow ownership
  - do not widen into native audio-device route ownership
  - do not let `whisper.cpp` inherit the top-level provider/session lane

## Required result

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

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

- define one bounded downloadable model and payload custody slice above the
  landed speech session and shell seams
- land first-party custody profile/state fields for explicit payload-review,
  shipping-posture, and provisioning-posture wording
- land explicit required/supported payload descriptors with bounded acquisition
  and integrity metadata
- add bounded service-health capability exposure and focused automation
- explicitly state which neighboring retained families stay closed

## Source-backed retained basis

Inspected retained donor basis:

- `C:\visual_studio_solutions\multi_project\GPT 5.4 HyperTwist parse\49-ggml-org-whisper-cpp-upstream-dossier.md`
- `C:\Workspaces\HyperTwist\mirrors\permissive\ggml-org\whisper.cpp\README.md`
- `C:\Workspaces\HyperTwist\mirrors\permissive\ggml-org\whisper.cpp\include\whisper.h`
- `C:\Workspaces\HyperTwist\mirrors\permissive\ggml-org\whisper.cpp\models\README.md`
- `C:\Workspaces\HyperTwist\mirrors\permissive\ggml-org\whisper.cpp\examples\server\README.md`
- `C:\Workspaces\HyperTwist\mirrors\permissive\ggml-org\whisper.cpp\examples\server\server.cpp`

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-W slice decision

The next widening slice is fixed as:

1. downloadable model and payload custody metadata

That narrowed slice covers:

- first-party speech contract expansion for:
  - payload custody profile ids
  - payload review / shipping / provisioning posture wording
  - required and supported model payload descriptors
  - bounded integrity-check metadata
- lifecycle sync for:
  - active session-config composition
  - mock and HTTP service-health exposure
  - provider-backed fallback health posture
- bounded capability exposure for:
  - `downloadableModelPayloadCustody`
  - `payloadIntegrityReview`
- focused automation coverage

## Deferred neighboring families

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

- actual runtime download or payload shipping ownership
- provider-profile or BYOK custody
- 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-V` to
  `Phase 6R-W`
- the packet records that the first `6R-W` widening slice is custody metadata
  only
- the packet states exact out-of-scope families for the first `6R-W` pass
- the packet preserves the upstream `MIT` attribution boundary explicitly
- the packet leaves actual shipping and provider-profile widening deferred

## Validation checklist

1. confirm the landed `Phase 6R-V` packet is the consumed prior queue head
2. confirm the retained `whisper.cpp` seam narrows cleanly to custody metadata
   rather than payload-shipping ownership
3. confirm the next implementation packet is framed as bounded source-backed
   widening rather than a broad speech-platform transplant

That is the packet.

## Queue effect

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

Once that slice lands, the next clean move should stay narrow inside the
retained speech lane at:

- a source-backed `Phase 6R-X` first-party provider-profile and BYOK custody
  preparation/control pass, while keeping actual payload shipping and real
  device workflow ownership separately deferred
