diff --git a/docs/HYPERTWIST_PHASE_1R_RETAINED_SET_CONTRACT_AND_HANDOFF_2026-05-13.md b/docs/HYPERTWIST_PHASE_1R_RETAINED_SET_CONTRACT_AND_HANDOFF_2026-05-13.md index 4e427fd..af09814 100644 --- a/docs/HYPERTWIST_PHASE_1R_RETAINED_SET_CONTRACT_AND_HANDOFF_2026-05-13.md +++ b/docs/HYPERTWIST_PHASE_1R_RETAINED_SET_CONTRACT_AND_HANDOFF_2026-05-13.md @@ -423,9 +423,12 @@ Do not: ## 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. +`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 next bounded move after those closures is `Phase 5R-A`: +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 @@ -435,3 +438,14 @@ The next bounded move after those closures is `Phase 5R-A`: - 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 diff --git a/docs/HYPERTWIST_REPO_EVALUATION_RESET_AND_IMPLEMENTATION_SCHEDULE_2026-05-11.md b/docs/HYPERTWIST_REPO_EVALUATION_RESET_AND_IMPLEMENTATION_SCHEDULE_2026-05-11.md index e220d55..68e0d59 100644 --- a/docs/HYPERTWIST_REPO_EVALUATION_RESET_AND_IMPLEMENTATION_SCHEDULE_2026-05-11.md +++ b/docs/HYPERTWIST_REPO_EVALUATION_RESET_AND_IMPLEMENTATION_SCHEDULE_2026-05-11.md @@ -582,22 +582,22 @@ Current curated HyperTwist shallow-eval set: Current verified live implementation state in checked `UnrealHyperTwist` source and materialized training surfaces: -- `19` repos are implemented/live +- `24` repos are implemented/live - `13` of those are permissive `MIT` or `Apache-2.0` lanes -- `5` of those are boundary-sensitive lanes -- `1` of those is a restrictive repo that was properly clean-roomed and then implemented +- `6` of those are boundary-sensitive lanes +- `5` of those are restrictive repos that were properly clean-roomed and then implemented -Current 2026-05-11 repo-row reset counts: +Current repo-row reset counts as of `2026-05-27`: - `implemented_live_permissive`: `13` -- `implemented_live_boundary_sensitive`: `5` -- `implemented_live_clean_room_verified`: `1` +- `implemented_live_boundary_sensitive`: `6` +- `implemented_live_clean_room_verified`: `5` - `selected_not_live_permissive_candidate`: `35` -- `selected_not_live_boundary_sensitive`: `1` -- `selected_not_live_clean_room_candidate`: `4` +- `selected_not_live_boundary_sensitive`: `0` +- `selected_not_live_clean_room_candidate`: `0` - `not_live_reference_or_discard_candidate`: `12` -### The twenty currently implemented/live repos +### The twenty-four currently implemented/live repos Permissive `MIT` or `Apache-2.0` lanes already implemented/live: @@ -615,9 +615,13 @@ Permissive `MIT` or `Apache-2.0` lanes already implemented/live: - `poliva/cubedex` - `newyork-anthonyng/rubiks-cross-trainer` -Restrictive lane already properly clean-roomed and implemented/live: +Restrictive lanes already properly clean-roomed and implemented/live: - `onionhoney/roux-trainers` +- `cubing/alg.js` +- `cubing/twisty.js` +- `HactarCE/2x2x2x2-Scrambler` +- `kash/cubedesk` Boundary-sensitive lanes already implemented/live: @@ -631,7 +635,7 @@ Boundary-sensitive lanes already implemented/live: ### What this means - HyperTwist does **not** currently have dozens of donor repos already implemented in owned Unreal surfaces. -- HyperTwist does **not** currently show live Unreal evidence for `cstimer`, `cubedesk`, `cubing/alg.js`, `cubing/twisty.js`, `Hyperspeedcube`, `qbr`, `MagicTile`, `MagicCube5D`, or `Magic120Cell`. +- HyperTwist does **not** currently show live Unreal evidence for `cstimer`, `Hyperspeedcube`, `qbr`, `MagicTile`, `MagicCube5D`, or `Magic120Cell`. - The previous confusion came from mixing: - docs-state classifications such as `integrate`, `repurpose`, `donor bench`, and `locked strategic donor` - with actual live implementation evidence @@ -664,24 +668,28 @@ Use this only when: - the implementation lane is accepted as clean-room compliant - the resulting first-party output is already landed/live -At the moment, only one HyperTwist repo should be described this way: +At the moment, five HyperTwist repos should be described this way: - `onionhoney/roux-trainers` +- `cubing/alg.js` +- `cubing/twisty.js` +- `HactarCE/2x2x2x2-Scrambler` +- `kash/cubedesk` ## Immediate governance correction HyperTwist should now proceed from the following rule: -- preserve the twenty live lanes -- do not reopen the `onionhoney/roux-trainers` lane as if it were an unresolved accidental donor import -- do not treat the remaining `51` current non-live rows as already implemented +- preserve the twenty-four live lanes +- do not reopen the five landed restrictive clean-room lanes as if they were unresolved accidental donor imports +- do not treat the remaining `47` current non-live rows as already implemented - keep `Phase 0R`, `Phase 1R`, and `Phase 2R` closed as completed packet classes -- continue later-phase widening from the closed packet sequence, with `Phase 5R-A` as the next non-optional move and `Phase 3R-G` deferred unless a real browser comparison gap appears +- continue later-phase widening from the closed packet sequence with no default new `Phase 5R-A` opening; use the landed restrictive per-lane authority for `onionhoney/roux-trainers`, `cubing/alg.js`, `cubing/twisty.js`, `HactarCE/2x2x2x2-Scrambler`, and `kash/cubedesk`, and keep `Phase 3R-G` deferred unless a real browser comparison gap appears In practical terms: -- no, do **not** mass-revert the twenty landed lanes -- no, do **not** pretend the remaining `51` current non-live rows are already implemented +- no, do **not** mass-revert the twenty-four landed lanes +- no, do **not** pretend the remaining `47` current non-live rows are already implemented - yes, preserve the landed `Aarav2709/KubeTimr`, `Hypercubers/hypercubing.xyz`, `apache/echarts`, `google/model-viewer`, `met4citizen/TalkingHead`, `mrdoob/three.js`, `pmndrs/react-three-fiber`, `pmndrs/xr`, `cubing/cubing.js`, `cutelyaware/magiccube4d`, `google/model-viewer/packages/shared-assets`, `PostHog/posthog`, `screenpipe/screenpipe`, and `remotion-dev/remotion` lanes as normal first-party enhancement surfaces within their packet-specific legal boundaries - yes, widen the next retained lane only through its closed packet stack and packet-specific legal boundary @@ -1048,9 +1056,9 @@ Only after that: The clean practical sequence is: -1. preserve the twenty landed lanes +1. preserve the twenty-four landed lanes 2. make the current truth explicit everywhere -3. deep-evaluate the remaining `51` +3. deep-evaluate the remaining `47` 4. discard what should not survive 5. re-schedule what remains by permissive, boundary-sensitive, clean-room, and benchmark lanes 6. resume later-phase widening from that corrected retained set @@ -1073,7 +1081,7 @@ Current status: - `Phase 4R-D` is now also complete - `Phase 4R-E` is now also complete - `Phase 4R-F` is now also complete -- the next bounded move is `Phase 5R-A` for `cubing/alg.js`, with the optional `Phase 3R-G` comparison lane deferred unless the landed primary browser spatial stack exposes a real gap +- there is no remaining default `Phase 5R-A` opening because later restrictive clean-room truth already landed `cubing/alg.js`, `cubing/twisty.js`, `HactarCE/2x2x2x2-Scrambler`, and `kash/cubedesk`; keep the optional `Phase 3R-G` comparison lane deferred unless the landed primary browser spatial stack exposes a real gap ## Companion docs diff --git a/docs/HYPERTWIST_REPO_STATE_BOARD_2026-05-11.md b/docs/HYPERTWIST_REPO_STATE_BOARD_2026-05-11.md index 263021c..c6552c8 100644 --- a/docs/HYPERTWIST_REPO_STATE_BOARD_2026-05-11.md +++ b/docs/HYPERTWIST_REPO_STATE_BOARD_2026-05-11.md @@ -7,16 +7,36 @@ This board is the readable row-by-row companion to the v6.3 CSVs. It is derived ## Canonical summary - Current curated HyperTwist shallow-eval set: `71` repos -- Currently verified live in checked `UnrealHyperTwist` surfaces: `20` repos +- Currently verified live in checked `UnrealHyperTwist` surfaces: `24` repos - Live permissive lanes: `13` - Live boundary-sensitive lanes: `6` -- Live restrictive clean-room lanes: `1` +- Live restrictive clean-room lanes: `5` - Remaining rows requiring `Phase 0R` deep repo evaluation: `0` ## 2026-05-13 packet and contract overlay The baseline live-state counts above now include the landed `Phase 3R-C` analytics lane, the landed `Phase 3R-D` browser viewer lane, the landed `Phase 3R-E` embodied companion lane, the landed `Phase 3R-F` browser spatial owner stack, the landed `Phase 4R-A` classic-cubing boundary-sensitive adapter lane, the landed `Phase 4R-B` attributed legacy `4D` boundary-sensitive lane, the landed `Phase 4R-C` shared-assets allowlist lane, the landed `Phase 4R-D` PostHog control-plane lane, the landed `Phase 4R-E` screenpipe capture-history lane, and the landed `Phase 4R-F` Remotion media-export lane, while `Phase 0R` and `Phase 1R` remain closed. +## 2026-05-27 restrictive clean-room status update + +Later current-live truth is broader than the original `Phase 4R-F` stopping +point above. + +The restrictive clean-room sequence is no longer a future four-row queue headed +by `Phase 5R-A`. + +Later current-live restrictive clean-room lanes now also include: + +- `cubing/alg.js` +- `cubing/twisty.js` +- `HactarCE/2x2x2x2-Scrambler` +- `kash/cubedesk` + +Use +[HYPERTWIST_RESTRICTIVE_CLEAN_ROOM_LIVE_STATE_RECONCILIATION_2026-05-27.md](C:/HyperTwist/docs/HYPERTWIST_RESTRICTIVE_CLEAN_ROOM_LIVE_STATE_RECONCILIATION_2026-05-27.md:1) +for the current restrictive-lane preserve posture and for the correction that +the original `Phase 5R-A next` wording is now historical only. + Read together with: - [HYPERTWIST_PHASE_1R_RETAINED_SET_CONTRACT_AND_HANDOFF_2026-05-13.md](C:/HyperTwist/docs/HYPERTWIST_PHASE_1R_RETAINED_SET_CONTRACT_AND_HANDOFF_2026-05-13.md:1) @@ -78,7 +98,11 @@ Important authority correction: - future implementation of the `0R-B` permissive set should start from `Packet 0R-B`, then the relevant closed `2R-B` or `2R-C` ownership packet, not from this board alone - there are no remaining non-live boundary-sensitive repos after the closed `Phase 4R-F` packet; future work on those lanes starts from the live-lane audit and the repo-specific landed `Phase 4R-*` packet - future widening of the landed `cubing/cubing.js` lane should start from the live-lane audit, then `Phase 4R-A`, then `REPO_LICENSE_TRACKING.md` -- future implementation of those four restrictive repos should start from `Packet 0R-D`, then `REPO_LICENSE_TRACKING.md`, then the repo-specific scrubbed Model A handoff +- future preservation or later widening of the five landed restrictive + clean-room lanes should start from `REPO_LICENSE_TRACKING.md`, + `MODEL_B_SOURCE_ACCESS_BOUNDARY.md`, the repo-specific scrubbed Model A + handoff, later per-lane reconciliation notes, and first-party owner + surfaces, not from this board alone - future implementation or benchmarking decisions for the twelve `0R-E` rows should start from `Packet 0R-E`, not from this board alone - future routing by phase entry should start from `Phase 1R`, not from this board alone - this board remains the readable row-state companion, not the place for full source-value extraction @@ -89,7 +113,7 @@ Packet overlay result: - all `6` boundary-sensitive rows have now been packet-evaluated - all `4` restrictive clean-room rows have now been packet-evaluated - all `12` reference, benchmark, reserve, and discard rows have now been packet-evaluated -- all `20` live rows now also have symmetric source-backed preservation authority +- all `20` originally live rows now also have symmetric source-backed preservation authority - `Phase 2R-A` is now closed for the five core retained permissive rows - `Phase 2R-B` is now closed for the retained permissive support-plane owners, subordinate packages, and helper/dependency lanes in scope - `Phase 2R-C` is now closed for the final retained permissive `0R-B` residual rows @@ -119,7 +143,7 @@ Packet overlay result: - the `0R-E` result split is: - `9` retained benchmark, oracle, or clean-room-later rows - `3` discarded active-set rows -- the next bounded move is `Phase 5R-A` +- the original queued next move after `Phase 4R-F` was `Phase 5R-A`, but later current-live restrictive clean-room truth closed `cubing/alg.js`, `cubing/twisty.js`, `HactarCE/2x2x2x2-Scrambler`, and `kash/cubedesk`, so no default restrictive opening remains ## 2026-05-14 state-vocabulary and anti-inflation rule @@ -160,10 +184,10 @@ audit when implementation truth matters. - `implemented_live_permissive`: `13` - `implemented_live_boundary_sensitive`: `6` -- `implemented_live_clean_room_verified`: `1` +- `implemented_live_clean_room_verified`: `5` - `selected_not_live_permissive_candidate`: `35` - `selected_not_live_boundary_sensitive`: `0` -- `selected_not_live_clean_room_candidate`: `4` +- `selected_not_live_clean_room_candidate`: `0` - `not_live_reference_or_discard_candidate`: `12` ## How to read this board @@ -216,15 +240,20 @@ Count: `6` | `screenpipe/screenpipe` | `MIT OR Apache-2.0 core; enterprise-restricted ee/` | Donor Bench | `repurpose` | `implemented_live_boundary_sensitive` | `landed_boundary_sensitive_preserve` | `Phase 4R-E` closed. Preserve as the landed first-party capture/history/replay, deterministic-permission, persistence, vault-lifecycle, timeline-review, and explicit permissive-core-versus-`ee/` subtree-compliance lane; start future widening from the live-lane audit, then `Phase 4R-E`, then `REPO_LICENSE_TRACKING.md`; keep the explicit `ee/` exclusion and mixed-license subtree boundary visible. | | `remotion-dev/remotion` | `Custom two-tier commercial license` | Donor Bench | `repurpose` | `implemented_live_boundary_sensitive` | `landed_boundary_sensitive_preserve` | `Phase 4R-F` closed. Preserve as the landed first-party media-export, embedded playback, parser, explainer-studio, and explicit package-split commercial-compliance lane; start future widening from the live-lane audit, then `Phase 4R-F`, then `REPO_LICENSE_TRACKING.md`; keep the explicit company-license and package-split boundary visible. | -## Landed Restrictive Clean-Room Lane +## Landed Restrictive Clean-Room Lanes -This is the only currently verified restrictive repo that was properly clean-roomed and then implemented. +These are the currently verified restrictive repos that were properly +clean-roomed and then implemented. -Count: `1` +Count: `5` | Repo | License | Prior bucket | Prior action | Current live state | Reset lane | Next step | | --- | --- | --- | --- | --- | --- | --- | | `onionhoney/roux-trainers` | `GPL-3.0` | Donor Bench | `repurpose` | `implemented_live_clean_room_verified` | `landed_clean_room_preserve` | Phase 1R closed. Preserve as the landed restrictive clean-room precedent; start future widening from the live-lane audit, then `REPO_LICENSE_TRACKING.md`, then `MODEL_B_SOURCE_ACCESS_BOUNDARY.md`, then scrubbed clean-room specs; never from the restrictive mirror. | +| `cubing/alg.js` | `GPL-3.0-or-later` | Donor Bench | `repurpose` | `implemented_live_clean_room_verified` | `landed_clean_room_preserve` | Later clean-room sequence closed through `Bound 4`. Preserve as the landed first-party algorithm-language owner lane; start future widening from first-party owner surfaces, `REPO_LICENSE_TRACKING.md`, `MODEL_B_SOURCE_ACCESS_BOUNDARY.md`, and the scrubbed Model A handoff; never from the restrictive mirror. | +| `cubing/twisty.js` | `GPL-3.0-or-later` | Donor Bench | `repurpose` | `implemented_live_clean_room_verified` | `landed_clean_room_preserve` | Later clean-room sequence closed through `Bound 4`. Preserve as the landed first-party replay-player, cursor/timeline transport, adapter/bootstrap, and local visualization owner lane; start future widening from first-party owner surfaces, `REPO_LICENSE_TRACKING.md`, `MODEL_B_SOURCE_ACCESS_BOUNDARY.md`, and the scrubbed Model A handoff; never from the restrictive mirror. | +| `HactarCE/2x2x2x2-Scrambler` | `GPL-3.0` | Donor Bench | `repurpose` | `implemented_live_clean_room_verified` | `landed_clean_room_preserve` | Later clean-room sequence closed through `Bound 4`. Preserve as the landed first-party Melinda state legality, random-state generation, move-family application, scramble-packet, and flat debug/teaching owner lane; start future widening from first-party owner surfaces, `REPO_LICENSE_TRACKING.md`, `MODEL_B_SOURCE_ACCESS_BOUNDARY.md`, and the scrubbed Model A handoff; never from the restrictive mirror. | +| `kash/cubedesk` | `GPLv3-or-later in README/LICENSE; package.json says All Rights Reserved` | Locked Strategic Donor | `repurpose` | `implemented_live_clean_room_verified` | `landed_clean_room_preserve` | Later clean-room sequence closed through `Bound 5`. Preserve as the landed first-party trainer-session coupling, session-domain, analytics-panel, integrated smart-device workflow, publication/entitlement, and local social challenge owner lane; start future widening from first-party owner surfaces, `REPO_LICENSE_TRACKING.md`, `MODEL_B_SOURCE_ACCESS_BOUNDARY.md`, and the scrubbed Model A handoff; never from the restrictive mirror. | ## Retained Permissive Candidates @@ -280,16 +309,17 @@ There are no remaining non-live boundary-sensitive implementation-board rows. ## Retained Restrictive Clean-Room Candidates -These rows are retained restrictive lanes that have now cleared `Phase 0R` deep evaluation. `Phase 1R` places them on the active implementation board with earliest re-entry through `Phase 5R`. +These rows were the original retained restrictive lanes that cleared `Phase 0R` +deep evaluation. -Count: `4` +Count: `0` -| Repo | License | Prior bucket | Prior action | Current live state | Reset lane | Next step | -| --- | --- | --- | --- | --- | --- | --- | -| `cubing/alg.js` | `GPL-3.0-or-later` | Donor Bench | `repurpose` | `selected_not_live_clean_room_candidate` | `phase0r_clean_room_eval_then_model_a_model_b` | `Packet 0R-D` closed. Retain as the clean-room-only algorithm-language donor; later implementation must start from the scrubbed Model A dossier rather than donor source. | -| `cubing/twisty.js` | `GPL-3.0-or-later` | Donor Bench | `repurpose` | `selected_not_live_clean_room_candidate` | `phase0r_clean_room_eval_then_model_a_model_b` | `Packet 0R-D` closed. Retain as the clean-room-only embedded viewer/player donor; later implementation must start from the scrubbed Model A dossier rather than donor source. | -| `HactarCE/2x2x2x2-Scrambler` | `GPL-3.0` | Donor Bench | `repurpose` | `selected_not_live_clean_room_candidate` | `phase0r_clean_room_eval_then_model_a_model_b` | `Packet 0R-D` closed. Retain as the clean-room-only Melinda `2x2x2x2` donor; keep the copied-port lineage explicit and implement later only from the scrubbed Model A dossier. | -| `kash/cubedesk` | `GPLv3-or-later in README/LICENSE; package.json says All Rights Reserved` | Locked Strategic Donor | `repurpose` | `selected_not_live_clean_room_candidate` | `phase0r_clean_room_eval_then_model_a_model_b` | `Packet 0R-D` closed. Retain as the clean-room-only timer/trainer/stats/smart-cube product-pattern donor; later work must stay bounded and start from the scrubbed Model A dossier. | +There are no remaining non-live restrictive clean-room implementation-board +rows. + +Future restrictive work starts from the landed per-lane preserve sequence for +the five live rows above, or from a newly justified clean-room opening if a +benchmark, oracle, or retained non-live row later proves a real owner gap. ## Reference, Benchmark, Or Discard Results @@ -314,9 +344,9 @@ Count: `12` ## Implementation rule going forward -- Preserve the twenty landed lanes as current truth. -- Keep `onionhoney/roux-trainers` explicitly marked as the only currently verified restrictive clean-room lane already implemented. +- Preserve the twenty-four landed lanes as current truth. +- Keep `onionhoney/roux-trainers`, `cubing/alg.js`, `cubing/twisty.js`, `HactarCE/2x2x2x2-Scrambler`, and `kash/cubedesk` explicitly marked as the five currently verified restrictive clean-room lanes already implemented. - Keep `cubing/cubing.js`, `cutelyaware/magiccube4d`, `google/model-viewer/packages/shared-assets`, `PostHog/posthog`, `screenpipe/screenpipe`, and `remotion-dev/remotion` explicitly marked as the six currently verified live boundary-sensitive lanes. -- `Phase 0R` is now fully closed for the remaining `51` non-live rows. +- `Phase 0R` is now fully closed for the remaining `47` non-live rows. - `Phase 1R` is now the routing authority for retained-set widening and benchmark exclusion. -- The next bounded move is `Phase 5R-A` for the retained `cubing/alg.js` clean-room implementation lane, while the optional `Phase 3R-G` browser comparison lane remains deferred unless the landed primary browser spatial stack exposes a real gap. +- There is no remaining default `Phase 5R-A` opening. Future restrictive work starts from the landed per-lane preserve sequence or from a newly justified clean-room opening, while the optional `Phase 3R-G` browser comparison lane remains deferred unless the landed primary browser spatial stack exposes a real gap. diff --git a/docs/HYPERTWIST_RESTRICTIVE_CLEAN_ROOM_LIVE_STATE_RECONCILIATION_2026-05-27.md b/docs/HYPERTWIST_RESTRICTIVE_CLEAN_ROOM_LIVE_STATE_RECONCILIATION_2026-05-27.md new file mode 100644 index 0000000..e0e8f65 --- /dev/null +++ b/docs/HYPERTWIST_RESTRICTIVE_CLEAN_ROOM_LIVE_STATE_RECONCILIATION_2026-05-27.md @@ -0,0 +1,98 @@ +# HyperTwist Restrictive Clean-Room Live State Reconciliation - 2026-05-27 + +## Status + +This document is the current-live reconciliation note for HyperTwist's +restrictive clean-room lane sequence. + +It answers one narrow question: + +- does the current canon still correctly describe the restrictive queue as a + future `Phase 5R-A` opening, or has later clean-room implementation already + closed that queue into landed preserve lanes + +Result: + +- the original `Phase 5R-A next` wording is now historical only +- the restrictive queue is no longer a non-live four-row implementation board +- five restrictive clean-room lanes are already landed and must now be treated + as preserve-or-later-widen owner lanes + +## Source basis + +- `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:\HyperTwist\docs\v6_5_deep_manual_pack\HyperTwist\FEATURE_REGISTRY.md` +- `C:\HyperTwist\docs\HYPERTWIST_LIVE_LANES_SOURCE_AND_PRESERVATION_AUDIT_2026-05-13.md` +- `C:\Workspaces\HyperTwist\clean-room-specs\0100-cubing-alg-js.clean-room-prompt-sequence.md` +- `C:\Workspaces\HyperTwist\clean-room-specs\0200-cubing-twisty-js.clean-room-prompt-sequence.md` +- `C:\Workspaces\HyperTwist\clean-room-specs\0300-hactarce-2x2x2x2-scrambler.clean-room-prompt-sequence.md` +- `C:\Workspaces\HyperTwist\clean-room-specs\0400-kash-cubedesk.clean-room-prompt-sequence.md` + +## Current live restrictive clean-room set + +Current restrictive clean-room live lanes: + +- `onionhoney/roux-trainers` +- `cubing/alg.js` +- `cubing/twisty.js` +- `HactarCE/2x2x2x2-Scrambler` +- `kash/cubedesk` + +Current live counts at the repo-row level: + +- `71` total curated repo rows +- `24` current live repo rows +- `13` live permissive rows +- `6` live boundary-sensitive rows +- `5` live restrictive clean-room rows +- `47` current non-live rows + +## Why the old queue wording is now stale + +The original `Phase 5R-A` queue description was correct only before the later +clean-room implementation sequence landed. + +Current later authority already says: + +- `cubing/alg.js` is live and closed through `Bound 4` +- `cubing/twisty.js` is live and closed through `Bound 4` +- `HactarCE/2x2x2x2-Scrambler` is live and closed through `Bound 4` +- `kash/cubedesk` is live and closed through `Bound 5` +- `onionhoney/roux-trainers` remains the earliest landed restrictive + clean-room precedent, not the only one + +That means the restrictive clean-room board is no longer: + +- `1` landed row +- `4` selected-not-live clean-room candidates + +It is now: + +- `5` landed restrictive clean-room preserve rows +- `0` selected-not-live clean-room implementation-board rows + +## Current preserve-and-widen rule + +For the five landed restrictive rows: + +- do not reopen them by default as if they were still queued donor lanes +- do not treat their landed state as permission for direct restrictive mirror + reuse +- start later work 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 +- only open a new packet when a real later-bound widening or consumer-owner + gap is source-backed and explicit + +## Final call + +The correct current restrictive clean-room operator posture is: + +- preserve five landed restrictive clean-room owner lanes +- treat the original `Phase 5R-A next` wording as historical only +- do not advertise any default new restrictive opening +- keep the optional `Phase 3R-G` browser comparison lane deferred unless a + real browser-side gap is later proven diff --git a/docs/v6_5_deep_manual_pack/HyperTwist/AGENTS.md b/docs/v6_5_deep_manual_pack/HyperTwist/AGENTS.md index 72c8cb0..69cea5e 100644 --- a/docs/v6_5_deep_manual_pack/HyperTwist/AGENTS.md +++ b/docs/v6_5_deep_manual_pack/HyperTwist/AGENTS.md @@ -86,11 +86,14 @@ Canonical doctrine doc: For HyperTwist, keep this explicit: - current shallow-eval set: `71` repos -- currently verified live/implemented in checked Unreal surfaces: `20` +- currently verified live/implemented in checked Unreal surfaces: `24` - permissive live lanes: `13` - boundary-sensitive live lanes: `6` -- restrictive live lane: `1` -- the restrictive landed lane is `onionhoney/roux-trainers`, and it is to be treated as properly clean-roomed and then implemented +- restrictive live lanes: `5` +- the restrictive landed lanes are `onionhoney/roux-trainers`, + `cubing/alg.js`, `cubing/twisty.js`, `HactarCE/2x2x2x2-Scrambler`, and + `kash/cubedesk`, and they are to be treated as properly clean-roomed and + then implemented Do not collapse: @@ -105,8 +108,14 @@ into: ## Reset rule -Before recommending new HyperTwist donor-shaped widening from the remaining `51` current non-live rows: +Before recommending new HyperTwist donor-shaped widening from the remaining +`47` current non-live rows: - do not reopen the already closed `Phase 0R`, `Phase 1R`, or `Phase 2R` packets -- preserve the twenty landed rows as current truth -- continue from the closed packet sequence, with `Phase 5R-A` as the next non-optional move and the optional `Phase 3R-G` comparison lane deferred unless the landed primary browser spatial stack exposes a real gap +- preserve the twenty-four landed rows as current truth +- continue from the closed packet sequence with no default new `Phase 5R-A` + opening; use the landed restrictive per-lane authority for + `onionhoney/roux-trainers`, `cubing/alg.js`, `cubing/twisty.js`, + `HactarCE/2x2x2x2-Scrambler`, and `kash/cubedesk`, and keep the optional + `Phase 3R-G` comparison lane deferred unless the landed primary browser + spatial stack exposes a real gap