# HyperTwist Phase 4 dashboard guidance preview band inspect surface packet

- bounded Phase `4` dashboard-consumer slice
- date: `2026-05-11`

## Intent

Deliberately choose the next adjacent live dashboard consumer band in the active preview neighborhood and expose the guidance preview selection, case detail, case navigation, launch control, and recommended/follow-up deck preview cluster as one inspectable gameplay and Blueprint seam.

## Why this packet exists

`UHyperTwistCoachDashboardWidget` already exposed six adjacent preview-focused surfaces:

- `GetDisplayedGuidancePreviewSelectionInspectSurface()`
- `GetDisplayedGuidancePreviewCaseDetailInspectSurface()`
- `GetDisplayedGuidancePreviewCaseNavigationInspectSurface()`
- `GetDisplayedGuidancePreviewLaunchActionControlInspectSurface()`
- `GetDisplayedRecommendedGuidanceDeckPreviewInspectSurface()`
- `GetDisplayedFollowUpGuidanceDeckPreviewInspectSurface()`

But callers that wanted to reason about that whole preview-focused dashboard cluster still had to stitch six adjacent getters together manually.

## What changed

- added `FHyperTwistTrainingCoachDashboardGuidancePreviewBandInspectSurface`
- added `GetDisplayedGuidancePreviewBandInspectSurface()`
- composed the new surface entirely over the already-landed preview selection, preview case detail/navigation, preview launch control, and recommended/follow-up deck preview surfaces
- kept the packet bounded by avoiding any new backend derivation or new widget-state caching

## Files

- `C:\HyperTwist\UnrealHyperTwist\Source\UnrealHyperTwist\Public\HyperTwistTraining\HyperTwistTrainingTypes.h`
- `C:\HyperTwist\UnrealHyperTwist\Source\UnrealHyperTwist\Public\HyperTwistTraining\HyperTwistCoachDashboardWidget.h`
- `C:\HyperTwist\UnrealHyperTwist\Source\UnrealHyperTwist\Private\HyperTwistTraining\HyperTwistCoachDashboardWidget.cpp`
- `C:\HyperTwist\docs\HYPERTWIST_ROADMAP_OVERHAUL_EXPANSION_GUIDE.md`

## Outcome

Gameplay and Blueprint callers can now inspect:

- the whole adjacent guidance preview dashboard band through one surface
- preview selection, preview case detail/navigation, preview launch control, and recommended/follow-up deck preview status lines together
- active preview lane, deck/case identity, preview start-control posture, and recommended/follow-up deck availability posture

without stitching six separate adjacent getters together manually.

## Validation

- full `Development Editor | Win64` MSBuild on `UnrealHyperTwist.sln`
  - passed with `0 Warning(s), 0 Error(s)`

## Next clean slice

Treat the retained-history text-band lane, the template-launch / preview action-control band, the execution-action-control band, the verification / recognition / review-policy status band, the selected-queue band, the queue scheduling / recovery band, the closure-recovery band, the queue-suppression band, the handoff-history band, the guidance-decision-history band, the template-launch-history band, the method-drill recovery-outcome-history band, the method-drill recovery-memory-history band, the method-drill follow-up-history band, and the guidance-preview band as landed baseline, then deliberately choose another adjacent live dashboard consumer band instead of reopening already-landed surfaces by drift.
