# HyperTwist cubing.js Reference Incorporation Provenance Board - 2026-05-27

## Status

This document is the source-backed provenance and hierarchy note for the live
repo-backed reference-incorporation side currently materialized from
`cubing/cubing.js`.

It closes the source-specific reference side that remained implicit after the
landed `Phase 4R-A` packet and the broader live-lane and `MPL`-boundary
audits.

It answers one narrow question:

- do the live `cubing/cubing.js` reference targets reopen already landed
  first-party classic-cubing semantic/runtime and `MPL`-boundary
  implementation, or do they instead need a reference-side provenance-board and
  canon backfill

Result:

- no product-code reopening is required
- yes reference-side provenance-board and feature-canon backfill is required

## Source basis

- `C:\HyperTwist\docs\HT_REPO_INCORPORATION_AUDIT_2026-05-11.md`
- `C:\HyperTwist\docs\HYPERTWIST_PHASE_4R_PACKET_4R_A_CUBING_JS_ADAPTER_IMPLEMENTATION_2026-05-13.md`
- `C:\HyperTwist\docs\HYPERTWIST_LIVE_LANES_SOURCE_AND_PRESERVATION_AUDIT_2026-05-13.md`
- `C:\HyperTwist\docs\REPO_LICENSE_TRACKING.md`
- `C:\HyperTwist\docs\ops\HYPERTWIST_MPL_BOUNDARY_AND_NON_GPL_USAGE_DOCTRINE_2026-05-25.md`
- `C:\HyperTwist\docs\v6_5_deep_manual_pack\HyperTwist\FEATURE_REGISTRY.md`
- `C:\HyperTwist\UnrealHyperTwist\Content\HyperTwistTraining\MaterializedCatalog\hypertwist-reference-incorporation-targets.json`
- `C:\HyperTwist\UnrealHyperTwist\Content\HyperTwistTraining\MaterializedCatalog\raw-extracts\cubing-cubing-js-reference-pages.jsonl`

## Counts confirmed from current first-party materialization

Current live `cubing/cubing.js` reference-incorporation targets:

- `7` total rewritten reference targets
- all `7` are under `Classic Cubing Semantics and Runtime`
- all `7` stay inside the already-landed `Phase 4R-A` bounded lane

Exact surfaces:

1. `reference/cubing-cubing-js-semantic-reference-page-stack`
   - `SurfaceType`: `classic-cubing-semantic-reference`
   - `IncorporationChannel`: `semantic-contract`
   - `TargetAssetFamily`: `semantic-contract-note`
2. `reference/cubing-cubing-js-geometry-reference-page-stack`
   - `SurfaceType`: `classic-cubing-geometry-reference`
   - `IncorporationChannel`: `geometry-contract`
   - `TargetAssetFamily`: `geometry-contract-note`
3. `reference/cubing-cubing-js-viewer-reference-page-stack`
   - `SurfaceType`: `classic-cubing-viewer-reference`
   - `IncorporationChannel`: `viewer-adapter-contract`
   - `TargetAssetFamily`: `viewer-adapter-note`
4. `reference/cubing-cubing-js-device-reference-page-boundary`
   - `SurfaceType`: `classic-cubing-device-reference`
   - `IncorporationChannel`: `device-adapter-boundary`
   - `TargetAssetFamily`: `device-boundary-note`
5. `reference/cubing-cubing-js-search-reference-page-stack`
   - `SurfaceType`: `classic-cubing-search-reference`
   - `IncorporationChannel`: `search-contract`
   - `TargetAssetFamily`: `search-contract-note`
6. `reference/cubing-cubing-js-bridge-reference-page-melinda`
   - `SurfaceType`: `classic-cubing-bridge-reference`
   - `IncorporationChannel`: `melinda-bridge-boundary`
   - `TargetAssetFamily`: `bridge-note`
7. `reference/cubing-cubing-js-compliance-reference-page-boundary`
   - `SurfaceType`: `classic-cubing-compliance-reference`
   - `IncorporationChannel`: `mpl-compliance-boundary`
   - `TargetAssetFamily`: `compliance-boundary-note`

Important adjacent fact:

- all seven targets preserve the explicit practical `MPL` path, notice
  retention, and future source-file publication duty boundary already enforced
  by the landed lane

## Slice-local verdict

| Slice | Primary authority | Secondary value kept | Result |
|---|---|---|---|
| First-party classic-cubing semantic/runtime and `MPL`-boundary implementation | first-party current code plus landed `Phase 4R-A` packet | retained `cubing/cubing.js` reference targets stay subordinate provenance-grounding surfaces | unchanged live implementation owner |
| Rewritten semantics, geometry, viewer, device, search, and Melinda-bridge grounding | `cubing/cubing.js` retained boundary-sensitive lane | factual classic-cubing state, geometry, viewer, protocol, search, and bridge semantics are preserved while prose remains first-party | unchanged retained reference-grounding surface beneath first-party contracts |
| `MPL` compliance and notice-boundary grounding | `cubing/cubing.js` retained boundary-sensitive lane | the practical `MPL` path, notice retention, and future modified-file publication duty stay explicit in first-party compliance notes | unchanged bounded compliance-grounding surface |

## Why no product-code reopening is required

The live surfaces here are already rewritten first-party targets, not copied
donor docs, donor Twizzle shell UI, or a silent upstream private fork.

The checked targets explicitly require:

- preserving factual semantic, geometry, viewer, device, search, bridge, and
  `MPL`-boundary semantics
- rewriting donor wording, donor docs/demo framing, and any broader donor
  product-shell assumptions

That means the retained surfaces are provenance and factual grounding, not
donor shell ownership.

So this pass does not reopen:

- the closed `Phase 4R-A` first-party classic-cubing lane
- the separate `cubing/twisty.js` clean-room replay shell lane
- the separate `cubing/alg.js` parser/AST lane
- any silent flattening of the `MPL` boundary into an untracked fork posture

## Current exact grounded role

`cubing/cubing.js` currently grounds seven live rewritten first-party
contract/reference targets for `Classic Cubing Semantics and Runtime`:

- semantic state, transformation, notation, and binary or Twizzle interop
- named-puzzle and geometry construction
- viewer, player, and editor adapter behavior
- smart-device and protocol adapter boundary
- search, scramble, and solve-helper contract
- bounded Melinda `2x2x2x2` bridge semantics
- practical `MPL` adapter and notice boundary

These targets preserve bounded classic-cubing semantics while keeping all
surfaced prose and shell framing first-party.

## Backfill result

### Earlier incorporation audit reopened

- `C:\HyperTwist\docs\HT_REPO_INCORPORATION_AUDIT_2026-05-11.md`

### Feature canon reopened

- `C:\HyperTwist\docs\v6_5_deep_manual_pack\HyperTwist\FEATURE_REGISTRY.md`

## Final call

The live `cubing/cubing.js` reference-incorporation side is now explicit:

- `7` rewritten first-party contract/reference targets
- all `7` remain inside the landed `Phase 4R-A` classic-cubing lane
- the practical `MPL` path, notice retention, and modified-file publication
  duty boundary stay explicit

This closes the `cubing/cubing.js` reference side without reopening product
code.
