# HyperTwist - FEATURE_REGISTRY.md

## Purpose

This file is the canonical normalized feature extraction surface for
HyperTwist.

It exists so later work such as:

- manuals
- onboarding docs
- roadmap summaries
- UI copy planning
- marketing drafts
- portfolio/status summaries

does not need to recover feature truth from packet notes, roadmap fragments,
and donor comparisons.

This file is deliberately not only an "implemented now" list.

It separates:

- current implemented truth
- deep-source grounded retained capability
- shallow placeholder capability

That separation is the important part.

## Governing rule

Treat this file as the normalized feature registry.

Treat packet docs, standing notes, and current product code as the authority
behind each entry.

If this registry and a packet disagree, the packet wins.

If this registry and live code disagree, live code plus the current
implementation kickoff and roadmap win.

Primary authority surfaces behind this registry:

- `C:\HyperTwist\docs\v6_5_deep_manual_pack\HyperTwist\PRD.md`
- `C:\HyperTwist\docs\v6_5_deep_manual_pack\HyperTwist\ARCHITECTURE.md`
- `C:\HyperTwist\docs\v6_5_deep_manual_pack\HyperTwist\ROADMAP.md`
- `C:\HyperTwist\docs\v6_5_deep_manual_pack\HyperTwist\CAPABILITY_CONSOLIDATION_DOCTRINE.md`
- `C:\HyperTwist\docs\ops\HYPERTWIST_IMPLEMENTATION_PHASE_1_KICKOFF.md`
- `C:\HyperTwist\docs\ops\HYPERTWIST_MEMORY_LANE_AUTHORITY_AND_PHASE_IMPLEMENTATION_DOCTRINE_2026-05-21.md`
- `C:\HyperTwist\docs\ops\HYPERTWIST_CONTINUITY_LATTICE_AND_CONTEXT_ASSEMBLY_PROFILE_DOCTRINE_2026-05-23.md`
- `C:\HyperTwist\docs\VECTORSHELL_MEMORY_SYSTEM_IMPORT_AUTHORITY_FOR_HYPERTWIST_2026-05-25.md`
- `C:\HyperTwist\docs\ops\HYPERTWIST_PROVIDER_NEUTRALITY_AND_BYOK_DOCTRINE_2026-05-21.md`
- `C:\HyperTwist\docs\ops\HYPERTWIST_SKILLIZATION_AND_COMMAND_SURFACE_DOCTRINE_2026-05-21.md`
- the relevant implementation packet docs

## Status taxonomy

Every feature entry in this registry must use one of these tiers.

### `Implemented now`

Meaning:

- first-party product-surface evidence exists now
- safe to describe as current product capability

### `Deep-source grounded retained`

Meaning:

- feature is source-backed and retained through repo evaluation or bounded
  implementation authority
- not necessarily implemented in the live product yet
- safe to describe as retained or planned product capability
- not safe to describe as already shipped unless separate product evidence
  exists

### `Shallow placeholder`

Meaning:

- feature family is known from shallow intake, README signal, queue shape, or
  portfolio census
- exact source-backed capability boundaries are not yet established
- not safe to market as a committed feature
- useful only as an internal stub

## Extraction rule

When later generating user-facing material:

1. `Implemented now`
   - may be described as present
2. `Deep-source grounded retained`
   - may be described as retained, planned, or roadmap capability
3. `Shallow placeholder`
   - must stay internal unless later deep-source work upgrades it

Do not collapse those three tiers into one undifferentiated "features" voice.

## Current implemented truth

