hypertwist/docs/v6_5_deep_manual_pack/HyperTwist/DEVELOPMENT.md

HyperTwist — DEVELOPMENT.md

Development philosophy

HyperTwist should be developed as a serious native product:

• Unreal project as the main runtime
• C++ simulation and rendering core
• Blueprints for interaction and curriculum logic
• bounded CV or analytics sidecars where needed
• minimal web-only surface

Current development gate

Do not reopen broad donor-driven widening as if the whole retained portfolio were already settled.

Current truth:

• 9 repos are currently verified live in checked Unreal surfaces
• 8 are permissive MIT or Apache-2.0
• 1 is the restrictive onionhoney/roux-trainers lane that is already properly clean-roomed and implemented
• Phase 0R is now closed for the remaining 62 non-live rows
• Phase 1R is now closed as the retained-set contract and handoff overhaul
• Phase 2R is now closed as the retained-set ownership and acceptance packet sequence
• Phase 3R-A is now closed as the landed Aarav2709/KubeTimr widening packet
• Phase 3R-B is now closed as the landed Hypercubers/hypercubing.xyz widening packet
• Phase 3R-C is now closed as the landed apache/echarts widening packet

Next sequence:

1. preserve the nine landed lanes
2. use the retained-set contract as the only legal/roadmap routing surface for non-live rows
3. keep Aarav2709/KubeTimr, Hypercubers/hypercubing.xyz, and apache/echarts on preserve-and-enhance footing through their landed packets
4. continue broader permissive widening from Phase 3R-D

Suggested repo structure

• HyperTwist/
  • Source/HyperTwistCore
  • Source/HyperTwistSimulation
  • Source/HyperTwistRecognition
  • Source/HyperTwistReplay
  • Source/HyperTwistTraining
  • Source/HyperTwistCoach
  • Source/HyperTwistXR
• hypertwist-services/
  • optional CV inference service
  • optional progression or coaching service
• docs/
  • replay packet specs
  • trainer logic
  • notation / interchange specs
  • benchmark notes

Build order

1. preserve and document landed implementation truth
2. completed Phase 0R deep source evaluation reset for remaining rows
3. completed Phase 1R contract / handoff / provenance overhaul
4. completed retained-set ratification and packet design
5. permissive implementation waves from retained rows
6. boundary-sensitive adapter or sidecar waves
7. restrictive clean-room waves from retained rows
8. simulation core expansion from retained set
9. state and notation standardization
10. replay and export
11. physical recognition
12. trainer/progression
13. AI coach
14. immersive hyper modes
15. optimization and polish

Testing

• move/state correctness
• replay integrity
• scramble validity
• CV uncertainty handling
• coaching recommendation stability
• XR interaction reliability
• progression persistence and analytics