# HyperTwist magiccube4d 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
`cutelyaware/magiccube4d`.

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

It answers one narrow question:

- do the live `cutelyaware/magiccube4d` reference targets reopen already landed
  first-party legacy `4D` interaction, history, macro, topology, and
  provenance 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_B_MAGICCUBE4D_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\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\cutelyaware-magiccube4d-reference-pages.jsonl`

## Counts confirmed from current first-party materialization

Current live `cutelyaware/magiccube4d` reference-incorporation targets:

- `6` total rewritten reference targets
- all `6` are under `Legacy 4D Interaction and History`
- all `6` stay inside the already-landed `Phase 4R-B` bounded lane

Exact surfaces:

1. `reference/cutelyaware-magiccube4d-history-reference-page-stack`
   - `SurfaceType`: `legacy-4d-history-reference`
   - `IncorporationChannel`: `history-contract`
   - `TargetAssetFamily`: `history-contract-note`
2. `reference/cutelyaware-magiccube4d-macro-reference-page-stack`
   - `SurfaceType`: `legacy-4d-macro-reference`
   - `IncorporationChannel`: `macro-contract`
   - `TargetAssetFamily`: `macro-contract-note`
3. `reference/cutelyaware-magiccube4d-puzzle-description-reference-page-stack`
   - `SurfaceType`: `legacy-4d-puzzle-description-reference`
   - `IncorporationChannel`: `puzzle-description-contract`
   - `TargetAssetFamily`: `puzzle-description-note`
4. `reference/cutelyaware-magiccube4d-interaction-reference-page-stack`
   - `SurfaceType`: `legacy-4d-interaction-reference`
   - `IncorporationChannel`: `interaction-contract`
   - `TargetAssetFamily`: `interaction-contract-note`
5. `reference/cutelyaware-magiccube4d-view-reference-page-stack`
   - `SurfaceType`: `legacy-4d-view-reference`
   - `IncorporationChannel`: `view-controller-reference`
   - `TargetAssetFamily`: `view-controller-note`
6. `reference/cutelyaware-magiccube4d-attribution-reference-page-boundary`
   - `SurfaceType`: `legacy-4d-attribution-reference`
   - `IncorporationChannel`: `attribution-boundary`
   - `TargetAssetFamily`: `compliance-boundary-note`

Important adjacent fact:

- all six targets preserve the explicit visible-attribution, upstream-link,
  notice-retention, and `MyMath` provenance boundary already enforced by the
  landed lane

## Slice-local verdict

| Slice | Primary authority | Secondary value kept | Result |
|---|---|---|---|
| First-party legacy `4D` interaction, history, macro, topology, and provenance implementation | first-party current code plus landed `Phase 4R-B` packet | retained `cutelyaware/magiccube4d` reference targets stay subordinate provenance-grounding surfaces | unchanged live implementation owner |
| Rewritten history, macro, puzzle-description, interaction, and view-controller grounding | `cutelyaware/magiccube4d` retained boundary-sensitive lane | factual legacy `4D` history, macro, topology, and interaction semantics are preserved while prose remains first-party | unchanged retained reference-grounding surface beneath first-party contracts |
| Attribution-request and `MyMath` provenance boundary grounding | `cutelyaware/magiccube4d` retained boundary-sensitive lane | the visible-attribution, upstream-link, notice-retention, and `MyMath` caveat 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 pages or donor Swing shell UI.

The checked targets explicitly require:

- preserving factual history, macro, topology, interaction, view-controller,
  and attribution semantics
- rewriting donor wording, donor applet or Swing framing, and any broader
  legacy host-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-B` first-party legacy `4D` lane
- the `Hyperspeedcube` runtime anchor
- the later `MagicTile` topology and transform-aware macro widening
- any silent erosion of attribution or `MyMath` provenance duties

## Current exact grounded role

`cutelyaware/magiccube4d` currently grounds six live rewritten first-party
contract/reference targets for `Legacy 4D Interaction and History`:

- history, marks, macro brackets, undo or redo, and save-restore semantics
- reference-grip macro remapping, reversal, and playback semantics
- generic polytope slicing and puzzle-description topology semantics
- `4D` rotation, picking, highlight, slice-mask, and queued-animation semantics
- view-controller composition, callbacks, and motion-aware highlight refresh
- visible attribution, upstream-link, notice-retention, and `MyMath`
  provenance boundary

These targets preserve bounded legacy `4D` 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 `cutelyaware/magiccube4d` reference-incorporation side is now
explicit:

- `6` rewritten first-party contract/reference targets
- all `6` remain inside the landed `Phase 4R-B` legacy `4D` lane
- the visible-attribution, upstream-link, notice, and `MyMath` provenance
  boundary stays explicit

This closes the `cutelyaware/magiccube4d` reference side without reopening
product code.