| Feature | Status | Primary authority | Notes |
|---|---|---|---|
| Native Unreal training runtime | Implemented now | first-party runtime + kickoff note | Current runtime center is real, not speculative. |
| Training session orchestration and coaching cockpit | Implemented now | current training/coaching surfaces | `UHyperTwistTrainingSubsystem`, `UHyperTwistTrainingRuntimeLibrary`, `UHyperTwistTrainingPanelWidget`, and `UHyperTwistCoachDashboardWidget` are real first-party anchors. |
| Curriculum/catalog materialization and generated-mode launch | Implemented now | first-party catalog/training surfaces | Imported training packs and generated-mode launch flows are live. |
| Classic-cube timing, drill, and training-session flows | Implemented now | landed timer/training packets | Current training surface is broader than a timer-only shell. The live timer substrate is still the narrower landed `KubeTimr`-derived local subsystem slice, while bounded `kash/cubedesk` clean-room implementation is now also live above it for trainer-session coupling, solve/session/training-session/game-session domain surfaces, analytics panels, and integrated smart-device workflow composition; broader competitive timer parity remains retained under `cs0x7f/cstimer` specifically for competition-grade inspection or multi-phase timing semantics, rolling stats/average or `DNF` math, session/import-export expectations, scramble-registry breadth, and `GAN`/smart-device behavior, and legacy session-format reference value remains retained under `cubing/qqTimer`. |
| Publication/leaderboard projection and entitlement gating | Implemented now | landed `kash/cubedesk` bounded packets | Publication and entitlement are live first-party training surfaces. |
| Local social challenge bundle | Implemented now | landed `kash/cubedesk` `Bound 5` | Challenge/social training slice is real, but bounded. |
| Classic-cube calibration and ordered face observation | Implemented now | landed `qbr` packet | Calibration contract and ordered face-observation contract are live. |
| Classic-cube webcam shell | Implemented now | landed `qbr` `Phase 6R-O` | First-party webcam shell profile, bounded overlay panels, and input-action contract are live. |
| Locale-aware solve-guidance routing overlay | Implemented now | landed `qbr` `Phase 6R-AK` + landed `rubix-cube-solver` `Phase 6R-Q` | First-party supported-locale contract, locale-display routing, and qbr-grounded starting-orientation reminder are live above the bounded webcam and solve-explanation stack without widening into bundled-font shipping or standalone multilingual shell rendering. |
| Multilingual solve-shell presentation posture | Implemented now | landed `qbr` `Phase 6R-AN` | First-party script-direction, text-flow, and complex-text-shaping posture are now live for the qbr-grounded locale set without authorizing donor-font redistribution or standalone donor-rendered solve shells. |
| Bundled-font review boundary | Implemented now | landed `qbr` `Phase 6R-AS` | First-party font-review profile ids, per-locale review-descriptor routing, and active shell / solve-guidance review metadata are now live for the qbr-grounded locale set while donor font redistribution and standalone multilingual rendering stay deferred. |
| Committed-face reconstruction and final classic-net shaping | Implemented now | landed `rubix-cube-solver` packet | Reconstruction session boundary is live. |
| Browser-assisted recognition shell | Implemented now | landed `rubix-cube-solver` `Phase 6R-P` | First-party browser-shell profile, websocket session metadata, stage routing, and manual-edit handoff are live. |
| Bounded solve explanation and recommendation shell | Implemented now | landed `rubix-cube-solver` `Phase 6R-Q` | First-party stage-ladder guidance and recommendation-state readout are live after full reconstruction. |
| Bundled browser visualization asset review boundary | Implemented now | landed `rubix-cube-solver` `Phase 6R-AT` | First-party browser-asset review profile ids, twistysim review-descriptor routing, and active browser-shell review metadata are now live while donor asset redistribution and broad playback/runtime ownership stay deferred. |
| Correction-resolution closure shell | Implemented now | landed shared `Phase 6R-S` packet | First-party accepted-resolution ledger, per-face manual-review acceptance, and solve-guidance reopen/unlock semantics are live above the bounded correction shell. |
| Hyper puzzle catalog contract | Implemented now | landed `Hyperspeedcube` `Phase 6R-A` | Narrow retained hyper-puzzle catalog slice is live. |
| Hyper notation and replay-log serialization boundary | Implemented now | landed `Hyperspeedcube` `Phase 6R-K` | Narrow retained notation and log-serialization slice is live. |
| Hyper replay verification boundary | Implemented now | landed `Hyperspeedcube` `Phase 6R-L` | Narrow retained replay-verification and solve-proof slice is live. |
| Tiling topology and geometry-family contract | Implemented now | landed `MagicTile` `Phase 6R-D` | Narrow retained non-Euclidean topology slice is live. |
| Transform-aware tiling macro remapping and persistence boundary | Implemented now | landed `MagicTile` `Phase 6R-T` | First-party transform-aware remapping, reverse/setup-move playback tags, and macro XML compatibility boundary are live above the landed topology slice. |
| Embedded browser host decision for non-Euclidean tiling | Implemented now | landed first-party `MagicTile` `Phase 7A` | First-party `MagicTile` posture now routes live non-Euclidean interaction through the already-landed embedded browser/CEF shell above the retained topology and macro lanes, while native spherical/hyperbolic renderer ownership and the legacy `WinForms` / `OpenTK` host shell remain deferred. |
| Tiling browser state bridge, shared scramble normalization, and unified timer transport | Implemented now | landed first-party `MagicTile` `Phase 7B` | First-party tiling state envelopes, bridge-contract descriptors, browser widget/bridge decoding, shared scramble normalization, and training-timer continuity are live above the embedded-browser host posture without claiming generic runtime-base replacement. |
| Provider-backed recognition session boundary | Implemented now | first-party current code | `UHyperTwistHttpVisionClient` and normalized recognition envelopes are live first-party seams. |
| Speech transcript session boundary | Implemented now | landed `whisper.cpp` `Phase 6R-E` | Transcript sessions, utterance envelopes, and speech-health seams are live. |
| Live microphone capture shell | Implemented now | landed `whisper.cpp` `Phase 6R-U` | First-party microphone shell profile, bounded panel/action contract, and live shell-state composition are now live above the transcript-session seam. |
| Device-permission and capture-route readiness shell | Implemented now | landed `whisper.cpp` `Phase 6R-V` | First-party permission/readiness shell posture, issue objects, retry/request semantics, and bounded capability exposure are now live above the microphone shell seam. |
| Downloadable model and payload custody boundary | Implemented now | landed `whisper.cpp` `Phase 6R-W` | First-party payload-custody profile, required/supported model-payload descriptors, and bounded integrity metadata are now live above the landed speech session and shell seams. |
| First-party provider profile and BYOK custody boundary | Implemented now | landed first-party `Phase 6R-X` | First-party provider-profile definitions, BYOK custody definitions, per-profile model/capability maps, and out-of-band auth-reference wording are now live above the landed speech session, shell, and payload-custody seams. |
| First-party provider routing and workflow-policy boundary | Implemented now | landed first-party `Phase 6R-Y` | First-party routing-policy ids/definitions, route-decision summaries, fallback-health posture, and workflow-policy capability exposure are now live above the landed provider-custody seam. |
| First-party normalized usage/cost event surface | Implemented now | landed first-party `Phase 6R-Z` | First-party accounting-profile definitions, normalized usage/cost event templates and health summaries, quota/rate-limit state, and bounded capability exposure are now live above the landed provider-routing seam. |
| First-party operator-facing provider usage/cost dashboard shell | Implemented now | landed first-party `Phase 6R-AA` | First-party dashboard shell profiles, dashboard issue/state objects, quota escalation banners, route diagnostics, and operator-facing panel/action contracts are now live above the landed normalized usage/cost seam. |
| First-party provider usage/cost history/export shell | Implemented now | landed first-party `Phase 6R-AB` | First-party rolling history entries, export issue/state objects, summary export preview/copy posture, and operator-facing panel/action contracts are now live above the landed provider usage/cost dashboard seam. |
| First-party provider receipt review and posted-charge inspection shell | Implemented now | landed first-party `Phase 6R-AC` | First-party receipt-review shell profiles, derived receipt-review entries, charge-pending and variance issue posture, and bounded inspection capability exposure are now live above the landed provider usage/cost history/export seam. |
| First-party provider billing settlement and invoice reconciliation shell | Implemented now | landed first-party `Phase 6R-AD` | First-party settlement shell profiles, derived settlement entries, invoice-reconciliation posture, settlement-readiness issue state, and bounded settlement capability exposure are now live above the landed provider receipt-review seam. |
| First-party provider settlement exception and external-portal handoff shell | Implemented now | landed first-party `Phase 6R-AE` | First-party settlement-exception shell profiles, derived exception entries, reference-only external-portal handoff posture, and bounded exception capability exposure are now live above the landed provider settlement seam. |
| First-party real device-permission workflow | Implemented now | landed first-party `Phase 6R-AF` | First-party permission-workflow profiles, request/settings/recheck posture, and bounded workflow capability exposure are now live above the landed permission/readiness shell seam. The bounded first-party native capture-route workflow/control layer now lives in landed `Phase 6R-AG`. |
| First-party native capture-route ownership and workflow preparation/control | Implemented now | landed first-party `Phase 6R-AG` | First-party native capture-route ownership assessment, preparation/retry/reopen posture, and bounded workflow capability exposure are now live above the landed permission-workflow seam. The bounded first-party operator-facing shell layer now lives in landed `Phase 6R-AH`. |
| First-party operator-facing native capture-route workflow shell | Implemented now | landed first-party `Phase 6R-AH` | First-party shell profiles, shell-state posture, ownership-summary/preparation/session-reopen card contracts, and bounded operator-facing capability exposure are now live above the landed native capture-route workflow/control seam. Actual OS permission-grant execution, payment execution, provider-portal ownership, and payload shipping remain deferred. |
| First-party provider-neutral custom-endpoint runtime routing | Implemented now | landed first-party `Phase 6R-AI` | First-party per-session provider-profile endpoint selection, runtime routing, fallback-health reflection, and bounded provider-backed transport-failure posture are now live above the landed provider-profile/BYOK and provider-routing seams. Provider-specific overlays, payment execution, provider-portal ownership, and payload shipping remain deferred. |
| Analytics/reporting surfaces | Implemented now | landed analytics/reporting packets | Reporting is real, but bounded to accepted retained slices. |
| Rewritten training analytics and report reference grounding | Implemented now | `apache/echarts` retained permissive lane + first-party current code | Current live `Training Analytics` reference side includes four rewritten first-party targets grounded in retained `apache/echarts`: session outcome and progress reporting, analytics data-view and export, timing-trend history and overview interaction, and the optional richer explainer or sidecar boundary. This does not displace the landed `Phase 3R-C` first-party analytics/reporting owner or elevate `ecomfe/echarts-gl` and `ecomfe/zrender` beyond support-only sidecars. |
| Browser/spatial/media adjunct surfaces | Implemented now | landed `three.js`, `react-three-fiber`, `xr`, `model-viewer`, `remotion` packets | These are implemented bounded families, and the current Phase 1 browser-runtime landing now includes a first-party authoritative `Content/Browser/index.html` shell, bundled-runtime upgrade path, committed clean-checkout plain-JS fallback runtime, embedded `UHyperTwistBrowserWidget` bridge, the `2026-06-19` runtime-ready queue hardening that retains outbound Unreal shell traffic until the browser runtime is ready, a same-day first-party `Browser Runtime Status` surface with shared boot-state ownership across bundled and fallback shells, a follow-on typed Unreal-side `browser-runtime-status` capture seam that retains the last valid runtime snapshot across unrelated later envelope traffic until explicit reset, a second follow-on typed Unreal-side `hypertwist-runtime-ready` capture seam that raises the original handshake payload out of raw JSON-only handling without changing queue flush behavior, a third same-day native/operator-facing status surface that consumes those typed seams inside Unreal while clearing retained runtime ownership on shell-authority change, a fourth same-day native training/operator diagnostics-panel continuation that wires that typed status ownership into `UHyperTwistTrainingPanelWidget` and the coach dashboard without making the dashboard inspect seam depend on stale rendered strings, a fifth same-day diagnostics-fidelity continuation that now carries bootstrap/runtime-ready timestamps, last command/shell-state receipt timestamps, and fallback reason through the same native operator/training seams, and a later `2026-06-23` control/input readiness continuation that projects shipped keyboard/input truth and unfinished XR/preferences truth through the same native training/operator surfaces. This still is not proof of unlimited browser-shell parity. |
| Bounded native OpenXR runtime-owner substrate | Implemented now | landed first-party `2026-07-01` bounded XR continuation | The desktop-hosted branch now enables `OpenXR` plus `XRBase`, ships first-party runtime-owner/profile ownership through `UHyperTwistXrRuntimeLibrary` and `AHyperTwistXrTrainingPawn`, and keeps the stable ids `xr/openxr-desktop-training-runtime-owner`, `xr-openxr-training-preferences/v1`, and `xr-openxr-motion-controllers/v1` visible through both native XR code and the operator/training inspect surfaces. The current same-family hardening pass also clamps invalid preference values back into bounded ranges, wires bounded manual vertical-adjust input into the XR training pawn instead of leaving that preference field inert, and clears stale desktop-fallback rotation when headset runtime becomes active so desktop look-pitch does not leak forward into live HMD posture. The maintained reverse-SSH Windows lane revalidated the exact-source state on `C:\HyperTwist_worktrees\phase10validate` with final editor build `Result: Succeeded` at UnrealBuildTool `3672.35 seconds`, focused XR automation report `XR-BoundedRuntimeOwner-Hardening-20260701` with `4/4` green, and full browser automation report `Browser-XrHardening-20260701` with all `26` `HyperTwist.Browser.*` tests green. The current same-family continuation source now also adds first-party controller-settings/rebinding ownership above that substrate, while broader controller widening and live packaged headset/controller proof remain explicitly unfinished. A later exact-source semantics hardening follow-up on `2026-07-02` then rebuilt the same maintained root with `Result: Succeeded` at UnrealBuildTool `3104.63 seconds`, re-exported `XR-ControllerSettingsOwnership-Semantics-20260702` with all `4` `HyperTwist.FirstParty.XR.*` tests green plus `Browser-XrControllerSettingsOwnership-Semantics-20260702` with all `26` `HyperTwist.Browser.*` tests green, and kept first-party controller-settings/rebinding ownership distinct from legacy finished packaged-proof state so the bounded lane now says `owned` without overstating `shipping complete`. The next same-family packaged-validation continuation on that same date then added first-party packaged XR launch-surface/game-mode/report ownership through `UHyperTwistXrPackageValidationLibrary`, `AHyperTwistXrTrainingGameMode`, `scripts\Invoke-HyperTwistXrPackage.ps1`, and `scripts\Launch-HyperTwistXrPackage.ps1`; after repairing stale `-SkipBuild` semantics with a truthful full packaged rebuild (`Result: Succeeded`, UnrealBuildTool `2499.70 seconds`, `BuildCookRun time: 2593.82 s`), the final exact-source rerun stayed green in headless `nullrhi` mode with `BuildCookRun time: 85.47 s`, both XR smoke maps passed, and checked-in aggregate proof now lives at `docs/generated/xr/xr_packaged_validation_report_2026-07-02.json`. That package seam proves first-party Windows packaged structural launch and ownership truth, while the remaining live gates stay explicit as `xr/windows-packaged-headset-session-observation` and `xr/windows-packaged-controller-input-observation`. A final same-day preflight continuation then tightened the last live gate itself by adding interactive-session and active-`OpenXR` preflight reporting to `scripts\Launch-HyperTwistXrPackage.ps1`, adding the dedicated live wrapper `scripts\Invoke-HyperTwistXrWindowedObservation.ps1`, and checking in `docs/generated/xr/xr_windowed_live_observation_probe_2026-07-02.json`, which truthfully records that the current reverse-SSH/OpenSSH launcher is Session `0`, the Explorer desktop remains Session `1`, and no active `OpenXR` runtime is currently registered on the host. The next same-day bridge continuation then added `scripts\Invoke-HyperTwistInteractiveDesktopTask.ps1`, checked in `docs/generated/xr/xr_interactive_desktop_task_probe_2026-07-02.json`, and re-ran the XR windowed observation through a real Session `1` desktop bridge with resulting proof in `docs/generated/xr/xr_windowed_interactive_desktop_probe_2026-07-02.json`, so the remaining live blocker was first narrowed from “desktop-session bridge plus runtime” down to the absent active `OpenXR` runtime alone. The latest same-day continuation then removed even that runtime-resolution blocker without mutating the machine-wide registry: the wrappers now own bounded per-process `OpenXrRuntimePathOverride`, the maintained lane proved existing host manifest `C:\Windows\System32\MixedRealityRuntime.json` through corrected grace-hardened evidence at `docs/generated/xr/xr_interactive_desktop_task_probe_wmr_override_grace_2026-07-02.json` and `docs/generated/xr/xr_windowed_interactive_desktop_probe_wmr_override_grace_2026-07-02.json`, and the remaining live blockers are now the actual physical observations `bHeadMountedDisplayConnected: false`, `bHeadMountedDisplayEnabled: false`, and no controller-input activity yet rather than runtime manifest resolution. |
| Native control/input readiness inspect surface | Implemented now | landed first-party `2026-06-23` browser/native operator continuation | `UHyperTwistTrainingPanelWidget` and `UHyperTwistCoachDashboardWidget` now expose `FHyperTwistTrainingControlInputReadinessInspectSurface`, including the shipped `classic-wca-keyboard/v1` mapping, exact classic-cube pointer, orbit, zoom, and action-shortcut truth, higher-dimensional dedicated-family runtime ownership truth, project-level `EnhancedInput` plus motion-controller groundwork facts, immersive-presence contract presence, and explicit bounded XR/runtime plus controller-settings truth. The rendered detail line now also carries the fixed desktop-hosted `No-Go` decision on native OpenXR/controller widening instead of leaving that truth stranded in a non-rendered follow-up field. A later same-day structured-boundary hardening follow-up then promoted that same XR/controller boundary into stable inspect-surface fields as well, including decision id `desktop-hosted-openxr-controller-widening-no-go` plus explicit reopen requirements for dedicated runtime owners, user-facing settings or rebinding ownership, and Windows packaged controller validation, so native operator automation no longer depends only on rendered prose to verify the boundary. The recovered primary reverse-SSH `localhost:22022` lane rebuilt maintained validation worktree `C:\HyperTwist_worktrees\phase10validate` on `2026-06-23` with `Result: Succeeded`, UnrealBuildTool `Total execution time: 1563.53 seconds`, and exported `Saved\AutomationReports\Browser-ControlInputReadiness-Verify\index.json` with all `16` `HyperTwist.Browser.*` tests passing, including `CoachDashboard.ControlInputReadinessInspectSurface` and `TrainingPanel.ControlInputReadinessInspectSurface`. A later same-day quality follow-up then moved the project-input-groundwork inspection behind that surface from raw text scanning into structured Unreal config reads, rebuilt the same maintained validation worktree again with `Result: Succeeded`, UnrealBuildTool `Total execution time: 158.13 seconds`, and re-exported focused browser proof to `Saved\AutomationReports\Browser-ControlInputReadiness-StructuredConfig-Verify` with all `16` `HyperTwist.Browser.*` tests green again. The latest same-family truth-render follow-up on `2026-06-24` then rebuilt that same maintained validation root with `Result: Succeeded`, UnrealBuildTool `Total execution time: 172.52 seconds`, and exported `Saved\AutomationReports\Browser-XrNoGoRendered-Verify\index.json` with all `20` `HyperTwist.Browser.*` tests green again, explicitly covering both training-panel and coach-dashboard control-input detail-line visibility for the `No-Go` host decision. A later same-day post-build structured-boundary follow-up then rebuilt that same maintained validation root once more with `Result: Succeeded`, UnrealBuildTool `Total execution time: 2323.18 seconds`, and exported `Saved\AutomationReports\Browser-XrBoundaryStructured-PostBuild-Verify\index.json` with all `20` `HyperTwist.Browser.*` tests green again, now explicitly covering the stable decision-id and reopen-requirement fields on both control-input inspect surfaces alongside the sibling control/settings and control/profile seams. A later same-day `2026-06-25` parity follow-up then widened the same surface from general readiness truth into literal roster truth by rendering dedicated classic-cube pointer and action-shortcut lines, rebuilding the maintained validation root with `Result: Succeeded` at `5278.57 seconds` and exact-source rerun `70.76 seconds`, and exporting `Saved\AutomationReports\Browser-ControlRosterParity-Verify\index.json` with all `21` `HyperTwist.Browser.*` tests green, including both training-panel and coach-dashboard control-input surfaces plus the structured dashboard artifact seam. The latest same-family `2026-06-28` ownership-truth follow-up then tightened higher-dimensional readiness again by resolving the shipped `Magic120Cell` and `MagicCube5D` dedicated-family host, view-context, session, and interactive-scene surfaces explicitly by activation profile id instead of treating broad catalog validity as equivalent proof. That exact-source-state follow-up rebuilt maintained validation root `C:\HyperTwist_worktrees\phase10validate` with `Result: Succeeded`, UnrealBuildTool `Total execution time: 109.14 seconds`, then passed all three focused browser filters `TrainingPanel.ControlInputReadinessInspectSurface`, `CoachDashboard.ControlInputReadinessInspectSurface`, and `CoachDashboard.ControlSurfaceStructuredTextArtifacts`, so both the inspect surfaces and the rendered structured dashboard row now keep concrete family ownership ids such as `phase6c/magic120cell/runtime-host-surface` and `phase6c/magiccube5d/interactive-scene-surface` visible to operators. A later same-day bounded preferences-continuity follow-up then tightened the non-`XR` seam again without reopening the controller lane: the preferences line now resolves the first valid viewer camera-export artifact instead of trusting only the first listed id, keeps `artifact/camera-export-json` plus `immersive-training-session-recall-boundary` visible with recall-scope and preference-field counts, and preserves the honest boundary that packaged controller proof and broader XR completion are still not shipped. That exact-source continuity follow-up then rebuilt maintained validation root `C:\HyperTwist_worktrees\phase10validate` with `Result: Succeeded`, UnrealBuildTool `Total execution time: 3372.27 seconds`, and exported `Browser-PreferencesContinuity-20260628-HyperTwist.Browser.TrainingPanel.ControlInputReadinessInspectSurface`, `Browser-PreferencesContinuity-20260628-HyperTwist.Browser.CoachDashboard.ControlInputReadinessInspectSurface`, and `Browser-PreferencesContinuity-20260628-HyperTwist.Browser.CoachDashboard.ControlSurfaceStructuredTextArtifacts`, each with `index.json` `State=Success`, while the accepted unattended `Failed to create the web browser window.` dialog remained a non-blocking Windows editor lane artifact. The current same-family XR hardening follow-up then widened that same inspect truth again without widening the broader `No-Go` decision: the native/operator surface now also proves the dedicated vertical-adjust axis is present in project input config, and the XR preference line now keeps vertical-adjust plus pointer-length ownership explicit instead of burying those bounded controls inside the profile only. The current controller-settings continuation source now also carries `xr-openxr-controller-settings-owner/v1`, `xr-openxr-controller-rebinding-surface/v1`, `xr-openxr-controller-layout-default/v1`, exact field/input/layout counts, and explicit truth that packaged controller validation is the remaining reopen gate. |
| Native control/settings ownership inspect surface | Implemented now | landed first-party `2026-06-24` browser/native operator continuation | `UHyperTwistTrainingPanelWidget` and `UHyperTwistCoachDashboardWidget` now expose `FHyperTwistTrainingControlSettingsOwnershipInspectSurface`, including the shipped viewer camera-settings owner `tool/camera-settings`, the immersive-presence control contract, dedicated-family `magic120cell-focus-view-profile` and `magiccube5d-projection-view-profile` view ownership, higher-dimensional selector ownership, persisted generated-mode selector recall when a structurally valid launch request is present, and bounded XR/controller settings plus rebinding ownership truth while packaged proof remains unfinished. A later same-day structured-boundary hardening follow-up then carried the same `desktop-hosted-openxr-controller-widening-no-go` decision id plus the explicit reopen requirements for dedicated runtime owners, polished user-facing settings or rebinding ownership, and Windows packaged controller validation into this surface’s structured state as well, so control-settings diagnostics no longer have to prove the boundary only by substring matching their rendered detail line. The same primary reverse-SSH `localhost:22022` lane rebuilt maintained validation worktree `C:\HyperTwist_worktrees\phase10validate` on `2026-06-24` with `Result: Succeeded`, UnrealBuildTool `Total execution time: 4331.11 seconds`, and then exported `Saved\AutomationReports\Browser-ControlSettingsOwnership-Verify\index.json` with all `18` `HyperTwist.Browser.*` tests passing, including `CoachDashboard.ControlSettingsOwnershipInspectSurface`, `TrainingPanel.ControlSettingsOwnershipInspectSurface`, and the previously landed runtime plus control/input inspect seams. A later same-day selector-recall hardening follow-up then rebuilt that same maintained validation root again with `Result: Succeeded`, UnrealBuildTool `Total execution time: 4084.77 seconds`, and exported `Saved\AutomationReports\Browser-SelectorRecall-Verify\index.json` with all `20` `HyperTwist.Browser.*` tests passing, keeping the current control/settings proof aligned with the latest repository-backed selector-recall behavior. A later same-day post-build structured-boundary follow-up then rebuilt that same maintained validation root once more with `Result: Succeeded`, UnrealBuildTool `Total execution time: 2323.18 seconds`, and exported `Saved\AutomationReports\Browser-XrBoundaryStructured-PostBuild-Verify\index.json` with all `20` `HyperTwist.Browser.*` tests green again, now explicitly covering the stable decision-id and reopen-requirement fields on both control/settings inspect surfaces alongside the sibling control/input and control/profile seams. The latest same-family `2026-06-28` ownership-proof follow-up then tightened this settings seam again by resolving the active higher-dimensional session surface, active interactive-scene surface, dedicated-family session surface, dedicated-family interactive-scene surface, persistence-boundary id, and state-semantics id explicitly for both `Magic120Cell` and `MagicCube5D`, while also carrying concrete projection, symmetry, stereo, visibility, and focus tag counts plus persistence-readiness booleans in structured state instead of leaving that ownership implied by broad view-profile validity. That exact-source proof-hardening follow-up synced the tightened browser test source into the already-current maintained validation root, rebuilt it with `Result: Succeeded` and UnrealBuildTool `Total execution time: 168.35 seconds`, then passed focused browser proof for `HyperTwist.Browser.TrainingPanel.ControlSettingsOwnershipInspectSurface`, `HyperTwist.Browser.CoachDashboard.ControlSettingsOwnershipInspectSurface`, and `HyperTwist.Browser.CoachDashboard.ControlSurfaceStructuredTextArtifacts`, so both the inspect surfaces and the rendered structured dashboard row now keep exact family-owned ids such as `phase6c/magic120cell/dedicated-training-session-surface`, `phase6c/magic120cell/interactive-scene-surface`, `magic120cell-persistence-boundary`, `phase6c/magiccube5d/dedicated-training-session-surface`, and `phase6c/magiccube5d/family-owned-scene-state` visible to operators. A later same-day bounded preferences-continuity follow-up then tightened the same settings seam again without reopening native controller widening: the structured state now carries camera workflow, preview-state, export-artifact, immersive presence-surface, recall-scope, preference-field, and reset-surface counts together with explicit camera-continuity and immersive-session-recall readiness booleans; the rendered status text now distinguishes `missing`, `partial`, and `ready` ownership truth instead of collapsing those states; and the shipped `artifact/camera-export-json` plus `immersive-training-session-recall-boundary` ids now stay visible in both the training-panel and coach-dashboard settings detail lines. That exact-source continuity follow-up then rebuilt maintained validation root `C:\HyperTwist_worktrees\phase10validate` with `Result: Succeeded`, UnrealBuildTool `Total execution time: 3372.27 seconds`, and exported `Browser-PreferencesContinuity-20260628-HyperTwist.Browser.TrainingPanel.ControlSettingsOwnershipInspectSurface`, `Browser-PreferencesContinuity-20260628-HyperTwist.Browser.CoachDashboard.ControlSettingsOwnershipInspectSurface`, and `Browser-PreferencesContinuity-20260628-HyperTwist.Browser.CoachDashboard.ControlSurfaceStructuredTextArtifacts`, each with `index.json` `State=Success`, while the same accepted unattended `Failed to create the web browser window.` dialog remained non-blocking on the Windows editor lane. A later same-family `2026-06-30` degraded-state hardening follow-up then pulled that same readiness doctrine fully into the shared formatter layer itself, so absent higher-dimensional family ownership now renders as `missing` instead of being overstated as generic `partial`, one-sided view-versus-persistence lanes still render as `partial`, and both the dedicated family lines and the selector-ownership line now mask stale ids/counts while preserving the side of the lane that is actually ready. The current controller-settings continuation source now also carries `xr-openxr-controller-settings-owner/v1`, `xr-openxr-controller-rebinding-surface/v1`, `xr-openxr-controller-layout-default/v1`, exact field/input/layout counts, and explicit truth that packaged controller validation is the remaining reopen gate. |
| Native control/profile roster inspect surface | Implemented now | landed first-party `2026-06-24` browser/native operator continuation | `UHyperTwistTrainingPanelWidget` and `UHyperTwistCoachDashboardWidget` now expose `FHyperTwistTrainingControlProfileRosterInspectSurface`, keeping the actually shipped selectable native roster visible: classic keyboard profile `classic-wca-keyboard/v1` with `18` bindings plus the exact classic move roster, immersive-presence contract `immersive-training-presence-control-contract` with `3` intensity plus `3` reduced-distraction presets, dedicated-family `Magic120Cell` runtime/view ids `magic120cell-runtime-profile` and `magic120cell-focus-view-profile`, dedicated-family `MagicCube5D` runtime/view ids `magiccube5d-runtime-profile` and `magiccube5d-projection-view-profile`, the current `4` selectors in each dedicated-family roster, persisted generated-mode selector recall when a structurally valid launch request is present, and bounded XR controller settings/rebinding ownership truth while packaged proof remains unfinished. The rendered roster boundary now also states the fixed desktop-hosted `No-Go` decision on native OpenXR/controller widening instead of sounding like a merely pending generic settings packet. A later same-day structured-boundary hardening follow-up then carried the same `desktop-hosted-openxr-controller-widening-no-go` decision id plus its explicit reopen requirements into the roster surface’s structured state too, so native operator automation can prove the shipped roster boundary without depending only on rendered text. After hash-syncing the touched type/training/dashboard/test files into maintained validation worktree `C:\HyperTwist_worktrees\phase10validate`, the same primary reverse-SSH `localhost:22022` lane rebuilt the widened slice on `2026-06-24` with `Result: Succeeded`, UnrealBuildTool `Total execution time: 3606.23 seconds`, then exported `Saved\AutomationReports\Browser-ControlProfileRoster-Verify\index.json` with all `20` `HyperTwist.Browser.*` tests passing, including `CoachDashboard.ControlProfileRosterInspectSurface` and `TrainingPanel.ControlProfileRosterInspectSurface`. A later same-day selector-recall hardening follow-up then rebuilt that same maintained validation root again with `Result: Succeeded`, UnrealBuildTool `Total execution time: 4084.77 seconds`, and exported `Saved\AutomationReports\Browser-SelectorRecall-Verify\index.json` with all `20` `HyperTwist.Browser.*` tests passing again, now explicitly covering imported-request fallback plus active-deck precedence for repository-backed selector recall inside the training-panel and coach-dashboard roster surface. The latest same-family truth-render follow-up on `2026-06-24` then rebuilt that same maintained validation root with `Result: Succeeded`, UnrealBuildTool `Total execution time: 172.52 seconds`, and exported `Saved\AutomationReports\Browser-XrNoGoRendered-Verify\index.json` with all `20` `HyperTwist.Browser.*` tests green again, explicitly covering the roster detail-line visibility of the same fixed `No-Go` boundary. A later same-day post-build structured-boundary follow-up then rebuilt that same maintained validation root once more with `Result: Succeeded`, UnrealBuildTool `Total execution time: 2323.18 seconds`, and exported `Saved\AutomationReports\Browser-XrBoundaryStructured-PostBuild-Verify\index.json` with all `20` `HyperTwist.Browser.*` tests green again, now explicitly covering the stable decision-id and reopen-requirement fields on both control/profile inspect surfaces alongside the sibling control/input and control/settings seams. A later same-day `2026-06-25` parity follow-up then added the literal shipped classic move-roster line to that surface, mirrored it into dedicated coach-dashboard structured rows, rebuilt the maintained validation root with `Result: Succeeded` at `5278.57 seconds` and exact-source rerun `70.76 seconds`, and exported `Saved\AutomationReports\Browser-ControlRosterParity-Verify\index.json` with all `21` `HyperTwist.Browser.*` tests green, including both training-panel and coach-dashboard control/profile surfaces plus the structured dashboard artifact seam. The later same-family `2026-06-28` continuity follow-up then widened that roster seam again by carrying the active higher-dimensional scene id alongside the active activation, view-context, and session ids, while also resolving the first valid viewer camera-export artifact and keeping `artifact/camera-export-json` plus `immersive-training-session-recall-boundary` visible with recall-scope and preference-field counts through both the native detail line and a dedicated coach-dashboard structured row. The authoritative short-root recovery lane on `C:\HTpp` then re-synced the exact touched Unreal files, rebuilt the exact-source state with `Result: Succeeded` and UnrealBuildTool `Total execution time: 2374.44 seconds`, and exported both `Browser-ControlProfileContinuityParity-20260628-HyperTwist.Browser.TrainingPanel.ControlProfileContinuityParity` and `Browser-ControlProfileContinuityParity-20260628-HyperTwist.Browser.CoachDashboard.ControlProfileContinuityArtifacts` with `Result={Success}`, while the repeated `Failed to create the web browser window.` dialog remained a non-blocking unattended editor artifact. A later exact-source short-root recovery proof on `2026-06-29` then rebuilt the same touched state again with `Result: Succeeded` and UnrealBuildTool `Total execution time: 78.51 seconds`, re-exported `Saved\AutomationReports\ControlProfileContinuity-Rerun` with `HyperTwist.Browser.CoachDashboard.ControlProfileContinuityArtifacts`, `HyperTwist.Browser.TrainingPanel.ControlProfileContinuityParity`, and `HyperTwist.Browser.ControlProfileContinuityStateFormatting` all `Result={Success}`, and also re-exported `Saved\AutomationReports\ContinuityStateFormatting-Rerun` with the wider shared continuity-formatting trio green, so the roster-parity and shared continuity-helper seams are both grounded in current exact-source Windows proof rather than only the earlier broader maintained-root evidence. A final maintained-root exact-source hardening follow-up later that same day then tightened the shared continuity formatter so absent readiness masks stale ids and counts instead of leaking carried-over values, rebuilt `C:\HyperTwist_worktrees\phase10validate` with `Result: Succeeded` and UnrealBuildTool `Total execution time: 3325.07 seconds`, and exported `Continuity-CountMasking-20260629-*` with `HyperTwist.Browser.ControlProfileContinuityStateFormatting`, `HyperTwist.Browser.TrainingPanel.ControlProfileContinuityParity`, and `HyperTwist.Browser.CoachDashboard.ControlProfileContinuityArtifacts` all `Result={Success}`, keeping the shipped roster-continuity truth grounded in current maintained-root degraded-state proof as well. The current controller-settings continuation source now also carries `xr-openxr-controller-settings-owner/v1`, `xr-openxr-controller-rebinding-surface/v1`, `xr-openxr-controller-layout-default/v1`, exact field/input/layout counts, and explicit truth that packaged controller validation is the remaining reopen gate. |
| Native XR project-plugin posture inspect truth | Implemented now | landed first-party `2026-06-25` browser/native operator continuation | All three native control/input, control/settings, and control/profile inspect surfaces now expose the current project `OpenXR` plugin enabled/disabled fact in both structured state and rendered operator lines, so project-level motion-controller groundwork no longer masquerades as an enabled `OpenXR` shipping posture. The same primary reverse-SSH `localhost:22022` lane rebuilt the exact-source state on maintained validation root `C:\HyperTwist_worktrees\phase10validate` with `Result: Succeeded`, UnrealBuildTool `Total execution time: 99.38 seconds`, then exported `Saved\AutomationReports\Browser-XrPluginProjectPosture-Verify\index.json` with all `20` `HyperTwist.Browser.*` tests green across the training-panel and coach-dashboard input/settings/profile seams. |
| Optional full-browser client path above Unreal backend authority | Deep-source grounded retained | landed first-party `Phase 8B` preparation packet + spec/evidence continuation + backend-contract continuation | This branch remains a spec-only first-party option: a browser-owned rendering and input shell may sit above explicit Unreal backend seams while Unreal remains authoritative for puzzle, training, timer, replay, and persistence state. The current continuation now fixes the allowed seam families to catalog, session, action, state, continuity push, replay, persistence status, and runtime health, then further fixes transport-neutral operation labels, minimum identity or freshness requirements, and the owned state/runtime payload anchors that any later browser-client backend implementation must preserve. The landed embedded browser/CEF shell remains the current shipping posture, and this branch stays separate from any native `MagicTile` behavior or renderer widening. |
| Rewritten browser spatial scene and renderer reference grounding | Implemented now | `mrdoob/three.js` retained permissive lane + first-party current code | Current live `Browser 3D and XR Support` reference side includes one rewritten first-party target grounded in retained `mrdoob/three.js`: the browser spatial scene and renderer contract. This does not displace the landed `Phase 3R-F` first-party browser spatial owner trio or absorb the adjacent `react-three-fiber` renderer-bridge and `xr` session slices. |
| Rewritten React-side browser renderer and event-bridge grounding | Implemented now | `pmndrs/react-three-fiber` retained permissive lane + first-party current code | Current live `Browser 3D and XR Support` reference side includes one rewritten first-party target grounded in retained `react-three-fiber`: the React scene renderer and event bridge. This does not displace the landed `Phase 3R-F` first-party browser spatial owner trio or absorb the adjacent `three.js` scene substrate and `xr` session slices. |
| Rewritten browser XR session and immersive-interaction grounding | Implemented now | `pmndrs/xr` retained permissive lane + first-party current code | Current live `Browser 3D and XR Support` reference side includes one rewritten first-party target grounded in retained `pmndrs/xr`: the browser XR session and immersive interaction contract. This does not displace the landed `Phase 3R-F` first-party browser spatial owner trio or absorb the adjacent `three.js` scene substrate and `react-three-fiber` renderer-bridge slices. |
| Rewritten world-anchored spatial UI grounding | Implemented now | `pmndrs/uikit` retained permissive lane + first-party current code | Current live `Browser 3D and XR Support` reference side includes one rewritten first-party target grounded in retained `pmndrs/uikit`: browser spatial UI and world-anchored controls. This does not displace the landed `Phase 3R-F` first-party browser spatial owner trio or absorb the adjacent `postprocessing` effect-boundary and `drei` helper-stack slices. |
| Rewritten browser post-processing and effect-boundary grounding | Implemented now | `pmndrs/postprocessing` retained permissive lane + first-party current code | Current live `Browser 3D and XR Support` reference side includes one rewritten first-party target grounded in retained `pmndrs/postprocessing`: the browser post-processing and effect boundary. This does not displace the landed `Phase 3R-F` first-party browser spatial owner trio or absorb the adjacent `drei` helper-stack and `uikit` spatial-UI slices. |
| Rewritten browser helper-stack and utility grounding | Implemented now | `pmndrs/drei` retained permissive lane + first-party current code | Current live `Browser 3D and XR Support` reference side includes one rewritten first-party target grounded in retained `pmndrs/drei`: the browser spatial helper and utility stack. This does not displace the landed `Phase 3R-F` first-party browser spatial owner trio or absorb the adjacent `zustand` state-motion and `postprocessing` effect-boundary slices. |
| Rewritten browser state, gesture, and motion grounding | Implemented now | `pmndrs/zustand` retained permissive lane + first-party current code | Current live `Browser 3D and XR Support` reference side includes one rewritten first-party target grounded in retained `pmndrs/zustand`: the browser spatial state, gesture, and motion contract. This does not displace the landed `Phase 3R-F` first-party browser spatial owner trio or reopen the broader support-cluster implementation packet. |

