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

Created on `2026-05-25`

## Status

- first-party HyperTwist packet
- source-backed `Phase 6R-AF` preparation/control slice

## Purpose

This packet scopes 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 granted slice is:

- first-party real device-permission workflow only

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 control pass stands on:

- `docs/ops/HYPERTWIST_PROVIDER_NEUTRALITY_AND_BYOK_DOCTRINE_2026-05-21.md`
- `docs/arch/HYPERTWIST_PHASE6R_V_WHISPER_CPP_DEVICE_PERMISSION_AND_CAPTURE_ROUTE_READINESS_SHELL_IMPLEMENTATION_PACKET_2026-05-24.md`
- `docs/arch/HYPERTWIST_PHASE6R_AE_FIRST_PARTY_PROVIDER_SETTLEMENT_EXCEPTION_AND_EXTERNAL_PORTAL_HANDOFF_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 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

## Granted family

The bounded `Phase 6R-AF` slice may land:

1. first-party permission-workflow profile ids and definitions
2. derived permission-workflow entry, issue, and shell-state record shapes
3. session-config and companion-session-state expansion for those shapes
4. bounded capability exposure for:
   - `devicePermissionWorkflow`
   - `devicePermissionSettingsHandoff`
   - `devicePermissionRecheck`
5. focused automation for:
   - permission-request-required posture
   - settings-review-required posture
   - permission-recheck posture

The packet must stay out of:

- native audio-device route ownership
- actual OS permission-grant execution ownership
- actual payment execution
- provider-portal ownership
- actual payload download or redistribution ownership

## Proposed implementation shape

Land the narrower first-party boundary through:

- retained recognition contract types for:
  - permission-workflow profile
  - permission-workflow entry
  - permission-workflow issue
  - permission-workflow state
  - expanded speech session config
  - expanded companion speech session state
- contract-library defaults for:
  - permission-workflow profile ids and definitions
  - action bindings and panel ids
  - service-health capability exposure
- training-subsystem composition for:
  - bounded request / settings handoff / recheck posture
  - explicit separation between workflow posture and native route ownership
  - explicit separation between workflow posture and actual OS grant execution
- direct speech-client health capability exposure for:
  - `devicePermissionWorkflow`
  - `devicePermissionSettingsHandoff`
  - `devicePermissionRecheck`

## Validation target

Validate with:

- Unreal build for `UnrealHyperTwistEditor Win64 Development`
- focused automation:
  - `HyperTwist.Permissive.WhisperCpp.Phase6R.AF`
- regressions:
  - `HyperTwist.Permissive.WhisperCpp.Phase6R.AE`
  - `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-AG` first-party native capture-route ownership and
  workflow preparation/control pass

Keep the narrow sequencing guards visible:

- keep native capture-route ownership separate from the landed
  permission-workflow posture
- 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
