diff --git a/docs/ops/HYPERTWIST_PUBLIC_WEBSITE_CONTENT_AND_OPERATOR_MANUAL_PACKET_2026-06-22.md b/docs/ops/HYPERTWIST_PUBLIC_WEBSITE_CONTENT_AND_OPERATOR_MANUAL_PACKET_2026-06-22.md index 47cf90a..57a670d 100644 --- a/docs/ops/HYPERTWIST_PUBLIC_WEBSITE_CONTENT_AND_OPERATOR_MANUAL_PACKET_2026-06-22.md +++ b/docs/ops/HYPERTWIST_PUBLIC_WEBSITE_CONTENT_AND_OPERATOR_MANUAL_PACKET_2026-06-22.md @@ -1229,3 +1229,41 @@ Latest same-family offline-manual continuity follow-up on `2026-06-30`: - website deployment/readiness tooling suite: `4` files, `34` tests passed - website/server suite: `10` files, `36` tests passed - successful website and `Content/Browser` production builds + +Later same-family offline-manual deepening follow-up still on `2026-06-30`: + +- the downloadable operator manual is no longer only the lighter companion to + the live route atlas +- `website/public/manual/hypertwist-operator-manual.md` now mirrors the richer + public-manual truth directly, including: + - current browser auth/account posture + - the first operator journey from public launch posture through protected + downloads and desktop-link pairing + - concrete desktop workflow tracks for classic practice, recognition and + correction, replay/coaching review, higher-dimensional training, and + browser-return governance + - the shipped classic control roster plus bounded settings/persistence truth + - dedicated `Magic120Cell`, `MagicCube5D`, and embedded-browser `MagicTile` + runtime guidance + - operator adjunct families such as bounded speech, provider/routing, and + continuity/provenance posture + - degraded-state recovery guidance + - public/protected route atlas descriptions instead of route-name lists alone +- the public release feed now also carries that manual change explicitly + through the new same-day `changelogEntries` item in `website/src/site-data.ts` +- the full owned web-surface gate was rerun again on that deeper manual state + and stayed green under: + - `scripts/run-hypertwist-web-surface-validation.sh` + - focused website route/auth/release validation: `14` files, `84` tests passed + - deployment/readiness tooling validation: `4` files, `34` tests passed + - `website/server` validation: `10` files, `36` tests passed + - successful website and `Content/Browser` production builds + - `website/` and `Content/Browser/` production audits stayed at + `found 0 vulnerabilities` + - `website/server/` again retained only the same already-documented upstream + `supertokens-node -> nodemailer` residual advisory +- current truthful reading after this follow-up: + - the offline manual is now closer to a real deployment/reference packet, + not just a shorter brochure copy + - the public website and protected shell still remain complementary to the + native simulator rather than competing claims over the same runtime job diff --git a/docs/v6_5_deep_manual_pack/HyperTwist/DEVELOPMENT.md b/docs/v6_5_deep_manual_pack/HyperTwist/DEVELOPMENT.md index 9f17ffc..b757908 100644 --- a/docs/v6_5_deep_manual_pack/HyperTwist/DEVELOPMENT.md +++ b/docs/v6_5_deep_manual_pack/HyperTwist/DEVELOPMENT.md @@ -2579,6 +2579,48 @@ Latest same-family responsive public-route expansion follow-up on `2026-06-29`: - the native XR/controller lane still remains a deliberate desktop-hosted `No-Go` rather than something this refresh reclassified as complete +## Offline operator-manual deepening still on `2026-06-30` + +- the next same-family continuation stayed above the already-landed public + manual lane instead of widening product topology again +- `website/public/manual/hypertwist-operator-manual.md` is no longer only a + lighter offline summary of the public site +- the downloadable manual now mirrors the richer route-atlas and simulator-use + truth directly, including: + - browser auth/account posture and protected download authority + - the first operator journey from public launch posture through protected + download handoff and desktop-link pairing + - concrete desktop workflow tracks for classic practice, recognition and + correction, replay/coaching review, higher-dimensional session use, and + browser-return governance + - the shipped classic control roster plus bounded settings/persistence truth + - dedicated-family runtime guidance for `Magic120Cell`, `MagicCube5D`, and + the current embedded-browser `MagicTile` host lane + - degraded-state recovery guidance and public/protected route atlas +- the public changelog now also records that manual deepening explicitly + through the new same-day entry in `website/src/site-data.ts` +- the full owned web-surface gate then reran green on that deeper manual state: + - `scripts/run-hypertwist-web-surface-validation.sh` + - focused website route/auth/release validation: + - `14` files passed + - `84` tests passed + - deployment/readiness tooling validation: + - `4` files passed + - `34` tests passed + - `website/server` validation: + - `10` files passed + - `36` tests passed + - successful website and `Content/Browser` production builds + - `website/` and `Content/Browser/` production audits stayed at + `found 0 vulnerabilities` + - `website/server/` again retained only the same already-documented upstream + `supertokens-node -> nodemailer` residual advisory +- current truthful reading after this continuation: + - the offline manual is now much closer to a real rollout/reference packet + rather than only a shorter companion to the live site + - no new web-surface regressions appeared while deepening that manual + content + ## Latest exact-state audit refresh later on `2026-06-29` - the next same-family continuation stayed bounded to current-truth diff --git a/website/public/manual/hypertwist-operator-manual.md b/website/public/manual/hypertwist-operator-manual.md index d532f41..e93fe52 100644 --- a/website/public/manual/hypertwist-operator-manual.md +++ b/website/public/manual/hypertwist-operator-manual.md @@ -14,8 +14,10 @@ Use this manual when you need one offline reference for: - first-session onboarding - protected dashboard follow-through - desktop download and pairing -- current control roster and runtime settings truth +- current control roster, settings, and desktop workflow truth - higher-dimensional runtime ownership +- release, billing, and distribution posture +- support, recovery, and escalation guidance - release, notice, and support follow-through ## Product topology @@ -47,25 +49,108 @@ Important boundary: - they own access, pricing, entitlement, notices, release posture, and pairing - the desktop runtime remains the actual simulator authority -## First session +## Browser access and account posture -1. Start on the public website - - review `/launch-status` if release posture matters - - review `/pricing` if access or provisioning matters - - review `/download` for the current public package posture -2. Sign in or create an account - - continue into `/app` - - use the protected browser shell for account-aware follow-through -3. Open the protected download lane - - use `/app/downloads` - - confirm target platform, entitlement, and current package proof -4. Pair the desktop runtime - - generate the desktop-link token from the protected dashboard - - do not reuse your password inside the desktop handoff flow -5. Verify the first simulator lane - - confirm the current packaged build - - confirm the current runtime lane you intend to use - - confirm the current control boundary before assuming more than the product ships +The browser lane is intentionally narrower than the simulator. + +Use it for: + +- public documentation and rollout context +- account access and protected release posture +- pricing and entitlement follow-through +- release notes, notices, and corresponding-source references +- browser-to-desktop identity pairing + +Current truthful browser auth posture: + +- email/password is the baseline shared-auth lane +- GitHub, Google, and ORCID may also appear when the deployment has them configured +- sign-in opens protected account, release, and pairing surfaces +- sign-in does not turn the browser into the simulator + +## First operator journey + +Use this as the current first serious-session path. + +### 1. Resolve access and choose the right build + +- start on `/download` when the target platform matters +- review `/launch-status` when rollout posture matters +- review `/pricing` when access, plan, or provisioning matters +- preserve the chosen platform through sign-in into the protected release lane + +### 2. Sign in and move into the protected shell + +- continue into `/app` +- use the protected browser shell for account-aware follow-through +- keep release posture, notices, and entitlement attached to the same account context + +### 3. Open the protected download lane + +- use `/app/downloads` +- confirm target platform, entitlement, and current package proof +- treat the protected release lane as the delivery authority + +### 4. Pair the installed desktop runtime + +- generate the desktop-link token from the protected dashboard +- use the token during first launch +- do not reuse your password inside the desktop handoff flow + +### 5. Verify the first native session + +- confirm the current packaged build and release notes +- open the first classic-cube training lane +- verify the shipped control roster before assuming broader device support +- verify the higher-dimensional lane you intend to use +- keep the XR/controller boundary explicit + +## Current desktop workflow tracks + +### Classic-cube practice + +Use the desktop runtime when the goal is actual practice rather than product +orientation. + +- launch the classic-cube training lane from the installed desktop runtime +- confirm the timer, scramble, HUD, and replay posture first +- use the native desktop lane as the authoritative practice loop rather than a browser substitute + +### Recognition and correction + +Use the desktop runtime when you need the real cube-state intake and +reconstruction workflow. + +- calibrate and observe the cube through the bounded recognition lane +- use browser-assisted recognition and native correction closure together +- read reconstruction and solve guidance as desktop workflow truth + +### Replay, coaching, and analytics + +Use the desktop runtime when the session needs review continuity. + +- finish or import the training session +- review replay, coaching, leaderboard, and diagnostics surfaces in the native runtime +- return to the browser shell only when account, release, entitlement, or support posture becomes the next concern + +### Higher-dimensional sessions + +Use the packaged dedicated-family maps when training moves beyond the classic +cube. + +- launch the dedicated `Magic120Cell` or `MagicCube5D` map from the desktop runtime +- use the shipped selector, focus, projection, symmetry/stereo, and visibility posture +- use selector recall when the latest persisted generated-mode launch request is valid +- keep XR/controller widening explicit No-Go rather than assuming parity from groundwork alone + +### Browser-return governance + +Return to the browser shell when the job becomes commercial, operational, or +release-facing rather than simulator-facing. + +- use the protected dashboard for plan, entitlement, desktop-link pairing, and release-manifest review +- use public or protected launch-status, notices, pricing, and release-notes routes when rollout posture changes +- keep browser access issues separate from native runtime issues ## Current desktop runtime scope @@ -105,6 +190,29 @@ Representative shipped actions include: - `V` hold-to-talk - `C` cycle voice +Representative shipped keyboard roster includes: + +- `I/K = R/R'` +- `J/F = U/U'` +- `H/G = F/F'` +- `D/E = L/L'` +- `S/L = D/D'` +- `W/O = B/B'` +- `T/Y = x/x'` +- `N/B = y/y'` +- `P/Q = z/z'` + +Current settings truth also includes: + +- viewer camera settings ownership +- bounded camera-export continuity through `artifact/camera-export-json` +- immersive session-local recall through `immersive-training-session-recall-boundary` +- dedicated family-specific view defaults for `Magic120Cell` and `MagicCube5D` +- native diagnostics that expose the active activation, view-context, session, and interactive-scene owners + +This is real settings ownership, but it is still narrower than a finished +global rebinding/preferences suite. + ## Higher-dimensional runtime truth Current higher-dimensional truth includes: @@ -118,6 +226,24 @@ Current higher-dimensional truth includes: The serious higher-dimensional lanes are not placeholders in the live product story. They remain part of current product truth. +### Magic120Cell packaged runtime + +- launch the dedicated `Magic120Cell` training map from the desktop runtime +- use the current symmetry, focus, logical-visibility depth, and center-cell posture as the owned runtime lane +- use native diagnostics to confirm the dedicated session surface, interactive-scene surface, persistence boundary, and state semantics for this family + +### MagicCube5D packaged runtime + +- launch the dedicated `MagicCube5D` training map from the desktop runtime +- use the current projection-distance, stereo, face-visibility, and focus posture as the owned runtime lane +- use native diagnostics to confirm the dedicated session surface, interactive-scene surface, persistence boundary, and state semantics for this family + +### MagicTile embedded-browser runtime + +- treat the embedded browser/CEF shell as the current shipped host for the live non-Euclidean tiling lane +- keep the first-party bridge, state transport, and timer continuity attached to the native shell +- do not describe a separate native renderer port as live while that renderer-widening gate remains explicit No-Go + ## XR and controller truth HyperTwist does not currently claim a finished VR/controller product lane. @@ -159,10 +285,17 @@ Use the desktop runtime when you need: - higher-dimensional execution - native diagnostics or runtime-adjacent operator work -## Download and release follow-through +## Release, download, and distribution posture -The public `/download` page describes supported targets and release posture. -The actual delivery authority stays in the protected release lane. +HyperTwist is digitally delivered through browser account access and desktop +downloads. + +Current operating rules: + +- the public `/download` page describes supported targets and release posture +- actual delivery authority stays in the protected release lane +- Windows Unreal packaged validation is currently the strongest public package-proof lane +- package proof, release notes, pricing posture, notices, and corresponding-source follow-through belong to one release story Check these before broader rollout: @@ -173,63 +306,113 @@ Check these before broader rollout: - pricing and provisioning posture truthful - support contact present -## Degraded-state guidance +## Operator adjunct families -If the auth server or release manifest is degraded: +HyperTwist already has real adjunct operator surfaces around the simulator. + +- current bounded speech/microphone/transcript, narration, and model-custody lanes are real +- provider-neutral routing, BYOK/profile custody, and usage/cost governance shells are real +- continuity, memory, notes, knowledge, and provenance-aware workflow families are real +- these are operator-grade support surfaces around the simulator, not a claim that the website itself becomes the training runtime + +## Degraded-state and recovery guidance + +### Browser auth degraded or mixed + +- use degraded browser posture for bounded continuity, not as a silent claim of full production authority +- use the protected dashboard to inspect what still works and what remains intentionally withheld +- clear missing auth env vars and origin/runtime warnings before treating browser auth as fully production-ready + +### Release authority temporarily unavailable + +- keep fallback release context separate from real raw package-delivery authority +- use package proof, notices, and release references for orientation while live manifest authority is degraded +- refresh the protected release lane first, then escalate if rollout or entitlement work remains blocked + +### Desktop-first continuity during recovery - keep public posture and protected fallback guidance separate from live release authority -- do not treat fallback continuity as proof of full production readiness +- do not treat fallback continuity as proof of full production readiness or full public-launch readiness - use the protected launch-status and support routes for the next truthful move -## Support lanes +## Support and escalation lanes -Use the public or protected support path according to the problem: +### Account and entitlement issues -- launch readiness - - checkout wiring - - release target publication - - notice and corresponding-source follow-through -- operator access - - sign-in - - entitlement - - protected download access - - pairing -- studio rollout - - broader deployment planning - - higher-dimensional readiness review - - production-lane coordination +- missing plan access, absent download buttons, or failed desktop-link pairing belong to the protected dashboard lane +- confirm auth, billing, and entitlement posture before troubleshooting simulator behavior + +### Download and install issues + +- confirm the selected platform, release version, and package validation summary first +- recheck notices, release notes, and rollout instructions before redistributing the build +- escalate with the exact target platform and release channel when the package itself is the issue + +### Runtime and training issues + +- call out whether the issue affects classic-cube training, replay/coaching, or higher-dimensional family maps +- separate unfinished XR/controller/preferences expectations from actual regressions in the shipped keyboard/mouse lanes +- keep MagicTile browser-host behavior and dedicated-family packaged-map behavior distinguished when reporting issues + +### Rollout and compliance issues + +- route pricing, notices, and corresponding-source questions through the public/support lane +- keep package, pricing, and legal posture tied together before broader operator rollout + +## Canonical route atlas + +### Public routes + +- `/` + - shortest truthful overview of the product, surface split, and release posture +- `/about` + - product rationale and higher-dimensional seriousness in operator-grade language +- `/features` + - capability truth rather than pitch language +- `/resources` + - public reference portal for rollout, simulator, and training surfaces +- `/getting-started` + - canonical first-session manual from browser access into the native runtime +- `/launch-status` + - canonical public rollout and blocker authority page +- `/docs` + - the richest public product-safe manual surface +- `/support` + - recovery and escalation lane selection +- `/pricing` + - plan comparison with topology and launch posture kept honest +- `/download` + - supported targets, package proof, and protected-delivery handoff +- `/changelog` + - operator-facing shipping chronology +- `/open-source-notices` + - legal-distribution and corresponding-source follow-through +- `/privacy` + - browser-account and desktop-runtime boundary wording +- `/terms` + - access model and protected-download boundary +- `/shipping-payment` + - digital-delivery and payment posture + +### Protected routes + +- `/app` + - signed-in overview, account posture, and next operator move +- `/app/launch-status` + - signed-in rollout authority and release follow-through +- `/app/downloads` + - protected release lane and entitled desktop delivery +- `/app/browser-access` + - protected browser-shell posture and boundary explanation +- `/app/account` + - signed-in plan, session, and auth-method continuity +- `/app/notices` + - protected distribution references and compliance follow-through Primary support contact: - `hello@hypertwist.app` -## Canonical public routes - -- `/` -- `/about` -- `/features` -- `/resources` -- `/getting-started` -- `/docs` -- `/pricing` -- `/download` -- `/support` -- `/changelog` -- `/launch-status` -- `/open-source-notices` -- `/privacy` -- `/terms` -- `/shipping-payment` - -Primary protected routes: - -- `/app` -- `/app/launch-status` -- `/app/downloads` -- `/app/browser-access` -- `/app/account` -- `/app/notices` - ## Final operating rule Read HyperTwist as a desktop-first simulator with a necessary browser shell diff --git a/website/src/site-data.ts b/website/src/site-data.ts index d3c6832..c56ec6e 100644 --- a/website/src/site-data.ts +++ b/website/src/site-data.ts @@ -1143,6 +1143,11 @@ export const publicManualRouteAtlasCards = [ ] as const export const changelogEntries = [ + { + date: 'June 30, 2026', + title: 'Downloadable operator manual now mirrors the richer public manual routes', + details: 'The same-origin offline operator manual is no longer the thinner sibling of the live website. It now mirrors the richer public/manual lane with browser-auth posture, protected release handoff, concrete desktop workflow tracks, the shipped control roster, higher-dimensional family guidance, operator adjunct families, recovery guidance, and a public/protected route atlas so rollout teams can carry one substantial offline reference without inventing a second product story.', + }, { date: 'June 30, 2026', title: 'Homepage and About now answer the browser-versus-desktop boundary directly',