scriptoriumadmin/hypertwist
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

Expand HyperTwist public workflow manual

Browse source
This commit is contained in:
axiomlogicnexus 2026-06-30 00:33:57 +00:00
parent 152f5e4d62
commit d81339fde6
2 changed files with 86 additions and 0 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

31
website/src/pages/public-pages-marketing.tsx
View file

@ -12,6 +12,7 @@ import {
changelogEntries,
companyNarrative,
degradedStateRecoveryTracks,
desktopWorkflowTracks,
desktopFirstLaunchCards,
deploymentReadinessTracks,
digitalDeliveryCards,
@ -246,6 +247,12 @@ export function HomeLanding() {
</div>
</Section>
<StepCardSection
title="Desktop workflows already supported"
description="The homepage is more useful when it also points at the concrete desktop workflows the software already supports today."
cards={desktopWorkflowTracks.slice(0, 3)}
/>
<OperatorDesktopQuickstartSection title="What the first serious session should look like" />
<SurfaceChoiceGuideSection description="This is the shortest practical answer to the browser-versus-desktop question: stay public for release-safe context, move protected for account-aware release work, and move native for the actual simulator." />
@ -332,6 +339,12 @@ export function AboutPage() {
</div>
</Section>
<StepCardSection
title="How the software is actually used"
description="These are the practical desktop and operator workflows that already exist behind the product narrative."
cards={desktopWorkflowTracks}
/>
<SurfaceChoiceGuideSection description="Keeping the website and the desktop build together only makes sense if the handoff is explicit. This guide keeps the right surface choice visible in plain language." />
<PublicReleaseDecisionGuideSection
@ -514,6 +527,12 @@ export function ResourcesPage() {
</div>
</Section>
<StepCardSection
title="Practical software workflows"
description="These cards focus on how the actual software is used today once the browser shell has already done its access and rollout job."
cards={desktopWorkflowTracks}
/>
<SimulatorManualSection
title="Simulator use today"
description="This summary is deliberately practical: what you actually do in the desktop runtime once browser identity and release posture are already resolved."
@ -597,6 +616,12 @@ function GettingStartedPageContent({
cards={operatorManualTracks}
/>
<StepCardSection
title="Practical desktop workflows after first launch"
description="Once access and pairing are done, these are the concrete software workflows HyperTwist already supports in the native runtime."
cards={desktopWorkflowTracks}
/>
<BrowserAuthMethodsSection
description="The onboarding path is easier to trust when the shared-auth provider lineup is visible before operators cross into the protected shell."
/>
@ -740,6 +765,12 @@ export function DocsPage() {
cards={operatorManualTracks}
/>
<StepCardSection
title="Core software workflows"
description="This is the practical use manual for the actual software once access is resolved and the desktop runtime is in hand."
cards={desktopWorkflowTracks}
/>
<OperatorDesktopQuickstartSection />
<BrowserAuthMethodsSection

55
website/src/site-data.ts
View file

@ -387,6 +387,54 @@ export const operatorManualTracks = [
},
] as const
export const desktopWorkflowTracks = [
{
title: '1. Run a classic-cube training session',
description: 'Use the desktop runtime when the goal is actual practice, not product orientation.',
steps: [
'Launch the classic-cube training lane from the installed desktop runtime and confirm the HUD, timer, and scramble posture first.',
'Use the shipped classic control lane for turns, orbit, zoom, hint, fresh-attempt restart, and hold-to-talk behavior during the solve.',
'Treat this as the authoritative packaged practice loop rather than trying to reproduce it through the public website.',
],
},
{
title: '2. Run a recognition and correction workflow',
description: 'Use the desktop runtime when you need the real cube-state intake, correction, and solve-guidance lane.',
steps: [
'Calibrate and observe the cube through the bounded classic-cube recognition workflow in the native runtime.',
'Use the browser-assisted recognition shell, then resolve any manual corrections and accepted closure steps from the native training lane.',
'Read the reconstruction and solve-guidance output as desktop workflow truth, not as a claim that the public website itself performs the recognition job.',
],
},
{
title: '3. Review replay, coaching, and analytics',
description: 'Use the packaged desktop lane when the session needs replay continuity, coaching review, and outcome evidence in one place.',
steps: [
'Finish or import the training session, then open replay, coaching, and leaderboard or diagnostics surfaces inside the desktop runtime.',
'Use the current native analytics and review surfaces to inspect timing, progression, and coaching output before escalating or exporting anything outward.',
'Return to the browser shell only when account, release, entitlement, or support posture becomes the next real concern.',
],
},
{
title: '4. Open the higher-dimensional family lanes',
description: 'Use the packaged dedicated-family maps when training moves beyond the classic cube.',
steps: [
'Launch the dedicated Magic120Cell or MagicCube5D map from the desktop runtime instead of expecting a browser parity lane.',
'Use the shipped selector, focus, projection, symmetry or stereo, and visibility posture that the native operator surfaces already own explicitly.',
'Use selector recall when a valid generated-mode launch history exists, while still reading XR and controller widening as explicit No-Go until a later dedicated completion packet lands.',
],
},
{
title: '5. Return to the browser shell for operator governance',
description: 'Use the browser shell after or around sessions when the next job is commercial, operational, or release-facing rather than simulator-facing.',
steps: [
'Use the protected dashboard for plan, entitlement, browser-to-desktop pairing, and release-manifest review.',
'Use public or protected launch-status, notices, pricing, and release-notes routes when rollout, legal, or distribution posture changes.',
'Keep browser access issues separate from native runtime issues so support and rollout work stay attached to the correct surface.',
],
},
] as const
export const operatorDesktopQuickstartCards = [
{
title: '1. Resolve access and choose the right build',
@ -888,6 +936,7 @@ export const resourceCollections = [
'Roadmap-honest separation between shipped and retained capability',
'Release notes that surface what actually landed',
'Desktop-first simulator posture with browser-shell boundaries kept explicit',
'Practical software-workflow manual for classic-cube, recognition, replay, and higher-dimensional use',
'Public manual now surfaces the live speech, provider, and continuity adjunct families too',
],
},
@ -904,6 +953,7 @@ export const resourceCollections = [
title: 'Training depth',
items: [
'Classic-cube recognition and correction workflows',
'Step-by-step desktop workflow guidance for practice, review, and higher-dimensional sessions',
'Replay, coaching, analytics, and package validation posture',
'Higher-dimensional puzzle-family references and browser-host boundaries',
'120-cell and 5D dedicated-family runtime ownership overview',
@ -1093,6 +1143,11 @@ export const publicManualRouteAtlasCards = [
] as const
export const changelogEntries = [
{
date: 'June 30, 2026',
title: 'Public manual now teaches concrete desktop workflows across the main operator routes',
details: 'Home, About, Getting Started, Docs, and Resources now include first-party practical workflow cards for classic-cube training, recognition and correction, replay/coaching review, higher-dimensional session use, and browser-return governance. The public site no longer explains topology and readiness only; it now also teaches how the current software is actually used.',
},
{
date: 'June 29, 2026',
title: 'Public manual now surfaces shipped speech, provider, and continuity adjunct families',