# HyperTwist Phase 3R Packet 3R-B Hypercubing.xyz Implementation

Created on `2026-05-13`

## Status

`Phase 3R / Packet 3R-B` is now `closed`.

This packet converts `Hypercubers/hypercubing.xyz` from the retained knowledge, curriculum, notation, and community anchor into a landed first-party HyperTwist knowledge-reference lane.

It does not reopen `Phase 0R`, `Phase 1R`, or `Phase 2R-B`.

Those earlier packets still own source-value extraction, retained-set routing, and ownership boundaries.

This packet owns the next question instead:

- what first-party implementation actually landed
- which donor value was realized
- what remains explicitly out of scope for this lane
- what validation was completed
- what the next bounded implementation move is after this landing

## Authority order

For future work on the `Hypercubers/hypercubing.xyz` lane, read in this order:

1. this packet for first-party landing scope, accepted widening, and validation result
2. [HYPERTWIST_LIVE_LANES_SOURCE_AND_PRESERVATION_AUDIT_2026-05-13.md](C:/HyperTwist/docs/HYPERTWIST_LIVE_LANES_SOURCE_AND_PRESERVATION_AUDIT_2026-05-13.md:1) for live-lane preserve posture
3. [HYPERTWIST_PHASE_2R_PACKET_2R_B_OWNERSHIP_AND_ACCEPTANCE_CONTRACT_2026-05-13.md](C:/HyperTwist/docs/HYPERTWIST_PHASE_2R_PACKET_2R_B_OWNERSHIP_AND_ACCEPTANCE_CONTRACT_2026-05-13.md:1) for ownership boundaries and pre-widening acceptance markers
4. [HYPERTWIST_PHASE_0R_PACKET_0R_B_EVALUATION_2026-05-12.md](C:/HyperTwist/docs/HYPERTWIST_PHASE_0R_PACKET_0R_B_EVALUATION_2026-05-12.md:1) for source-value extraction and non-promotion rationale
5. [REPO_LICENSE_TRACKING.md](C:/HyperTwist/docs/REPO_LICENSE_TRACKING.md:1) for license and notice obligations

## Packet licensing snapshot

- `Hypercubers/hypercubing.xyz`: `MIT`

Checked local license note:

- [LICENSE](C:/Workspaces/HyperTwist/mirrors/permissive/Hypercubers/hypercubing.xyz/LICENSE:1) currently uses the notice `Copyright (c) 2023 Hypercubers`

## Packet result

`3R-B` lands `Hypercubers/hypercubing.xyz` as:

- `implemented_live_permissive`
- `landed_permissive_preserve`

Current portfolio effect:

- curated HyperTwist shallow-eval set: `71`
- currently verified live in checked Unreal surfaces: `8`
- permissive live lanes: `7`
- restrictive live clean-room lanes: `1`
- active non-live implementation-board rows: `51`

## Donor source surfaces read

The source read for this widening remained bounded to the retained knowledge, notation, progression, software-comparison, and leaderboard domains:

- [README.md](C:/Workspaces/HyperTwist/mirrors/permissive/Hypercubers/hypercubing.xyz/README.md:1)
- [LICENSE](C:/Workspaces/HyperTwist/mirrors/permissive/Hypercubers/hypercubing.xyz/LICENSE:1)
- [docs/progression.md](C:/Workspaces/HyperTwist/mirrors/permissive/Hypercubers/hypercubing.xyz/docs/progression.md:1)
- [docs/notation.md](C:/Workspaces/HyperTwist/mirrors/permissive/Hypercubers/hypercubing.xyz/docs/notation.md:1)
- [docs/software/index.md](C:/Workspaces/HyperTwist/mirrors/permissive/Hypercubers/hypercubing.xyz/docs/software/index.md:1)
- [docs/software/hyperspeedcube.md](C:/Workspaces/HyperTwist/mirrors/permissive/Hypercubers/hypercubing.xyz/docs/software/hyperspeedcube.md:1)
- [hooks/feature_matrix.py](C:/Workspaces/HyperTwist/mirrors/permissive/Hypercubers/hypercubing.xyz/hooks/feature_matrix.py:1)
- [leaderboards/generate_leaderboards.py](C:/Workspaces/HyperTwist/mirrors/permissive/Hypercubers/hypercubing.xyz/leaderboards/generate_leaderboards.py:1)
- [leaderboards/formats.yml](C:/Workspaces/HyperTwist/mirrors/permissive/Hypercubers/hypercubing.xyz/leaderboards/formats.yml:1)
- [leaderboards/tabs.yml](C:/Workspaces/HyperTwist/mirrors/permissive/Hypercubers/hypercubing.xyz/leaderboards/tabs.yml:1)
- [leaderboards/solvers.yml](C:/Workspaces/HyperTwist/mirrors/permissive/Hypercubers/hypercubing.xyz/leaderboards/solvers.yml:1)

## First-party landing surfaces

The landed first-party Unreal surfaces are:

