# HyperTwist Phase 1R Retained-Set Contract And Handoff

Created on `2026-05-13`

## Status

`Phase 1R` is now `closed`.

This document is the canonical `retained-set contract and handoff authority` that follows `Phase 0R`.

It does not redo source reading.

That work already lives in:

- [HYPERTWIST_PHASE_0R_PACKET_0R_A_EVALUATION_2026-05-12.md](C:/HyperTwist/docs/HYPERTWIST_PHASE_0R_PACKET_0R_A_EVALUATION_2026-05-12.md:1)
- [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)
- [HYPERTWIST_PHASE_0R_PACKET_0R_C_EVALUATION_2026-05-12.md](C:/HyperTwist/docs/HYPERTWIST_PHASE_0R_PACKET_0R_C_EVALUATION_2026-05-12.md:1)
- [HYPERTWIST_PHASE_0R_PACKET_0R_D_EVALUATION_2026-05-13.md](C:/HyperTwist/docs/HYPERTWIST_PHASE_0R_PACKET_0R_D_EVALUATION_2026-05-13.md:1)
- [HYPERTWIST_PHASE_0R_PACKET_0R_E_EVALUATION_2026-05-13.md](C:/HyperTwist/docs/HYPERTWIST_PHASE_0R_PACKET_0R_E_EVALUATION_2026-05-13.md:1)
- [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)

This document answers the next question instead:

- which rows are still active
- which class each row belongs to
- which phase may touch that row next
- which documents must be read before that row is widened
- which rows are out of the active implementation set entirely

## 2026-05-14 state-separation doctrine

This document starts after the intake and source-evaluation stages.

That means a row appearing here is not merely:

- bookmarked
- queued
- source-read

It already passed into retained-set discussion.

But this document still must not collapse:

- retained
- product-fit
- implementation-authorized
- implemented

Retained-set rule:

- a retained row here survived evaluation in some posture
- that does not automatically mean the row is a preferred donor
- that does not automatically mean maximum realization is required
- that does not automatically mean the row is currently implementation-authorized
- that does not automatically mean the row is already implemented

Use:

- [HYPERTWIST_REPO_INTAKE_RETENTION_AND_PRODUCT_FIT_DOCTRINE_2026-05-14.md](C:/HyperTwist/docs/HYPERTWIST_REPO_INTAKE_RETENTION_AND_PRODUCT_FIT_DOCTRINE_2026-05-14.md:1)

for the canonical definitions and anti-conflation rules.

## Purpose

`Phase 0R` closed the source-evaluation backlog.

`Phase 1R` closes the handoff gap that remained after those packet decisions.

That means:

- no future instance should infer implementation routing from stale pre-`0R` donor language
- no future instance should reopen `Phase 0R` because the packet results were not surfaced clearly enough
- no future instance should confuse:
  - `already live`
  - `active retained implementation candidate`
  - `benchmark/oracle only`
  - `clean-room only`
  - `discarded`

## Authority boundary

Use the documents in this order:

1. this document for retained-set class, phase entry, and handoff routing
2. [HYPERTWIST_REPO_STATE_BOARD_2026-05-11.md](C:/HyperTwist/docs/HYPERTWIST_REPO_STATE_BOARD_2026-05-11.md:1) for row-by-row readable state
3. the relevant `0R-*` packet for source-value extraction and exclusion rationale
4. [HYPERTWIST_MODEL_A_MAX_VALUE_EXTRACTION_MODUS_OPERANDI_2026-05-13.md](C:/HyperTwist/docs/HYPERTWIST_MODEL_A_MAX_VALUE_EXTRACTION_MODUS_OPERANDI_2026-05-13.md:1) for the canonical interpretation rule that keeps future `Model A` work rich inside retained lanes
5. [REPO_LICENSE_TRACKING.md](C:/HyperTwist/docs/REPO_LICENSE_TRACKING.md:1) for repo-row legal, attribution, notice, and provenance obligations
6. [MODEL_B_SOURCE_ACCESS_BOUNDARY.md](C:/HyperTwist/docs/MODEL_B_SOURCE_ACCESS_BOUNDARY.md:1) when a row is clean-room-sensitive or benchmark-only

Document responsibilities are now strict:

