Document remotion restrictive-custody routing
This commit is contained in:
axiomlogicnexus
parent
9fafc9b1dd
commit
8c1847ca29
14 changed files with 71 additions and 4 deletions
|
|
@ -53,6 +53,13 @@ For HyperTwist repo evaluation, repo-custody, or license-audit work, a deep-sour
|
|||
- `docs/ops/HYPERTWIST_UNREAL_BUILD_VALIDATION_REQUIREMENT_2026-06-01.md` when Unreal build-validation posture or command changes
|
||||
- `docs/ops/HYPERTWIST_REVERSE_SSH_WINDOWS_BUILD_LANE_VERIFICATION_2026-06-01.md` when the verified reverse-tunnel path or proof details change
|
||||
|
||||
Current routing correction that future sessions must preserve:
|
||||
|
||||
- `remotion-dev/remotion` is no longer to be treated as a default boundary-sensitive widening lane for fresh HyperTwist implementation work
|
||||
- preserve the already-landed first-party `Phase 4R-F` media-export and replay-explainer outputs
|
||||
- treat any future donor-backed widening from `remotion-dev/remotion` as restrictive-custody and route it through explicit clean-room/specification work unless the lane is intentionally replaced by a first-party Unreal-native export path
|
||||
- prefer Unreal-native export for fresh shipping work when the retained Remotion value is not strictly required
|
||||
|
||||
The current HyperTwist restart endpoint for this sequence is `C:\HyperTwist\docs\ops\HYPERTWIST_DEEP_SOURCE_CLOSEOUT_AND_LEGAL_EVIDENCE_SEQUENCE_2026-05-26.md`.
|
||||
|
||||
When the user says continue, interpret it as continue in logical sequence, not merely resume the nearest open task. If the user says `c`, apply the same rule. If two or more options are paired and one logically widens or completes the lane needed by the others, do that sequence rather than picking an isolated substep out of order. In those cases, prefer the sequence that completes both or all aligned options, except for truly negligible or irrelevant leftovers that can be deferred without distorting the packet. The default continuation target is: scope the current packet, implement it, validate it, and keep going until the safe package is ready to land unless validation fails or a real decision is required.
|
||||
|
|
|
|||
|
|
@ -55,6 +55,12 @@ The current reconciled HyperTwist truth is:
|
|||
- currently verified live boundary-sensitive lanes: `6`
|
||||
- currently verified live restrictive lanes: `1`
|
||||
|
||||
`2026-06-12` routing correction:
|
||||
|
||||
- the `2026-05-12` snapshot above remains historically accurate for that restart pass
|
||||
- preserve the already-landed first-party `Phase 4R-F` outputs
|
||||
- for current work, do not treat `remotion-dev/remotion` as a default future boundary-sensitive widening lane; route future donor-backed widening through restrictive custody and explicit clean-room/specification work, or replace it with a first-party Unreal-native export path
|
||||
|
||||
The thirteen currently verified live permissive lanes are:
|
||||
|
||||
- `Aarav2709/KubeTimr`
|
||||
|
|
|
|||
|
|
@ -75,6 +75,12 @@ This document intentionally separates permissive, boundary-sensitive, and restri
|
|||
|
||||
Do not use this document as permission for `Model B` to read the restrictive mirror.
|
||||
|
||||
`2026-06-12` remotion routing correction:
|
||||
|
||||
- this audit's original `2026-05-13` snapshot recorded `remotion-dev/remotion` as a live boundary-sensitive lane
|
||||
- preserve the already-landed first-party `Phase 4R-F` outputs from that snapshot
|
||||
- do not use this audit as permission for fresh direct widening from `remotion-dev/remotion`; current future routing for that donor is restrictive-custody unless a later clean-room/specification pass explicitly reopens it
|
||||
|
||||
## Result
|
||||
|
||||
Current result:
|
||||
|
|
@ -507,6 +513,7 @@ Current status:
|
|||
|
||||
- `implemented_live_boundary_sensitive`
|
||||
- preserve as a landed first-party boundary-sensitive lane
|
||||
- `2026-06-12` routing correction: preserve the already-landed first-party outputs, but treat future donor-backed widening from `remotion-dev/remotion` as restrictive-custody and prefer Unreal-native export for fresh shipping work
|
||||
|
||||
Licensing posture:
|
||||
|
||||
|
|
@ -1282,6 +1289,7 @@ Rationale:
|
|||
|
||||
- this lane is strongest where HyperTwist needs replay explainers, bounded media export, embeddable playback, and parser semantics
|
||||
- the right preserve posture is a first-party sidecar lane with explicit package and commercial boundaries, not a broad product-shell carryover
|
||||
- future donor-backed widening now routes through restrictive custody and explicit clean-room/specification work, or through a first-party Unreal-native export replacement
|
||||
|
||||
Future widening rule:
|
||||
|
||||
|
|
|
|||
|
|
@ -219,6 +219,7 @@ Contract:
|
|||
- 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`
|
||||
- `2026-06-12` routing correction: preserve the already-landed first-party `Phase 4R-F` outputs, but do not treat `remotion-dev/remotion` as a default future boundary-sensitive widening lane; route future donor-backed widening through restrictive custody and explicit clean-room/specification work, or replace it with a first-party Unreal-native export path
|
||||
- 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
|
||||
|
||||
|
|
|
|||
|
|
@ -82,6 +82,16 @@ Boundary result:
|
|||
|
||||
- `remotion-dev/remotion` -> `implemented_live_boundary_sensitive`
|
||||
|
||||
## 2026-06-12 routing correction
|
||||
|
||||
This packet remains the historical first-party landing record for the already-landed Unreal media-export, embedded-playback, parser, and replay-explainer surfaces.
|
||||
|
||||
Current doctrine correction:
|
||||
|
||||
- do not treat this packet as permission to reopen `remotion-dev/remotion` as a default future boundary-sensitive widening lane
|
||||
- treat future donor-backed widening from `remotion-dev/remotion` as restrictive-custody and route it through explicit clean-room/specification work
|
||||
- prefer Unreal-native export for fresh shipping work when the retained Remotion value is not strictly required
|
||||
|
||||
Current portfolio effect:
|
||||
|
||||
- curated HyperTwist shallow-eval set: `71`
|
||||
|
|
|
|||
|
|
@ -9,6 +9,7 @@ Boundary:
|
|||
- historical alias rows whose standalone repo surfaces are gone but whose maintained public source surfaces now live elsewhere are kept visible as historical references, not as unresolved mirror-restoration work
|
||||
- upstream-unavailable rows, unresolved missing mirror paths, and genuinely unrelated non-standalone paths stay visible outside the standalone count instead of being silently discarded
|
||||
- when later repos are mirrored or their root-license evidence changes, rerun `C:\HyperTwist\scripts\Write-HyperTwistRepoLicenseEvidenceAudit.ps1` in the same pass that updates the legal tracker
|
||||
- `2026-06-12` routing alignment note: this audit already records `remotion-dev/remotion` under restrictive mirror custody and a commercial-custom root license signal, so current product/routing docs should not keep treating it as a default future boundary-sensitive widening lane
|
||||
|
||||
Counts:
|
||||
- total deduped repos scanned: 69
|
||||
|
|
|
|||
|
|
@ -37,6 +37,16 @@ Use
|
|||
for the current restrictive-lane preserve posture and for the correction that
|
||||
the original `Phase 5R-A next` wording is now historical only.
|
||||
|
||||
## 2026-06-12 remotion routing correction
|
||||
|
||||
This board still preserves the historical `Phase 4R-F` row as it was landed in that packet sequence.
|
||||
|
||||
Current routing correction:
|
||||
|
||||
- preserve the already-landed first-party `Phase 4R-F` media-export and replay-explainer outputs
|
||||
- do not treat `remotion-dev/remotion` as an unproblematic future boundary-sensitive widening lane
|
||||
- route future donor-backed widening from `remotion-dev/remotion` through restrictive custody and explicit clean-room/specification work, or replace it with a first-party Unreal-native export path
|
||||
|
||||
## 2026-05-27 later permissive live-state update
|
||||
|
||||
Later current-live permissive truth inside this original `71`-row shallow-eval
|
||||
|
|
|
|||
|
|
@ -796,6 +796,12 @@ The six boundary-sensitive live lanes are:
|
|||
- `screenpipe/screenpipe`
|
||||
- `remotion-dev/remotion`
|
||||
|
||||
`2026-06-12` routing correction:
|
||||
|
||||
- preserve the already-landed first-party `Phase 4R-F` outputs
|
||||
- do not treat `remotion-dev/remotion` as a default future boundary-sensitive widening lane even though older summaries grouped it here
|
||||
- route future donor-backed widening from `remotion-dev/remotion` through restrictive custody and explicit clean-room/specification work, or replace it with a first-party Unreal-native export path
|
||||
|
||||
Those boundary-sensitive lanes should now be treated as:
|
||||
|
||||
- implementation-authorized without clean-room by default
|
||||
|
|
@ -816,6 +822,10 @@ The six restrictive live lanes are:
|
|||
- `kash/cubedesk`
|
||||
- `poliva/cubedex`
|
||||
|
||||
Current restrictive-routing clarification:
|
||||
|
||||
- `remotion-dev/remotion` now shares the restrictive-custody future-widening posture even though the older summary above still preserves its historical `Phase 4R-F` landing position
|
||||
|
||||
Those restrictive lanes should now be treated as:
|
||||
|
||||
- the five historically restrictive implementation lanes remain properly
|
||||
|
|
@ -2799,8 +2809,8 @@ Current licensing judgment:
|
|||
|
||||
- custom commercial two-tier license at repo level
|
||||
- not a clean permissive donor
|
||||
- not a clean-room requirement by default
|
||||
- treat as a landed commercially sensitive bounded sidecar preserve lane through `Phase 4R-F`
|
||||
- preserve the already-landed first-party `Phase 4R-F` sidecar outputs
|
||||
- current future-widening posture is restrictive-custody and explicit clean-room/specification work unless the lane is intentionally replaced by a first-party Unreal-native export path
|
||||
|
||||
Source basis:
|
||||
|
||||
|
|
@ -2837,6 +2847,7 @@ Approved working posture:
|
|||
- preserve the first-party landed result as a bounded media-export, embedded-playback, parser, explainer-studio, and package-split compliance lane
|
||||
- do not treat the broader authoring shell, template ecosystem, or platform shell as landed donor value
|
||||
- start future enhancement work from the live-lane audit, then `Phase 4R-F`, then this tracker, rather than from the raw mirror alone
|
||||
- do not reopen direct donor-backed widening from the raw mirror; future widening now routes through restrictive custody and explicit clean-room/specification work, or through a first-party Unreal-native export replacement
|
||||
|
||||
### `met4citizen/TalkingHead`
|
||||
|
||||
|
|
|
|||
|
|
@ -407,10 +407,13 @@ Closure read:
|
|||
- [ ] Load replay, reconstruct animation
|
||||
|
||||
### 9B — Media Export
|
||||
- [ ] Integrate `remotion-dev/remotion` or UE `MovieRenderQueue` for video export
|
||||
- [ ] Use UE `MovieRenderQueue` as the primary video-export route; treat `remotion-dev/remotion` only as restrictive-custody reference context unless a later clean-room/specification pass explicitly reopens it
|
||||
- [ ] Export solve animation as MP4
|
||||
- [ ] Export scramble + time as shareable image
|
||||
|
||||
Routing correction:
|
||||
- `2026-06-12`: `remotion-dev/remotion` is no longer an unproblematic direct widening lane for Phase `9B`; preserve the already-landed first-party `Phase 4R-F` outputs, but route any new donor-backed widening through restrictive custody and prefer Unreal-native export for fresh shipping work
|
||||
|
||||
### 9C — Leaderboard Stub
|
||||
- [ ] Local SQLite or JSON leaderboard (no backend yet)
|
||||
- [ ] Store best times per puzzle type + scramble length
|
||||
|
|
|
|||
|
|
@ -117,6 +117,7 @@ That matters immediately for retained restrictive lanes such as:
|
|||
- `cubing/twisty.js`
|
||||
- `HactarCE/2x2x2x2-Scrambler`
|
||||
- `kash/cubedesk`
|
||||
- `remotion-dev/remotion` for future donor-backed media-export or replay-explainer widening now that the lane is treated as restrictive-custody rather than a default boundary-sensitive route
|
||||
|
||||
Donor commands remain:
|
||||
|
||||
|
|
|
|||
|
|
@ -127,6 +127,7 @@ For HyperTwist, keep this explicit:
|
|||
- permissive live lanes: `21`
|
||||
- boundary-sensitive live lanes: `7`
|
||||
- restrictive live lanes: `5`
|
||||
- `2026-06-12` routing correction: preserve the already-landed first-party `Phase 4R-F` outputs, but do not treat `remotion-dev/remotion` as a default future boundary-sensitive widening lane; route future donor-backed widening through restrictive custody and explicit clean-room/specification work, or replace it with a first-party Unreal-native export path
|
||||
- current repo-row source-truth pack therefore sits at `33` live rows
|
||||
overall: `21` permissive, `7` boundary-sensitive, and `5` restrictive
|
||||
clean-room lanes
|
||||
|
|
|
|||
|
|
@ -166,7 +166,7 @@ repo.
|
|||
| Classic-cubing semantic, bridge, and `MPL`-boundary reference grounding | Implemented now | `cubing/cubing.js` retained boundary-sensitive lane + first-party current code | Current live `Classic Cubing Semantics and Runtime` reference side includes seven rewritten first-party contract/reference targets grounded in `cubing/cubing.js`: semantics, geometry, viewer adapter, device boundary, search contract, Melinda bridge, and explicit `MPL` compliance-boundary notes. This does not displace the landed `Phase 4R-A` first-party owner lane, the separate `cubing/twisty.js` replay shell lane, the separate `cubing/alg.js` parser/AST lane, or the explicit practical `MPL` path and notice-retention boundary. |
|
||||
| Seeded competition scramble workflow and lightweight scramble-operator shell adjuncts | Deep-source grounded retained | `cubing/cubing.js` retained lane + `cubing/mark3` / `cubing/scramble.cubing.net` successor evaluation | Source-backed successor surfaces sharpen competition-spec workflow and operator-shell expectations above the retained scramble and visualization seams, but they do not displace `cubing/cubing.js` or `cubing/twisty.js`; `scramble-display` remains comparison-only. |
|
||||
| Replay shell and timeline | Implemented now | landed `cubing/twisty.js` bounded packets | First-party `HyperTwistSimulation` now owns the bounded replay-player shell, cursor/timeline transport, adapter/bootstrap, and local visualization or fallback presentation contract grounded in `cubing/twisty.js`; classic-cubing semantics remain with `cubing/cubing.js`, parser and AST ownership remain with `cubing/alg.js`, and broader browser support ownership stays with the landed browser lanes. |
|
||||
| Media-export, embedded-playback, and replay-explainer reference grounding | Implemented now | `remotion-dev/remotion` retained boundary-sensitive lane + first-party current code | Current live `Media Export and Replay Explainers` reference side includes five rewritten first-party contract/reference targets grounded in `remotion-dev/remotion`: embedded playback, render orchestration, media parser, explainer-studio preview/output registration, and explicit commercial-license/package-split compliance-boundary notes. This does not displace the landed `Phase 4R-F` first-party owner lane, the broader browser/spatial/media adjunct family, or the explicit package-split commercial boundary. |
|
||||
| Media-export, embedded-playback, and replay-explainer reference grounding | Implemented now | `remotion-dev/remotion` retained restrictive-custody lane + first-party current code | Current live `Media Export and Replay Explainers` reference side includes five rewritten first-party contract/reference targets grounded in `remotion-dev/remotion`: embedded playback, render orchestration, media parser, explainer-studio preview/output registration, and explicit commercial-license/package-split compliance-boundary notes. This does not displace the landed `Phase 4R-F` first-party owner lane, the broader browser/spatial/media adjunct family, or the explicit package-split commercial boundary. Current routing correction: preserve the already-landed first-party outputs, but treat future donor-backed widening from `remotion-dev/remotion` as restrictive-custody and prefer Unreal-native export for fresh shipping work. |
|
||||
| Browser-viewer, compact-editor, export, and docs-boundary grounding | Implemented now | `google/model-viewer` retained permissive lane + first-party current code | Current live `Browser Viewer and Asset QA` reference side includes five rewritten first-party contract/reference targets grounded in the root `google/model-viewer` lane: viewer embed, compact editor/inspection, snippet/export, renderer comparison/fidelity, and docs/demo separation. The subordinate `space-opera`, `modelviewer.dev`, and `render-fidelity-tools` source attributions are absorbed here as support-only contributors rather than separate live owner lanes. This does not displace the landed `Phase 3R-D` first-party owner lane, the separate `KhronosGroup/glTF-Sample-Viewer` standards-aware QA lane, or the already explicit `google/model-viewer/packages/shared-assets` boundary-sensitive fixture lane. |
|
||||
| Standards-aware asset-validation and statistics grounding | Implemented now | `KhronosGroup/glTF-Sample-Viewer` retained permissive support lane + first-party current code | Current live `Browser Viewer and Asset QA` reference side includes one rewritten first-party target grounded in `KhronosGroup/glTF-Sample-Viewer`: standards-aware asset validation and statistics. This does not displace the landed `Phase 3R-D` first-party browser viewer owner, the separate root `google/model-viewer` viewer/reference lane, or the already explicit shared-assets boundary-sensitive fixture lane. |
|
||||
| Browser-viewer shared-asset fixture and provenance grounding | Implemented now | `google/model-viewer/packages/shared-assets` retained boundary-sensitive lane + first-party current code | Current live `Browser Viewer Shared Asset Fixtures` reference side includes five rewritten first-party contract/reference targets grounded in `google/model-viewer/packages/shared-assets`: fixture allowlist, `CC0` environment matrix, provenance-boundary review split, fixture-refresh pattern, and contributed geometry smoke-test boundary notes. This does not displace the landed `Phase 4R-C` first-party owner lane, the broader `google/model-viewer` browser viewer lane, or the explicit mixed per-asset review and shipping boundary. |
|
||||
|
|
|
|||
|
|
@ -151,6 +151,12 @@ The seven boundary-sensitive live lanes are:
|
|||
- `screenpipe/screenpipe`
|
||||
- `remotion-dev/remotion`
|
||||
|
||||
`2026-06-12` routing correction:
|
||||
|
||||
- preserve the already-landed first-party `Phase 4R-F` outputs
|
||||
- do not treat `remotion-dev/remotion` as a default future boundary-sensitive widening lane even though older summaries grouped it here
|
||||
- route future donor-backed widening from `remotion-dev/remotion` through restrictive custody and explicit clean-room/specification work, or replace it with a first-party Unreal-native export path
|
||||
|
||||
The five restrictive live lanes are:
|
||||
|
||||
- `onionhoney/roux-trainers`
|
||||
|
|
@ -258,6 +264,7 @@ Current HyperTwist correction:
|
|||
- twenty-one permissive lanes are already live, including the landed analytics/reporting lane, the landed hypercubing knowledge and community-reference lane, the landed browser spatial owner trio, the landed bounded speech/voice permissive lanes, and the landed bounded hyper/simulation widening lanes
|
||||
- seven boundary-sensitive lanes are already live: `coqui-ai/TTS` through an explicit `MPL` code-side boundary, `cubing/cubing.js` through an explicit `MPL`-aware adapter posture, `cutelyaware/magiccube4d` through an explicit attribution/provenance boundary, `google/model-viewer/packages/shared-assets` through an explicit allowlist/provenance boundary, `PostHog/posthog` through an explicit root-`MIT`-core-versus-`ee/` subtree boundary, `screenpipe/screenpipe` through an explicit permissive-core-versus-`ee/` subtree boundary, and `remotion-dev/remotion` through an explicit package-split commercial boundary
|
||||
- five restrictive lanes are now live in custody terms, with `onionhoney/roux-trainers` preserved as the earlier clean-room precedent and the later retained restrictive rows landed through accepted clean-room routing; `poliva/cubedex` remains restrictive-custody comparison context only and is not a live restrictive lane
|
||||
- `2026-06-12` remotion route correction: preserve the already-landed first-party `Phase 4R-F` media-export and replay-explainer outputs, but do not treat `remotion-dev/remotion` as a default future boundary-sensitive widening lane; for future donor-backed widening, route it through restrictive custody and explicit clean-room/specification work, or replace it with a first-party Unreal-native export path
|
||||
- supplemental row `cubing/qqTimer` is mirrored under restrictive custody with no clear root license signal
|
||||
- `cubing/scrambles` is now a historical alias row rather than an active unresolved mirror-restoration target, because maintained public scramble source surfaces are already visible elsewhere in the cubing family
|
||||
- the `google/model-viewer/packages/*` and `pmndrs/react-spring/packages/*`
|
||||
|
|
|
|||
|
|
@ -465,6 +465,7 @@ Donor-strength rule:
|
|||
- `Phase 4R-D` is now closed as the landed `PostHog/posthog` control-plane subtree-boundary widening packet
|
||||
- `Phase 4R-E` is now closed as the landed `screenpipe/screenpipe` capture-history subtree-boundary widening packet
|
||||
- `Phase 4R-F` is now closed as the landed `remotion-dev/remotion` media-export and package-split commercial-boundary widening packet
|
||||
- `2026-06-12` routing correction: preserve the already-landed first-party `Phase 4R-F` outputs, but treat `remotion-dev/remotion` itself as restrictive-custody for future donor-backed widening and prefer Unreal-native export for fresh shipping work
|
||||
|
||||
Current routing truth:
|
||||
|
||||
|
|
|
|||
Loading…
Add table
Reference in a new issue