- [HyperTwistTrainingKnowledgeLibrary.h](C:/HyperTwist/UnrealHyperTwist/Source/UnrealHyperTwist/Public/HyperTwistTraining/HyperTwistTrainingKnowledgeLibrary.h:1)
- [HyperTwistTrainingKnowledgeLibrary.cpp](C:/HyperTwist/UnrealHyperTwist/Source/UnrealHyperTwist/Private/HyperTwistTraining/HyperTwistTrainingKnowledgeLibrary.cpp:1)
- [HyperTwistTrainingRuntimeLibrary.h](C:/HyperTwist/UnrealHyperTwist/Source/UnrealHyperTwist/Public/HyperTwistTraining/HyperTwistTrainingRuntimeLibrary.h:1)
- [HyperTwistTrainingRuntimeLibrary.cpp](C:/HyperTwist/UnrealHyperTwist/Source/UnrealHyperTwist/Private/HyperTwistTraining/HyperTwistTrainingRuntimeLibrary.cpp:1)
- [hypertwist-reference-incorporation-targets.json](C:/HyperTwist/UnrealHyperTwist/Content/HyperTwistTraining/MaterializedCatalog/hypertwist-reference-incorporation-targets.json:1)
- [hypertwist-catalog-materialization-summary.json](C:/HyperTwist/UnrealHyperTwist/Content/HyperTwistTraining/MaterializedCatalog/hypertwist-catalog-materialization-summary.json:1)
- [hypercubing-xyz-reference-pages.jsonl](C:/HyperTwist/UnrealHyperTwist/Content/HyperTwistTraining/MaterializedCatalog/raw-extracts/hypercubing-xyz-reference-pages.jsonl:1)

## Landed implementation scope

What landed:

- a first-party compiled knowledge-reference bundle for hypercubing taxonomy, notation, progression, software comparison, solver profiles, and leaderboard event definitions
- first-party search and lookup helpers for taxonomy nodes, notation terms, progression stages, software references, and leaderboard events
- first-party leaderboard formatting helpers for duration labels, move-count labels, relative-date labels, and program badge resolution
- a runtime-library entry point that exposes the bundled Hypercubing knowledge-reference surface through the central training API layer
- bundled first-party catalog reference targets for progression, notation, software-matrix, and leaderboard/report surfaces
- bundled raw source-reference capture for the four new Hypercubing reference-target families

What that means in practice:

- `Hypercubers/hypercubing.xyz` now owns the landed permissive knowledge, curriculum, notation, and community-reference lane in HyperTwist
- the lane is live as compiled first-party Unreal data and helpers, not only as planning or documentation intent
- the lane is also visible in the bundled catalog-reference surface, so later packets can discover the preserved factual targets without re-reading donor mirrors

## Preserved landed value

The donor value that was actually promoted is:

- progression-ladder ordering across `3D`, `4D`, non-Euclidean, and `5D+` learning surfaces
- hypercubing notation grammar for cells, piece labels, twist naming, slice layers, wide moves, plane rotations, and turn metrics
- software-comparison capability taxonomy for primary hypercubing tools and their puzzle-family roles
- community-reference event identity and display rules for leaderboard/report surfaces
- solver-profile naming conventions and program-badge conventions from the donor leaderboard generator

## Excluded or non-promotion boundary

Do not promote this lane into:

- runtime semantics, puzzle simulation, or solver execution ownership
- recognition, reconstruction, or timer execution ownership
- the host application shell or static-site architecture owner
- a replacement for `HactarCE/Hyperspeedcube`, `kkoomen/qbr`, or the already-landed training subsystems

Rationale:

- this repo was retained because it is the strongest bounded knowledge and community-reference donor in the set
- its value is high precisely because it codifies taxonomy, notation, progression, and reporting conventions without trying to own the core runtime
- runtime, recognition, timer, and topology ownership remain elsewhere in the retained and landed portfolio

## Acceptance markers satisfied

The `2R-B` acceptance markers for this row are now satisfied in first-party Unreal surfaces:

- a first-party knowledge and taxonomy schema exists for puzzles, methods, software, and progression stages
- a first-party notation reference contract exists with glossary terms, examples, and cross-linking boundaries
- a first-party progression contract exists with stage identity, prerequisites, learning-order metadata, and display grouping
- a first-party leaderboard/report contract exists with event IDs, solver profiles, formatted time rules, relative-date rules, and program badge rules

## Validation

Validation completed for this packet:

- `git diff --check` passed apart from CRLF conversion warnings
- JSON validation passed for the updated materialized-catalog files and workspace manifest
- Unreal build succeeded with:
  - `C:\Program Files\Epic Games\UE_5.7\Engine\Build\BatchFiles\Build.bat UnrealHyperTwistEditor Win64 Development C:\HyperTwist\UnrealHyperTwist\UnrealHyperTwist.uproject -WaitMutex -NoHotReloadFromIDE`

Build result:

- `Succeeded` on `2026-05-13`

## Next move

The next bounded move is `Phase 3R-C`:

- widen `apache/echarts` as the retained analytics, reporting, and progress-visualization lane
- keep the newly landed `Hypercubers/hypercubing.xyz` knowledge-reference lane on preserve-and-enhance footing rather than treating it as an open donor candidate again