- `0R` packet docs own source-value extraction and non-promotion rationale
- [HYPERTWIST_MODEL_A_MAX_VALUE_EXTRACTION_MODUS_OPERANDI_2026-05-13.md](C:/HyperTwist/docs/HYPERTWIST_MODEL_A_MAX_VALUE_EXTRACTION_MODUS_OPERANDI_2026-05-13.md:1) owns the anti-over-narrowing interpretation rule for future `Model A` work
- `REPO_LICENSE_TRACKING.md` owns repo-row licensing and attribution detail
- this document owns retained-set routing and phase entry
- the state board owns the readable row-by-row companion view

## Current retained-set contract

Current post-`Phase 1R` truth:

- curated HyperTwist shallow-eval set: `71`
- currently verified live in checked Unreal surfaces: `20`
- rows with source-backed authority now visible in canonical docs: `71`
- retained rows total: `68`
- discarded from the active retained set: `3`

Retained split:

- landed/live preserve lanes: `20`
- non-live active implementation-board rows: `39`
- non-live benchmark, oracle, or clean-room-later rows outside the active implementation board: `9`

The `39` non-live active implementation-board rows break down as:

- straight permissive implementation candidates: `35`
- boundary-sensitive adapter or sidecar candidates: `0`
- restrictive clean-room-only candidates: `4`

## Contract classes

| Class | Count | Earliest next phase | Meaning |
| --- | --- | --- | --- |
| `landed_permissive_preserve` | `13` | ordinary first-party enhancement only | Already live. Preserve notices and attribution. Do not treat as speculative donor backlog. |
| `landed_boundary_sensitive_preserve` | `6` | ordinary first-party enhancement only with explicit notice discipline | Already live. Preserve the explicit notice, attribution, subtree, package-split, and adapter/provenance boundaries and do not turn them into silent donor-shell carryover. |
| `landed_clean_room_preserve` | `1` | ordinary first-party enhancement only | Already live. Preserve the clean-room chain and work from first-party outputs, not the restrictive mirror. |
| `phase3r_permissive_candidate` | `35` | `Phase 3R` | Retained for direct permissive implementation or bounded first-party adaptation. No clean-room lane is needed. |
| `phase4r_boundary_candidate` | `0` | closed | No retained non-live boundary-sensitive rows remain after `Phase 4R-F`. |
| `phase5r_clean_room_candidate` | `4` | `Phase 5R` | Retained only through refreshed Model A / Model B clean-room work. |
| `benchmark_oracle_only` | `9` | outside the active implementation board | Retained only for validation, parity, oracle behavior, or a later explicitly reopened clean-room-later lane. |
| `discarded_active_set` | `3` | none | Excluded from the retained implementation board. Do not schedule new work from these rows. |

## Core doctrine

- Retained rows default to `full bounded realization of their retained value`, not token helper reuse.
- Bookmark presence or queue position never grants a row ownership weight or implementation momentum by itself.
- `Not foundation owner` does not mean `take one helper and forget the rest`.
- For boundary-sensitive and clean-room-sensitive rows, `do not promote` and similar packet wording is a boundary filter, not a cap on later `Model A` extraction depth.
- If a future `Model A` instance finds that a retained row's positive handoff is too thin, the right move is to strengthen the packet or scrubbed handoff while preserving the existing guardrails.
- Benchmark and oracle rows are not implementation-ready just because they remain documented.
- Discarded rows are not soft-retained. They are out of the active set unless new evidence reopens them explicitly.
- `Permissive` does not automatically mean `high priority`.
- `MIT` or `Apache-2.0` status never outranks stronger retained anchors, domain fit, or already-set ownership boundaries.
- donor strength and legal posture are separate axes.
- a restrictive or boundary-sensitive row may still be the stronger technical owner for its bounded lane.
- if such a row wins technically, preserve that owner verdict and then route it through clean-room, sidecar, adapter, allowlist, or other required boundary discipline.
- easier route never decides the ownership comparison by itself.
- implementation truth is exception-based: assume a row is not implemented unless explicit landed packet authority or the live-lane audit says otherwise.

## Landed preserve lanes

These twenty rows are the only currently verified live rows in checked Unreal surfaces.

### Landed permissive preserve

- `Aarav2709/KubeTimr` — `MIT`
- `apache/echarts` — `Apache-2.0`
- `abunickabhi/5style-Trainer` — `MIT`
- `google/model-viewer` — `Apache-2.0`
- `Hypercubers/hypercubing.xyz` — `MIT`
- `Lykos/cube_trainer` — `MIT`
- `met4citizen/TalkingHead` — `MIT`
- `mrdoob/three.js` — `MIT`
- `newyork-anthonyng/rubiks-cross-trainer` — `MIT`
- `pmndrs/react-three-fiber` — `MIT`
- `pmndrs/xr` — `MIT`
- `tao-yu/Alg-Trainer` — `MIT`

