hypertwist/docs/HYPERTWIST_ROADMAP_OVERHAUL_EXPANSION_GUIDE.md
2026-04-27 00:26:45 +02:00

3.3 KiB

HyperTwist roadmap overhaul and expansion guide

Created on 2026-04-26

Purpose:

  • preserve the roadmap-overhaul decision inside the product repo docs root
  • make the current planning call visible without needing chat context
  • point future planning models or human reviewers to the richer workbook and parse-side planning pack

Product-level call

The original HyperTwist roadmap is still valuable.

It should remain preserved as the intent and lineage baseline.

It should not remain the sole live execution authority.

Why this changed

HyperTwist now has real owned implementation in the Unreal-centered backend across:

  • training
  • replay
  • recognition integration
  • coaching
  • queueing and scheduling
  • timing and analytics
  • clean-room governance

That means the product has outgrown a one-line-per-phase roadmap.

Use five planning surfaces:

  1. preserved historical roadmap baseline
  2. roadmap invariants
  3. live execution roadmap
  4. feature-set matrix
  5. model role and provider matrix

Timing call

Now is a good time for the overhaul because:

  • the backend is real enough to anchor planning
  • the repo state is clean
  • multi-model expansion has not yet been allowed to reshape architecture

Main rule for model expansion

Define roles first.

Evaluate providers second.

Integrate providers only after the roles and feature-set map exist.

Current correction call from the source-exposed audit:

  • preserve the roadmap direction
  • update the canonical planning docs so they reflect:
    • the reconciled 14-family feature set
    • manifest and custody governance gaps
    • pre-Phase-5 speech governance gates
    • retained benchmark-oracle and mirror-intake reservations

Higher-detail planning references

For the fuller planning pack, read:

  • C:\visual_studio_solutions\multi_project\GPT 5.4 HyperTwist parse\92-hypertwist-roadmap-overhaul-planning-layer.md
  • C:\visual_studio_solutions\multi_project\GPT 5.4 HyperTwist parse\93-hypertwist-roadmap-overhaul-document-map.md
  • C:\visual_studio_solutions\multi_project\GPT 5.4 HyperTwist parse\94-hypertwist-roadmap-overhaul-model-prompts.md
  • C:\visual_studio_solutions\multi_project\GPT 5.4 HyperTwist parse\95-hypertwist-roadmap-invariants.md
  • C:\visual_studio_solutions\multi_project\GPT 5.4 HyperTwist parse\96-hypertwist-live-execution-roadmap.md
  • C:\visual_studio_solutions\multi_project\GPT 5.4 HyperTwist parse\97-hypertwist-feature-set-matrix.md
  • C:\visual_studio_solutions\multi_project\GPT 5.4 HyperTwist parse\98-hypertwist-model-role-and-provider-matrix.md
  • C:\visual_studio_solutions\multi_project\GPT 5.4 HyperTwist parse\99-hypertwist-roadmap-expansion-established-insights.md
  • C:\visual_studio_solutions\multi_project\GPT 5.4 HyperTwist parse\roadmap-overhaul-pack\outputs\abc-phase-2-reconciled-roadmap-expansion.md
  • C:\visual_studio_solutions\multi_project\GPT 5.4 HyperTwist parse\roadmap-overhaul-pack\outputs\source-exposed-audit-reconciled.md
  • C:\Workspaces\HyperTwist\implementation-workspaces\scratch\roadmap-bootstrap\docs\architecture\roadmap-overhaul-and-expansion-readiness.md
  • C:\Workspaces\HyperTwist\implementation-workspaces\scratch\roadmap-bootstrap\docs\architecture\roadmap-expansion-pack-checkpoint.md

Safety rule

This overhaul should stay documentation-first until the new planning layer is accepted.