# HyperTwist Phase 6R-AG first-party native capture-route ownership and workflow preparation/control implementation packet

Created on `2026-05-26`

## Status

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

## Purpose

This packet lands the next bounded first-party slice above the landed speech
session, microphone-shell, permission/readiness shell, permission-workflow,
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 native capture-route ownership and workflow preparation/control

It is not:

- an unrestricted low-level audio-device takeover 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_AG_FIRST_PARTY_NATIVE_CAPTURE_ROUTE_OWNERSHIP_AND_WORKFLOW_PREPARATION_CONTROL_PREPARATION_PACKET_2026-05-26.md`
- `docs/arch/HYPERTWIST_PHASE6R_AF_FIRST_PARTY_REAL_DEVICE_PERMISSION_WORKFLOW_IMPLEMENTATION_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 bounded native capture-route workflow
  owner for this slice
- `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 native capture-route workflow seam
through:

- retained recognition contract types for:
  - `FHyperTwistSpeechNativeCaptureRouteWorkflowProfile`
  - `FHyperTwistSpeechNativeCaptureRouteWorkflowEntry`
  - `FHyperTwistSpeechNativeCaptureRouteWorkflowIssue`
  - `FHyperTwistSpeechNativeCaptureRouteWorkflowState`
  - expanded `FHyperTwistSpeechSessionConfig`
  - expanded `FHyperTwistTrainingCompanionSpeechSessionState`
- contract-library defaults for:
  - native capture-route workflow profile ids and definitions
  - workflow panel ids and action bindings
  - service-health capability exposure
- active companion session-config, service-health, and derived native
  capture-route workflow composition in:
  - `UHyperTwistTrainingSubsystem`
- direct speech-client health capability exposure in:
  - `UHyperTwistHttpSpeechClient`
  - `UHyperTwistMockSpeechClient`
- focused automation coverage in:
  - `HyperTwistWhisperCppPhase6RAGNativeCaptureRouteWorkflowContractTest.cpp`

## Why this is still intentionally bounded

This packet lands the bounded native capture-route ownership assessment and
workflow preparation/control family only.

Still deferred:

- unrestricted low-level audio-device takeover beyond the landed bounded
  workflow/control 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.AG` `4/4`

Regression automation validation:

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

Non-blocking warnings stayed limited to the existing Unreal headless/editor
noise, the pre-existing plugin dependency warning on `UnrealMCP`, the headless
CEF/web-browser warning, and the known `http:/vision/health` plus
`http:/speech/health` hostname-resolution warnings in provider-backed
automation.

## Queue effect

This packet consumes the current `Phase 6R-AG` 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
  - first-party native capture-route ownership assessment and workflow
    preparation/control boundary for:
    - session-open-required posture
    - permission-workflow dependency posture
    - preparation-required posture
    - route-retry posture
    - bounded capability exposure for:
      - `nativeCaptureRouteWorkflow`
      - `captureRoutePreparationControl`
      - `captureRouteOwnershipAssessment`
      - `reopenSpeechSession`
  - 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:
  - unrestricted low-level audio-device takeover beyond the landed bounded
    workflow/control 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 not another restrictive packet by default.

If a follow-on speech-adjacent packet is later justified, keep these guards
visible:

- prove a narrower remaining native capture-route ownership gap before widening
  into actual OS permission-grant execution
- keep actual payment execution and provider-portal ownership separate from any
  such packet
- keep actual payload shipping separate from usage/cost governance unless a
  narrower first-party gap is proven first