Contract:

- preserve as landed first-party lanes
- preserve required notices and attribution
- read [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) before widening any of these lanes
- treat future work here as normal first-party enhancement work rather than retained-donor backlog work
- `2026-05-27` trainer hierarchy clarification: `tao-yu/Alg-Trainer` keeps the
  landed broad algorithm-training shell and case-corpus foundation slice,
  `Lykos/cube_trainer` keeps the landed persisted coaching and
  weighted-sampling slice, and current first-party code owns the practical
  training-session, review-plan, queue, follow-up, and coaching union above
  both
- `2026-05-27` trainer micro-drill clarification:
  `newyork-anthonyng/rubiks-cross-trainer` keeps only the landed CFOP cross
  scramble-ladder micro-drill slice, `abunickabhi/5style-Trainer` keeps only
  the landed advanced `5-style` / BLD micro-drill slice, and neither row
  reopens the broader first-party training/coaching runtime or the landed
  `Alg-Trainer` / `cube_trainer` owner split
- `2026-05-27` custody correction: `poliva/cubedex` is no longer to be
  treated as a landed permissive preserve row. Preserve the existing
  first-party outputs, but route any future donor-backed work from restrictive
  custody only and do not treat the mirror as a normal `MIT` donor surface.
- `2026-05-27` hierarchy clarification: `poliva/cubedex` is also no longer a
  default future clean-room queue row. Treat it only as restrictive comparison
  context for a narrower smartcube-aware practice-shell, review/SRS UX,
  recognition-versus-execution timing presentation, and local stats/history
  slice beneath the current first-party training, `KubeTimr`, `CubeDesk`,
  `tao-yu/Alg-Trainer`, and `Lykos/cube_trainer` owners.

### Landed boundary-sensitive preserve

- `cubing/cubing.js` - `MPL-2.0 OR GPL-3.0-or-later`
- `cutelyaware/magiccube4d` - `custom permissive attribution-request license`
- `google/model-viewer/packages/shared-assets` - `Apache-2.0 container; mixed per-asset terms`
- `PostHog/posthog` - `MIT` outside `ee/`; enterprise license inside `ee/`
- `screenpipe/screenpipe` - `MIT OR Apache-2.0` core; enterprise license inside `ee/`
- `remotion-dev/remotion` - `custom two-tier commercial license`; `@remotion/studio` is `MIT` but player/renderer/media-parser remain under checked Remotion terms

Contract:

- preserve as the landed first-party boundary-sensitive classic-cubing adapter lane
- preserve as the landed first-party attributed legacy `4D` interaction, history, macro, topology-reference, and provenance-boundary lane beneath the `Hyperspeedcube` anchor
- preserve as the landed first-party shared-assets allowlist, provenance-boundary, and fixture-refresh lane beneath `google/model-viewer`
- preserve as the landed first-party control-plane telemetry, replay-diagnostic, scheduled-change, early-access, and explicit root-`MIT`-core-versus-`ee/` compliance lane
- preserve as the landed first-party capture/history/replay, deterministic-permission, persistence, vault-lifecycle, and explicit permissive-core-versus-`ee/` compliance lane
- preserve as the landed first-party media-export, embedded playback, parser, explainer-studio, and explicit package-split commercial-compliance lane
- preserve the explicit `MPL` notice and publication-duty boundary
- preserve the explicit attribution, upstream-link, and provenance boundary for `cutelyaware/magiccube4d`
- preserve the explicit per-asset allowlist, review-only, and local-only boundary for `google/model-viewer/packages/shared-assets`
- preserve the explicit `ee/` exclusion and mixed-license subtree boundary for `PostHog/posthog`
- preserve the explicit `ee/` exclusion and mixed-license subtree boundary for `screenpipe/screenpipe`
- preserve the explicit company-license, package-split, and non-shell boundary for `remotion-dev/remotion`
- read [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), then [HYPERTWIST_PHASE_4R_PACKET_4R_A_CUBING_JS_ADAPTER_IMPLEMENTATION_2026-05-13.md](C:/HyperTwist/docs/HYPERTWIST_PHASE_4R_PACKET_4R_A_CUBING_JS_ADAPTER_IMPLEMENTATION_2026-05-13.md:1), [HYPERTWIST_PHASE_4R_PACKET_4R_B_MAGICCUBE4D_ADAPTER_IMPLEMENTATION_2026-05-13.md](C:/HyperTwist/docs/HYPERTWIST_PHASE_4R_PACKET_4R_B_MAGICCUBE4D_ADAPTER_IMPLEMENTATION_2026-05-13.md:1), [HYPERTWIST_PHASE_4R_PACKET_4R_C_SHARED_ASSETS_ALLOWLIST_IMPLEMENTATION_2026-05-13.md](C:/HyperTwist/docs/HYPERTWIST_PHASE_4R_PACKET_4R_C_SHARED_ASSETS_ALLOWLIST_IMPLEMENTATION_2026-05-13.md:1), [HYPERTWIST_PHASE_4R_PACKET_4R_D_POSTHOG_CONTROL_PLANE_IMPLEMENTATION_2026-05-13.md](C:/HyperTwist/docs/HYPERTWIST_PHASE_4R_PACKET_4R_D_POSTHOG_CONTROL_PLANE_IMPLEMENTATION_2026-05-13.md:1), [HYPERTWIST_PHASE_4R_PACKET_4R_E_SCREENPIPE_CAPTURE_HISTORY_IMPLEMENTATION_2026-05-13.md](C:/HyperTwist/docs/HYPERTWIST_PHASE_4R_PACKET_4R_E_SCREENPIPE_CAPTURE_HISTORY_IMPLEMENTATION_2026-05-13.md:1), or [HYPERTWIST_PHASE_4R_PACKET_4R_F_REMOTION_MEDIA_EXPORT_IMPLEMENTATION_2026-05-13.md](C:/HyperTwist/docs/HYPERTWIST_PHASE_4R_PACKET_4R_F_REMOTION_MEDIA_EXPORT_IMPLEMENTATION_2026-05-13.md:1) as appropriate, then [HYPERTWIST_MODEL_A_MAX_VALUE_EXTRACTION_MODUS_OPERANDI_2026-05-13.md](C:/HyperTwist/docs/HYPERTWIST_MODEL_A_MAX_VALUE_EXTRACTION_MODUS_OPERANDI_2026-05-13.md:1), before widening these lanes
- do not treat any of these mirrors as silent private-fork or donor-shell surfaces

### Landed restrictive clean-room preserve

- `onionhoney/roux-trainers` — `GPL-3.0`

Contract:

- preserve as the only currently verified restrictive lane that was properly clean-roomed and then implemented
- keep the Model A / Model B lineage explicit
- read [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) and [HYPERTWIST_MODEL_A_MAX_VALUE_EXTRACTION_MODUS_OPERANDI_2026-05-13.md](C:/HyperTwist/docs/HYPERTWIST_MODEL_A_MAX_VALUE_EXTRACTION_MODUS_OPERANDI_2026-05-13.md:1) before widening this lane
- never treat the donor mirror itself as implementation-ready source
- `2026-05-27` Roux hierarchy clarification: this row keeps only the landed
  bounded method-stage, blockbuilding, and generated stage-trainer family
  already materialized in first-party outputs; it does not reopen the broader
  first-party training/coaching runtime and it does not relax restrictive
  governance for later rows

## Active implementation-board rows

These rows remain active for future widening, but only through their assigned classes.

### `0R-A` retained core set -> `Phase 2R-A` split routing

- `HactarCE/Hyperspeedcube` — hyper runtime anchor -> `Phase 6R`
- `kkoomen/qbr` — recognition anchor -> `Phase 6R`
- `vivaansinghvi07/rubix-cube-solver` — recognition companion -> `Phase 6R`
- `Aarav2709/KubeTimr` — landed timer subsystem preserve lane through `Phase 3R-A`
- `roice3/MagicTile` — primary non-Euclidean/topology donor -> `Phase 6R`
- `roice3/Magic120Cell` — later specialized `4D` donor
- `roice3/MagicCube5D` — later specialized `5D` donor

Contract:

- read `Packet 0R-A` before any widening
- read [HYPERTWIST_PHASE_2R_PACKET_2R_A_OWNERSHIP_AND_ACCEPTANCE_CONTRACT_2026-05-13.md](C:/HyperTwist/docs/HYPERTWIST_PHASE_2R_PACKET_2R_A_OWNERSHIP_AND_ACCEPTANCE_CONTRACT_2026-05-13.md:1) before implementing the five core rows above
- read [HYPERTWIST_PHASE_3R_PACKET_3R_A_KUBETIMR_IMPLEMENTATION_2026-05-13.md](C:/HyperTwist/docs/HYPERTWIST_PHASE_3R_PACKET_3R_A_KUBETIMR_IMPLEMENTATION_2026-05-13.md:1) plus the live-lane audit before widening the already-landed `Aarav2709/KubeTimr` lane further
- route remaining direct implementation only through `Phase 6R` for `HactarCE/Hyperspeedcube`, `kkoomen/qbr`, `vivaansinghvi07/rubix-cube-solver`, and `roice3/MagicTile`
- do not reopen `Phase 0R` debate on these rows unless new source evidence appears

### `0R-B` retained permissive support set -> `Phase 2R-B` / `2R-C` split routing

`Phase 2R-B` is now closed for the primary permissive support-plane rows.

`apache/echarts` has now already completed `Phase 3R-C` and moved into the landed preserve set.

`google/model-viewer` has now also completed `Phase 3R-D` and moved into the landed preserve set.

`met4citizen/TalkingHead` has now also completed `Phase 3R-E` and moved into the landed preserve set.

`mrdoob/three.js`, `pmndrs/react-three-fiber`, and `pmndrs/xr` have now also completed `Phase 3R-F` and moved into the landed preserve set.

The remaining non-live support-plane rows covered by `2R-B` are:

- `ecomfe/zrender` -> subordinate beneath landed `Phase 3R-C`
- `ecomfe/echarts-gl` -> subordinate beneath landed `Phase 3R-C`
- `google/model-viewer/packages/model-viewer-effects` -> subordinate beneath landed `Phase 3R-D`
- `google/model-viewer/packages/modelviewer.dev` -> subordinate beneath landed `Phase 3R-D`
- `google/model-viewer/packages/render-fidelity-tools` -> subordinate beneath landed `Phase 3R-D`
- `google/model-viewer/packages/space-opera` -> subordinate beneath landed `Phase 3R-D`
- `KhronosGroup/glTF-Sample-Renderer` -> subordinate beneath landed `Phase 3R-D`
- `KhronosGroup/glTF-Sample-Viewer` -> subordinate beneath landed `Phase 3R-D`
- `@react-spring/animated`
- `@react-spring/core`
- `@react-spring/parallax`
- `@react-spring/rafz`
- `@react-spring/shared`
- `@react-spring/types`
- `pmndrs/drei`
- `pmndrs/leva`
- `pmndrs/maath`
- `pmndrs/postprocessing`
- `pmndrs/react-postprocessing`
- `pmndrs/react-spring`
- `pmndrs/three-stdlib`
- `pmndrs/uikit`
- `pmndrs/use-gesture`
- `pmndrs/zustand` -> `Phase 3R-F`

Residual `0R-B` rows are still retained but not closed by `2R-B`:

- `cahidenes/rubiks-cube-solver`
- `tentone/rubix-solver`
- `NuiLab/code-vr`
- `pissang/claygl`
- `pissang/clay-viewer`

`Phase 2R-C` is now also closed for those residual rows:

- `cahidenes/rubiks-cube-solver` -> `Phase 6R-E`
- `tentone/rubix-solver` -> `Phase 6R-E`
- `NuiLab/code-vr` -> `Phase 6R-F`
- `pissang/claygl` -> `Phase 3R-G`
- `pissang/clay-viewer` -> `Phase 3R-G`

Contract:

