# HyperTwist Phase 6R-AF first-party real device-permission workflow implementation packet

Created on `2026-05-25`

## Status

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

## Purpose

This packet lands the next bounded first-party slice above the landed speech
session, microphone-shell, permission/readiness shell, payload-custody,
provider-custody, provider-routing, normalized usage/cost event,
operator-facing usage/cost dashboard, provider usage/cost history/export,
provider receipt-review, provider billing-settlement, and provider settlement
exception seams.

The landed slice is:

- first-party real device-permission workflow

It is not:

- a native audio-device route ownership packet
- an actual OS permission-grant execution packet
- an actual payment execution packet
- a provider-portal ownership packet
- an actual payload-shipping 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_AF_FIRST_PARTY_REAL_DEVICE_PERMISSION_WORKFLOW_PREPARATION_PACKET_2026-05-25.md`
- `docs/arch/HYPERTWIST_PHASE6R_V_WHISPER_CPP_DEVICE_PERMISSION_AND_CAPTURE_ROUTE_READINESS_SHELL_IMPLEMENTATION_PACKET_2026-05-24.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
- first-party HyperTwist remains the real device-permission workflow 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 permission-workflow seam through:

- retained recognition contract types for:
  - `FHyperTwistSpeechDevicePermissionWorkflowProfile`
  - `FHyperTwistSpeechDevicePermissionWorkflowEntry`
  - `FHyperTwistSpeechDevicePermissionWorkflowIssue`
  - `FHyperTwistSpeechDevicePermissionWorkflowState`
  - expanded `FHyperTwistSpeechSessionConfig`
  - expanded `FHyperTwistTrainingCompanionSpeechSessionState`
- contract-library defaults for:
  - permission-workflow profile ids and definitions
  - permission panel ids and action bindings
  - service-health capability exposure
- active companion session-config, service-health, and derived
  permission-workflow composition in:
  - `UHyperTwistTrainingSubsystem`
- direct speech-client health capability exposure in:
  - `UHyperTwistHttpSpeechClient`
  - `UHyperTwistMockSpeechClient`
- focused automation coverage in:
  - `HyperTwistWhisperCppPhase6RAFDevicePermissionWorkflowContractTest.cpp`

## Why this is still intentionally bounded

This packet lands the real device-permission workflow family only.

Still deferred:

- native audio-device route ownership beyond bounded readiness/workflow posture
- actual OS permission-grant execution ownership
- actual payment execution or provider-portal ownership
- actual downloadable model/payload shipping
- broad assistant-platform scope

## Validation

Build validation:

- `UnrealHyperTwistEditor Win64 Development`

Focused automation validation:

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

Regression automation validation:

- `HyperTwist.Permissive.WhisperCpp.Phase6R.AE` `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:/vision/health` hostname-resolution warnings in provider-backed
automation.

## Queue effect

This packet consumes the current `Phase 6R-AF` 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
  - first-party real device-permission workflow boundary for:
    - permission-workflow profile ids and definitions
    - request / settings handoff / recheck issue posture
    - bounded capability exposure for:
      - `devicePermissionWorkflow`
      - `devicePermissionSettingsHandoff`
      - `devicePermissionRecheck`
  - 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
  - first-party provider receipt review and posted-charge inspection shell
    boundary
  - first-party provider billing settlement and invoice reconciliation shell
    boundary
  - first-party provider settlement exception and external-portal handoff shell
    boundary
- still deferred:
  - native audio-device route ownership beyond bounded readiness/workflow
    posture
  - actual OS permission-grant execution ownership
  - actual payment execution or provider-portal ownership
  - actual downloadable model/payload shipping
  - broad assistant-platform scope

The next clean move is:

- a source-backed `Phase 6R-AG` first-party native capture-route ownership and
  workflow 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, history/export shell
    lane, receipt-review shell lane, settlement shell lane,
    exception/handoff shell lane, and permission-workflow 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, history/export, receipt-review,
    settlement, exception/handoff, and permission-workflow seams rather than
    widening it into native route ownership, payment execution, or
    provider-portal ownership
