Reconcile cubing alg landed hierarchy

This commit is contained in:
axiomlogicnexus 2026-05-27 05:58:21 +02:00
parent a94d996a7d
commit 3f9e044210
4 changed files with 216 additions and 1 deletions

View file

@ -0,0 +1,196 @@
# HyperTwist Algorithm-Language And Training-Semantic Hierarchy Reconciliation - 2026-05-27
## Status
This document is the source-backed reconciliation note for the current
algorithm-language and training-semantic family across:
- `cubing/alg.js`
- the landed first-party `HyperTwistAlgorithm/*` owner lane
- the current first-party training-runtime consumer surfaces
- adjacent classic-cubing semantics and viewer/runtime lanes that must not
absorb this donor
It answers one narrow question:
- does the current `cubing/alg.js` source require reopening the landed bounded
first-party algorithm-language owner lane before any future semantic,
consumer, or shell packet is considered
Result:
- no product-code reopening is required
- yes selective authority backfill is required so candidate-era metadata no
longer understates the already-landed owner lane
- the exact current owner slice remains narrow: algorithm-language parser, AST,
traversal, validation, keyboard mapping, and share/interchange semantics
## Source basis
- `C:\HyperTwist\docs\HYPERTWIST_PHASE_0R_PACKET_0R_D_EVALUATION_2026-05-13.md`
- `C:\HyperTwist\docs\REPO_LICENSE_TRACKING.md`
- `C:\HyperTwist\docs\v6_5_deep_manual_pack\HyperTwist\FEATURE_REGISTRY.md`
- `C:\Workspaces\HyperTwist\repos.manifest.json`
- `C:\Workspaces\HyperTwist\clean-room-specs\cubing-alg-js.model-a.md`
- `C:\Workspaces\HyperTwist\clean-room-specs\outputs\cubing-alg-js.model-b-reconciled.md`
- `C:\Workspaces\HyperTwist\mirrors\restrictive\cubing\alg.js\README.md`
- `C:\Workspaces\HyperTwist\mirrors\restrictive\cubing\alg.js\src\parser.ts`
- `C:\Workspaces\HyperTwist\mirrors\restrictive\cubing\alg.js\src\json.ts`
- `C:\Workspaces\HyperTwist\mirrors\restrictive\cubing\alg.js\src\traversal.ts`
- `C:\Workspaces\HyperTwist\mirrors\restrictive\cubing\alg.js\src\validation.ts`
- `C:\Workspaces\HyperTwist\mirrors\restrictive\cubing\alg.js\src\keyboard.ts`
- `C:\Workspaces\HyperTwist\mirrors\restrictive\cubing\alg.js\src\url.ts`
- current first-party runtime and test authority under:
- `C:\HyperTwist\UnrealHyperTwist\Source\UnrealHyperTwist\Public\HyperTwistAlgorithm`
- `C:\HyperTwist\UnrealHyperTwist\Source\UnrealHyperTwist\Private\HyperTwistAlgorithm`
- `C:\HyperTwist\UnrealHyperTwist\Source\UnrealHyperTwist\Private\HyperTwistTraining\HyperTwistTrainingRuntimeLibrary.cpp`
## Slice-local verdict
| Slice | Primary authority | Secondary value kept | Route | Width | Result |
| --- | --- | --- | --- | --- | --- |
| Algorithm-language parser, owned AST, traversal, validation, keyboard mapping, and share/interchange semantics | first-party `HyperTwistAlgorithm/*` lane grounded in `cubing/alg.js` | retained donor lineage only | `R3` | `F2` | unchanged live implementation owner |
| Training-runtime parse/store/serialize adoption of the active algorithm sequence | first-party training runtime | `cubing/alg.js` remains upstream lineage only | existing first-party route | `F2` | unchanged consumer owner |
| Broader classic-cubing semantics, puzzle-state ownership, and viewer/runtime shells | `cubing/cubing.js`, `cubing/twisty.js`, and first-party runtime owners | none required from `cubing/alg.js` | existing adjacent routes | `F2` | unchanged adjacent owners |
## Why no product-code reopening is required
### `cubing/alg.js`
The donor still owns the narrow algorithm-language center of gravity:
- parser boundary
- durable immutable AST family
- traversal and transform behavior
- validation profiles and structured issues
- keyboard-to-move mapping
- URL/share and structured interchange helpers
That retained slice is still the correct one. It does not widen into puzzle
state, runtime, viewer, device, or solver ownership.
### Landed first-party owner lane
The first-party owner lane is already live and closed in current code:
- public owner surfaces exist under `Public/HyperTwistAlgorithm`
- private implementation surfaces exist under `Private/HyperTwistAlgorithm`
- current training-runtime adoption is already wired through
`UHyperTwistTrainingRuntimeLibrary::ParseAlgJs` and `SerializeAlgJs`
- the repo-local reconciled note already records `Bounds 1-4 closed`
- automation coverage exists in `HyperTwistAlgorithmAutomationTests.cpp`
That means the same-bound owner work is already landed. This pass does not find
an owner-side gap that justifies reopening it.
### Current training-runtime consumer seam
The checked consumer seam is narrow and appropriate:
- training runtime parses text through the first-party parser
- training runtime stores the active algorithm sequence in the training
subsystem
- training runtime serializes back through the first-party serializer
That is consumer adoption above the owner lane, not evidence that the
algorithm-language lane itself is still incomplete.
## Selective backfill result
### Earlier packet reopened
- `C:\HyperTwist\docs\HYPERTWIST_PHASE_0R_PACKET_0R_D_EVALUATION_2026-05-13.md`
### Earlier standing note reopened
- `C:\Workspaces\HyperTwist\clean-room-specs\cubing-alg-js.model-a.md`
### Manifest row reopened
- `C:\Workspaces\HyperTwist\repos.manifest.json`
### Additional canon reopened
- `C:\HyperTwist\docs\REPO_LICENSE_TRACKING.md`
- `C:\HyperTwist\docs\v6_5_deep_manual_pack\HyperTwist\FEATURE_REGISTRY.md`
### Reason
The landed lane itself was already correct. The stale part was the metadata:
- the canonical `Model A` handoff still described the row as not yet verified
live
- the manifest row still preserved the older reset-era wording
- the tracker and registry were accurate at a high level but still too compact
to express the exact narrow landed owner slice and the consumer-owner
separation cleanly
### Change class
- repo-local extraction did not change
- landed owner interpretation was confirmed rather than reversed
- dependent canon was sharpened so the lane stays narrow and clearly closed
- no product-code change occurred
### What remained valid
- the restrictive `GPL-3.0-or-later` clean-room route remained valid
- the original `0R-D` decision to keep `cubing/alg.js` separate from
`cubing/cubing.js` custody remained valid
- the repo-local `Bounds 1-4 closed` conclusion remained valid
### What changed
The dependent canon now makes the current landed role explicit:
- keep `cubing/alg.js` grounded first-party ownership inside
`HyperTwistAlgorithm/*`
- keep training-runtime parse/store/serialize behavior as a consumer seam, not
as proof that the owner lane is still open
- keep puzzle-state semantics, runtime ownership, and viewer/player ownership
with their adjacent lanes
- do not reopen the closed `Bound 1` through `Bound 4` sequence by default
## Propagation result
### Feature registry
Updated.
The registry now says what is actually live: first-party algorithm-language
ownership is real for parser, AST, traversal, validation, keyboard mapping, and
share/interchange semantics, while training-runtime adoption remains a consumer
surface above it.
### Cross-lane doctrine
No doctrine wording change was needed.
This pass applied the existing `A/R/F` hierarchy; it did not change the
hierarchy rules themselves.
### Skillization
No doctrine or `SKILLS.md` change was needed.
This pass did not create or reopen any command or skill surface.
### Legal evidence
No license-status or mirror-custody change occurred.
The repo-row tracker, feature registry, manifest row, and canonical handoff
status were sharpened instead.
## Operational answer
Before any future consumer-side semantic shell, registry, or broader
algorithm-facing packet is considered, the correct move was this authority
backfill first.
After this pass:
- do not reopen `Bound 1`, `Bound 2`, `Bound 3`, or `Bound 4`
- do not reinterpret training-runtime adoption as a same-bound owner gap
- if later work is justified, scope it as a new consumer-owner or shell packet
above the closed algorithm-language owner lane