- read `Packet 0R-B` before any widening
- read [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) before implementing any row covered by `2R-B`
- read [HYPERTWIST_PHASE_2R_PACKET_2R_C_OWNERSHIP_AND_ACCEPTANCE_CONTRACT_2026-05-13.md](C:/HyperTwist/docs/HYPERTWIST_PHASE_2R_PACKET_2R_C_OWNERSHIP_AND_ACCEPTANCE_CONTRACT_2026-05-13.md:1) before implementing any row covered by `2R-C`
- read [HYPERTWIST_PHASE_3R_PACKET_3R_B_HYPERCUBING_XYZ_IMPLEMENTATION_2026-05-13.md](C:/HyperTwist/docs/HYPERTWIST_PHASE_3R_PACKET_3R_B_HYPERCUBING_XYZ_IMPLEMENTATION_2026-05-13.md:1) plus the live-lane audit before widening the already-landed `Hypercubers/hypercubing.xyz` lane further
- read [HYPERTWIST_PHASE_3R_PACKET_3R_C_ECHARTS_IMPLEMENTATION_2026-05-13.md](C:/HyperTwist/docs/HYPERTWIST_PHASE_3R_PACKET_3R_C_ECHARTS_IMPLEMENTATION_2026-05-13.md:1) plus the live-lane audit before widening the already-landed `apache/echarts` lane further
- read [HYPERTWIST_PHASE_3R_PACKET_3R_D_MODEL_VIEWER_IMPLEMENTATION_2026-05-13.md](C:/HyperTwist/docs/HYPERTWIST_PHASE_3R_PACKET_3R_D_MODEL_VIEWER_IMPLEMENTATION_2026-05-13.md:1) plus the live-lane audit before widening the already-landed `google/model-viewer` lane further
- read [HYPERTWIST_PHASE_3R_PACKET_3R_F_BROWSER_SPATIAL_SUPPORT_IMPLEMENTATION_2026-05-13.md](C:/HyperTwist/docs/HYPERTWIST_PHASE_3R_PACKET_3R_F_BROWSER_SPATIAL_SUPPORT_IMPLEMENTATION_2026-05-13.md:1) plus the live-lane audit before widening the already-landed browser spatial owner trio further
- treat `2R-B` rows as support-plane owners, subordinate packages, or helper/dependency lanes according to the packet, not as equal foundation owners
- treat `2R-C` rows as comparison adjuncts, symbolic-to-spatial experiment donors, or alternative browser comparison lanes rather than equal support-plane owners

### Remaining `0R-C` boundary-sensitive set -> `Phase 4R`

`Phase 4R` is now closed for the retained boundary-sensitive set.

There are no remaining non-live boundary-sensitive implementation-board rows.

Contract:

- read `Packet 0R-C` plus the landed `Phase 4R-A` through `Phase 4R-F` packets before widening any of the six boundary-sensitive preserve lanes further
- read [HYPERTWIST_MODEL_A_MAX_VALUE_EXTRACTION_MODUS_OPERANDI_2026-05-13.md](C:/HyperTwist/docs/HYPERTWIST_MODEL_A_MAX_VALUE_EXTRACTION_MODUS_OPERANDI_2026-05-13.md:1) so boundary-sensitive `non-promotion` language is not misread as a shallow-extraction rule
- do not treat any of the landed boundary-sensitive mirrors as broad donor shells
- keep the optional `Phase 3R-G` browser comparison lane deferred unless the landed primary browser spatial stack exposes a real gap

### `0R-D` clean-room-only set -> `Phase 5R`

- `cubing/alg.js`
- `cubing/twisty.js`
- `HactarCE/2x2x2x2-Scrambler`
- `kash/cubedesk`

Contract:

