Broaden HyperTwist public manual coverage

This commit is contained in:
axiomlogicnexus 2026-06-29 18:22:17 +00:00
parent e197fbe2ea
commit e9827c7e66
5 changed files with 167 additions and 16 deletions

View file

@ -1515,10 +1515,76 @@ Latest exact-state audit confirmation later on `2026-06-29`:
- `website/server/` again retained only the same already-documented upstream
`supertokens-node -> nodemailer` residual advisory
- current truthful reading after this confirmation:
- no remaining `sentrux` structural debt is currently being reported by the
owned HyperTwist source-only gate
- vanilla refactoring is complete as a toolchain-ownership and
regression-loop task inside HyperTwist
- future refactors should now be selected for real simulator, website, or
native-runtime value rather than for missing analyzer adoption or stale
proof drift
- the HyperTwist-owned regression loop is healthy, but the source-only gate
still reports one remaining `god file` hotspot in the training repository
library
- vanilla refactoring is not yet fully complete as a code-shape task, even
though toolchain ownership and the regression loop themselves are now
established and repeatable inside HyperTwist
- future refactors should keep being selected for real simulator, website,
or native-runtime maintainability value rather than for missing analyzer
adoption or stale proof drift
Latest exact-source public/manual parity follow-up later on `2026-06-29`:
- the next same-family continuation widened the public/manual lane so the
website no longer underreports shipped feature-registry families outside the
core recognition plus higher-dimensional story:
- homepage capability and shipping summaries now also surface the live
speech/voice, provider-governance, and continuity/provenance adjunct
families
- the public feature atlas and docs lane now carry a dedicated advanced
adjunct section for those same shipped families
- the resources portal now also exposes those adjunct families directly
rather than leaving them implicit inside deeper canonical docs only
- the shared public FAQ and public changelog now also answer and record that
same broader shipped posture explicitly
- the HyperTwist-owned browser/distribution umbrella stayed green again on
that broader exact-source state:
- `scripts/run-hypertwist-web-surface-validation.sh`
- focused website route/auth/release validation:
- `14` files passed
- `82` tests passed
- deployment/readiness tooling validation:
- `3` files passed
- `30` tests passed
- `website/server` validation:
- `10` files passed
- `36` tests passed
- website plus `Content/Browser` production builds passed
- `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
- the owned structural loop still stayed stable on that same exact-source
state:
- `scripts/run-hypertwist-sentrux-source-only.sh`
- `Quality: 6234`
- all `7` rules pass
- `scripts/run-hypertwist-sentrux-gate.sh`
- comparison result:
- `Quality: 6234 -> 6234`
- `Coupling: 0.15 -> 0.15`
- `Cycles: 0 -> 0`
- `God files: 1 -> 1`
- `No degradation detected`
- `scripts/run-hypertwist-gitnexus-analyze.sh`
- the retained local CLI again failed cleanly on this Linux host because of
the cross-platform `LadybugDB` native payload mismatch
- the wrapper truthfully fell back to `npx gitnexus@latest`
- bounded mirror result:
- `16,430` nodes
- `38,826` edges
- `678` clusters
- `300` flows
- `scripts/run-hypertwist-gitnexus-status.sh`
- `Indexed commit: 3d20ea5`
- `Current commit: 3d20ea5`
- bounded mirror `Status: up-to-date`
- current truthful reading after this follow-up:
- the public/manual lane now represents more of the actually shipped product
surface without widening into speculative branches
- the HyperTwist-owned toolchain still says one remaining large repository
hotspot exists, so the next native refactor seam remains a real task
- the right next refactor target remains the same-family training-repository
extraction work rather than reopening browser or product topology

View file

@ -2317,13 +2317,13 @@ Latest same-family responsive public-route expansion follow-up on `2026-06-29`:
the cross-platform `LadybugDB` native payload mismatch
- the wrapper truthfully fell back to `npx gitnexus@latest`
- bounded mirror result:
- `16,406` nodes
- `38,773` edges
- `677` clusters
- `16,430` nodes
- `38,826` edges
- `678` clusters
- `300` flows
- `scripts/run-hypertwist-gitnexus-status.sh`
- `Indexed commit: 7ec96c8`
- `Current commit: 7ec96c8`
- `Indexed commit: 3d20ea5`
- `Current commit: 3d20ea5`
- bounded mirror `Status: up-to-date`
- the full owned web-surface gate then reran green on the same exact state:
- `scripts/run-hypertwist-web-surface-validation.sh`
@ -2342,16 +2342,21 @@ Latest same-family responsive public-route expansion follow-up on `2026-06-29`:
- `website/server/` again retained only the same already-documented upstream
`supertokens-node -> nodemailer` residual advisory
- current truthful reading after this refresh:
- no remaining `sentrux` structural debt is currently being reported by the
owned HyperTwist source-only gate
- vanilla refactoring is complete as a toolchain-ownership and
regression-loop task inside HyperTwist
- the HyperTwist-owned regression loop is healthy, but the source-only gate
still reports one remaining `god file` hotspot in the training repository
library
- vanilla refactoring is not yet fully complete as a code-shape task, even
though toolchain ownership and the regression loop themselves are now
established and repeatable inside HyperTwist
- the next worthwhile refactors should keep being chosen for real simulator,
website-manual, or native-runtime value rather than for missing analyzer
adoption or stale proof drift
- the browser surface remains complementary rather than superfluous because
it owns account, rollout, billing, notices, release posture, and browser-
to-desktop handoff while the simulator remains native and package-validated
- the public/manual lane now also surfaces the shipped speech, provider, and
continuity/provenance adjunct families more directly instead of flattening
public product truth down to recognition plus higher-dimensional runtime
## Latest responsive public/protected proof plus live preview-readiness rerun (`2026-06-29`)

View file

@ -4,6 +4,7 @@ import { SiteMetadata } from '../components/seo/SiteMetadata'
import { PublicLaunchStatus } from '../components/ui/PublicLaunchStatus'
import { ProductSurfaceMatrix } from '../components/ui/ProductSurfaceMatrix'
import {
advancedOperatorAdjunctTracks,
deploymentReadinessTracks,
featureAtlasCurrentTracks,
featureRegistryTierCards,
@ -55,6 +56,12 @@ export function FeaturesPage() {
cards={featureAtlasCurrentTracks}
/>
<BulletCardSection
title="Advanced live adjunct families"
description="The current product is broader than the core simulator loop alone. These adjacent operator-grade families are already implemented and should stay visible in public truth."
cards={advancedOperatorAdjunctTracks}
/>
<Section
title="Current surface authority map"
description="This is the clean public answer to the architecture question: public website, protected dashboard, embedded browser shell, native runtime, and the frozen browser-client branch each have different ownership."

View file

@ -7,6 +7,7 @@ import { PublicLaunchStatus } from '../components/ui/PublicLaunchStatus'
import { ProductSurfaceMatrix } from '../components/ui/ProductSurfaceMatrix'
import { brandConfig } from '../site-config'
import {
advancedOperatorAdjunctTracks,
capabilityPillars,
changelogEntries,
companyNarrative,
@ -518,6 +519,12 @@ export function ResourcesPage() {
description="This summary is deliberately practical: what you actually do in the desktop runtime once browser identity and release posture are already resolved."
/>
<BulletCardSection
title="Advanced operator adjuncts"
description="The resources portal should also surface the live speech, provider, and continuity families that surround the simulator, so teams do not mistake them for hidden internal-only work."
cards={advancedOperatorAdjunctTracks}
/>
<HigherDimensionalRuntimeGuideSection
title="Higher-dimensional runtime guide"
description="These public-safe cards explain which higher-dimensional family lanes are already real and what runtime posture each one actually uses."
@ -721,6 +728,12 @@ export function DocsPage() {
cards={featureAtlasCurrentTracks}
/>
<BulletCardSection
title="Advanced operator and continuity adjuncts"
description="The public manual is more truthful when it also surfaces the already-live speech, provider, and continuity families that support serious operator work around the simulator."
cards={advancedOperatorAdjunctTracks}
/>
<StepCardSection
title="Operator manual"
description="This is the public-facing manual for how HyperTwist is actually used today: browser first for identity and release posture, desktop first for the simulator."

View file

@ -24,6 +24,10 @@ export const capabilityPillars = [
title: 'Desktop-first distribution',
description: 'Browser account access supports the operator, while the real simulator and package-validation story remain desktop-first and Unreal-backed.',
},
{
title: 'Operator adjunct intelligence',
description: 'Speech capture, provider-neutral routing, usage governance, and continuity/provenance families already exist as real operator-grade adjunct surfaces around the simulator.',
},
] as const
export const deliverySurfaceCards = [
@ -287,6 +291,36 @@ export const featureAtlasCurrentTracks = [
},
] as const
export const advancedOperatorAdjunctTracks = [
{
title: 'Speech, voice, and capture adjuncts',
description: 'HyperTwist already owns bounded speech capture and narration families around the simulator instead of leaving all voice work as future intent.',
bullets: [
'Live microphone capture, permission/readiness workflows, and native capture-route control already ship in bounded first-party form.',
'Downloadable speech-model custody, transcript envelopes, faster-whisper orchestration, local narration, and advanced voice-model review all exist as operator-facing adjunct surfaces.',
'These are support-plane and runtime-adjacent capabilities; they do not change the desktop-first simulator authority.',
],
},
{
title: 'Provider routing, BYOK, and usage governance',
description: 'The product already includes provider-neutral AI or service governance instead of assuming one hidden backend forever.',
bullets: [
'Provider-neutral speech and vision contracts, BYOK/profile custody, custom-endpoint routing, and workflow-policy surfaces are already implemented.',
'Usage/cost dashboards, history/export, receipt review, settlement, and exception handoff already exist as operator-facing governance shells.',
'This keeps external-service posture inspectable without pretending browser billing or auth is the same thing as simulator execution.',
],
},
{
title: 'Continuity, memory, and provenance',
description: 'HyperTwist also ships continuity-oriented surfaces that keep replay, training, and publication state from collapsing into stateless sessions.',
bullets: [
'Session continuity, workspace recall, chronicle, notes, knowledge, and derived memory families are already in the live feature registry.',
'Provenance-aware replay or publication state plus ledger-style continuity and control-plane telemetry are part of the owned reference posture.',
'These families support serious operator and study workflows around the simulator rather than replacing the simulator itself.',
],
},
] as const
export const shippingNowCards = [
'Native Unreal training runtime, coaching cockpit, and generated-mode launch',
'Classic-cube timing, drill flows, local leaderboard persistence, and replay recording',
@ -294,6 +328,8 @@ export const shippingNowCards = [
'Embedded browser runtime with live operator/runtime diagnostics inside Unreal',
'MagicTile browser host bridge plus bounded native behavior proof',
'Higher-dimensional 120-cell and 5D runtime-state, projection, and persistence ownership',
'Speech capture, narration, and downloadable model-custody adjuncts',
'Provider-neutral routing, usage governance, and continuity or provenance support surfaces',
] as const
export const roadmapHonestyCards = [
@ -852,6 +888,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',
'Public manual now surfaces the live speech, provider, and continuity adjunct families too',
],
},
{
@ -870,6 +907,16 @@ export const resourceCollections = [
'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',
'Speech capture, narration, and model-custody adjunct posture',
],
},
{
title: 'Operator adjuncts',
items: [
'Provider-neutral routing, BYOK/profile custody, and custom-endpoint posture',
'Usage or cost dashboards, export history, receipts, settlement, and exception handoff',
'Continuity, memory, notes, and provenance-aware replay or publication state',
'Operator-safe reference surfaces around the simulator instead of generic AI-platform claims',
],
},
{
@ -1046,6 +1093,11 @@ export const publicManualRouteAtlasCards = [
] as const
export const changelogEntries = [
{
date: 'June 29, 2026',
title: 'Public manual now surfaces shipped speech, provider, and continuity adjunct families',
details: 'The homepage, feature atlas, docs, and resources now stop flattening HyperTwist down to recognition plus hypercubing only. Public-facing product truth now also carries the already-live speech capture and narration lane, provider-neutral routing and usage-governance shells, and the continuity or provenance families that support serious operator workflows around the desktop simulator.',
},
{
date: 'June 29, 2026',
title: 'Fresh exact-state audit kept the owned toolchain and release surfaces green',
@ -1346,6 +1398,14 @@ export const supportFaqs = [
question: 'Can I download a build immediately after sign-in?',
answer: 'Yes, once a release URL is configured for your plan. The dashboard also exposes a desktop-link token so the browser account can pair with the desktop app safely.',
},
{
question: 'Does HyperTwist already include voice or speech support?',
answer: 'Yes, in a bounded adjunct form. The live product already owns microphone capture, permission/readiness workflows, native capture-route control, transcript session envelopes, downloadable speech-model custody, Python transcription-service orchestration, local narration, and advanced voice-model review posture. Those are real operator-facing support surfaces around the simulator, not a claim that the website itself becomes the training runtime.',
},
{
question: 'Are provider routing and continuity features already real?',
answer: 'Yes, again in a bounded operator-grade form. HyperTwist already has provider-neutral speech or vision contracts, BYOK/profile custody, custom-endpoint routing, workflow-policy posture, usage/cost and settlement shells, plus continuity, memory, knowledge, notes, and provenance-aware replay or publication state families. These are adjunct governance and workflow surfaces around the simulator, not a claim that every external service is mandatory for core local training.',
},
{
question: 'Why is there an open-source notices page on pricing and download surfaces?',
answer: 'Because HyperTwist already carries explicit doctrine requiring public legal and corresponding-source linkage whenever a downloadable shipped build contains MPL-covered material.',