# HyperTwist RiftSketch Immersive Live Coding Discard Confirmation Reconciliation - 2026-05-27

## Status

This document is the source-backed discard-confirmation note for
`brianpeiris/RiftSketch` inside the HyperTwist `0R-E` non-live queue.

It answers one narrow question:

- does the current `RiftSketch` source justify any retained HyperTwist owner,
  donor, benchmark, or comparison lane beyond historical reference

Result:

- no retained HyperTwist owner or donor lane survives
- the earlier `0R-E` discard call remains correct
- keep it only as permissive historical comparison context for immersive
  live-coding patterns
- no product-code reopening or new implementation route is required

## Source basis

- `C:\HyperTwist\docs\HYPERTWIST_PHASE_0R_PACKET_0R_E_EVALUATION_2026-05-13.md`
- `C:\HyperTwist\docs\REPO_LICENSE_TRACKING.md`
- `C:\HyperTwist\docs\HYPERTWIST_REPO_STATE_BOARD_2026-05-11.md`
- `C:\HyperTwist\docs\HYPERTWIST_PHASE_1R_RETAINED_SET_CONTRACT_AND_HANDOFF_2026-05-13.md`
- `C:\HyperTwist\docs\HYPERTWIST_REPO_EVALUATION_RESET_AND_IMPLEMENTATION_SCHEDULE_2026-05-11.md`
- `C:\Workspaces\HyperTwist\repos.manifest.json`
- `C:\Workspaces\HyperTwist\mirrors\permissive\brianpeiris\RiftSketch\README.md`
- `C:\Workspaces\HyperTwist\mirrors\permissive\brianpeiris\RiftSketch\js\Sketch.js`
- `C:\Workspaces\HyperTwist\mirrors\permissive\brianpeiris\RiftSketch\js\SketchController.js`
- `C:\Workspaces\HyperTwist\mirrors\permissive\brianpeiris\RiftSketch\js\RiftSandbox.js`
- `C:\Workspaces\HyperTwist\mirrors\permissive\brianpeiris\RiftSketch\js\File.js`

## Why discard remains correct

The source is real and coherent, but its center of gravity is still off-domain
for HyperTwist:

- `README.md` explicitly describes a web-based live-coding environment for
  virtual reality rather than a cubing/training/runtime owner
- `SketchController.js` is centered on local sketch persistence, DOM text
  areas, dynamic `new Function(...)` sketch execution, and a live sketch loop
- `RiftSandbox.js` is centered on `Three.js` scene setup, `WebXR` session
  entry, world-space text areas, a monitor surface, and general immersive scene
  interception
- `File.js` and the sample `Cube.js` flow support editor-side sketch behavior,
  not a retained HyperTwist product lane

Those are interesting interaction ideas, but they do not beat HyperTwist's
current retained owners for the things that matter in scope:

- `pmndrs/xr` already covers retained browser/XR session and input grounding
- `pmndrs/uikit`, `react-three-fiber`, `three.js`, `drei`,
  `postprocessing`, and `zustand` already cover the retained browser-spatial
  renderer, UI, helper, effect, and state stack
- `screenpipe/screenpipe`, `PostHog/posthog`, and `remotion-dev/remotion`
  already cover retained capture/history, instrumentation/session-control, and
  export/explainer reference value

So `RiftSketch` has no surviving unique HyperTwist slice after the later canon
was sharpened.

## Operational result

Keep `RiftSketch` as:

- historical reference only
- permissive custody only
- inactive for HyperTwist implementation planning

Do not keep `RiftSketch` as:

- an active retained benchmark
- a future donor or merge row
- an XR runtime next step
- a training or perception donor
- a clean-room or implementation candidate

## Propagation answer

The current board, tracker, handoff, and manifest discard posture remains
correct.

This note exists only to close the stale source-pack donor wording and make the
row's discard state explicit and source-backed, so the row no longer depends on
packet-era discard prose alone.