- read `Packet 0R-D`
- read [HYPERTWIST_MODEL_A_MAX_VALUE_EXTRACTION_MODUS_OPERANDI_2026-05-13.md](C:/HyperTwist/docs/HYPERTWIST_MODEL_A_MAX_VALUE_EXTRACTION_MODUS_OPERANDI_2026-05-13.md:1)
- then read the scrubbed Model A handoff in `C:\Workspaces\HyperTwist\clean-room-specs\`
- implementation may start only in `Phase 5R`
- donor source is not an allowed implementation input

## Retained rows outside the active implementation board

These rows stay retained, but not as active implementation backlog.

### `0R-E` benchmark, oracle, and clean-room-later rows

- `cs0x7f/cstimer` — primary restrictive oracle for competition-grade timer semantics, rolling stats/`DNF` math, session interchange, scramble-registry breadth, and `GAN`/smart-device behavior; reopen only through a dedicated clean-room timer-pattern handoff if a specific gap is proven
- `brownan/Rubiks-Cube-Solver` — primary compact solver oracle and clean-room-later heuristic/search benchmark
- `efrantar/rob-twophase` — secondary solver oracle for metric and performance comparison
- `ShellPuppy/RCube` — large-`N` centers/edges/parity benchmark and later clean-room research input
- `vwcwong/CubeSim` — readable state/history and beginner-solver decomposition benchmark
- `AviKaufman/Rubix-cube-trainer` — primary all-rights-reserved guided-pedagogy benchmark
- `alinen/cube` — no-license planner and task-segmentation benchmark
- `ambisinister/blindsolve` — no-license BLD memo benchmark
- `yakupbilen/drl-rubiks-cube` — MIT learned-heuristic, `ADI` state-generation, and offline solver-experimentation benchmark

Contract:

- read `Packet 0R-E` before using any of these rows
- do not place these rows into ordinary `Phase 3R`, `4R`, or `5R` implementation packets by default
- use them for validation, parity, oracle behavior, or a later explicitly reopened clean-room-later approval

## Discarded rows

These rows are no longer part of the active retained set.

- `aMonteSl/CodeXR` — off-topic XR collaboration value already superseded by stronger retained rows
- `MathewKJ2048/Rubiks-cube-simulator` — inferior duplicate of stronger pedagogy, planner, and history benchmarks
- `brianpeiris/RiftSketch` — immersive live-coding shell is off topic to HyperTwist's retained roadmap

Contract:

- do not schedule implementation work from these rows
- keep them only as historical comparison context if a future operator needs to explain why they were excluded

## Mandatory routing rules

Before touching any non-live retained row:

1. read this `Phase 1R` contract doc
2. read the relevant `0R-*` packet
3. read [HYPERTWIST_MODEL_A_MAX_VALUE_EXTRACTION_MODUS_OPERANDI_2026-05-13.md](C:/HyperTwist/docs/HYPERTWIST_MODEL_A_MAX_VALUE_EXTRACTION_MODUS_OPERANDI_2026-05-13.md:1)
4. read `REPO_LICENSE_TRACKING.md`
5. if the row is clean-room-sensitive or benchmark-only, obey `MODEL_B_SOURCE_ACCESS_BOUNDARY.md`

Do not:

- reopen `Phase 0R` because a packet result was not surfaced clearly enough
- pull benchmark rows into ordinary implementation packets by convenience
- treat discarded rows as low-priority retained rows
- treat `onionhoney/roux-trainers` as proof that other restrictive rows are also implementation-ready

## Phase result

`Phase 1R` is now closed with this result:

- retained-set contract is explicit
- live rows are separated from non-live retained rows
- non-live active implementation-board rows are separated from benchmark-only retained rows
- discarded rows are explicit
- phase entry is explicit:
  - `Phase 3R` for retained straight-permissive widening
  - `Phase 4R` for boundary-sensitive rows
  - `Phase 5R` for clean-room-only rows
  - benchmark/oracle rows remain outside the active implementation board unless later explicitly reopened

## Next move

`Phase 2R` is now closed, `Phase 3R-A` through `Phase 3R-F` are now also
closed for the primary straight-permissive widening path, and `Phase 4R-A`
through `Phase 4R-F` are now closed for the six landed boundary-sensitive live
lanes.

The historical next bounded move after those earlier closures was `Phase 5R-A`:

- preserve the landed `cubing/cubing.js` lane through its live-lane audit and `Phase 4R-A` packet authority
- preserve the landed `cutelyaware/magiccube4d` lane through its live-lane audit and `Phase 4R-B` packet authority
- preserve the landed `google/model-viewer/packages/shared-assets` lane through its live-lane audit and `Phase 4R-C` packet authority
- preserve the landed `PostHog/posthog` lane through its live-lane audit and `Phase 4R-D` packet authority
- preserve the landed `screenpipe/screenpipe` lane through its live-lane audit and `Phase 4R-E` packet authority
- preserve the landed `remotion-dev/remotion` lane through its live-lane audit and `Phase 4R-F` packet authority
- open `cubing/alg.js` as the first refreshed clean-room implementation lane from its scrubbed Model A dossier
- keep the optional `Phase 3R-G` `pissang/claygl` and `pissang/clay-viewer` comparison lane deferred unless the landed primary browser spatial stack exposes a real gap that requires it

Current `2026-05-27` truth is later than that historical handoff:

- later restrictive clean-room implementation also landed for `cubing/alg.js`,
  `cubing/twisty.js`, `HactarCE/2x2x2x2-Scrambler`, and `kash/cubedesk`
- no default restrictive opening remains
- future restrictive work must now start from first-party owner surfaces,
  `REPO_LICENSE_TRACKING.md`, `MODEL_B_SOURCE_ACCESS_BOUNDARY.md`, scrubbed
  Model A handoffs, and later per-lane reconciliation notes
- keep the optional `Phase 3R-G` comparison lane deferred unless the landed
  primary browser spatial stack exposes a real gap that actually justifies it