View file

@ -242,6 +242,16 @@ Integration call:
- use it in `Phase 2R` to freeze first-party parser, AST, validation, serialization, keyboard-input, and URL/interchange contracts
- refresh the Model A handoff with the deeper node-family and traversal findings
- if later implementation proceeds, schedule Model B work in `Phase 5R`, not as direct donor use
- current `2026-05-27` reconciliation overlay:
- repo-local extraction unchanged
- the first-party `HyperTwistAlgorithm/*` owner lane is now verified live and
closed through `Bound 4`
- current training-runtime parse/store/serialize usage is a consumer seam,
not a same-bound owner gap
- keep broader classic-cubing semantics with `cubing/cubing.js` and
viewer/player ownership with `cubing/twisty.js`
- do not reopen `Bound 1` through `Bound 4` by default; later work must be a
new consumer-owner or shell packet if justified
### `cubing/twisty.js`

View file

@ -1024,6 +1024,15 @@ Approved working posture:
- treat it as its own Model A extraction line for parser, AST, traversal, validation, keyboard, and URL/interchange semantics
- Model B must not read the mirror
- Model B may only consume `C:\Workspaces\HyperTwist\clean-room-specs\cubing-alg-js.model-a.md`
- current `2026-05-27` reconciliation overlay:
- the bounded first-party `HyperTwistAlgorithm/*` owner lane is verified live
and closed through `Bound 4`
- the landed owner slice is parser, AST, traversal, validation, keyboard
mapping, and share/interchange semantics only
- checked training-runtime parse/store/serialize adoption stays a consumer
seam above that owner lane
- do not reopen the closed owner lane by default; later work must be a new
consumer-owner or shell packet if justified
### `cubing/twisty.js`