## Feature families

The rest of this registry is normalized by feature family rather than donor
repo.

### 1. Puzzle runtime, notation, and replay

| Feature | Status | Primary authority | Notes |
|---|---|---|---|
| Native puzzle-state runtime | Implemented now | first-party runtime + landed donor packets | Core product identity. |
| Classic-cube playable runtime loop | Implemented now | first-party current code + landed timer/training substrate | First-party `AHyperTwistClassicCubeActor`, `AHyperTwistClassicCubeGameMode`, `AHyperTwistClassicCubePlayerController`, `AHyperTwistClassicCubeOrbitPawn`, and `UHyperTwistClassicCubeHUDWidget` now own the bounded classic-cube scramble/play/timer/solve loop with left-click, right-click, touch, middle-mouse drag orbit, scroll-wheel zoom, GUI or keyboard fresh-attempt restart, solved-state submission, active-cube orbit focus, solver hint glow, follow-along guidance, hold-to-talk voice commands, voice-profile cycling, and coach narration in code. Dedicated `L_HyperTwist_ClassicTraining` and `L_HyperTwist_FollowAlongTraining` maps plus the authored classic-cube material family are now source-controlled through `scripts/Invoke-HyperTwistClassicCubeMapAuthoring.ps1`, `scripts/hypertwist_author_classic_cube_training_maps.py`, `scripts/Invoke-HyperTwistClassicCubePackage.ps1`, and `scripts/Launch-HyperTwistClassicCubePackage.ps1`. That route was first package-proven on `2026-06-12` through the fallback reverse-SSH `localhost:22023` lane and then package-proven again on `2026-06-13` through the primary reverse-SSH `localhost:22022` lane on isolated worktree `C:\HyperTwist_worktrees\phase10validate`, including packaged smoke boots on both training maps. The maintained package helper now also emits aggregate validation JSON plus per-map smoke JSON under the archived `validation\` tree, rejects missing or unparseable smoke JSON, rejects non-`passed` smoke results, and rejects unexpected `mapUrl` drift before the package lane is declared green. That stricter helper/report posture was rechecked during the `2026-06-18` Phase `10B/10C` hardening slice after the replay/leaderboard continuation repairs and the refreshed `20`-test Windows automation packet, then package-revalidated again through archive `C:\HyperTwist_worktrees\phase10validate_packaged_phase10b10c_repair4` with explicit runtime-only cooker exclusions `-DisablePlugins=MovieRenderPipeline` plus `-SkipCookingEditorContent`, aggregate validation JSON `result: passed`, and both packaged smoke maps green. |
| Classic-cubing semantic/runtime adapter | Implemented now | landed `cubing/cubing.js` packet | Live adapter family. |
| Classic-cubing semantic, bridge, and `MPL`-boundary reference grounding | Implemented now | `cubing/cubing.js` retained boundary-sensitive lane + first-party current code | Current live `Classic Cubing Semantics and Runtime` reference side includes seven rewritten first-party contract/reference targets grounded in `cubing/cubing.js`: semantics, geometry, viewer adapter, device boundary, search contract, Melinda bridge, and explicit `MPL` compliance-boundary notes. This does not displace the landed `Phase 4R-A` first-party owner lane, the separate `cubing/twisty.js` replay shell lane, the separate `cubing/alg.js` parser/AST lane, or the explicit practical `MPL` path and notice-retention boundary. |
| Seeded competition scramble workflow and lightweight scramble-operator shell adjuncts | Deep-source grounded retained | `cubing/cubing.js` retained lane + `cubing/mark3` / `cubing/scramble.cubing.net` successor evaluation | Source-backed successor surfaces sharpen competition-spec workflow and operator-shell expectations above the retained scramble and visualization seams, but they do not displace `cubing/cubing.js` or `cubing/twisty.js`; `scramble-display` remains comparison-only. |
| Replay shell and timeline | Implemented now | landed `cubing/twisty.js` bounded packets | First-party `HyperTwistSimulation` now owns the bounded replay-player shell, cursor/timeline transport, adapter/bootstrap, and local visualization or fallback presentation contract grounded in `cubing/twisty.js`; classic-cubing semantics remain with `cubing/cubing.js`, parser and AST ownership remain with `cubing/alg.js`, and broader browser support ownership stays with the landed browser lanes. |
| Classic-cube runtime replay capture, JSON persistence, and playback reconstruction | Implemented now | first-party current code + landed replay/training substrate | Current classic-cube runtime records move and state-snapshot replay events with timestamps during live solves, persists replay packets as `.json` through `UHyperTwistReplayPersistenceLibrary`, restores replay metadata into `AHyperTwistClassicCubeGameMode`, and reconstructs saved move streams for local playback in current code. Replay save, load, and viewer-import paths now normalize schema-light packets by repairing packet version, replay/session ids, duplicate or missing event ids, out-of-order or non-monotonic event sequences, monotonic timestamps, and derived replay summary before the packet is reused. The primary reverse-SSH `localhost:22022` Windows validation lane then refreshed the full `HyperTwist.Integration.ClassicCube` suite on isolated worktree `C:\HyperTwist_worktrees\phase10validate` on `2026-06-13`, passing `ReplayPersistenceRoundTrip`, `ReplayPersistenceNormalization`, `ReplayViewerLoad`, and `RuntimeReplaySmoke` alongside the related leaderboard integration cases, and then refreshed the hardened `ReplayPersistenceSequenceRepair` coverage again on `2026-06-18` inside the green `20`-test Phase `10B/10C` packet. |
| Classic-cube Unreal-native replay media export | Implemented now | first-party current code + landed replay/training substrate | Current classic-cube export code now owns `MovieRenderQueue` plan generation, authoritative `LS_HyperTwist_ClassicReplayCapture` sequence authoring, Python-host executor routing, reverse-SSH-safe offscreen render invocation, canonical MP4/still/share-card output normalization, and aggregate export-report generation in current code. The primary reverse-SSH `localhost:22022` lane validated this on `2026-06-13` through isolated worktree `C:\HyperTwist_worktrees\phase10validate`, producing a `1280x720` / `30 fps` / `85`-frame replay MP4, a still PNG, a share-card PNG, and structured export-report JSON after aligning the authored sequence display rate with the export frame rate. |
| Media-export, embedded-playback, and replay-explainer reference grounding | Implemented now | `remotion-dev/remotion` retained restrictive-custody lane + first-party current code | Current live `Media Export and Replay Explainers` reference side includes five rewritten first-party contract/reference targets grounded in `remotion-dev/remotion`: embedded playback, render orchestration, media parser, explainer-studio preview/output registration, and explicit commercial-license/package-split compliance-boundary notes. This does not displace the landed `Phase 4R-F` first-party owner lane, the broader browser/spatial/media adjunct family, or the explicit package-split commercial boundary. Current routing correction: preserve the already-landed first-party outputs, but treat future donor-backed widening from `remotion-dev/remotion` as restrictive-custody and prefer Unreal-native export for fresh shipping work. |
| Browser-viewer, compact-editor, export, and docs-boundary grounding | Implemented now | `google/model-viewer` retained permissive lane + first-party current code | Current live `Browser Viewer and Asset QA` reference side includes five rewritten first-party contract/reference targets grounded in the root `google/model-viewer` lane: viewer embed, compact editor/inspection, snippet/export, renderer comparison/fidelity, and docs/demo separation. The subordinate `space-opera`, `modelviewer.dev`, and `render-fidelity-tools` source attributions are absorbed here as support-only contributors rather than separate live owner lanes. This does not displace the landed `Phase 3R-D` first-party owner lane, the separate `KhronosGroup/glTF-Sample-Viewer` standards-aware QA lane, or the already explicit `google/model-viewer/packages/shared-assets` boundary-sensitive fixture lane. |
| Standards-aware asset-validation and statistics grounding | Implemented now | `KhronosGroup/glTF-Sample-Viewer` retained permissive support lane + first-party current code | Current live `Browser Viewer and Asset QA` reference side includes one rewritten first-party target grounded in `KhronosGroup/glTF-Sample-Viewer`: standards-aware asset validation and statistics. This does not displace the landed `Phase 3R-D` first-party browser viewer owner, the separate root `google/model-viewer` viewer/reference lane, or the already explicit shared-assets boundary-sensitive fixture lane. |
| Browser-viewer shared-asset fixture and provenance grounding | Implemented now | `google/model-viewer/packages/shared-assets` retained boundary-sensitive lane + first-party current code | Current live `Browser Viewer Shared Asset Fixtures` reference side includes five rewritten first-party contract/reference targets grounded in `google/model-viewer/packages/shared-assets`: fixture allowlist, `CC0` environment matrix, provenance-boundary review split, fixture-refresh pattern, and contributed geometry smoke-test boundary notes. This does not displace the landed `Phase 4R-C` first-party owner lane, the broader `google/model-viewer` browser viewer lane, or the explicit mixed per-asset review and shipping boundary. |
| Alternative browser viewer/editor and substrate comparison lane | Deep-source grounded retained | `pissang/claygl` + `pissang/clay-viewer` retained comparison lane | Renderer/scene/camera/control substrate plus compact viewer/editor patterns remain retained only as optional browser comparison context behind the landed `three.js` / `react-three-fiber` / `xr` and `google/model-viewer` owners. `3R-G` remains deferred unless a real browser-side gap is proven. |
| Algorithm/training semantic lane | Implemented now | landed `cubing/alg.js` bounded packets | First-party `HyperTwistAlgorithm/*` now owns the bounded parser, AST, traversal, validation, keyboard-mapping, and share/interchange contract grounded in `cubing/alg.js`; current training-runtime parse/store/serialize usage remains a consumer seam above that owner lane rather than proof that the lane is still open. |
| Melinda `2x2x2x2` state core and flat teaching projection | Implemented now | landed `HactarCE/2x2x2x2-Scrambler` bounded packets | First-party `HyperTwistCore` now owns the bounded Melinda state legality, parity or handedness and twist validation, move-family application, random-state generation, scramble-packet construction, and flat debug or teaching projection contract grounded in the restrictive lane; broader higher-dimensional runtime ownership remains with adjacent live lanes and `magiccube4d` remains legacy reference context only. |
| Melinda `2x2x2x2` visible cell-first runtime and interaction packet | Implemented now | first-party current code above the landed Melinda core | First-party `HyperTwistSimulation` now owns exact Melinda cell-turn transform construction, the stable `melinda-2x2x2x2-cell-first-projection-v1` packet, procedural `AHyperTwistMelindaProjectionActor` / `AHyperTwistMelindaProjectionGameMode` / `AHyperTwistMelindaProjectionPlayerController` / `AHyperTwistMelindaProjectionOrbitPawn` surfaces, solved-or-random state refresh, and targeted `Phase 6A` automation proof. This widens the already-landed Melinda core into a visible interactive `2x2x2x2` lane without silently claiming `3x3x3x3`, occlusion-management, or broader higher-dimensional runtime ownership. |
| Virtual `3x3x3x3` visible slice runtime and keyboard interaction packet | Implemented now | first-party current code above the landed Melinda core and `Hyperspeedcube` catalog lane | First-party `HyperTwistSimulation` now owns the bounded exact `hypercube/3x3x3x3` runtime state, the stable `hypercube-3x3x3x3-visible-slice-projection-v1` contract, procedural `AHyperTwistVirtual3333ProjectionActor` / `AHyperTwistVirtual3333ProjectionGameMode` / `AHyperTwistVirtual3333ProjectionPlayerController` / `AHyperTwistVirtual3333ProjectionOrbitPawn` surfaces, keyboard slice-axis or layer or rotation-axis twist control, optional translucent shell rendering, scene-context composition, and targeted `Phase 6B` automation proof. This widens the owned hyper runtime into a visible interactive `3x3x3x3` lane without silently claiming `Magic120Cell`, `MagicCube5D`, or broader non-hypercube topology ownership. |
| Readable classic-cube state/history and beginner-helper benchmark | Deep-source grounded retained | `vwcwong/CubeSim` retained clean-room benchmark lane | Retained as `A1 + R4 + F2` only for a small renderer-independent classic-cube state/history split, scramble parse or invert behavior, and beginner `LBL` decomposition benchmark for later clean-room lesson/debug/helper use. This does not displace the first-party canonical replay packet, training attempt/solve/review history, or the bounded classic-cube `Phase 6R-Q/R/S` explanation and correction shells. |
| Large-`N` classic-cube center/edge/parity strategy | Deep-source grounded retained | `ShellPuppy/RCube` retained benchmark/oracle lane | Retained as `A1 + R4 + F2` only for large-`N` classic-cube center-stage planning, edge-pairing/parity handling, and virtual-rotation strategy. This does not displace the landed `Hyperspeedcube`, `MagicTile`, `Magic120Cell`, or `MagicCube5D` higher-dimensional runtime families, and it does not reopen the bounded classic-cube `Phase 6R-Q/R/S` shell/state seams. |
| Hyper puzzle catalog | Implemented now | `Hyperspeedcube` bounded packet | Current realized hyper-puzzle entry slice. |
| Hyper notation and replay-log serialization | Implemented now | landed `Hyperspeedcube` `Phase 6R-K` | Retained notation parse/format and log-serialization boundary are live. |
| Hyper replay verification and solve-proof diagnostics | Implemented now | landed `Hyperspeedcube` `Phase 6R-L` | Retained replay verification, timestamp proof routing, and bounded solve diagnostics are live. |
| Hyper stats-shape and solve-record boundary | Implemented now | landed `Hyperspeedcube` `Phase 6R-M` | Retained PB categories, solve-record qualifiers, and bounded solve-proof result shape are live. |
| Hyper puzzle DSL authoring | Implemented now | landed `Hyperspeedcube` `Phase 6R-N` | Retained Hyperpuzzlescript authoring, module/evaluation boundary, and bounded diagnostics are live. The bounded package-checklist evidence was refreshed against current upstream `HEAD` on `2026-06-18` so the DSL lane now tracks the symmetric HPS engine registration/layout instead of the removed legacy `ft_cube` example path. |

### 2. Physical recognition and reconstruction

| Feature | Status | Primary authority | Notes |
|---|---|---|---|
| Calibration profile and ordered face observation | Implemented now | `qbr` bounded packet | Live bounded recognition intake. |
| Classic-cube webcam shell | Implemented now | `qbr` bounded packet | Live first-party webcam shell profile and shell-state composition above the bounded recognition intake. |
| Locale-aware solve-guidance routing overlay | Implemented now | `qbr` bounded packet + landed `rubix-cube-solver` solve-explanation seam | Live first-party locale-routing contract, supported-locale metadata, qbr-grounded starting-orientation reminder, and bounded locale-presentation metadata above the webcam and solve-explanation stack. |
| Bundled-font review boundary | Implemented now | `qbr` bounded packet | Live first-party font-review profiles, per-locale review-descriptor routing, and active shell / solve-explanation review metadata above the bounded locale-routing and locale-presentation seams. This keeps donor font redistribution and standalone multilingual rendering deferred. |
| Committed-face reconstruction session | Implemented now | `rubix-cube-solver` bounded packet | Live bounded reconstruction seam. |
| Browser recognition shell | Implemented now | `rubix-cube-solver` bounded packet | Live browser session-state, websocket transport routing, and manual-edit handoff above the bounded reconstruction seam. |
| Bounded solve explanation/recommendation shell | Implemented now | `rubix-cube-solver` bounded packet | Live stage-ladder recommendation state above the bounded browser recognition shell. This is not a generalized solver backend. |
| Bundled browser visualization asset review boundary | Implemented now | `rubix-cube-solver` bounded packet | Live first-party browser-asset review profiles, twistysim review-descriptor routing, and active browser-shell review metadata above the bounded browser recognition shell. This keeps donor asset redistribution and broad playback/runtime ownership deferred. |
| Provider-backed recognition service contract | Implemented now | first-party recognition client surfaces | First-party normalized recognition session boundary is real. |
| Multilingual recognition guidance shell rendering and font shipping | Deep-source grounded retained | `qbr` retained remainder | Kept deferred until a font-safe and provenance-safe shipping path is explicit. The landed locale-aware routing, locale-presentation, and bundled-font review seams do not by themselves authorize bundled-font redistribution or full standalone multilingual shell rendering. |
| Recognition-comparison adjunct boundary | Deep-source grounded retained | `cahidenes/rubiks-cube-solver` + `tentone/rubix-solver` retained adjunct lane | Narrow face-placement, cube-string cross-check, quad sorting, square-mask color sampling, center-color face labeling, and native face/state comparison value remain retained only behind the landed `qbr`, `rubix-cube-solver`, and first-party correction-stack owners. No default widening packet is open. |
| Multi-face correction/explanation shell | Implemented now | first-party recognition/training surfaces | Current bounded correction profile, contradiction-aware correction state, accepted-resolution ledger, and correction-explanation / solve-unlock shell are live above the landed `Phase 6R-O`, `Phase 6R-P`, `Phase 6R-Q`, `Phase 6R-R`, `Phase 6R-S`, and `Phase 6R-AT` seams. Bundled-asset, generalized solver-backend, and broad playback/runtime widening remain deferred. |
| Compact classic-cube solver correctness and heuristic-search oracle | Deep-source grounded retained | `brownan/Rubiks-Cube-Solver` retained lane + `efrantar/rob-twophase` comparator | Broad solver-backend ownership remains non-live. `brownan` remains the primary compact correctness and heuristic-table oracle, while `efrantar` remains the retained metric, pruning, robot-execution, and performance comparator. |
| First-party learned heuristic search and `ADI` experimentation profile | Implemented now | landed first-party `Phase 6R-AV` packet grounded in retained `yakupbilen` benchmark surfaces | Current bounded first-party `54`-sticker experiment profile, `ADI` generation boundary, offline neural-search benchmark boundary, and attribution boundary are live. This does not displace `qbr` or `rubix-cube-solver` for live perception/reconstruction ownership, and it does not displace `brownan` or `efrantar` for correctness/performance oracle ownership. |
| First-party learned-search sequence-policy and search-budget refinement | Implemented now | landed first-party `Phase 6R-AW` packet grounded in retained `yakupbilen` benchmark surfaces | Current bounded first-party anti-cancellation sequence policy, solved-state inclusion and weighting posture, frontier-budget policy, iteration/time-cap search posture, and benchmark checkpoint-clone boundary are live above the landed `Phase 6R-AV` experimentation seam. This does not displace live replay ownership, `qbr` / `rubix-cube-solver` recognition ownership, or `brownan` / `efrantar` oracle ownership. |
| First-party learned-search node identity and state-expansion boundary | Implemented now | landed first-party `Phase 6R-AX` packet grounded in retained `yakupbilen` benchmark surfaces | Current bounded first-party flattened-byte node hashing, parent and move lineage posture, closed-node shallower-depth replacement policy, vectorized `12`-way successor expansion, solved-state goal tagging, and offline-only reward-scan boundary are live above the landed `Phase 6R-AV` and `Phase 6R-AW` seams. This does not displace replay ownership, `qbr` / `rubix-cube-solver` recognition ownership, or `brownan` / `efrantar` oracle ownership. |
| First-party learned-search frontier scoring and solution unwind boundary | Implemented now | landed first-party `Phase 6R-AY` packet grounded in retained `yakupbilen` benchmark surfaces | Current bounded first-party batched frontier pop windows, weighted `f`-score depth penalty, one-hot categorical heuristic input shaping, no-grad evaluation posture, parent-chain solution unwind, clear-seq normalization, and iteration or timeout reporting are live above the landed `Phase 6R-AV` through `Phase 6R-AX` seams. This does not displace canonical replay ownership, `qbr` / `rubix-cube-solver` recognition ownership, or `brownan` / `efrantar` oracle ownership. |
| First-party learned-search value-network shape and generator-sync boundary | Implemented now | landed first-party `Phase 6R-AZ` packet grounded in retained `yakupbilen` benchmark surfaces | Current bounded first-party flattened-input value-network shape, `4096-2048-512` linear stack, ReLU ladder, Xavier and zero-bias init posture, tau-weighted generator refresh, and device-aware parameter sync semantics are live above the landed `Phase 6R-AV` through `Phase 6R-AY` seams. This does not displace deployed model serving ownership, `qbr` / `rubix-cube-solver` recognition ownership, or `brownan` / `efrantar` oracle ownership. |
| Learned heuristic search and `ADI` state-generation research benchmark | Deep-source grounded retained | `yakupbilen/drl-rubiks-cube` retained research lane | Retained for `54`-sticker transition encoding, anti-cancellation move-sequence generation, `ADI` state generation, batched neural `A*` search experiments, compact node identity and dedupe posture, vectorized successor expansion, frontier scoring, solution unwind, value-network shape, generator refresh, and small value-network research. The landed first-party `Phase 6R-AV` through `Phase 6R-AZ` lane now uses that benchmark slice explicitly without promoting it into live perception/reconstruction or correctness/performance oracle ownership. |

### 3. Training, coaching, and progression cockpit

| Feature | Status | Primary authority | Notes |
|---|---|---|---|
| Training sessions, method drills, and coaching dashboard | Implemented now | first-party training/coaching surfaces | Current live cockpit anchor. |
| Follow-up templates, session queues, and coach summaries | Implemented now | first-party current code | Real first-party orchestration surface. |
| Algorithm-training shell, set/subset corpus, and smartcube-capable drill foundation | Implemented now | landed `tao-yu/Alg-Trainer` preserve lane + first-party training stack | Current live algorithm-training foundation remains grounded in the landed permissive `Alg-Trainer` preserve lane for broad case-corpus breadth, set/subset drill structure, timer/reveal/scramble/virtual-cube flow, and smartcube-capable algorithm drill posture. This does not displace the first-party review-plan, queue, or follow-up orchestration family, nor the landed `cube_trainer` persisted-coaching slice. |
| Persisted coaching, weighted sampling, and BLD-domain session modeling | Implemented now | landed `Lykos/cube_trainer` preserve lane + first-party training stack | Current live persistence-heavy coaching adjunct remains grounded in the landed permissive `cube_trainer` preserve lane for weighted sampling, method exploration, and BLD-domain training-session logic. This does not displace the broader `Alg-Trainer` algorithm-shell/case-corpus foundation, the `KubeTimr` timer substrate, or the current first-party trainer-shell and follow-up orchestration union. |
| Cross-planning scramble ladder and CFOP cross micro-drill progression | Implemented now | landed `newyork-anthonyng/rubiks-cross-trainer` preserve lane + first-party training stack | Current live cross-planning track remains grounded in the landed permissive `rubiks-cross-trainer` row for its explicit `1`-move through `8`-move scramble ladder and narrow cross-drill corpus. This does not displace the broader `Alg-Trainer` foundation, the `cube_trainer` persistence-heavy coaching slice, or the current first-party trainer-shell and review-plan orchestration union. |
| Advanced `5-style` edge-cycle and blindfold micro-drill progression | Implemented now | landed `abunickabhi/5style-Trainer` preserve lane + first-party training stack | Current live advanced `5-style` / BLD micro-drill track remains grounded in the landed permissive `5style-Trainer` row for narrow mover-subset drilling, timed reveal flow, and high-skill edge-cycle practice. This does not displace the broader `Alg-Trainer` foundation, the `cube_trainer` persistence-heavy coaching slice, or the current first-party trainer-shell and follow-up orchestration union. |
| Roux method-stage, blockbuilding, and generated stage-trainer family | Implemented now | landed `onionhoney/roux-trainers` clean-room preserve lane + first-party training stack | Current live Roux and blockbuilding family remains grounded in the landed restrictive clean-room `roux-trainers` row for static case decks, generated stage-trainer surfaces, and method-stage drill structure. This does not displace the broader `Alg-Trainer` foundation, the `cube_trainer` persistence-heavy coaching slice, or the current first-party trainer-shell and review-plan orchestration union, and it does not relax restrictive governance for later rows. |
| Guided beginner lesson-state and stepwise pedagogy benchmark | Deep-source grounded retained | `AviKaufman/Rubix-cube-trainer` retained clean-room benchmark lane | Retained as `A1 + R4 + F2` only for named beginner milestones, oversatisfied-step explanation, bounded step help, and manual-turn/tutorial coherence on a live cube surface. This does not displace the first-party training-session, method-drill, coaching queue/follow-up, or bounded classic-cube `Phase 6R-Q/R/S` explanation and correction seams. |
| Guided task-planner and focus-playback benchmark | Deep-source grounded retained | `alinen/cube` retained clean-room benchmark lane | Retained as `A1 + R4 + F2` only for a separable lesson-task graph, bounded task-local planner, focus-target cueing, and queued move demonstration on a visible cube surface. This does not displace the first-party training-session, method-drill, coaching queue/follow-up, canonical replay, or bounded classic-cube `Phase 6R-Q/R/S` explanation and correction seams. |
| Blindfold memo attempt and validation benchmark | Deep-source grounded retained | `ambisinister/blindsolve` retained clean-room benchmark lane | Retained as `A1 + R4 + F2` only for a narrow blindfold memo attempt-phase loop, conceal/reveal validation, letter-pair token entry, parity-aware memo expectation, and lightweight repeat cadence. This does not displace the first-party timing-policy templates, coaching-memory/follow-up surfaces, replay-verification blindfold event taxonomy, or the broader memory doctrine. |
| Smartcube-aware practice-shell and review/SRS UX comparison | Deep-source grounded retained | `poliva/cubedex` restrictive reference row | Retained as `A1 + R4 + F2` only for smartcube-aware practice-shell comparison, offline-first drill UX composition, review/SRS workflow presentation, recognition-versus-execution timing presentation, and local stats/history comparison. This does not displace the current first-party training-session, review-plan, coaching, `KubeTimr` timer substrate, `CubeDesk` smart-device workflow composition, or the landed permissive trainer-foundation lanes. |
| Scenic virtual training environments and focus-presence shells | Implemented now | landed first-party `Phase I-A` through `Phase I-E` scaffold | Current code now owns the first bounded HyperTwist-native immersive foundation, focus-presence, teaching, reactive-cue, and hardening slices: scenic environment profile, legibility-first lighting preset boundary, calm ambient-audio boundary, stable puzzle/replay/coach world anchors, intensity and reduced-distraction controls, comfort/vignette posture, seated-standing posture variants, session-local environment recall, coach cue anchors, ghost targets, replay emphasis, lesson-state spotlighting, session-state transition cues, pacing-aware lighting and audio responses, study-versus-challenge differentiation, comfort-safe transition rules, accessibility-legibility review, performance-budget posture, and reduced-effects fallback modes. This remains a training/runtime lane rather than a generic virtual desktop shell. |
| Replay integrity and validation benchmark foundations | Implemented now | landed first-party `Phase J-A`, `Phase J-B`, `Phase J-C`, `Phase J-D`, `Phase J-E`, `Phase J-F`, `Phase J-G`, `Phase J-H`, `Phase J-I`, `Phase J-J`, `Phase J-K`, `Phase J-L`, `Phase J-M`, `Phase J-N`, `Phase J-O`, `Phase J-P`, `Phase J-Q`, `Phase J-R`, `Phase J-S`, `Phase J-T`, `Phase J-U`, `Phase J-V`, `Phase J-W`, `Phase J-X`, `Phase J-Y`, `Phase J-Z`, `Phase J-AA`, `Phase J-AB`, `Phase J-AC`, `Phase J-AD`, `Phase J-AE`, `Phase J-AF`, `Phase J-AG`, `Phase J-AH`, `Phase J-AI`, `Phase J-AJ`, `Phase J-AK`, `Phase J-AL`, `Phase J-AM`, `Phase J-AN`, `Phase J-AO`, `Phase J-AP`, `Phase J-AQ`, `Phase J-AR`, `Phase J-AS`, `Phase J-AT`, `Phase J-AU`, `Phase J-AV`, `Phase J-AW`, `Phase J-AX`, `Phase J-AY`, `Phase J-AZ`, `Phase J-BA`, `Phase J-BB`, `Phase J-BC`, `Phase J-BD`, `Phase J-BE`, `Phase J-BF`, `Phase J-BG`, `Phase J-BH`, `Phase J-BI`, `Phase J-BJ`, `Phase J-BK`, `Phase J-BL`, `Phase J-BM`, `Phase J-BN`, `Phase J-BO`, `Phase J-BP`, `Phase J-BQ`, `Phase J-BR`, `Phase J-BS`, `Phase J-BT`, `Phase J-BU`, `Phase J-BV`, `Phase J-BW`, `Phase J-BX`, `Phase J-BY`, `Phase J-BZ`, `Phase J-CA`, `Phase J-CB`, `Phase J-CC`, `Phase J-CD`, `Phase J-CE`, `Phase J-CF`, `Phase J-CG`, `Phase J-CH`, `Phase J-CI`, `Phase J-CJ`, `Phase J-CK`, `Phase J-CL`, `Phase J-CM`, `Phase J-CN`, `Phase J-CO`, `Phase J-CP`, `Phase J-CQ`, `Phase J-CR`, `Phase J-CS`, `Phase J-CT`, `Phase J-CU`, `Phase J-CV`, `Phase J-CW`, `Phase J-CX`, `Phase J-CY`, `Phase J-CZ`, `Phase J-DA`, `Phase J-DB`, `Phase J-DC`, `Phase J-DD`, `Phase J-DE`, `Phase J-DF`, `Phase J-DG`, `Phase J-DH`, `Phase J-DI`, `Phase J-DJ`, `Phase J-DK`, `Phase J-DL`, `Phase J-DM`, `Phase J-DN`, `Phase J-DO`, `Phase J-DP`, `Phase J-DQ`, `Phase J-DR`, `Phase J-DS`, `Phase J-DT`, `Phase J-DU`, `Phase J-DV`, `Phase J-DW`, `Phase J-DX`, `Phase J-DY`, `Phase J-DZ`, `Phase J-EA`, `Phase J-EB`, `Phase J-EC`, `Phase J-ED`, `Phase J-EE`, `Phase J-EF`, `Phase J-EG`, `Phase J-EH`, `Phase J-EI`, `Phase J-EJ`, `Phase J-EK`, `Phase J-EL`, `Phase J-EM`, `Phase J-EN`, `Phase J-EO`, `Phase J-EP`, `Phase J-EQ`, `Phase J-ER`, `Phase J-ES`, `Phase J-ET`, `Phase J-EU`, `Phase J-EV`, `Phase J-EW`, `Phase J-EX`, `Phase J-EY`, `Phase J-EZ`, `Phase J-FA`, `Phase J-FB`, `Phase J-FC`, `Phase J-FD`, `Phase J-FE`, `Phase J-FF`, `Phase J-FG`, `Phase J-FH`, `Phase J-FI`, `Phase J-FJ`, `Phase J-FK`, `Phase J-FL`, `Phase J-FM`, `Phase J-FN`, `Phase J-FO`, `Phase J-FP`, `Phase J-FQ`, `Phase J-FR`, `Phase J-FS`, `Phase J-FT`, `Phase J-FU`, `Phase J-FV`, `Phase J-FW`, `Phase J-FX`, `Phase J-FY`, `Phase J-FZ`, `Phase J-GA`, `Phase J-GB`, `Phase J-GC`, `Phase J-GD`, `Phase J-GE`, `Phase J-GF`, `Phase J-GG`, `Phase J-GH`, `Phase J-GI`, `Phase J-GJ`, `Phase J-GK`, `Phase J-GL`, `Phase J-GM`, `Phase J-GN`, `Phase J-GO`, `Phase J-GP`, `Phase J-GQ`, `Phase J-GR`, `Phase J-GS`, `Phase J-GT`, `Phase J-GU`, `Phase J-GV`, `Phase J-GW`, `Phase J-GX`, `Phase J-GY`, `Phase J-GZ`, `Phase J-HA`, and `Phase J-HB`, `Phase J-HC`, `Phase J-HD`, `Phase J-HE`, `Phase J-HF`, `Phase J-HG` packets | Current code now owns the first bounded HyperTwist-native validation and benchmarking substrate: replay-integrity contract, puzzle-state validation contract, repeatable benchmark-profile boundary, validation-scorecard contract, regression-snapshot contract, cross-run benchmark-delta boundary, validation-evidence export contract, benchmark-fixture packet boundary, validation-run-summary contract, operator-review packet boundary, validation-triage queue contract, manual sign-off note boundary, validation-exception waiver contract, validation-handoff closure boundary, validation-carry-forward ledger contract, reviewer-continuity digest boundary, validation-disposition snapshot contract, validation-reopen note boundary, validation-deferred follow-up bundle contract, validation-revisit cue boundary, validation-revisit completion receipt contract, validation-pending-state clearance boundary, validation-dormant-state ledger contract, validation-resurfacing cue boundary, validation-return-readiness packet contract, validation-wake-state confirmation boundary, validation-resumed-state checkpoint contract, validation-continuation-attestation boundary, validation-stable-state ledger contract, validation-continuation-state digest boundary, validation-settled-state packet contract, validation-ongoing-state confirmation boundary, validation-persistent-state ledger contract, validation-ongoing-state acknowledgement boundary, validation-durable-state packet contract, validation-ongoing-state attestation boundary, validation-enduring-state ledger contract, validation-ongoing-state certification boundary, validation-sustained-state packet contract, validation-ongoing-state assurance boundary, validation-anchored-state ledger contract, validation-ongoing-state affirmation boundary, validation-grounded-state packet contract, validation-ongoing-state endorsement boundary, validation-rooted-state ledger contract, validation-ongoing-state ratification boundary, validation-embedded-state packet contract, validation-ongoing-state reconciliation boundary, validation-nested-state ledger contract, validation-ongoing-state harmonization boundary, validation-layered-state packet contract, validation-ongoing-state alignment boundary, validation-stacked-state ledger contract, validation-ongoing-state convergence boundary, validation-composite-state packet contract, validation-ongoing-state synthesis boundary, validation-aggregated-state ledger contract, validation-ongoing-state consolidation boundary, validation-integrated-state packet contract, validation-ongoing-state unification boundary, validation-fused-state ledger contract, validation-ongoing-state coherence boundary, validation-merged-state packet contract, validation-ongoing-state concordance boundary, validation-blended-state ledger contract, validation-ongoing-state correspondence boundary, validation-interlaced-state packet contract, validation-ongoing-state affinity boundary, validation-woven-state ledger contract, validation-ongoing-state resonance boundary, validation-knotted-state packet contract, validation-ongoing-state harmonic boundary, validation-braided-state ledger contract, validation-ongoing-state cadence boundary, validation-looped-state packet contract, validation-ongoing-state refrain boundary, validation-spiraled-state ledger contract, validation-ongoing-state chorus boundary, validation-coiled-state packet contract, validation-ongoing-state reprise boundary, validation-helixed-state ledger contract, validation-ongoing-state echo boundary, validation-twisted-state packet contract, validation-ongoing-state reflection boundary, validation-wound-state ledger contract, validation-ongoing-state reverberation boundary, validation-folded-state packet contract, validation-ongoing-state aftertone boundary, validation-creased-state ledger contract, validation-ongoing-state residue boundary, validation-pleated-state packet contract, validation-ongoing-state remnant boundary, validation-crimped-state ledger contract, validation-ongoing-state imprint boundary, validation-corrugated-state packet contract, validation-ongoing-state trace boundary, validation-ribbed-state ledger contract, validation-ongoing-state signature boundary, validation-fluted-state packet contract, validation-ongoing-state mark boundary, validation-grooved-state ledger contract, validation-ongoing-state seal boundary, validation-ridged-state packet contract, validation-ongoing-state stamp boundary, validation-terraced-state ledger contract, validation-ongoing-state impression boundary, validation-buttressed-state packet contract, validation-ongoing-state etching boundary, validation-bastioned-state ledger contract, validation-ongoing-state engraving boundary, validation-fortified-state packet contract, validation-ongoing-state carving boundary, validation-bulwarked-state ledger contract, validation-ongoing-state inscription boundary, validation-rampart-state packet contract, validation-ongoing-state marking boundary, validation-citadel-state ledger contract, validation-ongoing-state tracing boundary, validation-keep-state packet contract, validation-ongoing-state notation boundary, validation-stronghold-state ledger contract, validation-ongoing-state annotation boundary, validation-watchtower-state packet contract, validation-ongoing-state gloss boundary, validation-battlement-state ledger contract, validation-ongoing-state caption boundary, validation-parapet-state packet contract, validation-ongoing-state legend boundary, validation-merlon-state ledger contract, validation-ongoing-state callout boundary, validation-crenel-state packet contract, validation-ongoing-state marginalia boundary, validation-embrasure-state ledger contract, validation-ongoing-state sidenote boundary, validation-machicolation-state packet contract, validation-ongoing-state footnote boundary, validation-bartizan-state ledger contract, validation-ongoing-state endnote boundary, validation-turret-state packet contract, validation-ongoing-state addendum boundary, validation-barbican-state ledger contract, validation-ongoing-state appendix boundary, validation-gatehouse-state packet contract, validation-ongoing-state codicil boundary, validation-portcullis-state ledger contract, validation-ongoing-state postscript boundary, validation-drawbridge-state packet contract, validation-ongoing-state afterword boundary, validation-moat-state ledger contract, validation-ongoing-state epilogue boundary, validation-causeway-state packet contract, validation-ongoing-state coda boundary, validation-viaduct-state ledger contract, validation-ongoing-state encore boundary, validation-aqueduct-state packet contract, validation-ongoing-state finale boundary, validation-trestle-state ledger contract, validation-ongoing-state curtain-call boundary, validation-span-state packet contract, validation-ongoing-state bow boundary, validation-arch-state ledger contract, validation-ongoing-state ovation boundary, validation-vault-state packet contract, validation-ongoing-state applause boundary, validation-keystone-state ledger contract, validation-ongoing-state acclamation boundary, validation-abutment-state packet contract, validation-ongoing-state commendation boundary, validation-pier-state ledger contract, validation-ongoing-state tribute boundary, validation-footing-state packet contract, validation-ongoing-state homage boundary, validation-pilaster-state ledger contract, validation-ongoing-state salute boundary, validation-column-state packet contract, validation-ongoing-state accolade boundary, validation-capital-state ledger contract, validation-ongoing-state plaudit boundary, validation-frieze-state packet contract, validation-ongoing-state laurel boundary, validation-cornice-state ledger contract, validation-ongoing-state honor boundary, validation-pediment-state packet contract, validation-ongoing-state distinction boundary, validation-entablature-state ledger contract, validation-ongoing-state recognition boundary, validation-architrave-state packet contract, validation-ongoing-state appreciation boundary, validation-metope-state ledger contract, validation-ongoing-state admiration boundary, validation-triglyph-state packet contract, validation-ongoing-state esteem boundary, validation-regula-state ledger contract, validation-ongoing-state regard boundary, validation-guttae-state packet contract, validation-ongoing-state respect boundary, validation-mutule-state ledger contract, validation-ongoing-state deference boundary, validation-taenia-state packet contract, validation-ongoing-state reverence boundary, validation-cymatium-state ledger contract, validation-ongoing-state veneration boundary, validation-sima-state packet contract, validation-ongoing-state devotion boundary, validation-corona-state ledger contract, validation-ongoing-state adoration boundary, validation-soffit-state packet contract, validation-ongoing-state praise boundary, validation-fascia-state ledger contract, validation-ongoing-state exaltation boundary, validation-fillet-state packet contract, validation-ongoing-state glorification boundary, validation-bead-state ledger contract, validation-ongoing-state celebration boundary, validation-ovolo-state packet contract, validation-ongoing-state jubilation boundary, validation-cavetto-state ledger contract, validation-ongoing-state rejoicing boundary, validation-torus-state packet contract, validation-ongoing-state exultation boundary, validation-scotia-state ledger contract, validation-ongoing-state elation boundary, validation-cyma-state packet contract, validation-ongoing-state delight boundary, validation-astragal-state ledger contract, validation-ongoing-state gladness boundary, validation-trochilus-state packet contract, validation-ongoing-state cheer boundary, validation-annulet-state ledger contract, validation-ongoing-state joy boundary, validation-listel-state packet contract, validation-ongoing-state merriment boundary, validation-cincture-state ledger contract, validation-ongoing-state gaiety boundary, validation-girdle-state packet contract, validation-ongoing-state revelry boundary, validation-collarino-state ledger contract, validation-ongoing-state festivity boundary, validation-apophyge-state packet contract, validation-ongoing-state conviviality boundary, validation-doucine-state ledger contract, validation-ongoing-state sociability boundary, validation-cyma-recta-state packet contract, validation-ongoing-state fellowship boundary, validation-cyma-reversa-state ledger contract, validation-ongoing-state camaraderie boundary, validation-echinus-state packet contract, validation-ongoing-state companionship boundary, validation-abacus-state ledger contract, validation-ongoing-state fraternity boundary, validation-necking-state packet contract, validation-ongoing-state solidarity boundary, validation-hypotrachelion-state ledger contract, validation-ongoing-state alliance boundary, validation-gorgerin-state packet contract, validation-ongoing-state accord boundary, validation-bolster-state ledger contract, validation-ongoing-state concord boundary, validation-taper-state packet contract, validation-ongoing-state harmony boundary, validation-shaft-state ledger contract, validation-ongoing-state unity boundary, validation-base-state packet contract, validation-ongoing-state union boundary, validation-plinth-state ledger contract, validation-ongoing-state coalition boundary, validation-pedestal-state packet contract, validation-ongoing-state partnership boundary, validation-stylobate-state ledger contract, validation-ongoing-state consortium boundary, validation-stereobate-state packet contract, validation-ongoing-state federation boundary, validation-podium-state ledger contract, validation-ongoing-state confederation boundary, validation-dais-state packet contract, validation-ongoing-state league boundary, validation-rostrum-state ledger contract, validation-ongoing-state assembly boundary, validation-tribune-state packet contract, validation-ongoing-state forum boundary, validation-lectern-state ledger contract, validation-ongoing-state council boundary, validation-pulpit-state packet contract, validation-ongoing-state caucus boundary, validation-ambo-state ledger contract, validation-ongoing-state quorum boundary, validation-minbar-state packet contract, validation-ongoing-state conclave boundary, validation-cathedra-state ledger contract, validation-ongoing-state synod boundary, validation-bema-state packet contract, validation-ongoing-state convocation boundary, validation-sedilia-state ledger contract, validation-ongoing-state chapter boundary, validation-choir-state packet contract, validation-ongoing-state vestry boundary, validation-stall-state ledger contract, validation-ongoing-state consistory boundary, validation-pew-state packet contract, validation-ongoing-state presbytery boundary, validation-nave-state ledger contract, validation-ongoing-state transept boundary, validation-aisle-state packet contract, validation-ongoing-state chancel boundary, validation-sanctuary-state ledger contract, validation-ongoing-state apse boundary, validation-altar-state packet contract, validation-ongoing-state reredos boundary, validation-retable-state ledger contract, validation-ongoing-state iconostasis boundary, validation-ciborium-state packet contract, validation-ongoing-state baldachin boundary, validation-predella-state ledger contract, validation-ongoing-state dossal boundary, validation-frontal-state packet contract, validation-ongoing-state antependium boundary, validation-superfrontal-state ledger contract, validation-ongoing-state fair-linen boundary, validation-corporal-state packet contract, validation-ongoing-state pall boundary, validation-purificator-state ledger contract, validation-ongoing-state chalice-veil boundary, validation-paten-state packet contract, validation-ongoing-state burse boundary, validation-pyx-state ledger contract, validation-ongoing-state monstrance boundary, validation-cruet-state packet contract, validation-ongoing-state lavabo boundary, validation-thurible-state ledger contract, validation-ongoing-state navicula boundary, validation-aspergillum-state packet contract, validation-ongoing-state aspersorium boundary, validation-stoup-state ledger contract, validation-ongoing-state font boundary, validation-piscina-state packet contract, validation-ongoing-state credence boundary, validation-aumbry-state ledger contract, validation-ongoing-state tabernacle boundary, validation-sacrarium-state packet contract, validation-ongoing-state conopeum boundary, validation-lunette-state ledger contract, validation-ongoing-state humeral-veil boundary, validation-custodia-state packet contract, validation-ongoing-state pyx-cloth boundary, validation-ostensorium-state ledger contract, validation-ongoing-state velum boundary, validation-lunula-state ledger contract, validation-ongoing-state cope boundary, validation-amice-state ledger contract, validation-ongoing-state stole boundary, validation-alb-state ledger contract, validation-ongoing-state chasuble boundary, validation-dalmatic-state ledger contract, validation-ongoing-state tunicle boundary, validation-maniple-state ledger contract, validation-ongoing-state fanon boundary, validation-mitre-state ledger contract, validation-ongoing-state crosier boundary, validation-pectoral-cross-state ledger contract, validation-ongoing-state ring boundary, validation-zucchetto-state ledger contract, validation-ongoing-state biretta boundary, validation-mozzetta-state ledger contract, validation-ongoing-state rochet boundary, validation-surplice-state ledger contract, validation-ongoing-state tippet boundary, validation-chimere-state ledger contract, validation-ongoing-state scarf boundary, validation-cassock-state ledger contract, validation-ongoing-state rabat boundary, validation-camauro-state ledger contract, validation-ongoing-state saturno boundary, validation-ferraiolo-state ledger contract, validation-ongoing-state mantelletta boundary, validation-cappa-magna-state ledger contract, validation-ongoing-state pellegrina boundary, validation-galero-state ledger contract, validation-ongoing-state simar boundary, validation-tabarro-state ledger contract, validation-ongoing-state gremiale boundary, validation-falda-state ledger contract, validation-ongoing-state mantum boundary, validation-sakkos-state ledger contract, validation-ongoing-state omophorion boundary, validation-epigonation-state ledger contract, validation-ongoing-state epimanikia boundary, validation-orarion-state ledger contract, validation-ongoing-state epitrachelion boundary, validation-sticharion-state ledger contract, validation-ongoing-state zonarion boundary, validation-phelonion-state ledger contract, validation-ongoing-state riassa boundary, validation-klobuk-state ledger contract, validation-ongoing-state mandyas boundary, validation-kamelavkion-state ledger contract, validation-ongoing-state epanokamelavkion boundary, validation-koukoulion-state ledger contract, validation-ongoing-state paramandyas boundary, validation-analavos-state ledger contract, validation-ongoing-state polystavrion boundary, validation-epanorion-state ledger contract, and validation-ongoing-state epirrhiptarion boundary, validation-engolpion-state ledger contract, validation-ongoing-state panagia boundary, validation-dikerion-state ledger contract, validation-ongoing-state trikerion boundary, validation-ripidion-state ledger contract, validation-ongoing-state asteriskos boundary, validation-diskos-state ledger contract, validation-ongoing-state kalymma boundary, validation-antimension-state ledger contract, validation-ongoing-state eiliton boundary, validation-aer-state ledger contract, validation-ongoing-state labis boundary, validation-diskarion-state ledger contract, validation-ongoing-state zeon boundary, validation-lonche-state ledger contract, validation-ongoing-state lance boundary, validation-lavida-state ledger contract, validation-ongoing-state sudarion boundary, validation-hexapterygon-state ledger contract, and validation-ongoing-state cherubikon boundary. This remains a runtime-evidence lane rather than a public leaderboard, cross-product telemetry platform, release-gate authority, or generic approval workflow. |
| Phase J registry condensation note | Implemented now | editorial clarification `2026-06-23` | Read the preceding validation row concisely as: HyperTwist owns an internal replay-integrity, benchmark, scorecard, regression, evidence-export, operator-review, triage, sign-off, and continuity-oriented validation substrate. It is runtime evidence infrastructure, not a public leaderboard or release-gate workflow replacement. |
| Structural-only `Phase J` deprecation and behavior-first validation posture | Implemented now | landed first-party `Phase 10A` plus already-landed `Phase 10B` / `Phase 10C` | The retained structural-only `Phase J` suite is preserved only as deprecated disabled build-history ballast (`221` files / `443` deprecated identifiers / `443` disabled flags), while live validation truth stays with the behavior and integration coverage. |
| Embodied companion/narration adjunct | Implemented now | landed `TalkingHead` packet | Live bounded avatar/narration family. |
| Rewritten embodied companion and narrated coaching reference grounding | Implemented now | `met4citizen/TalkingHead` retained permissive lane + first-party current code | Current live `Embodied Companion and Narrated Coaching` reference side includes six rewritten first-party targets grounded in retained `TalkingHead`: queued companion narration, subtitle and viseme sync, avatar-only embed, gesture and mood cues, streaming/listening lifecycle, and TTS or asset adapter boundary posture. This does not displace the landed `Phase 3R-E` first-party embodied companion owner, any separate speech-input or queue-owner lane, or any separate voice-output provider sidecar. |
| Broader long-horizon coach memory and cognitive state | Deep-source grounded retained | first-party target + memory doctrine | Doctrine-governed future widening; not yet a mature memory system. |

### 4. Catalog, curriculum, and knowledge

| Feature | Status | Primary authority | Notes |
|---|---|---|---|
| Imported training catalog packs | Implemented now | first-party current code | Already in product. |
| Retained advanced and multi-puzzle algorithm corpus grounding | Implemented now | `SpeedCubeDB` retained web content + first-party current code | Current live imported catalog breadth across advanced `3x3`, big cube, megaminx, broad pyraminx, broad skewb, and broad square-1 families remains grounded in retained `SpeedCubeDB` web content beneath the first-party rewritten course layer. This does not displace the first-party training runtime or the narrower `CubingApp` one-handed/shaped-subset adjunct. |
| Retained one-handed and shaped-subset adjunct corpus grounding | Implemented now | `CubingApp` retained web content + first-party current code | Current live imported adjunct depth across one-handed `CMLL`, Sarah-intermediate skewb triggers, pyraminx last-layer, and square-1 `CSP` / `OBL` families remains grounded in retained `CubingApp` web content beneath the first-party rewritten course layer. This does not displace the broader `SpeedCubeDB` corpus ground or the first-party training runtime. |
| Rewritten advanced `3x3` reference supplement and tool-reference grounding | Implemented now | `SpeedCubeDB` retained web content + first-party current code | Current live `Advanced 3x3 Systems` reference side includes two rewritten first-party targets grounded in retained `SpeedCubeDB` web content: one course-reference supplement and one tool-reference note for the `Speedcubedb Root` surface. This does not displace the first-party knowledge/reference shell or the broader retained `SpeedCubeDB` deck-corpus ground. |
| Rewritten hypercubing software-manual and solution-reference grounding | Implemented now | `superliminal.com` retained web content + first-party current code | Current live `Hypercubing Software Manuals` reference side includes six rewritten first-party targets grounded in retained `superliminal.com` web content: one `Magic Cube 4D` course-reference supplement plus five software-manual pages across `Magic Cube 4D`, `Magic Cube 7D`, `Magic Hyperbolic Tile`, `Magic Puzzle Ultimate`, and `Magic Simplex 5D`. This does not displace the first-party knowledge/reference shell or any first-party higher-dimensional runtime owner. |
| Rewritten hypercubing historical-reference grounding | Implemented now | `Superliminal Wiki` retained web content + first-party current code | Current live `Hypercubing Reference` side includes one rewritten first-party historical-reference note grounded in retained `Superliminal Wiki` web content for the `Hypercubing Historical Reference` surface. This does not displace the first-party knowledge/reference shell or any first-party higher-dimensional runtime owner. |
| Hypercubing knowledge/reference bundle | Implemented now | landed knowledge packet + first-party consumption | Live knowledge family. |
| Rewritten hypercubing progression, notation, software-matrix, and leaderboard-reference grounding | Implemented now | `Hypercubers/hypercubing.xyz` retained permissive lane + first-party current code | Current live hypercubing reference side includes four rewritten first-party targets grounded in retained `hypercubing.xyz`: progression ladder, cell-turning hypercube notation, software matrix, and leaderboard conventions. This does not displace the landed `Phase 3R-B` first-party knowledge-reference owner or widen into runtime simulation, timer execution, recognition, solver execution, or host-shell ownership. |
| Symbolic-to-spatial pedagogy experiment boundary | Deep-source grounded retained | `NuiLab/code-vr` retained pedagogy lane | AST/graph-to-scene conversion, parse/export/runtime separation, and abstract-structure spatial pedagogy remain retained only behind the first-party knowledge shell and landed browser-spatial/XR owners. No default widening packet is open. |
| Curated training atlas / wiki-like memory | Deep-source grounded retained | first-party target + memory doctrine | Not yet source-grounded enough for stronger external-lane ownership. |

### 5. Publication, leaderboard, entitlement, and social training

| Feature | Status | Primary authority | Notes |
|---|---|---|---|
| Publication/leaderboard projection | Implemented now | landed `kash/cubedesk` `Bound 4` | Live bounded slice. |
| Classic-cube local leaderboard stub | Implemented now | first-party current code + landed timer/training substrate | Current classic-cube runtime persists best local solve times by puzzle id and scramble-length bucket to JSON, carries replay/session identity forward on winning entries, repairs schema-light or duplicate local leaderboard buckets before resolving the displayed best entry, routes the user-facing HUD best-time wording through a centralized deterministic status-line formatter, and projects the best current-bucket line into the in-game HUD without requiring a backend. The primary reverse-SSH `localhost:22022` Windows validation lane refreshed the corresponding leaderboard coverage on isolated worktree `C:\HyperTwist_worktrees\phase10validate` on `2026-06-13`, passing `LeaderboardPersistence`, `LeaderboardNormalization`, and `LeaderboardStatusLine`. |
| Entitlement gating | Implemented now | landed `kash/cubedesk` `Bound 4` | Live bounded slice. |
| Local social challenge bundle | Implemented now | landed `kash/cubedesk` `Bound 5` | Live bounded slice. |
| Broader admin/report lane | Deep-source grounded retained | repo-local justification required | `Bound 6` is deferred and not currently justified for implementation. |

### 6. Public website, distribution, and account surfaces

| Feature | Status | Primary authority | Notes |
|---|---|---|---|
| Public `hypertwist.app` marketing shell | Implemented now | first-party `website/` app + feature registry/roadmap authority | HyperTwist now has a dedicated first-party public web surface for homepage, feature atlas, about, resources, pricing, download, support, legal routes, a dedicated `/getting-started` onboarding surface, and a dedicated `/launch-status` authority surface. This lane is separate from the embedded Unreal browser runtime under `Content/Browser/` and does not claim browser-simulator parity. The same public lane now also serves as a bounded operator/distribution manual through the docs/resources/download/support surfaces, the public feature-atlas route, the dedicated getting-started route, the dedicated launch-status route, and related launch/status surfaces, explaining browser-versus-desktop posture, rollout steps, package proof, simulator-use guidance, and current input/device truth without claiming browser ownership of the native runtime or overclaiming unfinished VR/controller posture. The same package now also carries a first-party external runtime-readiness verifier so deploy-time env and live health posture can be checked outside the dashboard, plus separated local-versus-production env templates whose placeholder values are intentionally rejected until real launch config is in place, bootstrap CI now validates both the frontend and auth-server website commands directly, and the auth server can now auto-serve the built `website/dist` bundle with bounded SPA fallback for same-origin public deployment. Request-level server coverage now also proves that public/app shell delivery does not shadow `/api/*`, `/auth*`, `/health`, or missing asset paths, while the pricing/download/notices routes now surface first-party preview-versus-launch posture from the same bounded launch checklist instead of relying on hidden operator-only status. The shared marketing shell now also carries a compact public-site-status banner across public pages, the homepage keeps a fuller status section, and the shared public launch-status component now consumes live auth-health webhook/runtime truth in addition to release-manifest download readiness so public marketing copy does not claim launch posture from static checkout/download config alone. The auth server now also emits an authoritative `launch` summary on `/api/auth/health`, including required blocker labels, billing product/price-map gates, and current checkout targets, so the public banner and protected dashboard no longer duplicate launch-blocker evaluation client-side. A later same-family continuation then widened that release-manifest authority again to carry public runtime commerce config for operator/studio checkout URLs and live plan-price strings, so pricing, notices, and dashboard launch-readiness surfaces no longer depend only on frontend build-time checkout config. The live website lane now also owns route-aware title/description/canonical/Open-Graph/Twitter metadata for the real `hypertwist.app` marketing surface so deployed public pages no longer remain on a single generic SPA title/description, plus first-party `robots.txt` and `sitemap.xml` assets for the public route set while keeping `/app`, `/login`, and `/register` out of crawler posture. The later shared search-authority hardening pass then moved both assets onto one generated authority seam backed by `website/src/public-route-registry.json`, `website/src/public-search-policy.json`, and first-party script/test ownership, keeping `/app`, `/api/`, `/auth`, `/health`, `/login`, and `/register` aligned without hand-maintained crawler drift. The real `check-runtime-readiness` CLI is now also exercised against the checked-in production example env files, and a spawned `website/server` bootstrap proof now verifies the live same-origin process path from production-shaped env into `/health`, `/api/auth/health`, built-shell serving, and the public anonymous release-manifest posture for the shared desktop release lane. The same verifier now also probes the deployed root-shell marker and can explicitly fail when the public origin is still serving the older placeholder rollout page instead of the first-party website/auth-server lane, while the repo now also carries first-party `website/deploy/` `nginx` plus `systemd` handoff templates, a concrete same-origin public-host cutover guide, a deployment-file renderer that emits resolved operator outputs from real checkout paths, and a manifest-driven bundle renderer that lets one authoritative input own the public origin while emitting validated env plus install artifacts together, with the shared-VPS-safe default upstream moved to `3011` after live host inspection confirmed `3001` is already occupied by FamiliarOS. The same deployment lane now also distinguishes `launch` from `preview` posture so honest missing checkout/download/webhook/release values are accepted only for non-public rehearsal while placeholder strings still fail, `runtime.mode: mixed` plus `public_origin_ready: true` counts as valid preview-host proof, and the staging helper can archive either committed `HEAD` or the live worktree through `--archive-source worktree`. An isolated VPS-local staging proof then confirmed that both the committed HyperTwist website lane and the later preview-tier worktree packet can serve green health, release-manifest, and first-party shell responses on that real shared host behind `3011`, and a later root-owned cutover then replaced the public placeholder site with the live first-party same-origin preview deployment on `https://hypertwist.app`. The package now also ships a bounded root-owned live-deploy helper that stages the committed checkout, uploads the rendered bundle, installs env, rebuilds the site, replaces the live `systemd` plus `nginx` files, and validates the public origin; that helper has already been re-proved idempotently against the live host. The repo now also ships that host-proof flow as a first-party staging helper so future sessions can rerun the temp checkout/build/boot verification path directly before or after root-owned cutover. The website lane now also owns a sanitized generated packaged-validation summary for the Windows higher-dimensional desktop proof, rendered from the checked-in authoritative package report into `website/src/shared/generated/windows-package-validation-summary.json`, and the owned web-surface validation gate now checks that generated proof for freshness before approving the current public/auth/download/browser lane. The repo now also carries checked-in preview-tier frontend/server env examples plus a matching preview same-origin bundle example for the current live `hypertwist.app` posture, while the launch-tier examples still intentionally fail until real checkout, download, source, and webhook values replace their placeholders. The remaining public conversion seams now also stop dead-ending on generic sign-in/support detours when the next lane is already known: the explorer CTA preserves `/register?next=/app`, operator fallback opens the protected downloads lane, studio fallback opens the protected browser-access rollout lane, and launch/download fallback callouts now point directly at protected release, notices, or dashboard follow-through. The narrative/help surfaces then widened again so the public About and Support pages also surface the same live launch-readiness callout and packaged desktop-proof section already used by the stronger public manual routes, keeping maturity language attached to current native release evidence instead of leaving those pages purely abstract. The same public manual continuation now also adds a direct reusable surface-choice guide across the homepage, About, Pricing, Download, and Support pages so operators no longer have to infer from the larger surface matrix alone when they should stay on the public web surface, move into the protected dashboard, or move into the packaged desktop runtime. A later same-family continuation then propagated that same guide through the remaining public feature/docs/resources/changelog/legal pages as well, so the whole public site now preserves one consistent browser-versus-protected-versus-desktop handoff story instead of leaving those lower-traffic surfaces on older implicit wording. A further same-day manual-clarity continuation then added a reusable direct comparison section across the homepage, About, Docs, and Download routes explaining why the website remains necessary, where it is intentionally narrower than the simulator, why the native Unreal runtime stays primary, and how the current keyboard or mouse versus unfinished XR/controller truth should be read. The latest same-family parity follow-up then widened that exact browser-versus-desktop reality section into Pricing and Resources as well, so commercial and reference-heavy public routes no longer rely only on the lighter surface-choice guide when explaining what stays native and where the current XR/controller boundary still begins. The next adjacent parity follow-up then extended the same direct comparison into the public Feature atlas and Support routes as well, so the remaining major public operator-facing surfaces no longer fall back to the lighter guide alone when capability review or recovery work needs the sharper website-versus-native split. A later same-family continuity follow-up then widened the shared release-decision guide into the remaining public legal/notices routes too, so open-source notices, privacy, terms, and shipping/payment now also tell the operator whether the next honest move is protected desktop access, pricing/provisioning, protected browser/account continuity, or notices/source follow-through instead of leaving those pages on the older lighter handoff only. The same browser shell now also has a first-party top-level runtime-recovery boundary, so unexpected React route failures degrade into a HyperTwist-owned retry/return surface that keeps the browser-versus-desktop product truth explicit instead of collapsing into a blank shell. A later same-family quickstart/manual continuation then added a reusable first serious-session guide across homepage, docs, and download so operators can see the real path from release-target choice through desktop-link pairing, first native verification, higher-dimensional verification, and the current XR/controller `No-Go` boundary in one place instead of reconstructing that flow from scattered adjacent sections. That same onboarding/manual packet is now also anchored at a dedicated public `/getting-started` route so the shortest complete browser-to-desktop first-session path is canonical, crawlable, and easier to hand off than the broader site sections alone. The next adjacent launch-authority continuation then did the same for rollout truth through a dedicated public `/launch-status` route, giving preview-versus-launch posture, rollout blockers, packaged proof, and release-reference follow-through one canonical public authority surface instead of leaving that lane distributed across pricing and compact status banners alone. The next same-family shared-auth manual continuation then widened the real browser-account method lineup beyond the auth entry forms and deeper docs surfaces into the homepage, pricing, download, and support routes too, so the public pages where operators actually decide to sign in, buy access, or recover access posture now expose the real provider lineup directly. The latest same-family manual continuation now also adds a shared public route atlas across homepage, docs, and resources so each major public page explains its exact job in the broader operator/distribution manual instead of leaving page purpose mostly implicit in navigation alone. The latest same-family atlas-parity follow-up then widened the public feature-atlas route again so it now also carries the shared runtime control guide directly, keeping the practical classic-control, higher-dimensional-control, native-diagnostics, and explicit XR/controller-boundary truth visible on `/features` instead of forcing advanced readers to leave the atlas for deeper manual routes. The latest same-family responsive-proof expansion then widened browser-level viewport evidence across those newer manual and authority routes too, so `/features`, `/docs`, `/getting-started`, and `/launch-status` now sit inside the owned public responsive validation lane instead of relying only on source-level or unit-level proof. The latest same-family commerce/download manual deepening follow-up then widened `/pricing` and `/download` again so the actual purchase and package routes now carry the installed-software simulator manual, the higher-dimensional family guide, and the current input/device plus runtime-control truth directly instead of leaving that practical product explanation to docs/resources/getting-started alone. A later same-family continuation then completed the shared-section path on the feature atlas itself by routing its higher-dimensional guide, input/device posture, control-profile roster, and runtime-control guide through the same shared helper ownership as the surrounding public routes, and widened responsive public-route proof across `/changelog`, `/open-source-notices`, `/privacy`, `/terms`, and `/shipping-payment`, while a later adjacent auth-entry parity follow-up also brought `/login` into that same owned mobile/tablet matrix, bringing the explicit public-route browser proof to `34` passed Playwright checks while the broader `13`-file/`79`-test website route/auth/release suite and `10`-file/`36`-test auth-server suite stayed green. The latest same-family high-traffic FAQ promotion follow-up then surfaced the shared browser-versus-desktop boundary Q&A directly on homepage and About as well, so operators no longer have to drill into deeper support/manual surfaces just to learn that the current browser lane is intentionally narrower than the desktop simulator and why that narrower posture is still the stronger shipping product shape. The latest same-family legal/distribution continuity follow-up then widened `/open-source-notices` and `/shipping-payment` again so those deeper public routes now also carry the live surface-authority map plus offline operator-manual continuity, while the shipping/payment lane also keeps the shared auth-method lineup visible, preventing the purchase, payment, source, and notices surfaces from degrading back into a materially thinner shell than the main brochure/manual routes. |
| Browser-based operator/account dashboard | Implemented now | first-party `website/` app + shared auth/dashboard packet | A protected browser dashboard is now live for operator access, account state, download posture, browser-access boundary explanation, notices review, and bounded billing/entitlement status. It reuses the shared SuperTokens auth posture proven in FamiliarOS and ScriptoriumAI while remaining HyperTwist-specific in product content and boundary claims, the current auth-health surface now truthfully distinguishes configured versus reachable or ready shared-core posture while exposing fallback-active reason instead of hardcoding readiness, and the same dashboard now also surfaces launch-readiness truth for download URLs, checkout links, source/notices URLs, billing-secret/map configuration, and local-versus-public runtime deployment posture. The same shared-auth lane now also carries end-to-end optional provider parity for GitHub, Google, and bounded ORCID sign-in: the auth server owns the ORCID custom-provider path, the same-origin bundle emits matching ORCID frontend/server env truth, the browser client now registers ORCID through the supported third-party recipe provider contract instead of leaving that final step implicit, auth-health reports ORCID readiness alongside the other providers, and the public docs route now exposes the current browser-account method lineup instead of leaving provider truth visible only on the form pages. The surrounding public decision surfaces now also mirror that same provider-lineup truth on homepage, pricing, download, and support, so shared-auth reality is not hidden until operators reach either the auth forms or the deeper manual. The same protected overview now also consumes the server-backed Windows packaged-validation summary that the release-manifest authority exposes, so operators can see current higher-dimensional desktop proof without drilling into the dedicated downloads screen. The adjacent protected `/app/browser-access` and `/app/notices` routes now also reuse the bounded escalation-map and release-follow-through guidance from the public support/manual lane, so sign-in does not degrade operator troubleshooting quality into a thinner shell than the public surface. The protected overview and protected download center now also mirror the same launch-readiness, operator-access, and studio-rollout help lanes as the public support/manual surface, but translate those actions into direct signed-in dashboard, downloads, browser-access, account, notices, pricing, and release-notes targets instead of sending the operator back through anonymous auth detours. A later same-family parity follow-up then added the same blunt browser-versus-desktop reality explanation to the protected dashboard, protected downloads, and browser-access routes as well, so sign-in no longer makes the product boundary or unfinished XR/controller truth less explicit than the public manual. The next adjacent parity follow-up then extended that same compact reality panel into the protected account and notices routes too, so entitlement review and distribution/compliance work no longer soften the browser-support versus native-simulator split after sign-in. The auth entry pages now also render the same browser-versus-desktop truth before sign-in is even complete, so login and register no longer rely only on next-step routing plus later dashboard surfaces to explain what stays native and where the current XR/controller boundary still begins. A later same-family protected-shell continuation then widened signed-in auth truth itself, so the dashboard and account routes now surface the auth method, current provider lineup, shared-auth readiness, runtime origins, cookie/public-origin posture, fallback state, and deployment diagnostics directly instead of collapsing that truth down to a thin stack label. The protected fallback path now also preserves signed-in viewer plan/access posture from local session truth when live manifest authority is temporarily unavailable, while still keeping download authority conservative until the auth server returns. The shared browser auth layer now also has a bounded release-authority reconciliation path that refreshes and persists the local browser session snapshot from fresher manifest viewer truth, while the dashboard and account surfaces expose a compact live-authority sync notice summarizing what changed so operators can see the session catch-up clearly. That same auth layer now also clears stale stored sessions when shared auth is configured and `/api/auth/me` returns `401`, while still preserving the intended offline/local-fallback posture when the account API is merely unreachable or shared auth is not configured. The next adjacent protected-shell launch-authority continuation then added a dedicated signed-in `/app/launch-status` route, so launch posture, rollout blockers, release references, packaged proof, and signed-in next actions no longer collapse back to a single overview panel once account context exists. The follow-through continuation after that then threaded the same signed-in launch-status route back through protected release-action cards, release-reference panels, and the browser-access, download, account, and notices surfaces, so rollout authority remains attached to the surrounding signed-in operator shell instead of becoming an isolated page. Focused frontend coverage now also protects deep-link login redirect preservation, safe `next`-path normalization across auth entry points, fallback/email auth-bootstrap normalization, login/register continuation behavior, public download-gating behavior, protected-route/shell behavior, real lazy-route tree behavior for key public and protected paths, top-level app-bootstrap and SuperTokens-wrapper posture, login/register unhappy-path and OAuth-button behavior, support-topic fallback routing when live checkout is not configured, desktop-link verify-url/dashboard readiness behavior, and explicit `noindex,nofollow` posture on protected/auth browser surfaces. The validation lane now also has a bounded signed test-session harness under `TEST_MODE=testing` that proves `/api/auth/me`, stale-session invalidation, release-authority reconciliation, and `/api/auth/desktop-link` behavior through the live spawned auth-server process without widening production auth posture. A later same-family responsive-browser hardening follow-up then added Playwright viewport proof for `/app`, `/app/launch-status`, `/app/downloads`, `/app/browser-access`, `/app/account`, and `/app/notices`, so the shipped signed-in operator shell now has the same bounded mobile/tablet no-horizontal-overflow proof posture as the current public-route family. |
| Windows desktop installer, readiness, upgrade, and uninstall ownership | Implemented now | first-party Release 19 installer lane | `packaging/windows/HyperTwistInstaller.nsi`, `scripts/Build-HyperTwistWindowsInstaller.ps1`, `scripts/Test-HyperTwistWindowsReadiness.ps1`, and `scripts/Test-HyperTwistWindowsInstaller.ps1` now own the per-machine x64 Windows install lane above the Release 19 Shipping payload. The installer bundles a valid Microsoft-signed Visual C++ runtime, excludes debug/PDB payloads, carries a complete `143`-file SHA-256 manifest, refuses unsafe leaves and unowned non-empty roots, defers owned upgrade cleanup until prerequisites succeed, resolves app/readiness/uninstall/desktop shortcuts, and preserves current-user settings, saves, replays, and diagnostics on uninstall. The final `851049086`-byte artifact passed first install, full payload parity, installed readiness, stock-Shipping launch diagnostics, in-place upgrade, second parity, uninstall, user-data preservation, and cleanup from a path containing spaces. Its SHA-256 is `c31ed6b0b2ae1feb449c27e484d72dc2e07ba220e3cdafa4c3605429d638e0ea`; trusted Authenticode signing and a genuinely fresh Windows VM remain external release gates. |
| Desktop download posture and browser-to-desktop pairing | Implemented now | first-party `website/` app + `website/server` desktop-link endpoints | Public download targets, dashboard-side release posture, and short-lived desktop-link token generation/verification are now first-party owned. The current server posture now enforces exact website-origin matching, bounded per-user issuance, one-time token consumption, and billing-backed plan/download entitlement resolution with focused `website/server` tests green on `2026-06-22`, and the verify handshake now returns the same resolved download-entitlement posture the dashboard sees instead of only identity plus plan/role. The same lane now also owns a shared `GET /api/releases/manifest` runtime authority for release version/channel/build/published/file-size/checksum/docs/source metadata, with anonymous callers intentionally denied raw download URLs while entitled session-backed callers receive the configured direct platform URL. That manifest now also carries first-party packaged-validation summary truth for the Windows higher-dimensional desktop lane, so the public `/download` page, the public `/resources` reference page, and the protected `/app/downloads` surface can project real package evidence for the dedicated-family `Magic120Cell` / `MagicCube5D` maps even while launch-tier release URLs remain unconfigured. That website-facing packaged proof is now sourced through a sanitized generated summary rendered from the checked-in authoritative `phase6c_dedicated_family_package_validation_report.json`, and the owned web-surface validation gate now checks that generated summary for freshness before approving the current public/auth/download/browser lane. The public `/download` page now keeps raw download URLs behind the protected dashboard instead of exposing them directly, preserves requested platform continuity through `/app/downloads?platform=...`, and surfaces that requested target again after auth handoff inside the protected release lane. The public download fallbacks now also open exact protected download and dashboard follow-through instead of stopping at a generic anonymous login hop. When live manifest authority is unavailable, the protected fallback path now still reflects the signed-in viewer posture from local session truth while continuing to withhold raw delivery authority. When live manifest authority resolves fresher entitled viewer truth than the local browser auth snapshot, the protected download-center lane now also follows that server-backed viewer posture for the actual download action instead of leaving the operator blocked behind stale local session state. Both the public and protected download surfaces now also carry first-party rollout steps, first-launch desktop setup guidance, browser-to-desktop pairing follow-through, and release/notices/source references so the desktop setup lane is more than a generic link bucket, while the support surface now carries an explicit escalation map separating account, package, runtime, and rollout/compliance problems. The protected dashboard overview and protected account surface now also mirror that same first-launch follow-through, and the protected browser-access/notices routes now mirror the same escalation separation, so post-sign-in operator guidance does not collapse back into a thinner release-only shell. The protected download center now also mirrors the same three help-topic lanes used by the public support/manual surface, but with direct signed-in actions for downloads, dashboard, account, browser access, notices, and release notes so entitled operators can stay inside the protected rollout lane once auth has already succeeded. The dashboard plus public launch-status callouts now consume the same manifest-backed Windows download truth instead of only static frontend config. Actual release URLs remain deployment configuration rather than hardcoded product truth. |
| Paddle-ready pricing and billing webhook seam | Implemented now | first-party `website/` app + `website/server` billing endpoint | The public pricing surface now exists with plan structure, checkout-link configuration seams, and the same `/api/billing/paddle/webhook` endpoint family used by the broader product website lane. The current server now verifies `Paddle-Signature` against `PADDLE_WEBHOOK_SECRET` using the documented raw-body HMAC flow, persists a bounded first-party billing state file, and applies verified Paddle events into account/download entitlement state that the browser dashboard consumes, with focused `website/server` tests green on `2026-06-22`. The shared `GET /api/releases/manifest` authority now also carries public runtime commerce config for operator/studio checkout URLs and live plan-price strings, allowing the pricing page to switch from frontend build-time checkout assumptions to auth-server runtime truth when those values are configured. The fallback plan CTAs now also use exact protected release/browser-access targets when live checkout URLs are absent, instead of routing operators back into a vague public support detour. A spawned live-process proof now also verifies that a real signed webhook updates processed-event health and persisted billing state through the actual auth-server runtime, not only helper-level store tests, and transaction events no longer leak their id into stored `subscriptionId` state. Production checkout URLs, secret management, and broader operator/admin billing workflows remain deployment/application tasks, not shipped-code omissions. |
| Public open-source notices and corresponding-source surface | Implemented now | first-party `website/` app + `HYPERTWIST_MPL_DISTRIBUTION_PLACEMENT_CHECKLIST_2026-05-25.md` | HyperTwist now has a stable public `Open Source Notices` route linked from pricing, download, and footer surfaces, satisfying the requirement that public distribution surfaces expose notice and corresponding-source guidance when shipped builds contain `MPL`-covered material. The exact public corresponding-source URL still must be configured before external launch. |

### 7. Hyper puzzle topology and non-Euclidean runtime

| Feature | Status | Primary authority | Notes |
|---|---|---|---|
| Legacy `4D` interaction/history/macro/provenance boundary | Implemented now | landed `magiccube4d` packet | Already part of current product truth. |
| Legacy `4D` reference grounding and attribution boundary | Implemented now | `cutelyaware/magiccube4d` retained boundary-sensitive lane + first-party current code | Current live `Legacy 4D Interaction and History` reference side includes six rewritten first-party contract/reference targets grounded in `cutelyaware/magiccube4d`: history, macro remapping, puzzle-description topology, interaction grammar, view-controller composition, and explicit visible-attribution/upstream-link/`MyMath` provenance-boundary notes. This does not displace the landed `Phase 4R-B` first-party owner lane, the retained `Hyperspeedcube` runtime anchor, or the later `MagicTile` topology and transform-aware macro widening. |
| Tiling topology and geometry-family contract | Implemented now | landed `MagicTile` packet | New bounded widening is live. |
| Transform-aware macro remapping and macro persistence boundary | Implemented now | landed `MagicTile` `Phase 6R-T` | Current bounded remapping contract, reverse/setup-move playback support, and macro XML compatibility boundary are live above the landed topology contract. |
| Embedded browser host decision for non-Euclidean tiling | Implemented now | landed first-party `MagicTile` `Phase 7A` | Current bounded `MagicTile` host posture routes live non-Euclidean interaction through the already-landed embedded browser/CEF shell with retained `three.js` and `react-three-fiber`, while native spherical/hyperbolic renderer ownership and the legacy `WinForms` / `OpenTK` host shell remain deferred. |
| Tiling browser state bridge, shared scramble normalization, and unified timer transport | Implemented now | landed first-party `MagicTile` `Phase 7B` | First-party tiling state envelopes, bridge-contract descriptors, browser widget/bridge decoding, scramble normalization, and training-timer continuity are live above the embedded-browser host posture without reopening generic runtime-base replacement. |
| Native MagicTile behavior proof contract and probe | Implemented now | landed first-party `MagicTile` `Phase 7C` | First-party native behavior proof contract/probe now carry selected-cell focus, candidate-twist disambiguation, preview token, commit or cancel semantics, and timer continuity above the landed browser host/bridge seam without claiming renderer-port or legacy host ownership. |
| Optional native MagicTile renderer-port path above the landed proof seam | Deep-source grounded retained | landed first-party `MagicTile` `Phase 7D` decision packet | This branch is now defined only as an explicit go/no-go lane. Default posture remains `No-Go` unless a later packet proves a real browser-host insufficiency, bounded owned-surface scope, `Phase 7C` behavior parity, and full Windows validation. The adjacent `2026-06-19` evidence audit kept the branch closed because the live browser shell, bridge, and `Phase 7C` proof seam currently show no demonstrated host failure and no bounded renderer target. |
| Dedicated `120-cell` family runtime profile and persistence boundary | Implemented now | landed `Magic120Cell` packet | Current bounded family-specific widening is live beneath the retained `Hyperspeedcube` runtime anchor. |
| Dedicated `120-cell` symmetry-aware focus view profiles | Implemented now | landed `Magic120Cell` `Phase 6R-AL` | Current bounded settings-derived projection, symmetry preset, logical-visibility, per-cell visibility, and center-cell focus posture are live above the landed dedicated `120-cell` runtime-profile seam without widening into renderer, host-shell, or generic topology ownership. |
| Dedicated `5D` family runtime profile and persistence boundary | Implemented now | landed `MagicCube5D` packet | Current bounded family-specific widening is live beneath the retained `Hyperspeedcube` runtime anchor. |
| Dedicated `5D` projection and focus view profiles | Implemented now | landed `MagicCube5D` `Phase 6R-AM` | Current bounded settings-derived projection-distance, stereo posture, per-face visibility, accent emphasis, and fifth-axis focus posture are live above the landed dedicated `5D` runtime-profile seam without widening into renderer, host-shell, or generic hyper-runtime ownership. |
| Higher-dimensional clean-room runtime activation catalog | Implemented now | landed `Phase 6C` activation packet | First-party current code now resolves canonical `polychoron/magic120cell` and `hypercube/magiccube5d/order3` puzzle definitions, default launch posture, primary donor-boundary contract ids, and the no-external-process clean-room stance above the retained `Magic120Cell` / `MagicCube5D` contracts and the retained `Hyperspeedcube` runtime anchor. The current continuation also resolves the active higher-dimensional activation profile from live training run state through both puzzle-id and imported generated-mode `RuntimeModeId` paths, then mirrors that resolved profile through the training runtime library plus the training panel/session caches; the primary `localhost:22022` Windows lane passed all `5` `HyperTwist.FirstParty.HigherDimensional.Phase6C` tests on `2026-06-13`. |
| Higher-dimensional initial shared-map launch and view-context execution bridge | Implemented now | landed `Phase 6C` continuation packet | First-party current code first bundled higher-dimensional launch surfaces and view-context surfaces for `Magic120Cell` and `MagicCube5D`, resolved those surfaces through the training runtime library plus the live training panel/session-actor caches, and let the training subsystem start the shared-map seed run, apply default selector posture, persist the generated-mode launch request, and start the owned generated run without widening into external-process ownership. After recovering an interrupted follow-up, the primary reverse-SSH `localhost:22022` Windows lane rebuilt that cleaned slice on `2026-06-18` with `Result: Succeeded`, UnrealBuildTool `Total execution time: 124.81 seconds`, and passed all `8` `HyperTwist.FirstParty.HigherDimensional.Phase6C` tests, including `LaunchCatalog`, `ViewContextCatalog`, `LaunchExecution`, and `RunStateActivationResolution`; that initial bridge is now superseded by the later dedicated-family map ownership continuation. |
| Higher-dimensional explicit dedicated-host seam | Implemented now | landed `Phase 6C` host-surface continuation packet | First-party current code then recorded the preferred dedicated-family `Magic120Cell` / `MagicCube5D` host-map targets in an explicit higher-dimensional host-surface catalog while the slice still kept the shared training map as the interim effective runtime fallback, mirrored that resolved host seam through the training runtime library plus the panel/session caches, and threaded the host-surface id into the launch/view-context surfaces and generated-mode lineage. The primary reverse-SSH `localhost:22022` Windows lane rebuilt this widened slice on `2026-06-18` with `Result: Succeeded`, UnrealBuildTool `Total execution time: 2858.02 seconds`, and passed all `9` `HyperTwist.FirstParty.HigherDimensional.Phase6C` tests, including the new `HostCatalog`; that interim fallback is now superseded by the later dedicated-family map ownership continuation. |
| Higher-dimensional executed runtime session surface | Implemented now | landed `Phase 6C` session-surface continuation packet | First-party current code now merges the higher-dimensional launch, host, and view-context seams into an explicit runtime-session catalog for `Magic120Cell` and `MagicCube5D`, mirrors that session surface through the training runtime library plus the panel/session caches, upgrades generated-mode deck lineage to record the resolved session surface, and applies the merged launch-plus-view selector posture at start time instead of only the narrower launch defaults. The primary reverse-SSH `localhost:22022` Windows lane rebuilt this widened slice on `2026-06-18` with `Result: Succeeded`, UnrealBuildTool `Total execution time: 3541.98 seconds`, and passed all `10` `HyperTwist.FirstParty.HigherDimensional.Phase6C` tests, including the new `SessionCatalog`; the longer `LaunchExecution` quiet interval of `573.84 seconds` remained known-good. |
| Higher-dimensional dedicated-family interactive scene ownership | Implemented now | landed `Phase 6C` interactive-scene and dedicated-host continuation packet | First-party current code now promotes the higher-dimensional runtime-session seams into explicit `Magic120Cell` and `MagicCube5D` interactive-scene surfaces with family-owned runtime-state, projection, and persistence envelopes, replaces the shared-map bridge with dedicated-family training-map assets plus dedicated host/launch/view-context/session surfaces, exposes explicit scene-envelope decoders through the runtime library, batches default selector application so generated-mode launch execution no longer rebuilds repository views once per selector, and then defers repository-view projection across the internal generated-mode handoff itself so only the final launch state forces a view refresh. The primary reverse-SSH `localhost:22022` Windows lane rebuilt the dedicated-family ownership slice on `2026-06-18` with `Result: Succeeded`, UnrealBuildTool `Total execution time: 1648.33 seconds`; the later projection-deferral hardening rebuild completed in `400.77 seconds`, and the exported automation report passed all `11` `HyperTwist.FirstParty.HigherDimensional.Phase6C` tests with `totalDuration` `41.88494873046875`, `LaunchExecution` duration `41.53509521484375`, and the controller quiet interval reduced to `41.52 seconds`. The current recovery-proof continuation now also deterministically reauthors the dedicated-family maps through `scripts/hypertwist_author_higher_dimensional_training_maps.py`, records manifest-backed owned hashes in `docs/generated/higher_dimensional_training_maps/phase6c_dedicated_family_map_manifest.json`, preserves the optional `AHyperTwistHigherDimensionalTrainingShellActor` for manual/editor authoring while intentionally skipping it on the headless commandlet lane because that spawn path still crashes `UnrealEditor-Cmd`, passes all `13` `HyperTwist.FirstParty.HigherDimensional.Phase6C` tests through pulled proof in `docs/generated/higher_dimensional_training_maps/phase6c_dedicated_map_ownership_automation_report.json`, including `DedicatedMapAuthoringManifest` and `DedicatedMapOwnedShell`, and now has a maintained packaged-validation seam through `scripts/Invoke-HyperTwistHigherDimensionalPackage.ps1` plus `scripts/Launch-HyperTwistHigherDimensionalPackage.ps1`. That helper was then live-validated on `2026-06-22` against isolated worktree `C:\HyperTwist_worktrees\phase10validate` in `-SkipBuild` mode, with `BuildCookRun time: 118.53 s`, archive output in `C:\HyperTwist_worktrees\phase10validate_packaged_phase6c_higherdim`, both dedicated-family packaged smoke maps green, and pulled aggregate proof in `docs/generated/higher_dimensional_training_maps/phase6c_dedicated_family_package_validation_report.json`. The same maintained helper lane was refreshed again on `2026-06-23` after the recovered authoritative editor rebuild, again in `-SkipBuild` mode against the existing receipt, with `BuildCookRun time: 70.74 s`, archive output in `C:\HyperTwist_worktrees\phase10validate_packaged_phase6c_higherdim_refresh_20260623`, both dedicated-family packaged smoke maps green again, and the checked-in aggregate report refreshed in place. A later exact-source recovery on `2026-06-30` then proved the same dedicated-family package lane can stay truthful even when the maintained isolated worktree is temporarily blocked by a Windows host file lock: the new bounded wrapper `scripts/run-hypertwist-remote-exact-source-browser-package-refresh.sh` retried the maintained-root editor build, fell back to `C:\HTpp` when the lock persisted, narrow-synced the exact-source browser/package support surfaces that fallback root lacked, reran `HyperTwist.Browser` proof with `26` succeeded and `0` failed, then completed a full packaged higher-dimensional build there because the fallback root did not yet have the packaged-game target receipt. Both dedicated-family smoke maps still passed, and the checked-in aggregate package report plus public summary were refreshed with truthful `skip_build: false` posture instead of pretending the old maintained-root `-SkipBuild` condition still applied. The later same-day maintained-root recovery then tightened that public release proof again by carrying both truths in the same generated artifact chain: the exact-source wrapper passed a fresh editor build on `C:\HyperTwist_worktrees\phase10validate`, the higher-dimensional package helper then legitimately reused the existing packaged-game receipt, and the aggregate package report plus website-facing summary now expose both the packet-level `prePackageEditorBuild` result and the helper-level `skipBuild` state instead of collapsing them into one ambiguous build flag. |
| Broad non-Euclidean interaction shell and host ownership | Deep-source grounded retained | `MagicTile` retained remainder | Broad interaction-shell, WinForms/OpenTK host ownership, native spherical/hyperbolic renderer ownership beyond the landed first-party native behavior proof, and generic runtime replacement remain deferred after the landed `Phase 6R-T`, `Phase 7A`, `Phase 7B`, and `Phase 7C` slices, with later native renderer reopening now governed by the separate spec-only `Phase 7D` decision gate. |

### 8. Speech input and voice sidecars

| Feature | Status | Primary authority | Notes |
|---|---|---|---|
| Speech transcript session boundary | Implemented now | landed `whisper.cpp` packet | Current bounded STT truth. |
| Live microphone capture shell | Implemented now | landed `whisper.cpp` `Phase 6R-U` packet | Current bounded microphone shell truth above the landed transcript-session and orchestration seams. |
| Device-permission and capture-route readiness shell | Implemented now | landed `whisper.cpp` `Phase 6R-V` packet | Current bounded permission/readiness shell posture, route fallback issue objects, and explicit retry/request semantics above the landed microphone shell seam. |
| First-party real device-permission workflow | Implemented now | landed first-party `Phase 6R-AF` packet | Current bounded permission-workflow profile ids/definitions, request/settings/recheck posture, and workflow capability exposure are live above the landed permission/readiness shell seam. The bounded first-party native capture-route workflow/control layer now lives in landed `Phase 6R-AG`. |
| First-party native capture-route ownership and workflow preparation/control | Implemented now | landed first-party `Phase 6R-AG` packet | Current bounded native capture-route ownership assessment, preparation/retry/reopen posture, and workflow capability exposure are live above the landed permission-workflow seam. The bounded first-party operator-facing shell layer now lives in landed `Phase 6R-AH`. |
| First-party operator-facing native capture-route workflow shell | Implemented now | landed first-party `Phase 6R-AH` packet | Current bounded shell profile ids/definitions, operator-facing shell-state posture, and ownership-summary/preparation/session-reopen card capability exposure are live above the landed native capture-route workflow/control seam. Actual OS permission-grant execution, payment execution, provider-portal ownership, and payload shipping remain deferred. |
| Downloadable model and payload custody boundary | Implemented now | landed `whisper.cpp` `Phase 6R-W` packet | Current bounded custody profile, required/supported payload descriptors, and health-surface integrity metadata above the landed transcript-session and shell seams. |
| Provider-backed speech session health and transcript envelopes | Implemented now | first-party speech client surfaces | Current first-party speech seam. |
| Python transcription-service orchestration profile | Implemented now | landed `faster-whisper` `Phase 6R-F` and `Phase 6R-AP` packets | Current bounded Python STT orchestration truth, batch-window tuning metadata, and prompt/retrieval-hint routing metadata are live above the existing speech session boundary. |
| Local narration sidecar seam | Implemented now | landed `piper` packet | Current bounded offline narration contract, voice catalog, and local sidecar truth. |
| Downloadable voice-asset review boundary | Implemented now | landed `piper` `Phase 6R-AQ` packet | Current bounded review profile, supported local voice-asset descriptors, and health-surface review metadata are live above the landed local narration sidecar seam. |
| Advanced narration orchestration profile | Implemented now | landed `coqui-ai/TTS` packet | Current bounded richer narration profile above the existing companion narration contract. |
| Downloadable voice/model review boundary | Implemented now | landed `coqui-ai/TTS` `Phase 6R-AR` packet | Current bounded review profile, supported advanced voice-model review descriptors, and health-surface review metadata are live above the landed advanced narration orchestration seam. |
| Cross-platform offline dictation shell, transcript history, output routing, OS-integration shell adjunct, and local model-catalog review posture | Implemented now, bounded permissive adjunct | landed `cjpais/Handy` `Phase 6R-AJ`, `Phase 6R-AO`, and `Phase 6R-AU` packets | Current bounded external dictation-shell profile/state, transcript-history retention, clipboard/typing/script-oriented output-routing posture, transcript post-process overlay posture, global-hotkey lifecycle shell posture, input/output device-selection shell posture, mute-while-recording plus microphone-mode shell posture, and local model-catalog / integrity / unload-policy review posture are live above the current speech stack. It does not displace landed `whisper.cpp`, `faster-whisper`, or first-party provider-neutral speech ownership, and actual model download/extract/unload execution ownership remains deferred. |
| Broad voice output / narration sidecars | Deep-source grounded retained | `piper`, `coqui-ai/TTS` retained remainder | Keep actual voice-asset shipping, playback/runtime ownership, and broader assistant-platform scope separate from the landed local review and narration packets. |
| Actual downloadable model and payload shipping | Deep-source grounded retained | `whisper.cpp` retained remainder | Keep real download/shipping ownership separate from the landed bounded custody boundary and from the code-license judgment. |

### 9. Provider-neutral AI/provider routing

| Feature | Status | Primary authority | Notes |
|---|---|---|---|
| First-party provider-neutral speech/vision contract | Implemented now | first-party recognition/speech client seams | Current bounded provider/session truth. |
| Provider-neutral BYOK/profile custody boundary | Implemented now | landed first-party `Phase 6R-X` packet | Current bounded provider-profile ids/definitions, BYOK custody ids/definitions, per-profile model/capability maps, and out-of-band auth-reference wording. |
| First-party provider routing and workflow-policy boundary | Implemented now | landed first-party `Phase 6R-Y` packet | Current bounded routing-policy ids/definitions, route-decision summaries, explicit fallback-health posture, and workflow-policy capability exposure above the landed provider/session and provider-custody seams. |
| First-party normalized usage/cost event surface | Implemented now | landed first-party `Phase 6R-Z` packet | Current bounded accounting-profile ids/definitions, normalized usage/cost event summaries, quota/rate-limit state, and bounded capability exposure above the landed provider-routing seam. |
| First-party operator-facing provider usage/cost dashboard shell | Implemented now | landed first-party `Phase 6R-AA` packet | Current bounded dashboard shell profile ids/definitions, dashboard issue/state posture, and capability exposure above the landed normalized usage/cost seam. |
| First-party provider usage/cost history/export shell | Implemented now | landed first-party `Phase 6R-AB` packet | Current bounded history/export shell profile ids/definitions, rolling history entry and export issue/state posture, summary export preview/copy behavior, and capability exposure above the landed provider usage/cost dashboard seam. |
| First-party provider receipt review and posted-charge inspection shell | Implemented now | landed first-party `Phase 6R-AC` packet | Current bounded receipt-review shell profile ids/definitions, derived receipt-review entry and issue/state posture, and capability exposure above the landed provider usage/cost history/export seam. |
| First-party provider billing settlement and invoice reconciliation shell | Implemented now | landed first-party `Phase 6R-AD` packet | Current bounded settlement shell profile ids/definitions, derived settlement entry and issue/state posture, invoice-reconciliation readiness, and capability exposure above the landed provider receipt-review seam. |
| First-party provider settlement exception and external-portal handoff shell | Implemented now | landed first-party `Phase 6R-AE` packet | Current bounded settlement-exception shell profile ids/definitions, derived exception entry and issue/state posture, reference-only external-portal handoff readiness, and capability exposure above the landed provider settlement seam. |
| First-party provider-neutral custom-endpoint runtime routing | Implemented now | landed first-party `Phase 6R-AI` packet | Current bounded per-session provider-profile endpoint selection, runtime routing, fallback-health reflection, and provider-backed transport-failure posture above the landed provider-profile/BYOK and provider-routing seams. OpenAI-compatible custom endpoints are no longer custody-only doctrine targets. |
| Provider-specific overlays | Shallow placeholder | future provider-family work only | Keep internal until source-grounded and normalized. |

### 10. Memory, continuity, notes, and provenance

| Feature | Status | Primary authority | Notes |
|---|---|---|---|
| Session continuity and workspace recall fragments | Implemented now | first-party runtime/training surfaces | Real substrate fragments under the canonical `Memory Lanes`; not yet a full lane implementation. |
| Provenance-aware training/replay/publication state | Implemented now | first-party contract/provenance surfaces | Existing product truth. |
| First-party memory contracts and ledger | Implemented now | landed first-party `Phase 6R-M1` packet | Current bounded memory lane ids, entity ids, provenance links, authority flags, feature gates, retention profiles, and ledger JSON round-trip are live. Later bounded chronicle/resume, recall/shared-context, cognitive consolidation, knowledge/note posture, and derived-adjunct layers now sit above this seam. |
| First-party chronicle and continuity | Implemented now | landed first-party `Phase 6R-M2` packet | Current bounded chronicle events, grouped continuity sessions, resume packs, and repo-aware continuity guards are live above the landed `Phase 6R-M1` ledger seam. Later bounded recall/shared-context, cognitive consolidation, knowledge/note posture, and derived-adjunct layers now sit above this seam. |
| First-party recall and shared context | Implemented now | landed first-party `Phase 6R-M3` packet | Current bounded explicit recall matches, history search, provenance drill-down, and revocable shared-context projections are live above the landed `Phase 6R-M1` ledger and `Phase 6R-M2` chronicle/continuity seams. Later bounded cognitive consolidation, knowledge/note posture, and derived-adjunct layers now sit above this seam. |
| First-party cognitive consolidation | Implemented now | landed first-party `Phase 6R-M4` packet | Current bounded provenance-backed cognitive facts, contradiction records, supersession links, and confidence-decay entries are live above the landed `Phase 6R-M1`, `Phase 6R-M2`, and `Phase 6R-M3` seams. Later bounded knowledge/note posture and derived-adjunct layers now sit above this seam. |
| First-party knowledge and notes posture | Implemented now | landed first-party `Phase 6R-M5` packet | Current bounded curated knowledge objects, reviewable promotion decisions, and explicit user-notes posture/gating are live above the landed `Phase 6R-M1`, `Phase 6R-M2`, `Phase 6R-M3`, and `Phase 6R-M4` seams. Active user-authored note capture still remains deferred, and the landed `Phase 6R-M6` derived-adjunct layer now sits above this seam. |
| Control-plane telemetry, replay-diagnostic, and rollout-governance reference grounding | Implemented now | `PostHog/posthog` retained boundary-sensitive lane + first-party current code | Current live `Control-Plane Telemetry and Replay Governance` reference side includes six rewritten first-party contract/reference targets grounded in `PostHog/posthog`: replay diagnostics, replay segmentation, feature governance, scheduled changes, early-access lifecycle, and explicit `MIT`-outside-`ee/` compliance-boundary notes. This does not displace the landed `Phase 4R-D` first-party owner lane, any replay-shell owner family, or the explicit enterprise-subtree exclusion boundary. |
| Capture-history, vault, and replay-inspection reference grounding | Implemented now | `screenpipe/screenpipe` retained boundary-sensitive lane + first-party current code | Current live `Capture History, Replay, and Vault Support` reference side includes six rewritten first-party contract/reference targets grounded in `screenpipe/screenpipe`: event-capture, pipe-permission, persistence, vault-lifecycle, timeline-review, and explicit permissive-core-versus-`ee/` compliance-boundary notes. This does not displace the landed `Phase 4R-E` first-party owner lane, the broader replay shell, or the explicit enterprise-subtree exclusion boundary. |
| Layered memory federation | Deep-source grounded retained | memory doctrine + VectorShell import entrypoint | Governing taxonomy exists; HyperTwist uses pointer-based synchronization to the current VectorShell memory canon rather than a frozen local fork. Lane widening remains future work and later superior evidence may revise only the exact affected lane or sub-slice. |
| Continuity Lattice context assembly | Deep-source grounded retained | continuity-lattice doctrine + VectorShell import entrypoint | One federated substrate with two preset-backed, overrideable profiles: `Max-Retention Mode` and `Economic-Retention Mode`. This is not a second memory system, does not weaken lane authority or optional-assistive override control, and does not justify automatic whole-repo absorption when one continuity sub-slice changes owner. |
| User-authored note lane | Deep-source grounded retained | memory doctrine, owner unresolved | Explicit note-lane posture/gating is live through `Phase 6R-M5`, but active user-authored note capture still must not be described as shipped until ownership is justified. |
| First-party derived memory and optional adjunct | Implemented now | landed first-party `Phase 6R-M6` packet | Current bounded compact summaries, reduced context packets, and optional digest views are live in explicit derived-only removable form. `Economic-Retention Mode` proves all-features-off correctness by keeping the lane empty and valid, while `Max-Retention Mode` exposes the optional derived adjunct surfaces without promoting them to authoritative truth. |

### 11. Skills and optional assistive layer

| Feature | Status | Primary authority | Notes |
|---|---|---|---|
| First-party skill registry and enable/disable governance | Implemented now | landed first-party `Phase S1-A`, `Phase S1-B`, `Phase S1-C`, `Phase S1-D`, `Phase S2-A`, `Phase S2-B`, `Phase S2-C`, `Phase S3-A`, `Phase S3-B`, `Phase S3-C`, `Phase S4-A`, `Phase S4-B`, `Phase S4-C`, `Phase S5-A`, `Phase S5-B`, `Phase S5-C`, `Phase S6-A`, `Phase S6-B`, `Phase S7-A`, `Phase S7-B`, and `Phase S7-C` packets | Current bounded first-party skill status/family contracts, command/service binding declarations, permission/scope declarations, provenance/log declarations, manifest entries, registry counts, durable master-switch/per-skill control-state, family visibility groups, disabled-but-installed inert-off-state truth, invocation-record format, command/service provenance, failure/cancel audit-ledger storage, authoring-template sections, registry-grounded examples, per-skill smoke/eval validation-harness contracts, structured permissive wrapper-output contracts, bounded first-party implementation/delegation spec contracts, bounded first-party plan/orchestration glue contracts, bounded first-party provider-profile/routing skill contracts, bounded first-party provider usage/operations audit skill contracts, bounded first-party domain-pack framework contracts, bounded first-party retained domain-pack contracts, bounded first-party creative/media pack contracts, first-party clean-room command-contract specs, first-party clean-room-ready skill specs, bounded first-party continuity/resume skill state, bounded recall/compact-view skill state, bounded workflow-memory capture skill state, bounded docs/design extraction skill state, bounded browser diagnostics skill state, bounded design-shell translation skill state, bounded workflow/review wrapper state, bounded implementation/delegation spec state, bounded plan/orchestration state, bounded provider-profile/routing state, bounded provider usage/operations audit state, bounded domain-pack framework state, bounded retained domain-pack state, and bounded creative/media pack state are live as bounded substrate. The current named first-party skillization ladder is now landed through `S7-C`. |
| Review/analyzer skill family | Implemented now | landed first-party `Phase S2-A`, `Phase S5-A`, `Phase S5-B`, and `Phase S5-C` packets | Current bounded first-party review/analyzer wrappers/specs are live for architecture scan, policy scan, proposal review, diff review, bounded workflow-wrapper output, implementation review, bounded delegation spec output, plan synthesis, and bounded workflow chaining over permissive product evidence. Broader provider/ops audit and domain widening still remains future work. |
| Memory/continuity skill family | Implemented now | landed first-party `Phase S3-A`, `Phase S3-B`, and `Phase S3-C` packets + skillization + memory doctrine | Current bounded `resume-session`, `search-history`, `recall-memory`, `generate-compact-view`, `capture-session-template`, and `capture-follow-up-routine` skills are live above the landed first-party `6R-M1`, `6R-M2`, `6R-M3`, and `6R-M6` memory seams, while `capture-note` remains explicit but non-live under separate owner activation because active user-authored note capture is still not landed beyond the bounded `6R-M5` seam. Compact views remain optional and linked to authoritative sources, workflow capture remains separate from user-authored notes, and the browser/docs/design extraction, browser diagnostics, design-shell translation, and workflow/review seams are now live above that memory base. |
| Browser/docs/design extraction skill family | Implemented now | landed first-party `Phase S4-A` packet | Current bounded `extract-docs` and `extract-design-spec` skills are live over authoritative first-party docs/design source surfaces. Structured extraction remains provenance-visible and derived-only, while browser diagnostics and design-shell translation remain separate bounded sibling seams. |
| Browser/docs/design browser diagnostics skill family | Implemented now | landed first-party `Phase S4-B` packet | Current bounded `capture-browser-trace` and `discover-browser-api` skills are live over authoritative first-party browser/service source surfaces. Browser diagnostics remain provenance-visible, extraction-dependent, and separate from bounded design-shell translation. |
| Browser/docs/design design shell skill family | Implemented now | landed first-party `Phase S4-C` packet | Current bounded `translate-design-shell` and `translate-design-interaction` skills are live over authoritative first-party docs, design, browser, and packet source surfaces. Design-shell translation remains provenance-visible, extraction-dependent, browser-diagnostics-dependent, and separate from generic browser-shell orchestration. |
| Workflow/review wrapper skill family | Implemented now | landed first-party `Phase S5-A` packet | Current bounded `review-proposal`, `review-diff`, and `wrap-bounded-workflow` skills are live over authoritative first-party extraction, workflow-memory, design-shell, and packet source surfaces. Workflow/review output remains provenance-visible, extraction-dependent, workflow-memory-dependent, and design-shell-dependent while staying separate from plan synthesis or broad orchestration widening. |
| Implementation/delegation spec skill family | Implemented now | landed first-party `Phase S5-B` packet | Current bounded `review-implementation` and `specify-bounded-delegation` skills are live over authoritative first-party workflow/review, design-shell, and packet source surfaces. Implementation/delegation output remains provenance-visible, workflow/review-dependent, design-shell-dependent, and separate from plan synthesis, autonomous execution claims, or broad orchestration widening. |
| Plan/orchestration glue skill family | Implemented now | landed first-party `Phase S5-C` packet | Current bounded `synthesize-plan` and `chain-bounded-workflow` skills are live over authoritative first-party implementation/delegation, workflow-memory, workflow/review, and packet source surfaces. Plan/orchestration output remains provenance-visible, implementation-dependent, workflow-memory-dependent, workflow-review-dependent, and separate from provider routing, domain skill-pack widening, or autonomous execution claims. |
| Provider/ops skill family | Implemented now | landed first-party `Phase S2-A`, `Phase S6-A`, and `Phase S6-B` packets + skillization + provider doctrine | Current bounded `provider-routing-inspector`, `inspect-provider-profile`, `setup-byok-profile`, `diagnose-provider-routing`, `audit-provider-usage`, `inspect-provider-topology`, and `diagnose-route-service` skills are live above the landed provider-neutral speech/provider seams. Provider/ops output remains provenance-visible, wrapper-aware, provider-neutral, custom-endpoint-aware, normalized-first-party-state-aware, and separate from settlement execution, provider-portal widening, or provider-specific overlay widening, while the landed `S7-A` domain-pack framework now sits above this normalized provider/ops lane and `S7-B` retained-pack widening remains next. |
| Restrictive training/coaching clean-room skill-spec family | Implemented now, spec-only bounded seam | landed first-party `Phase S2-B` and `Phase S2-C` packets + skillization doctrine | Current restrictive training/coaching skillization seam is now clean-room-ready in first-party terms for bounded Roux session review output. HyperTwist owns the first-party command contract, safety model, and clean-room-ready skill spec, while live clean-room skill behavior still remains separately deferred unless later reopened. |
| Domain/creative skill packs | Implemented now, retained-pack plus creative/media bounded seam | landed first-party `Phase S7-A`, `Phase S7-B`, and `Phase S7-C` packets + skillization doctrine | Current bounded `specify-domain-packaging`, `specify-domain-pack-grouping`, `review-training-replay-pack`, `curate-curriculum-content-pack`, `prepare-media-export-pack`, `compose-replay-explainer-pack`, `prepare-media-parser-pack`, and `curate-shared-fixture-pack` skills are live over authoritative first-party framework, training/replay, catalog/content, media/export, and shared-fixture source surfaces. The retained-pack layer remains provenance-visible, optional creative/media adjuncts now remain bounded above it, and mixed-terms fixture or commercial media boundaries stay explicit rather than widening into broad runtime or authoring-shell claims. |

## Shallow-known placeholder families

These are intentionally coarse placeholders.

They exist because the portfolio already signals the family strongly enough
that later extraction work should not forget it.

They are not yet source-grounded enough to promote as retained product
capabilities.

| Placeholder family | Current status | Use rule |
|---|---|---|
| Provider-specific overlay/dashboard variants | Shallow placeholder | Internal stub only until normalized and source-grounded. |
| Broader memory-donor families not yet evaluated for HyperTwist | Shallow placeholder | Internal stub only. |
| Broad skill-pack catalog beyond initial governance target | Shallow placeholder | Internal stub only. |
| Broader assistant-platform or agent-control families | Shallow placeholder | Internal stub only. |

## Maintenance rule

When a new packet materially adds or changes a normalized feature:

1. update the relevant family row here
2. upgrade any affected placeholder if it becomes source-grounded
3. preserve the status-tier distinction
4. do not silently promote a placeholder into retained or implemented truth

## Summary

### Latest continuity note (`2026-07-23`)

- the current desktop Alpha authority is the Release 19 stock-Shipping package
  delivered at
  `C:\Users\Anthracite Ace\Downloads\HyperTwist-Alpha-Test-20260723-R19`;
  Release 17 is retained as rollback provenance rather than current feature
  authority
- first-party packaged startup now owns a strict registered-route argument,
  `-HyperTwistStartupRoute=<route-id>`:
  - the route id must resolve through the same source-owned catalog used by the
    visible first-run buttons
  - empty, duplicate, unknown, overlong, case-drifted, and injected values are
    rejected
  - Follow-Along, Magic120Cell, and MagicCube5D package validation therefore
    proves product-route ownership rather than relying on a raw map argument
- stock Shipping now writes direct first-party runtime diagnostics independently
  of `UE_LOG`, while retaining separate bounded first-run route diagnostics
- the Release 19 semantic package matrix is green across all `9` native routes:
  - Classic and Follow-Along: exact maps, `26` renderable cubies, settled valid
    state
  - 4D orders `2` through `6`: exact dedicated maps, exact `N^4` state counts,
    and order-specific projected piece-view counts
  - Magic120Cell: exact dedicated map, `120` canonical elements, `6` layer
    materials
  - MagicCube5D: exact dedicated map, `242` canonical elements, `6` layer
    materials
- both the validation-archive executable and the exact final Downloads
  executable rendered a fresh semantic first-run frame with
  `launch-menu-renderable`; the two copied evidence images are byte-identical
  at SHA-256
  `caa45f3d3104a8e5406f493a60c8a136d852bd35e0bd1c8dfbf79738c1343892`
- archive verification reopened the `167`-entry ZIP and stream-hashed the
  outer launcher, inner Shipping executable, `tbbmalloc.dll`, cooked
  `pak`/`utoc`/`ucas`, exact solver table, and staged browser runtime; ZIP size
  is `1093537260` bytes and SHA-256 is
  `630963f96c681fc49130cbc56c6c850008d4cddda7e83f2ee9c077c52d7709a9`
- the final executable also accepts and opens `coach-dashboard` under direct
  Shipping diagnostics; a fresh dashboard screenshot remains a narrow
  operator-connected visual check because a disconnected desktop must not be
  treated as image authority
- the July 9 folder and ZIP were retired only after replacement launch and
  archive proof; Release 17 evidence remains under
  `docs/generated/alpha_test_20260723`, and current Release 19 evidence is
  indexed in `docs/generated/alpha_test_20260723_release19`

#### Release 19 combined delivery (package gate closed)

- the native first-run catalog now exposes eight puzzle entries rather than
  collapsing higher-dimensional play into three generic choices: Classic Cube,
  exact 4D orders `2x2x2x2` through `6x6x6x6`, Magic 120-cell, and the
  order-3 5D Cube; MagicTile remains a separate browser-preview lane behind its
  frozen native-renderer gate
- the 4D family now owns order-specific exact `N^4` state, legal turns,
  projection, persistence, dedicated routes, dedicated game modes, and five
  independently authored maps; the five map hashes and their generation
  authority live under `docs/generated/virtual_4d_training_maps`
- MagicCube5D now owns exact order-3 state (`243` cubies and `810` facelets),
  legal turns, projection, focus, and persistence; Magic120Cell now owns an
  exact `7,560`-facelet permutation, `7,440` legal base moves, inverse and
  forward turns, focus, and persistence while its current scene remains
  truthfully bounded to a representative `120`-center visualization
- the native product shell now has player-facing main, Learn, Settings,
  Account, Advanced, About/Credits, pause, and exit surfaces with reliable
  back navigation; Settings owns Controls, Audio, Graphics, Accessibility,
  and Speech & Coach rather than exposing operator diagnostics as the primary
  player UI
- the Learn surface now owns a persisted Learning Studio with OLL, cross,
  5-style, Roux, and blindfold case decks, reveal, self-grading, timing,
  progression, review priority, and Classic-runtime scramble handoff
- the common native puzzle controller now owns a fixed in-game coach opened
  with `F3`; it keeps bounded session-only history, local help, optional
  provider-backed responses, global dictation, and asynchronous optional
  narration while remaining usable without AI, STT, TTS, or an API key
- the FamiliarOS pattern review was read-only: HyperTwist independently owns
  provider-neutral AI/STT/TTS configuration, protected per-Windows-user
  credentials, cloud-consent gates, endpoint policy, microphone selection and
  non-retaining test, global hold/toggle dictation, temporary WAV deletion,
  readiness labels, managed audio categories, and fixed-coach reply narration
- `UHyperTwistFirstRunLaunchLibrary::BuildIntegratedCapabilityCatalog()` now
  exposes exactly the original `29` implemented/live repository capabilities
  as `18` permissive, `5` restrictive clean-room, and `6`
  boundary-sensitive rows across `5` native-playable, `14` native-service,
  `7` browser-support, and `3` operator-support surfaces; the player-facing
  About & Credits page renders that catalog
- the separate historical Phase 1 queue of `29` selected wiring candidates is
  now also independently count-checked from positions `1` through `29` in
  both the bundled browser registry and clean-checkout fallback; its
  dependency-only, QA/editor-sidecar, source-sidecar, and reference-only rows
  remain explicit instead of being mislabeled as native game modes
- exact Windows evidence for this source continuation is green through UE 5.7
  editor build plus `8/8` `HyperTwist.FirstRun`, `7/7` Learning Studio,
  `17/17` Classic Cube, and the final `5/5`
  `HyperTwist.PlayerExperience` focused automation; the final player-experience
  report adds `GlobalAssistantSpeechSession` proof that global dictation can
  open outside an active Classic training run
- browser `verify:shell` and the Vite production build are green with `1,872`
  transformed modules; exact Windows cook/package, staged `Content/Browser`
  verification, all `9` native route smokes, archive validation, archive-level
  visible acceptance, Downloads hash parity, and final Downloads visible
  acceptance are all green, so this combined source state now supersedes
  Release 17 as Release 19
- the row-level realization and evidence authority is
  `docs/ops/HYPERTWIST_ORIGINAL_29_LIVE_REPOSITORY_RUNTIME_CAPABILITY_PROOF_MATRIX_2026-07-23.md`

### Latest continuity note (`2026-07-02`)

- the first-party native desktop boot path now has a code-owned first-run
  launch and settings surface:
  - `AHyperTwistFirstRunLaunchGameMode` is the default project game mode
  - `AHyperTwistFirstRunLaunchPlayerController` owns the boot input mode,
    dashboard handoff, map-opening route execution, startup diagnostics, and
    automatic gameplay fallback if the launch widget cannot be shown
  - `UHyperTwistFirstRunLaunchWidget` renders the initial keyboard/mouse,
    route, web-versus-desktop, XR live-proof, and operator log-path guidance
  - `UHyperTwistFirstRunLaunchLibrary` exposes stable contracts for Coach
    Dashboard/settings, classic cube free play, follow-along training,
    `Magic120Cell`, `MagicCube5D`, OpenXR validation, the packaged startup map,
    the fallback route, and the runtime/startup log file names
  - historical packaged first-run repair on `2026-07-09`, superseded by the
    verified `2026-07-23` Shipping Alpha: the maintained Windows package
    lane proved that `GameDefaultMap` alone was not sufficient because
    `L_HyperTwist_ClassicTraining` still carried its own authored game-mode
    override; `DefaultEngine.ini` now also sets `LocalMapOptions` to
    `?game=/Script/UnrealHyperTwist.HyperTwistFirstRunLaunchGameMode`, and the
    regression suite now asserts both the startup map and the explicit
    packaged-game-mode handoff so packaged boot cannot silently fall back to
    the blank/default-stage ownership path again
- the packaged desktop lane also now has a first-party verified zip export
  helper:
  - `scripts/Export-HyperTwistPackagedBuildZip.ps1`
  - validates that the produced archive is non-empty and still contains a
    packaged `UnrealHyperTwist.exe` entry before reporting success
  - historical Windows proof on `2026-07-09`, retained as provenance but no
    longer distributed: the repaired desktop artifact at
    `C:\HyperTwist_worktrees\phase10validate\packaged\desktop-first-run-authority-repair-20260709`
    logged `BeginPlay`, `ApplyFirstRunInputMode`, and
    `ShowFirstRunLaunchMenu` from `LogHyperTwistFirstRunLaunch`, and the fresh
    deliverable zip
    `C:\Users\Anthracite Ace\Downloads\HyperTwist-desktop-first-run-authority-repair-20260709.zip`
    passed archive verification with `142` entries, executable entry
    `Windows\UnrealHyperTwist.exe`, size `719569118` bytes, and SHA-256
    `4ec2d5f8e00e28d727590ca584ce40843eed5b85fa7e03c578b7a404c3f45d67`;
    both that Downloads folder and ZIP were deleted on `2026-07-23` after the
    Release 17 replacement was fully verified
- this makes first launch materially less raw while keeping the same honest
  boundary: the web simulator remains a lighter account/preview surface, the
  Unreal download remains simulator authority, and physical headset/controller
  observation is still the remaining XR proof gate
- validation: maintained reverse-SSH Windows worktree
  `C:\HyperTwist_worktrees\phase10validate` rebuilt the exact source state with
  `UnrealHyperTwistEditor` `Result: Succeeded`, UnrealBuildTool total
  execution `52.97` seconds, and exported
  `Saved\AutomationReports\FirstRunLaunchSurface-20260702\index.json` with
  `3` `HyperTwist.FirstRun` tests succeeded and `0` failed/not-run/in-process
- the first-party `website/` public/auth shell now carries one shared
  product-reality strip across public marketing routes and browser account
  access routes:
  - desktop Unreal remains the simulator authority
  - the website remains the account, pricing, documentation, release, notices,
    support, and protected handoff surface
  - keyboard and mouse remain the viable current development and operator
    review path
  - live commerce/download/auth configuration plus physical headset/controller
    observation remain explicit launch gates
- the same browser-account lane now treats auth-shell backdrop stacking as a
  launch-readiness invariant rather than decoration-only CSS: `/login` and
  `/register` must render their forms above the fixed decorative/auth backdrop,
  and the website test suite now carries both source-level and browser-level
  regression proof for that condition
- this is a copy and layout coherence hardening pass, not a topology widening
  and not a promotion of the optional full-browser simulator branch

### Previous continuity note (`2026-06-30`)

- the first-party `website/` public manual lane widened again without changing
  topology:
  - `/download`, `/getting-started`, and `/docs` now carry a shared
    first-session verification packet
  - `/docs` and `/support` now also carry a shared issue-reporting packet
  - the same-origin downloadable operator manual now mirrors that
    browser-limitations, verification, and reporting truth under a dedicated
    regression test instead of remaining a materially thinner offline sibling

This file is the shortest path from packet authority to later user-facing
explanation.

It should be the default extraction surface for:

- manuals
- onboarding
- help surfaces
- roadmap summaries
- product copy drafts

provided the status taxonomy above is preserved exactly.