View file

@ -152,7 +152,7 @@ repo.
| Classic-cubing semantic/runtime adapter | Implemented now | landed `cubing/cubing.js` packet | Live adapter family. |
| Seeded competition scramble workflow and lightweight scramble-operator shell adjuncts | Deep-source grounded retained | `cubing/cubing.js` retained lane + `cubing/mark3` / `cubing/scramble.cubing.net` successor evaluation | Source-backed successor surfaces sharpen competition-spec workflow and operator-shell expectations above the retained scramble and visualization seams, but they do not displace `cubing/cubing.js` or `cubing/twisty.js`; `scramble-display` remains comparison-only. |
| Replay shell and timeline | Implemented now | landed `cubing/twisty.js` bounded packets | Replay/runtime viewer family is real. |
| Algorithm/training semantic lane | Implemented now | landed `cubing/alg.js` bounded packets | Semantic/training contract is real. |
| Algorithm/training semantic lane | Implemented now | landed `cubing/alg.js` bounded packets | First-party `HyperTwistAlgorithm/*` now owns the bounded parser, AST, traversal, validation, keyboard-mapping, and share/interchange contract grounded in `cubing/alg.js`; current training-runtime parse/store/serialize usage remains a consumer seam above that owner lane rather than proof that the lane is still open. |
| Readable classic-cube state/history and beginner-helper benchmark | Deep-source grounded retained | `vwcwong/CubeSim` retained clean-room benchmark lane | Retained as `A1 + R4 + F2` only for a small renderer-independent classic-cube state/history split, scramble parse or invert behavior, and beginner `LBL` decomposition benchmark for later clean-room lesson/debug/helper use. This does not displace the first-party canonical replay packet, training attempt/solve/review history, or the bounded classic-cube `Phase 6R-Q/R/S` explanation and correction shells. |
| Large-`N` classic-cube center/edge/parity strategy | Deep-source grounded retained | `ShellPuppy/RCube` retained benchmark/oracle lane | Retained as `A1 + R4 + F2` only for large-`N` classic-cube center-stage planning, edge-pairing/parity handling, and virtual-rotation strategy. This does not displace the landed `Hyperspeedcube`, `MagicTile`, `Magic120Cell`, or `MagicCube5D` higher-dimensional runtime families, and it does not reopen the bounded classic-cube `Phase 6R-Q/R/S` shell/state seams. |
| Hyper puzzle catalog | Implemented now | `Hyperspeedcube` bounded packet | Current realized hyper-puzzle entry slice. |