From ba262b7f820136ac4a7feabcb62420c3acafd67f Mon Sep 17 00:00:00 2001 From: axiomlogicnexus Date: Wed, 13 May 2026 17:57:10 +0200 Subject: [PATCH] Close HyperTwist Phase 3R packet 3R-E --- ...twist-catalog-materialization-summary.json | 4 +- ...twist-reference-incorporation-targets.json | 252 ++++++- ...4citizen-talkinghead-reference-pages.jsonl | 6 + .../HyperTwistTrainingCompanionLibrary.cpp | 622 ++++++++++++++++++ .../HyperTwistTrainingRuntimeLibrary.cpp | 49 ++ .../HyperTwistTrainingCompanionLibrary.h | 405 ++++++++++++ .../HyperTwistTrainingRuntimeLibrary.h | 25 + ..._MIRROR_WORKSPACE_AND_SUBMODULE_HANDOFF.md | 10 +- .../HT_REPO_INCORPORATION_AUDIT_2026-05-11.md | 8 +- ...NICAL_RESTART_RECONCILIATION_2026-05-12.md | 30 +- ...OURCE_AND_PRESERVATION_AUDIT_2026-05-13.md | 84 ++- ...NED_SET_CONTRACT_AND_HANDOFF_2026-05-13.md | 24 +- ...E_TALKINGHEAD_IMPLEMENTATION_2026-05-13.md | 152 +++++ ..._AND_IMPLEMENTATION_SCHEDULE_2026-05-11.md | 51 +- .../HYPERTWIST_REPO_STATE_BOARD_2026-05-11.md | 36 +- docs/REPO_LICENSE_TRACKING.md | 20 +- ..._unified_copyleft_strategy_matrix_v6_3.csv | 2 +- ...epo_portfolio_unified_operational_v6_3.csv | 68 +- docs/repo_portfolio_unified_phase_g_v6_3.csv | 68 +- ...po_portfolio_unified_source_audit_v6_3.csv | 2 +- .../HyperTwist/AGENTS.md | 8 +- .../HyperTwist/DEVELOPMENT.md | 11 +- .../HyperTwist/LICENSETRACKING.md | 13 +- .../HyperTwist/ROADMAP.md | 9 +- 24 files changed, 1791 insertions(+), 168 deletions(-) create mode 100644 UnrealHyperTwist/Content/HyperTwistTraining/MaterializedCatalog/raw-extracts/met4citizen-talkinghead-reference-pages.jsonl create mode 100644 UnrealHyperTwist/Source/UnrealHyperTwist/Private/HyperTwistTraining/HyperTwistTrainingCompanionLibrary.cpp create mode 100644 UnrealHyperTwist/Source/UnrealHyperTwist/Public/HyperTwistTraining/HyperTwistTrainingCompanionLibrary.h create mode 100644 docs/HYPERTWIST_PHASE_3R_PACKET_3R_E_TALKINGHEAD_IMPLEMENTATION_2026-05-13.md diff --git a/UnrealHyperTwist/Content/HyperTwistTraining/MaterializedCatalog/hypertwist-catalog-materialization-summary.json b/UnrealHyperTwist/Content/HyperTwistTraining/MaterializedCatalog/hypertwist-catalog-materialization-summary.json index f387170..4c3f471 100644 --- a/UnrealHyperTwist/Content/HyperTwistTraining/MaterializedCatalog/hypertwist-catalog-materialization-summary.json +++ b/UnrealHyperTwist/Content/HyperTwistTraining/MaterializedCatalog/hypertwist-catalog-materialization-summary.json @@ -1,5 +1,5 @@ { - "generated_at": "2026-05-13T14:31:59.5116632Z", + "generated_at": "2026-05-13T16:20:00Z", "slice": "catalog-materialization", "slice_status": "closed", "counts": { @@ -7,7 +7,7 @@ "track_manifests": 14, "deck_import_specs": 498, "runtime_content_bundles": 498, - "reference_targets": 23, + "reference_targets": 29, "overlap_pruned_exclusions": 29 } } diff --git a/UnrealHyperTwist/Content/HyperTwistTraining/MaterializedCatalog/hypertwist-reference-incorporation-targets.json b/UnrealHyperTwist/Content/HyperTwistTraining/MaterializedCatalog/hypertwist-reference-incorporation-targets.json index 86bf931..d18ad85 100644 --- a/UnrealHyperTwist/Content/HyperTwistTraining/MaterializedCatalog/hypertwist-reference-incorporation-targets.json +++ b/UnrealHyperTwist/Content/HyperTwistTraining/MaterializedCatalog/hypertwist-reference-incorporation-targets.json @@ -1,5 +1,5 @@ { - "generated_at": "2026-05-13T14:31:59.4856400Z", + "generated_at": "2026-05-13T16:20:00Z", "reference_targets": [ { "ReferenceTargetId": "reference/speedcubedb-course-reference-page-speedcubedb-root", @@ -930,10 +930,258 @@ "family": "docs-demo-separation", "subset": null }, - "MaterializationNotes": [ + "MaterializationNotes": [ "Preserve bounded docs/demo separation semantics while rewriting the actual support copy and shell in first-party HyperTwist language.", "This target keeps modelviewer.dev explicitly subordinate to the landed browser viewer lane." ] + }, + { + "ReferenceTargetId": "reference/met4citizen-talkinghead-companion-reference-page-narration", + "SurfaceType": "companion-reference", + "TrackTitle": "Embodied Companion and Narrated Coaching", + "ItemTitle": "Embodied Companion Narration", + "IncorporationChannel": "narration-contract", + "TargetAssetFamily": "companion-note", + "PuzzleFamily": "Other", + "NotationProfile": "family-specific", + "SourceAttribution": { + "SourceMode": "DirectDonor", + "SourceRepo": "met4citizen/TalkingHead", + "SourceLicense": "MIT", + "SourceTrackId": "companion/narration-contract", + "SourceDeckId": "", + "SourceCaseId": "", + "SourceNotes": "First-party HyperTwist narration target preserving queued coach speech, subtitle timing, viseme alignment, and gesture-aware companion presentation from the retained TalkingHead lane." + }, + "PreserveFactualElements": [ + "queued speech lifecycle", + "subtitle timing", + "viseme alignment", + "gesture and mood cues" + ], + "RewriteRequiredElements": [ + "all donor example-shell framing", + "all donor vendor-specific copy", + "all donor avatar-demo wording" + ], + "ContentSourceFile": "./raw-extracts/met4citizen-talkinghead-reference-pages.jsonl", + "MatchFilter": { + "source": "met4citizen/TalkingHead", + "source_scope": "repo-backed", + "structure_template": "embodied-companion-reference-page", + "family": "embodied-companion-narration", + "subset": null + }, + "MaterializationNotes": [ + "Preserve bounded coach narration semantics while rewriting the actual companion shell in first-party HyperTwist terms.", + "This target pairs with the compiled Phase 3R-E narration contract and runtime access layer." + ] + }, + { + "ReferenceTargetId": "reference/met4citizen-talkinghead-companion-subtitle-reference-page-sync", + "SurfaceType": "companion-subtitle-reference", + "TrackTitle": "Embodied Companion and Narrated Coaching", + "ItemTitle": "Subtitle and Viseme Synchronization", + "IncorporationChannel": "subtitle-sync-contract", + "TargetAssetFamily": "subtitle-checklist", + "PuzzleFamily": "Other", + "NotationProfile": "family-specific", + "SourceAttribution": { + "SourceMode": "DirectDonor", + "SourceRepo": "met4citizen/TalkingHead", + "SourceLicense": "MIT", + "SourceTrackId": "companion/subtitle-and-viseme-sync", + "SourceDeckId": "", + "SourceCaseId": "", + "SourceNotes": "First-party HyperTwist subtitle target preserving bounded caption timing, marker sync, and viseme-envelope behavior from the retained TalkingHead lane." + }, + "PreserveFactualElements": [ + "word-level subtitle cues", + "marker sync", + "blendshape viseme envelopes" + ], + "RewriteRequiredElements": [ + "all donor UI wording", + "all donor demo captions", + "all donor tutorial framing" + ], + "ContentSourceFile": "./raw-extracts/met4citizen-talkinghead-reference-pages.jsonl", + "MatchFilter": { + "source": "met4citizen/TalkingHead", + "source_scope": "repo-backed", + "structure_template": "companion-subtitle-reference-page", + "family": "subtitle-and-viseme-sync", + "subset": null + }, + "MaterializationNotes": [ + "Preserve bounded subtitle and viseme timing semantics while rewriting the surfaced cue shell in first-party HyperTwist language.", + "This target pairs with the compiled Phase 3R-E subtitle and viseme reference bundle." + ] + }, + { + "ReferenceTargetId": "reference/met4citizen-talkinghead-companion-avatar-reference-page-embed", + "SurfaceType": "companion-avatar-reference", + "TrackTitle": "Embodied Companion and Narrated Coaching", + "ItemTitle": "Avatar-Only Embed Contract", + "IncorporationChannel": "avatar-embed-contract", + "TargetAssetFamily": "embed-note", + "PuzzleFamily": "Other", + "NotationProfile": "family-specific", + "SourceAttribution": { + "SourceMode": "DirectDonor", + "SourceRepo": "met4citizen/TalkingHead", + "SourceLicense": "MIT", + "SourceTrackId": "companion/avatar-only-embed", + "SourceDeckId": "", + "SourceCaseId": "", + "SourceNotes": "First-party HyperTwist embed target preserving bounded external-scene avatar composition, retargeting, and camera-safe companion presence from the retained TalkingHead lane." + }, + "PreserveFactualElements": [ + "external scene embedding", + "camera-safe avatar composition", + "retargeted motion and pose" + ], + "RewriteRequiredElements": [ + "all donor asset assumptions", + "all donor demo shell framing", + "all donor avatar picker UX" + ], + "ContentSourceFile": "./raw-extracts/met4citizen-talkinghead-reference-pages.jsonl", + "MatchFilter": { + "source": "met4citizen/TalkingHead", + "source_scope": "repo-backed", + "structure_template": "companion-avatar-reference-page", + "family": "avatar-only-embedding", + "subset": null + }, + "MaterializationNotes": [ + "Preserve bounded avatar-only embedding semantics while rewriting the actual companion scene shell in first-party HyperTwist terms.", + "This target pairs with the compiled Phase 3R-E avatar embed contract." + ] + }, + { + "ReferenceTargetId": "reference/met4citizen-talkinghead-companion-gesture-reference-page-presets", + "SurfaceType": "companion-gesture-reference", + "TrackTitle": "Embodied Companion and Narrated Coaching", + "ItemTitle": "Gesture, Mood, and Pose Surface", + "IncorporationChannel": "gesture-mood-contract", + "TargetAssetFamily": "gesture-note", + "PuzzleFamily": "Other", + "NotationProfile": "family-specific", + "SourceAttribution": { + "SourceMode": "DirectDonor", + "SourceRepo": "met4citizen/TalkingHead", + "SourceLicense": "MIT", + "SourceTrackId": "companion/gesture-mood-and-pose", + "SourceDeckId": "", + "SourceCaseId": "", + "SourceNotes": "First-party HyperTwist gesture target preserving bounded coach acknowledgement, focus-callout, celebration, and mood-switching semantics from the retained TalkingHead lane." + }, + "PreserveFactualElements": [ + "gesture presets", + "mood switching", + "coach-facing pose cues" + ], + "RewriteRequiredElements": [ + "all donor animation-demo framing", + "all donor shell wording", + "all donor example choreography copy" + ], + "ContentSourceFile": "./raw-extracts/met4citizen-talkinghead-reference-pages.jsonl", + "MatchFilter": { + "source": "met4citizen/TalkingHead", + "source_scope": "repo-backed", + "structure_template": "companion-gesture-reference-page", + "family": "gesture-mood-and-pose", + "subset": null + }, + "MaterializationNotes": [ + "Preserve bounded gesture, mood, and pose semantics while rewriting the actual coach-presence shell in first-party HyperTwist language.", + "This target keeps expressive presentation inside the embodied companion lane rather than spreading it into unrelated owners." + ] + }, + { + "ReferenceTargetId": "reference/met4citizen-talkinghead-companion-listening-reference-page-lifecycle", + "SurfaceType": "companion-listening-reference", + "TrackTitle": "Embodied Companion and Narrated Coaching", + "ItemTitle": "Streaming and Listening Lifecycle", + "IncorporationChannel": "listening-lifecycle-contract", + "TargetAssetFamily": "listening-note", + "PuzzleFamily": "Other", + "NotationProfile": "family-specific", + "SourceAttribution": { + "SourceMode": "DirectDonor", + "SourceRepo": "met4citizen/TalkingHead", + "SourceLicense": "MIT", + "SourceTrackId": "companion/streaming-and-listening-lifecycle", + "SourceDeckId": "", + "SourceCaseId": "", + "SourceNotes": "First-party HyperTwist listening target preserving bounded streaming playback, queue underrun handling, and microphone threshold-gating semantics from the retained TalkingHead lane." + }, + "PreserveFactualElements": [ + "audio stream buffering", + "queue underrun handling", + "listening thresholds", + "microphone handoff" + ], + "RewriteRequiredElements": [ + "all donor vendor tutorial text", + "all donor example shell framing", + "all donor microphone-demo wording" + ], + "ContentSourceFile": "./raw-extracts/met4citizen-talkinghead-reference-pages.jsonl", + "MatchFilter": { + "source": "met4citizen/TalkingHead", + "source_scope": "repo-backed", + "structure_template": "companion-listening-reference-page", + "family": "streaming-and-listening-lifecycle", + "subset": null + }, + "MaterializationNotes": [ + "Preserve bounded streaming and listening semantics while rewriting the surfaced audio and microphone shell in first-party HyperTwist terms.", + "This target pairs with the compiled Phase 3R-E queue lifecycle and listening contract surfaces." + ] + }, + { + "ReferenceTargetId": "reference/met4citizen-talkinghead-companion-boundary-reference-page-adapter", + "SurfaceType": "companion-boundary-reference", + "TrackTitle": "Embodied Companion and Narrated Coaching", + "ItemTitle": "TTS and Asset Adapter Boundary", + "IncorporationChannel": "vendor-adapter-boundary", + "TargetAssetFamily": "boundary-note", + "PuzzleFamily": "Other", + "NotationProfile": "family-specific", + "SourceAttribution": { + "SourceMode": "DirectDonor", + "SourceRepo": "met4citizen/TalkingHead", + "SourceLicense": "MIT", + "SourceTrackId": "companion/tts-and-asset-adapter-boundary", + "SourceDeckId": "", + "SourceCaseId": "", + "SourceNotes": "First-party HyperTwist boundary target preserving configurable TTS, JWT, avatar, and streaming seams while keeping donor examples and sample assets explicitly outside the shipped companion lane." + }, + "PreserveFactualElements": [ + "replaceable voice-service fields", + "asset-seam boundaries", + "demo-only shell separation" + ], + "RewriteRequiredElements": [ + "all donor vendor branding", + "all donor example copy", + "all donor sample-asset assumptions" + ], + "ContentSourceFile": "./raw-extracts/met4citizen-talkinghead-reference-pages.jsonl", + "MatchFilter": { + "source": "met4citizen/TalkingHead", + "source_scope": "repo-backed", + "structure_template": "companion-boundary-reference-page", + "family": "tts-and-asset-adapter-boundary", + "subset": null + }, + "MaterializationNotes": [ + "Preserve bounded TTS and asset-adapter semantics while rewriting the surfaced configuration shell in first-party HyperTwist language.", + "This target keeps sample avatars, vendor wiring, and donor examples subordinate to the landed companion owner." + ] } ] } diff --git a/UnrealHyperTwist/Content/HyperTwistTraining/MaterializedCatalog/raw-extracts/met4citizen-talkinghead-reference-pages.jsonl b/UnrealHyperTwist/Content/HyperTwistTraining/MaterializedCatalog/raw-extracts/met4citizen-talkinghead-reference-pages.jsonl new file mode 100644 index 0000000..0e54a97 --- /dev/null +++ b/UnrealHyperTwist/Content/HyperTwistTraining/MaterializedCatalog/raw-extracts/met4citizen-talkinghead-reference-pages.jsonl @@ -0,0 +1,6 @@ +{"source":"met4citizen/TalkingHead","source_scope":"repo-backed","family":"embodied-companion-narration","subset":"narration","page_id":"embodied-companion-narration","page_title":"Embodied Companion Narration Contract","surface_type":"companion-reference","origin_paths":["C:\\Workspaces\\HyperTwist\\mirrors\\permissive\\met4citizen\\TalkingHead\\modules\\talkinghead.mjs"],"preserve_factual_elements":["queued speech lifecycle","subtitle timing","viseme alignment","gesture and mood cues"],"notes":"Source-backed narration target for first-party HyperTwist coach speech, subtitle synchronization, viseme timing, and gesture-aware companion presentation without promoting the donor demo shell."} +{"source":"met4citizen/TalkingHead","source_scope":"repo-backed","family":"subtitle-and-viseme-sync","subset":"subtitle","page_id":"subtitle-and-viseme-sync","page_title":"Subtitle and Viseme Synchronization","surface_type":"companion-subtitle-reference","origin_paths":["C:\\Workspaces\\HyperTwist\\mirrors\\permissive\\met4citizen\\TalkingHead\\modules\\talkinghead.mjs","C:\\Workspaces\\HyperTwist\\mirrors\\permissive\\met4citizen\\TalkingHead\\modules\\lipsync-en.mjs"],"preserve_factual_elements":["word-level subtitle cues","marker sync","blendshape viseme envelopes"],"notes":"Source-backed subtitle and viseme target for first-party HyperTwist caption timing, viseme emission, and marker-aligned coach playback beneath the embodied companion lane."} +{"source":"met4citizen/TalkingHead","source_scope":"repo-backed","family":"avatar-only-embedding","subset":"embed","page_id":"avatar-only-embed","page_title":"Avatar-Only Embed Contract","surface_type":"companion-avatar-reference","origin_paths":["C:\\Workspaces\\HyperTwist\\mirrors\\permissive\\met4citizen\\TalkingHead\\modules\\talkinghead.mjs","C:\\Workspaces\\HyperTwist\\mirrors\\permissive\\met4citizen\\TalkingHead\\modules\\retargeter.mjs"],"preserve_factual_elements":["external scene embedding","camera-safe avatar composition","retargeted motion and pose"],"notes":"Source-backed avatar-only embed target for first-party HyperTwist external-scene companion presence, retargeting-aware motion, and bounded camera framing."} +{"source":"met4citizen/TalkingHead","source_scope":"repo-backed","family":"gesture-mood-and-pose","subset":"gesture","page_id":"gesture-mood-and-pose","page_title":"Gesture, Mood, and Pose Surface","surface_type":"companion-gesture-reference","origin_paths":["C:\\Workspaces\\HyperTwist\\mirrors\\permissive\\met4citizen\\TalkingHead\\modules\\talkinghead.mjs"],"preserve_factual_elements":["gesture presets","mood switching","coach-facing pose cues"],"notes":"Source-backed gesture and mood target for first-party HyperTwist coach acknowledgements, focus callouts, celebration cues, and supportive pose changes."} +{"source":"met4citizen/TalkingHead","source_scope":"repo-backed","family":"streaming-and-listening-lifecycle","subset":"listening","page_id":"streaming-and-listening-lifecycle","page_title":"Streaming and Listening Lifecycle","surface_type":"companion-listening-reference","origin_paths":["C:\\Workspaces\\HyperTwist\\mirrors\\permissive\\met4citizen\\TalkingHead\\modules\\talkinghead.mjs","C:\\Workspaces\\HyperTwist\\mirrors\\permissive\\met4citizen\\TalkingHead\\tests\\streaming-tests.html","C:\\Workspaces\\HyperTwist\\mirrors\\permissive\\met4citizen\\TalkingHead\\examples\\azure-audio-streaming.html"],"preserve_factual_elements":["audio stream buffering","queue underrun handling","listening thresholds","microphone handoff"],"notes":"Source-backed streaming and listening target for first-party HyperTwist low-latency coach playback, queue lifecycle metrics, and microphone threshold gating."} +{"source":"met4citizen/TalkingHead","source_scope":"repo-backed","family":"tts-and-asset-adapter-boundary","subset":"boundary","page_id":"tts-and-asset-adapter-boundary","page_title":"TTS and Asset Adapter Boundary","surface_type":"companion-boundary-reference","origin_paths":["C:\\Workspaces\\HyperTwist\\mirrors\\permissive\\met4citizen\\TalkingHead\\README.md","C:\\Workspaces\\HyperTwist\\mirrors\\permissive\\met4citizen\\TalkingHead\\modules\\talkinghead.mjs","C:\\Workspaces\\HyperTwist\\mirrors\\permissive\\met4citizen\\TalkingHead\\examples\\azure-audio-streaming.html"],"preserve_factual_elements":["replaceable voice-service fields","asset-seam boundaries","demo-only shell separation"],"notes":"Source-backed boundary target showing which voice-service, avatar, and example-shell seams stay replaceable and outside the shippable first-party HyperTwist embodied companion owner."} diff --git a/UnrealHyperTwist/Source/UnrealHyperTwist/Private/HyperTwistTraining/HyperTwistTrainingCompanionLibrary.cpp b/UnrealHyperTwist/Source/UnrealHyperTwist/Private/HyperTwistTraining/HyperTwistTrainingCompanionLibrary.cpp new file mode 100644 index 0000000..2730e8b --- /dev/null +++ b/UnrealHyperTwist/Source/UnrealHyperTwist/Private/HyperTwistTraining/HyperTwistTrainingCompanionLibrary.cpp @@ -0,0 +1,622 @@ +#include "HyperTwistTraining/HyperTwistTrainingCompanionLibrary.h" + +namespace HyperTwistTrainingCompanionLibraryInternal +{ + FHyperTwistTrainingSourceAttribution MakeAttribution( + const FString& TrackId, + const FString& Notes + ) + { + FHyperTwistTrainingSourceAttribution Attribution; + Attribution.SourceMode = EHyperTwistTrainingSourceMode::DirectDonor; + Attribution.SourceRepo = TEXT("met4citizen/TalkingHead"); + Attribution.SourceLicense = TEXT("MIT"); + Attribution.SourceTrackId = TrackId; + Attribution.SourceNotes = Notes; + return Attribution; + } + + FHyperTwistTrainingCompanionSpeechInputReference MakeSpeechInput( + const FString& InputId, + const FString& Label, + const TArray& InputKinds, + const TArray& ConfigFields, + const FString& Summary, + const FHyperTwistTrainingSourceAttribution& SourceAttribution + ) + { + FHyperTwistTrainingCompanionSpeechInputReference Input; + Input.InputId = InputId; + Input.Label = Label; + Input.InputKinds = InputKinds; + Input.ConfigFields = ConfigFields; + Input.Summary = Summary; + Input.SourceAttribution = SourceAttribution; + return Input; + } + + FHyperTwistTrainingCompanionQueueLifecycleState MakeQueueState( + const FString& StateId, + const FString& Label, + const FString& Trigger, + const FString& OutputSurface, + const TArray& MetricLabels, + const FHyperTwistTrainingSourceAttribution& SourceAttribution + ) + { + FHyperTwistTrainingCompanionQueueLifecycleState State; + State.StateId = StateId; + State.Label = Label; + State.Trigger = Trigger; + State.OutputSurface = OutputSurface; + State.MetricLabels = MetricLabels; + State.SourceAttribution = SourceAttribution; + return State; + } + + FHyperTwistTrainingCompanionSubtitleCueReference MakeSubtitleCueReference( + const FString& CueTemplateId, + const FString& Label, + const TArray& RequiredFields, + const TArray& SyncSignals, + const FHyperTwistTrainingSourceAttribution& SourceAttribution + ) + { + FHyperTwistTrainingCompanionSubtitleCueReference Cue; + Cue.CueTemplateId = CueTemplateId; + Cue.Label = Label; + Cue.RequiredFields = RequiredFields; + Cue.SyncSignals = SyncSignals; + Cue.SourceAttribution = SourceAttribution; + return Cue; + } + + FHyperTwistTrainingCompanionVisemeReference MakeVisemeReference( + const FString& VisemeReferenceId, + const FString& Label, + const TArray& TimingFields, + const TArray& BlendshapeTargets, + const FHyperTwistTrainingSourceAttribution& SourceAttribution + ) + { + FHyperTwistTrainingCompanionVisemeReference Reference; + Reference.VisemeReferenceId = VisemeReferenceId; + Reference.Label = Label; + Reference.TimingFields = TimingFields; + Reference.BlendshapeTargets = BlendshapeTargets; + Reference.SourceAttribution = SourceAttribution; + return Reference; + } + + FHyperTwistTrainingCompanionGesturePresetReference MakeGesturePresetReference( + const FString& GestureId, + const FString& Label, + const FString& Summary, + const TArray& GestureTags, + const TArray& RequiredStateTags, + const FHyperTwistTrainingSourceAttribution& SourceAttribution + ) + { + FHyperTwistTrainingCompanionGesturePresetReference Reference; + Reference.GestureId = GestureId; + Reference.Label = Label; + Reference.Summary = Summary; + Reference.GestureTags = GestureTags; + Reference.RequiredStateTags = RequiredStateTags; + Reference.SourceAttribution = SourceAttribution; + return Reference; + } + + FHyperTwistTrainingCompanionMoodPresetReference MakeMoodPresetReference( + const FString& MoodId, + const FString& Label, + const FString& Summary, + const TArray& ActivationSignals, + const FHyperTwistTrainingSourceAttribution& SourceAttribution + ) + { + FHyperTwistTrainingCompanionMoodPresetReference Reference; + Reference.MoodId = MoodId; + Reference.Label = Label; + Reference.Summary = Summary; + Reference.ActivationSignals = ActivationSignals; + Reference.SourceAttribution = SourceAttribution; + return Reference; + } + + void AppendJoined(FString& OutText, const TArray& Values) + { + for (int32 Index = 0; Index < Values.Num(); ++Index) + { + if (Index > 0) + { + OutText.Append(TEXT(", ")); + } + + OutText.Append(Values[Index]); + } + } +} + +FHyperTwistTrainingCompanionReferenceBundle +UHyperTwistTrainingCompanionLibrary::BuildBundledEmbodiedCompanionReferenceBundle() +{ + using namespace HyperTwistTrainingCompanionLibraryInternal; + + FHyperTwistTrainingCompanionReferenceBundle Bundle; + Bundle.ReferenceUtc = TEXT("2026-05-13T00:00:00Z"); + Bundle.PrimaryNarrationContractId = TEXT("embodied-companion-narration"); + Bundle.PrimaryAvatarEmbedContractId = TEXT("avatar-only-embed"); + Bundle.PrimaryListeningContractId = TEXT("listening-threshold-lifecycle"); + Bundle.PrimaryVendorAdapterBoundaryId = TEXT("tts-and-asset-adapter-boundary"); + + Bundle.SpeechInputs = + { + MakeSpeechInput( + TEXT("speech-input/text-script-and-voice-settings"), + TEXT("Scripted text and voice settings"), + {TEXT("coach-script"), TEXT("voice-parameters"), TEXT("subtitle-seed")}, + { + TEXT("tts-lang"), + TEXT("tts-voice"), + TEXT("tts-rate"), + TEXT("tts-pitch"), + TEXT("tts-volume") + }, + TEXT("Structured narration payload for queued coach speech, subtitle generation, and mood or gesture alignment."), + MakeAttribution( + TEXT("narration-queue"), + TEXT("Preserves text-to-speech queueing, parameterized voice settings, and subtitle-seeded narration behavior from talkinghead.mjs.") + ) + ), + MakeSpeechInput( + TEXT("speech-input/streamed-audio-packets"), + TEXT("Streamed audio packets"), + {TEXT("streamed-audio"), TEXT("viseme-stream"), TEXT("marker-events")}, + { + TEXT("jwt-get"), + TEXT("tts-endpoint"), + TEXT("tts-api-key"), + TEXT("stream-buffer-ms") + }, + TEXT("Streaming speech input for low-latency narration, live viseme scheduling, and queue underrun handling."), + MakeAttribution( + TEXT("streaming-audio"), + TEXT("Preserves low-latency streaming playback, queue buffering, and live viseme alignment from the donor streaming examples and runtime queue.") + ) + ), + MakeSpeechInput( + TEXT("speech-input/audio-marker-overrides"), + TEXT("Audio marker overrides"), + {TEXT("marker-audio"), TEXT("prebuilt-audio"), TEXT("gesture-sync")}, + { + TEXT("marker-id"), + TEXT("audio-offset-ms"), + TEXT("viseme-offset-ms"), + TEXT("gesture-cue-id") + }, + TEXT("Audio-marker input for externally prepared clips, marker callbacks, and deterministic gesture or subtitle sync."), + MakeAttribution( + TEXT("audio-markers"), + TEXT("Preserves speakAudio, speakMarker, and marker-aligned callback behavior from the donor narration queue.") + ) + ) + }; + + Bundle.QueueLifecycleStates = + { + MakeQueueState( + TEXT("queue/ready"), + TEXT("Ready"), + TEXT("avatar is loaded and no narration item is active"), + TEXT("companion ready surface"), + {TEXT("queue-depth"), TEXT("avatar-ready"), TEXT("voice-route-ready")}, + MakeAttribution( + TEXT("queue-ready"), + TEXT("Preserves the donor's idle-ready posture before narration or listening begins.") + ) + ), + MakeQueueState( + TEXT("queue/speaking"), + TEXT("Speaking"), + TEXT("queued narration or audio playback is active"), + TEXT("speech, subtitle, and viseme surface"), + {TEXT("queue-depth"), TEXT("subtitle-cue-count"), TEXT("viseme-frame-count")}, + MakeAttribution( + TEXT("queue-speaking"), + TEXT("Preserves queued speech playback, subtitle timing, and viseme emission behavior from talkinghead.mjs.") + ) + ), + MakeQueueState( + TEXT("queue/streaming"), + TEXT("Streaming"), + TEXT("audio stream packets are still arriving while playback is active"), + TEXT("streaming playback surface"), + {TEXT("stream-buffer-ms"), TEXT("underrun-count"), TEXT("pending-chunk-count")}, + MakeAttribution( + TEXT("queue-streaming"), + TEXT("Preserves live streaming, audio buffering, and underrun-aware queue handling from the donor streaming runtime.") + ) + ), + MakeQueueState( + TEXT("queue/listening"), + TEXT("Listening"), + TEXT("narration is paused or complete and microphone capture is active"), + TEXT("speech-input and listening surface"), + {TEXT("energy-threshold"), TEXT("speech-start-ms"), TEXT("speech-end-ms")}, + MakeAttribution( + TEXT("queue-listening"), + TEXT("Preserves listening lifecycle, threshold gating, and microphone-state expectations from the donor runtime.") + ) + ) + }; + + FHyperTwistTrainingCompanionNarrationContract NarrationContract; + NarrationContract.ContractId = TEXT("embodied-companion-narration"); + NarrationContract.Title = TEXT("Embodied companion narration contract"); + NarrationContract.Summary = TEXT("First-party coach narration boundary for queued speech, streaming playback, viseme alignment, subtitles, markers, and coach-driven gesture or mood cues."); + NarrationContract.SupportedSpeechInputIds = + { + TEXT("speech-input/text-script-and-voice-settings"), + TEXT("speech-input/streamed-audio-packets"), + TEXT("speech-input/audio-marker-overrides") + }; + NarrationContract.QueueLifecycleStateIds = + { + TEXT("queue/ready"), + TEXT("queue/speaking"), + TEXT("queue/streaming"), + TEXT("queue/listening") + }; + NarrationContract.OutputSurfaceTags = + { + TEXT("audio-playback"), + TEXT("subtitle-sync"), + TEXT("viseme-envelope"), + TEXT("marker-callback"), + TEXT("gesture-cue"), + TEXT("mood-cue") + }; + NarrationContract.ExplicitExclusions = + { + TEXT("external TTS vendor product shell"), + TEXT("sample avatar picker UI"), + TEXT("donor example page chrome"), + TEXT("generic speech-assistant platform ownership") + }; + NarrationContract.SourceAttribution = MakeAttribution( + TEXT("narration-contract"), + TEXT("Preserves queued narration, subtitle synchronization, viseme timing, and gesture-aware coach speech behavior from the retained TalkingHead lane.") + ); + Bundle.NarrationContracts = {NarrationContract}; + + Bundle.SubtitleCueReferences = + { + MakeSubtitleCueReference( + TEXT("subtitle/inline-word-cues"), + TEXT("Inline word subtitle cues"), + {TEXT("cue-id"), TEXT("start-ms"), TEXT("end-ms"), TEXT("text"), TEXT("emphasis-tags")}, + {TEXT("audio-playhead"), TEXT("word-boundary"), TEXT("gesture-cue")}, + MakeAttribution( + TEXT("subtitle-inline"), + TEXT("Preserves word-level subtitle timing and emphasis alignment from the donor queue and lipsync modules.") + ) + ), + MakeSubtitleCueReference( + TEXT("subtitle/marker-and-viseme-sync"), + TEXT("Marker and viseme synchronized subtitles"), + {TEXT("marker-id"), TEXT("caption-span"), TEXT("audio-offset-ms"), TEXT("viseme-offset-ms")}, + {TEXT("marker-callback"), TEXT("viseme-envelope"), TEXT("stream-chunk")}, + MakeAttribution( + TEXT("subtitle-markers"), + TEXT("Preserves subtitle, marker, and viseme co-scheduling behavior from streamed and prebuilt donor audio paths.") + ) + ) + }; + + Bundle.VisemeReferences = + { + MakeVisemeReference( + TEXT("viseme/blendshape-envelope"), + TEXT("Blendshape viseme envelope"), + {TEXT("start-ms"), TEXT("end-ms"), TEXT("viseme-id"), TEXT("weight")}, + {TEXT("aa"), TEXT("oh"), TEXT("ee"), TEXT("sil"), TEXT("blink")}, + MakeAttribution( + TEXT("viseme-envelope"), + TEXT("Preserves blendshape-target viseme timing and envelope semantics from the donor lipsync modules.") + ) + ), + MakeVisemeReference( + TEXT("viseme/stream-frame"), + TEXT("Streaming viseme frame"), + {TEXT("chunk-index"), TEXT("frame-time-ms"), TEXT("viseme-id"), TEXT("strength")}, + {TEXT("aa"), TEXT("oh"), TEXT("ee"), TEXT("sil")}, + MakeAttribution( + TEXT("viseme-stream"), + TEXT("Preserves live streaming viseme-frame scheduling from the donor audio-streaming pathway.") + ) + ) + }; + + Bundle.GesturePresets = + { + MakeGesturePresetReference( + TEXT("gesture/acknowledge"), + TEXT("Acknowledge"), + TEXT("Compact acknowledgement motion used when the coach confirms a learner action or successful state."), + {TEXT("confirmation"), TEXT("micro-gesture"), TEXT("coach-feedback")}, + {TEXT("avatar-ready"), TEXT("gesture-enabled")}, + MakeAttribution( + TEXT("gesture-acknowledge"), + TEXT("Preserves gesture-trigger behavior and compact coach presentation patterns from the donor runtime.") + ) + ), + MakeGesturePresetReference( + TEXT("gesture/focus-point"), + TEXT("Focus point"), + TEXT("Pointing or emphasis gesture used when the coach highlights a case detail, scene element, or training target."), + {TEXT("focus"), TEXT("pointing"), TEXT("scene-callout")}, + {TEXT("avatar-ready"), TEXT("scene-anchor-available")}, + MakeAttribution( + TEXT("gesture-focus"), + TEXT("Preserves pointing and focus-callout choreography from the donor gesture and pose orchestration surfaces.") + ) + ), + MakeGesturePresetReference( + TEXT("gesture/celebrate"), + TEXT("Celebrate"), + TEXT("Positive coach gesture used for completion, personal-best moments, or successful recognition review."), + {TEXT("celebration"), TEXT("completion"), TEXT("positive-feedback")}, + {TEXT("avatar-ready"), TEXT("gesture-enabled")}, + MakeAttribution( + TEXT("gesture-celebrate"), + TEXT("Preserves celebratory motion and timed coach feedback patterns from the donor animation surface.") + ) + ) + }; + + Bundle.MoodPresets = + { + MakeMoodPresetReference( + TEXT("mood/neutral"), + TEXT("Neutral"), + TEXT("Default coach presence for passive review, playback, and non-interruptive idle states."), + {TEXT("idle"), TEXT("reset"), TEXT("no-guidance-escalation")}, + MakeAttribution( + TEXT("mood-neutral"), + TEXT("Preserves avatar mood-state defaults and reset behavior from talkinghead.mjs.") + ) + ), + MakeMoodPresetReference( + TEXT("mood/focused"), + TEXT("Focused"), + TEXT("Concentrated coach presence for error correction, inspection, and case-specific guidance."), + {TEXT("analysis"), TEXT("error-review"), TEXT("focus-callout")}, + MakeAttribution( + TEXT("mood-focused"), + TEXT("Preserves focused pose and expression switching for inspection-heavy coaching states.") + ) + ), + MakeMoodPresetReference( + TEXT("mood/encouraging"), + TEXT("Encouraging"), + TEXT("Positive coach presence for affirmation, milestone completion, and motivational guidance."), + {TEXT("success"), TEXT("encouragement"), TEXT("completion")}, + MakeAttribution( + TEXT("mood-encouraging"), + TEXT("Preserves positive mood and encouragement state changes from the donor avatar presentation layer.") + ) + ) + }; + + FHyperTwistTrainingCompanionAvatarEmbedContract EmbedContract; + EmbedContract.ContractId = TEXT("avatar-only-embed"); + EmbedContract.Title = TEXT("Avatar-only embed contract"); + EmbedContract.Summary = TEXT("First-party external-scene avatar boundary for coach presence, camera-safe embedding, retargeted motion, and companion overlays without inheriting the donor demo shell."); + EmbedContract.RequiredStateTags = + { + TEXT("avatar-only"), + TEXT("external-scene"), + TEXT("external-camera"), + TEXT("retargeting-ready"), + TEXT("transparent-background-ready") + }; + EmbedContract.SceneBindingFields = + { + TEXT("scene-root"), + TEXT("avatar-anchor"), + TEXT("lighting-profile"), + TEXT("posture-anchor"), + TEXT("subtitle-anchor") + }; + EmbedContract.CameraBindingFields = + { + TEXT("camera-target"), + TEXT("camera-orbit"), + TEXT("field-of-view"), + TEXT("framing-policy"), + TEXT("distance-bias") + }; + EmbedContract.SupportedGestureIds = + { + TEXT("gesture/acknowledge"), + TEXT("gesture/focus-point"), + TEXT("gesture/celebrate") + }; + EmbedContract.SupportedMoodIds = + { + TEXT("mood/neutral"), + TEXT("mood/focused"), + TEXT("mood/encouraging") + }; + EmbedContract.ExplicitExclusions = + { + TEXT("donor demo shell"), + TEXT("sample avatar bundles"), + TEXT("donor camera-page assumptions"), + TEXT("generic character-platform ownership") + }; + EmbedContract.SourceAttribution = MakeAttribution( + TEXT("avatar-only-embedding"), + TEXT("Preserves avatarOnly external-scene embedding, camera-safe composition, and retargeting-aware companion presence from the retained TalkingHead lane.") + ); + Bundle.AvatarEmbedContracts = {EmbedContract}; + + FHyperTwistTrainingCompanionListeningContract ListeningContract; + ListeningContract.ContractId = TEXT("listening-threshold-lifecycle"); + ListeningContract.Title = TEXT("Listening threshold and lifecycle contract"); + ListeningContract.Summary = TEXT("First-party speech-input contract for microphone activation, silence gating, queue handoff, and coach listening readiness beneath the companion lane."); + ListeningContract.StartConditions = + { + TEXT("microphone-permission-granted"), + TEXT("narration-queue-empty-or-paused"), + TEXT("vad-ready") + }; + ListeningContract.StopConditions = + { + TEXT("silence-timeout"), + TEXT("manual-stop"), + TEXT("speech-commit"), + TEXT("narration-resume") + }; + ListeningContract.ThresholdFields = + { + TEXT("energy-threshold"), + TEXT("speech-start-ms"), + TEXT("speech-end-ms"), + TEXT("silence-gap-ms") + }; + ListeningContract.MetricLabels = + { + TEXT("energy-threshold"), + TEXT("speech-duration-ms"), + TEXT("queue-underrun-count"), + TEXT("stream-buffer-ms") + }; + ListeningContract.SourceAttribution = MakeAttribution( + TEXT("listening-thresholds"), + TEXT("Preserves listening thresholds, speech detection timing, and queue handoff behavior from the donor runtime.") + ); + Bundle.ListeningContracts = {ListeningContract}; + + FHyperTwistTrainingCompanionVendorAdapterBoundary Boundary; + Boundary.BoundaryId = TEXT("tts-and-asset-adapter-boundary"); + Boundary.Title = TEXT("TTS and asset adapter boundary"); + Boundary.Summary = TEXT("Separates shippable first-party companion behavior from donor example pages, sample avatar assumptions, and external TTS or CDN wiring."); + Boundary.ReplaceableVendorFields = + { + TEXT("jwt-get"), + TEXT("tts-endpoint"), + TEXT("tts-api-key"), + TEXT("avatar-uri"), + TEXT("audio-stream-provider") + }; + Boundary.FirstPartyOwnedFields = + { + TEXT("coach-script"), + TEXT("subtitle-text"), + TEXT("mood-policy"), + TEXT("gesture-policy"), + TEXT("session-cues"), + TEXT("audio-route-policy") + }; + Boundary.DemoOnlyBehaviors = + { + TEXT("sample avatar picker"), + TEXT("vendor-specific tutorial pages"), + TEXT("donor example-site framing"), + TEXT("direct third-party service marketing copy") + }; + Boundary.SourceAttribution = MakeAttribution( + TEXT("adapter-boundary"), + TEXT("Preserves configurable vendor and asset seams while keeping voice-service wiring, sample avatars, and donor demo framing outside the shippable companion owner.") + ); + Bundle.VendorAdapterBoundaries = {Boundary}; + + return Bundle; +} + +bool UHyperTwistTrainingCompanionLibrary::TryGetNarrationContractById( + const FHyperTwistTrainingCompanionReferenceBundle& Bundle, + const FString& ContractId, + FHyperTwistTrainingCompanionNarrationContract& OutContract +) +{ + for (const FHyperTwistTrainingCompanionNarrationContract& Contract : Bundle.NarrationContracts) + { + if (Contract.ContractId.Equals(ContractId, ESearchCase::IgnoreCase)) + { + OutContract = Contract; + return true; + } + } + + OutContract = FHyperTwistTrainingCompanionNarrationContract(); + return false; +} + +bool UHyperTwistTrainingCompanionLibrary::TryGetAvatarEmbedContractById( + const FHyperTwistTrainingCompanionReferenceBundle& Bundle, + const FString& ContractId, + FHyperTwistTrainingCompanionAvatarEmbedContract& OutContract +) +{ + for (const FHyperTwistTrainingCompanionAvatarEmbedContract& Contract : Bundle.AvatarEmbedContracts) + { + if (Contract.ContractId.Equals(ContractId, ESearchCase::IgnoreCase)) + { + OutContract = Contract; + return true; + } + } + + OutContract = FHyperTwistTrainingCompanionAvatarEmbedContract(); + return false; +} + +bool UHyperTwistTrainingCompanionLibrary::TryGetVendorAdapterBoundaryById( + const FHyperTwistTrainingCompanionReferenceBundle& Bundle, + const FString& BoundaryId, + FHyperTwistTrainingCompanionVendorAdapterBoundary& OutBoundary +) +{ + for (const FHyperTwistTrainingCompanionVendorAdapterBoundary& Boundary : Bundle.VendorAdapterBoundaries) + { + if (Boundary.BoundaryId.Equals(BoundaryId, ESearchCase::IgnoreCase)) + { + OutBoundary = Boundary; + return true; + } + } + + OutBoundary = FHyperTwistTrainingCompanionVendorAdapterBoundary(); + return false; +} + +FString UHyperTwistTrainingCompanionLibrary::BuildSubtitleCueChecklistTsv( + const FHyperTwistTrainingCompanionReferenceBundle& Bundle +) +{ + using namespace HyperTwistTrainingCompanionLibraryInternal; + + FString Output = TEXT("CueTemplateId\tLabel\tRequiredFields\tSyncSignals\tSourceRepo\n"); + for (const FHyperTwistTrainingCompanionSubtitleCueReference& Cue : Bundle.SubtitleCueReferences) + { + FString RequiredFields; + AppendJoined(RequiredFields, Cue.RequiredFields); + + FString SyncSignals; + AppendJoined(SyncSignals, Cue.SyncSignals); + + Output.Appendf( + TEXT("%s\t%s\t%s\t%s\t%s\n"), + *Cue.CueTemplateId, + *Cue.Label, + *RequiredFields, + *SyncSignals, + *Cue.SourceAttribution.SourceRepo + ); + } + + return Output; +} diff --git a/UnrealHyperTwist/Source/UnrealHyperTwist/Private/HyperTwistTraining/HyperTwistTrainingRuntimeLibrary.cpp b/UnrealHyperTwist/Source/UnrealHyperTwist/Private/HyperTwistTraining/HyperTwistTrainingRuntimeLibrary.cpp index bd704ab..2dfe72a 100644 --- a/UnrealHyperTwist/Source/UnrealHyperTwist/Private/HyperTwistTraining/HyperTwistTrainingRuntimeLibrary.cpp +++ b/UnrealHyperTwist/Source/UnrealHyperTwist/Private/HyperTwistTraining/HyperTwistTrainingRuntimeLibrary.cpp @@ -469,6 +469,12 @@ FHyperTwistTrainingViewerReferenceBundle UHyperTwistTrainingRuntimeLibrary::GetB return UHyperTwistTrainingViewerLibrary::BuildBundledBrowserViewerReferenceBundle(); } +FHyperTwistTrainingCompanionReferenceBundle +UHyperTwistTrainingRuntimeLibrary::GetBundledEmbodiedCompanionReferenceBundle() +{ + return UHyperTwistTrainingCompanionLibrary::BuildBundledEmbodiedCompanionReferenceBundle(); +} + bool UHyperTwistTrainingRuntimeLibrary::TryGetLatestGeneratedModeLaunchRequestForDeck( UObject* WorldContextObject, const FString& UserId, @@ -667,6 +673,49 @@ FString UHyperTwistTrainingRuntimeLibrary::BuildBundledBrowserViewerQaChecklistT return UHyperTwistTrainingViewerLibrary::BuildQaChecklistTsv(GetBundledBrowserViewerReferenceBundle()); } +bool UHyperTwistTrainingRuntimeLibrary::TryGetBundledEmbodiedCompanionNarrationContract( + const FString& ContractId, + FHyperTwistTrainingCompanionNarrationContract& OutContract +) +{ + return UHyperTwistTrainingCompanionLibrary::TryGetNarrationContractById( + GetBundledEmbodiedCompanionReferenceBundle(), + ContractId, + OutContract + ); +} + +bool UHyperTwistTrainingRuntimeLibrary::TryGetBundledEmbodiedCompanionAvatarEmbedContract( + const FString& ContractId, + FHyperTwistTrainingCompanionAvatarEmbedContract& OutContract +) +{ + return UHyperTwistTrainingCompanionLibrary::TryGetAvatarEmbedContractById( + GetBundledEmbodiedCompanionReferenceBundle(), + ContractId, + OutContract + ); +} + +bool UHyperTwistTrainingRuntimeLibrary::TryGetBundledEmbodiedCompanionVendorAdapterBoundary( + const FString& BoundaryId, + FHyperTwistTrainingCompanionVendorAdapterBoundary& OutBoundary +) +{ + return UHyperTwistTrainingCompanionLibrary::TryGetVendorAdapterBoundaryById( + GetBundledEmbodiedCompanionReferenceBundle(), + BoundaryId, + OutBoundary + ); +} + +FString UHyperTwistTrainingRuntimeLibrary::BuildBundledEmbodiedCompanionSubtitleCueChecklistTsv() +{ + return UHyperTwistTrainingCompanionLibrary::BuildSubtitleCueChecklistTsv( + GetBundledEmbodiedCompanionReferenceBundle() + ); +} + FHyperTwistTrainingLearnerDeckStateSummary UHyperTwistTrainingRuntimeLibrary::GetActiveTrainingLearnerDeckStateSummary(UObject* WorldContextObject) { if (UHyperTwistTrainingSubsystem* TrainingSubsystem = GetTrainingSubsystem(WorldContextObject)) diff --git a/UnrealHyperTwist/Source/UnrealHyperTwist/Public/HyperTwistTraining/HyperTwistTrainingCompanionLibrary.h b/UnrealHyperTwist/Source/UnrealHyperTwist/Public/HyperTwistTraining/HyperTwistTrainingCompanionLibrary.h new file mode 100644 index 0000000..2ef46bd --- /dev/null +++ b/UnrealHyperTwist/Source/UnrealHyperTwist/Public/HyperTwistTraining/HyperTwistTrainingCompanionLibrary.h @@ -0,0 +1,405 @@ +#pragma once + +#include "CoreMinimal.h" +#include "Kismet/BlueprintFunctionLibrary.h" +#include "HyperTwistTraining/HyperTwistTrainingTypes.h" +#include "HyperTwistTrainingCompanionLibrary.generated.h" + +USTRUCT(BlueprintType) +struct FHyperTwistTrainingCompanionSpeechInputReference +{ + GENERATED_BODY() + + UPROPERTY(EditAnywhere, BlueprintReadWrite, Category = "HyperTwist") + FString InputId; + + UPROPERTY(EditAnywhere, BlueprintReadWrite, Category = "HyperTwist") + FString Label; + + UPROPERTY(EditAnywhere, BlueprintReadWrite, Category = "HyperTwist") + TArray InputKinds; + + UPROPERTY(EditAnywhere, BlueprintReadWrite, Category = "HyperTwist") + TArray ConfigFields; + + UPROPERTY(EditAnywhere, BlueprintReadWrite, Category = "HyperTwist") + FString Summary; + + UPROPERTY(EditAnywhere, BlueprintReadWrite, Category = "HyperTwist") + FHyperTwistTrainingSourceAttribution SourceAttribution; + + bool IsStructurallyValid() const + { + return !InputId.IsEmpty() && !Label.IsEmpty() && SourceAttribution.IsStructurallyValid(); + } +}; + +USTRUCT(BlueprintType) +struct FHyperTwistTrainingCompanionQueueLifecycleState +{ + GENERATED_BODY() + + UPROPERTY(EditAnywhere, BlueprintReadWrite, Category = "HyperTwist") + FString StateId; + + UPROPERTY(EditAnywhere, BlueprintReadWrite, Category = "HyperTwist") + FString Label; + + UPROPERTY(EditAnywhere, BlueprintReadWrite, Category = "HyperTwist") + FString Trigger; + + UPROPERTY(EditAnywhere, BlueprintReadWrite, Category = "HyperTwist") + FString OutputSurface; + + UPROPERTY(EditAnywhere, BlueprintReadWrite, Category = "HyperTwist") + TArray MetricLabels; + + UPROPERTY(EditAnywhere, BlueprintReadWrite, Category = "HyperTwist") + FHyperTwistTrainingSourceAttribution SourceAttribution; + + bool IsStructurallyValid() const + { + return !StateId.IsEmpty() && !Label.IsEmpty() && SourceAttribution.IsStructurallyValid(); + } +}; + +USTRUCT(BlueprintType) +struct FHyperTwistTrainingCompanionNarrationContract +{ + GENERATED_BODY() + + UPROPERTY(EditAnywhere, BlueprintReadWrite, Category = "HyperTwist") + FString ContractId; + + UPROPERTY(EditAnywhere, BlueprintReadWrite, Category = "HyperTwist") + FString Title; + + UPROPERTY(EditAnywhere, BlueprintReadWrite, Category = "HyperTwist") + FString Summary; + + UPROPERTY(EditAnywhere, BlueprintReadWrite, Category = "HyperTwist") + TArray SupportedSpeechInputIds; + + UPROPERTY(EditAnywhere, BlueprintReadWrite, Category = "HyperTwist") + TArray QueueLifecycleStateIds; + + UPROPERTY(EditAnywhere, BlueprintReadWrite, Category = "HyperTwist") + TArray OutputSurfaceTags; + + UPROPERTY(EditAnywhere, BlueprintReadWrite, Category = "HyperTwist") + TArray ExplicitExclusions; + + UPROPERTY(EditAnywhere, BlueprintReadWrite, Category = "HyperTwist") + FHyperTwistTrainingSourceAttribution SourceAttribution; + + bool IsStructurallyValid() const + { + return !ContractId.IsEmpty() && !Title.IsEmpty() && SourceAttribution.IsStructurallyValid(); + } +}; + +USTRUCT(BlueprintType) +struct FHyperTwistTrainingCompanionSubtitleCueReference +{ + GENERATED_BODY() + + UPROPERTY(EditAnywhere, BlueprintReadWrite, Category = "HyperTwist") + FString CueTemplateId; + + UPROPERTY(EditAnywhere, BlueprintReadWrite, Category = "HyperTwist") + FString Label; + + UPROPERTY(EditAnywhere, BlueprintReadWrite, Category = "HyperTwist") + TArray RequiredFields; + + UPROPERTY(EditAnywhere, BlueprintReadWrite, Category = "HyperTwist") + TArray SyncSignals; + + UPROPERTY(EditAnywhere, BlueprintReadWrite, Category = "HyperTwist") + FHyperTwistTrainingSourceAttribution SourceAttribution; + + bool IsStructurallyValid() const + { + return !CueTemplateId.IsEmpty() && !Label.IsEmpty() && SourceAttribution.IsStructurallyValid(); + } +}; + +USTRUCT(BlueprintType) +struct FHyperTwistTrainingCompanionVisemeReference +{ + GENERATED_BODY() + + UPROPERTY(EditAnywhere, BlueprintReadWrite, Category = "HyperTwist") + FString VisemeReferenceId; + + UPROPERTY(EditAnywhere, BlueprintReadWrite, Category = "HyperTwist") + FString Label; + + UPROPERTY(EditAnywhere, BlueprintReadWrite, Category = "HyperTwist") + TArray TimingFields; + + UPROPERTY(EditAnywhere, BlueprintReadWrite, Category = "HyperTwist") + TArray BlendshapeTargets; + + UPROPERTY(EditAnywhere, BlueprintReadWrite, Category = "HyperTwist") + FHyperTwistTrainingSourceAttribution SourceAttribution; + + bool IsStructurallyValid() const + { + return !VisemeReferenceId.IsEmpty() && !Label.IsEmpty() && SourceAttribution.IsStructurallyValid(); + } +}; + +USTRUCT(BlueprintType) +struct FHyperTwistTrainingCompanionGesturePresetReference +{ + GENERATED_BODY() + + UPROPERTY(EditAnywhere, BlueprintReadWrite, Category = "HyperTwist") + FString GestureId; + + UPROPERTY(EditAnywhere, BlueprintReadWrite, Category = "HyperTwist") + FString Label; + + UPROPERTY(EditAnywhere, BlueprintReadWrite, Category = "HyperTwist") + FString Summary; + + UPROPERTY(EditAnywhere, BlueprintReadWrite, Category = "HyperTwist") + TArray GestureTags; + + UPROPERTY(EditAnywhere, BlueprintReadWrite, Category = "HyperTwist") + TArray RequiredStateTags; + + UPROPERTY(EditAnywhere, BlueprintReadWrite, Category = "HyperTwist") + FHyperTwistTrainingSourceAttribution SourceAttribution; + + bool IsStructurallyValid() const + { + return !GestureId.IsEmpty() && !Label.IsEmpty() && SourceAttribution.IsStructurallyValid(); + } +}; + +USTRUCT(BlueprintType) +struct FHyperTwistTrainingCompanionMoodPresetReference +{ + GENERATED_BODY() + + UPROPERTY(EditAnywhere, BlueprintReadWrite, Category = "HyperTwist") + FString MoodId; + + UPROPERTY(EditAnywhere, BlueprintReadWrite, Category = "HyperTwist") + FString Label; + + UPROPERTY(EditAnywhere, BlueprintReadWrite, Category = "HyperTwist") + FString Summary; + + UPROPERTY(EditAnywhere, BlueprintReadWrite, Category = "HyperTwist") + TArray ActivationSignals; + + UPROPERTY(EditAnywhere, BlueprintReadWrite, Category = "HyperTwist") + FHyperTwistTrainingSourceAttribution SourceAttribution; + + bool IsStructurallyValid() const + { + return !MoodId.IsEmpty() && !Label.IsEmpty() && SourceAttribution.IsStructurallyValid(); + } +}; + +USTRUCT(BlueprintType) +struct FHyperTwistTrainingCompanionAvatarEmbedContract +{ + GENERATED_BODY() + + UPROPERTY(EditAnywhere, BlueprintReadWrite, Category = "HyperTwist") + FString ContractId; + + UPROPERTY(EditAnywhere, BlueprintReadWrite, Category = "HyperTwist") + FString Title; + + UPROPERTY(EditAnywhere, BlueprintReadWrite, Category = "HyperTwist") + FString Summary; + + UPROPERTY(EditAnywhere, BlueprintReadWrite, Category = "HyperTwist") + TArray RequiredStateTags; + + UPROPERTY(EditAnywhere, BlueprintReadWrite, Category = "HyperTwist") + TArray SceneBindingFields; + + UPROPERTY(EditAnywhere, BlueprintReadWrite, Category = "HyperTwist") + TArray CameraBindingFields; + + UPROPERTY(EditAnywhere, BlueprintReadWrite, Category = "HyperTwist") + TArray SupportedGestureIds; + + UPROPERTY(EditAnywhere, BlueprintReadWrite, Category = "HyperTwist") + TArray SupportedMoodIds; + + UPROPERTY(EditAnywhere, BlueprintReadWrite, Category = "HyperTwist") + TArray ExplicitExclusions; + + UPROPERTY(EditAnywhere, BlueprintReadWrite, Category = "HyperTwist") + FHyperTwistTrainingSourceAttribution SourceAttribution; + + bool IsStructurallyValid() const + { + return !ContractId.IsEmpty() && !Title.IsEmpty() && SourceAttribution.IsStructurallyValid(); + } +}; + +USTRUCT(BlueprintType) +struct FHyperTwistTrainingCompanionListeningContract +{ + GENERATED_BODY() + + UPROPERTY(EditAnywhere, BlueprintReadWrite, Category = "HyperTwist") + FString ContractId; + + UPROPERTY(EditAnywhere, BlueprintReadWrite, Category = "HyperTwist") + FString Title; + + UPROPERTY(EditAnywhere, BlueprintReadWrite, Category = "HyperTwist") + FString Summary; + + UPROPERTY(EditAnywhere, BlueprintReadWrite, Category = "HyperTwist") + TArray StartConditions; + + UPROPERTY(EditAnywhere, BlueprintReadWrite, Category = "HyperTwist") + TArray StopConditions; + + UPROPERTY(EditAnywhere, BlueprintReadWrite, Category = "HyperTwist") + TArray ThresholdFields; + + UPROPERTY(EditAnywhere, BlueprintReadWrite, Category = "HyperTwist") + TArray MetricLabels; + + UPROPERTY(EditAnywhere, BlueprintReadWrite, Category = "HyperTwist") + FHyperTwistTrainingSourceAttribution SourceAttribution; + + bool IsStructurallyValid() const + { + return !ContractId.IsEmpty() && !Title.IsEmpty() && SourceAttribution.IsStructurallyValid(); + } +}; + +USTRUCT(BlueprintType) +struct FHyperTwistTrainingCompanionVendorAdapterBoundary +{ + GENERATED_BODY() + + UPROPERTY(EditAnywhere, BlueprintReadWrite, Category = "HyperTwist") + FString BoundaryId; + + UPROPERTY(EditAnywhere, BlueprintReadWrite, Category = "HyperTwist") + FString Title; + + UPROPERTY(EditAnywhere, BlueprintReadWrite, Category = "HyperTwist") + FString Summary; + + UPROPERTY(EditAnywhere, BlueprintReadWrite, Category = "HyperTwist") + TArray ReplaceableVendorFields; + + UPROPERTY(EditAnywhere, BlueprintReadWrite, Category = "HyperTwist") + TArray FirstPartyOwnedFields; + + UPROPERTY(EditAnywhere, BlueprintReadWrite, Category = "HyperTwist") + TArray DemoOnlyBehaviors; + + UPROPERTY(EditAnywhere, BlueprintReadWrite, Category = "HyperTwist") + FHyperTwistTrainingSourceAttribution SourceAttribution; + + bool IsStructurallyValid() const + { + return !BoundaryId.IsEmpty() && !Title.IsEmpty() && SourceAttribution.IsStructurallyValid(); + } +}; + +USTRUCT(BlueprintType) +struct FHyperTwistTrainingCompanionReferenceBundle +{ + GENERATED_BODY() + + UPROPERTY(EditAnywhere, BlueprintReadWrite, Category = "HyperTwist") + FString ReferenceUtc; + + UPROPERTY(EditAnywhere, BlueprintReadWrite, Category = "HyperTwist") + FString PrimaryNarrationContractId; + + UPROPERTY(EditAnywhere, BlueprintReadWrite, Category = "HyperTwist") + FString PrimaryAvatarEmbedContractId; + + UPROPERTY(EditAnywhere, BlueprintReadWrite, Category = "HyperTwist") + FString PrimaryListeningContractId; + + UPROPERTY(EditAnywhere, BlueprintReadWrite, Category = "HyperTwist") + FString PrimaryVendorAdapterBoundaryId; + + UPROPERTY(EditAnywhere, BlueprintReadWrite, Category = "HyperTwist") + TArray SpeechInputs; + + UPROPERTY(EditAnywhere, BlueprintReadWrite, Category = "HyperTwist") + TArray QueueLifecycleStates; + + UPROPERTY(EditAnywhere, BlueprintReadWrite, Category = "HyperTwist") + TArray NarrationContracts; + + UPROPERTY(EditAnywhere, BlueprintReadWrite, Category = "HyperTwist") + TArray SubtitleCueReferences; + + UPROPERTY(EditAnywhere, BlueprintReadWrite, Category = "HyperTwist") + TArray VisemeReferences; + + UPROPERTY(EditAnywhere, BlueprintReadWrite, Category = "HyperTwist") + TArray GesturePresets; + + UPROPERTY(EditAnywhere, BlueprintReadWrite, Category = "HyperTwist") + TArray MoodPresets; + + UPROPERTY(EditAnywhere, BlueprintReadWrite, Category = "HyperTwist") + TArray AvatarEmbedContracts; + + UPROPERTY(EditAnywhere, BlueprintReadWrite, Category = "HyperTwist") + TArray ListeningContracts; + + UPROPERTY(EditAnywhere, BlueprintReadWrite, Category = "HyperTwist") + TArray VendorAdapterBoundaries; + + bool IsStructurallyValid() const + { + return !PrimaryNarrationContractId.IsEmpty() && !PrimaryAvatarEmbedContractId.IsEmpty() + && SpeechInputs.Num() > 0 && NarrationContracts.Num() > 0 && AvatarEmbedContracts.Num() > 0; + } +}; + +UCLASS() +class UNREALHYPERTWIST_API UHyperTwistTrainingCompanionLibrary : public UBlueprintFunctionLibrary +{ + GENERATED_BODY() + +public: + UFUNCTION(BlueprintPure, Category = "HyperTwist|Training|Companion") + static FHyperTwistTrainingCompanionReferenceBundle BuildBundledEmbodiedCompanionReferenceBundle(); + + UFUNCTION(BlueprintCallable, Category = "HyperTwist|Training|Companion") + static bool TryGetNarrationContractById( + const FHyperTwistTrainingCompanionReferenceBundle& Bundle, + const FString& ContractId, + FHyperTwistTrainingCompanionNarrationContract& OutContract + ); + + UFUNCTION(BlueprintCallable, Category = "HyperTwist|Training|Companion") + static bool TryGetAvatarEmbedContractById( + const FHyperTwistTrainingCompanionReferenceBundle& Bundle, + const FString& ContractId, + FHyperTwistTrainingCompanionAvatarEmbedContract& OutContract + ); + + UFUNCTION(BlueprintCallable, Category = "HyperTwist|Training|Companion") + static bool TryGetVendorAdapterBoundaryById( + const FHyperTwistTrainingCompanionReferenceBundle& Bundle, + const FString& BoundaryId, + FHyperTwistTrainingCompanionVendorAdapterBoundary& OutBoundary + ); + + UFUNCTION(BlueprintPure, Category = "HyperTwist|Training|Companion") + static FString BuildSubtitleCueChecklistTsv(const FHyperTwistTrainingCompanionReferenceBundle& Bundle); +}; diff --git a/UnrealHyperTwist/Source/UnrealHyperTwist/Public/HyperTwistTraining/HyperTwistTrainingRuntimeLibrary.h b/UnrealHyperTwist/Source/UnrealHyperTwist/Public/HyperTwistTraining/HyperTwistTrainingRuntimeLibrary.h index 6a2692d..8586bab 100644 --- a/UnrealHyperTwist/Source/UnrealHyperTwist/Public/HyperTwistTraining/HyperTwistTrainingRuntimeLibrary.h +++ b/UnrealHyperTwist/Source/UnrealHyperTwist/Public/HyperTwistTraining/HyperTwistTrainingRuntimeLibrary.h @@ -5,6 +5,7 @@ #include "HyperTwistRecognition/HyperTwistRecognitionReplayLibrary.h" #include "HyperTwistReplay/HyperTwistReplayReviewLibrary.h" #include "HyperTwistTraining/HyperTwistTrainingAnalyticsLibrary.h" +#include "HyperTwistTraining/HyperTwistTrainingCompanionLibrary.h" #include "HyperTwistTraining/HyperTwistTrainingCoachLibrary.h" #include "HyperTwistTraining/HyperTwistTrainingKnowledgeLibrary.h" #include "HyperTwistTraining/HyperTwistTrainingViewerLibrary.h" @@ -152,6 +153,9 @@ public: UFUNCTION(BlueprintPure, Category = "HyperTwist|Training|Viewer") static FHyperTwistTrainingViewerReferenceBundle GetBundledBrowserViewerReferenceBundle(); + UFUNCTION(BlueprintPure, Category = "HyperTwist|Training|Companion") + static FHyperTwistTrainingCompanionReferenceBundle GetBundledEmbodiedCompanionReferenceBundle(); + UFUNCTION(BlueprintCallable, Category = "HyperTwist|Training", meta = (WorldContext = "WorldContextObject")) static bool TryGetLatestGeneratedModeLaunchRequestForDeck( UObject* WorldContextObject, @@ -227,6 +231,27 @@ public: UFUNCTION(BlueprintPure, Category = "HyperTwist|Training|Viewer") static FString BuildBundledBrowserViewerQaChecklistTsv(); + UFUNCTION(BlueprintCallable, Category = "HyperTwist|Training|Companion") + static bool TryGetBundledEmbodiedCompanionNarrationContract( + const FString& ContractId, + FHyperTwistTrainingCompanionNarrationContract& OutContract + ); + + UFUNCTION(BlueprintCallable, Category = "HyperTwist|Training|Companion") + static bool TryGetBundledEmbodiedCompanionAvatarEmbedContract( + const FString& ContractId, + FHyperTwistTrainingCompanionAvatarEmbedContract& OutContract + ); + + UFUNCTION(BlueprintCallable, Category = "HyperTwist|Training|Companion") + static bool TryGetBundledEmbodiedCompanionVendorAdapterBoundary( + const FString& BoundaryId, + FHyperTwistTrainingCompanionVendorAdapterBoundary& OutBoundary + ); + + UFUNCTION(BlueprintPure, Category = "HyperTwist|Training|Companion") + static FString BuildBundledEmbodiedCompanionSubtitleCueChecklistTsv(); + UFUNCTION(BlueprintPure, Category = "HyperTwist|Training", meta = (WorldContext = "WorldContextObject")) static FHyperTwistTrainingLearnerDeckStateSummary GetActiveTrainingLearnerDeckStateSummary(UObject* WorldContextObject); diff --git a/docs/EXTERNAL_MIRROR_WORKSPACE_AND_SUBMODULE_HANDOFF.md b/docs/EXTERNAL_MIRROR_WORKSPACE_AND_SUBMODULE_HANDOFF.md index 3449b0c..b49fe28 100644 --- a/docs/EXTERNAL_MIRROR_WORKSPACE_AND_SUBMODULE_HANDOFF.md +++ b/docs/EXTERNAL_MIRROR_WORKSPACE_AND_SUBMODULE_HANDOFF.md @@ -241,19 +241,19 @@ Practical rule: For HyperTwist specifically, the mirror/handoff model must now carry one additional explicit truth: - current curated shallow-eval set: `71` repos -- currently verified live in checked `UnrealHyperTwist` surfaces: `9` -- permissive live lanes: `8` +- currently verified live in checked `UnrealHyperTwist` surfaces: `11` +- permissive live lanes: `10` - restrictive live lane: `1` - the restrictive live lane is `onionhoney/roux-trainers` - that lane is to be treated as properly clean-roomed and then implemented - `Phase 0R` is now closed for the remaining `61` non-live rows - `Phase 1R` is now closed as the retained-set contract and handoff layer -- the ten already-live rows now also have a dedicated source-backed preservation authority doc +- the eleven already-live rows now also have a dedicated source-backed preservation authority doc - `Phase 2R-A` is now closed as the core ownership and acceptance authority for the five retained permissive anchor rows - `Phase 2R-B` is now closed as the support-plane ownership and acceptance authority for the retained permissive support rows in scope - `Phase 2R-C` is now closed as the residual adjunct and alternative-support ownership and acceptance authority for the final retained permissive `0R-B` rows - the current manifest and doc control plane should now distinguish: - - `49` non-live active implementation-board rows + - `48` non-live active implementation-board rows - `9` retained benchmark/oracle/clean-room-later rows outside the active implementation board - `3` discarded active-set rows @@ -269,7 +269,7 @@ Reset rule: - do not reopen `Phase 0R` - before new donor-shaped widening for HyperTwist, read: - - `docs/HYPERTWIST_LIVE_LANES_SOURCE_AND_PRESERVATION_AUDIT_2026-05-13.md` for the ten already-live lanes + - `docs/HYPERTWIST_LIVE_LANES_SOURCE_AND_PRESERVATION_AUDIT_2026-05-13.md` for the eleven already-live lanes - `docs/HYPERTWIST_PHASE_1R_RETAINED_SET_CONTRACT_AND_HANDOFF_2026-05-13.md` for routing - `docs/HYPERTWIST_PHASE_2R_PACKET_2R_A_OWNERSHIP_AND_ACCEPTANCE_CONTRACT_2026-05-13.md` for the five retained core permissive rows - `docs/HYPERTWIST_PHASE_2R_PACKET_2R_B_OWNERSHIP_AND_ACCEPTANCE_CONTRACT_2026-05-13.md` for the retained permissive support-plane rows in scope diff --git a/docs/HT_REPO_INCORPORATION_AUDIT_2026-05-11.md b/docs/HT_REPO_INCORPORATION_AUDIT_2026-05-11.md index 01d3774..db55470 100644 --- a/docs/HT_REPO_INCORPORATION_AUDIT_2026-05-11.md +++ b/docs/HT_REPO_INCORPORATION_AUDIT_2026-05-11.md @@ -28,6 +28,11 @@ Important correction added on `2026-05-13`: - `google/model-viewer` is now a currently verified live permissive lane through `Phase 3R-D`. - it is live through first-party Unreal browser-viewer and asset-QA contract code plus bundled reference-target materialization rather than through the direct training-deck bundle path used by the earlier five permissive donor lanes in this audit. +Important correction added on `2026-05-13`: + +- `met4citizen/TalkingHead` is now a currently verified live permissive lane through `Phase 3R-E`. +- it is live through first-party Unreal embodied-companion contract code plus bundled reference-target materialization rather than through the direct training-deck bundle path used by the earlier five permissive donor lanes in this audit. + ## Scope - Current repo set audited: the 71 `HyperTwist` rows in `docs/repo_portfolio_unified_source_audit_v6_3.csv`. @@ -299,7 +304,6 @@ The following sensitive or high-risk lanes showed no exact live Unreal evidence - `kash/cubedesk` - `HactarCE/Hyperspeedcube` - `kkoomen/qbr` -- `met4citizen/TalkingHead` - `roice3/Magic120Cell` - `roice3/MagicCube5D` - `roice3/MagicTile` @@ -308,7 +312,7 @@ That does not make them legally cleared or deeply audited. It only means this pa ## Recommended next implementation slice -The next clean bounded move is to preserve the ten landed lanes as the current truth, keep the `onionhoney/roux-trainers` clean-room status explicit everywhere, and continue from the closed retained-set packet sequence with `Phase 3R-E`. After that, do a second pass focused on the additional live non-71 surfaces (`SpeedCubeDB` and `CubingApp`) so the active training catalog has a complete provenance board before any further widening work resumes. +The next clean bounded move is to preserve the eleven landed lanes as the current truth, keep the `onionhoney/roux-trainers` clean-room status explicit everywhere, and continue from the closed retained-set packet sequence with `Phase 3R-F`. After that, do a second pass focused on the additional live non-71 surfaces (`SpeedCubeDB` and `CubingApp`) so the active training catalog has a complete provenance board before any further widening work resumes. For the readable all-rows follow-up board that pairs this audit with the reset schedule, use: diff --git a/docs/HYPERTWIST_CANONICAL_RESTART_RECONCILIATION_2026-05-12.md b/docs/HYPERTWIST_CANONICAL_RESTART_RECONCILIATION_2026-05-12.md index 30c96ad..885802b 100644 --- a/docs/HYPERTWIST_CANONICAL_RESTART_RECONCILIATION_2026-05-12.md +++ b/docs/HYPERTWIST_CANONICAL_RESTART_RECONCILIATION_2026-05-12.md @@ -38,11 +38,11 @@ Current handling: The current reconciled HyperTwist truth is: - current curated HyperTwist shallow-eval set: `71` repos -- currently verified live in checked `UnrealHyperTwist` surfaces: `10` -- currently verified live permissive lanes: `9` +- currently verified live in checked `UnrealHyperTwist` surfaces: `11` +- currently verified live permissive lanes: `10` - currently verified live restrictive lanes: `1` -The nine currently verified live permissive lanes are: +The ten currently verified live permissive lanes are: - `Aarav2709/KubeTimr` - `apache/echarts` @@ -51,6 +51,7 @@ The nine currently verified live permissive lanes are: - `Hypercubers/hypercubing.xyz` - `tao-yu/Alg-Trainer` - `Lykos/cube_trainer` +- `met4citizen/TalkingHead` - `poliva/cubedex` - `newyork-anthonyng/rubiks-cross-trainer` @@ -150,14 +151,14 @@ Use the following only as lineage or historical context unless a restart doc exp The restart is not a mass revert. -It is a provenance and planning reset around the remaining `61` current non-live rows while preserving the ten already-landed lanes. +It is a provenance and planning reset around the remaining `60` current non-live rows while preserving the eleven already-landed lanes. Required standing rules: -- preserve the ten landed lanes +- preserve the eleven landed lanes - preserve `onionhoney/roux-trainers` as the only currently verified landed restrictive clean-room lane - do not collapse `selected`, `retained`, `integrate`, `repurpose`, or `donor bench` into `already implemented` -- do not widen new donor-shaped implementation from the remaining `61` current non-live rows until the closed packet sequence routes it +- do not widen new donor-shaped implementation from the remaining `60` current non-live rows until the closed packet sequence routes it - before implementing any retained repo, read the packet-level deep-source authority doc for that repo class if one exists ## 2026-05-12 packet-depth correction @@ -467,7 +468,7 @@ Result: - `Packet 0R-D` is now the governance and Model A authority for the restrictive clean-room rows - `Packet 0R-E` is now the deep-source benchmark, reference, clean-room-later, and discard authority for its twelve rows - `Phase 1R` is now the retained-set contract and handoff authority for all post-`Phase 0R` routing -- the ten already-live rows now also have symmetric source-backed preservation authority through the live-lane audit +- the eleven already-live rows now also have symmetric source-backed preservation authority through the live-lane audit - `Phase 2R-A` is now the ownership and acceptance authority for the five core retained permissive rows - `Phase 2R-B` is now the ownership and acceptance authority for the primary retained permissive support-plane rows in scope - `Phase 2R-C` is now the ownership and acceptance authority for the final residual `0R-B` permissive rows @@ -480,11 +481,12 @@ Result: - `Hypercubers/hypercubing.xyz` is now the seventh permissive live lane and eighth live row overall - `apache/echarts` is now the eighth permissive live lane and ninth live row overall - `google/model-viewer` is now the ninth permissive live lane and tenth live row overall +- `met4citizen/TalkingHead` is now the tenth permissive live lane and eleventh live row overall - `HactarCE/Hyperspeedcube`, `kkoomen/qbr`, `vivaansinghvi07/rubix-cube-solver`, and `roice3/MagicTile` remain packetized for `Phase 6R` - `Hypercubers/hypercubing.xyz` is now a landed permissive knowledge/curriculum/community lane rather than the next straight permissive candidate - `apache/echarts` is now a landed permissive analytics/reporting lane rather than the next straight permissive candidate -- `google/model-viewer` plus `KhronosGroup/glTF-Sample-Viewer` are now the retained browser presentation/editor and standards-QA `3R-D` lane -- `met4citizen/TalkingHead` is now the retained embodied companion `3R-E` lane +- `google/model-viewer` plus `KhronosGroup/glTF-Sample-Viewer` are now the landed browser presentation/editor and standards-QA `3R-D` lane +- `met4citizen/TalkingHead` is now the landed embodied companion `3R-E` lane - `mrdoob/three.js`, `pmndrs/react-three-fiber`, and `pmndrs/xr` now define the retained browser `3D` / XR support `3R-F` lane - `cahidenes/rubiks-cube-solver` and `tentone/rubix-solver` now form the retained `6R-E` recognition-comparison adjunct lane - `NuiLab/code-vr` now forms the retained `6R-F` symbolic-to-spatial XR pedagogy experiment lane @@ -498,7 +500,7 @@ License-tracking boundary: - `docs/REPO_LICENSE_TRACKING.md` is the canonical repo-row legal and attribution ledger - `docs/v6_5_deep_manual_pack/HyperTwist/LICENSETRACKING.md` is policy-only and must not become a second repo-row legal ledger -- `docs/HYPERTWIST_LIVE_LANES_SOURCE_AND_PRESERVATION_AUDIT_2026-05-13.md` is the source-backed preservation authority for the ten already-live rows +- `docs/HYPERTWIST_LIVE_LANES_SOURCE_AND_PRESERVATION_AUDIT_2026-05-13.md` is the source-backed preservation authority for the eleven already-live rows - `docs/HYPERTWIST_PHASE_2R_PACKET_2R_A_OWNERSHIP_AND_ACCEPTANCE_CONTRACT_2026-05-13.md` is the packet authority for the five core retained permissive rows once source extraction has already been read - `docs/HYPERTWIST_PHASE_2R_PACKET_2R_B_OWNERSHIP_AND_ACCEPTANCE_CONTRACT_2026-05-13.md` is the packet authority for the primary retained permissive support-plane rows once source extraction has already been read - `docs/HYPERTWIST_PHASE_2R_PACKET_2R_C_OWNERSHIP_AND_ACCEPTANCE_CONTRACT_2026-05-13.md` is the packet authority for the final residual permissive `0R-B` adjunct and alternative-support rows once source extraction has already been read @@ -512,7 +514,7 @@ License-tracking boundary: The next bounded move is: -1. preserve the ten landed rows as the current truth -2. keep `Aarav2709/KubeTimr`, `Hypercubers/hypercubing.xyz`, `apache/echarts`, and `google/model-viewer` on preserve-and-enhance footing through their landed packets -3. open `Phase 3R-E` -4. widen `met4citizen/TalkingHead` as the retained embodied companion, narration, lip-sync, gesture, and subtitle lane +1. preserve the eleven landed rows as the current truth +2. keep `Aarav2709/KubeTimr`, `Hypercubers/hypercubing.xyz`, `apache/echarts`, `google/model-viewer`, and `met4citizen/TalkingHead` on preserve-and-enhance footing through their landed packets +3. open `Phase 3R-F` +4. widen `mrdoob/three.js`, `pmndrs/react-three-fiber`, and `pmndrs/xr` as the retained browser `3D`, XR session, and spatial-support lane diff --git a/docs/HYPERTWIST_LIVE_LANES_SOURCE_AND_PRESERVATION_AUDIT_2026-05-13.md b/docs/HYPERTWIST_LIVE_LANES_SOURCE_AND_PRESERVATION_AUDIT_2026-05-13.md index 7a64e1d..1233022 100644 --- a/docs/HYPERTWIST_LIVE_LANES_SOURCE_AND_PRESERVATION_AUDIT_2026-05-13.md +++ b/docs/HYPERTWIST_LIVE_LANES_SOURCE_AND_PRESERVATION_AUDIT_2026-05-13.md @@ -6,12 +6,12 @@ Created on `2026-05-13` This audit is `closed`. -It is the canonical source-backed preservation authority for the ten HyperTwist rows that are already live in checked first-party Unreal surfaces. +It is the canonical source-backed preservation authority for the eleven HyperTwist rows that are already live in checked first-party Unreal surfaces. It closes the symmetry gap that remained after `Phase 0R` and `Phase 1R`: -- the `61` non-live rows already have source-backed authority through `Packet 0R-A` through `Packet 0R-E` -- the `10` live rows now have source-backed authority through this live-lane preservation audit +- the `60` non-live rows already have source-backed authority through `Packet 0R-A` through `Packet 0R-E` +- the `11` live rows now have source-backed authority through this live-lane preservation audit ## Purpose @@ -27,7 +27,7 @@ Use this document to answer the live-lane questions that the `0R-*` packets do n This document intentionally separates permissive and restrictive handling: -- the nine permissive live lanes below are documented from donor mirror source plus first-party Unreal outputs +- the ten permissive live lanes below are documented from donor mirror source plus first-party Unreal outputs - the one restrictive live lane, `onionhoney/roux-trainers`, is documented here only from first-party Unreal outputs, `REPO_LICENSE_TRACKING.md`, and scrubbed clean-room materials Do not use this document as permission for `Model B` to read the restrictive mirror. @@ -37,19 +37,19 @@ Do not use this document as permission for `Model B` to read the restrictive mir Current result: - current curated HyperTwist shallow-eval set: `71` -- already covered by `0R-A` through `0R-E`: `61` current non-live rows -- covered by this audit: `10` live rows +- already covered by `0R-A` through `0R-E`: `60` current non-live rows +- covered by this audit: `11` live rows - total rows with source-backed authority now visible in canonical docs: `71` -- live permissive preserve lanes: `9` +- live permissive preserve lanes: `10` - live restrictive clean-room preserve lanes: `1` -- additional live rows discovered beyond the original six from the 2026-05-11 audit: `4` +- additional live rows discovered beyond the original six from the 2026-05-11 audit: `5` ## Authority order For future work on the already-live lanes, read in this order: 1. this live-lane audit -2. the relevant landed implementation packet where one exists, currently [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) for `Aarav2709/KubeTimr`, [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) for `Hypercubers/hypercubing.xyz`, [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) for `apache/echarts`, and [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) for `google/model-viewer` +2. the relevant landed implementation packet where one exists, currently [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) for `Aarav2709/KubeTimr`, [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) for `Hypercubers/hypercubing.xyz`, [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) for `apache/echarts`, [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) for `google/model-viewer`, and [HYPERTWIST_PHASE_3R_PACKET_3R_E_TALKINGHEAD_IMPLEMENTATION_2026-05-13.md](C:/HyperTwist/docs/HYPERTWIST_PHASE_3R_PACKET_3R_E_TALKINGHEAD_IMPLEMENTATION_2026-05-13.md:1) for `met4citizen/TalkingHead` 3. [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) 4. [REPO_LICENSE_TRACKING.md](C:/HyperTwist/docs/REPO_LICENSE_TRACKING.md:1) 5. [MODEL_B_SOURCE_ACCESS_BOUNDARY.md](C:/HyperTwist/docs/MODEL_B_SOURCE_ACCESS_BOUNDARY.md:1) for the `onionhoney/roux-trainers` lane @@ -62,6 +62,7 @@ For future work on the already-live lanes, read in this order: | `Hypercubers/hypercubing.xyz` | `MIT` | landed taxonomy, notation, progression, software-reference, and leaderboard-contract lane | the main landed permissive hypercubing knowledge and community-reference preserve lane | runtime simulation, solver execution, recognition, or timer ownership | | `apache/echarts` | `Apache-2.0` | landed analytics, reporting, export, and progress-visualization lane | the main landed permissive analytics and report-contract preserve lane | gameplay/runtime ownership, generic BI shell ownership, or separate live-lane claims for `zrender` / `echarts-gl` | | `google/model-viewer` | `Apache-2.0` | landed browser presentation, compact editor, and standards-aware asset-QA lane | the main landed permissive browser viewer and support-plane asset-QA preserve lane | gameplay/runtime ownership, donor docs/demo shell ownership, mixed-asset shipping from `shared-assets`, or separate live-lane claims for the subordinate package rows and Khronos sidecars | +| `met4citizen/TalkingHead` | `MIT` | landed embodied companion, narration, lip-sync, gesture, subtitle, and avatar-embed lane | the main landed permissive embodied coach and companion preserve lane | generic speech-engine ownership, sample-asset shipping assumptions, donor example-shell ownership, or vendor lock-in | | `tao-yu/Alg-Trainer` | `MIT` | broad algorithm-training shell and case-corpus foundation | the main landed permissive algorithm-trainer foundation | persisted coaching backend or smartcube-first review shell | | `Lykos/cube_trainer` | `MIT` | persisted coaching, weighted sampling, and BLD-domain lane | the main landed permissive training-session and coaching lane | broad front-end training-shell ownership | | `poliva/cubedex` | operational `MIT` posture in HyperTwist canon; checked mirror license surface incomplete | smartcube-aware practice, SRS, and review lane | the main landed permissive smartcube review and repetition lane | the sole case-corpus foundation or full backend owner | @@ -419,6 +420,67 @@ Future widening rule: - preserve the Apache license text and normal `NOTICE` handling expectations in redistributed builds - read the landed [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) before treating this lane as an open donor candidate again +### `met4citizen/TalkingHead` + +Current status: + +- `implemented_live_permissive` +- preserve as a landed first-party permissive lane + +Licensing posture: + +- `MIT` +- sample avatars, media, and external TTS or JWT-backed service flows remain separate provenance and deployment questions outside the code-license grant + +Source surfaces inspected: + +- [README.md](C:/Workspaces/HyperTwist/mirrors/permissive/met4citizen/TalkingHead/README.md:1) +- [LICENSE](C:/Workspaces/HyperTwist/mirrors/permissive/met4citizen/TalkingHead/LICENSE:1) +- [package.json](C:/Workspaces/HyperTwist/mirrors/permissive/met4citizen/TalkingHead/package.json:1) +- [modules/talkinghead.mjs](C:/Workspaces/HyperTwist/mirrors/permissive/met4citizen/TalkingHead/modules/talkinghead.mjs:1) +- [modules/retargeter.mjs](C:/Workspaces/HyperTwist/mirrors/permissive/met4citizen/TalkingHead/modules/retargeter.mjs:1) +- [modules/lipsync-en.mjs](C:/Workspaces/HyperTwist/mirrors/permissive/met4citizen/TalkingHead/modules/lipsync-en.mjs:1) +- [modules/playback-worklet.js](C:/Workspaces/HyperTwist/mirrors/permissive/met4citizen/TalkingHead/modules/playback-worklet.js:1) +- [examples/azure-audio-streaming.html](C:/Workspaces/HyperTwist/mirrors/permissive/met4citizen/TalkingHead/examples/azure-audio-streaming.html:1) +- [tests/streaming-tests.html](C:/Workspaces/HyperTwist/mirrors/permissive/met4citizen/TalkingHead/tests/streaming-tests.html:1) + +First-party live evidence: + +- [HyperTwistTrainingCompanionLibrary.h](C:/HyperTwist/UnrealHyperTwist/Source/UnrealHyperTwist/Public/HyperTwistTraining/HyperTwistTrainingCompanionLibrary.h:1) +- [HyperTwistTrainingCompanionLibrary.cpp](C:/HyperTwist/UnrealHyperTwist/Source/UnrealHyperTwist/Private/HyperTwistTraining/HyperTwistTrainingCompanionLibrary.cpp:1) +- [HyperTwistTrainingRuntimeLibrary.h](C:/HyperTwist/UnrealHyperTwist/Source/UnrealHyperTwist/Public/HyperTwistTraining/HyperTwistTrainingRuntimeLibrary.h:1) +- [HyperTwistTrainingRuntimeLibrary.cpp](C:/HyperTwist/UnrealHyperTwist/Source/UnrealHyperTwist/Private/HyperTwistTraining/HyperTwistTrainingRuntimeLibrary.cpp:1) +- [hypertwist-reference-incorporation-targets.json](C:/HyperTwist/UnrealHyperTwist/Content/HyperTwistTraining/MaterializedCatalog/hypertwist-reference-incorporation-targets.json:1) +- [hypertwist-catalog-materialization-summary.json](C:/HyperTwist/UnrealHyperTwist/Content/HyperTwistTraining/MaterializedCatalog/hypertwist-catalog-materialization-summary.json:1) +- [met4citizen-talkinghead-reference-pages.jsonl](C:/HyperTwist/UnrealHyperTwist/Content/HyperTwistTraining/MaterializedCatalog/raw-extracts/met4citizen-talkinghead-reference-pages.jsonl:1) + +Preserved landed value: + +- first-party embodied companion narration with queued speech, subtitles, viseme timing, and marker-aware coach playback +- first-party avatar-only embed boundaries for external-scene companion presence with retargeting-aware motion +- first-party gesture, mood, and pose cues for acknowledgement, focus-callout, celebration, and supportive coaching states +- first-party streaming and listening lifecycle states with queue-buffer, underrun, and microphone-threshold posture +- explicit vendor and asset boundary handling so service wiring and sample-asset assumptions stay replaceable and outside product-core ownership + +Excluded or non-promotion boundary: + +- do not promote this lane into generic speech-engine ownership +- do not promote it into vendor-locked TTS infrastructure +- do not promote donor example shells, sample avatar packs, or media payloads into the shipped first-party owner +- do not treat it as a generic avatar-product foundation + +Rationale: + +- the repo is valuable because it is the strongest bounded embodied companion and narrated coaching donor in the set +- its strongest value is queue discipline, avatar embedding, subtitle and viseme timing, and coach-facing expression control rather than host-shell or vendor ownership + +Future widening rule: + +- widen only through ordinary first-party enhancement work +- preserve the MIT notice as checked locally +- keep the sample-asset and external-service provenance caveat visible +- read the landed [HYPERTWIST_PHASE_3R_PACKET_3R_E_TALKINGHEAD_IMPLEMENTATION_2026-05-13.md](C:/HyperTwist/docs/HYPERTWIST_PHASE_3R_PACKET_3R_E_TALKINGHEAD_IMPLEMENTATION_2026-05-13.md:1) before treating this lane as an open donor candidate again + ### `Lykos/cube_trainer` Current status: @@ -618,7 +680,7 @@ Future widening rule: HyperTwist now has symmetric source-backed authority across the current `71`-row curated set: -- `61` current non-live rows through `Packet 0R-A` through `Packet 0R-E` -- `10` live rows through this live-lane preservation audit +- `60` current non-live rows through `Packet 0R-A` through `Packet 0R-E` +- `11` live rows through this live-lane preservation audit For live-lane work, the next instance should not start from stale donor labels or from the raw mirror alone. It should start from this document, then the retained-set contract, then the repo-row license tracker. 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 b930972..d45b9d0 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 @@ -66,20 +66,20 @@ Document responsibilities are now strict: Current post-`Phase 1R` truth: - curated HyperTwist shallow-eval set: `71` -- currently verified live in checked Unreal surfaces: `10` +- currently verified live in checked Unreal surfaces: `11` - 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: `10` -- non-live active implementation-board rows: `49` +- landed/live preserve lanes: `11` +- non-live active implementation-board rows: `48` - non-live benchmark, oracle, or clean-room-later rows outside the active implementation board: `9` -The `49` non-live active implementation-board rows break down as: +The `48` non-live active implementation-board rows break down as: -- straight permissive implementation candidates: `39` +- straight permissive implementation candidates: `38` - boundary-sensitive adapter or sidecar candidates: `6` - restrictive clean-room-only candidates: `4` @@ -87,9 +87,9 @@ The `49` non-live active implementation-board rows break down as: | Class | Count | Earliest next phase | Meaning | | --- | --- | --- | --- | -| `landed_permissive_preserve` | `9` | ordinary first-party enhancement only | Already live. Preserve notices and attribution. Do not treat as speculative donor backlog. | +| `landed_permissive_preserve` | `10` | ordinary first-party enhancement only | Already live. Preserve notices and attribution. Do not treat as speculative donor backlog. | | `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` | `40` | `Phase 3R` | Retained for direct permissive implementation or bounded first-party adaptation. No clean-room lane is needed. | +| `phase3r_permissive_candidate` | `38` | `Phase 3R` | Retained for direct permissive implementation or bounded first-party adaptation. No clean-room lane is needed. | | `phase4r_boundary_candidate` | `6` | `Phase 4R` | Retained only through explicit adapter, allowlist, sidecar, or notice-sensitive use. | | `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. | @@ -106,7 +106,7 @@ The `49` non-live active implementation-board rows break down as: ## Landed preserve lanes -These ten rows are the only currently verified live rows in checked Unreal surfaces. +These eleven rows are the only currently verified live rows in checked Unreal surfaces. ### Landed permissive preserve @@ -116,6 +116,7 @@ These ten rows are the only currently verified live rows in checked Unreal surfa - `google/model-viewer` — `Apache-2.0` - `Hypercubers/hypercubing.xyz` — `MIT` - `Lykos/cube_trainer` — `MIT` +- `met4citizen/TalkingHead` — `MIT` - `newyork-anthonyng/rubiks-cross-trainer` — `MIT` - `poliva/cubedex` — `MIT` - `tao-yu/Alg-Trainer` — `MIT` @@ -168,6 +169,8 @@ Contract: `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. + The remaining non-live support-plane rows covered by `2R-B` are: - `ecomfe/zrender` -> subordinate beneath landed `Phase 3R-C` @@ -178,7 +181,6 @@ The remaining non-live support-plane rows covered by `2R-B` are: - `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` -- `met4citizen/TalkingHead` -> `Phase 3R-E` - `mrdoob/three.js` - `@react-spring/animated` - `@react-spring/core` @@ -324,7 +326,7 @@ Do not: `Phase 2R` is now closed and `Phase 3R-A`, `Phase 3R-B`, `Phase 3R-C`, and `Phase 3R-D` are now also closed. -The next bounded move after those closures is `Phase 3R-E`: +The next bounded move after those closures is `Phase 3R-F`: -- widen `met4citizen/TalkingHead` as the retained embodied companion, narration, lip-sync, gesture, and subtitle lane +- widen `mrdoob/three.js`, `pmndrs/react-three-fiber`, and `pmndrs/xr` as the retained browser `3D`, XR session, and spatial-support lane - preserve `Aarav2709/KubeTimr`, `Hypercubers/hypercubing.xyz`, `apache/echarts`, and `google/model-viewer` as landed permissive lanes rather than reclassifying any of them as open candidates diff --git a/docs/HYPERTWIST_PHASE_3R_PACKET_3R_E_TALKINGHEAD_IMPLEMENTATION_2026-05-13.md b/docs/HYPERTWIST_PHASE_3R_PACKET_3R_E_TALKINGHEAD_IMPLEMENTATION_2026-05-13.md new file mode 100644 index 0000000..2e7d07e --- /dev/null +++ b/docs/HYPERTWIST_PHASE_3R_PACKET_3R_E_TALKINGHEAD_IMPLEMENTATION_2026-05-13.md @@ -0,0 +1,152 @@ +# HyperTwist Phase 3R Packet 3R-E TalkingHead Implementation + +Created on `2026-05-13` + +## Status + +`Phase 3R / Packet 3R-E` is now `closed`. + +This packet converts `met4citizen/TalkingHead` from the retained embodied companion anchor into a landed first-party HyperTwist embodied companion, narration, lip-sync, gesture, subtitle, and avatar-embed lane. + +It does not reopen `Phase 0R`, `Phase 1R`, or `Phase 2R-B`. + +Those earlier packets still own source-value extraction, retained-set routing, and ownership boundaries. + +This packet owns the next question instead: + +- what first-party implementation actually landed +- which donor value was realized +- what remains explicitly out of scope for this lane +- what validation was completed +- what the next bounded implementation move is after this landing + +## Authority order + +For future work on the `met4citizen/TalkingHead` lane, read in this order: + +1. this packet for first-party landing scope, accepted widening, and validation result +2. [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) for live-lane preserve posture +3. [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) for ownership boundaries and pre-widening acceptance markers +4. [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) for source-value extraction and non-promotion rationale +5. [REPO_LICENSE_TRACKING.md](C:/HyperTwist/docs/REPO_LICENSE_TRACKING.md:1) for license and notice obligations + +## Packet licensing snapshot + +- `met4citizen/TalkingHead`: `MIT` +- sample avatars, media, and external TTS or JWT-backed service flows are separate provenance and deployment questions, not part of the code-license grant widened by this packet + +Checked local notice surfaces: + +- [LICENSE](C:/Workspaces/HyperTwist/mirrors/permissive/met4citizen/TalkingHead/LICENSE:1) currently carries the MIT grant for the checked code +- [README.md](C:/Workspaces/HyperTwist/mirrors/permissive/met4citizen/TalkingHead/README.md:1) currently documents example avatar, voice-service, and demo-shell assumptions that remain outside the shippable first-party owner + +## Packet result + +`3R-E` lands `met4citizen/TalkingHead` as: + +- `implemented_live_permissive` +- `landed_permissive_preserve` + +Current portfolio effect: + +- curated HyperTwist shallow-eval set: `71` +- currently verified live in checked Unreal surfaces: `11` +- permissive live lanes: `10` +- restrictive live clean-room lanes: `1` +- active non-live implementation-board rows: `48` + +## Donor source surfaces read + +The source read for this widening remained bounded to the retained embodied companion, queued narration, subtitle and viseme timing, avatar-only embedding, retargeting, gesture and mood presentation, streaming playback, and listening-threshold domains: + +- [LICENSE](C:/Workspaces/HyperTwist/mirrors/permissive/met4citizen/TalkingHead/LICENSE:1) +- [README.md](C:/Workspaces/HyperTwist/mirrors/permissive/met4citizen/TalkingHead/README.md:1) +- [package.json](C:/Workspaces/HyperTwist/mirrors/permissive/met4citizen/TalkingHead/package.json:1) +- [modules/talkinghead.mjs](C:/Workspaces/HyperTwist/mirrors/permissive/met4citizen/TalkingHead/modules/talkinghead.mjs:1) +- [modules/retargeter.mjs](C:/Workspaces/HyperTwist/mirrors/permissive/met4citizen/TalkingHead/modules/retargeter.mjs:1) +- [modules/lipsync-en.mjs](C:/Workspaces/HyperTwist/mirrors/permissive/met4citizen/TalkingHead/modules/lipsync-en.mjs:1) +- [modules/playback-worklet.js](C:/Workspaces/HyperTwist/mirrors/permissive/met4citizen/TalkingHead/modules/playback-worklet.js:1) +- [examples/azure-audio-streaming.html](C:/Workspaces/HyperTwist/mirrors/permissive/met4citizen/TalkingHead/examples/azure-audio-streaming.html:1) +- [tests/streaming-tests.html](C:/Workspaces/HyperTwist/mirrors/permissive/met4citizen/TalkingHead/tests/streaming-tests.html:1) + +## First-party landing surfaces + +The landed first-party Unreal surfaces are: + +- [HyperTwistTrainingCompanionLibrary.h](C:/HyperTwist/UnrealHyperTwist/Source/UnrealHyperTwist/Public/HyperTwistTraining/HyperTwistTrainingCompanionLibrary.h:1) +- [HyperTwistTrainingCompanionLibrary.cpp](C:/HyperTwist/UnrealHyperTwist/Source/UnrealHyperTwist/Private/HyperTwistTraining/HyperTwistTrainingCompanionLibrary.cpp:1) +- [HyperTwistTrainingRuntimeLibrary.h](C:/HyperTwist/UnrealHyperTwist/Source/UnrealHyperTwist/Public/HyperTwistTraining/HyperTwistTrainingRuntimeLibrary.h:1) +- [HyperTwistTrainingRuntimeLibrary.cpp](C:/HyperTwist/UnrealHyperTwist/Source/UnrealHyperTwist/Private/HyperTwistTraining/HyperTwistTrainingRuntimeLibrary.cpp:1) +- [hypertwist-reference-incorporation-targets.json](C:/HyperTwist/UnrealHyperTwist/Content/HyperTwistTraining/MaterializedCatalog/hypertwist-reference-incorporation-targets.json:1) +- [hypertwist-catalog-materialization-summary.json](C:/HyperTwist/UnrealHyperTwist/Content/HyperTwistTraining/MaterializedCatalog/hypertwist-catalog-materialization-summary.json:1) +- [met4citizen-talkinghead-reference-pages.jsonl](C:/HyperTwist/UnrealHyperTwist/Content/HyperTwistTraining/MaterializedCatalog/raw-extracts/met4citizen-talkinghead-reference-pages.jsonl:1) + +## Landed implementation scope + +What landed: + +- a first-party compiled embodied companion reference bundle with explicit speech-input, queue lifecycle, narration, subtitle, viseme, gesture, mood, avatar-embed, listening, and vendor-boundary contracts +- a first-party runtime-library access layer for the bundled companion lane, including narration-contract lookup, avatar-embed lookup, vendor-boundary lookup, and subtitle checklist export +- bundled first-party reference targets for narration, subtitle and viseme synchronization, avatar-only embedding, gesture and mood presentation, streaming and listening lifecycle, and TTS or asset adapter boundaries +- bundled raw source-reference capture for the new `met4citizen/TalkingHead` reference-target families + +What that means in practice: + +- `met4citizen/TalkingHead` now owns the landed permissive embodied companion, narration, lip-sync, gesture, subtitle, and avatar-embed lane in HyperTwist +- the landed surface is a first-party Unreal companion contract and runtime API, not a vague future donor note +- sample avatars, direct vendor shells, and external TTS wiring remain explicit boundary surfaces rather than silently becoming product ownership + +## Preserved landed value + +The donor value that was actually promoted is: + +- explicit queued narration behavior with voice parameters, markers, subtitles, viseme timing, and mood or gesture cues +- explicit avatar-only embed behavior for bounded external-scene companion presence with camera-safe composition and retargeted motion +- explicit gesture, mood, and pose presentation surfaces for acknowledgement, focus, celebration, and supportive coaching states +- explicit streaming playback and listening-threshold lifecycle states with queue-buffer and underrun metrics +- explicit vendor-adapter boundaries so voice-service wiring, avatar assets, and donor example shells remain replaceable and out of product-core ownership + +## Excluded or non-promotion boundary + +Do not promote this lane into: + +- generic speech-engine ownership +- external TTS vendor lock-in +- generic avatar-product or character-platform ownership +- sample avatar or donor media shipping assumptions +- donor example-page shell, camera page, or tutorial framing + +Rationale: + +- this repo was retained and widened because it was the strongest bounded embodied companion donor in the set +- its highest value is queue discipline, avatar embedding, subtitle and viseme timing, and coach-facing expression control, not host-application or vendor-product ownership +- the vendor and asset seams remain useful precisely because they stay replaceable beneath the landed first-party owner + +## Acceptance markers satisfied + +The `2R-B` acceptance markers for this row are now satisfied in first-party Unreal surfaces: + +- a first-party narration event contract exists with speech inputs, queue lifecycle states, output tags, and exclusions +- a first-party avatar-embedding contract exists with scene and camera bindings plus explicit gesture and mood support +- a first-party vendor-adapter boundary exists with replaceable voice-service and asset fields kept separate from first-party coach-owned fields +- a first-party streaming and listening lifecycle exists with queue, stream-buffer, underrun, and microphone-threshold posture + +## Validation + +Validation completed for this packet: + +- `git diff --check` passed apart from CRLF conversion warnings +- JSON validation passed for the updated materialized-catalog files and workspace manifest +- Unreal build succeeded with: + - `C:\Program Files\Epic Games\UE_5.7\Engine\Build\BatchFiles\Build.bat UnrealHyperTwistEditor Win64 Development C:\HyperTwist\UnrealHyperTwist\UnrealHyperTwist.uproject -WaitMutex -NoHotReloadFromIDE` + +Build result: + +- `Succeeded` on `2026-05-13` + +## Next move + +The next bounded move is `Phase 3R-F`: + +- widen `mrdoob/three.js`, `pmndrs/react-three-fiber`, and `pmndrs/xr` as the retained browser `3D`, XR session, and spatial-support lane +- keep the newly landed `met4citizen/TalkingHead` embodied companion lane on preserve-and-enhance footing rather than treating it as an open donor candidate again 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 d849c1c..4064a1f 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 @@ -417,6 +417,31 @@ Next packet: - `3R-E` +`Phase 3R / Packet 3R-E` is now closed. + +- `Phase 3R-E` result doc: + - `docs/HYPERTWIST_PHASE_3R_PACKET_3R_E_TALKINGHEAD_IMPLEMENTATION_2026-05-13.md` + +Implementation result: + +- `met4citizen/TalkingHead` is now landed as a first-party embodied companion, narration, lip-sync, gesture, subtitle, and avatar-embed lane +- `met4citizen/TalkingHead` is now `implemented_live_permissive` +- sample avatars, media, and external TTS or JWT-backed service flows remain boundary surfaces and are not silently widened by this packet +- current verified live rows are now: + - `11` total + - `10` permissive + - `1` restrictive clean-room +- active non-live implementation-board rows are now `48` +- the `met4citizen/TalkingHead` embodied companion anchor is no longer a queued `Phase 3R` candidate; it is a landed live lane + +Validation result: + +- `UnrealHyperTwistEditor` build succeeded for the landed widening packet + +Next packet: + +- `3R-F` + Mandatory read rule before implementing, benchmarking against, or clean-rooming any `0R-E` repo: 1. read `docs/HYPERTWIST_PHASE_0R_PACKET_0R_E_EVALUATION_2026-05-13.md` @@ -444,20 +469,20 @@ Current curated HyperTwist shallow-eval set: Current verified live implementation state in checked `UnrealHyperTwist` source and materialized training surfaces: -- `10` repos are implemented/live -- `9` of those are permissive `MIT` or `Apache-2.0` lanes +- `11` repos are implemented/live +- `10` of those are permissive `MIT` or `Apache-2.0` lanes - `1` of those is a restrictive repo that was properly clean-roomed and then implemented Current 2026-05-11 repo-row reset counts: -- `implemented_live_permissive`: `9` +- `implemented_live_permissive`: `10` - `implemented_live_clean_room_verified`: `1` -- `selected_not_live_permissive_candidate`: `39` +- `selected_not_live_permissive_candidate`: `38` - `selected_not_live_boundary_sensitive`: `6` - `selected_not_live_clean_room_candidate`: `4` - `not_live_reference_or_discard_candidate`: `12` -### The ten currently implemented/live repos +### The eleven currently implemented/live repos Permissive `MIT` or `Apache-2.0` lanes already implemented/live: @@ -468,6 +493,7 @@ Permissive `MIT` or `Apache-2.0` lanes already implemented/live: - `Hypercubers/hypercubing.xyz` - `tao-yu/Alg-Trainer` - `Lykos/cube_trainer` +- `met4citizen/TalkingHead` - `poliva/cubedex` - `newyork-anthonyng/rubiks-cross-trainer` @@ -519,17 +545,17 @@ At the moment, only one HyperTwist repo should be described this way: HyperTwist should now proceed from the following rule: -- preserve the ten live lanes +- preserve the eleven live lanes - do not reopen the `onionhoney/roux-trainers` lane as if it were an unresolved accidental donor import -- do not treat the remaining `61` current non-live rows as already implemented +- do not treat the remaining `60` 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, currently `Phase 3R-E` +- continue later-phase widening from the closed packet sequence, currently `Phase 3R-F` In practical terms: -- no, do **not** mass-revert the ten landed lanes +- no, do **not** mass-revert the eleven landed lanes - no, do **not** pretend the remaining `61` current non-live rows are already implemented -- yes, preserve the landed `Aarav2709/KubeTimr`, `Hypercubers/hypercubing.xyz`, `apache/echarts`, and `google/model-viewer` lanes as normal first-party enhancement surfaces +- yes, preserve the landed `Aarav2709/KubeTimr`, `Hypercubers/hypercubing.xyz`, `apache/echarts`, `google/model-viewer`, and `met4citizen/TalkingHead` lanes as normal first-party enhancement surfaces - yes, widen the next retained permissive lane only through its closed packet stack ## Phase reset sequence @@ -895,7 +921,7 @@ Only after that: The clean practical sequence is: -1. preserve the ten landed lanes +1. preserve the eleven landed lanes 2. make the current truth explicit everywhere 3. deep-evaluate the remaining `65` 4. discard what should not survive @@ -912,7 +938,8 @@ Current status: - `Phase 3R-B` is now also complete - `Phase 3R-C` is now also complete - `Phase 3R-D` is now also complete -- the next bounded move is `Phase 3R-E` for `met4citizen/TalkingHead` +- `Phase 3R-E` is now also complete +- the next bounded move is `Phase 3R-F` for `mrdoob/three.js`, `pmndrs/react-three-fiber`, and `pmndrs/xr` ## 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 f3d0e15..8aaf4fe 100644 --- a/docs/HYPERTWIST_REPO_STATE_BOARD_2026-05-11.md +++ b/docs/HYPERTWIST_REPO_STATE_BOARD_2026-05-11.md @@ -7,14 +7,14 @@ 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: `10` repos -- Live permissive lanes: `9` +- Currently verified live in checked `UnrealHyperTwist` surfaces: `11` repos +- Live permissive lanes: `10` - Live restrictive clean-room lanes: `1` - 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 and the landed `Phase 3R-D` browser viewer lane, while `Phase 0R` and `Phase 1R` remain closed. +The baseline live-state counts above now include the landed `Phase 3R-C` analytics lane, the landed `Phase 3R-D` browser viewer lane, and the landed `Phase 3R-E` embodied companion lane, while `Phase 0R` and `Phase 1R` remain closed. Read together with: @@ -32,6 +32,7 @@ Read together with: - [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) - [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) - [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) +- [HYPERTWIST_PHASE_3R_PACKET_3R_E_TALKINGHEAD_IMPLEMENTATION_2026-05-13.md](C:/HyperTwist/docs/HYPERTWIST_PHASE_3R_PACKET_3R_E_TALKINGHEAD_IMPLEMENTATION_2026-05-13.md:1) That overlay closes evaluation for: @@ -51,7 +52,7 @@ Important authority correction: - `Packet 0R-C` is now the deep-source value-extraction and exclusion-rationale authority for its six boundary-sensitive repos - `Packet 0R-D` is now the governance and Model A authority for its four restrictive clean-room repos - `Packet 0R-E` is now the deep-source benchmark, reference, clean-room-later, and discard authority for its twelve rows -- the live-lane preservation audit is now the source-backed authority for the nine already-landed rows +- the live-lane preservation audit is now the source-backed authority for the eleven already-landed rows - `Phase 1R` is now the retained-set contract and handoff authority for all post-`Phase 0R` routing - `Phase 2R-A` is now the core ownership and acceptance authority for the five retained core permissive rows - `Phase 2R-B` is now the support-plane ownership and acceptance authority for the primary retained permissive support rows @@ -60,7 +61,8 @@ Important authority correction: - `Phase 3R-B` is now the landed implementation authority for `Hypercubers/hypercubing.xyz` - `Phase 3R-C` is now the landed implementation authority for `apache/echarts` - `Phase 3R-D` is now the landed implementation authority for `google/model-viewer` -- future enhancement or preservation work for the ten landed rows should start from the live-lane audit, then the repo-specific landed packet where one exists, not from this board alone +- `Phase 3R-E` is now the landed implementation authority for `met4citizen/TalkingHead` +- future enhancement or preservation work for the eleven landed rows should start from the live-lane audit, then the repo-specific landed packet where one exists, not from this board alone - future implementation of those seven repos should start from `Packet 0R-A`, not from this board alone - 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 - future implementation of those six boundary-sensitive repos should start from `Packet 0R-C`, not from this board alone @@ -75,7 +77,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 `10` live rows now also have symmetric source-backed preservation authority +- all `11` 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 @@ -83,23 +85,25 @@ Packet overlay result: - `Phase 3R-B` is now closed for the `Hypercubers/hypercubing.xyz` taxonomy, notation, progression, software-reference, and leaderboard-contract lane - `Phase 3R-C` is now closed for the `apache/echarts` analytics, reporting, export, and progress-visualization lane - `Phase 3R-D` is now closed for the `google/model-viewer` browser presentation, compact editor, and standards-aware asset-QA lane +- `Phase 3R-E` is now closed for the `met4citizen/TalkingHead` embodied companion, narration, lip-sync, gesture, subtitle, and avatar-embed lane - `Phase 2R` is now fully closed for the retained permissive set - `Aarav2709/KubeTimr` is now newly proven live in checked Unreal surfaces through `Phase 3R-A` - `Hypercubers/hypercubing.xyz` is now newly proven live in checked Unreal surfaces through `Phase 3R-B` - `apache/echarts` is now newly proven live in checked Unreal surfaces through `Phase 3R-C` - `google/model-viewer` is now newly proven live in checked Unreal surfaces through `Phase 3R-D` +- `met4citizen/TalkingHead` is now newly proven live in checked Unreal surfaces through `Phase 3R-E` - `Phase 0R` is now fully closed - `Phase 1R` is now fully closed - 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 3R-E` +- the next bounded move is `Phase 3R-F` ## Count by live-state class -- `implemented_live_permissive`: `9` +- `implemented_live_permissive`: `10` - `implemented_live_clean_room_verified`: `1` -- `selected_not_live_permissive_candidate`: `40` +- `selected_not_live_permissive_candidate`: `38` - `selected_not_live_boundary_sensitive`: `6` - `selected_not_live_clean_room_candidate`: `4` - `not_live_reference_or_discard_candidate`: `12` @@ -115,15 +119,17 @@ Packet overlay result: These are currently verified live in checked Unreal surfaces and are permissive lanes already implemented. -Count: `8` +Count: `10` | Repo | License | Prior bucket | Prior action | Current live state | Reset lane | Next step | | --- | --- | --- | --- | --- | --- | --- | | `Aarav2709/KubeTimr` | `MIT` | Donor Bench | `repurpose` | `implemented_live_permissive` | `landed_permissive_preserve` | `Phase 3R-A` closed. Preserve as the landed first-party timer, inspection, splits, stats, persistence, and timer-scoped replay lane; start future widening from the live-lane audit, then the `3R-A` implementation packet, then `REPO_LICENSE_TRACKING.md`. | | `apache/echarts` | `Apache-2.0` | Donor Bench | `repurpose` | `implemented_live_permissive` | `landed_permissive_preserve` | `Phase 3R-C` closed. Preserve as the landed first-party analytics, reporting, export, and progress-visualization lane; start future widening from the live-lane audit, then the `3R-C` implementation packet, then `REPO_LICENSE_TRACKING.md`. | | `abunickabhi/5style-Trainer` | `MIT` | Donor Bench | `repurpose` | `implemented_live_permissive` | `landed_permissive_preserve` | Phase 1R closed. Preserve as a landed first-party permissive lane; keep notices and attribution visible; start future widening from the live-lane audit, then `REPO_LICENSE_TRACKING.md`, then ordinary owned enhancement work. | +| `google/model-viewer` | `Apache-2.0` | Donor Bench | `repurpose` | `implemented_live_permissive` | `landed_permissive_preserve` | `Phase 3R-D` closed. Preserve as the landed first-party browser presentation, compact editor, and standards-aware asset-QA lane; start future widening from the live-lane audit, then the `3R-D` implementation packet, then `REPO_LICENSE_TRACKING.md`. | | `Hypercubers/hypercubing.xyz` | `MIT` | Locked Strategic Donor | `repurpose` | `implemented_live_permissive` | `landed_permissive_preserve` | `Phase 3R-B` closed. Preserve as the landed first-party hypercubing knowledge, notation, progression, software-reference, and leaderboard-contract lane; start future widening from the live-lane audit, then the `3R-B` implementation packet, then `REPO_LICENSE_TRACKING.md`. | | `Lykos/cube_trainer` | `MIT` | Locked Strategic Donor | `integrate` | `implemented_live_permissive` | `landed_permissive_preserve` | Phase 1R closed. Preserve as a landed first-party permissive lane; keep notices and attribution visible; start future widening from the live-lane audit, then `REPO_LICENSE_TRACKING.md`, then ordinary owned enhancement work. | +| `met4citizen/TalkingHead` | `MIT` | Donor Bench | `repurpose` | `implemented_live_permissive` | `landed_permissive_preserve` | `Phase 3R-E` closed. Preserve as the landed first-party embodied companion, narration, lip-sync, gesture, subtitle, and avatar-embed lane; start future widening from the live-lane audit, then the `3R-E` implementation packet, then `REPO_LICENSE_TRACKING.md`. | | `newyork-anthonyng/rubiks-cross-trainer` | `MIT` | Donor Bench | `repurpose` | `implemented_live_permissive` | `landed_permissive_preserve` | Phase 1R closed. Preserve as a landed first-party permissive lane; keep notices and attribution visible; start future widening from the live-lane audit, then `REPO_LICENSE_TRACKING.md`, then ordinary owned enhancement work. | | `poliva/cubedex` | `MIT` | Locked Strategic Donor | `integrate` | `implemented_live_permissive` | `landed_permissive_preserve` | Phase 1R closed. Preserve as a landed first-party permissive lane; keep notices and attribution visible; start future widening from the live-lane audit, then `REPO_LICENSE_TRACKING.md`, then ordinary owned enhancement work. | | `tao-yu/Alg-Trainer` | `MIT` | Locked Parallel Foundation | `integrate` | `implemented_live_permissive` | `landed_permissive_preserve` | Phase 1R closed. Preserve as a landed first-party permissive lane; keep notices and attribution visible; start future widening from the live-lane audit, then `REPO_LICENSE_TRACKING.md`, then ordinary owned enhancement work. | @@ -142,7 +148,7 @@ Count: `1` These rows are retained, not currently proven live, and have now cleared `Phase 0R` deep evaluation. `Phase 1R` places them on the active implementation board with earliest re-entry through `Phase 3R`. -Count: `40` +Count: `38` | Repo | License | Prior bucket | Prior action | Current live state | Reset lane | Next step | | --- | --- | --- | --- | --- | --- | --- | @@ -155,7 +161,6 @@ Count: `40` | `cahidenes/rubiks-cube-solver` | `MIT` | Locked Strategic Donor | `integrate` | `selected_not_live_permissive_candidate` | `phase0r_permissive_eval_then_implement` | `Phase 2R-C` closed. Freeze as part of the `Phase 6R-E` recognition-comparison adjunct lane for face placement and cube-string cross-checks behind the retained recognition anchors; do not widen in `Phase 3R`. | | `ecomfe/echarts-gl` | `BSD-3-Clause` | Merge Bench | `integrate` | `selected_not_live_permissive_candidate` | `phase0r_permissive_eval_then_implement` | `Phase 3R-C` closed for the anchor. Retain as an optional subordinate `3D` analytics and explainer sidecar beneath the landed `apache/echarts` lane; do not treat it as separately live. | | `ecomfe/zrender` | `BSD-3-Clause` | Merge Bench | `integrate` | `selected_not_live_permissive_candidate` | `phase0r_permissive_eval_then_implement` | `Phase 3R-C` closed for the anchor. Retain as the lower-level subordinate `2D` substrate beneath the landed `apache/echarts` lane; do not treat it as separately live. | -| `google/model-viewer` | `Apache-2.0` | Donor Bench | `repurpose` | `implemented_live_permissive` | `landed_permissive_preserve` | `Phase 3R-D` closed. Preserve as the landed first-party browser presentation, compact editor, and standards-aware asset-QA lane; start future widening from the live-lane audit, then the `3R-D` implementation packet, then `REPO_LICENSE_TRACKING.md`. | | `google/model-viewer/packages/model-viewer-effects` | `Apache-2.0` | Merge Bench | `integrate` | `selected_not_live_permissive_candidate` | `phase0r_permissive_eval_then_implement` | `Phase 3R-D` closed for the anchor. Retain as a subordinate emphasis and effects package beneath the landed `google/model-viewer` lane; do not treat it as separately live. | | `google/model-viewer/packages/modelviewer.dev` | `Apache-2.0` | Merge Bench | `integrate` | `selected_not_live_permissive_candidate` | `phase0r_permissive_eval_then_implement` | `Phase 3R-D` closed for the anchor. Retain as subordinate docs and demo infrastructure beneath the landed `google/model-viewer` lane; do not treat it as separately live or as a product-shell owner. | | `google/model-viewer/packages/render-fidelity-tools` | `Apache-2.0` | Merge Bench | `integrate` | `selected_not_live_permissive_candidate` | `phase0r_permissive_eval_then_implement` | `Phase 3R-D` closed for the anchor. Retain as the subordinate fidelity-oracle and regression sidecar beneath the landed `google/model-viewer` lane; do not treat it as separately live. | @@ -164,7 +169,6 @@ Count: `40` | `KhronosGroup/glTF-Sample-Renderer` | `Apache-2.0` | Merge Bench | `integrate` | `selected_not_live_permissive_candidate` | `phase0r_permissive_eval_then_implement` | `Phase 3R-D` closed for the anchor. Retain as the subordinate renderer/reference substrate beneath the landed `google/model-viewer` asset-QA lane; do not treat it as separately live. | | `KhronosGroup/glTF-Sample-Viewer` | `Apache-2.0` | Donor Bench | `repurpose` | `selected_not_live_permissive_candidate` | `phase0r_permissive_eval_then_implement` | `Phase 3R-D` closed for the anchor. Retain as the subordinate standards-aware asset QA and validation sidecar beneath the landed `google/model-viewer` lane; do not treat it as separately live. | | `kkoomen/qbr` | `MIT` | Locked Foundation | `integrate` | `selected_not_live_permissive_candidate` | `phase0r_permissive_eval_then_implement` | `Phase 2R-A` closed. Freeze as the `Phase 6R-B` calibration, perceptual color matching, contour ordering, and scan-state extraction anchor; keep browser-side correction ownership with `vivaansinghvi07/rubix-cube-solver`. | -| `met4citizen/TalkingHead` | `MIT` | Donor Bench | `repurpose` | `selected_not_live_permissive_candidate` | `phase0r_permissive_eval_then_implement` | `Phase 2R-B` closed. Freeze as the `Phase 3R-E` embodied companion, narration, lip-sync, gesture, and subtitle anchor; widen only from the `2R-B` ownership contract, then `0R-B`, then `REPO_LICENSE_TRACKING.md`. | | `mrdoob/three.js` | `MIT` | Donor Bench | `repurpose` | `selected_not_live_permissive_candidate` | `phase0r_permissive_eval_then_implement` | `Phase 2R-B` closed. Retain as the commodity `Phase 3R-F` browser `3D` substrate beneath higher-level support surfaces; do not let it displace the Unreal-first runtime stance. | | `NuiLab/code-vr` | `MIT` | Donor Bench | `repurpose` | `selected_not_live_permissive_candidate` | `phase0r_permissive_eval_then_implement` | `Phase 2R-C` closed. Freeze as the `Phase 6R-F` symbolic-to-spatial XR pedagogy experiment lane only; do not let it own the practical browser XR runtime. | | `pissang/clay-viewer` | `BSD-3-Clause` | Merge Bench | `integrate` | `selected_not_live_permissive_candidate` | `phase0r_permissive_eval_then_implement` | `Phase 2R-C` closed. Freeze as part of the optional `Phase 3R-G` alternative browser viewer/editor comparison lane subordinate to `google/model-viewer`; widen only if a real sidecar gap remains after the primary browser stack exists. | @@ -238,8 +242,8 @@ Count: `12` ## Implementation rule going forward -- Preserve the ten landed lanes as current truth. +- Preserve the eleven landed lanes as current truth. - Keep `onionhoney/roux-trainers` explicitly marked as the only currently verified restrictive clean-room lane already implemented. -- `Phase 0R` is now fully closed for the remaining `61` non-live rows. +- `Phase 0R` is now fully closed for the remaining `60` non-live rows. - `Phase 1R` is now the routing authority for retained-set widening and benchmark exclusion. -- The next bounded move is `Phase 3R-E` for the retained `met4citizen/TalkingHead` embodied companion, narration, lip-sync, gesture, and subtitle lane. +- The next bounded move is `Phase 3R-F` for the retained `mrdoob/three.js`, `pmndrs/react-three-fiber`, and `pmndrs/xr` browser `3D`, XR session, and spatial-support lane. diff --git a/docs/REPO_LICENSE_TRACKING.md b/docs/REPO_LICENSE_TRACKING.md index 0ef18bc..67d7127 100644 --- a/docs/REPO_LICENSE_TRACKING.md +++ b/docs/REPO_LICENSE_TRACKING.md @@ -53,11 +53,11 @@ Do not use it as the primary architecture ledger. The architecture and donor dec This file now also preserves the current truth that future models must not lose: - current curated HyperTwist shallow-eval set: `71` repos -- currently verified live/implemented in checked `UnrealHyperTwist` surfaces: `10` -- permissive live lanes: `9` +- currently verified live/implemented in checked `UnrealHyperTwist` surfaces: `11` +- permissive live lanes: `10` - restrictive live lanes: `1` -The nine permissive live lanes are: +The ten permissive live lanes are: - `Aarav2709/KubeTimr` - `apache/echarts` @@ -66,6 +66,7 @@ The nine permissive live lanes are: - `Hypercubers/hypercubing.xyz` - `tao-yu/Alg-Trainer` - `Lykos/cube_trainer` +- `met4citizen/TalkingHead` - `poliva/cubedex` - `newyork-anthonyng/rubiks-cross-trainer` @@ -117,7 +118,8 @@ Current practical interpretation: - the landed `Hypercubers/hypercubing.xyz` widening packet now lives in `docs/HYPERTWIST_PHASE_3R_PACKET_3R_B_HYPERCUBING_XYZ_IMPLEMENTATION_2026-05-13.md` - the landed `apache/echarts` widening packet now lives in `docs/HYPERTWIST_PHASE_3R_PACKET_3R_C_ECHARTS_IMPLEMENTATION_2026-05-13.md` - the landed `google/model-viewer` widening packet now lives in `docs/HYPERTWIST_PHASE_3R_PACKET_3R_D_MODEL_VIEWER_IMPLEMENTATION_2026-05-13.md` -- the next bounded move is `Phase 3R-E` +- the landed `met4citizen/TalkingHead` widening packet now lives in `docs/HYPERTWIST_PHASE_3R_PACKET_3R_E_TALKINGHEAD_IMPLEMENTATION_2026-05-13.md` +- the next bounded move is `Phase 3R-F` Companion docs: @@ -1243,7 +1245,7 @@ Current licensing judgment: - repo code is usable for HyperTwist under `MIT` - not a clean-room case -- treat as a strategic donor for the embodied coach and companion lane +- treat as a landed permissive preserve lane for the embodied coach and companion surface Source basis: @@ -1266,6 +1268,14 @@ Important distinction: - gesture, emoji, mood, and pose orchestration - Mixamo-style retargeting helpers - low-latency streaming audio playback with underrun/queue metrics +- this lane is now landed/live in first-party Unreal surfaces through [HYPERTWIST_PHASE_3R_PACKET_3R_E_TALKINGHEAD_IMPLEMENTATION_2026-05-13.md](C:/HyperTwist/docs/HYPERTWIST_PHASE_3R_PACKET_3R_E_TALKINGHEAD_IMPLEMENTATION_2026-05-13.md:1) + +Current implementation rule: + +- preserve as a landed permissive lane +- preserve the checked MIT notice +- keep sample-avatar, media, and external voice-service provenance separate from the code-license record +- read the landed `3R-E` packet and the live-lane audit before widening this lane further Approved working posture: diff --git a/docs/repo_portfolio_unified_copyleft_strategy_matrix_v6_3.csv b/docs/repo_portfolio_unified_copyleft_strategy_matrix_v6_3.csv index a75e16c..0b5d533 100644 --- a/docs/repo_portfolio_unified_copyleft_strategy_matrix_v6_3.csv +++ b/docs/repo_portfolio_unified_copyleft_strategy_matrix_v6_3.csv @@ -39,7 +39,7 @@ Hypercubers/hypercubing.xyz,https://github.com/Hypercubers/hypercubing.xyz,Hyper Aarav2709/KubeTimr,https://github.com/Aarav2709/KubeTimr,HyperTwist,Donor Bench,donor bench,repurpose,moderate modification,MIT,known_from_reference_material,uploaded_reference_docs,permissive_or_noncopyleft_known,direct_incorporation_ok,"This repo is permissively licensed and currently best treated as a focused subsystem donor for timer-state logic, split-phase handling, local persistence, and keyboard-first practice flow. Selective incorporation is legally straightforward, but the product shell should still be reshaped to fit HyperTwist.",high,routine-review-only,v6.3_final_source_of_truth,implemented_live_permissive,landed_permissive_preserve,"Phase 3R-A closed. Preserve as the landed first-party timer, inspection, splits, stats, persistence, and timer-scoped replay lane; start future widening from the live-lane audit, then the 3R-A implementation packet, then REPO_LICENSE_TRACKING.md." roice3/MagicTile,https://github.com/roice3/MagicTile,HyperTwist,Locked Strategic Donor,locked strategic donor,repurpose,moderate modification,MIT,known_from_reference_material,uploaded_reference_docs,permissive_or_noncopyleft_known,direct_incorporation_ok,The repo is MIT and is explicitly retained as a top-tier geometry/topology donor. Direct donor use is legally straightforward if the architecture benefits from it.,high,permissive-top-tier-donor,v6.3_final_source_of_truth,selected_not_live_permissive_candidate,phase0r_permissive_eval_then_implement,"Phase 1R closed. Retain as a Phase 3R permissive implementation candidate; implement only from its packet authority and the retained-set contract, not by reopening Phase 0R." PostHog/posthog,https://github.com/PostHog/posthog,HyperTwist,,donor bench,repurpose,moderate modification,MIT outside ee/; enterprise-restricted in ee/,known_from_reference_material,uploaded_reference_docs,mixed_or_boundary_sensitive_known,bounded_sidecar_or_selective_reimplementation,"The repo is mixed-license: MIT outside ee/ and enterprise-restricted inside ee/. Use only clearly MIT paths as bounded telemetry, replay, and feature-governance donor material, and exclude or reimplement enterprise-gated paths.",high,mixed-license-path-review-required,v6.3_final_source_of_truth,selected_not_live_boundary_sensitive,phase0r_boundary_sensitive_eval_then_adapter_or_sidecar,Phase 1R closed. Retain as a Phase 4R bounded telemetry and replay sidecar candidate; keep ee/ excluded and use explicit allowlists or first-party reimplementation where needed. -met4citizen/TalkingHead,https://github.com/met4citizen/TalkingHead,HyperTwist,Donor Bench,donor bench,repurpose,moderate modification,MIT,known_from_reference_material,uploaded_reference_docs,permissive_or_noncopyleft_known,direct_incorporation_ok,The code license is MIT and direct use is allowed. Treat it as a bounded browser-side donor for embodied coach presentation rather than as a product shell.,high,standard-notice-review,v6.3_markdown_backfill,selected_not_live_permissive_candidate,phase0r_permissive_eval_then_implement,"Phase 1R closed. Retain as a Phase 3R permissive implementation candidate; implement only from its packet authority and the retained-set contract, not by reopening Phase 0R." +met4citizen/TalkingHead,https://github.com/met4citizen/TalkingHead,HyperTwist,Donor Bench,donor bench,repurpose,moderate modification,MIT,known_from_reference_material,uploaded_reference_docs,permissive_or_noncopyleft_known,direct_incorporation_ok,The code license is MIT and direct use is allowed. Treat it as a bounded browser-side donor for embodied coach presentation rather than as a product shell.,high,standard-notice-review,v6.3_markdown_backfill,implemented_live_permissive,landed_permissive_preserve,"Phase 3R-E closed. Preserve as the landed first-party embodied companion, narration, lip-sync, gesture, subtitle, and avatar-embed lane; start future widening from the live-lane audit, then the 3R-E implementation packet, then REPO_LICENSE_TRACKING.md." apache/echarts,https://github.com/apache/echarts,HyperTwist,Donor Bench,donor bench,repurpose,moderate modification,Apache-2.0,known_from_reference_material,uploaded_reference_docs,permissive_or_noncopyleft_known,direct_incorporation_ok,The code license is Apache-2.0 and direct use is allowed. Treat it as a bounded reporting and analytics donor.,high,notice-file-review,v6.3_markdown_backfill,implemented_live_permissive,landed_permissive_preserve,"Phase 3R-C closed. Preserve as the landed first-party analytics, reporting, export, and progress-visualization lane; start future widening from the live-lane audit, then the 3R-C implementation packet, then REPO_LICENSE_TRACKING.md." ecomfe/echarts-gl,https://github.com/ecomfe/echarts-gl,HyperTwist,Merge Bench,merge bench,integrate,moderate modification,BSD-3-Clause,known_from_reference_material,uploaded_reference_docs,permissive_or_noncopyleft_known,direct_incorporation_ok,The code license is BSD-3-Clause and direct use is allowed. Treat it as a bounded 3D analytics extension rather than a runtime foundation.,high,standard-notice-review,v6.3_markdown_backfill,selected_not_live_permissive_candidate,phase0r_permissive_eval_then_implement,"Phase 3R-C closed for the anchor. Retain as an optional subordinate 3D analytics and explainer sidecar beneath the landed apache/echarts lane; do not treat it as separately live." KhronosGroup/glTF-Sample-Viewer,https://github.com/KhronosGroup/glTF-Sample-Viewer,HyperTwist,Donor Bench,donor bench,repurpose,moderate modification,Apache-2.0,known_from_reference_material,uploaded_reference_docs,permissive_or_noncopyleft_known,direct_incorporation_ok,The code license is Apache-2.0 and direct use is allowed. Treat it as a bounded standards-viewer and asset-QA donor.,high,notice-file-review,v6.3_markdown_backfill,selected_not_live_permissive_candidate,phase0r_permissive_eval_then_implement,"Phase 3R-D closed for the anchor. Retain as the subordinate standards-aware asset QA and validation sidecar beneath the landed google/model-viewer lane; do not treat it as separately live." diff --git a/docs/repo_portfolio_unified_operational_v6_3.csv b/docs/repo_portfolio_unified_operational_v6_3.csv index 98f9351..e92cf8b 100644 --- a/docs/repo_portfolio_unified_operational_v6_3.csv +++ b/docs/repo_portfolio_unified_operational_v6_3.csv @@ -1,30 +1,30 @@ execution_queue_order,repo,primary_url,best_fit_project_v2,project_rank,portfolio_priority_score,execution_priority_score_v3,priority_band,taxonomy_hardened,archetype_primary,archetype_secondary,portfolio_role_v3,recommended_action_v2,repurposing_potential_v2,modification_scope_detail_v3,capability_extract,integration_realization_detail,consolidation_detail,repurpose_detail,realization_checklist,inspection_depth_recommendation,hidden_value_hypothesis,source_inspection_questions,source_code_audit_targets,coding_model_instruction_v3,merger_partner_1,merger_type_1,merger_rationale_1,merger_partner_2,merger_type_2,merger_rationale_2,merger_partner_3,merger_type_3,merger_rationale_3,cross_project_transfer_targets,cross_project_transfer_rationale,exclusion_discipline,exclusion_reasoning_v3,confidence_v3,confidence_rationale_v3,confidence_reassessed,confidence_rationale,licensing_filter_status,bookmark_project_sections,bookmark_heading_paths_top,bookmark_description_sample,memo_signal_sample,expanded_reasoning,source_attachments,in_bookmarks,in_memo,bookmark_occurrences,memo_mentions,cluster_tag,source_audit_packet_id,category_guess_v2,reasoning,best_fit_project,category_guess,recommended_action,repurposing_potential,confidence,_repo_norm,v5_primary_eval_project,v5_runtime_project,v5_scriptorium_override_status,v5_scriptorium_current_reality_status,v5_scriptorium_bucket,v5_scriptorium_stack_layer,v5_scriptorium_source_audit_priority,v5_scriptorium_actual_role,v5_scriptorium_integration_boundary,v5_scriptorium_evidence_summary,v5_scriptorium_design_language_notes,v5_scriptorium_recommended_context_packet,v5_scriptorium_supersedes_prior_assessment,v5_scriptorium_bucket_rank,v5_scriptorium_prio_rank,v5_scriptorium_sort_score,v5_source_of_truth,v6_license_annotation,v6_license_annotation_status,v6_license_annotation_source,v6_supplemental_intake_present,v6_supplemental_source_groups,v6_supplemental_source_sections,v6_supplemental_source_files,v6_reference_material_position,v6_kali_agent_access_relevance,v6_branch_seed_prompt_included,v6_branch_seed_scope,v6_intake_wave,v6_notes,project_rank_num,audit_rank_num,priority_num,phase_g_bucket,phase_g_project_stack_layer,phase_g_inclusion_status,phase_g_source_audit_priority,copyleft_relevance_v6_1,copyleft_strategy_v6_1,copyleft_rationale_v6_1,preferred_boundary_model_v6_1,open_compliance_if_used_as_is_v6_1,reverse_engineer_if_proprietary_core_needed_v6_1,copyleft_strategy_confidence_v6_1,copyleft_manual_review_trigger_v6_1,as_is_incorporation_sensible_v6_1,v6_2_sre_layer,v6_2_sre_stratum,v6_2_sre_role,v6_2_sre_family,v6_2_related_kali_package,v6_2_related_upstream_repo,v6_2_kali_package_suffices_for_tool_execution,v6_2_upstream_repo_preferred_for_deep_eval,v6_2_index_page_followup_useful,v6_2_index_page_followup_reason,v6_2_sre_notes,v6_2_dnspy_ilspy_relevance,v6_3_source_of_truth,v6_3_merge_note,v6_3_live_state_2026_05_11,v6_3_reset_lane_2026_05_11,v6_3_reset_next_step_2026_05_11 -7701,HactarCE/Hyperspeedcube,https://github.com/HactarCE/Hyperspeedcube,HyperTwist,1.0,160.0,193.0,A,hypercubing / nD engine,foundation engine,simulation donor,locked core candidate,integrate,direct,"Keep the core engine or major subsystem mostly intact; change wrappers, branding, storage/auth, and integration seams so it becomes a first-class part of the target stack. For this repo class, that usually means preserving generalized puzzle/state/render logic while building a new application shell around it.",HactarCE/Hyperspeedcube — MIT OR Apache-2.0 — Modern 3D/4D puzzle simulator (thousands of puzzles). | This makes CubeForge the first true hypercubing training platform — solving every pain point while keeping the 3D core rock-solid.Exten...,"Integrate as a hypercubing / nD simulation subsystem for HyperTwist. Preserve the strongest existing pieces — nD state model, move notation, renderer, projection controls, solver/traversal logic, puzzle serialization, replay — and expose them behind a portfolio-stable interface. Wire first into cubing/cubing.js, then into tao-yu/Alg-Trainer for orchestration, visualization, or data exchange.","Consolidate under the Hyperspeedcube + cubing.js + qbr nucleus, not beside it as a separate silo. Normalize data contracts, auth/permissions, storage, and telemetry; then attach as a service, plugin, canvas layer, trainer, or analysis module. Descending combination order: cubing/cubing.js, tao-yu/Alg-Trainer, poliva/cubedex.",Repurpose here means: turn it into a higher-dimensional renderer/simulator donor and shared interaction grammar for HyperTwist and long-horizon VectorShell.,Map module boundaries; Identify hidden reusable internals; Define adapter/API boundary to target anchors; Write extraction tests against upstream behavior; Isolate puzzle/state core; Extract render/input abstractions; Document notation and save format,full subsystem extraction review,"Hidden value is likely in generalized puzzle/state representations, higher-dimensional transforms, notation systems, save formats, puzzle generators, and rendering abstractions.",Inspect generalized puzzle/state model; notation parser; transform math; rendering abstraction; save/load format; puzzle generator; input mapping; performance optimizations.,"Inspect package manifests, README/docs, src tree, examples, tests, CI workflows, config files, migrations/schemas, and hidden feature flags or experimental modules. Look for higher-dimensional state/notation representations, projection math, renderer abstractions, puzzle serialization, controls, and replay/training hooks.","Audit HactarCE/Hyperspeedcube as a hypercubing / nD engine candidate for HyperTwist. Do not stop at README-level features. Inspect: Inspect generalized puzzle/state model; notation parser; transform math; rendering abstraction; save/load format; puzzle generator; input mapping; performance optimizations. Decide whether the best extraction path is direct and whether it belongs as foundation engine / simulation donor. Test the three merger paths in order: 1) cubing/cubing.js [3D engine + notation/state donor]; 2) tao-yu/Alg-Trainer [training UX donor]; 3) cross-project transfer candidate [future merger]. Return hidden modules, reusable schemas, protocol layers, plugin hooks, render/state models, datasets/test fixtures, and any subsystem stronger than the visible product shell.",cubing/cubing.js,3D engine + notation/state donor,Use the partner for canonical state or rendering abstractions and merge this repo's specialized logic on top.,tao-yu/Alg-Trainer,training UX donor,Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.,cross-project transfer candidate,future merger,Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.,VectorShell | ScriptoriumAI,VectorShell can borrow spatial/rendering and perception primitives; ScriptoriumAI can borrow tutorial/educational visualization patterns rather than the full engine.,do not exclude,Keep in active merge-set and force full source audit before any demotion.,high,single-source signal; clear taxonomy; active integration value; foundation-level fit,high,portfolio anchor or repeatedly surfaced core candidate; memo mentions: 6,"Licensing intentionally ignored as a decision filter in this canonical evaluation; assess only architecture, capability, donor value, and concept transfer.",,,,"HactarCE/Hyperspeedcube — MIT OR Apache-2.0 — Modern 3D/4D puzzle simulator (thousands of puzzles). | This makes CubeForge the first true hypercubing training platform — solving every pain point while keeping the 3D core rock-solid.Extended Comprehensive Open-Source Building Blocks (April 2026)Updated exhaustive scan — focused on high-value for your codebase (simulators, trainers, vision, hyper).MIT or Apache Licensed (Fully permissive — fork/abs",HactarCE/Hyperspeedcube is treated as integrate for HyperTwist because visible metadata points to the hypercubing / nD simulation layer. Surface signal: HactarCE/Hyperspeedcube — MIT OR Apache-2.0 — Modern 3D/4D puzzle simulator (thousands of puzzles). | This makes CubeForge the first true hypercubing training platform — solving every pain point while keeping the 3D core rock-solid.Exten... The likely value is substantial enough to preserve as a named subsystem rather than just mining isolated ideas.,memo,False,True,0.0,6.0,HT_hyper_engine,HT_hyper_engine_0001,hypercubing / nD simulation,Integrate as a shared building block across at least two projects. Its memo and bookmark signals place it in the hypercubing / nD simulation layer.,multi-project,hypercubing / nD simulation,integrate,direct,medium,hactarce/hyperspeedcube,HyperTwist,,,,,,,,,,,,,,,,Original global operational v3 retained,MIT,known_from_reference_material,uploaded_reference_docs,yes,hypertwist_and_scriptoriumai,HyperTwist,HyperTwist & ScriptoriumAI.txt,Supplemental intake references are advisory only; v6 adjudication remains the source of truth.,Potentially relevant,yes,v6 unified all-project source-of-truth pack,v5_carry_forward,Existing v5 row reaffirmed or widened by v6 supplemental intake.,1.0,5,160.0,,,,,permissive_or_noncopyleft_known,direct_incorporation_ok,"This repo is aligned with a direct integration path for HyperTwist because it is either already implemented, strategically central, or donor-grade without a visible copyleft constraint in the current materials. Deep incorporation is sensible if the source audit confirms architectural cleanliness.","Direct embed, vendored module, package dependency, or tightly integrated adapter as the architecture requires.","Typically preserve notices, attribution, and license text where required; no special copyleft-driven disclosure posture is normally needed.",Usually unnecessary unless you later decide the existing implementation is too constraining architecturally.,high,strategic-or-implemented-component,yes,,,,,,,,,,,,,v6.3_final_source_of_truth,Merged v6.1 copyleft layer and v6.2 SRE layer; use v6.3 docs + workbook as canonical handoff.,selected_not_live_permissive_candidate,phase0r_permissive_eval_then_implement,"Phase 1R closed. Retain as a Phase 3R permissive implementation candidate; implement only from its packet authority and the retained-set contract, not by reopening Phase 0R." +7701,HactarCE/Hyperspeedcube,https://github.com/HactarCE/Hyperspeedcube,HyperTwist,1.0,160.0,193.0,A,hypercubing / nD engine,foundation engine,simulation donor,locked core candidate,integrate,direct,"Keep the core engine or major subsystem mostly intact; change wrappers, branding, storage/auth, and integration seams so it becomes a first-class part of the target stack. For this repo class, that usually means preserving generalized puzzle/state/render logic while building a new application shell around it.",HactarCE/Hyperspeedcube — MIT OR Apache-2.0 — Modern 3D/4D puzzle simulator (thousands of puzzles). | This makes CubeForge the first true hypercubing training platform — solving every pain point while keeping the 3D core rock-solid.Exten...,"Integrate as a hypercubing / nD simulation subsystem for HyperTwist. Preserve the strongest existing pieces — nD state model, move notation, renderer, projection controls, solver/traversal logic, puzzle serialization, replay — and expose them behind a portfolio-stable interface. Wire first into cubing/cubing.js, then into tao-yu/Alg-Trainer for orchestration, visualization, or data exchange.","Consolidate under the Hyperspeedcube + cubing.js + qbr nucleus, not beside it as a separate silo. Normalize data contracts, auth/permissions, storage, and telemetry; then attach as a service, plugin, canvas layer, trainer, or analysis module. Descending combination order: cubing/cubing.js, tao-yu/Alg-Trainer, poliva/cubedex.",Repurpose here means: turn it into a higher-dimensional renderer/simulator donor and shared interaction grammar for HyperTwist and long-horizon VectorShell.,Map module boundaries; Identify hidden reusable internals; Define adapter/API boundary to target anchors; Write extraction tests against upstream behavior; Isolate puzzle/state core; Extract render/input abstractions; Document notation and save format,full subsystem extraction review,"Hidden value is likely in generalized puzzle/state representations, higher-dimensional transforms, notation systems, save formats, puzzle generators, and rendering abstractions.",Inspect generalized puzzle/state model; notation parser; transform math; rendering abstraction; save/load format; puzzle generator; input mapping; performance optimizations.,"Inspect package manifests, README/docs, src tree, examples, tests, CI workflows, config files, migrations/schemas, and hidden feature flags or experimental modules. Look for higher-dimensional state/notation representations, projection math, renderer abstractions, puzzle serialization, controls, and replay/training hooks.","Audit HactarCE/Hyperspeedcube as a hypercubing / nD engine candidate for HyperTwist. Do not stop at README-level features. Inspect: Inspect generalized puzzle/state model; notation parser; transform math; rendering abstraction; save/load format; puzzle generator; input mapping; performance optimizations. Decide whether the best extraction path is direct and whether it belongs as foundation engine / simulation donor. Test the three merger paths in order: 1) cubing/cubing.js [3D engine + notation/state donor]; 2) tao-yu/Alg-Trainer [training UX donor]; 3) cross-project transfer candidate [future merger]. Return hidden modules, reusable schemas, protocol layers, plugin hooks, render/state models, datasets/test fixtures, and any subsystem stronger than the visible product shell.",cubing/cubing.js,3D engine + notation/state donor,Use the partner for canonical state or rendering abstractions and merge this repo's specialized logic on top.,tao-yu/Alg-Trainer,training UX donor,Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.,cross-project transfer candidate,future merger,Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.,VectorShell | ScriptoriumAI,VectorShell can borrow spatial/rendering and perception primitives; ScriptoriumAI can borrow tutorial/educational visualization patterns rather than the full engine.,do not exclude,Keep in active merge-set and force full source audit before any demotion.,high,single-source signal; clear taxonomy; active integration value; foundation-level fit,high,portfolio anchor or repeatedly surfaced core candidate; memo mentions: 6,"Licensing intentionally ignored as a decision filter in this canonical evaluation; assess only architecture, capability, donor value, and concept transfer.",,,,"HactarCE/Hyperspeedcube — MIT OR Apache-2.0 — Modern 3D/4D puzzle simulator (thousands of puzzles). | This makes CubeForge the first true hypercubing training platform — solving every pain point while keeping the 3D core rock-solid.Extended Comprehensive Open-Source Building Blocks (April 2026)Updated exhaustive scan — focused on high-value for your codebase (simulators, trainers, vision, hyper).MIT or Apache Licensed (Fully permissive — fork/abs",HactarCE/Hyperspeedcube is treated as integrate for HyperTwist because visible metadata points to the hypercubing / nD simulation layer. Surface signal: HactarCE/Hyperspeedcube — MIT OR Apache-2.0 — Modern 3D/4D puzzle simulator (thousands of puzzles). | This makes CubeForge the first true hypercubing training platform — solving every pain point while keeping the 3D core rock-solid.Exten... The likely value is substantial enough to preserve as a named subsystem rather than just mining isolated ideas.,memo,False,True,0.0,6.0,HT_hyper_engine,HT_hyper_engine_0001,hypercubing / nD simulation,Integrate as a shared building block across at least two projects. Its memo and bookmark signals place it in the hypercubing / nD simulation layer.,multi-project,hypercubing / nD simulation,integrate,direct,medium,hactarce/hyperspeedcube,HyperTwist,,,,,,,,,,,,,,,,Original global operational v3 retained,MIT,known_from_reference_material,uploaded_reference_docs,yes,hypertwist_and_scriptoriumai,HyperTwist,HyperTwist & ScriptoriumAI.txt,Supplemental intake references are advisory only; v6 adjudication remains the source of truth.,Potentially relevant,yes,v6 unified all-project source-of-truth pack,v5_carry_forward,Existing v5 row reaffirmed or widened by v6 supplemental intake.,1.0,5,160.0,,,,,permissive_or_noncopyleft_known,direct_incorporation_ok,"This repo is aligned with a direct integration path for HyperTwist because it is either already implemented, strategically central, or donor-grade without a visible copyleft constraint in the current materials. Deep incorporation is sensible if the source audit confirms architectural cleanliness.","Direct embed, vendored module, package dependency, or tightly integrated adapter as the architecture requires.","Typically preserve notices, attribution, and license text where required; no special copyleft-driven disclosure posture is normally needed.",Usually unnecessary unless you later decide the existing implementation is too constraining architecturally.,high,strategic-or-implemented-component,yes,,,,,,,,,,,,,v6.3_final_source_of_truth,Merged v6.1 copyleft layer and v6.2 SRE layer; use v6.3 docs + workbook as canonical handoff.,implemented_live_permissive,landed_permissive_preserve,"Phase 3R-E closed. Preserve as the landed first-party embodied companion, narration, lip-sync, gesture, subtitle, and avatar-embed lane; start future widening from the live-lane audit, then the 3R-E implementation packet, then REPO_LICENSE_TRACKING.md." 7704,SYSTRAN/faster-whisper,https://github.com/SYSTRAN/faster-whisper,multi-project,1.0,71.0,80.0,C,voice / multimodal I/O,subsystem donor,multimodal donor,donor bench,repurpose,moderate modification,"Retain the valuable internal engine, but expect to replace UI/product shell, adapt schemas/APIs, and refactor boundaries so it can plug into the target anchors cleanly. For this repo class, that usually means preserving parsers/graph schema/indexing while swapping layout, storage, or UX layers.",huggingface/faster-whisper – https://github.com/SYSTRAN/faster-whisper – MIT – Fast Whisper STT.,"Repurpose selected subsystems rather than the whole product. Mine the repo for VAD-aware segmentation, batch transcription, timestamps, hotword and prefix conditioning, and Python service ergonomics; keep what materially shortens build time, but rebind data contracts, permissions, storage, and deployment to the target architecture. Best first pairing order: ggml-org/whisper.cpp, rhasspy/piper, coqui-ai/TTS.","Consolidate under the project-specific anchor stack, not beside it as a separate silo. Normalize data contracts, auth/permissions, storage, and telemetry; then attach as a service, plugin, canvas layer, trainer, or analysis module. Descending combination order: sentrux/sentrux, HactarCE/Hyperspeedcube, outline/outline.","Repurpose here means: turn it into a Python STT service, timestamped speech pipeline, or batch transcription donor.",Map module boundaries; Identify hidden reusable internals; Define adapter/API boundary to target anchors; Write extraction tests against upstream behavior; Normalize graph schema; Decouple parser/indexer from UI; Expose query and layout services,deep source audit,"Hidden value may sit in AST/indexing pipelines, call/dependency graph schema, incremental refresh, layout heuristics, graph query APIs, and serialization formats that can be lifted into VectorShell.",Inspect transcription API and dataclasses; batched inference; VAD chunking; word timestamps; hotwords and prefix conditioning; service-layer boundaries; benchmark and test coverage.,"Inspect package manifests, README/docs, src tree, examples, tests, CI workflows, benchmark scripts, and hidden experimental modules. Look for VAD, batch inference, timestamps, hotwords, model/runtime constraints, and service-layer boundaries.","Audit SYSTRAN/faster-whisper as a voice / multimodal I/O candidate for multi-project. Do not stop at README-level features. Inspect: transcription API and dataclasses, batched inference, VAD chunking, word timestamps, hotwords and prefix conditioning, service-layer boundaries, and benchmark/test coverage. Decide whether it should remain the primary Python STT donor and what should stay behind a bounded Python service seam. Test the three merger paths in order: 1) project-local anchor [base + donor]; 2) shared portfolio utility [augmenter]; 3) cross-project transfer candidate [future merger]. Return hidden modules, reusable schemas, protocol layers, runtime boundaries, tests/benchmarks, and any subsystem stronger than the visible shell.",project-local anchor,base + donor,Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.,shared portfolio utility,augmenter,Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.,cross-project transfer candidate,future merger,Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.,project-local first,"Cross-project transfer is possible, but the value is clearest inside the assigned project until source audit exposes more reusable primitives.","exclude from core, keep as donor","Do not let it consume roadmap as a full product shell; mine reusable engines, adapters, schemas, UX patterns, or datasets.",medium-low,single-source signal; clear taxonomy; mostly donor/reference role,medium,memo mentions: 1,"Licensing intentionally ignored as a decision filter in this canonical evaluation; assess only architecture, capability, donor value, and concept transfer.",,,,huggingface/faster-whisper – https://github.com/SYSTRAN/faster-whisper – MIT – Fast Whisper STT.,"SYSTRAN/faster-whisper is treated as repurpose for multi-project because visible metadata points to the voice / speech / audio layer. Surface signal: huggingface/faster-whisper – https://github.com/SYSTRAN/faster-whisper – MIT – Fast Whisper STT. The fit looks real, but more as a donor/augmenter than as a standalone foundation.",memo,False,True,0.0,1.0,MU_misc,MU_misc_0001,voice / speech / audio,"Repurpose selectively for multi-project. Its source-backed role is a bounded Python STT donor and service-layer candidate, not an exclusion-only adjunct.",future/adjacent use,voice / speech / audio,repurpose,moderate modification,medium,systran/faster-whisper,multi-project,,,,,,,,,,,,,,,,Original global operational v3 retained,MIT,known_from_reference_material,uploaded_reference_docs,no,,,,Supplemental intake references are advisory only; v6 adjudication remains the source of truth.,Usually indirect,yes,v6 unified all-project source-of-truth pack,v5_carry_forward,,1.0,5,71.0,,,,,permissive_or_noncopyleft_known,direct_incorporation_ok,"The code license is MIT and direct use is allowed. Treat it as a bounded Python STT donor/service candidate; review chosen model checkpoints separately, but no clean-room path is required by default.",Use directly as a bounded Python STT service or adapter layer; keep model/runtime selection and deployment behind a speech-input seam.,"Typically preserve notices, attribution, and license text where required; review selected model checkpoints separately from the code license.",Usually unnecessary unless you later decide to replace a narrow hot path or remove Python/CTranslate2 dependencies.,high,model-artifact-review-required,yes,,,,,,,,,,,,,v6.3_final_source_of_truth,Merged v6.1 copyleft layer and v6.2 SRE layer; use v6.3 docs + workbook as canonical handoff.,,, 7705,cubing/alg.js,https://github.com/cubing/alg.js,HyperTwist,2.0,95.0,95.0,P0,puzzle_simulation_training_donor,puzzle_simulation_training_donor,geometry_renderer_or_binding,donor bench,repurpose,architecture only,"Moderate modification. Treat cubing/alg.js as a family-level donor for HyperTwist: extract the implementation layer that matches its strongest domain contribution, preserve its protocols/data models/CLI or renderer boundaries, and adapt only the surface integration needed for HyperTwist rather than rewriting it wholesale.","HyperTwist family. Likely value lies in puzzle logic, scrambler design, algorithm representations, n-dimensional geometry, rendering, bindings, or XR/game-engine surfaces relevant to hypercube and cube-training workflows.","Primary realization path: use as a simulation, training, renderer, binding, or integration donor inside HyperTwist's dual stack of physical-cube analysis and higher-dimensional virtual training.","Consolidate by HyperTwist layer: core puzzle logic, scramblers/algs, renderer/bindings, XR/game-engine surfaces, experiments/comparators.","Repurpose toward renderer abstractions, puzzle-logic libraries, solver bindings, training UIs, or XR/engine adapters.","Verify actual capability surface, identify reusable subsystems, confirm integration boundary, test output formats, and decide whether promotion or demotion is justified after source inspection.","P0 tier audit. Inspect state representations, move/alg parsers, scrambler generators, geometry/math cores, renderer abstractions, engine bindings, and XR/web surfaces.",cubing/alg.js may hide higher-value reusable components in its cubing family than its surface framing suggests; inspect internals before treating it as merely a category duplicate.,"Inspect state representations, move/alg parsers, scrambler generators, geometry/math cores, renderer abstractions, engine bindings, and XR/web surfaces.","Inspect state representations, move/alg parsers, scrambler generators, geometry/math cores, renderer abstractions, engine bindings, and XR/web surfaces.","Inspect cubing/alg.js at source level. Extract actual implemented capabilities, hidden modules, extension hooks, data models, and output contracts. Re-rank only if source evidence materially changes its donor/foundation potential for HyperTwist.",HactarCE/Hyperspeedcube,foundation repo + feature donor,"Use cubing/alg.js as a HyperTwist donor into HactarCE/Hyperspeedcube for puzzle logic, bindings, renderer ideas, or training/runtime augmentation.",cubing/cubing.js,engine repo + interface donor,"Use cubing/alg.js as a HyperTwist donor into cubing/cubing.js for puzzle logic, bindings, renderer ideas, or training/runtime augmentation.",kkoomen/qbr,feature extraction only,"Use cubing/alg.js as a HyperTwist donor into kkoomen/qbr for puzzle logic, bindings, renderer ideas, or training/runtime augmentation.",multi-project,"Source audit may reveal reusable abstractions that travel beyond the initially assigned project, especially in control-plane, visualization, renderer, or document/AI pipeline layers.","Do not omit for licensing. Exclude only from current horizon if source audit shows it is purely documentation, governance, packaging noise, or a weak duplicate with no meaningful reusable subsystem.","Current placement is preliminary and based on family fit, repo naming, and source grouping rather than source code inspection.",medium,"Pre-source-audit supplemental intake classification derived from source group, owner family, project fit, and project-wide design language.",medium,Will increase only after direct source inspection.,Licensing intentionally ignored as a decision filter per canonical directive; license is tracked separately only for optional review and packaging choices.,HyperTwist,HyperTwist,,Supplemental intake row added from v6 source-group expansion; reference docs may further inform merger logic.,"cubing/alg.js enters the corpus through the v6 supplemental intake. It is treated as donor bench for HyperTwist because its family suggests value in hypertwist family. likely value lies in puzzle logic, scrambler design, algorithm representations, n-dimensional geometry, rendering, bindings, or xr/game-engine surfaces relevant to hypercube and cube-training workflows. Its current judgment is intentionally provisional and should be upgraded or downgraded only after direct source inspection.",HyperTwist & ScriptoriumAI.txt,0,0,1.0,0.0,HT_cube_semantics,HT_cube_semantics_0002,puzzle_simulation_training_donor,Supplemental v6 intake from hypertwist_and_scriptoriumai; preliminary classification only.,HyperTwist,puzzle_simulation_training_donor,donor candidate,moderate modification,medium,cubing/alg.js,HyperTwist,supplemental_v6_not_runtime_anchored,,,,,,,,,,,no,,,,v6_unified_source_of_truth,GPL-3.0-or-later,known_from_reference_material,uploaded_reference_docs,yes,hypertwist_and_scriptoriumai,HyperTwist,HyperTwist & ScriptoriumAI.txt,"Supplemental intake references and prior Grok/initial-research docs used as reference, not as source of truth.",Usually indirect,yes,v6 unified all-project source-of-truth pack,v6_supplemental_intake,New row created from supplemental intake (POO/Security/Agent/HyperTwist-ScriptoriumAI/Kali/Consider II).,2.0,1,95.0,Donor Bench,Focused restrictive clean-room donor target,,P2,mixed_or_boundary_sensitive_known,reverse_engineer_preferred,The repo is GPL-3.0-or-later and should remain a focused clean-room donor lane rather than direct donor code. Preserve the parser/AST/traversal semantics through a scrubbed Model A handoff only.,Model A may inspect the restrictive source; Model B should implement only from a scrubbed first-party specification.,Direct incorporation would require GPL-compatible distribution/compliance and is not the planned HyperTwist path.,Yes — preferred path for reproducing parser/AST/traversal semantics in first-party code.,high,gpl-clean-room-donor,no,,,,,,,,,,,,,v6.3_final_source_of_truth,Assigned to HT_cube_semantics during cluster normalization on 2026-04-25.,selected_not_live_clean_room_candidate,phase0r_clean_room_eval_then_model_a_model_b,Phase 1R closed. Retain as a Phase 5R clean-room-only algorithm-language candidate; implement only from the scrubbed Model A dossier and retained-set contract. 7707,cubing/twisty.js,https://github.com/cubing/twisty.js,HyperTwist,2.0,95.0,95.0,P0,puzzle_simulation_training_donor,puzzle_simulation_training_donor,geometry_renderer_or_binding,donor bench,repurpose,architecture only,"Moderate modification. Treat cubing/twisty.js as a family-level donor for HyperTwist: extract the implementation layer that matches its strongest domain contribution, preserve its protocols/data models/CLI or renderer boundaries, and adapt only the surface integration needed for HyperTwist rather than rewriting it wholesale.","HyperTwist family. Likely value lies in puzzle logic, scrambler design, algorithm representations, n-dimensional geometry, rendering, bindings, or XR/game-engine surfaces relevant to hypercube and cube-training workflows.","Primary realization path: use as a simulation, training, renderer, binding, or integration donor inside HyperTwist's dual stack of physical-cube analysis and higher-dimensional virtual training.","Consolidate by HyperTwist layer: core puzzle logic, scramblers/algs, renderer/bindings, XR/game-engine surfaces, experiments/comparators.","Repurpose toward renderer abstractions, puzzle-logic libraries, solver bindings, training UIs, or XR/engine adapters.","Verify actual capability surface, identify reusable subsystems, confirm integration boundary, test output formats, and decide whether promotion or demotion is justified after source inspection.","P0 tier audit. Inspect state representations, move/alg parsers, scrambler generators, geometry/math cores, renderer abstractions, engine bindings, and XR/web surfaces.",cubing/twisty.js may hide higher-value reusable components in its cubing family than its surface framing suggests; inspect internals before treating it as merely a category duplicate.,"Inspect state representations, move/alg parsers, scrambler generators, geometry/math cores, renderer abstractions, engine bindings, and XR/web surfaces.","Inspect state representations, move/alg parsers, scrambler generators, geometry/math cores, renderer abstractions, engine bindings, and XR/web surfaces.","Inspect cubing/twisty.js at source level. Extract actual implemented capabilities, hidden modules, extension hooks, data models, and output contracts. Re-rank only if source evidence materially changes its donor/foundation potential for HyperTwist.",HactarCE/Hyperspeedcube,foundation repo + feature donor,"Use cubing/twisty.js as a HyperTwist donor into HactarCE/Hyperspeedcube for puzzle logic, bindings, renderer ideas, or training/runtime augmentation.",cubing/cubing.js,engine repo + interface donor,"Use cubing/twisty.js as a HyperTwist donor into cubing/cubing.js for puzzle logic, bindings, renderer ideas, or training/runtime augmentation.",kkoomen/qbr,feature extraction only,"Use cubing/twisty.js as a HyperTwist donor into kkoomen/qbr for puzzle logic, bindings, renderer ideas, or training/runtime augmentation.",multi-project,"Source audit may reveal reusable abstractions that travel beyond the initially assigned project, especially in control-plane, visualization, renderer, or document/AI pipeline layers.","Do not omit for licensing. Exclude only from current horizon if source audit shows it is purely documentation, governance, packaging noise, or a weak duplicate with no meaningful reusable subsystem.","Current placement is preliminary and based on family fit, repo naming, and source grouping rather than source code inspection.",medium,"Pre-source-audit supplemental intake classification derived from source group, owner family, project fit, and project-wide design language.",medium,Will increase only after direct source inspection.,Licensing intentionally ignored as a decision filter per canonical directive; license is tracked separately only for optional review and packaging choices.,HyperTwist,HyperTwist,,Supplemental intake row added from v6 source-group expansion; reference docs may further inform merger logic.,"cubing/twisty.js enters the corpus through the v6 supplemental intake. It is treated as donor bench for HyperTwist because its family suggests value in hypertwist family. likely value lies in puzzle logic, scrambler design, algorithm representations, n-dimensional geometry, rendering, bindings, or xr/game-engine surfaces relevant to hypercube and cube-training workflows. Its current judgment is intentionally provisional and should be upgraded or downgraded only after direct source inspection.",HyperTwist & ScriptoriumAI.txt,0,0,1.0,0.0,HT_cube_semantics,HT_cube_semantics_0003,puzzle_simulation_training_donor,Supplemental v6 intake from hypertwist_and_scriptoriumai; preliminary classification only.,HyperTwist,puzzle_simulation_training_donor,donor candidate,moderate modification,medium,cubing/twisty.js,HyperTwist,supplemental_v6_not_runtime_anchored,,,,,,,,,,,no,,,,v6_unified_source_of_truth,GPL-3.0-or-later,known_from_reference_material,uploaded_reference_docs,yes,hypertwist_and_scriptoriumai,HyperTwist,HyperTwist & ScriptoriumAI.txt,"Supplemental intake references and prior Grok/initial-research docs used as reference, not as source of truth.",Usually indirect,yes,v6 unified all-project source-of-truth pack,v6_supplemental_intake,New row created from supplemental intake (POO/Security/Agent/HyperTwist-ScriptoriumAI/Kali/Consider II).,2.0,1,95.0,Donor Bench,Focused restrictive clean-room donor target,,P2,mixed_or_boundary_sensitive_known,reverse_engineer_preferred,"The repo is GPL-3.0-or-later and should remain a focused clean-room donor lane rather than direct donor code. Preserve viewer/player shell, scrubber, and twisty-element behavior through a scrubbed Model A handoff only.",Model A may inspect the restrictive source; Model B should implement only from a scrubbed first-party specification.,Direct incorporation would require GPL-compatible distribution/compliance and is not the planned HyperTwist path.,Yes — preferred path for reproducing compact twisty-viewer behavior in first-party code.,high,gpl-clean-room-donor,no,,,,,,,,,,,,,v6.3_final_source_of_truth,Assigned to HT_cube_semantics during cluster normalization on 2026-04-25.,selected_not_live_clean_room_candidate,phase0r_clean_room_eval_then_model_a_model_b,Phase 1R closed. Retain as a Phase 5R clean-room-only embedded viewer candidate; implement only from the scrubbed Model A dossier and retained-set contract. 7709,HactarCE/2x2x2x2-Scrambler,https://github.com/HactarCE/2x2x2x2-Scrambler,HyperTwist,2.0,63.0,63.0,P2,puzzle_simulation_training_donor,puzzle_simulation_training_donor,geometry_renderer_or_binding,donor bench,repurpose,architecture only,"Architecture only. Treat HactarCE/2x2x2x2-Scrambler as a design and subsystem reference first; source audit should look for transplantable patterns, adapters, data contracts, pipeline ideas, or UI/control abstractions before any decision to operationalize.","HyperTwist family. Likely value lies in puzzle logic, scrambler design, algorithm representations, n-dimensional geometry, rendering, bindings, or XR/game-engine surfaces relevant to hypercube and cube-training workflows.","Primary realization path: use as a simulation, training, renderer, binding, or integration donor inside HyperTwist's dual stack of physical-cube analysis and higher-dimensional virtual training.","Consolidate by HyperTwist layer: core puzzle logic, scramblers/algs, renderer/bindings, XR/game-engine surfaces, experiments/comparators.","Repurpose toward renderer abstractions, puzzle-logic libraries, solver bindings, training UIs, or XR/engine adapters.","Verify actual capability surface, identify reusable subsystems, confirm integration boundary, test output formats, and decide whether promotion or demotion is justified after source inspection.","P2 tier audit. Inspect state representations, move/alg parsers, scrambler generators, geometry/math cores, renderer abstractions, engine bindings, and XR/web surfaces.",HactarCE/2x2x2x2-Scrambler may hide higher-value reusable components in its HactarCE family than its surface framing suggests; inspect internals before treating it as merely a category duplicate.,"Inspect state representations, move/alg parsers, scrambler generators, geometry/math cores, renderer abstractions, engine bindings, and XR/web surfaces.","Inspect state representations, move/alg parsers, scrambler generators, geometry/math cores, renderer abstractions, engine bindings, and XR/web surfaces.","Inspect HactarCE/2x2x2x2-Scrambler at source level. Extract actual implemented capabilities, hidden modules, extension hooks, data models, and output contracts. Re-rank only if source evidence materially changes its donor/foundation potential for HyperTwist.",HactarCE/Hyperspeedcube,foundation repo + feature donor,"Use HactarCE/2x2x2x2-Scrambler as a HyperTwist donor into HactarCE/Hyperspeedcube for puzzle logic, bindings, renderer ideas, or training/runtime augmentation.",cubing/cubing.js,engine repo + interface donor,"Use HactarCE/2x2x2x2-Scrambler as a HyperTwist donor into cubing/cubing.js for puzzle logic, bindings, renderer ideas, or training/runtime augmentation.",kkoomen/qbr,feature extraction only,"Use HactarCE/2x2x2x2-Scrambler as a HyperTwist donor into kkoomen/qbr for puzzle logic, bindings, renderer ideas, or training/runtime augmentation.",multi-project,"Source audit may reveal reusable abstractions that travel beyond the initially assigned project, especially in control-plane, visualization, renderer, or document/AI pipeline layers.","Do not omit for licensing. Exclude only from current horizon if source audit shows it is purely documentation, governance, packaging noise, or a weak duplicate with no meaningful reusable subsystem.","Current placement is preliminary and based on family fit, repo naming, and source grouping rather than source code inspection.",low-to-medium,"Pre-source-audit supplemental intake classification derived from source group, owner family, project fit, and project-wide design language.",low-to-medium,Will increase only after direct source inspection.,Licensing intentionally ignored as a decision filter per canonical directive; license is tracked separately only for optional review and packaging choices.,HyperTwist,HyperTwist,,Supplemental intake row added from v6 source-group expansion; reference docs may further inform merger logic.,"HactarCE/2x2x2x2-Scrambler enters the corpus through the v6 supplemental intake. It is treated as reserve bench for HyperTwist because its family suggests value in hypertwist family. likely value lies in puzzle logic, scrambler design, algorithm representations, n-dimensional geometry, rendering, bindings, or xr/game-engine surfaces relevant to hypercube and cube-training workflows. Its current judgment is intentionally provisional and should be upgraded or downgraded only after direct source inspection.",HyperTwist & ScriptoriumAI.txt,0,0,1.0,0.0,HT_cube_semantics,HT_cube_semantics_0004,puzzle_simulation_training_donor,Supplemental v6 intake from hypertwist_and_scriptoriumai; preliminary classification only.,HyperTwist,puzzle_simulation_training_donor,future candidate,architecture only,low-to-medium,hactarce/2x2x2x2-scrambler,HyperTwist,supplemental_v6_not_runtime_anchored,,,,,,,,,,,no,,,,v6_unified_source_of_truth,GPL-3.0,known_from_reference_material,uploaded_reference_docs,yes,hypertwist_and_scriptoriumai,HyperTwist,HyperTwist & ScriptoriumAI.txt,"Supplemental intake references and prior Grok/initial-research docs used as reference, not as source of truth.",Usually indirect,yes,v6 unified all-project source-of-truth pack,v6_supplemental_intake,New row created from supplemental intake (POO/Security/Agent/HyperTwist-ScriptoriumAI/Kali/Consider II).,2.0,3,63.0,Donor Bench,Focused restrictive clean-room donor target,,P2,mixed_or_boundary_sensitive_known,reverse_engineer_preferred,The repo is GPL-3.0 and the source explicitly notes a ported lineage from an earlier scrambler. Retain it only as a focused clean-room donor target and implement any valuable behavior through a scrubbed first-party specification.,Model A may inspect the restrictive source; Model B should implement only from a scrubbed first-party specification.,Direct incorporation would require GPL-compatible distribution/compliance and is not the planned HyperTwist path.,Yes — this is the preferred path for reproducing the 2x2x2x2 scrambler/state behaviors in first-party code.,high,gpl-clean-room-donor,no,,,,,,,,,,,,,v6.3_final_source_of_truth,Assigned to HT_cube_semantics during cluster normalization on 2026-04-25.,selected_not_live_clean_room_candidate,phase0r_clean_room_eval_then_model_a_model_b,Phase 1R closed. Retain as a Phase 5R clean-room-only Melinda 2x2x2x2 candidate; keep copied-port lineage explicit and implement only from the scrubbed Model A dossier. -7814,kkoomen/qbr,https://github.com/kkoomen/qbr,HyperTwist,2.0,158.0,191.0,A,vision / perception / AR,foundation engine,vision donor,locked core candidate,integrate,direct,"Keep the core engine or major subsystem mostly intact; change wrappers, branding, storage/auth, and integration seams so it becomes a first-class part of the target stack. For this repo class, that usually means preserving calibration/detection/state-reconstruction logic while replacing camera UX and integration surfaces.","kkoomen/qbr — MIT — Webcam-based 3x3 solver with accurate OpenCV color detection (perfect vision starter). | kkoomen/qbr — MIT — Webcam CV solver (base for 3D vision). | kkoomen/qbr — MIT — Webcam CV color detection. | poliva/cubedex, ta...","Integrate as a computer vision / AR subsystem for HyperTwist. Preserve the strongest existing pieces — camera ingest, calibration, segmentation/detection, pose or facelet extraction, state normalization, solver bridge, replay overlay, AR anchors — and expose them behind a portfolio-stable interface. Wire first into vivaansinghvi07/rubix-cube-solver, then into cubing/cubing.js for orchestration, visualization, or data exchange.","Consolidate under the Hyperspeedcube + cubing.js + qbr nucleus, not beside it as a separate silo. Normalize data contracts, auth/permissions, storage, and telemetry; then attach as a service, plugin, canvas layer, trainer, or analysis module. Descending combination order: vivaansinghvi07/rubix-cube-solver, cubing/cubing.js, HactarCE/Hyperspeedcube.","Repurpose here means: turn it into a perception microservice, cube-state API, replay generator, or AR overlay donor for HyperTwist.",Map module boundaries; Identify hidden reusable internals; Define adapter/API boundary to target anchors; Write extraction tests against upstream behavior; Benchmark calibration pipeline; Extract state reconstruction; Wrap with camera/AR adapter,full subsystem extraction review,"Hidden value often sits in calibration, preprocessing, stabilization, object/state reconstruction, replay artifacts, and camera-to-domain state pipelines that are not obvious from demos.",Inspect preprocessing/calibration; tracking stabilization; state reconstruction; replay/event model; camera abstraction; fallback heuristics; testing assets/videos; performance shortcuts.,"Inspect package manifests, README/docs, src tree, examples, tests, CI workflows, config files, migrations/schemas, and hidden feature flags or experimental modules. Look for calibration routines, detection heuristics/models, color/state normalization, replay serialization, solver bridges, camera abstraction layers, and debug visualizations.","Audit kkoomen/qbr as a vision / perception / AR candidate for HyperTwist. Do not stop at README-level features. Inspect: Inspect preprocessing/calibration; tracking stabilization; state reconstruction; replay/event model; camera abstraction; fallback heuristics; testing assets/videos; performance shortcuts. Decide whether the best extraction path is direct and whether it belongs as foundation engine / vision donor. Test the three merger paths in order: 1) vivaansinghvi07/rubix-cube-solver [perception + replay donor]; 2) cubing/cubing.js [state/render backend]; 3) cross-project transfer candidate [future merger]. Return hidden modules, reusable schemas, protocol layers, plugin hooks, render/state models, datasets/test fixtures, and any subsystem stronger than the visible product shell.",vivaansinghvi07/rubix-cube-solver,perception + replay donor,Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.,cubing/cubing.js,state/render backend,Use the partner for canonical state or rendering abstractions and merge this repo's specialized logic on top.,cross-project transfer candidate,future merger,Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.,VectorShell | ScriptoriumAI,VectorShell can borrow spatial/rendering and perception primitives; ScriptoriumAI can borrow tutorial/educational visualization patterns rather than the full engine.,do not exclude,Keep in active merge-set and force full source audit before any demotion.,high,single-source signal; clear taxonomy; active integration value; foundation-level fit,high,portfolio anchor or repeatedly surfaced core candidate; memo mentions: 5,"Licensing intentionally ignored as a decision filter in this canonical evaluation; assess only architecture, capability, donor value, and concept transfer.",,,,"kkoomen/qbr — MIT — Webcam-based 3x3 solver with accurate OpenCV color detection (perfect vision starter). | kkoomen/qbr — MIT — Webcam CV solver (base for 3D vision). | kkoomen/qbr — MIT — Webcam CV color detection. | poliva/cubedex, tao-yu/Alg-Trainer, kkoomen/qbr, vivaansinghvi07/rubix-cube-solver, NuiLab/code-vr, molgenis/Graph2VR (core permissive parts), brianpeiris/RiftSketch, aMonteSl/CodeXR.","kkoomen/qbr is treated as integrate for HyperTwist because visible metadata points to the computer vision / AR layer. Surface signal: kkoomen/qbr — MIT — Webcam-based 3x3 solver with accurate OpenCV color detection (perfect vision starter). | kkoomen/qbr — MIT — Webcam CV solver (base for 3D vision). | kkoomen/qbr — MIT — Webcam CV color detection. | poliva/cubedex, ta... The likely value is substantial enough to preserve as a named subsystem rather than just mining isolated ideas.",memo,False,True,0.0,5.0,HT_cube_vision,HT_cube_vision_0001,computer vision / AR,Integrate as a shared building block across at least two projects. Its memo and bookmark signals place it in the computer vision / AR layer.,multi-project,computer vision / AR,integrate,heavy modification,medium,kkoomen/qbr,HyperTwist,,,,,,,,,,,,,,,,Original global operational v3 retained,MIT,known_from_reference_material,uploaded_reference_docs,no,,,,Supplemental intake references are advisory only; v6 adjudication remains the source of truth.,Potentially relevant,yes,v6 unified all-project source-of-truth pack,v5_carry_forward,,2.0,5,158.0,,,,,permissive_or_noncopyleft_known,direct_incorporation_ok,"This repo is aligned with a direct integration path for HyperTwist because it is either already implemented, strategically central, or donor-grade without a visible copyleft constraint in the current materials. Deep incorporation is sensible if the source audit confirms architectural cleanliness.","Direct embed, vendored module, package dependency, or tightly integrated adapter as the architecture requires.","Typically preserve notices, attribution, and license text where required; no special copyleft-driven disclosure posture is normally needed.",Usually unnecessary unless you later decide the existing implementation is too constraining architecturally.,high,strategic-or-implemented-component,yes,,,,,,,,,,,,,v6.3_final_source_of_truth,Merged v6.1 copyleft layer and v6.2 SRE layer; use v6.3 docs + workbook as canonical handoff.,selected_not_live_permissive_candidate,phase0r_permissive_eval_then_implement,"Phase 1R closed. Retain as a Phase 3R permissive implementation candidate; implement only from its packet authority and the retained-set contract, not by reopening Phase 0R." +7814,kkoomen/qbr,https://github.com/kkoomen/qbr,HyperTwist,2.0,158.0,191.0,A,vision / perception / AR,foundation engine,vision donor,locked core candidate,integrate,direct,"Keep the core engine or major subsystem mostly intact; change wrappers, branding, storage/auth, and integration seams so it becomes a first-class part of the target stack. For this repo class, that usually means preserving calibration/detection/state-reconstruction logic while replacing camera UX and integration surfaces.","kkoomen/qbr — MIT — Webcam-based 3x3 solver with accurate OpenCV color detection (perfect vision starter). | kkoomen/qbr — MIT — Webcam CV solver (base for 3D vision). | kkoomen/qbr — MIT — Webcam CV color detection. | poliva/cubedex, ta...","Integrate as a computer vision / AR subsystem for HyperTwist. Preserve the strongest existing pieces — camera ingest, calibration, segmentation/detection, pose or facelet extraction, state normalization, solver bridge, replay overlay, AR anchors — and expose them behind a portfolio-stable interface. Wire first into vivaansinghvi07/rubix-cube-solver, then into cubing/cubing.js for orchestration, visualization, or data exchange.","Consolidate under the Hyperspeedcube + cubing.js + qbr nucleus, not beside it as a separate silo. Normalize data contracts, auth/permissions, storage, and telemetry; then attach as a service, plugin, canvas layer, trainer, or analysis module. Descending combination order: vivaansinghvi07/rubix-cube-solver, cubing/cubing.js, HactarCE/Hyperspeedcube.","Repurpose here means: turn it into a perception microservice, cube-state API, replay generator, or AR overlay donor for HyperTwist.",Map module boundaries; Identify hidden reusable internals; Define adapter/API boundary to target anchors; Write extraction tests against upstream behavior; Benchmark calibration pipeline; Extract state reconstruction; Wrap with camera/AR adapter,full subsystem extraction review,"Hidden value often sits in calibration, preprocessing, stabilization, object/state reconstruction, replay artifacts, and camera-to-domain state pipelines that are not obvious from demos.",Inspect preprocessing/calibration; tracking stabilization; state reconstruction; replay/event model; camera abstraction; fallback heuristics; testing assets/videos; performance shortcuts.,"Inspect package manifests, README/docs, src tree, examples, tests, CI workflows, config files, migrations/schemas, and hidden feature flags or experimental modules. Look for calibration routines, detection heuristics/models, color/state normalization, replay serialization, solver bridges, camera abstraction layers, and debug visualizations.","Audit kkoomen/qbr as a vision / perception / AR candidate for HyperTwist. Do not stop at README-level features. Inspect: Inspect preprocessing/calibration; tracking stabilization; state reconstruction; replay/event model; camera abstraction; fallback heuristics; testing assets/videos; performance shortcuts. Decide whether the best extraction path is direct and whether it belongs as foundation engine / vision donor. Test the three merger paths in order: 1) vivaansinghvi07/rubix-cube-solver [perception + replay donor]; 2) cubing/cubing.js [state/render backend]; 3) cross-project transfer candidate [future merger]. Return hidden modules, reusable schemas, protocol layers, plugin hooks, render/state models, datasets/test fixtures, and any subsystem stronger than the visible product shell.",vivaansinghvi07/rubix-cube-solver,perception + replay donor,Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.,cubing/cubing.js,state/render backend,Use the partner for canonical state or rendering abstractions and merge this repo's specialized logic on top.,cross-project transfer candidate,future merger,Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.,VectorShell | ScriptoriumAI,VectorShell can borrow spatial/rendering and perception primitives; ScriptoriumAI can borrow tutorial/educational visualization patterns rather than the full engine.,do not exclude,Keep in active merge-set and force full source audit before any demotion.,high,single-source signal; clear taxonomy; active integration value; foundation-level fit,high,portfolio anchor or repeatedly surfaced core candidate; memo mentions: 5,"Licensing intentionally ignored as a decision filter in this canonical evaluation; assess only architecture, capability, donor value, and concept transfer.",,,,"kkoomen/qbr — MIT — Webcam-based 3x3 solver with accurate OpenCV color detection (perfect vision starter). | kkoomen/qbr — MIT — Webcam CV solver (base for 3D vision). | kkoomen/qbr — MIT — Webcam CV color detection. | poliva/cubedex, tao-yu/Alg-Trainer, kkoomen/qbr, vivaansinghvi07/rubix-cube-solver, NuiLab/code-vr, molgenis/Graph2VR (core permissive parts), brianpeiris/RiftSketch, aMonteSl/CodeXR.","kkoomen/qbr is treated as integrate for HyperTwist because visible metadata points to the computer vision / AR layer. Surface signal: kkoomen/qbr — MIT — Webcam-based 3x3 solver with accurate OpenCV color detection (perfect vision starter). | kkoomen/qbr — MIT — Webcam CV solver (base for 3D vision). | kkoomen/qbr — MIT — Webcam CV color detection. | poliva/cubedex, ta... The likely value is substantial enough to preserve as a named subsystem rather than just mining isolated ideas.",memo,False,True,0.0,5.0,HT_cube_vision,HT_cube_vision_0001,computer vision / AR,Integrate as a shared building block across at least two projects. Its memo and bookmark signals place it in the computer vision / AR layer.,multi-project,computer vision / AR,integrate,heavy modification,medium,kkoomen/qbr,HyperTwist,,,,,,,,,,,,,,,,Original global operational v3 retained,MIT,known_from_reference_material,uploaded_reference_docs,no,,,,Supplemental intake references are advisory only; v6 adjudication remains the source of truth.,Potentially relevant,yes,v6 unified all-project source-of-truth pack,v5_carry_forward,,2.0,5,158.0,,,,,permissive_or_noncopyleft_known,direct_incorporation_ok,"This repo is aligned with a direct integration path for HyperTwist because it is either already implemented, strategically central, or donor-grade without a visible copyleft constraint in the current materials. Deep incorporation is sensible if the source audit confirms architectural cleanliness.","Direct embed, vendored module, package dependency, or tightly integrated adapter as the architecture requires.","Typically preserve notices, attribution, and license text where required; no special copyleft-driven disclosure posture is normally needed.",Usually unnecessary unless you later decide the existing implementation is too constraining architecturally.,high,strategic-or-implemented-component,yes,,,,,,,,,,,,,v6.3_final_source_of_truth,Merged v6.1 copyleft layer and v6.2 SRE layer; use v6.3 docs + workbook as canonical handoff.,implemented_live_permissive,landed_permissive_preserve,"Phase 3R-E closed. Preserve as the landed first-party embodied companion, narration, lip-sync, gesture, subtitle, and avatar-embed lane; start future widening from the live-lane audit, then the 3R-E implementation packet, then REPO_LICENSE_TRACKING.md." 7818,coqui-ai/TTS,https://github.com/coqui-ai/TTS,multi-project,2.0,71.0,80.0,C,voice / multimodal I/O,subsystem donor,multimodal donor,donor bench,repurpose,moderate modification,"Retain the valuable internal engine, but expect to replace UI/product shell, adapt schemas/APIs, and refactor boundaries so it can plug into the target anchors cleanly. For this repo class, that usually means preserving streaming/audio pipeline logic while adapting commands, wake flows, and assistant integration.",https://github.com/coqui-ai/TTS – Coqui XTTS v2.,"Repurpose selected subsystems rather than the whole product. Mine the repo for synthesis orchestration, multilingual and speaker handling, local service wrappers, voice-conversion paths, and model-registry/license handling; keep what materially shortens build time, but rebind data contracts, permissions, storage, and deployment to the target architecture. Best first pairing order: rhasspy/piper, ggml-org/whisper.cpp, SYSTRAN/faster-whisper.","Consolidate under the project-specific anchor stack, not beside it as a separate silo. Normalize data contracts, auth/permissions, storage, and telemetry; then attach as a service, plugin, canvas layer, trainer, or analysis module. Descending combination order: sentrux/sentrux, HactarCE/Hyperspeedcube, outline/outline.","Repurpose here means: turn it into a bounded voice-service seam, coach narration donor, or multilingual TTS and cloning donor.",Map module boundaries; Identify hidden reusable internals; Define adapter/API boundary to target anchors; Write extraction tests against upstream behavior; Isolate streaming/audio pipeline; Normalize command schema; Add local/offline fallback layer,deep source audit,"Hidden value often lives in streaming segmentation, VAD, device abstraction, latency mitigation, translation chains, and local/offline fallback paths.","Inspect public API, synthesis and orchestration spine, server boundary, multilingual and speaker handling, XTTS path, model registry and license metadata, and optional voice conversion.","Inspect package manifests, README/docs, src tree, examples, tests, CI workflows, model registry files, and hidden experimental modules. Look for synthesis orchestration, sentence splitting, multilingual and speaker handling, voice conversion, server deployment patterns, and model-license metadata.","Audit coqui-ai/TTS as a voice / multimodal I/O candidate for multi-project. Do not stop at README-level features. Inspect: public API surface, synthesis/orchestration spine, server boundary, multilingual and speaker handling, XTTS path, model registry and license metadata, and optional voice conversion. Decide whether it should remain the strongest voice/coaching donor and what should stay behind a bounded voice-service seam. Test the three merger paths in order: 1) project-local anchor [base + donor]; 2) shared portfolio utility [augmenter]; 3) cross-project transfer candidate [future merger]. Return hidden modules, reusable schemas, protocol layers, runtime boundaries, tests/fixtures, and any subsystem stronger than the visible shell.",project-local anchor,base + donor,Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.,shared portfolio utility,augmenter,Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.,cross-project transfer candidate,future merger,Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.,VectorShell | HyperTwist | ScriptoriumAI,"This capability is broadly portable across the portfolio because interaction, orchestration, and shell/UI patterns can be shared with thin domain adapters.","exclude from core, keep as donor","Do not let it consume roadmap as a full product shell; mine reusable engines, adapters, schemas, UX patterns, or datasets.",medium-low,single-source signal; clear taxonomy; mostly donor/reference role,medium,memo mentions: 1,"Licensing intentionally ignored as a decision filter in this canonical evaluation; assess only architecture, capability, donor value, and concept transfer.",,,,https://github.com/coqui-ai/TTS – Coqui XTTS v2.,"coqui-ai/TTS is treated as repurpose for multi-project because visible metadata points to the voice / speech / audio layer. Surface signal: https://github.com/coqui-ai/TTS – Coqui XTTS v2. The fit looks real, but more as a donor/augmenter than as a standalone foundation.",memo,False,True,0.0,1.0,MU_misc,MU_misc_0002,voice / speech / audio,"Repurpose selectively for multi-project. Its source-backed role is the richest current voice-output and coaching donor, but it should stay behind a bounded voice-service seam because code and model payload licensing diverge.",future/adjacent use,voice / speech / audio,repurpose,moderate modification,medium,coqui-ai/tts,multi-project,,,,,,,,,,,,,,,,Original global operational v3 retained,MPL-2.0 code; mixed model payload licenses,known_from_reference_material,uploaded_reference_docs,no,,,,Supplemental intake references are advisory only; v6 adjudication remains the source of truth.,Usually indirect,yes,v6 unified all-project source-of-truth pack,v5_carry_forward,,2.0,5,71.0,,,,,mixed_or_boundary_sensitive_known,bounded_sidecar_or_selective_reimplementation,"Code is usable under MPL-2.0, but selected model weights carry mixed per-model licenses and some require separate terms. Keep the repo behind a bounded voice-service seam and decide model adoption case by case rather than treating it as a blanket permissive dependency.",Use the code behind a bounded voice-service seam; select model weights individually and keep model-license decisions separate from code adoption.,"Preserve MPL notices and file-level obligations where applicable, and review each chosen model license or ToS separately before shipping.",Sometimes useful only if you later need a fully proprietary embedded voice stack or want to avoid model-license entanglement; not the default path.,medium,model-license-selection-required,yes,,,,,,,,,,,,,v6.3_final_source_of_truth,Merged v6.1 copyleft layer and v6.2 SRE layer; use v6.3 docs + workbook as canonical handoff.,,, -8543,vivaansinghvi07/rubix-cube-solver,https://github.com/vivaansinghvi07/rubix-cube-solver,HyperTwist,3.0,158.0,191.0,A,vision / perception / AR,foundation engine,vision donor,locked core candidate,integrate,direct,"Keep the core engine or major subsystem mostly intact; change wrappers, branding, storage/auth, and integration seams so it becomes a first-class part of the target stack. For this repo class, that usually means preserving calibration/detection/state-reconstruction logic while replacing camera UX and integration surfaces.","Yes — 100% possible to consolidate everything into one no-compromises, enterprise-grade platform. You're not half-arsing it, and neither am I. Modern vision models (and even classical OpenCV pipelines refined over the last decade) are mo...","Integrate as a computer vision / AR subsystem for HyperTwist. Preserve the strongest existing pieces — camera ingest, calibration, segmentation/detection, pose or facelet extraction, state normalization, solver bridge, replay overlay, AR anchors — and expose them behind a portfolio-stable interface. Wire first into kkoomen/qbr, then into cubing/cubing.js for orchestration, visualization, or data exchange.","Consolidate under the Hyperspeedcube + cubing.js + qbr nucleus, not beside it as a separate silo. Normalize data contracts, auth/permissions, storage, and telemetry; then attach as a service, plugin, canvas layer, trainer, or analysis module. Descending combination order: kkoomen/qbr, cubing/cubing.js, HactarCE/Hyperspeedcube.","Repurpose here means: turn it into a perception microservice, cube-state API, replay generator, or AR overlay donor for HyperTwist.",Map module boundaries; Identify hidden reusable internals; Define adapter/API boundary to target anchors; Write extraction tests against upstream behavior; Benchmark calibration pipeline; Extract state reconstruction; Wrap with camera/AR adapter,full subsystem extraction review,"Hidden value often sits in calibration, preprocessing, stabilization, object/state reconstruction, replay artifacts, and camera-to-domain state pipelines that are not obvious from demos.",Inspect preprocessing/calibration; tracking stabilization; state reconstruction; replay/event model; camera abstraction; fallback heuristics; testing assets/videos; performance shortcuts.,"Inspect package manifests, README/docs, src tree, examples, tests, CI workflows, config files, migrations/schemas, and hidden feature flags or experimental modules. Look for calibration routines, detection heuristics/models, color/state normalization, replay serialization, solver bridges, camera abstraction layers, and debug visualizations.","Audit vivaansinghvi07/rubix-cube-solver as a vision / perception / AR candidate for HyperTwist. Do not stop at README-level features. Inspect: Inspect preprocessing/calibration; tracking stabilization; state reconstruction; replay/event model; camera abstraction; fallback heuristics; testing assets/videos; performance shortcuts. Decide whether the best extraction path is direct and whether it belongs as foundation engine / vision donor. Test the three merger paths in order: 1) kkoomen/qbr [foundation + perception donor]; 2) cubing/cubing.js [state/render backend]; 3) cross-project transfer candidate [future merger]. Return hidden modules, reusable schemas, protocol layers, plugin hooks, render/state models, datasets/test fixtures, and any subsystem stronger than the visible product shell.",kkoomen/qbr,foundation + perception donor,"Use this repo against the partner as an augmenting layer; preserve the partner as the likely base and mine this repo for capabilities that improve breadth, UX, or specialization.",cubing/cubing.js,state/render backend,Use the partner for canonical state or rendering abstractions and merge this repo's specialized logic on top.,cross-project transfer candidate,future merger,Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.,VectorShell | ScriptoriumAI,VectorShell can borrow spatial/rendering and perception primitives; ScriptoriumAI can borrow tutorial/educational visualization patterns rather than the full engine.,do not exclude,Keep in active merge-set and force full source audit before any demotion.,high,single-source signal; clear taxonomy; active integration value; foundation-level fit,high,portfolio anchor or repeatedly surfaced core candidate; memo mentions: 10,"Licensing intentionally ignored as a decision filter in this canonical evaluation; assess only architecture, capability, donor value, and concept transfer.",,,,"Yes — 100% possible to consolidate everything into one no-compromises, enterprise-grade platform. You're not half-arsing it, and neither am I. Modern vision models (and even classical OpenCV pipelines refined over the last decade) are more than accurate enough in 2026 for reliable small-square/facelet color recognition on a standard 3x3 (or larger) Rubik's Cube under normal lighting. Production examples prove it:Multiple MIT-licensed projects (qb",vivaansinghvi07/rubix-cube-solver is treated as integrate for HyperTwist because current dossier work keeps it in the committed vision path as the strongest reconstruction and replay-oriented companion to qbr rather than as a generic donor.,memo,False,True,0.0,10.0,HT_cube_vision,HT_cube_vision_0002,computer vision / AR,Integrate primarily for HyperTwist. Its memo and bookmark signals place it in the computer vision / AR layer.,HyperTwist,computer vision / AR,integrate,heavy modification,medium,vivaansinghvi07/rubix-cube-solver,HyperTwist,,,,,,,,,,,,,,,,Original global operational v3 retained,MIT,known_from_reference_material,uploaded_reference_docs,no,,,,Supplemental intake references are advisory only; v6 adjudication remains the source of truth.,Usually indirect,yes,v6 unified all-project source-of-truth pack,v5_carry_forward,,3.0,5,158.0,Locked Parallel Foundation,Parallel foundation and reconstruction companion donor,,,permissive_or_noncopyleft_known,direct_incorporation_ok,"This repo is aligned with a direct integration path for HyperTwist because it is either already implemented, strategically central, or donor-grade without a visible copyleft constraint in the current materials. Deep incorporation is sensible if the source audit confirms architectural cleanliness.","Direct embed, vendored module, package dependency, or tightly integrated adapter as the architecture requires.","Typically preserve notices, attribution, and license text where required; no special copyleft-driven disclosure posture is normally needed.",Usually unnecessary unless you later decide the existing implementation is too constraining architecturally.,high,strategic-or-implemented-component,yes,,,,,,,,,,,,,v6.3_final_source_of_truth,Normalized legacy wording to dossier-backed parallel-foundation posture on 2026-04-25.,selected_not_live_permissive_candidate,phase0r_permissive_eval_then_implement,"Phase 1R closed. Retain as a Phase 3R permissive implementation candidate; implement only from its packet authority and the retained-set contract, not by reopening Phase 0R." +8543,vivaansinghvi07/rubix-cube-solver,https://github.com/vivaansinghvi07/rubix-cube-solver,HyperTwist,3.0,158.0,191.0,A,vision / perception / AR,foundation engine,vision donor,locked core candidate,integrate,direct,"Keep the core engine or major subsystem mostly intact; change wrappers, branding, storage/auth, and integration seams so it becomes a first-class part of the target stack. For this repo class, that usually means preserving calibration/detection/state-reconstruction logic while replacing camera UX and integration surfaces.","Yes — 100% possible to consolidate everything into one no-compromises, enterprise-grade platform. You're not half-arsing it, and neither am I. Modern vision models (and even classical OpenCV pipelines refined over the last decade) are mo...","Integrate as a computer vision / AR subsystem for HyperTwist. Preserve the strongest existing pieces — camera ingest, calibration, segmentation/detection, pose or facelet extraction, state normalization, solver bridge, replay overlay, AR anchors — and expose them behind a portfolio-stable interface. Wire first into kkoomen/qbr, then into cubing/cubing.js for orchestration, visualization, or data exchange.","Consolidate under the Hyperspeedcube + cubing.js + qbr nucleus, not beside it as a separate silo. Normalize data contracts, auth/permissions, storage, and telemetry; then attach as a service, plugin, canvas layer, trainer, or analysis module. Descending combination order: kkoomen/qbr, cubing/cubing.js, HactarCE/Hyperspeedcube.","Repurpose here means: turn it into a perception microservice, cube-state API, replay generator, or AR overlay donor for HyperTwist.",Map module boundaries; Identify hidden reusable internals; Define adapter/API boundary to target anchors; Write extraction tests against upstream behavior; Benchmark calibration pipeline; Extract state reconstruction; Wrap with camera/AR adapter,full subsystem extraction review,"Hidden value often sits in calibration, preprocessing, stabilization, object/state reconstruction, replay artifacts, and camera-to-domain state pipelines that are not obvious from demos.",Inspect preprocessing/calibration; tracking stabilization; state reconstruction; replay/event model; camera abstraction; fallback heuristics; testing assets/videos; performance shortcuts.,"Inspect package manifests, README/docs, src tree, examples, tests, CI workflows, config files, migrations/schemas, and hidden feature flags or experimental modules. Look for calibration routines, detection heuristics/models, color/state normalization, replay serialization, solver bridges, camera abstraction layers, and debug visualizations.","Audit vivaansinghvi07/rubix-cube-solver as a vision / perception / AR candidate for HyperTwist. Do not stop at README-level features. Inspect: Inspect preprocessing/calibration; tracking stabilization; state reconstruction; replay/event model; camera abstraction; fallback heuristics; testing assets/videos; performance shortcuts. Decide whether the best extraction path is direct and whether it belongs as foundation engine / vision donor. Test the three merger paths in order: 1) kkoomen/qbr [foundation + perception donor]; 2) cubing/cubing.js [state/render backend]; 3) cross-project transfer candidate [future merger]. Return hidden modules, reusable schemas, protocol layers, plugin hooks, render/state models, datasets/test fixtures, and any subsystem stronger than the visible product shell.",kkoomen/qbr,foundation + perception donor,"Use this repo against the partner as an augmenting layer; preserve the partner as the likely base and mine this repo for capabilities that improve breadth, UX, or specialization.",cubing/cubing.js,state/render backend,Use the partner for canonical state or rendering abstractions and merge this repo's specialized logic on top.,cross-project transfer candidate,future merger,Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.,VectorShell | ScriptoriumAI,VectorShell can borrow spatial/rendering and perception primitives; ScriptoriumAI can borrow tutorial/educational visualization patterns rather than the full engine.,do not exclude,Keep in active merge-set and force full source audit before any demotion.,high,single-source signal; clear taxonomy; active integration value; foundation-level fit,high,portfolio anchor or repeatedly surfaced core candidate; memo mentions: 10,"Licensing intentionally ignored as a decision filter in this canonical evaluation; assess only architecture, capability, donor value, and concept transfer.",,,,"Yes — 100% possible to consolidate everything into one no-compromises, enterprise-grade platform. You're not half-arsing it, and neither am I. Modern vision models (and even classical OpenCV pipelines refined over the last decade) are more than accurate enough in 2026 for reliable small-square/facelet color recognition on a standard 3x3 (or larger) Rubik's Cube under normal lighting. Production examples prove it:Multiple MIT-licensed projects (qb",vivaansinghvi07/rubix-cube-solver is treated as integrate for HyperTwist because current dossier work keeps it in the committed vision path as the strongest reconstruction and replay-oriented companion to qbr rather than as a generic donor.,memo,False,True,0.0,10.0,HT_cube_vision,HT_cube_vision_0002,computer vision / AR,Integrate primarily for HyperTwist. Its memo and bookmark signals place it in the computer vision / AR layer.,HyperTwist,computer vision / AR,integrate,heavy modification,medium,vivaansinghvi07/rubix-cube-solver,HyperTwist,,,,,,,,,,,,,,,,Original global operational v3 retained,MIT,known_from_reference_material,uploaded_reference_docs,no,,,,Supplemental intake references are advisory only; v6 adjudication remains the source of truth.,Usually indirect,yes,v6 unified all-project source-of-truth pack,v5_carry_forward,,3.0,5,158.0,Locked Parallel Foundation,Parallel foundation and reconstruction companion donor,,,permissive_or_noncopyleft_known,direct_incorporation_ok,"This repo is aligned with a direct integration path for HyperTwist because it is either already implemented, strategically central, or donor-grade without a visible copyleft constraint in the current materials. Deep incorporation is sensible if the source audit confirms architectural cleanliness.","Direct embed, vendored module, package dependency, or tightly integrated adapter as the architecture requires.","Typically preserve notices, attribution, and license text where required; no special copyleft-driven disclosure posture is normally needed.",Usually unnecessary unless you later decide the existing implementation is too constraining architecturally.,high,strategic-or-implemented-component,yes,,,,,,,,,,,,,v6.3_final_source_of_truth,Normalized legacy wording to dossier-backed parallel-foundation posture on 2026-04-25.,implemented_live_permissive,landed_permissive_preserve,"Phase 3R-E closed. Preserve as the landed first-party embodied companion, narration, lip-sync, gesture, subtitle, and avatar-embed lane; start future widening from the live-lane audit, then the 3R-E implementation packet, then REPO_LICENSE_TRACKING.md." 8547,ggml-org/whisper.cpp,https://github.com/ggml-org/whisper.cpp,multi-project,3.0,71.0,80.0,C,voice / multimodal I/O,subsystem donor,multimodal donor,donor bench,repurpose,moderate modification,"Retain the valuable internal engine, but expect to replace UI/product shell, adapt schemas/APIs, and refactor boundaries so it can plug into the target anchors cleanly. For this repo class, that usually means preserving streaming/audio pipeline logic while adapting commands, wake flows, and assistant integration.",7. Speech / Voice Models (STT + TTS)ggml-org/whisper.cpp – https://github.com/ggml-org/whisper.cpp – MIT – Native C++ Whisper for STT.,"Repurpose selected subsystems rather than the whole product. Mine the repo for native STT runtime seams, VAD, grammar-constrained decoding, segmented speech capture, and server-side deployment patterns; keep what materially shortens build time, but rebind data contracts, permissions, storage, and deployment to the target architecture. Best first pairing order: SYSTRAN/faster-whisper, rhasspy/piper, coqui-ai/TTS.","Consolidate under the project-specific anchor stack, not beside it as a separate silo. Normalize data contracts, auth/permissions, storage, and telemetry; then attach as a service, plugin, canvas layer, trainer, or analysis module. Descending combination order: sentrux/sentrux, HactarCE/Hyperspeedcube, outline/outline.","Repurpose here means: turn it into an offline STT sidecar, grammar-constrained command surface, or native speech-input donor.",Map module boundaries; Identify hidden reusable internals; Define adapter/API boundary to target anchors; Write extraction tests against upstream behavior; Isolate streaming/audio pipeline; Normalize command schema; Add local/offline fallback layer,deep source audit,"Hidden value often lives in streaming segmentation, VAD, device abstraction, latency mitigation, translation chains, and local/offline fallback paths.",Inspect C/C++ API surface; VAD path; grammar-constrained decoding; server/runtime examples; model loading and portability seams; tests and benchmarks.,"Inspect package manifests, README/docs, src/include tree, examples, tests, CI workflows, build configs, model tooling, and hidden experimental modules. Look for VAD, grammar support, streaming/segmentation, server boundaries, device/runtime abstraction, and performance shortcuts.","Audit ggml-org/whisper.cpp as a voice / multimodal I/O candidate for multi-project. Do not stop at README-level features. Inspect: C/C++ API surface, VAD, grammar-constrained decoding, server/runtime examples, model loading and portability seams, and benchmark/test coverage. Decide whether it should remain the primary offline STT sidecar candidate and what should stay behind a bounded native seam. Test the three merger paths in order: 1) project-local anchor [base + donor]; 2) shared portfolio utility [augmenter]; 3) cross-project transfer candidate [future merger]. Return hidden modules, reusable schemas, protocol layers, runtime boundaries, tests/benchmarks, and any subsystem stronger than the visible shell.",project-local anchor,base + donor,Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.,shared portfolio utility,augmenter,Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.,cross-project transfer candidate,future merger,Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.,VectorShell | HyperTwist | ScriptoriumAI,"This capability is broadly portable across the portfolio because interaction, orchestration, and shell/UI patterns can be shared with thin domain adapters.","exclude from core, keep as donor","Do not let it consume roadmap as a full product shell; mine reusable engines, adapters, schemas, UX patterns, or datasets.",medium-low,single-source signal; clear taxonomy; mostly donor/reference role,medium,memo mentions: 1,"Licensing intentionally ignored as a decision filter in this canonical evaluation; assess only architecture, capability, donor value, and concept transfer.",,,,7. Speech / Voice Models (STT + TTS)ggml-org/whisper.cpp – https://github.com/ggml-org/whisper.cpp – MIT – Native C++ Whisper for STT.,"ggml-org/whisper.cpp is treated as repurpose for multi-project because visible metadata points to the voice / speech / audio layer. Surface signal: 7. Speech / Voice Models (STT + TTS)ggml-org/whisper.cpp – https://github.com/ggml-org/whisper.cpp – MIT – Native C++ Whisper for STT. The fit looks real, but more as a donor/augmenter than as a standalone foundation.",memo,False,True,0.0,1.0,MU_misc,MU_misc_0003,voice / speech / audio,"Repurpose selectively for multi-project. Its source-backed role is a bounded speech-input donor and offline/native STT sidecar candidate, not an exclusion-only adjunct.",future/adjacent use,voice / speech / audio,repurpose,moderate modification,medium,ggml-org/whisper.cpp,multi-project,,,,,,,,,,,,,,,,Original global operational v3 retained,MIT,known_from_reference_material,uploaded_reference_docs,no,,,,Supplemental intake references are advisory only; v6 adjudication remains the source of truth.,Usually indirect,yes,v6 unified all-project source-of-truth pack,v5_carry_forward,,3.0,5,71.0,,,,,permissive_or_noncopyleft_known,direct_incorporation_ok,The code license is MIT and direct use is allowed. This repo is best used as a bounded offline STT sidecar or native speech-input seam; no clean-room path is required by default.,"Use directly as a bounded native STT sidecar or library adapter; keep grammar, VAD, and model/runtime choices behind a speech-input seam.","Typically preserve notices, attribution, and license text where required; review selected model files or distributions separately from the code license.",Usually unnecessary unless you later choose to replace a narrow hot path or fully internalize the runtime.,high,model-artifact-review-recommended,yes,,,,,,,,,,,,,v6.3_final_source_of_truth,Merged v6.1 copyleft layer and v6.2 SRE layer; use v6.3 docs + workbook as canonical handoff.,,, 11766,tao-yu/Alg-Trainer,https://github.com/tao-yu/Alg-Trainer,HyperTwist,4.0,156.0,189.0,A,cubing trainer / solver / timing,foundation engine,training donor,locked core candidate,integrate,direct,"Keep the core engine or major subsystem mostly intact; change wrappers, branding, storage/auth, and integration seams so it becomes a first-class part of the target stack. For this repo class, that usually means preserving cube-state, scramble, scheduling, or timer internals while adapting pedagogy, analytics, and UI.","Alg-Trainer (tao-yu/Alg-Trainer) | tao-yu/Alg-Trainer — MIT — Most powerful multi-set alg trainer (ZBLL, full custom sets, smartcube/virtual cube). Live: https://tao-yu.github.io/Alg-Trainer/. | tao-yu/Alg-Trainer — MIT — Multi-set alg t...","Integrate as a cubing / algorithm training subsystem for HyperTwist. Preserve the strongest existing pieces — scramble generation, algorithm database, recognition/training loop, timing/statistics, virtual cube, smartcube hooks, spaced repetition — and expose them behind a portfolio-stable interface. Wire first into poliva/cubedex, then into Lykos/cube_trainer for orchestration, visualization, or data exchange.","Consolidate under the Hyperspeedcube + cubing.js + qbr nucleus, not beside it as a separate silo. Normalize data contracts, auth/permissions, storage, and telemetry; then attach as a service, plugin, canvas layer, trainer, or analysis module. Descending combination order: poliva/cubedex, Lykos/cube_trainer, cubing/cubing.js.","Repurpose here means: turn it into a trainer engine, solver/timer backend, recognition drill module, or method-specific practice mode for HyperTwist.",Map module boundaries; Identify hidden reusable internals; Define adapter/API boundary to target anchors; Write extraction tests against upstream behavior; Extract cube-state model; Normalize trainer/case schema; Expose analytics and replay hooks,full subsystem extraction review,"Hidden value often sits in cube-state representation, scramble generation, weighted drill scheduling, recognition datasets, replay/timer internals, and case database schemas.",Inspect cube-state model; scramble generator; trainer weighting/scheduling; case database and metadata; replay/timer model; import/export of alg sets; smartcube or sensor adapters.,"Inspect package manifests, README/docs, src tree, examples, tests, CI workflows, config files, migrations/schemas, and hidden feature flags or experimental modules. Look for algorithm databases, spaced-repetition logic, scramble generation, timer/stat code, virtual cube components, smartcube adapters, and custom-trainer configuration support.","Audit tao-yu/Alg-Trainer as a cubing trainer / solver / timing candidate for HyperTwist. Do not stop at README-level features. Inspect: Inspect cube-state model; scramble generator; trainer weighting/scheduling; case database and metadata; replay/timer model; import/export of alg sets; smartcube or sensor adapters. Decide whether the best extraction path is direct and whether it belongs as foundation engine / training donor. Test the three merger paths in order: 1) poliva/cubedex [specialized training UX donor]; 2) Lykos/cube_trainer [sampling/analytics donor]; 3) cross-project transfer candidate [future merger]. Return hidden modules, reusable schemas, protocol layers, plugin hooks, render/state models, datasets/test fixtures, and any subsystem stronger than the visible product shell.",poliva/cubedex,specialized training UX donor,Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.,Lykos/cube_trainer,sampling/analytics donor,Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.,cross-project transfer candidate,future merger,Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.,project-local first,"Cross-project transfer is possible, but the value is clearest inside the assigned project until source audit exposes more reusable primitives.",do not exclude,Keep in active merge-set and force full source audit before any demotion.,high,single-source signal; clear taxonomy; active integration value; foundation-level fit,high,portfolio anchor or repeatedly surfaced core candidate; memo mentions: 5,"Licensing intentionally ignored as a decision filter in this canonical evaluation; assess only architecture, capability, donor value, and concept transfer.",,,,"Alg-Trainer (tao-yu/Alg-Trainer) | tao-yu/Alg-Trainer — MIT — Most powerful multi-set alg trainer (ZBLL, full custom sets, smartcube/virtual cube). Live: https://tao-yu.github.io/Alg-Trainer/. | tao-yu/Alg-Trainer — MIT — Multi-set alg trainer (extend to hyper commutators). | tao-yu/Alg-Trainer — MIT — Multi-set alg trainer.","tao-yu/Alg-Trainer is treated as integrate for HyperTwist because visible metadata points to the cubing / algorithm training layer. Surface signal: Alg-Trainer (tao-yu/Alg-Trainer) | tao-yu/Alg-Trainer — MIT — Most powerful multi-set alg trainer (ZBLL, full custom sets, smartcube/virtual cube). Live: https://tao-yu.github.io/Alg-Trainer/. | tao-yu/Alg-Trainer — MIT — Multi-set alg t... The likely value is substantial enough to preserve as a named subsystem rather than just mining isolated ideas.",memo,False,True,0.0,5.0,HT_training_stack,HT_training_stack_0001,cubing / algorithm training,Integrate primarily for HyperTwist. Its memo and bookmark signals place it in the cubing / algorithm training layer.,HyperTwist,cubing / algorithm training,integrate,moderate modification,medium,tao-yu/alg-trainer,HyperTwist,,,,,,,,,,,,,,,,Original global operational v3 retained,MIT,known_from_reference_material,uploaded_reference_docs,no,,,,Supplemental intake references are advisory only; v6 adjudication remains the source of truth.,Usually indirect,yes,v6 unified all-project source-of-truth pack,v5_carry_forward,,4.0,5,156.0,,,,,permissive_or_noncopyleft_known,direct_incorporation_ok,"This repo is aligned with a direct integration path for HyperTwist because it is either already implemented, strategically central, or donor-grade without a visible copyleft constraint in the current materials. Deep incorporation is sensible if the source audit confirms architectural cleanliness.","Direct embed, vendored module, package dependency, or tightly integrated adapter as the architecture requires.","Typically preserve notices, attribution, and license text where required; no special copyleft-driven disclosure posture is normally needed.",Usually unnecessary unless you later decide the existing implementation is too constraining architecturally.,high,strategic-or-implemented-component,yes,,,,,,,,,,,,,v6.3_final_source_of_truth,Merged v6.1 copyleft layer and v6.2 SRE layer; use v6.3 docs + workbook as canonical handoff.,implemented_live_permissive,landed_permissive_preserve,Phase 1R closed. Preserve as a landed first-party permissive lane; keep notices and attribution visible and widen only through ordinary owned enhancement work. 11769,rhasspy/piper,https://github.com/rhasspy/piper,multi-project,4.0,71.0,80.0,C,voice / multimodal I/O,subsystem donor,multimodal donor,donor bench,repurpose,moderate modification,"Retain the valuable internal engine, but expect to replace UI/product shell, adapt schemas/APIs, and refactor boundaries so it can plug into the target anchors cleanly. For this repo class, that usually means preserving streaming/audio pipeline logic while adapting commands, wake flows, and assistant integration.",rhasspy/piper – https://github.com/rhasspy/piper – MIT – Real-time TTS (recommended).,"Repurpose selected subsystems rather than the whole product. Mine the repo for lean local TTS runtime, HTTP wrapping, voice loading and download logic, streaming WAV and raw output, and ONNX/eSpeak integration; keep what materially shortens build time, but rebind data contracts, permissions, storage, and deployment to the target architecture. Best first pairing order: coqui-ai/TTS, ggml-org/whisper.cpp, SYSTRAN/faster-whisper.","Consolidate under the project-specific anchor stack, not beside it as a separate silo. Normalize data contracts, auth/permissions, storage, and telemetry; then attach as a service, plugin, canvas layer, trainer, or analysis module. Descending combination order: sentrux/sentrux, HactarCE/Hyperspeedcube, outline/outline.",Repurpose here means: turn it into a lean offline TTS sidecar or direct local narration donor.,Map module boundaries; Identify hidden reusable internals; Define adapter/API boundary to target anchors; Write extraction tests against upstream behavior; Isolate streaming/audio pipeline; Normalize command schema; Add local/offline fallback layer,deep source audit,"Hidden value often lives in streaming segmentation, VAD, device abstraction, latency mitigation, translation chains, and local/offline fallback paths.",Inspect C++ runtime core; voice loading and download path; streaming output; HTTP service boundary; speaker and phonemization config; selected voice artifact constraints.,"Inspect package manifests, README/docs, src tree, examples, tests, build configs, voice catalog files, and hidden runtime switches. Look for ONNX runtime integration, phonemization, lightweight service boundaries, audio streaming, voice acquisition, and deployment constraints.","Audit rhasspy/piper as a voice / multimodal I/O candidate for multi-project. Do not stop at README-level features. Inspect: C++ runtime core, voice loading and download path, streaming output, HTTP service boundary, speaker and phonemization config, and selected voice artifact constraints. Decide whether it should remain the lean direct local TTS sidecar candidate and what should stay behind a bounded local voice seam. Test the three merger paths in order: 1) project-local anchor [base + donor]; 2) shared portfolio utility [augmenter]; 3) cross-project transfer candidate [future merger]. Return hidden modules, reusable schemas, protocol layers, runtime boundaries, tests/fixtures, and any subsystem stronger than the visible shell.",project-local anchor,base + donor,Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.,shared portfolio utility,augmenter,Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.,cross-project transfer candidate,future merger,Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.,VectorShell | HyperTwist | ScriptoriumAI,"This capability is broadly portable across the portfolio because interaction, orchestration, and shell/UI patterns can be shared with thin domain adapters.","exclude from core, keep as donor","Do not let it consume roadmap as a full product shell; mine reusable engines, adapters, schemas, UX patterns, or datasets.",medium-low,single-source signal; clear taxonomy; mostly donor/reference role,medium,memo mentions: 1,"Licensing intentionally ignored as a decision filter in this canonical evaluation; assess only architecture, capability, donor value, and concept transfer.",,,,rhasspy/piper – https://github.com/rhasspy/piper – MIT – Real-time TTS (recommended).,"rhasspy/piper is treated as repurpose for multi-project because visible metadata points to the voice / speech / audio layer. Surface signal: rhasspy/piper – https://github.com/rhasspy/piper – MIT – Real-time TTS (recommended). The fit looks real, but more as a donor/augmenter than as a standalone foundation.",memo,False,True,0.0,1.0,MU_misc,MU_misc_0004,voice / speech / audio,"Repurpose selectively for multi-project. Its source-backed role is a lean local TTS sidecar candidate, not an exclusion-only adjunct.",future/adjacent use,voice / speech / audio,repurpose,moderate modification,medium,rhasspy/piper,multi-project,,,,,,,,,,,,,,,,Original global operational v3 retained,MIT code; voice artifacts reviewed separately,known_from_reference_material,uploaded_reference_docs,no,,,,Supplemental intake references are advisory only; v6 adjudication remains the source of truth.,Usually indirect,yes,v6 unified all-project source-of-truth pack,v5_carry_forward,,4.0,5,71.0,,,,,permissive_or_noncopyleft_known,direct_incorporation_ok,"The code license is MIT and direct use is allowed. The real review point is selected voice artifacts, not the runtime code; keep voice selection separate from code adoption.",Use directly as a bounded local TTS sidecar or simple HTTP service; keep selected voice artifacts under separate review.,"Typically preserve notices, attribution, and license text where required; review chosen voices or model cards separately from the code license.",Usually unnecessary unless you later replace the runtime for packaging or architecture reasons.,high,voice-artifact-review-required,yes,,,,,,,,,,,,,v6.3_final_source_of_truth,Merged v6.1 copyleft layer and v6.2 SRE layer; use v6.3 docs + workbook as canonical handoff.,,, 11771,cubing/cubing.js,https://github.com/cubing/cubing.js,HyperTwist,5.0,152.0,185.0,A,interface / visualization / shell surface,foundation engine,visualization donor,locked strategic donor,integrate,direct,"Keep the core engine or major subsystem mostly intact; change wrappers, branding, storage/auth, and integration seams so it becomes a first-class part of the target stack. For this repo class, that usually means preserving scene/layout primitives and replacing surrounding data models or backend assumptions.",Other Notable ResourcesCubing.js library (for building your own tools): https://github.com/cubing/cubing.js – Open-source core used in many trainers above.,"Integrate as a ui / design / frontend subsystem for HyperTwist. Preserve the strongest existing pieces — component library, canvas/animation engine, interaction patterns, layout/state models, accessibility hooks, theming, editor widgets — and expose them behind a portfolio-stable interface. Wire first into HactarCE/Hyperspeedcube, then into kkoomen/qbr for orchestration, visualization, or data exchange.","Consolidate under the Hyperspeedcube + cubing.js + qbr nucleus, not beside it as a separate silo. Normalize data contracts, auth/permissions, storage, and telemetry; then attach as a service, plugin, canvas layer, trainer, or analysis module. Descending combination order: HactarCE/Hyperspeedcube, kkoomen/qbr.","Repurpose here means: turn it into a frontend interaction donor, canvas/editor pattern library, or polished shell layer on top of existing anchors.",Map module boundaries; Identify hidden reusable internals; Define adapter/API boundary to target anchors; Write extraction tests against upstream behavior; Extract layout/scene primitives; Map import/export schema; Detach UI shell from backend assumptions,full subsystem extraction review,"Hidden value often sits in scene graph/canvas model, component primitives, import/export schema, gesture/keyboard interactions, and plugin-ready layout abstractions.",Inspect scene graph/canvas data model; layout primitives; component library; keyboard/gesture interactions; import/export schema; theming; plugin or extension hooks.,"Inspect package manifests, README/docs, src tree, examples, tests, CI workflows, config files, migrations/schemas, and hidden feature flags or experimental modules. Look for reusable canvas/editor components, design tokens, state models, keyboard shortcuts, drag/drop, accessibility, virtualization, and polished interaction patterns.","Audit cubing/cubing.js as a interface / visualization / shell surface candidate for HyperTwist. Do not stop at README-level features. Inspect: Inspect scene graph/canvas data model; layout primitives; component library; keyboard/gesture interactions; import/export schema; theming; plugin or extension hooks. Decide whether the best extraction path is direct and whether it belongs as foundation engine / visualization donor. Test the three merger paths in order: 1) project-local anchor [base + donor]; 2) shared portfolio utility [augmenter]; 3) cross-project transfer candidate [future merger]. Return hidden modules, reusable schemas, protocol layers, plugin hooks, render/state models, datasets/test fixtures, and any subsystem stronger than the visible product shell.",project-local anchor,base + donor,Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.,shared portfolio utility,augmenter,Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.,cross-project transfer candidate,future merger,Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.,VectorShell | HyperTwist | ScriptoriumAI,"This capability is broadly portable across the portfolio because interaction, orchestration, and shell/UI patterns can be shared with thin domain adapters.",do not exclude,Keep in active merge-set and force full source audit before any demotion.,medium-high,single-source signal; clear taxonomy; active integration value; foundation-level fit,high,portfolio anchor or repeatedly surfaced core candidate; memo mentions: 1,"Licensing intentionally ignored as a decision filter in this canonical evaluation; assess only architecture, capability, donor value, and concept transfer.",,,,Other Notable ResourcesCubing.js library (for building your own tools): https://github.com/cubing/cubing.js – Open-source core used in many trainers above.,cubing/cubing.js is treated as integrate for HyperTwist because visible metadata points to the ui / design / frontend layer. Surface signal: Other Notable ResourcesCubing.js library (for building your own tools): https://github.com/cubing/cubing.js – Open-source core used in many trainers above. The likely value is substantial enough to preserve as a named subsystem rather than just mining isolated ideas.,memo,False,True,0.0,1.0,HT_cube_semantics,HT_cube_semantics_0001,cubing / algorithm training,Integrate primarily for HyperTwist. Its memo and bookmark signals place it in the cubing / algorithm training layer.,HyperTwist,cubing / algorithm training,integrate,moderate modification,medium,cubing/cubing.js,HyperTwist,,,,,,,,,,,,,,,,Original global operational v3 retained,MPL-2.0 OR GPL-3.0-or-later,known_from_reference_material,uploaded_reference_docs,yes,hypertwist_and_scriptoriumai,HyperTwist,HyperTwist & ScriptoriumAI.txt,Supplemental intake references are advisory only; v6 adjudication remains the source of truth.,Usually indirect,yes,v6 unified all-project source-of-truth pack,v5_carry_forward,Existing v5 row reaffirmed or widened by v6 supplemental intake.,5.0,5,152.0,Locked Strategic Donor,Boundary-sensitive classic-cubing semantics and rendering donor,,P1,mixed_or_boundary_sensitive_known,bounded_sidecar_or_selective_reimplementation,"The repo is dual-licensed MPL-2.0 OR GPL-3.0-or-later. HyperTwist can consume it as a package or bounded adapter under the MPL side, but should avoid a carefree deep private source fork of upstream files.",Prefer package/dependency consumption or a bounded adapter seam under the MPL side; avoid deep private forks of upstream source files.,Preserve MPL notices and publish modifications to MPL-covered files when distribution obligations apply; avoid assuming the GPL side is the intended operational path.,Only if you later need to replace narrow upstream-covered seams with first-party equivalents or avoid carrying MPL-governed source modifications.,high,dual-license-boundary-review,yes,,,,,,,,,,,,,v6.3_final_source_of_truth,Assigned to HT_cube_semantics during cluster normalization on 2026-04-25.,selected_not_live_boundary_sensitive,phase0r_boundary_sensitive_eval_then_adapter_or_sidecar,Phase 1R closed. Retain as a Phase 4R boundary-sensitive candidate through MPL-side dependency or adapter use; avoid deep private forks unless publication obligations are acceptable. -11848,cahidenes/rubiks-cube-solver,https://github.com/cahidenes/rubiks-cube-solver,HyperTwist,6.0,148.0,174.0,A,vision / perception / AR,foundation engine,vision donor,locked strategic donor,integrate,direct,"Keep the core engine or major subsystem mostly intact; change wrappers, branding, storage/auth, and integration seams so it becomes a first-class part of the target stack. For this repo class, that usually means preserving calibration/detection/state-reconstruction logic while replacing camera UX and integration surfaces.",cahidenes/rubiks-cube-solver — MIT — OpenCV cube detection + Kociemba solver. | cahidenes/rubiks-cube-solver — MIT — OpenCV + solver. | Yes — we already have several strong open-source visual models for cube recognition from earlier in o...,"Integrate as a computer vision / AR subsystem for HyperTwist. Preserve the strongest existing pieces — camera ingest, calibration, segmentation/detection, pose or facelet extraction, state normalization, solver bridge, replay overlay, AR anchors — and expose them behind a portfolio-stable interface. Wire first into kkoomen/qbr, then into vivaansinghvi07/rubix-cube-solver for orchestration, visualization, or data exchange.","Consolidate under the Hyperspeedcube + cubing.js + qbr nucleus, not beside it as a separate silo. Normalize data contracts, auth/permissions, storage, and telemetry; then attach as a service, plugin, canvas layer, trainer, or analysis module. Descending combination order: kkoomen/qbr, vivaansinghvi07/rubix-cube-solver, cubing/cubing.js.","Repurpose here means: turn it into a perception microservice, cube-state API, replay generator, or AR overlay donor for HyperTwist.",Map module boundaries; Identify hidden reusable internals; Define adapter/API boundary to target anchors; Write extraction tests against upstream behavior; Benchmark calibration pipeline; Extract state reconstruction; Wrap with camera/AR adapter,full subsystem extraction review,"Hidden value often sits in calibration, preprocessing, stabilization, object/state reconstruction, replay artifacts, and camera-to-domain state pipelines that are not obvious from demos.",Inspect preprocessing/calibration; tracking stabilization; state reconstruction; replay/event model; camera abstraction; fallback heuristics; testing assets/videos; performance shortcuts.,"Inspect package manifests, README/docs, src tree, examples, tests, CI workflows, config files, migrations/schemas, and hidden feature flags or experimental modules. Look for calibration routines, detection heuristics/models, color/state normalization, replay serialization, solver bridges, camera abstraction layers, and debug visualizations.","Audit cahidenes/rubiks-cube-solver as a vision / perception / AR candidate for HyperTwist. Do not stop at README-level features. Inspect: Inspect preprocessing/calibration; tracking stabilization; state reconstruction; replay/event model; camera abstraction; fallback heuristics; testing assets/videos; performance shortcuts. Decide whether the best extraction path is direct and whether it belongs as foundation engine / vision donor. Test the three merger paths in order: 1) kkoomen/qbr [foundation + perception donor]; 2) vivaansinghvi07/rubix-cube-solver [perception + replay donor]; 3) cubing/cubing.js [state/render backend]. Return hidden modules, reusable schemas, protocol layers, plugin hooks, render/state models, datasets/test fixtures, and any subsystem stronger than the visible product shell.",kkoomen/qbr,foundation + perception donor,"Use this repo against the partner as an augmenting layer; preserve the partner as the likely base and mine this repo for capabilities that improve breadth, UX, or specialization.",vivaansinghvi07/rubix-cube-solver,perception + replay donor,Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.,cubing/cubing.js,state/render backend,Use the partner for canonical state or rendering abstractions and merge this repo's specialized logic on top.,VectorShell | ScriptoriumAI,VectorShell can borrow spatial/rendering and perception primitives; ScriptoriumAI can borrow tutorial/educational visualization patterns rather than the full engine.,do not exclude,Keep in active merge-set and force full source audit before any demotion.,high,single-source signal; clear taxonomy; active integration value; foundation-level fit,high,memo mentions: 5,"Licensing intentionally ignored as a decision filter in this canonical evaluation; assess only architecture, capability, donor value, and concept transfer.",,,,"cahidenes/rubiks-cube-solver — MIT — OpenCV cube detection + Kociemba solver. | cahidenes/rubiks-cube-solver — MIT — OpenCV + solver. | Yes — we already have several strong open-source visual models for cube recognition from earlier in our conversation. I went back through the entire history and pulled the exact ones we discussed (qbr, vivaansinghvi07/rubix-cube-solver, tentone/rubix-solver, cahidenes/rubiks-cube-solver). These are still the high","cahidenes/rubiks-cube-solver is treated as integrate for HyperTwist because the current dossier keeps it active as a strategic donor for constrained capture flow, stickerless-friendly grouping, face-placement logic, and solver-handoff normalization behind the two vision anchors.",memo,False,True,0.0,5.0,HT_cube_vision,HT_cube_vision_0003,computer vision / AR,Integrate primarily for HyperTwist. Its memo and bookmark signals place it in the computer vision / AR layer.,HyperTwist,computer vision / AR,integrate,heavy modification,medium,cahidenes/rubiks-cube-solver,HyperTwist,,,,,,,,,,,,,,,,Original global operational v3 retained,MIT,known_from_reference_material,uploaded_reference_docs,no,,,,Supplemental intake references are advisory only; v6 adjudication remains the source of truth.,Usually indirect,yes,v6 unified all-project source-of-truth pack,v5_carry_forward,,6.0,5,148.0,Locked Strategic Donor,Active recognition-heuristics and validation donor,,,permissive_or_noncopyleft_known,direct_incorporation_ok,"This repo is aligned with a direct integration path for HyperTwist because it is either already implemented, strategically central, or donor-grade without a visible copyleft constraint in the current materials. Deep incorporation is sensible if the source audit confirms architectural cleanliness.","Direct embed, vendored module, package dependency, or tightly integrated adapter as the architecture requires.","Typically preserve notices, attribution, and license text where required; no special copyleft-driven disclosure posture is normally needed.",Usually unnecessary unless you later decide the existing implementation is too constraining architecturally.,high,strategic-or-implemented-component,yes,,,,,,,,,,,,,v6.3_final_source_of_truth,Normalized legacy candidate-core wording to dossier-backed strategic-donor posture on 2026-04-25.,selected_not_live_permissive_candidate,phase0r_permissive_eval_then_implement,"Phase 1R closed. Retain as a Phase 3R permissive implementation candidate; implement only from its packet authority and the retained-set contract, not by reopening Phase 0R." -11852,tentone/rubix-solver,https://github.com/tentone/rubix-solver,HyperTwist,7.0,148.0,174.0,A,vision / perception / AR,foundation engine,vision donor,locked strategic donor,integrate,direct,"Keep the core engine or major subsystem mostly intact; change wrappers, branding, storage/auth, and integration seams so it becomes a first-class part of the target stack. For this repo class, that usually means preserving calibration/detection/state-reconstruction logic while replacing camera UX and integration surfaces.","tentone/rubix-solver — MIT — OpenCV cube detection. | Yes — 100% possible to consolidate everything into one no-compromises, enterprise-grade platform. You're not half-arsing it, and neither am I. Modern vision models (and even classical...","Integrate as a computer vision / AR subsystem for HyperTwist. Preserve the strongest existing pieces — camera ingest, calibration, segmentation/detection, pose or facelet extraction, state normalization, solver bridge, replay overlay, AR anchors — and expose them behind a portfolio-stable interface. Wire first into kkoomen/qbr, then into vivaansinghvi07/rubix-cube-solver for orchestration, visualization, or data exchange.","Consolidate under the Hyperspeedcube + cubing.js + qbr nucleus, not beside it as a separate silo. Normalize data contracts, auth/permissions, storage, and telemetry; then attach as a service, plugin, canvas layer, trainer, or analysis module. Descending combination order: kkoomen/qbr, vivaansinghvi07/rubix-cube-solver, cubing/cubing.js.","Repurpose here means: turn it into a perception microservice, cube-state API, replay generator, or AR overlay donor for HyperTwist.",Map module boundaries; Identify hidden reusable internals; Define adapter/API boundary to target anchors; Write extraction tests against upstream behavior; Benchmark calibration pipeline; Extract state reconstruction; Wrap with camera/AR adapter,full subsystem extraction review,"Hidden value often sits in calibration, preprocessing, stabilization, object/state reconstruction, replay artifacts, and camera-to-domain state pipelines that are not obvious from demos.",Inspect preprocessing/calibration; tracking stabilization; state reconstruction; replay/event model; camera abstraction; fallback heuristics; testing assets/videos; performance shortcuts.,"Inspect package manifests, README/docs, src tree, examples, tests, CI workflows, config files, migrations/schemas, and hidden feature flags or experimental modules. Look for calibration routines, detection heuristics/models, color/state normalization, replay serialization, solver bridges, camera abstraction layers, and debug visualizations.","Audit tentone/rubix-solver as a vision / perception / AR candidate for HyperTwist. Do not stop at README-level features. Inspect: Inspect preprocessing/calibration; tracking stabilization; state reconstruction; replay/event model; camera abstraction; fallback heuristics; testing assets/videos; performance shortcuts. Decide whether the best extraction path is direct and whether it belongs as foundation engine / vision donor. Test the three merger paths in order: 1) kkoomen/qbr [foundation + perception donor]; 2) vivaansinghvi07/rubix-cube-solver [perception + replay donor]; 3) cubing/cubing.js [state/render backend]. Return hidden modules, reusable schemas, protocol layers, plugin hooks, render/state models, datasets/test fixtures, and any subsystem stronger than the visible product shell.",kkoomen/qbr,foundation + perception donor,"Use this repo against the partner as an augmenting layer; preserve the partner as the likely base and mine this repo for capabilities that improve breadth, UX, or specialization.",vivaansinghvi07/rubix-cube-solver,perception + replay donor,Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.,cubing/cubing.js,state/render backend,Use the partner for canonical state or rendering abstractions and merge this repo's specialized logic on top.,VectorShell | ScriptoriumAI,VectorShell can borrow spatial/rendering and perception primitives; ScriptoriumAI can borrow tutorial/educational visualization patterns rather than the full engine.,do not exclude,Keep in active merge-set and force full source audit before any demotion.,high,single-source signal; clear taxonomy; active integration value; foundation-level fit,high,memo mentions: 7,"Licensing intentionally ignored as a decision filter in this canonical evaluation; assess only architecture, capability, donor value, and concept transfer.",,,,"tentone/rubix-solver — MIT — OpenCV cube detection. | Yes — 100% possible to consolidate everything into one no-compromises, enterprise-grade platform. You're not half-arsing it, and neither am I. Modern vision models (and even classical OpenCV pipelines refined over the last decade) are more than accurate enough in 2026 for reliable small-square/facelet color recognition on a standard 3x3 (or larger) Rubik's Cube under normal lighting. Productio","tentone/rubix-solver is treated as integrate for HyperTwist because the current dossier keeps it active as a strategic donor for compact C++ and OpenCV detection heuristics and comparison-bench value, not for its brute-force solver shell.",memo,False,True,0.0,7.0,HT_cube_vision,HT_cube_vision_0004,computer vision / AR,Integrate primarily for HyperTwist. Its memo and bookmark signals place it in the computer vision / AR layer.,HyperTwist,computer vision / AR,integrate,heavy modification,medium,tentone/rubix-solver,HyperTwist,,,,,,,,,,,,,,,,Original global operational v3 retained,MIT,known_from_reference_material,uploaded_reference_docs,no,,,,Supplemental intake references are advisory only; v6 adjudication remains the source of truth.,Usually indirect,yes,v6 unified all-project source-of-truth pack,v5_carry_forward,,7.0,5,148.0,Locked Strategic Donor,Active native-CV donor and comparison bench,,,permissive_or_noncopyleft_known,direct_incorporation_ok,"This repo is aligned with a direct integration path for HyperTwist because it is either already implemented, strategically central, or donor-grade without a visible copyleft constraint in the current materials. Deep incorporation is sensible if the source audit confirms architectural cleanliness.","Direct embed, vendored module, package dependency, or tightly integrated adapter as the architecture requires.","Typically preserve notices, attribution, and license text where required; no special copyleft-driven disclosure posture is normally needed.",Usually unnecessary unless you later decide the existing implementation is too constraining architecturally.,high,strategic-or-implemented-component,yes,,,,,,,,,,,,,v6.3_final_source_of_truth,Normalized legacy candidate-core wording to dossier-backed strategic-donor posture on 2026-04-25.,selected_not_live_permissive_candidate,phase0r_permissive_eval_then_implement,"Phase 1R closed. Retain as a Phase 3R permissive implementation candidate; implement only from its packet authority and the retained-set contract, not by reopening Phase 0R." +11848,cahidenes/rubiks-cube-solver,https://github.com/cahidenes/rubiks-cube-solver,HyperTwist,6.0,148.0,174.0,A,vision / perception / AR,foundation engine,vision donor,locked strategic donor,integrate,direct,"Keep the core engine or major subsystem mostly intact; change wrappers, branding, storage/auth, and integration seams so it becomes a first-class part of the target stack. For this repo class, that usually means preserving calibration/detection/state-reconstruction logic while replacing camera UX and integration surfaces.",cahidenes/rubiks-cube-solver — MIT — OpenCV cube detection + Kociemba solver. | cahidenes/rubiks-cube-solver — MIT — OpenCV + solver. | Yes — we already have several strong open-source visual models for cube recognition from earlier in o...,"Integrate as a computer vision / AR subsystem for HyperTwist. Preserve the strongest existing pieces — camera ingest, calibration, segmentation/detection, pose or facelet extraction, state normalization, solver bridge, replay overlay, AR anchors — and expose them behind a portfolio-stable interface. Wire first into kkoomen/qbr, then into vivaansinghvi07/rubix-cube-solver for orchestration, visualization, or data exchange.","Consolidate under the Hyperspeedcube + cubing.js + qbr nucleus, not beside it as a separate silo. Normalize data contracts, auth/permissions, storage, and telemetry; then attach as a service, plugin, canvas layer, trainer, or analysis module. Descending combination order: kkoomen/qbr, vivaansinghvi07/rubix-cube-solver, cubing/cubing.js.","Repurpose here means: turn it into a perception microservice, cube-state API, replay generator, or AR overlay donor for HyperTwist.",Map module boundaries; Identify hidden reusable internals; Define adapter/API boundary to target anchors; Write extraction tests against upstream behavior; Benchmark calibration pipeline; Extract state reconstruction; Wrap with camera/AR adapter,full subsystem extraction review,"Hidden value often sits in calibration, preprocessing, stabilization, object/state reconstruction, replay artifacts, and camera-to-domain state pipelines that are not obvious from demos.",Inspect preprocessing/calibration; tracking stabilization; state reconstruction; replay/event model; camera abstraction; fallback heuristics; testing assets/videos; performance shortcuts.,"Inspect package manifests, README/docs, src tree, examples, tests, CI workflows, config files, migrations/schemas, and hidden feature flags or experimental modules. Look for calibration routines, detection heuristics/models, color/state normalization, replay serialization, solver bridges, camera abstraction layers, and debug visualizations.","Audit cahidenes/rubiks-cube-solver as a vision / perception / AR candidate for HyperTwist. Do not stop at README-level features. Inspect: Inspect preprocessing/calibration; tracking stabilization; state reconstruction; replay/event model; camera abstraction; fallback heuristics; testing assets/videos; performance shortcuts. Decide whether the best extraction path is direct and whether it belongs as foundation engine / vision donor. Test the three merger paths in order: 1) kkoomen/qbr [foundation + perception donor]; 2) vivaansinghvi07/rubix-cube-solver [perception + replay donor]; 3) cubing/cubing.js [state/render backend]. Return hidden modules, reusable schemas, protocol layers, plugin hooks, render/state models, datasets/test fixtures, and any subsystem stronger than the visible product shell.",kkoomen/qbr,foundation + perception donor,"Use this repo against the partner as an augmenting layer; preserve the partner as the likely base and mine this repo for capabilities that improve breadth, UX, or specialization.",vivaansinghvi07/rubix-cube-solver,perception + replay donor,Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.,cubing/cubing.js,state/render backend,Use the partner for canonical state or rendering abstractions and merge this repo's specialized logic on top.,VectorShell | ScriptoriumAI,VectorShell can borrow spatial/rendering and perception primitives; ScriptoriumAI can borrow tutorial/educational visualization patterns rather than the full engine.,do not exclude,Keep in active merge-set and force full source audit before any demotion.,high,single-source signal; clear taxonomy; active integration value; foundation-level fit,high,memo mentions: 5,"Licensing intentionally ignored as a decision filter in this canonical evaluation; assess only architecture, capability, donor value, and concept transfer.",,,,"cahidenes/rubiks-cube-solver — MIT — OpenCV cube detection + Kociemba solver. | cahidenes/rubiks-cube-solver — MIT — OpenCV + solver. | Yes — we already have several strong open-source visual models for cube recognition from earlier in our conversation. I went back through the entire history and pulled the exact ones we discussed (qbr, vivaansinghvi07/rubix-cube-solver, tentone/rubix-solver, cahidenes/rubiks-cube-solver). These are still the high","cahidenes/rubiks-cube-solver is treated as integrate for HyperTwist because the current dossier keeps it active as a strategic donor for constrained capture flow, stickerless-friendly grouping, face-placement logic, and solver-handoff normalization behind the two vision anchors.",memo,False,True,0.0,5.0,HT_cube_vision,HT_cube_vision_0003,computer vision / AR,Integrate primarily for HyperTwist. Its memo and bookmark signals place it in the computer vision / AR layer.,HyperTwist,computer vision / AR,integrate,heavy modification,medium,cahidenes/rubiks-cube-solver,HyperTwist,,,,,,,,,,,,,,,,Original global operational v3 retained,MIT,known_from_reference_material,uploaded_reference_docs,no,,,,Supplemental intake references are advisory only; v6 adjudication remains the source of truth.,Usually indirect,yes,v6 unified all-project source-of-truth pack,v5_carry_forward,,6.0,5,148.0,Locked Strategic Donor,Active recognition-heuristics and validation donor,,,permissive_or_noncopyleft_known,direct_incorporation_ok,"This repo is aligned with a direct integration path for HyperTwist because it is either already implemented, strategically central, or donor-grade without a visible copyleft constraint in the current materials. Deep incorporation is sensible if the source audit confirms architectural cleanliness.","Direct embed, vendored module, package dependency, or tightly integrated adapter as the architecture requires.","Typically preserve notices, attribution, and license text where required; no special copyleft-driven disclosure posture is normally needed.",Usually unnecessary unless you later decide the existing implementation is too constraining architecturally.,high,strategic-or-implemented-component,yes,,,,,,,,,,,,,v6.3_final_source_of_truth,Normalized legacy candidate-core wording to dossier-backed strategic-donor posture on 2026-04-25.,implemented_live_permissive,landed_permissive_preserve,"Phase 3R-E closed. Preserve as the landed first-party embodied companion, narration, lip-sync, gesture, subtitle, and avatar-embed lane; start future widening from the live-lane audit, then the 3R-E implementation packet, then REPO_LICENSE_TRACKING.md." +11852,tentone/rubix-solver,https://github.com/tentone/rubix-solver,HyperTwist,7.0,148.0,174.0,A,vision / perception / AR,foundation engine,vision donor,locked strategic donor,integrate,direct,"Keep the core engine or major subsystem mostly intact; change wrappers, branding, storage/auth, and integration seams so it becomes a first-class part of the target stack. For this repo class, that usually means preserving calibration/detection/state-reconstruction logic while replacing camera UX and integration surfaces.","tentone/rubix-solver — MIT — OpenCV cube detection. | Yes — 100% possible to consolidate everything into one no-compromises, enterprise-grade platform. You're not half-arsing it, and neither am I. Modern vision models (and even classical...","Integrate as a computer vision / AR subsystem for HyperTwist. Preserve the strongest existing pieces — camera ingest, calibration, segmentation/detection, pose or facelet extraction, state normalization, solver bridge, replay overlay, AR anchors — and expose them behind a portfolio-stable interface. Wire first into kkoomen/qbr, then into vivaansinghvi07/rubix-cube-solver for orchestration, visualization, or data exchange.","Consolidate under the Hyperspeedcube + cubing.js + qbr nucleus, not beside it as a separate silo. Normalize data contracts, auth/permissions, storage, and telemetry; then attach as a service, plugin, canvas layer, trainer, or analysis module. Descending combination order: kkoomen/qbr, vivaansinghvi07/rubix-cube-solver, cubing/cubing.js.","Repurpose here means: turn it into a perception microservice, cube-state API, replay generator, or AR overlay donor for HyperTwist.",Map module boundaries; Identify hidden reusable internals; Define adapter/API boundary to target anchors; Write extraction tests against upstream behavior; Benchmark calibration pipeline; Extract state reconstruction; Wrap with camera/AR adapter,full subsystem extraction review,"Hidden value often sits in calibration, preprocessing, stabilization, object/state reconstruction, replay artifacts, and camera-to-domain state pipelines that are not obvious from demos.",Inspect preprocessing/calibration; tracking stabilization; state reconstruction; replay/event model; camera abstraction; fallback heuristics; testing assets/videos; performance shortcuts.,"Inspect package manifests, README/docs, src tree, examples, tests, CI workflows, config files, migrations/schemas, and hidden feature flags or experimental modules. Look for calibration routines, detection heuristics/models, color/state normalization, replay serialization, solver bridges, camera abstraction layers, and debug visualizations.","Audit tentone/rubix-solver as a vision / perception / AR candidate for HyperTwist. Do not stop at README-level features. Inspect: Inspect preprocessing/calibration; tracking stabilization; state reconstruction; replay/event model; camera abstraction; fallback heuristics; testing assets/videos; performance shortcuts. Decide whether the best extraction path is direct and whether it belongs as foundation engine / vision donor. Test the three merger paths in order: 1) kkoomen/qbr [foundation + perception donor]; 2) vivaansinghvi07/rubix-cube-solver [perception + replay donor]; 3) cubing/cubing.js [state/render backend]. Return hidden modules, reusable schemas, protocol layers, plugin hooks, render/state models, datasets/test fixtures, and any subsystem stronger than the visible product shell.",kkoomen/qbr,foundation + perception donor,"Use this repo against the partner as an augmenting layer; preserve the partner as the likely base and mine this repo for capabilities that improve breadth, UX, or specialization.",vivaansinghvi07/rubix-cube-solver,perception + replay donor,Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.,cubing/cubing.js,state/render backend,Use the partner for canonical state or rendering abstractions and merge this repo's specialized logic on top.,VectorShell | ScriptoriumAI,VectorShell can borrow spatial/rendering and perception primitives; ScriptoriumAI can borrow tutorial/educational visualization patterns rather than the full engine.,do not exclude,Keep in active merge-set and force full source audit before any demotion.,high,single-source signal; clear taxonomy; active integration value; foundation-level fit,high,memo mentions: 7,"Licensing intentionally ignored as a decision filter in this canonical evaluation; assess only architecture, capability, donor value, and concept transfer.",,,,"tentone/rubix-solver — MIT — OpenCV cube detection. | Yes — 100% possible to consolidate everything into one no-compromises, enterprise-grade platform. You're not half-arsing it, and neither am I. Modern vision models (and even classical OpenCV pipelines refined over the last decade) are more than accurate enough in 2026 for reliable small-square/facelet color recognition on a standard 3x3 (or larger) Rubik's Cube under normal lighting. Productio","tentone/rubix-solver is treated as integrate for HyperTwist because the current dossier keeps it active as a strategic donor for compact C++ and OpenCV detection heuristics and comparison-bench value, not for its brute-force solver shell.",memo,False,True,0.0,7.0,HT_cube_vision,HT_cube_vision_0004,computer vision / AR,Integrate primarily for HyperTwist. Its memo and bookmark signals place it in the computer vision / AR layer.,HyperTwist,computer vision / AR,integrate,heavy modification,medium,tentone/rubix-solver,HyperTwist,,,,,,,,,,,,,,,,Original global operational v3 retained,MIT,known_from_reference_material,uploaded_reference_docs,no,,,,Supplemental intake references are advisory only; v6 adjudication remains the source of truth.,Usually indirect,yes,v6 unified all-project source-of-truth pack,v5_carry_forward,,7.0,5,148.0,Locked Strategic Donor,Active native-CV donor and comparison bench,,,permissive_or_noncopyleft_known,direct_incorporation_ok,"This repo is aligned with a direct integration path for HyperTwist because it is either already implemented, strategically central, or donor-grade without a visible copyleft constraint in the current materials. Deep incorporation is sensible if the source audit confirms architectural cleanliness.","Direct embed, vendored module, package dependency, or tightly integrated adapter as the architecture requires.","Typically preserve notices, attribution, and license text where required; no special copyleft-driven disclosure posture is normally needed.",Usually unnecessary unless you later decide the existing implementation is too constraining architecturally.,high,strategic-or-implemented-component,yes,,,,,,,,,,,,,v6.3_final_source_of_truth,Normalized legacy candidate-core wording to dossier-backed strategic-donor posture on 2026-04-25.,implemented_live_permissive,landed_permissive_preserve,"Phase 3R-E closed. Preserve as the landed first-party embodied companion, narration, lip-sync, gesture, subtitle, and avatar-embed lane; start future widening from the live-lane audit, then the 3R-E implementation packet, then REPO_LICENSE_TRACKING.md." 11857,Lykos/cube_trainer,https://github.com/Lykos/cube_trainer,HyperTwist,8.0,145.0,171.0,A,cubing trainer / solver / timing,foundation engine,training donor,locked strategic donor,integrate,direct,"Keep the core engine or major subsystem mostly intact; change wrappers, branding, storage/auth, and integration seams so it becomes a first-class part of the target stack. For this repo class, that usually means preserving cube-state, scramble, scheduling, or timer internals while adapting pedagogy, analytics, and UI.",Lykos/cube_trainer — MIT — Smart-sampled training. | CubeTrainer (Lykos/cube_trainer) | Lykos/cube_trainer — MIT — Smart-sampled alg/BLD trainer. Live: https://www.cubetrainer.org.,"Integrate as a cubing / algorithm training subsystem for HyperTwist. Preserve the strongest existing pieces — scramble generation, algorithm database, recognition/training loop, timing/statistics, virtual cube, smartcube hooks, spaced repetition — and expose them behind a portfolio-stable interface. Wire first into tao-yu/Alg-Trainer, then into poliva/cubedex for orchestration, visualization, or data exchange.","Consolidate under the Hyperspeedcube + cubing.js + qbr nucleus, not beside it as a separate silo. Normalize data contracts, auth/permissions, storage, and telemetry; then attach as a service, plugin, canvas layer, trainer, or analysis module. Descending combination order: tao-yu/Alg-Trainer, poliva/cubedex, cubing/cubing.js.","Repurpose here means: turn it into a trainer engine, solver/timer backend, recognition drill module, or method-specific practice mode for HyperTwist.",Map module boundaries; Identify hidden reusable internals; Define adapter/API boundary to target anchors; Write extraction tests against upstream behavior; Extract cube-state model; Normalize trainer/case schema; Expose analytics and replay hooks,full subsystem extraction review,"Hidden value often sits in cube-state representation, scramble generation, weighted drill scheduling, recognition datasets, replay/timer internals, and case database schemas.",Inspect cube-state model; scramble generator; trainer weighting/scheduling; case database and metadata; replay/timer model; import/export of alg sets; smartcube or sensor adapters.,"Inspect package manifests, README/docs, src tree, examples, tests, CI workflows, config files, migrations/schemas, and hidden feature flags or experimental modules. Look for algorithm databases, spaced-repetition logic, scramble generation, timer/stat code, virtual cube components, smartcube adapters, and custom-trainer configuration support.","Audit Lykos/cube_trainer as a cubing trainer / solver / timing candidate for HyperTwist. Do not stop at README-level features. Inspect: Inspect cube-state model; scramble generator; trainer weighting/scheduling; case database and metadata; replay/timer model; import/export of alg sets; smartcube or sensor adapters. Decide whether the best extraction path is direct and whether it belongs as foundation engine / training donor. Test the three merger paths in order: 1) tao-yu/Alg-Trainer [base + donor swarm]; 2) poliva/cubedex [specialized training UX donor]; 3) cross-project transfer candidate [future merger]. Return hidden modules, reusable schemas, protocol layers, plugin hooks, render/state models, datasets/test fixtures, and any subsystem stronger than the visible product shell.",tao-yu/Alg-Trainer,base + donor swarm,Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.,poliva/cubedex,specialized training UX donor,Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.,cross-project transfer candidate,future merger,Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.,project-local first,"Cross-project transfer is possible, but the value is clearest inside the assigned project until source audit exposes more reusable primitives.",do not exclude,Keep in active merge-set and force full source audit before any demotion.,high,single-source signal; clear taxonomy; active integration value; foundation-level fit,high,strong adjacency to identified core stack; memo mentions: 4,"Licensing intentionally ignored as a decision filter in this canonical evaluation; assess only architecture, capability, donor value, and concept transfer.",,,,Lykos/cube_trainer — MIT — Smart-sampled training. | CubeTrainer (Lykos/cube_trainer) | Lykos/cube_trainer — MIT — Smart-sampled alg/BLD trainer. Live: https://www.cubetrainer.org.,"Lykos/cube_trainer is treated as integrate for HyperTwist because the current dossier keeps it as a top-tier strategic donor for persisted sessions, results and statistics, personalization, and advanced BLD-oriented training-domain concepts rather than as a shell to transplant wholesale.",memo,False,True,0.0,4.0,HT_training_stack,HT_training_stack_0002,cubing / algorithm training,Integrate primarily for HyperTwist. Its memo and bookmark signals place it in the cubing / algorithm training layer.,HyperTwist,cubing / algorithm training,integrate,moderate modification,medium,lykos/cube_trainer,HyperTwist,,,,,,,,,,,,,,,,Original global operational v3 retained,MIT,known_from_reference_material,uploaded_reference_docs,no,,,,Supplemental intake references are advisory only; v6 adjudication remains the source of truth.,Usually indirect,yes,v6 unified all-project source-of-truth pack,v5_carry_forward,,8.0,5,145.0,Locked Strategic Donor,Top-tier persistent training-domain donor,,,permissive_or_noncopyleft_known,direct_incorporation_ok,"This repo is aligned with a direct integration path for HyperTwist because it is either already implemented, strategically central, or donor-grade without a visible copyleft constraint in the current materials. Deep incorporation is sensible if the source audit confirms architectural cleanliness.","Direct embed, vendored module, package dependency, or tightly integrated adapter as the architecture requires.","Typically preserve notices, attribution, and license text where required; no special copyleft-driven disclosure posture is normally needed.",Usually unnecessary unless you later decide the existing implementation is too constraining architecturally.,high,strategic-or-implemented-component,yes,,,,,,,,,,,,,v6.3_final_source_of_truth,Normalized legacy candidate-core wording to dossier-backed strategic-donor posture on 2026-04-25.,implemented_live_permissive,landed_permissive_preserve,Phase 1R closed. Preserve as a landed first-party permissive lane; keep notices and attribution visible and widen only through ordinary owned enhancement work. 11861,poliva/cubedex,https://github.com/poliva/cubedex,HyperTwist,9.0,145.0,171.0,A,interface / visualization / shell surface,foundation engine,visualization donor,locked strategic donor,integrate,direct,"Keep the core engine or major subsystem mostly intact; change wrappers, branding, storage/auth, and integration seams so it becomes a first-class part of the target stack. For this repo class, that usually means preserving scene/layout primitives and replacing surrounding data models or backend assumptions.","poliva/cubedex — MIT — Smartcube alg trainer. | Open source repositories and software specifically designed to drill (""hammer"") Rubik's Cube algorithms into muscle memory through repeated practice, timing, smart sampling, real scrambles,...","Integrate as a cubing / algorithm training subsystem for HyperTwist. Preserve the strongest existing pieces — scramble generation, algorithm database, recognition/training loop, timing/statistics, virtual cube, smartcube hooks, spaced repetition — and expose them behind a portfolio-stable interface. Wire first into tao-yu/Alg-Trainer, then into Lykos/cube_trainer for orchestration, visualization, or data exchange.","Consolidate under the Hyperspeedcube + cubing.js + qbr nucleus, not beside it as a separate silo. Normalize data contracts, auth/permissions, storage, and telemetry; then attach as a service, plugin, canvas layer, trainer, or analysis module. Descending combination order: tao-yu/Alg-Trainer, Lykos/cube_trainer, cubing/cubing.js.","Repurpose here means: turn it into a trainer engine, solver/timer backend, recognition drill module, or method-specific practice mode for HyperTwist.",Map module boundaries; Identify hidden reusable internals; Define adapter/API boundary to target anchors; Write extraction tests against upstream behavior; Extract layout/scene primitives; Map import/export schema; Detach UI shell from backend assumptions,full subsystem extraction review,"Hidden value often sits in scene graph/canvas model, component primitives, import/export schema, gesture/keyboard interactions, and plugin-ready layout abstractions.",Inspect scene graph/canvas data model; layout primitives; component library; keyboard/gesture interactions; import/export schema; theming; plugin or extension hooks.,"Inspect package manifests, README/docs, src tree, examples, tests, CI workflows, config files, migrations/schemas, and hidden feature flags or experimental modules. Look for algorithm databases, spaced-repetition logic, scramble generation, timer/stat code, virtual cube components, smartcube adapters, and custom-trainer configuration support.","Audit poliva/cubedex as a interface / visualization / shell surface candidate for HyperTwist. Do not stop at README-level features. Inspect: Inspect scene graph/canvas data model; layout primitives; component library; keyboard/gesture interactions; import/export schema; theming; plugin or extension hooks. Decide whether the best extraction path is direct and whether it belongs as foundation engine / visualization donor. Test the three merger paths in order: 1) project-local anchor [base + donor]; 2) shared portfolio utility [augmenter]; 3) cross-project transfer candidate [future merger]. Return hidden modules, reusable schemas, protocol layers, plugin hooks, render/state models, datasets/test fixtures, and any subsystem stronger than the visible product shell.",project-local anchor,base + donor,Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.,shared portfolio utility,augmenter,Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.,cross-project transfer candidate,future merger,Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.,VectorShell | HyperTwist | ScriptoriumAI,"This capability is broadly portable across the portfolio because interaction, orchestration, and shell/UI patterns can be shared with thin domain adapters.",do not exclude,Keep in active merge-set and force full source audit before any demotion.,high,single-source signal; clear taxonomy; active integration value; foundation-level fit,high,strong adjacency to identified core stack; memo mentions: 4,"Licensing intentionally ignored as a decision filter in this canonical evaluation; assess only architecture, capability, donor value, and concept transfer.",,,,"poliva/cubedex — MIT — Smartcube alg trainer. | Open source repositories and software specifically designed to drill (""hammer"") Rubik's Cube algorithms into muscle memory through repeated practice, timing, smart sampling, real scrambles, virtual cubes, and/or smartcube integration.These tools focus on repetitive training for sets like PLL, OLL, ZBLL, etc., rather than just solving the whole cube.Cubedex (poliva/cubedex) | poliva/cubedex, tao-yu/A","poliva/cubedex is treated as integrate for HyperTwist because the current dossier keeps it as a top-tier strategic donor for smartcube-aware, offline-first training UX, case-card design, and drill ergonomics without promoting it to training-lane foundation status.",memo,False,True,0.0,4.0,HT_training_stack,HT_training_stack_0016,cubing / algorithm training,Integrate primarily for HyperTwist. Its memo and bookmark signals place it in the cubing / algorithm training layer.,HyperTwist,cubing / algorithm training,integrate,moderate modification,medium,poliva/cubedex,HyperTwist,,,,,,,,,,,,,,,,Original global operational v3 retained,MIT,known_from_reference_material,uploaded_reference_docs,no,,,,Supplemental intake references are advisory only; v6 adjudication remains the source of truth.,Usually indirect,yes,v6 unified all-project source-of-truth pack,v5_carry_forward,,9.0,5,145.0,Locked Strategic Donor,Top-tier training UX and smartcube donor,,,permissive_or_noncopyleft_known,direct_incorporation_ok,"This repo is aligned with a direct integration path for HyperTwist because it is either already implemented, strategically central, or donor-grade without a visible copyleft constraint in the current materials. Deep incorporation is sensible if the source audit confirms architectural cleanliness.","Direct embed, vendored module, package dependency, or tightly integrated adapter as the architecture requires.","Typically preserve notices, attribution, and license text where required; no special copyleft-driven disclosure posture is normally needed.",Usually unnecessary unless you later decide the existing implementation is too constraining architecturally.,high,strategic-or-implemented-component,yes,,,,,,,,,,,,,v6.3_final_source_of_truth,Assigned from legacy HY_misc to HT_training_stack during cluster normalization on 2026-04-25.,implemented_live_permissive,landed_permissive_preserve,Phase 1R closed. Preserve as a landed first-party permissive lane; keep notices and attribution visible and widen only through ordinary owned enhancement work. 11865,kash/cubedesk,https://github.com/kash/cubedesk,HyperTwist,10.0,145.0,171.0,A,hypercubing / nD engine,foundation engine,simulation donor,locked strategic donor,repurpose,architecture only,"Keep the core engine or major subsystem mostly intact; change wrappers, branding, storage/auth, and integration seams so it becomes a first-class part of the target stack. For this repo class, that usually means preserving generalized puzzle/state/render logic while building a new application shell around it.",AGPL / GPL / Strong Copyleft (Forces open-sourcing derivatives — study/reference only or use as backend/service; avoid for closed-source core)kash/cubedesk — GPL-3.0 — Full timer + 750+ alg trainers + analytics/community platform. Live: ...,"Integrate as a hypercubing / nD simulation subsystem for HyperTwist. Preserve the strongest existing pieces — nD state model, move notation, renderer, projection controls, solver/traversal logic, puzzle serialization, replay — and expose them behind a portfolio-stable interface. Wire first into HactarCE/Hyperspeedcube, then into cubing/cubing.js for orchestration, visualization, or data exchange.","Consolidate under the Hyperspeedcube + cubing.js + qbr nucleus, not beside it as a separate silo. Normalize data contracts, auth/permissions, storage, and telemetry; then attach as a service, plugin, canvas layer, trainer, or analysis module. Descending combination order: HactarCE/Hyperspeedcube, cubing/cubing.js, tao-yu/Alg-Trainer.",Repurpose here means: turn it into a higher-dimensional renderer/simulator donor and shared interaction grammar for HyperTwist and long-horizon VectorShell.,Map module boundaries; Identify hidden reusable internals; Define adapter/API boundary to target anchors; Write extraction tests against upstream behavior; Isolate puzzle/state core; Extract render/input abstractions; Document notation and save format,full subsystem extraction review,"Hidden value is likely in generalized puzzle/state representations, higher-dimensional transforms, notation systems, save formats, puzzle generators, and rendering abstractions.",Inspect generalized puzzle/state model; notation parser; transform math; rendering abstraction; save/load format; puzzle generator; input mapping; performance optimizations.,"Inspect package manifests, README/docs, src tree, examples, tests, CI workflows, config files, migrations/schemas, and hidden feature flags or experimental modules. Look for higher-dimensional state/notation representations, projection math, renderer abstractions, puzzle serialization, controls, and replay/training hooks.","Audit kash/cubedesk as a hypercubing / nD engine candidate for HyperTwist. Do not stop at README-level features. Inspect: Inspect generalized puzzle/state model; notation parser; transform math; rendering abstraction; save/load format; puzzle generator; input mapping; performance optimizations. Decide whether the best extraction path is direct and whether it belongs as foundation engine / simulation donor. Test the three merger paths in order: 1) HactarCE/Hyperspeedcube [foundation + donor]; 2) cubing/cubing.js [3D engine + notation/state donor]; 3) tao-yu/Alg-Trainer [training UX donor]. Return hidden modules, reusable schemas, protocol layers, plugin hooks, render/state models, datasets/test fixtures, and any subsystem stronger than the visible product shell.",HactarCE/Hyperspeedcube,foundation + donor,"Use this repo against the partner as an augmenting layer; preserve the partner as the likely base and mine this repo for capabilities that improve breadth, UX, or specialization.",cubing/cubing.js,3D engine + notation/state donor,Use the partner for canonical state or rendering abstractions and merge this repo's specialized logic on top.,tao-yu/Alg-Trainer,training UX donor,Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.,VectorShell | ScriptoriumAI,VectorShell can borrow spatial/rendering and perception primitives; ScriptoriumAI can borrow tutorial/educational visualization patterns rather than the full engine.,do not exclude,Keep in active merge-set and force full source audit before any demotion.,high,single-source signal; clear taxonomy; active integration value; foundation-level fit,high,memo mentions: 4,"Licensing intentionally ignored as a decision filter in this canonical evaluation; assess only architecture, capability, donor value, and concept transfer.",,,,AGPL / GPL / Strong Copyleft (Forces open-sourcing derivatives — study/reference only or use as backend/service; avoid for closed-source core)kash/cubedesk — GPL-3.0 — Full timer + 750+ alg trainers + analytics/community platform. Live: https://www.cubedesk.io. | cubing.js (MPL with MIT-vendored parts) remains the 3D foundation — pair with Hyperspeedcube for nD.AGPL / GPL / Strong Copyleft (Study/reference only or backend; avoid for closed-source,"kash/cubedesk is treated as repurpose for HyperTwist because the current dossier keeps it as a restrictive clean-room donor target for timer, trainer, solve/session/stat, smart-device, membership-gating, and broader cubing-platform architecture rather than as a direct donor or foundation.",memo,False,True,0.0,4.0,HT_hyper_engine,HT_hyper_engine_0002,cubing / algorithm training,"Integrate primarily for HyperTwist. The memo context explicitly treats it as a nucleus, foundation, or unusually high-value building block.",HyperTwist,hypercubing / nD simulation,integrate,direct,medium,kash/cubedesk,HyperTwist,,,,,,,,,,,,,,,,Original global operational v3 retained,GPLv3-or-later in README/LICENSE; package.json says All Rights Reserved,known_from_reference_material,uploaded_reference_docs,no,,,,Supplemental intake references are advisory only; v6 adjudication remains the source of truth.,Usually indirect,yes,v6 unified all-project source-of-truth pack,v5_carry_forward,,10.0,5,145.0,Locked Strategic Donor,Restrictive clean-room donor target,,P1,mixed_or_boundary_sensitive_known,reverse_engineer_preferred,"The repo has conflicting license signals and should remain in restrictive clean-room custody. Treat it as a strategic product-pattern and subsystem extraction target, not as direct donor code.",Model A may inspect and extract product/subsystem behavior; Model B should implement only from a scrubbed first-party specification.,Do not incorporate directly until the license contradiction is fully resolved; current HyperTwist posture is clean-room donor only.,Yes — this is the preferred path because the strategic value is broad but direct reuse is blocked by the contradictory license posture.,high,license-contradiction-clean-room-donor,no,,,,,,,,,,,,,v6.3_final_source_of_truth,Corrected on 2026-04-25 from stale direct-donor posture to dossier-backed restrictive clean-room strategic donor status.,selected_not_live_clean_room_candidate,phase0r_clean_room_eval_then_model_a_model_b,"Phase 1R closed. Retain as a Phase 5R clean-room-only timer, trainer, stats, and smart-cube product-pattern candidate; implement only from the scrubbed Model A dossier." 11869,cutelyaware/magiccube4d,https://github.com/cutelyaware/magiccube4d/tree/master,HyperTwist,11.0,122.0,137.0,A,hypercubing / nD engine,subsystem donor,simulation donor,locked strategic donor,repurpose,moderate modification,"Retain the valuable internal engine, but expect to replace UI/product shell, adapt schemas/APIs, and refactor boundaries so it can plug into the target anchors cleanly. For this repo class, that usually means preserving generalized puzzle/state/render logic while building a new application shell around it.",Automatically exported from code.google.com/p/magiccube4d,"Integrate as a hypercubing / nD simulation subsystem for HyperTwist. Preserve the strongest existing pieces — nD state model, move notation, renderer, projection controls, solver/traversal logic, puzzle serialization, replay — and expose them behind a portfolio-stable interface. Wire first into HactarCE/Hyperspeedcube, then into cubing/cubing.js for orchestration, visualization, or data exchange.","Consolidate under the Hyperspeedcube + cubing.js + qbr nucleus, not beside it as a separate silo. Normalize data contracts, auth/permissions, storage, and telemetry; then attach as a service, plugin, canvas layer, trainer, or analysis module. Descending combination order: HactarCE/Hyperspeedcube, cubing/cubing.js, tao-yu/Alg-Trainer.",Repurpose here means: turn it into a higher-dimensional renderer/simulator donor and shared interaction grammar for HyperTwist and long-horizon VectorShell.,Map module boundaries; Identify hidden reusable internals; Define adapter/API boundary to target anchors; Write extraction tests against upstream behavior; Isolate puzzle/state core; Extract render/input abstractions; Document notation and save format,deep source audit,"Hidden value is likely in generalized puzzle/state representations, higher-dimensional transforms, notation systems, save formats, puzzle generators, and rendering abstractions.",Inspect generalized puzzle/state model; notation parser; transform math; rendering abstraction; save/load format; puzzle generator; input mapping; performance optimizations.,"Inspect package manifests, README/docs, src tree, examples, tests, CI workflows, config files, migrations/schemas, and hidden feature flags or experimental modules. Look for higher-dimensional state/notation representations, projection math, renderer abstractions, puzzle serialization, controls, and replay/training hooks.","Audit cutelyaware/magiccube4d as a hypercubing / nD engine candidate for HyperTwist. Do not stop at README-level features. Inspect: Inspect generalized puzzle/state model; notation parser; transform math; rendering abstraction; save/load format; puzzle generator; input mapping; performance optimizations. Decide whether the best extraction path is moderate modification and whether it belongs as subsystem donor / simulation donor. Test the three merger paths in order: 1) HactarCE/Hyperspeedcube [foundation + donor]; 2) cubing/cubing.js [3D engine + notation/state donor]; 3) tao-yu/Alg-Trainer [training UX donor]. Return hidden modules, reusable schemas, protocol layers, plugin hooks, render/state models, datasets/test fixtures, and any subsystem stronger than the visible product shell.",HactarCE/Hyperspeedcube,foundation + donor,"Use this repo against the partner as an augmenting layer; preserve the partner as the likely base and mine this repo for capabilities that improve breadth, UX, or specialization.",cubing/cubing.js,3D engine + notation/state donor,Use the partner for canonical state or rendering abstractions and merge this repo's specialized logic on top.,tao-yu/Alg-Trainer,training UX donor,Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.,VectorShell | ScriptoriumAI,VectorShell can borrow spatial/rendering and perception primitives; ScriptoriumAI can borrow tutorial/educational visualization patterns rather than the full engine.,exclude from standalone? no,"Not necessarily the final base, but keep as an active subsystem candidate or major donor.",medium,single-source signal; clear taxonomy; active integration value,medium,explicit bookmark description available,"Licensing intentionally ignored as a decision filter in this canonical evaluation; assess only architecture, capability, donor value, and concept transfer.",HyperTwist(1),HyperTwist Consider,Automatically exported from code.google.com/p/magiccube4d,,"cutelyaware/magiccube4d is treated as repurpose for HyperTwist because the current dossier keeps it as one of the most important legacy 4D interaction donors, with operationally usable custom licensing but explicit attribution and provenance obligations.",bookmarks,True,False,1.0,0.0,HT_hyper_engine,HT_hyper_engine_0003,hypercubing / nD simulation,"Integrate primarily for HyperTwist. Its description and bookmark placement under ""HyperTwist Consider"" place it in the cubing / algorithm training layer.",HyperTwist,cubing / algorithm training,integrate,moderate modification,medium,cutelyaware/magiccube4d,HyperTwist,,,,,,,,,,,,,,,,Original global operational v3 retained,Custom broad-use license with attribution requested,known_from_reference_material,uploaded_reference_docs,no,,,,Supplemental intake references are advisory only; v6 adjudication remains the source of truth.,Usually indirect,yes,v6 unified all-project source-of-truth pack,v5_carry_forward,,11.0,5,122.0,Locked Strategic Donor,"Top-tier 4D interaction, history, and macro donor with attribution obligations",,P1,mixed_or_boundary_sensitive_known,direct_incorporation_ok,"The repo is operationally usable because the custom license explicitly allows use, modification, and redistribution, but attribution and provenance obligations must be preserved and tracked.",Direct donor use is acceptable with explicit attribution and provenance tracking; keep the MyMath.java provenance note visible in license tracking.,"Preserve the custom license text, requested attribution, and the provenance note for utility code with referenced GPL lineage.",Usually unnecessary unless later isolating a narrow seam is cleaner than carrying the legacy code directly.,medium,custom-license-attribution-review,yes,,,,,,,,,,,,,v6.3_final_source_of_truth,Corrected on 2026-04-25 from stale unknown-license merge-bench posture to dossier-backed usable custom-license donor status.,selected_not_live_boundary_sensitive,phase0r_boundary_sensitive_eval_then_adapter_or_sidecar,Phase 1R closed. Retain as a Phase 4R attributed donor beneath the Hyperspeedcube anchor; preserve attribution and provenance explicitly. -11873,roice3/Magic120Cell,https://github.com/roice3/Magic120Cell,HyperTwist,12.0,122.0,137.0,A,hypercubing / nD engine,subsystem donor,simulation donor,locked strategic donor,repurpose,moderate modification,"Retain the valuable internal engine, but expect to replace UI/product shell, adapt schemas/APIs, and refactor boundaries so it can plug into the target anchors cleanly. For this repo class, that usually means preserving generalized puzzle/state/render logic while building a new application shell around it.",4D Megaminx Analogue,"Integrate as a hypercubing / nD simulation subsystem for HyperTwist. Preserve the strongest existing pieces — nD state model, move notation, renderer, projection controls, solver/traversal logic, puzzle serialization, replay — and expose them behind a portfolio-stable interface. Wire first into HactarCE/Hyperspeedcube, then into cubing/cubing.js for orchestration, visualization, or data exchange.","Consolidate under the Hyperspeedcube + cubing.js + qbr nucleus, not beside it as a separate silo. Normalize data contracts, auth/permissions, storage, and telemetry; then attach as a service, plugin, canvas layer, trainer, or analysis module. Descending combination order: HactarCE/Hyperspeedcube, cubing/cubing.js, tao-yu/Alg-Trainer.",Repurpose here means: turn it into a higher-dimensional renderer/simulator donor and shared interaction grammar for HyperTwist and long-horizon VectorShell.,Map module boundaries; Identify hidden reusable internals; Define adapter/API boundary to target anchors; Write extraction tests against upstream behavior; Isolate puzzle/state core; Extract render/input abstractions; Document notation and save format,deep source audit,"Hidden value is likely in generalized puzzle/state representations, higher-dimensional transforms, notation systems, save formats, puzzle generators, and rendering abstractions.",Inspect generalized puzzle/state model; notation parser; transform math; rendering abstraction; save/load format; puzzle generator; input mapping; performance optimizations.,"Inspect package manifests, README/docs, src tree, examples, tests, CI workflows, config files, migrations/schemas, and hidden feature flags or experimental modules. Look for higher-dimensional state/notation representations, projection math, renderer abstractions, puzzle serialization, controls, and replay/training hooks.","Audit roice3/Magic120Cell as a hypercubing / nD engine candidate for HyperTwist. Do not stop at README-level features. Inspect: Inspect generalized puzzle/state model; notation parser; transform math; rendering abstraction; save/load format; puzzle generator; input mapping; performance optimizations. Decide whether the best extraction path is moderate modification and whether it belongs as subsystem donor / simulation donor. Test the three merger paths in order: 1) HactarCE/Hyperspeedcube [foundation + donor]; 2) cubing/cubing.js [3D engine + notation/state donor]; 3) tao-yu/Alg-Trainer [training UX donor]. Return hidden modules, reusable schemas, protocol layers, plugin hooks, render/state models, datasets/test fixtures, and any subsystem stronger than the visible product shell.",HactarCE/Hyperspeedcube,foundation + donor,"Use this repo against the partner as an augmenting layer; preserve the partner as the likely base and mine this repo for capabilities that improve breadth, UX, or specialization.",cubing/cubing.js,3D engine + notation/state donor,Use the partner for canonical state or rendering abstractions and merge this repo's specialized logic on top.,tao-yu/Alg-Trainer,training UX donor,Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.,VectorShell | ScriptoriumAI,VectorShell can borrow spatial/rendering and perception primitives; ScriptoriumAI can borrow tutorial/educational visualization patterns rather than the full engine.,exclude from standalone? no,"Not necessarily the final base, but keep as an active subsystem candidate or major donor.",medium,single-source signal; clear taxonomy; active integration value,medium,explicit bookmark description available,"Licensing intentionally ignored as a decision filter in this canonical evaluation; assess only architecture, capability, donor value, and concept transfer.",HyperTwist(1),HyperTwist Consider,4D Megaminx Analogue,,"roice3/Magic120Cell is treated as repurpose for HyperTwist because the current dossier keeps it as a specialized 4D interaction and puzzle-UX donor with real save/load, visibility, filtering, and navigation value rather than as a foundation shell.",bookmarks,True,False,1.0,0.0,HT_hyper_engine,HT_hyper_engine_0004,hypercubing / nD simulation,"Integrate primarily for HyperTwist. Its description and bookmark placement under ""HyperTwist Consider"" place it in the hypercubing / nD simulation layer.",HyperTwist,hypercubing / nD simulation,integrate,heavy modification,medium,roice3/magic120cell,HyperTwist,,,,,,,,,,,,,,,,Original global operational v3 retained,MIT,known_from_reference_material,uploaded_reference_docs,no,,,,Supplemental intake references are advisory only; v6 adjudication remains the source of truth.,Usually indirect,yes,v6 unified all-project source-of-truth pack,v5_carry_forward,,12.0,5,122.0,Locked Strategic Donor,Specialized 4D interaction and puzzle-UX donor,,P1,permissive_or_noncopyleft_known,direct_incorporation_ok,The repo is MIT and should remain a specialized 4D interaction donor. Direct donor use is legally straightforward if HyperTwist wants to preserve its dedicated UX and puzzle-handling surfaces.,Direct donor use or bounded extraction are both acceptable; choose the seam that best preserves specialized 4D interaction behavior.,Preserve MIT notices and attribution where required.,Usually unnecessary unless later replacing a narrow seam is cleaner than carrying the upstream code.,high,permissive-specialized-donor,yes,,,,,,,,,,,,,v6.3_final_source_of_truth,Corrected on 2026-04-25 from stale unknown-license merge-bench posture to dossier-backed MIT specialized donor status.,selected_not_live_permissive_candidate,phase0r_permissive_eval_then_implement,"Phase 1R closed. Retain as a Phase 3R permissive implementation candidate; implement only from its packet authority and the retained-set contract, not by reopening Phase 0R." -11877,roice3/MagicCube5D,https://github.com/roice3/MagicCube5D,HyperTwist,13.0,122.0,137.0,A,hypercubing / nD engine,subsystem donor,simulation donor,locked strategic donor,repurpose,moderate modification,"Retain the valuable internal engine, but expect to replace UI/product shell, adapt schemas/APIs, and refactor boundaries so it can plug into the target anchors cleanly. For this repo class, that usually means preserving generalized puzzle/state/render logic while building a new application shell around it.",5D Rubik's Cube Analogue,"Integrate as a hypercubing / nD simulation subsystem for HyperTwist. Preserve the strongest existing pieces — nD state model, move notation, renderer, projection controls, solver/traversal logic, puzzle serialization, replay — and expose them behind a portfolio-stable interface. Wire first into HactarCE/Hyperspeedcube, then into cubing/cubing.js for orchestration, visualization, or data exchange.","Consolidate under the Hyperspeedcube + cubing.js + qbr nucleus, not beside it as a separate silo. Normalize data contracts, auth/permissions, storage, and telemetry; then attach as a service, plugin, canvas layer, trainer, or analysis module. Descending combination order: HactarCE/Hyperspeedcube, cubing/cubing.js, tao-yu/Alg-Trainer.",Repurpose here means: turn it into a higher-dimensional renderer/simulator donor and shared interaction grammar for HyperTwist and long-horizon VectorShell.,Map module boundaries; Identify hidden reusable internals; Define adapter/API boundary to target anchors; Write extraction tests against upstream behavior; Isolate puzzle/state core; Extract render/input abstractions; Document notation and save format,deep source audit,"Hidden value is likely in generalized puzzle/state representations, higher-dimensional transforms, notation systems, save formats, puzzle generators, and rendering abstractions.",Inspect generalized puzzle/state model; notation parser; transform math; rendering abstraction; save/load format; puzzle generator; input mapping; performance optimizations.,"Inspect package manifests, README/docs, src tree, examples, tests, CI workflows, config files, migrations/schemas, and hidden feature flags or experimental modules. Look for higher-dimensional state/notation representations, projection math, renderer abstractions, puzzle serialization, controls, and replay/training hooks.","Audit roice3/MagicCube5D as a hypercubing / nD engine candidate for HyperTwist. Do not stop at README-level features. Inspect: Inspect generalized puzzle/state model; notation parser; transform math; rendering abstraction; save/load format; puzzle generator; input mapping; performance optimizations. Decide whether the best extraction path is moderate modification and whether it belongs as subsystem donor / simulation donor. Test the three merger paths in order: 1) HactarCE/Hyperspeedcube [foundation + donor]; 2) cubing/cubing.js [3D engine + notation/state donor]; 3) tao-yu/Alg-Trainer [training UX donor]. Return hidden modules, reusable schemas, protocol layers, plugin hooks, render/state models, datasets/test fixtures, and any subsystem stronger than the visible product shell.",HactarCE/Hyperspeedcube,foundation + donor,"Use this repo against the partner as an augmenting layer; preserve the partner as the likely base and mine this repo for capabilities that improve breadth, UX, or specialization.",cubing/cubing.js,3D engine + notation/state donor,Use the partner for canonical state or rendering abstractions and merge this repo's specialized logic on top.,tao-yu/Alg-Trainer,training UX donor,Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.,VectorShell | ScriptoriumAI,VectorShell can borrow spatial/rendering and perception primitives; ScriptoriumAI can borrow tutorial/educational visualization patterns rather than the full engine.,exclude from standalone? no,"Not necessarily the final base, but keep as an active subsystem candidate or major donor.",medium,single-source signal; clear taxonomy; active integration value,medium,explicit bookmark description available,"Licensing intentionally ignored as a decision filter in this canonical evaluation; assess only architecture, capability, donor value, and concept transfer.",HyperTwist(1),HyperTwist Consider,5D Rubik's Cube Analogue,,"roice3/MagicCube5D is treated as repurpose for HyperTwist because the current dossier keeps it as a specialized 5D interaction, macro, progress, and slice donor rather than as a foundation shell.",bookmarks,True,False,1.0,0.0,HT_hyper_engine,HT_hyper_engine_0005,hypercubing / nD simulation,"Integrate primarily for HyperTwist. Its description and bookmark placement under ""HyperTwist Consider"" place it in the cubing / algorithm training layer.",HyperTwist,cubing / algorithm training,integrate,moderate modification,medium,roice3/magiccube5d,HyperTwist,,,,,,,,,,,,,,,,Original global operational v3 retained,MIT,known_from_reference_material,uploaded_reference_docs,no,,,,Supplemental intake references are advisory only; v6 adjudication remains the source of truth.,Usually indirect,yes,v6 unified all-project source-of-truth pack,v5_carry_forward,,13.0,5,122.0,Locked Strategic Donor,"Specialized 5D cube interaction, progress, and macro donor",,P1,permissive_or_noncopyleft_known,direct_incorporation_ok,The repo is MIT and should remain a specialized 5D interaction donor. Direct donor use is legally straightforward if HyperTwist wants to preserve its advanced cube-specific UX and macro behavior.,Direct donor use or bounded extraction are both acceptable; choose the seam that best preserves specialized 5D interaction and macro behavior.,Preserve MIT notices and attribution where required.,Usually unnecessary unless later replacing a narrow seam is cleaner than carrying the upstream code.,high,permissive-specialized-donor,yes,,,,,,,,,,,,,v6.3_final_source_of_truth,Corrected on 2026-04-25 from stale unknown-license merge-bench posture to dossier-backed MIT specialized donor status.,selected_not_live_permissive_candidate,phase0r_permissive_eval_then_implement,"Phase 1R closed. Retain as a Phase 3R permissive implementation candidate; implement only from its packet authority and the retained-set contract, not by reopening Phase 0R." +11873,roice3/Magic120Cell,https://github.com/roice3/Magic120Cell,HyperTwist,12.0,122.0,137.0,A,hypercubing / nD engine,subsystem donor,simulation donor,locked strategic donor,repurpose,moderate modification,"Retain the valuable internal engine, but expect to replace UI/product shell, adapt schemas/APIs, and refactor boundaries so it can plug into the target anchors cleanly. For this repo class, that usually means preserving generalized puzzle/state/render logic while building a new application shell around it.",4D Megaminx Analogue,"Integrate as a hypercubing / nD simulation subsystem for HyperTwist. Preserve the strongest existing pieces — nD state model, move notation, renderer, projection controls, solver/traversal logic, puzzle serialization, replay — and expose them behind a portfolio-stable interface. Wire first into HactarCE/Hyperspeedcube, then into cubing/cubing.js for orchestration, visualization, or data exchange.","Consolidate under the Hyperspeedcube + cubing.js + qbr nucleus, not beside it as a separate silo. Normalize data contracts, auth/permissions, storage, and telemetry; then attach as a service, plugin, canvas layer, trainer, or analysis module. Descending combination order: HactarCE/Hyperspeedcube, cubing/cubing.js, tao-yu/Alg-Trainer.",Repurpose here means: turn it into a higher-dimensional renderer/simulator donor and shared interaction grammar for HyperTwist and long-horizon VectorShell.,Map module boundaries; Identify hidden reusable internals; Define adapter/API boundary to target anchors; Write extraction tests against upstream behavior; Isolate puzzle/state core; Extract render/input abstractions; Document notation and save format,deep source audit,"Hidden value is likely in generalized puzzle/state representations, higher-dimensional transforms, notation systems, save formats, puzzle generators, and rendering abstractions.",Inspect generalized puzzle/state model; notation parser; transform math; rendering abstraction; save/load format; puzzle generator; input mapping; performance optimizations.,"Inspect package manifests, README/docs, src tree, examples, tests, CI workflows, config files, migrations/schemas, and hidden feature flags or experimental modules. Look for higher-dimensional state/notation representations, projection math, renderer abstractions, puzzle serialization, controls, and replay/training hooks.","Audit roice3/Magic120Cell as a hypercubing / nD engine candidate for HyperTwist. Do not stop at README-level features. Inspect: Inspect generalized puzzle/state model; notation parser; transform math; rendering abstraction; save/load format; puzzle generator; input mapping; performance optimizations. Decide whether the best extraction path is moderate modification and whether it belongs as subsystem donor / simulation donor. Test the three merger paths in order: 1) HactarCE/Hyperspeedcube [foundation + donor]; 2) cubing/cubing.js [3D engine + notation/state donor]; 3) tao-yu/Alg-Trainer [training UX donor]. Return hidden modules, reusable schemas, protocol layers, plugin hooks, render/state models, datasets/test fixtures, and any subsystem stronger than the visible product shell.",HactarCE/Hyperspeedcube,foundation + donor,"Use this repo against the partner as an augmenting layer; preserve the partner as the likely base and mine this repo for capabilities that improve breadth, UX, or specialization.",cubing/cubing.js,3D engine + notation/state donor,Use the partner for canonical state or rendering abstractions and merge this repo's specialized logic on top.,tao-yu/Alg-Trainer,training UX donor,Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.,VectorShell | ScriptoriumAI,VectorShell can borrow spatial/rendering and perception primitives; ScriptoriumAI can borrow tutorial/educational visualization patterns rather than the full engine.,exclude from standalone? no,"Not necessarily the final base, but keep as an active subsystem candidate or major donor.",medium,single-source signal; clear taxonomy; active integration value,medium,explicit bookmark description available,"Licensing intentionally ignored as a decision filter in this canonical evaluation; assess only architecture, capability, donor value, and concept transfer.",HyperTwist(1),HyperTwist Consider,4D Megaminx Analogue,,"roice3/Magic120Cell is treated as repurpose for HyperTwist because the current dossier keeps it as a specialized 4D interaction and puzzle-UX donor with real save/load, visibility, filtering, and navigation value rather than as a foundation shell.",bookmarks,True,False,1.0,0.0,HT_hyper_engine,HT_hyper_engine_0004,hypercubing / nD simulation,"Integrate primarily for HyperTwist. Its description and bookmark placement under ""HyperTwist Consider"" place it in the hypercubing / nD simulation layer.",HyperTwist,hypercubing / nD simulation,integrate,heavy modification,medium,roice3/magic120cell,HyperTwist,,,,,,,,,,,,,,,,Original global operational v3 retained,MIT,known_from_reference_material,uploaded_reference_docs,no,,,,Supplemental intake references are advisory only; v6 adjudication remains the source of truth.,Usually indirect,yes,v6 unified all-project source-of-truth pack,v5_carry_forward,,12.0,5,122.0,Locked Strategic Donor,Specialized 4D interaction and puzzle-UX donor,,P1,permissive_or_noncopyleft_known,direct_incorporation_ok,The repo is MIT and should remain a specialized 4D interaction donor. Direct donor use is legally straightforward if HyperTwist wants to preserve its dedicated UX and puzzle-handling surfaces.,Direct donor use or bounded extraction are both acceptable; choose the seam that best preserves specialized 4D interaction behavior.,Preserve MIT notices and attribution where required.,Usually unnecessary unless later replacing a narrow seam is cleaner than carrying the upstream code.,high,permissive-specialized-donor,yes,,,,,,,,,,,,,v6.3_final_source_of_truth,Corrected on 2026-04-25 from stale unknown-license merge-bench posture to dossier-backed MIT specialized donor status.,implemented_live_permissive,landed_permissive_preserve,"Phase 3R-E closed. Preserve as the landed first-party embodied companion, narration, lip-sync, gesture, subtitle, and avatar-embed lane; start future widening from the live-lane audit, then the 3R-E implementation packet, then REPO_LICENSE_TRACKING.md." +11877,roice3/MagicCube5D,https://github.com/roice3/MagicCube5D,HyperTwist,13.0,122.0,137.0,A,hypercubing / nD engine,subsystem donor,simulation donor,locked strategic donor,repurpose,moderate modification,"Retain the valuable internal engine, but expect to replace UI/product shell, adapt schemas/APIs, and refactor boundaries so it can plug into the target anchors cleanly. For this repo class, that usually means preserving generalized puzzle/state/render logic while building a new application shell around it.",5D Rubik's Cube Analogue,"Integrate as a hypercubing / nD simulation subsystem for HyperTwist. Preserve the strongest existing pieces — nD state model, move notation, renderer, projection controls, solver/traversal logic, puzzle serialization, replay — and expose them behind a portfolio-stable interface. Wire first into HactarCE/Hyperspeedcube, then into cubing/cubing.js for orchestration, visualization, or data exchange.","Consolidate under the Hyperspeedcube + cubing.js + qbr nucleus, not beside it as a separate silo. Normalize data contracts, auth/permissions, storage, and telemetry; then attach as a service, plugin, canvas layer, trainer, or analysis module. Descending combination order: HactarCE/Hyperspeedcube, cubing/cubing.js, tao-yu/Alg-Trainer.",Repurpose here means: turn it into a higher-dimensional renderer/simulator donor and shared interaction grammar for HyperTwist and long-horizon VectorShell.,Map module boundaries; Identify hidden reusable internals; Define adapter/API boundary to target anchors; Write extraction tests against upstream behavior; Isolate puzzle/state core; Extract render/input abstractions; Document notation and save format,deep source audit,"Hidden value is likely in generalized puzzle/state representations, higher-dimensional transforms, notation systems, save formats, puzzle generators, and rendering abstractions.",Inspect generalized puzzle/state model; notation parser; transform math; rendering abstraction; save/load format; puzzle generator; input mapping; performance optimizations.,"Inspect package manifests, README/docs, src tree, examples, tests, CI workflows, config files, migrations/schemas, and hidden feature flags or experimental modules. Look for higher-dimensional state/notation representations, projection math, renderer abstractions, puzzle serialization, controls, and replay/training hooks.","Audit roice3/MagicCube5D as a hypercubing / nD engine candidate for HyperTwist. Do not stop at README-level features. Inspect: Inspect generalized puzzle/state model; notation parser; transform math; rendering abstraction; save/load format; puzzle generator; input mapping; performance optimizations. Decide whether the best extraction path is moderate modification and whether it belongs as subsystem donor / simulation donor. Test the three merger paths in order: 1) HactarCE/Hyperspeedcube [foundation + donor]; 2) cubing/cubing.js [3D engine + notation/state donor]; 3) tao-yu/Alg-Trainer [training UX donor]. Return hidden modules, reusable schemas, protocol layers, plugin hooks, render/state models, datasets/test fixtures, and any subsystem stronger than the visible product shell.",HactarCE/Hyperspeedcube,foundation + donor,"Use this repo against the partner as an augmenting layer; preserve the partner as the likely base and mine this repo for capabilities that improve breadth, UX, or specialization.",cubing/cubing.js,3D engine + notation/state donor,Use the partner for canonical state or rendering abstractions and merge this repo's specialized logic on top.,tao-yu/Alg-Trainer,training UX donor,Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.,VectorShell | ScriptoriumAI,VectorShell can borrow spatial/rendering and perception primitives; ScriptoriumAI can borrow tutorial/educational visualization patterns rather than the full engine.,exclude from standalone? no,"Not necessarily the final base, but keep as an active subsystem candidate or major donor.",medium,single-source signal; clear taxonomy; active integration value,medium,explicit bookmark description available,"Licensing intentionally ignored as a decision filter in this canonical evaluation; assess only architecture, capability, donor value, and concept transfer.",HyperTwist(1),HyperTwist Consider,5D Rubik's Cube Analogue,,"roice3/MagicCube5D is treated as repurpose for HyperTwist because the current dossier keeps it as a specialized 5D interaction, macro, progress, and slice donor rather than as a foundation shell.",bookmarks,True,False,1.0,0.0,HT_hyper_engine,HT_hyper_engine_0005,hypercubing / nD simulation,"Integrate primarily for HyperTwist. Its description and bookmark placement under ""HyperTwist Consider"" place it in the cubing / algorithm training layer.",HyperTwist,cubing / algorithm training,integrate,moderate modification,medium,roice3/magiccube5d,HyperTwist,,,,,,,,,,,,,,,,Original global operational v3 retained,MIT,known_from_reference_material,uploaded_reference_docs,no,,,,Supplemental intake references are advisory only; v6 adjudication remains the source of truth.,Usually indirect,yes,v6 unified all-project source-of-truth pack,v5_carry_forward,,13.0,5,122.0,Locked Strategic Donor,"Specialized 5D cube interaction, progress, and macro donor",,P1,permissive_or_noncopyleft_known,direct_incorporation_ok,The repo is MIT and should remain a specialized 5D interaction donor. Direct donor use is legally straightforward if HyperTwist wants to preserve its advanced cube-specific UX and macro behavior.,Direct donor use or bounded extraction are both acceptable; choose the seam that best preserves specialized 5D interaction and macro behavior.,Preserve MIT notices and attribution where required.,Usually unnecessary unless later replacing a narrow seam is cleaner than carrying the upstream code.,high,permissive-specialized-donor,yes,,,,,,,,,,,,,v6.3_final_source_of_truth,Corrected on 2026-04-25 from stale unknown-license merge-bench posture to dossier-backed MIT specialized donor status.,implemented_live_permissive,landed_permissive_preserve,"Phase 3R-E closed. Preserve as the landed first-party embodied companion, narration, lip-sync, gesture, subtitle, and avatar-embed lane; start future widening from the live-lane audit, then the 3R-E implementation packet, then REPO_LICENSE_TRACKING.md." 11881,cs0x7f/cstimer,https://github.com/cs0x7f/cstimer,HyperTwist,14.0,121.0,147.0,A,gold-standard timer benchmark,benchmark,Gold-standard timer benchmark,Reserve Bench,future candidate,architecture only,"Retain the valuable internal engine, but expect to replace UI/product shell, adapt schemas/APIs, and refactor boundaries so it can plug into the target anchors cleanly. For this repo class, that usually means preserving cube-state, scramble, scheduling, or timer internals while adapting pedagogy, analytics, and UI.","Benchmark-only retained value: mature timer-state handling, persistence, statistics, reconstruction tooling, scramble generation, and smart-device expectations. Study behavior and category expectations only.","Keep as a restrictive benchmark. Use it as the timer behavior reference point for HyperTwist, not as donor code.",Do not merge this repo into the HyperTwist core. Translate only high-level timer and stats expectations into first-party implementations.,"Repurpose here means: derive acceptance-test targets and product expectations for timer flow, persistence, statistics, and hardware support.",Map module boundaries; Identify hidden reusable internals; Define adapter/API boundary to target anchors; Write extraction tests against upstream behavior; Extract cube-state model; Normalize trainer/case schema; Expose analytics and replay hooks,behavior and acceptance-test benchmark review,"Hidden value sits in timer edge cases, persistence behavior, reconstruction/statistics expectations, and mature product-surface decisions.","Which timer behaviors, persistence expectations, and solve-analysis surfaces should become first-party acceptance criteria?","Inspect timer-state transitions, solve/session persistence, statistics/reconstruction surfaces, scramble integration, and smart-device behavior as benchmark material only.","Audit cs0x7f/cstimer only as a restrictive gold-standard timer benchmark for HyperTwist. Extract behavior expectations and acceptance criteria, not donor code.",tao-yu/Alg-Trainer,base + donor swarm,Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.,poliva/cubedex,specialized training UX donor,Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.,Lykos/cube_trainer,sampling/analytics donor,Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.,Reference only,"Retain only as benchmark, oracle, acceptance-test, or clean-room planning input.",exclude from donor lane,The repo is GPL timer/training software and should remain the behavior/category benchmark in the timer lane rather than a donor codebase.,high,"Dossier-backed classification is stable: the retained value is benchmark authority, not source incorporation.",high,"Dossier-backed classification is stable: the retained value is benchmark authority, not source incorporation.","Licensing intentionally ignored as a decision filter in this canonical evaluation; assess only architecture, capability, donor value, and concept transfer.",,,,cs0x7f/cstimer — GPL timer/training platform; keep only as the gold-standard timer benchmark.,"cs0x7f/cstimer remains valuable because it defines the product-behavior ceiling for timer flow, persistence, and statistics. That value is benchmark authority, not donor code.",memo,False,True,0.0,5.0,HT_timer_training,HT_timer_training_0001,Gold-standard timer benchmark,"Gold-standard timer benchmark for HyperTwist; retained for behavior calibration, not donor use.",HyperTwist,Gold-standard timer benchmark,future candidate,architecture only,medium,cs0x7f/cstimer,HyperTwist,,,,,,,,,,,,,,,,Original global operational v3 retained,GPL-3.0,known_from_reference_material,uploaded_reference_docs,no,,,,Supplemental intake references are advisory only; v6 adjudication remains the source of truth.,Usually indirect,yes,v6 unified all-project source-of-truth pack,v5_carry_forward,,14.0,5,121.0,Reserve Bench,Gold-standard timer benchmark,Included,P2,mixed_or_boundary_sensitive_known,pattern_only_preferred,"The repo is GPL-3.0 and remains the primary restrictive timer, stats, scramble, and smart-device benchmark. Use it for behavioral parity and acceptance criteria, not direct source incorporation.","Reference only: benchmark timer, statistics, scramble, and smart-device behavior without direct source incorporation.",Direct incorporation would require GPL-compatible distribution/compliance and is not the planned HyperTwist path.,Only if a narrow timer behavior later proves strategically necessary to recreate in first-party code; otherwise keep this as a benchmark.,high,gpl-timer-benchmark,no,,,,,,,,,,,,,v6.3_final_source_of_truth,Corrected on 2026-04-25 from stale donor posture to dossier-backed gold-standard timer benchmark status.,not_live_reference_or_discard_candidate,phase0r_reference_benchmark_or_discard_eval,Packet 0R-E closed. Retain as the primary restrictive timer/stats/scramble/smart-device benchmark and future clean-room timer-pattern oracle. 11889,aMonteSl/CodeXR,https://github.com/aMonteSl/CodeXR,HyperTwist,16.0,119.0,134.0,B,reference-only XR benchmark,benchmark,Reference-only XR benchmark,Reserve Bench,future candidate,architecture only,"Retain the valuable internal engine, but expect to replace UI/product shell, adapt schemas/APIs, and refactor boundaries so it can plug into the target anchors cleanly. For this repo class, that usually means preserving calibration/detection/state-reconstruction logic while replacing camera UX and integration surfaces.","Benchmark-only retained value: immersive interaction, collaboration-room, virtual-screen, and scene-launch patterns. Study behavior and workflow ideas only; do not plan direct product incorporation.",Keep in restrictive/reference custody. Use only as a benchmark for XR interaction ideas and immersive UI patterns; do not merge source into HyperTwist.,"Do not treat this repo as part of the HyperTwist merge nucleus. If useful, translate isolated interaction ideas into first-party designs without inheriting the code-analysis shell.",Repurpose here means: abstract useful XR interaction ideas into first-party browser/XR surfaces without reusing source.,Map module boundaries; Identify hidden reusable internals; Define adapter/API boundary to target anchors; Write extraction tests against upstream behavior; Benchmark calibration pipeline; Extract state reconstruction; Wrap with camera/AR adapter,behavior-level benchmark review,"Hidden value sits in collaboration-room flow, scene-launch orchestration, virtual-screen components, and immersive inspection patterns.",Which interaction patterns are reusable at the behavior level without inheriting the code-analysis product identity or GPL source?,"Inspect XR launch flow, collaboration-room server patterns, virtual-screen behavior, and immersive UI choreography as benchmark material only.","Audit aMonteSl/CodeXR only as a reference-only XR benchmark for HyperTwist. Do not recommend direct incorporation. Extract interaction patterns, collaboration metaphors, and virtual-screen ideas only.",kkoomen/qbr,foundation + perception donor,"Use this repo against the partner as an augmenting layer; preserve the partner as the likely base and mine this repo for capabilities that improve breadth, UX, or specialization.",vivaansinghvi07/rubix-cube-solver,perception + replay donor,Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.,cubing/cubing.js,state/render backend,Use the partner for canonical state or rendering abstractions and merge this repo's specialized logic on top.,Reference only,"Retain only as benchmark, oracle, acceptance-test, or clean-room planning input.",exclude from donor lane,The repo is a GPL-3.0-only VS Code XR analysis extension and materially off-mission for HyperTwist; retain only as a reference benchmark.,high,Source-backed dossier and license verification collapse the old donor thesis.,high,Source-backed dossier and license verification collapse the old donor thesis.,"Licensing intentionally ignored as a decision filter in this canonical evaluation; assess only architecture, capability, donor value, and concept transfer.",,,,aMonteSl/CodeXR — GPL-3.0-only VS Code XR analysis extension; keep only as a reference-only XR benchmark for interaction ideas.,"aMonteSl/CodeXR is retained only as a reference-only XR benchmark. It is a legitimate immersive code-analysis product, but the GPL-3.0-only license and domain mismatch rule out donor treatment for HyperTwist.",memo,False,True,0.0,3.0,HT_cube_vision,HT_cube_vision_0005,Reference-only XR benchmark,Reference-only XR benchmark for HyperTwist; not a donor lane.,HyperTwist,Reference-only XR benchmark,future candidate,architecture only,medium,amontesl/codexr,HyperTwist,,,,,,,,,,,,,,,,Original global operational v3 retained,GPL-3.0-only,known_from_reference_material,uploaded_reference_docs,no,,,,Supplemental intake references are advisory only; v6 adjudication remains the source of truth.,Potentially relevant,yes,v6 unified all-project source-of-truth pack,v5_carry_forward,,16.0,5,119.0,Reserve Bench,Reference-only XR benchmark,Included,P3,mixed_or_boundary_sensitive_known,pattern_only_preferred,The repo is GPL-3.0-only and was discarded from the active HyperTwist retained set because its strongest XR collaboration value is off-domain and already superseded by stronger retained rows.,Reference only: discarded historical comparison context for XR collaboration patterns; do not plan direct incorporation.,Direct incorporation would require GPL-compatible distribution/compliance and is not the planned HyperTwist path.,Only if a uniquely valuable interaction pattern later needs first-party recreation; otherwise keep this as a benchmark.,high,gpl-reference-only-benchmark,no,,,,,,,,,,,,,v6.3_final_source_of_truth,Corrected on 2026-04-25 from stale pre-dossier donor posture to dossier-backed GPL reference-only benchmark status.,not_live_reference_or_discard_candidate,phase0r_reference_benchmark_or_discard_eval,Packet 0R-E closed. Discard from the active retained set; its XR collaboration value is off-domain and already superseded by stronger retained rows. 11893,brianpeiris/RiftSketch,https://github.com/brianpeiris/RiftSketch,HyperTwist,17.0,119.0,134.0,B,vision / perception / AR,subsystem donor,vision donor,Reserve Bench,future candidate,architecture only,"Retain the valuable internal engine, but expect to replace UI/product shell, adapt schemas/APIs, and refactor boundaries so it can plug into the target anchors cleanly. For this repo class, that usually means preserving calibration/detection/state-reconstruction logic while replacing camera UX and integration surfaces.","brianpeiris/RiftSketch — https://github.com/brianpeiris/RiftSketch | brianpeiris/RiftSketch — MIT — WebVR live coding. | poliva/cubedex, tao-yu/Alg-Trainer, kkoomen/qbr, vivaansinghvi07/rubix-cube-solver, NuiLab/code-vr, molgenis/Graph2V...","Integrate as a cubing / algorithm training subsystem for HyperTwist. Preserve the strongest existing pieces — scramble generation, algorithm database, recognition/training loop, timing/statistics, virtual cube, smartcube hooks, spaced repetition — and expose them behind a portfolio-stable interface. Wire first into tao-yu/Alg-Trainer, then into poliva/cubedex for orchestration, visualization, or data exchange.","Consolidate under the Hyperspeedcube + cubing.js + qbr nucleus, not beside it as a separate silo. Normalize data contracts, auth/permissions, storage, and telemetry; then attach as a service, plugin, canvas layer, trainer, or analysis module. Descending combination order: tao-yu/Alg-Trainer, poliva/cubedex, Lykos/cube_trainer.","Repurpose here means: turn it into a trainer engine, solver/timer backend, recognition drill module, or method-specific practice mode for HyperTwist.",Map module boundaries; Identify hidden reusable internals; Define adapter/API boundary to target anchors; Write extraction tests against upstream behavior; Benchmark calibration pipeline; Extract state reconstruction; Wrap with camera/AR adapter,deep source audit,"Hidden value often sits in calibration, preprocessing, stabilization, object/state reconstruction, replay artifacts, and camera-to-domain state pipelines that are not obvious from demos.",Inspect preprocessing/calibration; tracking stabilization; state reconstruction; replay/event model; camera abstraction; fallback heuristics; testing assets/videos; performance shortcuts.,"Inspect package manifests, README/docs, src tree, examples, tests, CI workflows, config files, migrations/schemas, and hidden feature flags or experimental modules. Look for algorithm databases, spaced-repetition logic, scramble generation, timer/stat code, virtual cube components, smartcube adapters, and custom-trainer configuration support.","Audit brianpeiris/RiftSketch as a vision / perception / AR candidate for HyperTwist. Do not stop at README-level features. Inspect: Inspect preprocessing/calibration; tracking stabilization; state reconstruction; replay/event model; camera abstraction; fallback heuristics; testing assets/videos; performance shortcuts. Decide whether the best extraction path is moderate modification and whether it belongs as subsystem donor / vision donor. Test the three merger paths in order: 1) kkoomen/qbr [foundation + perception donor]; 2) vivaansinghvi07/rubix-cube-solver [perception + replay donor]; 3) cubing/cubing.js [state/render backend]. Return hidden modules, reusable schemas, protocol layers, plugin hooks, render/state models, datasets/test fixtures, and any subsystem stronger than the visible product shell.",kkoomen/qbr,foundation + perception donor,"Use this repo against the partner as an augmenting layer; preserve the partner as the likely base and mine this repo for capabilities that improve breadth, UX, or specialization.",vivaansinghvi07/rubix-cube-solver,perception + replay donor,Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.,cubing/cubing.js,state/render backend,Use the partner for canonical state or rendering abstractions and merge this repo's specialized logic on top.,VectorShell | ScriptoriumAI,VectorShell can borrow spatial/rendering and perception primitives; ScriptoriumAI can borrow tutorial/educational visualization patterns rather than the full engine.,exclude from standalone? no,"Not necessarily the final base, but keep as an active subsystem candidate or major donor.",medium,single-source signal; clear taxonomy; active integration value,medium,memo mentions: 3,"Licensing intentionally ignored as a decision filter in this canonical evaluation; assess only architecture, capability, donor value, and concept transfer.",,,,"brianpeiris/RiftSketch — https://github.com/brianpeiris/RiftSketch | brianpeiris/RiftSketch — MIT — WebVR live coding. | poliva/cubedex, tao-yu/Alg-Trainer, kkoomen/qbr, vivaansinghvi07/rubix-cube-solver, NuiLab/code-vr, molgenis/Graph2VR (core permissive parts), brianpeiris/RiftSketch, aMonteSl/CodeXR.","brianpeiris/RiftSketch is treated as a future candidate for HyperTwist because the current dossier retains it mainly for WebXR spatial-UI, world-space monitor, and immersive tooling patterns rather than as a cubing-specific core or active merge donor.",memo,False,True,0.0,3.0,HT_cube_vision,HT_cube_vision_0006,cubing / algorithm training,Integrate as a shared building block across at least two projects. Its memo and bookmark signals place it in the computer vision / AR layer.,multi-project,computer vision / AR,integrate,heavy modification,medium,brianpeiris/riftsketch,HyperTwist,,,,,,,,,,,,,,,,Original global operational v3 retained,MIT,known_from_reference_material,uploaded_reference_docs,no,,,,Supplemental intake references are advisory only; v6 adjudication remains the source of truth.,Potentially relevant,yes,v6 unified all-project source-of-truth pack,v5_carry_forward,,17.0,5,119.0,Reserve Bench,XR interaction and spatial-UI bench,,,permissive_or_noncopyleft_known,pattern_only_preferred,The repo is MIT but was discarded from the active retained set because its immersive live-coding shell is off topic to HyperTwist's retained product scope.,Reference only: discarded historical comparison context for immersive live-coding patterns; do not plan direct incorporation.,"Typically preserve notices, attribution, and license text where required; no special copyleft-driven disclosure posture is normally needed.",Usually unnecessary unless you later decide the existing implementation is too constraining architecturally.,high,strategic-or-implemented-component,yes,,,,,,,,,,,,,v6.3_final_source_of_truth,Normalized legacy merge-bench wording to dossier-backed below-core benchmark posture on 2026-04-25.,not_live_reference_or_discard_candidate,phase0r_reference_benchmark_or_discard_eval,Packet 0R-E closed. Discard from the active retained set; immersive live-coding is off topic to HyperTwist's retained product scope. 11897,abunickabhi/5style-Trainer,https://github.com/abunickabhi/5style-Trainer,HyperTwist,18.0,118.0,133.0,B,cubing trainer / solver / timing,subsystem donor,training donor,donor bench,repurpose,moderate modification,"Retain the valuable internal engine, but expect to replace UI/product shell, adapt schemas/APIs, and refactor boundaries so it can plug into the target anchors cleanly. For this repo class, that usually means preserving cube-state, scramble, scheduling, or timer internals while adapting pedagogy, analytics, and UI.",abunickabhi/5style-Trainer — MIT — 5-style BLD trainer (fork of Alg-Trainer). | abunickabhi/5style-Trainer — MIT (BLD extension).,"Integrate as a cubing / algorithm training subsystem for HyperTwist. Preserve the strongest existing pieces — scramble generation, algorithm database, recognition/training loop, timing/statistics, virtual cube, smartcube hooks, spaced repetition — and expose them behind a portfolio-stable interface. Wire first into tao-yu/Alg-Trainer, then into poliva/cubedex for orchestration, visualization, or data exchange.","Consolidate under the Hyperspeedcube + cubing.js + qbr nucleus, not beside it as a separate silo. Normalize data contracts, auth/permissions, storage, and telemetry; then attach as a service, plugin, canvas layer, trainer, or analysis module. Descending combination order: tao-yu/Alg-Trainer, poliva/cubedex, Lykos/cube_trainer.","Repurpose here means: turn it into a trainer engine, solver/timer backend, recognition drill module, or method-specific practice mode for HyperTwist.",Map module boundaries; Identify hidden reusable internals; Define adapter/API boundary to target anchors; Write extraction tests against upstream behavior; Extract cube-state model; Normalize trainer/case schema; Expose analytics and replay hooks,deep source audit,"Hidden value often sits in cube-state representation, scramble generation, weighted drill scheduling, recognition datasets, replay/timer internals, and case database schemas.",Inspect cube-state model; scramble generator; trainer weighting/scheduling; case database and metadata; replay/timer model; import/export of alg sets; smartcube or sensor adapters.,"Inspect package manifests, README/docs, src tree, examples, tests, CI workflows, config files, migrations/schemas, and hidden feature flags or experimental modules. Look for algorithm databases, spaced-repetition logic, scramble generation, timer/stat code, virtual cube components, smartcube adapters, and custom-trainer configuration support.","Audit abunickabhi/5style-Trainer as a cubing trainer / solver / timing candidate for HyperTwist. Do not stop at README-level features. Inspect: Inspect cube-state model; scramble generator; trainer weighting/scheduling; case database and metadata; replay/timer model; import/export of alg sets; smartcube or sensor adapters. Decide whether the best extraction path is moderate modification and whether it belongs as subsystem donor / training donor. Test the three merger paths in order: 1) tao-yu/Alg-Trainer [base + donor swarm]; 2) poliva/cubedex [specialized training UX donor]; 3) Lykos/cube_trainer [sampling/analytics donor]. Return hidden modules, reusable schemas, protocol layers, plugin hooks, render/state models, datasets/test fixtures, and any subsystem stronger than the visible product shell.",tao-yu/Alg-Trainer,base + donor swarm,Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.,poliva/cubedex,specialized training UX donor,Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.,Lykos/cube_trainer,sampling/analytics donor,Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.,project-local first,"Cross-project transfer is possible, but the value is clearest inside the assigned project until source audit exposes more reusable primitives.",exclude from standalone? no,"Not necessarily the final base, but keep as an active subsystem candidate or major donor.",medium,single-source signal; clear taxonomy; active integration value,medium,strong adjacency to identified core stack; memo mentions: 2,"Licensing intentionally ignored as a decision filter in this canonical evaluation; assess only architecture, capability, donor value, and concept transfer.",,,,abunickabhi/5style-Trainer — MIT — 5-style BLD trainer (fork of Alg-Trainer). | abunickabhi/5style-Trainer — MIT (BLD extension).,"abunickabhi/5style-Trainer is treated as repurpose for HyperTwist because the current dossier keeps it as a focused advanced-training donor for 5-style edge-cycle drilling, subset practice, Giiker-aware flow, and high-skill BLD-oriented practice patterns rather than as a separate platform lane.",memo,False,True,0.0,2.0,HT_training_stack,HT_training_stack_0006,cubing / algorithm training,Integrate primarily for HyperTwist. Its memo and bookmark signals place it in the cubing / algorithm training layer.,HyperTwist,cubing / algorithm training,integrate,direct,medium,abunickabhi/5style-trainer,HyperTwist,,,,,,,,,,,,,,,,Original global operational v3 retained,MIT,known_from_reference_material,uploaded_reference_docs,no,,,,Supplemental intake references are advisory only; v6 adjudication remains the source of truth.,Usually indirect,yes,v6 unified all-project source-of-truth pack,v5_carry_forward,,18.0,5,118.0,Donor Bench,Focused advanced-training donor,,,permissive_or_noncopyleft_known,direct_incorporation_ok,"This repo is aligned with a direct integration path for HyperTwist because it is either already implemented, strategically central, or donor-grade without a visible copyleft constraint in the current materials. Deep incorporation is sensible if the source audit confirms architectural cleanliness.","Direct embed, vendored module, package dependency, or tightly integrated adapter as the architecture requires.","Typically preserve notices, attribution, and license text where required; no special copyleft-driven disclosure posture is normally needed.",Usually unnecessary unless you later decide the existing implementation is too constraining architecturally.,high,strategic-or-implemented-component,yes,,,,,,,,,,,,,v6.3_final_source_of_truth,Normalized legacy merge-bench wording to dossier-backed focused advanced-training donor posture on 2026-04-25.,implemented_live_permissive,landed_permissive_preserve,Phase 1R closed. Preserve as a landed first-party permissive lane; keep notices and attribution visible and widen only through ordinary owned enhancement work. 11900,MathewKJ2048/Rubiks-cube-simulator,https://github.com/MathewKJ2048/Rubiks-cube-simulator,HyperTwist,19.0,118.0,133.0,B,clean-room simulator benchmark,benchmark,Clean-room simulator benchmark,Reserve Bench,future candidate,architecture only,"Retain the valuable internal engine, but expect to replace UI/product shell, adapt schemas/APIs, and refactor boundaries so it can plug into the target anchors cleanly. For this repo class, that usually means preserving cube-state, scramble, scheduling, or timer internals while adapting pedagogy, analytics, and UI.","Benchmark-only retained value: lightweight simulator flow, text-command grammar, move-history UX, and timed step-playback behavior suitable for first-party clean-room reimplementation.",Keep only as a clean-room benchmark. Use it to shape lightweight simulator behavior; do not incorporate source.,Do not treat this repo as a merge candidate. Convert useful simulator behaviors into a scrubbed Model A spec only.,Repurpose here means: derive first-party lightweight simulator behavior through a clean-room process.,Map module boundaries; Identify hidden reusable internals; Define adapter/API boundary to target anchors; Write extraction tests against upstream behavior; Extract cube-state model; Normalize trainer/case schema; Expose analytics and replay hooks,clean-room benchmark review,"Hidden value sits in text-command grammar, move-history logging, and timed step playback.",Which lightweight simulator behaviors are worth preserving through a scrubbed Model A handoff?,"Inspect command grammar, move-history handling, beginner-solver flow, and timed step playback as clean-room benchmark material only.",Audit MathewKJ2048/Rubiks-cube-simulator only as a clean-room simulator benchmark. Extract behaviors into a scrubbed spec; do not recommend direct source incorporation.,tao-yu/Alg-Trainer,base + donor swarm,Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.,poliva/cubedex,specialized training UX donor,Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.,Lykos/cube_trainer,sampling/analytics donor,Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.,Reference only,"Retain only as benchmark, oracle, acceptance-test, or clean-room planning input.",exclude from donor lane,The repo is GPL simulator code and should remain only as a low-priority clean-room simulator benchmark.,high,The dossier-backed classification is stable: retain only the lightweight simulator behaviors through a clean-room path.,high,The dossier-backed classification is stable: retain only the lightweight simulator behaviors through a clean-room path.,"Licensing intentionally ignored as a decision filter in this canonical evaluation; assess only architecture, capability, donor value, and concept transfer.",,,,MathewKJ2048/Rubiks-cube-simulator — GPL-3.0 simulator; keep only as a clean-room simulator benchmark.,"MathewKJ2048/Rubiks-cube-simulator is retained only as a clean-room simulator benchmark. Its value is in small simulator behaviors, not donor code.",memo,False,True,0.0,2.0,HT_training_clean_room,HT_training_clean_room_0004,Clean-room simulator benchmark,Clean-room simulator benchmark for HyperTwist; retained for behavior extraction only.,HyperTwist,Clean-room simulator benchmark,future candidate,architecture only,medium,mathewkj2048/rubiks-cube-simulator,HyperTwist,,,,,,,,,,,,,,,,Original global operational v3 retained,GPL-3.0,known_from_reference_material,uploaded_reference_docs,no,,,,Supplemental intake references are advisory only; v6 adjudication remains the source of truth.,Usually indirect,yes,v6 unified all-project source-of-truth pack,v5_carry_forward,,19.0,5,118.0,Reserve Bench,Clean-room simulator benchmark,Included,P3,mixed_or_boundary_sensitive_known,pattern_only_preferred,"The repo is GPL simulator code and was discarded from the active retained set as an inferior duplicate of stronger pedagogy, planner, and history benchmarks.",Reference only: discarded historical comparison context for simulator pedagogy and history flow; do not plan direct incorporation.,Direct incorporation would require GPL-compatible distribution/compliance and is not the planned HyperTwist path.,Yes — this is the preferred path if lightweight simulator behavior later proves strategically necessary.,high,gpl-clean-room-benchmark,no,,,,,,,,,,,,,v6.3_final_source_of_truth,Corrected on 2026-04-25 from stale donor posture to dossier-backed clean-room simulator benchmark status.,not_live_reference_or_discard_candidate,phase0r_reference_benchmark_or_discard_eval,"Packet 0R-E closed. Discard from the active retained set as an inferior duplicate of stronger pedagogy, planner, and history benchmarks." -11903,NuiLab/code-vr,https://github.com/NuiLab/code-vr,HyperTwist,20.0,118.0,133.0,B,vision / perception / AR,subsystem donor,vision donor,donor bench,repurpose,moderate modification,"Retain the valuable internal engine, but expect to replace UI/product shell, adapt schemas/APIs, and refactor boundaries so it can plug into the target anchors cleanly. For this repo class, that usually means preserving calibration/detection/state-reconstruction logic while replacing camera UX and integration surfaces.","NuiLab/code-vr — (license permissive per repo) — VR codebase explorer. | poliva/cubedex, tao-yu/Alg-Trainer, kkoomen/qbr, vivaansinghvi07/rubix-cube-solver, NuiLab/code-vr, molgenis/Graph2VR (core permissive parts), brianpeiris/RiftSketc...","Integrate as a cubing / algorithm training subsystem for HyperTwist. Preserve the strongest existing pieces — scramble generation, algorithm database, recognition/training loop, timing/statistics, virtual cube, smartcube hooks, spaced repetition — and expose them behind a portfolio-stable interface. Wire first into tao-yu/Alg-Trainer, then into poliva/cubedex for orchestration, visualization, or data exchange.","Consolidate under the Hyperspeedcube + cubing.js + qbr nucleus, not beside it as a separate silo. Normalize data contracts, auth/permissions, storage, and telemetry; then attach as a service, plugin, canvas layer, trainer, or analysis module. Descending combination order: tao-yu/Alg-Trainer, poliva/cubedex, Lykos/cube_trainer.","Repurpose here means: turn it into a trainer engine, solver/timer backend, recognition drill module, or method-specific practice mode for HyperTwist.",Map module boundaries; Identify hidden reusable internals; Define adapter/API boundary to target anchors; Write extraction tests against upstream behavior; Benchmark calibration pipeline; Extract state reconstruction; Wrap with camera/AR adapter,deep source audit,"Hidden value often sits in calibration, preprocessing, stabilization, object/state reconstruction, replay artifacts, and camera-to-domain state pipelines that are not obvious from demos.",Inspect preprocessing/calibration; tracking stabilization; state reconstruction; replay/event model; camera abstraction; fallback heuristics; testing assets/videos; performance shortcuts.,"Inspect package manifests, README/docs, src tree, examples, tests, CI workflows, config files, migrations/schemas, and hidden feature flags or experimental modules. Look for algorithm databases, spaced-repetition logic, scramble generation, timer/stat code, virtual cube components, smartcube adapters, and custom-trainer configuration support.","Audit NuiLab/code-vr as a vision / perception / AR candidate for HyperTwist. Do not stop at README-level features. Inspect: Inspect preprocessing/calibration; tracking stabilization; state reconstruction; replay/event model; camera abstraction; fallback heuristics; testing assets/videos; performance shortcuts. Decide whether the best extraction path is moderate modification and whether it belongs as subsystem donor / vision donor. Test the three merger paths in order: 1) kkoomen/qbr [foundation + perception donor]; 2) vivaansinghvi07/rubix-cube-solver [perception + replay donor]; 3) cubing/cubing.js [state/render backend]. Return hidden modules, reusable schemas, protocol layers, plugin hooks, render/state models, datasets/test fixtures, and any subsystem stronger than the visible product shell.",kkoomen/qbr,foundation + perception donor,"Use this repo against the partner as an augmenting layer; preserve the partner as the likely base and mine this repo for capabilities that improve breadth, UX, or specialization.",vivaansinghvi07/rubix-cube-solver,perception + replay donor,Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.,cubing/cubing.js,state/render backend,Use the partner for canonical state or rendering abstractions and merge this repo's specialized logic on top.,VectorShell | ScriptoriumAI,VectorShell can borrow spatial/rendering and perception primitives; ScriptoriumAI can borrow tutorial/educational visualization patterns rather than the full engine.,exclude from standalone? no,"Not necessarily the final base, but keep as an active subsystem candidate or major donor.",medium,single-source signal; clear taxonomy; active integration value,medium,memo mentions: 2,"Licensing intentionally ignored as a decision filter in this canonical evaluation; assess only architecture, capability, donor value, and concept transfer.",,,,"NuiLab/code-vr — (license permissive per repo) — VR codebase explorer. | poliva/cubedex, tao-yu/Alg-Trainer, kkoomen/qbr, vivaansinghvi07/rubix-cube-solver, NuiLab/code-vr, molgenis/Graph2VR (core permissive parts), brianpeiris/RiftSketch, aMonteSl/CodeXR.",NuiLab/code-vr is treated as repurpose for HyperTwist because the current dossier keeps it below core tier as an XR pedagogy and code-to-scene representation donor rather than as an active merge-set candidate or product shell.,memo,False,True,0.0,2.0,HT_cube_vision,HT_cube_vision_0007,cubing / algorithm training,Integrate as a shared building block across at least two projects. Its memo and bookmark signals place it in the computer vision / AR layer.,multi-project,computer vision / AR,integrate,heavy modification,medium,nuilab/code-vr,HyperTwist,,,,,,,,,,,,,,,,Original global operational v3 retained,MIT,known_from_reference_material,uploaded_reference_docs,no,,,,Supplemental intake references are advisory only; v6 adjudication remains the source of truth.,Potentially relevant,yes,v6 unified all-project source-of-truth pack,v5_carry_forward,,20.0,5,118.0,Donor Bench,XR pedagogy and code-to-scene representation donor,,P2,permissive_or_noncopyleft_known,direct_incorporation_ok,"The repo is MIT and direct use is legally straightforward, but the current HyperTwist posture is still below-core donor use because the strongest value is in XR pedagogy, embodied onboarding, and code-to-scene boundary ideas rather than product-core ownership.",Use selectively as a donor or bounded adapter where the XR pedagogy and code-to-scene representation ideas materially shorten build time.,Preserve MIT notices and attribution where required.,Usually unnecessary unless later replacing a narrow implementation seam is architecturally cleaner than carrying the upstream code.,high,below-core-mit-donor,yes,,,,,,,,,,,,,v6.3_final_source_of_truth,Corrected on 2026-04-25 from stale merge-bench posture to dossier-backed below-core XR pedagogy donor status.,selected_not_live_permissive_candidate,phase0r_permissive_eval_then_implement,"Phase 1R closed. Retain as a Phase 3R permissive implementation candidate; implement only from its packet authority and the retained-set contract, not by reopening Phase 0R." +11903,NuiLab/code-vr,https://github.com/NuiLab/code-vr,HyperTwist,20.0,118.0,133.0,B,vision / perception / AR,subsystem donor,vision donor,donor bench,repurpose,moderate modification,"Retain the valuable internal engine, but expect to replace UI/product shell, adapt schemas/APIs, and refactor boundaries so it can plug into the target anchors cleanly. For this repo class, that usually means preserving calibration/detection/state-reconstruction logic while replacing camera UX and integration surfaces.","NuiLab/code-vr — (license permissive per repo) — VR codebase explorer. | poliva/cubedex, tao-yu/Alg-Trainer, kkoomen/qbr, vivaansinghvi07/rubix-cube-solver, NuiLab/code-vr, molgenis/Graph2VR (core permissive parts), brianpeiris/RiftSketc...","Integrate as a cubing / algorithm training subsystem for HyperTwist. Preserve the strongest existing pieces — scramble generation, algorithm database, recognition/training loop, timing/statistics, virtual cube, smartcube hooks, spaced repetition — and expose them behind a portfolio-stable interface. Wire first into tao-yu/Alg-Trainer, then into poliva/cubedex for orchestration, visualization, or data exchange.","Consolidate under the Hyperspeedcube + cubing.js + qbr nucleus, not beside it as a separate silo. Normalize data contracts, auth/permissions, storage, and telemetry; then attach as a service, plugin, canvas layer, trainer, or analysis module. Descending combination order: tao-yu/Alg-Trainer, poliva/cubedex, Lykos/cube_trainer.","Repurpose here means: turn it into a trainer engine, solver/timer backend, recognition drill module, or method-specific practice mode for HyperTwist.",Map module boundaries; Identify hidden reusable internals; Define adapter/API boundary to target anchors; Write extraction tests against upstream behavior; Benchmark calibration pipeline; Extract state reconstruction; Wrap with camera/AR adapter,deep source audit,"Hidden value often sits in calibration, preprocessing, stabilization, object/state reconstruction, replay artifacts, and camera-to-domain state pipelines that are not obvious from demos.",Inspect preprocessing/calibration; tracking stabilization; state reconstruction; replay/event model; camera abstraction; fallback heuristics; testing assets/videos; performance shortcuts.,"Inspect package manifests, README/docs, src tree, examples, tests, CI workflows, config files, migrations/schemas, and hidden feature flags or experimental modules. Look for algorithm databases, spaced-repetition logic, scramble generation, timer/stat code, virtual cube components, smartcube adapters, and custom-trainer configuration support.","Audit NuiLab/code-vr as a vision / perception / AR candidate for HyperTwist. Do not stop at README-level features. Inspect: Inspect preprocessing/calibration; tracking stabilization; state reconstruction; replay/event model; camera abstraction; fallback heuristics; testing assets/videos; performance shortcuts. Decide whether the best extraction path is moderate modification and whether it belongs as subsystem donor / vision donor. Test the three merger paths in order: 1) kkoomen/qbr [foundation + perception donor]; 2) vivaansinghvi07/rubix-cube-solver [perception + replay donor]; 3) cubing/cubing.js [state/render backend]. Return hidden modules, reusable schemas, protocol layers, plugin hooks, render/state models, datasets/test fixtures, and any subsystem stronger than the visible product shell.",kkoomen/qbr,foundation + perception donor,"Use this repo against the partner as an augmenting layer; preserve the partner as the likely base and mine this repo for capabilities that improve breadth, UX, or specialization.",vivaansinghvi07/rubix-cube-solver,perception + replay donor,Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.,cubing/cubing.js,state/render backend,Use the partner for canonical state or rendering abstractions and merge this repo's specialized logic on top.,VectorShell | ScriptoriumAI,VectorShell can borrow spatial/rendering and perception primitives; ScriptoriumAI can borrow tutorial/educational visualization patterns rather than the full engine.,exclude from standalone? no,"Not necessarily the final base, but keep as an active subsystem candidate or major donor.",medium,single-source signal; clear taxonomy; active integration value,medium,memo mentions: 2,"Licensing intentionally ignored as a decision filter in this canonical evaluation; assess only architecture, capability, donor value, and concept transfer.",,,,"NuiLab/code-vr — (license permissive per repo) — VR codebase explorer. | poliva/cubedex, tao-yu/Alg-Trainer, kkoomen/qbr, vivaansinghvi07/rubix-cube-solver, NuiLab/code-vr, molgenis/Graph2VR (core permissive parts), brianpeiris/RiftSketch, aMonteSl/CodeXR.",NuiLab/code-vr is treated as repurpose for HyperTwist because the current dossier keeps it below core tier as an XR pedagogy and code-to-scene representation donor rather than as an active merge-set candidate or product shell.,memo,False,True,0.0,2.0,HT_cube_vision,HT_cube_vision_0007,cubing / algorithm training,Integrate as a shared building block across at least two projects. Its memo and bookmark signals place it in the computer vision / AR layer.,multi-project,computer vision / AR,integrate,heavy modification,medium,nuilab/code-vr,HyperTwist,,,,,,,,,,,,,,,,Original global operational v3 retained,MIT,known_from_reference_material,uploaded_reference_docs,no,,,,Supplemental intake references are advisory only; v6 adjudication remains the source of truth.,Potentially relevant,yes,v6 unified all-project source-of-truth pack,v5_carry_forward,,20.0,5,118.0,Donor Bench,XR pedagogy and code-to-scene representation donor,,P2,permissive_or_noncopyleft_known,direct_incorporation_ok,"The repo is MIT and direct use is legally straightforward, but the current HyperTwist posture is still below-core donor use because the strongest value is in XR pedagogy, embodied onboarding, and code-to-scene boundary ideas rather than product-core ownership.",Use selectively as a donor or bounded adapter where the XR pedagogy and code-to-scene representation ideas materially shorten build time.,Preserve MIT notices and attribution where required.,Usually unnecessary unless later replacing a narrow implementation seam is architecturally cleaner than carrying the upstream code.,high,below-core-mit-donor,yes,,,,,,,,,,,,,v6.3_final_source_of_truth,Corrected on 2026-04-25 from stale merge-bench posture to dossier-backed below-core XR pedagogy donor status.,implemented_live_permissive,landed_permissive_preserve,"Phase 3R-E closed. Preserve as the landed first-party embodied companion, narration, lip-sync, gesture, subtitle, and avatar-embed lane; start future widening from the live-lane audit, then the 3R-E implementation packet, then REPO_LICENSE_TRACKING.md." 11906,ShellPuppy/RCube,https://github.com/ShellPuppy/RCube,HyperTwist,21.0,118.0,133.0,B,large-N solver benchmark,benchmark,Large-N solver benchmark,Reserve Bench,future candidate,architecture only,"Retain the valuable internal engine, but expect to replace UI/product shell, adapt schemas/APIs, and refactor boundaries so it can plug into the target anchors cleanly. For this repo class, that usually means preserving cube-state, scramble, scheduling, or timer internals while adapting pedagogy, analytics, and UI.","Benchmark-only retained value: large-N orientation tricks, stage framing, and big-cube algorithm expectations. Study the algorithm/reference behavior only.","Keep as a restrictive large-N solver benchmark. Use it for algorithm/reference comparison, not as donor code.",Do not treat this repo as a merge candidate. Translate only large-cube orientation and stage-framing ideas into first-party work if later needed.,Repurpose here means: use as an algorithm/reference benchmark for large-cube state and orientation tricks.,Map module boundaries; Identify hidden reusable internals; Define adapter/API boundary to target anchors; Write extraction tests against upstream behavior; Extract cube-state model; Normalize trainer/case schema; Expose analytics and replay hooks,algorithm benchmark review,Hidden value sits in orientation shortcuts and stage framing for extremely large cubes.,Which large-cube orientation and stage strategies are worth preserving as benchmark knowledge?,"Inspect large-cube orientation logic, stage structure, and output/reporting surfaces as benchmark material only.","Audit ShellPuppy/RCube only as a restrictive large-N solver benchmark. Extract algorithm ideas and acceptance-test expectations, not donor code.",tao-yu/Alg-Trainer,base + donor swarm,Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.,poliva/cubedex,specialized training UX donor,Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.,Lykos/cube_trainer,sampling/analytics donor,Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.,Reference only,"Retain only as benchmark, oracle, acceptance-test, or clean-room planning input.",exclude from donor lane,The repo is GPL large-N solver code and should remain only as an algorithm/reference benchmark for big-cube behavior.,high,Dossier-backed classification is stable: the retained value is algorithm/reference benchmarking for large-N cubes.,high,Dossier-backed classification is stable: the retained value is algorithm/reference benchmarking for large-N cubes.,"Licensing intentionally ignored as a decision filter in this canonical evaluation; assess only architecture, capability, donor value, and concept transfer.",,,,ShellPuppy/RCube — GPL large-N cube solver; keep only as a large-N solver benchmark.,ShellPuppy/RCube remains useful only because it captures a narrow large-N solver lane that HyperTwist may later benchmark against. It is not a donor candidate.,memo,False,True,0.0,2.0,HT_solver_oracles,HT_solver_oracles_0001,Large-N solver benchmark,"Large-N solver benchmark for HyperTwist; retained for reference value, not donor use.",HyperTwist,Large-N solver benchmark,future candidate,architecture only,medium,shellpuppy/rcube,HyperTwist,,,,,,,,,,,,,,,,Original global operational v3 retained,GPL-3.0,known_from_reference_material,uploaded_reference_docs,no,,,,Supplemental intake references are advisory only; v6 adjudication remains the source of truth.,Usually indirect,yes,v6 unified all-project source-of-truth pack,v5_carry_forward,,21.0,5,118.0,Reserve Bench,Large-N solver benchmark,Included,P3,mixed_or_boundary_sensitive_known,pattern_only_preferred,"The repo is GPL large-N solver code and remains a benchmark/reference lane for centers, edges, parity, and later clean-room research rather than donor use.","Reference only: use as a large-N centers, edges, and parity benchmark without direct source incorporation.",Direct incorporation would require GPL-compatible distribution/compliance and is not the planned HyperTwist path.,Only if a later first-party large-N lane needs recreation of a narrow behavior or algorithmic framing; otherwise keep this as a benchmark.,high,gpl-large-n-benchmark,no,,,,,,,,,,,,,v6.3_final_source_of_truth,Corrected on 2026-04-25 from stale donor posture to dossier-backed large-N solver benchmark status.,not_live_reference_or_discard_candidate,phase0r_reference_benchmark_or_discard_eval,"Packet 0R-E closed. Retain as a large-N centers/edges/parity benchmark and later clean-room research input, not as an active product donor." 11909,brownan/Rubiks-Cube-Solver,https://github.com/brownan/Rubiks-Cube-Solver,HyperTwist,22.0,118.0,133.0,B,cubing trainer / solver / timing,subsystem donor,training donor,Reserve Bench,future candidate,architecture only,"Retain the valuable internal engine, but expect to replace UI/product shell, adapt schemas/APIs, and refactor boundaries so it can plug into the target anchors cleanly. For this repo class, that usually means preserving cube-state, scramble, scheduling, or timer internals while adapting pedagogy, analytics, and UI.",brownan/Rubiks-Cube-Solver — GPL-3.0 — Optimal pattern-database solver. | brownan/Rubiks-Cube-Solver — GPL-3.0.,"Integrate as a cubing / algorithm training subsystem for HyperTwist. Preserve the strongest existing pieces — scramble generation, algorithm database, recognition/training loop, timing/statistics, virtual cube, smartcube hooks, spaced repetition — and expose them behind a portfolio-stable interface. Wire first into tao-yu/Alg-Trainer, then into poliva/cubedex for orchestration, visualization, or data exchange.","Consolidate under the Hyperspeedcube + cubing.js + qbr nucleus, not beside it as a separate silo. Normalize data contracts, auth/permissions, storage, and telemetry; then attach as a service, plugin, canvas layer, trainer, or analysis module. Descending combination order: tao-yu/Alg-Trainer, poliva/cubedex, Lykos/cube_trainer.","Repurpose here means: turn it into a trainer engine, solver/timer backend, recognition drill module, or method-specific practice mode for HyperTwist.",Map module boundaries; Identify hidden reusable internals; Define adapter/API boundary to target anchors; Write extraction tests against upstream behavior; Extract cube-state model; Normalize trainer/case schema; Expose analytics and replay hooks,deep source audit,"Hidden value often sits in cube-state representation, scramble generation, weighted drill scheduling, recognition datasets, replay/timer internals, and case database schemas.",Inspect cube-state model; scramble generator; trainer weighting/scheduling; case database and metadata; replay/timer model; import/export of alg sets; smartcube or sensor adapters.,"Inspect package manifests, README/docs, src tree, examples, tests, CI workflows, config files, migrations/schemas, and hidden feature flags or experimental modules. Look for algorithm databases, spaced-repetition logic, scramble generation, timer/stat code, virtual cube components, smartcube adapters, and custom-trainer configuration support.","Audit brownan/Rubiks-Cube-Solver as a cubing trainer / solver / timing candidate for HyperTwist. Do not stop at README-level features. Inspect: Inspect cube-state model; scramble generator; trainer weighting/scheduling; case database and metadata; replay/timer model; import/export of alg sets; smartcube or sensor adapters. Decide whether the best extraction path is moderate modification and whether it belongs as subsystem donor / training donor. Test the three merger paths in order: 1) tao-yu/Alg-Trainer [base + donor swarm]; 2) poliva/cubedex [specialized training UX donor]; 3) Lykos/cube_trainer [sampling/analytics donor]. Return hidden modules, reusable schemas, protocol layers, plugin hooks, render/state models, datasets/test fixtures, and any subsystem stronger than the visible product shell.",tao-yu/Alg-Trainer,base + donor swarm,Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.,poliva/cubedex,specialized training UX donor,Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.,Lykos/cube_trainer,sampling/analytics donor,Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.,project-local first,"Cross-project transfer is possible, but the value is clearest inside the assigned project until source audit exposes more reusable primitives.",exclude from standalone? no,"Not necessarily the final base, but keep as an active subsystem candidate or major donor.",medium,single-source signal; clear taxonomy; active integration value,medium,memo mentions: 2,"Licensing intentionally ignored as a decision filter in this canonical evaluation; assess only architecture, capability, donor value, and concept transfer.",,,,brownan/Rubiks-Cube-Solver — GPL-3.0 — Optimal pattern-database solver. | brownan/Rubiks-Cube-Solver — GPL-3.0.,brownan/Rubiks-Cube-Solver is treated as a future candidate for HyperTwist because the current dossier keeps it as a benchmark oracle and later clean-room optimal-solver target rather than as a direct donor.,memo,False,True,0.0,2.0,HT_training_stack,HT_training_stack_0007,cubing / algorithm training,Integrate primarily for HyperTwist. Its memo and bookmark signals place it in the cubing / algorithm training layer.,HyperTwist,cubing / algorithm training,integrate,moderate modification,medium,brownan/rubiks-cube-solver,HyperTwist,,,,,,,,,,,,,,,,Original global operational v3 retained,GPL-3.0,known_from_reference_material,uploaded_reference_docs,no,,,,Supplemental intake references are advisory only; v6 adjudication remains the source of truth.,Usually indirect,yes,v6 unified all-project source-of-truth pack,v5_carry_forward,,22.0,5,118.0,Reserve Bench,Benchmark oracle and clean-room optimal-solver candidate,,P2,mixed_or_boundary_sensitive_known,reverse_engineer_preferred,The repo is GPL-3.0 and remains the primary compact solver oracle and clean-room-later heuristic/search benchmark. Preserve correctness and search behavior through scrubbed first-party specifications only.,Use as an oracle and Model A source only; Model B should implement any solver work from a scrubbed first-party specification.,Direct incorporation would require GPL-compatible distribution/compliance and is not the planned HyperTwist path.,Yes — this is the preferred path for any later first-party optimal-solver effort.,high,gpl-oracle-clean-room-review,no,,,,,,,,,,,,,v6.3_final_source_of_truth,Corrected on 2026-04-25 from stale unknown-license merge-bench posture to dossier-backed benchmark-oracle and clean-room optimal-solver status.,not_live_reference_or_discard_candidate,phase0r_reference_benchmark_or_discard_eval,"Packet 0R-E closed. Retain as the primary compact solver oracle and clean-room-later heuristic/search benchmark; use for correctness, not donor code." 11915,newyork-anthonyng/rubiks-cross-trainer,https://github.com/newyork-anthonyng/rubiks-cross-trainer,HyperTwist,24.0,118.0,133.0,B,cubing trainer / solver / timing,subsystem donor,training donor,donor bench,repurpose,moderate modification,"Retain the valuable internal engine, but expect to replace UI/product shell, adapt schemas/APIs, and refactor boundaries so it can plug into the target anchors cleanly. For this repo class, that usually means preserving cube-state, scramble, scheduling, or timer internals while adapting pedagogy, analytics, and UI.",newyork-anthonyng/rubiks-cross-trainer — MIT — Cross trainer library (scramble generator). | newyork-anthonyng/rubiks-cross-trainer — MIT.,"Integrate as a cubing / algorithm training subsystem for HyperTwist. Preserve the strongest existing pieces — scramble generation, algorithm database, recognition/training loop, timing/statistics, virtual cube, smartcube hooks, spaced repetition — and expose them behind a portfolio-stable interface. Wire first into tao-yu/Alg-Trainer, then into poliva/cubedex for orchestration, visualization, or data exchange.","Consolidate under the Hyperspeedcube + cubing.js + qbr nucleus, not beside it as a separate silo. Normalize data contracts, auth/permissions, storage, and telemetry; then attach as a service, plugin, canvas layer, trainer, or analysis module. Descending combination order: tao-yu/Alg-Trainer, poliva/cubedex, Lykos/cube_trainer.","Repurpose here means: turn it into a trainer engine, solver/timer backend, recognition drill module, or method-specific practice mode for HyperTwist.",Map module boundaries; Identify hidden reusable internals; Define adapter/API boundary to target anchors; Write extraction tests against upstream behavior; Extract cube-state model; Normalize trainer/case schema; Expose analytics and replay hooks,deep source audit,"Hidden value often sits in cube-state representation, scramble generation, weighted drill scheduling, recognition datasets, replay/timer internals, and case database schemas.",Inspect cube-state model; scramble generator; trainer weighting/scheduling; case database and metadata; replay/timer model; import/export of alg sets; smartcube or sensor adapters.,"Inspect package manifests, README/docs, src tree, examples, tests, CI workflows, config files, migrations/schemas, and hidden feature flags or experimental modules. Look for algorithm databases, spaced-repetition logic, scramble generation, timer/stat code, virtual cube components, smartcube adapters, and custom-trainer configuration support.","Audit newyork-anthonyng/rubiks-cross-trainer as a cubing trainer / solver / timing candidate for HyperTwist. Do not stop at README-level features. Inspect: Inspect cube-state model; scramble generator; trainer weighting/scheduling; case database and metadata; replay/timer model; import/export of alg sets; smartcube or sensor adapters. Decide whether the best extraction path is moderate modification and whether it belongs as subsystem donor / training donor. Test the three merger paths in order: 1) tao-yu/Alg-Trainer [base + donor swarm]; 2) poliva/cubedex [specialized training UX donor]; 3) Lykos/cube_trainer [sampling/analytics donor]. Return hidden modules, reusable schemas, protocol layers, plugin hooks, render/state models, datasets/test fixtures, and any subsystem stronger than the visible product shell.",tao-yu/Alg-Trainer,base + donor swarm,Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.,poliva/cubedex,specialized training UX donor,Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.,Lykos/cube_trainer,sampling/analytics donor,Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.,project-local first,"Cross-project transfer is possible, but the value is clearest inside the assigned project until source audit exposes more reusable primitives.",exclude from standalone? no,"Not necessarily the final base, but keep as an active subsystem candidate or major donor.",medium,single-source signal; clear taxonomy; active integration value,medium,memo mentions: 2,"Licensing intentionally ignored as a decision filter in this canonical evaluation; assess only architecture, capability, donor value, and concept transfer.",,,,newyork-anthonyng/rubiks-cross-trainer — MIT — Cross trainer library (scramble generator). | newyork-anthonyng/rubiks-cross-trainer — MIT.,newyork-anthonyng/rubiks-cross-trainer is treated as repurpose for HyperTwist because the current dossier keeps it as a focused donor for its precomputed one-to-eight-move cross corpus and cross-specific drill progression rather than as a platform lane.,memo,False,True,0.0,2.0,HT_training_stack,HT_training_stack_0008,cubing / algorithm training,Integrate primarily for HyperTwist. Its memo and bookmark signals place it in the cubing / algorithm training layer.,HyperTwist,cubing / algorithm training,integrate,moderate modification,medium,newyork-anthonyng/rubiks-cross-trainer,HyperTwist,,,,,,,,,,,,,,,,Original global operational v3 retained,MIT,known_from_reference_material,uploaded_reference_docs,no,,,,Supplemental intake references are advisory only; v6 adjudication remains the source of truth.,Usually indirect,yes,v6 unified all-project source-of-truth pack,v5_carry_forward,,24.0,5,118.0,Donor Bench,Focused donor,,,permissive_or_noncopyleft_known,direct_incorporation_ok,"This repo is aligned with a direct integration path for HyperTwist because it is either already implemented, strategically central, or donor-grade without a visible copyleft constraint in the current materials. Deep incorporation is sensible if the source audit confirms architectural cleanliness.","Direct embed, vendored module, package dependency, or tightly integrated adapter as the architecture requires.","Typically preserve notices, attribution, and license text where required; no special copyleft-driven disclosure posture is normally needed.",Usually unnecessary unless you later decide the existing implementation is too constraining architecturally.,high,strategic-or-implemented-component,yes,,,,,,,,,,,,,v6.3_final_source_of_truth,Normalized legacy merge-bench wording to dossier-backed focused-donor posture on 2026-04-25.,implemented_live_permissive,landed_permissive_preserve,Phase 1R closed. Preserve as a landed first-party permissive lane; keep notices and attribution visible and widen only through ordinary owned enhancement work. @@ -37,40 +37,40 @@ execution_queue_order,repo,primary_url,best_fit_project_v2,project_rank,portfoli 11936,yakupbilen/drl-rubiks-cube,https://github.com/yakupbilen/drl-rubiks-cube,HyperTwist,31.0,117.0,132.0,B,vision / perception / AR,subsystem donor,vision donor,Reserve Bench,future candidate,architecture only,"Retain the valuable internal engine, but expect to replace UI/product shell, adapt schemas/APIs, and refactor boundaries so it can plug into the target anchors cleanly. For this repo class, that usually means preserving calibration/detection/state-reconstruction logic while replacing camera UX and integration surfaces.",yakupbilen/drl-rubiks-cube — MIT — RL solver with PyQt5 + webcam input.,"Integrate as a cubing / algorithm training subsystem for HyperTwist. Preserve the strongest existing pieces — scramble generation, algorithm database, recognition/training loop, timing/statistics, virtual cube, smartcube hooks, spaced repetition — and expose them behind a portfolio-stable interface. Wire first into tao-yu/Alg-Trainer, then into poliva/cubedex for orchestration, visualization, or data exchange.","Consolidate under the Hyperspeedcube + cubing.js + qbr nucleus, not beside it as a separate silo. Normalize data contracts, auth/permissions, storage, and telemetry; then attach as a service, plugin, canvas layer, trainer, or analysis module. Descending combination order: tao-yu/Alg-Trainer, poliva/cubedex, Lykos/cube_trainer.","Repurpose here means: turn it into a trainer engine, solver/timer backend, recognition drill module, or method-specific practice mode for HyperTwist.",Map module boundaries; Identify hidden reusable internals; Define adapter/API boundary to target anchors; Write extraction tests against upstream behavior; Benchmark calibration pipeline; Extract state reconstruction; Wrap with camera/AR adapter,deep source audit,"Hidden value often sits in calibration, preprocessing, stabilization, object/state reconstruction, replay artifacts, and camera-to-domain state pipelines that are not obvious from demos.",Inspect preprocessing/calibration; tracking stabilization; state reconstruction; replay/event model; camera abstraction; fallback heuristics; testing assets/videos; performance shortcuts.,"Inspect package manifests, README/docs, src tree, examples, tests, CI workflows, config files, migrations/schemas, and hidden feature flags or experimental modules. Look for algorithm databases, spaced-repetition logic, scramble generation, timer/stat code, virtual cube components, smartcube adapters, and custom-trainer configuration support.","Audit yakupbilen/drl-rubiks-cube as a vision / perception / AR candidate for HyperTwist. Do not stop at README-level features. Inspect: Inspect preprocessing/calibration; tracking stabilization; state reconstruction; replay/event model; camera abstraction; fallback heuristics; testing assets/videos; performance shortcuts. Decide whether the best extraction path is moderate modification and whether it belongs as subsystem donor / vision donor. Test the three merger paths in order: 1) kkoomen/qbr [foundation + perception donor]; 2) vivaansinghvi07/rubix-cube-solver [perception + replay donor]; 3) cubing/cubing.js [state/render backend]. Return hidden modules, reusable schemas, protocol layers, plugin hooks, render/state models, datasets/test fixtures, and any subsystem stronger than the visible product shell.",kkoomen/qbr,foundation + perception donor,"Use this repo against the partner as an augmenting layer; preserve the partner as the likely base and mine this repo for capabilities that improve breadth, UX, or specialization.",vivaansinghvi07/rubix-cube-solver,perception + replay donor,Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.,cubing/cubing.js,state/render backend,Use the partner for canonical state or rendering abstractions and merge this repo's specialized logic on top.,VectorShell | ScriptoriumAI,VectorShell can borrow spatial/rendering and perception primitives; ScriptoriumAI can borrow tutorial/educational visualization patterns rather than the full engine.,exclude from standalone? no,"Not necessarily the final base, but keep as an active subsystem candidate or major donor.",medium,single-source signal; clear taxonomy; active integration value,medium,memo mentions: 1,"Licensing intentionally ignored as a decision filter in this canonical evaluation; assess only architecture, capability, donor value, and concept transfer.",,,,yakupbilen/drl-rubiks-cube — MIT — RL solver with PyQt5 + webcam input.,"yakupbilen/drl-rubiks-cube is treated as a future candidate for HyperTwist because the current dossier retains it mainly for learned-heuristic search, batched A-star style experimentation, and training-loop ideas, not as part of the committed perception core.",memo,False,True,0.0,1.0,HT_cube_vision,HT_cube_vision_0008,cubing / algorithm training,Integrate primarily for HyperTwist. Its memo and bookmark signals place it in the cubing / algorithm training layer.,HyperTwist,cubing / algorithm training,integrate,moderate modification,medium,yakupbilen/drl-rubiks-cube,HyperTwist,,,,,,,,,,,,,,,,Original global operational v3 retained,MIT,known_from_reference_material,uploaded_reference_docs,no,,,,Supplemental intake references are advisory only; v6 adjudication remains the source of truth.,Usually indirect,yes,v6 unified all-project source-of-truth pack,v5_carry_forward,,31.0,5,117.0,Reserve Bench,Search/training systems bench,,,permissive_or_noncopyleft_known,pattern_only_preferred,"The repo is MIT and remains a research benchmark for learned heuristic search, ADI state generation, and offline experimentation rather than a near-term product donor.",Reference only: benchmark learned heuristic search and training experiments without near-term direct incorporation.,"Typically preserve notices, attribution, and license text where required; no special copyleft-driven disclosure posture is normally needed.",Usually unnecessary unless you later decide the existing implementation is too constraining architecturally.,high,strategic-or-implemented-component,yes,,,,,,,,,,,,,v6.3_final_source_of_truth,Normalized legacy merge-bench wording to dossier-backed below-core benchmark posture on 2026-04-25.,not_live_reference_or_discard_candidate,phase0r_reference_benchmark_or_discard_eval,"Packet 0R-E closed. Retain as an MIT research benchmark for learned heuristic search, ADI training loops, and offline experimentation rather than near-term product implementation." 11939,Hypercubers/hypercubing.xyz,https://github.com/Hypercubers/hypercubing.xyz,HyperTwist,32.0,92.0,101.0,C,hypercubing / nD engine,subsystem donor,simulation donor,locked strategic donor,repurpose,moderate modification,"Treat this as a mineable codebase: keep selected internals (algorithms, renderers, adapters, parsers, schedulers) while replacing the surrounding product assumptions and architecture. For this repo class, that usually means preserving generalized puzzle/state/render logic while building a new application shell around it.",Website for the Hypercubing community,"Repurpose selected subsystems rather than the whole product. Mine the repo for nD state model, move notation, renderer, projection controls, solver/traversal logic, puzzle serialization, replay; keep what materially shortens build time, but rebind data contracts, permissions, UI shell, storage, and deployment to the HyperTwist architecture. Best first pairing order: HactarCE/Hyperspeedcube, cubing/cubing.js, tao-yu/Alg-Trainer.","Consolidate under the Hyperspeedcube + cubing.js + qbr nucleus, not beside it as a separate silo. Normalize data contracts, auth/permissions, storage, and telemetry; then attach as a service, plugin, canvas layer, trainer, or analysis module. Descending combination order: HactarCE/Hyperspeedcube, cubing/cubing.js, tao-yu/Alg-Trainer.",Repurpose here means: turn it into a higher-dimensional renderer/simulator donor and shared interaction grammar for HyperTwist and long-horizon VectorShell.,Map module boundaries; Identify hidden reusable internals; Define adapter/API boundary to target anchors; Write extraction tests against upstream behavior; Isolate puzzle/state core; Extract render/input abstractions; Document notation and save format,deep source audit,"Hidden value is likely in generalized puzzle/state representations, higher-dimensional transforms, notation systems, save formats, puzzle generators, and rendering abstractions.",Inspect generalized puzzle/state model; notation parser; transform math; rendering abstraction; save/load format; puzzle generator; input mapping; performance optimizations.,"Inspect package manifests, README/docs, src tree, examples, tests, CI workflows, config files, migrations/schemas, and hidden feature flags or experimental modules. Look for higher-dimensional state/notation representations, projection math, renderer abstractions, puzzle serialization, controls, and replay/training hooks.","Audit Hypercubers/hypercubing.xyz as a hypercubing / nD engine candidate for HyperTwist. Do not stop at README-level features. Inspect: Inspect generalized puzzle/state model; notation parser; transform math; rendering abstraction; save/load format; puzzle generator; input mapping; performance optimizations. Decide whether the best extraction path is heavy modification and whether it belongs as subsystem donor / simulation donor. Test the three merger paths in order: 1) HactarCE/Hyperspeedcube [foundation + donor]; 2) cubing/cubing.js [3D engine + notation/state donor]; 3) tao-yu/Alg-Trainer [training UX donor]. Return hidden modules, reusable schemas, protocol layers, plugin hooks, render/state models, datasets/test fixtures, and any subsystem stronger than the visible product shell.",HactarCE/Hyperspeedcube,foundation + donor,"Use this repo against the partner as an augmenting layer; preserve the partner as the likely base and mine this repo for capabilities that improve breadth, UX, or specialization.",cubing/cubing.js,3D engine + notation/state donor,Use the partner for canonical state or rendering abstractions and merge this repo's specialized logic on top.,tao-yu/Alg-Trainer,training UX donor,Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.,VectorShell | ScriptoriumAI,VectorShell can borrow spatial/rendering and perception primitives; ScriptoriumAI can borrow tutorial/educational visualization patterns rather than the full engine.,"exclude from core, keep as donor","Do not let it consume roadmap as a full product shell; mine reusable engines, adapters, schemas, UX patterns, or datasets.",medium-low,single-source signal; clear taxonomy; mostly donor/reference role,medium,explicit bookmark description available,"Licensing intentionally ignored as a decision filter in this canonical evaluation; assess only architecture, capability, donor value, and concept transfer.",HyperTwist(1),HyperTwist Consider,Website for the Hypercubing community,,"Hypercubers/hypercubing.xyz is treated as repurpose for HyperTwist because visible metadata points to the hypercubing / nD simulation layer. Surface signal: Website for the Hypercubing community The fit looks real, but more as a donor/augmenter than as a standalone foundation.",bookmarks,True,False,1.0,0.0,HT_hyper_engine,HT_hyper_engine_0006,hypercubing / nD simulation,"Integrate primarily for HyperTwist. Its description and bookmark placement under ""HyperTwist Consider"" place it in the hypercubing / nD simulation layer.",HyperTwist,hypercubing / nD simulation,integrate,heavy modification,medium,hypercubers/hypercubing.xyz,HyperTwist,,,,,,,,,,,,,,,,Original global operational v3 retained,MIT,known_from_reference_material,uploaded_reference_docs,no,,,,Supplemental intake references are advisory only; v6 adjudication remains the source of truth.,Usually indirect,yes,v6 unified all-project source-of-truth pack,v5_carry_forward,,32.0,5,92.0,Locked Strategic Donor,Knowledge and curriculum donor,,P1,permissive_or_noncopyleft_known,direct_incorporation_ok,The repo is MIT and is retained as a high-value knowledge and curriculum donor. Direct use of code/content structures is legally straightforward where it materially helps HyperTwist.,"Use selectively as a donor for knowledge structures, notation, taxonomy, and leaderboard-generation logic; do not confuse the site snapshot with the canonical repo.",Preserve MIT notices and attribution where required.,Usually unnecessary unless later replacing a narrow implementation seam is cleaner than carrying the upstream code.,high,permissive-knowledge-donor,yes,,,,,,,,,,,,,v6.3_final_source_of_truth,Corrected on 2026-04-25 from stale unknown-license donor-bench posture to dossier-backed MIT knowledge/curriculum donor status.,implemented_live_permissive,landed_permissive_preserve,"Phase 3R-B closed. Preserve as the landed first-party hypercubing knowledge, notation, progression, software-reference, and leaderboard-contract lane; start future widening from the live-lane audit, then the 3R-B implementation packet, then REPO_LICENSE_TRACKING.md." 11945,Aarav2709/KubeTimr,https://github.com/Aarav2709/KubeTimr,HyperTwist,34.0,88.0,97.0,C,cubing trainer / solver / timing,subsystem donor,training donor,donor bench,repurpose,moderate modification,"Retain the valuable internal engine, but expect to replace UI/product shell, adapt schemas/APIs, and refactor boundaries so it can plug into the target anchors cleanly. For this repo class, that usually means preserving cube-state, scramble, scheduling, or timer internals while adapting pedagogy, analytics, and UI.",Aarav2709/KubeTimr — MIT — Keyboard-first offline timer. | Aarav2709/KubeTimr — MIT — Offline timer.,"Repurpose selected subsystems rather than the whole product. Mine the repo for scramble generation, algorithm database, recognition/training loop, timing/statistics, virtual cube, smartcube hooks, spaced repetition; keep what materially shortens build time, but rebind data contracts, permissions, UI shell, storage, and deployment to the HyperTwist architecture. Best first pairing order: tao-yu/Alg-Trainer, poliva/cubedex, Lykos/cube_trainer.","Consolidate under the Hyperspeedcube + cubing.js + qbr nucleus, not beside it as a separate silo. Normalize data contracts, auth/permissions, storage, and telemetry; then attach as a service, plugin, canvas layer, trainer, or analysis module. Descending combination order: tao-yu/Alg-Trainer, poliva/cubedex, Lykos/cube_trainer.","Repurpose here means: turn it into a trainer engine, solver/timer backend, recognition drill module, or method-specific practice mode for HyperTwist.",Map module boundaries; Identify hidden reusable internals; Define adapter/API boundary to target anchors; Write extraction tests against upstream behavior; Extract cube-state model; Normalize trainer/case schema; Expose analytics and replay hooks,deep source audit,"Hidden value often sits in cube-state representation, scramble generation, weighted drill scheduling, recognition datasets, replay/timer internals, and case database schemas.",Inspect cube-state model; scramble generator; trainer weighting/scheduling; case database and metadata; replay/timer model; import/export of alg sets; smartcube or sensor adapters.,"Inspect package manifests, README/docs, src tree, examples, tests, CI workflows, config files, migrations/schemas, and hidden feature flags or experimental modules. Look for algorithm databases, spaced-repetition logic, scramble generation, timer/stat code, virtual cube components, smartcube adapters, and custom-trainer configuration support.","Audit Aarav2709/KubeTimr as a cubing trainer / solver / timing candidate for HyperTwist. Do not stop at README-level features. Inspect: Inspect cube-state model; scramble generator; trainer weighting/scheduling; case database and metadata; replay/timer model; import/export of alg sets; smartcube or sensor adapters. Decide whether the best extraction path is moderate modification and whether it belongs as subsystem donor / training donor. Test the three merger paths in order: 1) tao-yu/Alg-Trainer [base + donor swarm]; 2) poliva/cubedex [specialized training UX donor]; 3) Lykos/cube_trainer [sampling/analytics donor]. Return hidden modules, reusable schemas, protocol layers, plugin hooks, render/state models, datasets/test fixtures, and any subsystem stronger than the visible product shell.",tao-yu/Alg-Trainer,base + donor swarm,Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.,poliva/cubedex,specialized training UX donor,Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.,Lykos/cube_trainer,sampling/analytics donor,Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.,project-local first,"Cross-project transfer is possible, but the value is clearest inside the assigned project until source audit exposes more reusable primitives.","exclude from core, keep as donor","Do not let it consume roadmap as a full product shell; mine reusable engines, adapters, schemas, UX patterns, or datasets.",medium,single-source signal; clear taxonomy; mostly donor/reference role,medium,strong adjacency to identified core stack; memo mentions: 2,"Licensing intentionally ignored as a decision filter in this canonical evaluation; assess only architecture, capability, donor value, and concept transfer.",,,,Aarav2709/KubeTimr — MIT — Keyboard-first offline timer. | Aarav2709/KubeTimr — MIT — Offline timer.,"Aarav2709/KubeTimr is treated as repurpose for HyperTwist because the current dossier keeps it as a focused subsystem donor for timer-state logic, split-phase handling, local persistence, rolling stats, and keyboard-first offline practice flow rather than as a broader training-platform anchor.",memo,False,True,0.0,2.0,HT_training_stack,HT_training_stack_0015,cubing / algorithm training,Integrate primarily for HyperTwist. Its memo and bookmark signals place it in the cubing / algorithm training layer.,HyperTwist,cubing / algorithm training,integrate,moderate modification,medium,aarav2709/kubetimr,HyperTwist,,,,,,,,,,,,,,,,Original global operational v3 retained,MIT,known_from_reference_material,uploaded_reference_docs,no,,,,Supplemental intake references are advisory only; v6 adjudication remains the source of truth.,Usually indirect,yes,v6 unified all-project source-of-truth pack,v5_carry_forward,,34.0,5,88.0,Donor Bench,Focused subsystem donor,,,permissive_or_noncopyleft_known,direct_incorporation_ok,"This repo is permissively licensed and currently best treated as a focused subsystem donor for timer-state logic, split-phase handling, local persistence, and keyboard-first practice flow. Selective incorporation is legally straightforward, but the product shell should still be reshaped to fit HyperTwist.","Direct embed, vendored module, package dependency, or tightly integrated adapter as the architecture requires.","Typically preserve notices, attribution, and license text where required; no special copyleft-driven disclosure posture is normally needed.",Usually unnecessary unless you later decide the existing implementation is too constraining architecturally.,high,routine-review-only,yes,,,,,,,,,,,,,v6.3_final_source_of_truth,Normalized legacy adjacency wording and stale clean-room boundary posture to dossier-backed focused subsystem donor on 2026-04-25.,implemented_live_permissive,landed_permissive_preserve,"Phase 3R-A closed. Preserve as the landed first-party timer, inspection, splits, stats, persistence, and timer-scoped replay lane; start future widening from the live-lane audit, then the 3R-A implementation packet, then REPO_LICENSE_TRACKING.md." -11951,roice3/MagicTile,https://github.com/roice3/MagicTile,HyperTwist,36.0,88.0,97.0,C,infra / runtime / observability / integration,subsystem donor,integration utility,locked strategic donor,repurpose,moderate modification,"Retain the valuable internal engine, but expect to replace UI/product shell, adapt schemas/APIs, and refactor boundaries so it can plug into the target anchors cleanly. For this repo class, that usually means preserving collectors/adapters/runtime topology logic while integrating into a larger control plane.",Non-euclidean Rubik's Cube Analogues,"Repurpose selected subsystems rather than the whole product. Mine the repo for scramble generation, algorithm database, recognition/training loop, timing/statistics, virtual cube, smartcube hooks, spaced repetition; keep what materially shortens build time, but rebind data contracts, permissions, UI shell, storage, and deployment to the HyperTwist architecture. Best first pairing order: tao-yu/Alg-Trainer, poliva/cubedex, Lykos/cube_trainer.","Consolidate under the Hyperspeedcube + cubing.js + qbr nucleus, not beside it as a separate silo. Normalize data contracts, auth/permissions, storage, and telemetry; then attach as a service, plugin, canvas layer, trainer, or analysis module. Descending combination order: tao-yu/Alg-Trainer, poliva/cubedex, Lykos/cube_trainer.","Repurpose here means: turn it into a trainer engine, solver/timer backend, recognition drill module, or method-specific practice mode for HyperTwist.",Map module boundaries; Identify hidden reusable internals; Define adapter/API boundary to target anchors; Write extraction tests against upstream behavior; Extract collectors/adapters; Normalize topology/config schema; Bridge into control-plane API,deep source audit,"Hidden value usually sits in service topology schemas, collector agents, auth/integration adapters, caching, deployment abstractions, and metrics/event correlation.",Inspect topology/service schema; collectors/agents; auth/integration adapters; caching/state sync; deployment/runtime abstractions; metrics/event correlation; config layering.,"Inspect package manifests, README/docs, src tree, examples, tests, CI workflows, config files, migrations/schemas, and hidden feature flags or experimental modules. Look for algorithm databases, spaced-repetition logic, scramble generation, timer/stat code, virtual cube components, smartcube adapters, and custom-trainer configuration support.","Audit roice3/MagicTile as a infra / runtime / observability / integration candidate for HyperTwist. Do not stop at README-level features. Inspect: Inspect topology/service schema; collectors/agents; auth/integration adapters; caching/state sync; deployment/runtime abstractions; metrics/event correlation; config layering. Decide whether the best extraction path is moderate modification and whether it belongs as subsystem donor / integration utility. Test the three merger paths in order: 1) project-local anchor [base + donor]; 2) shared portfolio utility [augmenter]; 3) cross-project transfer candidate [future merger]. Return hidden modules, reusable schemas, protocol layers, plugin hooks, render/state models, datasets/test fixtures, and any subsystem stronger than the visible product shell.",project-local anchor,base + donor,Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.,shared portfolio utility,augmenter,Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.,cross-project transfer candidate,future merger,Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.,project-local first,"Cross-project transfer is possible, but the value is clearest inside the assigned project until source audit exposes more reusable primitives.","exclude from core, keep as donor","Do not let it consume roadmap as a full product shell; mine reusable engines, adapters, schemas, UX patterns, or datasets.",medium-low,single-source signal; clear taxonomy; mostly donor/reference role,medium,explicit bookmark description available,"Licensing intentionally ignored as a decision filter in this canonical evaluation; assess only architecture, capability, donor value, and concept transfer.",HyperTwist(1),HyperTwist Consider,Non-euclidean Rubik's Cube Analogues,,"roice3/MagicTile is treated as repurpose for HyperTwist because visible metadata points to the cubing / algorithm training layer. Surface signal: Non-euclidean Rubik's Cube Analogues The fit looks real, but more as a donor/augmenter than as a standalone foundation.",bookmarks,True,False,1.0,0.0,HT_hyper_engine,HT_hyper_engine_0007,cubing / algorithm training,"Integrate primarily for HyperTwist. Its description and bookmark placement under ""HyperTwist Consider"" place it in the cubing / algorithm training layer.",HyperTwist,cubing / algorithm training,integrate,moderate modification,medium,roice3/magictile,HyperTwist,,,,,,,,,,,,,,,,Original global operational v3 retained,MIT,known_from_reference_material,uploaded_reference_docs,no,,,,Supplemental intake references are advisory only; v6 adjudication remains the source of truth.,Usually indirect,yes,v6 unified all-project source-of-truth pack,v5_carry_forward,,36.0,5,88.0,Locked Strategic Donor,Top-tier non-Euclidean geometry and topology donor,,P1,permissive_or_noncopyleft_known,direct_incorporation_ok,The repo is MIT and is explicitly retained as a top-tier geometry/topology donor. Direct donor use is legally straightforward if the architecture benefits from it.,Direct donor use or bounded adapter extraction are both acceptable; choose the seam that best preserves the topology and twist infrastructure.,Preserve MIT notices and attribution where required.,Usually unnecessary unless later replacing a narrow seam is cleaner than carrying the upstream code.,high,permissive-top-tier-donor,yes,,,,,,,,,,,,,v6.3_final_source_of_truth,Assigned from legacy HY_misc to HT_hyper_engine during cluster normalization on 2026-04-25.,selected_not_live_permissive_candidate,phase0r_permissive_eval_then_implement,"Phase 1R closed. Retain as a Phase 3R permissive implementation candidate; implement only from its packet authority and the retained-set contract, not by reopening Phase 0R." +11951,roice3/MagicTile,https://github.com/roice3/MagicTile,HyperTwist,36.0,88.0,97.0,C,infra / runtime / observability / integration,subsystem donor,integration utility,locked strategic donor,repurpose,moderate modification,"Retain the valuable internal engine, but expect to replace UI/product shell, adapt schemas/APIs, and refactor boundaries so it can plug into the target anchors cleanly. For this repo class, that usually means preserving collectors/adapters/runtime topology logic while integrating into a larger control plane.",Non-euclidean Rubik's Cube Analogues,"Repurpose selected subsystems rather than the whole product. Mine the repo for scramble generation, algorithm database, recognition/training loop, timing/statistics, virtual cube, smartcube hooks, spaced repetition; keep what materially shortens build time, but rebind data contracts, permissions, UI shell, storage, and deployment to the HyperTwist architecture. Best first pairing order: tao-yu/Alg-Trainer, poliva/cubedex, Lykos/cube_trainer.","Consolidate under the Hyperspeedcube + cubing.js + qbr nucleus, not beside it as a separate silo. Normalize data contracts, auth/permissions, storage, and telemetry; then attach as a service, plugin, canvas layer, trainer, or analysis module. Descending combination order: tao-yu/Alg-Trainer, poliva/cubedex, Lykos/cube_trainer.","Repurpose here means: turn it into a trainer engine, solver/timer backend, recognition drill module, or method-specific practice mode for HyperTwist.",Map module boundaries; Identify hidden reusable internals; Define adapter/API boundary to target anchors; Write extraction tests against upstream behavior; Extract collectors/adapters; Normalize topology/config schema; Bridge into control-plane API,deep source audit,"Hidden value usually sits in service topology schemas, collector agents, auth/integration adapters, caching, deployment abstractions, and metrics/event correlation.",Inspect topology/service schema; collectors/agents; auth/integration adapters; caching/state sync; deployment/runtime abstractions; metrics/event correlation; config layering.,"Inspect package manifests, README/docs, src tree, examples, tests, CI workflows, config files, migrations/schemas, and hidden feature flags or experimental modules. Look for algorithm databases, spaced-repetition logic, scramble generation, timer/stat code, virtual cube components, smartcube adapters, and custom-trainer configuration support.","Audit roice3/MagicTile as a infra / runtime / observability / integration candidate for HyperTwist. Do not stop at README-level features. Inspect: Inspect topology/service schema; collectors/agents; auth/integration adapters; caching/state sync; deployment/runtime abstractions; metrics/event correlation; config layering. Decide whether the best extraction path is moderate modification and whether it belongs as subsystem donor / integration utility. Test the three merger paths in order: 1) project-local anchor [base + donor]; 2) shared portfolio utility [augmenter]; 3) cross-project transfer candidate [future merger]. Return hidden modules, reusable schemas, protocol layers, plugin hooks, render/state models, datasets/test fixtures, and any subsystem stronger than the visible product shell.",project-local anchor,base + donor,Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.,shared portfolio utility,augmenter,Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.,cross-project transfer candidate,future merger,Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.,project-local first,"Cross-project transfer is possible, but the value is clearest inside the assigned project until source audit exposes more reusable primitives.","exclude from core, keep as donor","Do not let it consume roadmap as a full product shell; mine reusable engines, adapters, schemas, UX patterns, or datasets.",medium-low,single-source signal; clear taxonomy; mostly donor/reference role,medium,explicit bookmark description available,"Licensing intentionally ignored as a decision filter in this canonical evaluation; assess only architecture, capability, donor value, and concept transfer.",HyperTwist(1),HyperTwist Consider,Non-euclidean Rubik's Cube Analogues,,"roice3/MagicTile is treated as repurpose for HyperTwist because visible metadata points to the cubing / algorithm training layer. Surface signal: Non-euclidean Rubik's Cube Analogues The fit looks real, but more as a donor/augmenter than as a standalone foundation.",bookmarks,True,False,1.0,0.0,HT_hyper_engine,HT_hyper_engine_0007,cubing / algorithm training,"Integrate primarily for HyperTwist. Its description and bookmark placement under ""HyperTwist Consider"" place it in the cubing / algorithm training layer.",HyperTwist,cubing / algorithm training,integrate,moderate modification,medium,roice3/magictile,HyperTwist,,,,,,,,,,,,,,,,Original global operational v3 retained,MIT,known_from_reference_material,uploaded_reference_docs,no,,,,Supplemental intake references are advisory only; v6 adjudication remains the source of truth.,Usually indirect,yes,v6 unified all-project source-of-truth pack,v5_carry_forward,,36.0,5,88.0,Locked Strategic Donor,Top-tier non-Euclidean geometry and topology donor,,P1,permissive_or_noncopyleft_known,direct_incorporation_ok,The repo is MIT and is explicitly retained as a top-tier geometry/topology donor. Direct donor use is legally straightforward if the architecture benefits from it.,Direct donor use or bounded adapter extraction are both acceptable; choose the seam that best preserves the topology and twist infrastructure.,Preserve MIT notices and attribution where required.,Usually unnecessary unless later replacing a narrow seam is cleaner than carrying the upstream code.,high,permissive-top-tier-donor,yes,,,,,,,,,,,,,v6.3_final_source_of_truth,Assigned from legacy HY_misc to HT_hyper_engine during cluster normalization on 2026-04-25.,implemented_live_permissive,landed_permissive_preserve,"Phase 3R-E closed. Preserve as the landed first-party embodied companion, narration, lip-sync, gesture, subtitle, and avatar-embed lane; start future widening from the live-lane audit, then the 3R-E implementation packet, then REPO_LICENSE_TRACKING.md." 11967,PostHog/posthog,https://github.com/PostHog/posthog,HyperTwist,41.0,72.0,81.0,C,telemetry / replay / feature governance,subsystem donor,telemetry donor,donor bench,repurpose,moderate modification,"Retain the valuable internal engine, but expect to replace UI/product shell, adapt schemas/APIs, and refactor boundaries so it can plug into the target anchors cleanly. For this repo class, that usually means preserving calibration/detection/state-reconstruction logic while replacing camera UX and integration surfaces.","🦔 PostHog is an all-in-one developer platform for building successful products. We offer product analytics, web analytics, session replay, error tracking, feature flags, experimentation, surveys, data warehouse, a CDP, and an AI product ...","Repurpose selected subsystems rather than the whole product. Mine the repo for telemetry and event schemas, replay diagnostics, replay query surfaces, feature-flag governance, activity logs, and product/service boundary patterns; keep what materially shortens build time, but rebind data contracts, permissions, storage, and deployment to the HyperTwist architecture. Best first pairing order: HactarCE/Hyperspeedcube, cubing/cubing.js, kkoomen/qbr.","Consolidate under the Hyperspeedcube + cubing.js + qbr nucleus, not beside it as a separate silo. Normalize data contracts, auth/permissions, storage, and telemetry; then attach as a service, plugin, canvas layer, trainer, or analysis module. Descending combination order: HactarCE/Hyperspeedcube, cubing/cubing.js, kkoomen/qbr.","Repurpose here means: turn it into a telemetry spine, replay diagnostics donor, feature-governance donor, or control-plane integration layer.",Map module boundaries; Identify hidden reusable internals; Define adapter/API boundary to target anchors; Write extraction tests against upstream behavior; Benchmark calibration pipeline; Extract state reconstruction; Wrap with camera/AR adapter,deep source audit,"Hidden value often sits in calibration, preprocessing, stabilization, object/state reconstruction, replay artifacts, and camera-to-domain state pipelines that are not obvious from demos.","Inspect replay routes and deep links; replay diagnostics; feature-flag CRUD, dependencies, and evaluation; telemetry and event schemas; product and service boundaries; MIT versus ee path splits.","Inspect package manifests, README/docs, product slices, services, tests, migrations/schemas, and hidden feature flags or experimental modules. Look for replay diagnostics, replay query surfaces, feature-flag governance, activity logs, event schemas, service boundaries, and MIT versus ee/ path splits.","Audit PostHog/posthog as a telemetry / replay / feature-governance candidate for HyperTwist. Do not stop at README-level features. Inspect: replay routes and deep links, replay diagnostics, feature-flag CRUD/dependencies/evaluation, telemetry and event schemas, product/service boundaries, and MIT versus ee/ path splits. Decide whether the best extraction path remains moderate modification and which seams should stay bounded due mixed licensing or mission misfit. Return hidden modules, reusable schemas, protocol layers, plugin hooks, replay/debugging surfaces, and any subsystem stronger than the visible product shell.",kkoomen/qbr,foundation + perception donor,"Use this repo against the partner as an augmenting layer; preserve the partner as the likely base and mine this repo for capabilities that improve breadth, UX, or specialization.",vivaansinghvi07/rubix-cube-solver,perception + replay donor,Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.,cubing/cubing.js,state/render backend,Use the partner for canonical state or rendering abstractions and merge this repo's specialized logic on top.,VectorShell | ScriptoriumAI,VectorShell can borrow spatial/rendering and perception primitives; ScriptoriumAI can borrow tutorial/educational visualization patterns rather than the full engine.,"exclude from core, keep as donor","Do not let it consume roadmap as a full product shell; mine reusable engines, adapters, schemas, UX patterns, or datasets.",medium-low,single-source signal; clear taxonomy; mostly donor/reference role,medium,explicit bookmark description available,"Licensing intentionally ignored as a decision filter in this canonical evaluation; assess only architecture, capability, donor value, and concept transfer.",HyperTwist(1),HyperTwist Consider,"🦔 PostHog is an all-in-one developer platform for building successful products. We offer product analytics, web analytics, session replay, error tracking, feature flags, experimentation, surveys, data warehouse, a CDP, and an AI product assistant to help debug your code, ship features faster, and keep all your usage and customer data in one stack.",,"PostHog/posthog is treated as repurpose for HyperTwist because visible metadata points to the cloud / infra / observability / api layer. Surface signal: 🦔 PostHog is an all-in-one developer platform for building successful products. We offer product analytics, web analytics, session replay, error tracking, feature flags, experimentation, surveys, data warehouse, a CDP, and an AI product ... The fit looks real, but more as a donor/augmenter than as a standalone foundation.",bookmarks,True,False,1.0,0.0,HT_control_plane,HT_control_plane_0001,cloud / infra / observability / api,"Repurpose selectively for HyperTwist. Its visible platform signal and source audit place it in telemetry, replay, and feature-governance rather than computer vision or AR.",HyperTwist,telemetry / replay / feature governance,repurpose,moderate modification,medium,posthog/posthog,HyperTwist,,,,,,,,,,,,,,,,Original global operational v3 retained,MIT outside ee/; enterprise-restricted in ee/,known_from_reference_material,uploaded_reference_docs,no,,,,Supplemental intake references are advisory only; v6 adjudication remains the source of truth.,Usually indirect,yes,v6 unified all-project source-of-truth pack,v5_carry_forward,,41.0,5,72.0,,Telemetry / replay / feature-governance donor,,,mixed_or_boundary_sensitive_known,bounded_sidecar_or_selective_reimplementation,"The repo is mixed-license: MIT outside ee/ and enterprise-restricted inside ee/. Use only clearly MIT paths as bounded telemetry, replay, and feature-governance donor material, and exclude or reimplement enterprise-gated paths.","Use only clearly MIT paths outside ee/ as bounded telemetry, replay, and feature-governance donor surfaces; exclude enterprise paths or reimplement equivalent seams.",Keep MIT notices for reused paths and do not incorporate ee/ without separate commercial rights; verify path provenance before shipping.,"Sometimes useful for enterprise-gated or off-mission slices, but not required for clearly MIT paths.",high,mixed-license-path-review-required,no,,,,,,,,,,,,,v6.3_final_source_of_truth,Assigned to HT_control_plane and normalized telemetry/replay/feature-governance wording on 2026-04-25.,selected_not_live_boundary_sensitive,phase0r_boundary_sensitive_eval_then_adapter_or_sidecar,Phase 1R closed. Retain as a Phase 4R bounded telemetry and replay sidecar candidate; keep ee/ excluded and use explicit allowlists or first-party reimplementation where needed. -,met4citizen/TalkingHead,https://github.com/met4citizen/TalkingHead,HyperTwist,,,,,interface / visualization / shell surface,subsystem donor,interface donor,donor bench,repurpose,moderate modification,"Retain the reusable avatar, lip-sync, and retargeting layers, but replace the demo shell, asset assumptions, and voice-service integration with HyperTwist-owned surfaces.",,"Repurpose selected subsystems rather than the whole product. Mine the repo for embodied coach avatar runtime, lip-sync and subtitle timing, avatar-only embedding, retargeting, and streamed speech playback; keep what shortens build time, but rebind assets, voice services, and UI shell to the HyperTwist architecture.",,Repurpose here means: turn it into a browser-side embodied coach or companion layer.,,,,Inspect talkinghead runtime; speech queueing and streaming; viseme and blendshape flow; avatarOnly embedding; retargeting; and audio worklet behavior.,"Inspect modules, examples, tests, site config, streaming demos, retargeter, and playback worklet code. Look for embodied-coach embedding, lip-sync, subtitle timing, gesture and expression surfaces, and asset assumptions.","Audit met4citizen/TalkingHead as a browser embodied-coach candidate for HyperTwist. Inspect the avatar runtime, streaming lip-sync, subtitle timing, avatarOnly embedding, retargeting, and audio worklet behavior. Decide which seams can be used directly and which must remain bounded behind the HyperTwist coaching shell.",,,,,,,,,,,,,,medium,"Canonized Markdown dossier exists and the repo has been source-backed, but CSV backfill is later than the original v6.3 board generation.",medium,Source-backed dossier exists and the repo has been reconciled into the later Markdown authority stack.,,,,,,,,,,,,HT_browser_surface,HT_browser_surface_0001,browser / 3D / XR / presentation,"Repurpose selectively for HyperTwist. Its source-backed role is an embodied coach and companion presentation donor, not a generic avatar product shell.",HyperTwist,browser / 3D / XR / presentation,repurpose,moderate modification,medium,met4citizen/talkinghead,,,,,,,,,,,,,,,,,,MIT,known_from_reference_material,uploaded_reference_docs,,,,,,,,,,,,,,Donor Bench,Browser embodied coach surface,Included,P2,permissive_or_noncopyleft_known,direct_incorporation_ok,The code license is MIT and direct use is allowed. Treat it as a bounded browser-side donor for embodied coach presentation rather than as a product shell.,"Use directly as a bounded browser-side dependency or adapter layer; keep voice services, product logic, and asset provenance outside the upstream shell.","Typically preserve notices, attribution, and license text where required; review sample avatars or media separately from the code license.",Usually unnecessary unless you later replace a narrow upstream layer for product-shaping reasons.,high,standard-notice-review,yes,,,,,,,,,,,,,v6.3_markdown_backfill,Backfilled from canonized Markdown dossier pass on 2026-04-24.,selected_not_live_permissive_candidate,phase0r_permissive_eval_then_implement,"Phase 1R closed. Retain as a Phase 3R permissive implementation candidate; implement only from its packet authority and the retained-set contract, not by reopening Phase 0R." -,apache/echarts,https://github.com/apache/echarts,HyperTwist,,,,,analytics / visualization / reporting,subsystem donor,interface donor,donor bench,repurpose,moderate modification,"Retain the reusable chart runtime and reporting patterns, but keep HyperTwist domain schemas, page shell, and training logic outside the upstream system.",,"Repurpose selected subsystems rather than the whole product. Mine the repo for chart runtime, option and data-store patterns, export and save-as-image behavior, zoom and history handling, and SSR reporting surfaces; keep what shortens build time, but rebind analytics schemas and application shell to the HyperTwist architecture.",,"Repurpose here means: turn it into a bounded browser analytics and reporting layer for dashboards, replay summaries, and coaching views.",,,,"Inspect OptionManager, DataStore, zoom and history behavior, thumbnail and export features, SSR and hydration seams, and accessibility surface.","Inspect manifests, README/docs, src core, model, data, component, export, and SSR folders. Look for modular chart runtime, data-store abstractions, export surfaces, and reporting-specific UI behavior.","Audit apache/echarts as a browser analytics and reporting candidate for HyperTwist. Inspect the modular chart runtime, OptionManager and DataStore, export surfaces, zoom and history behavior, SSR path, and accessibility seams. Decide which parts should remain direct dependencies versus concept-only references.",,,,,,,,,,,,,,medium,"Canonized Markdown dossier exists and the repo has been source-backed, but CSV backfill is later than the original v6.3 board generation.",medium,Source-backed dossier exists and the repo has been reconciled into the later Markdown authority stack.,,,,,,,,,,,,HT_browser_surface,HT_browser_surface_0002,analytics / visualization / reporting,Repurpose selectively for HyperTwist. Its source-backed role is a bounded analytics and reporting donor rather than a generic dashboard widget.,HyperTwist,analytics / visualization / reporting,repurpose,moderate modification,medium,apache/echarts,,,,,,,,,,,,,,,,,,Apache-2.0,known_from_reference_material,uploaded_reference_docs,,,,,,,,,,,,,,Donor Bench,Browser analytics and reporting surface,Included,P2,permissive_or_noncopyleft_known,direct_incorporation_ok,The code license is Apache-2.0 and direct use is allowed. Treat it as a bounded reporting and analytics donor.,Use directly as a bounded browser analytics dependency; keep HyperTwist data contracts and product logic outside the upstream shell.,Preserve LICENSE and NOTICE materials where required and review redistributed assets separately from the code license.,Usually unnecessary unless you later replace a narrow upstream layer for product-shaping reasons.,high,notice-file-review,yes,,,,,,,,,,,,,v6.3_markdown_backfill,Backfilled from canonized Markdown dossier pass on 2026-04-24.,selected_not_live_permissive_candidate,phase0r_permissive_eval_then_implement,"Phase 1R closed. Retain as a Phase 3R permissive implementation candidate; implement only from its packet authority and the retained-set contract, not by reopening Phase 0R." -,ecomfe/echarts-gl,https://github.com/ecomfe/echarts-gl,HyperTwist,,,,,interface / visualization / shell surface,subsystem donor,visualization donor,merge bench,integrate,moderate modification,"Retain selective 3D analytics surfaces, but keep HyperTwist domain models, scene ownership, and broader product shell outside the upstream package.",,"Integrate selected subsystems rather than the whole product. Mine the repo for 3D analytics and explainer surfaces, GL layer mounting, and view helper behavior; keep what shortens build time, but bind it to HyperTwist analytics schemas and browser companion UI.",,Integrate here means: merge bounded 3D analytics and explainer surfaces into the browser reporting stack.,,,,"Inspect 3D and GL chart exports, GL layer mounting, graph and flow surfaces, view helper behavior, and chart-space interaction handling.","Inspect manifests, README/docs, src chart and component exports, GL helper modules, and integration points with echarts and zrender.","Audit ecomfe/echarts-gl as a browser 3D analytics companion to apache/echarts. Inspect the 3D chart exports, GL view handling, and interaction seams. Decide which pieces deserve direct dependency use versus conceptual guidance only.",,,,,,,,,,,,,,medium,"Canonized Markdown dossier exists and the repo has been source-backed, but CSV backfill is later than the original v6.3 board generation.",medium,Source-backed dossier exists and the repo has been reconciled into the later Markdown authority stack.,,,,,,,,,,,,HT_browser_surface,HT_browser_surface_0003,browser / 3D / XR / presentation,Integrate selectively for HyperTwist. Its source-backed role is a 3D analytics and explainer extension beneath echarts rather than a standalone simulation lane.,HyperTwist,browser / 3D / XR / presentation,integrate,moderate modification,medium,ecomfe/echarts-gl,,,,,,,,,,,,,,,,,,BSD-3-Clause,known_from_reference_material,uploaded_reference_docs,,,,,,,,,,,,,,Merge Bench,Browser 3D analytics and explainer surface,Included,P3,permissive_or_noncopyleft_known,direct_incorporation_ok,The code license is BSD-3-Clause and direct use is allowed. Treat it as a bounded 3D analytics extension rather than a runtime foundation.,Use directly as a bounded browser-side dependency beneath the reporting stack; keep HyperTwist scene ownership and product logic outside the upstream shell.,"Typically preserve notices, attribution, and license text where required.",Usually unnecessary unless you later replace a narrow upstream layer for product-shaping reasons.,high,standard-notice-review,yes,,,,,,,,,,,,,v6.3_markdown_backfill,Backfilled from canonized Markdown dossier pass on 2026-04-24.,selected_not_live_permissive_candidate,phase0r_permissive_eval_then_implement,"Phase 1R closed. Retain as a Phase 3R permissive implementation candidate; implement only from its packet authority and the retained-set contract, not by reopening Phase 0R." +,met4citizen/TalkingHead,https://github.com/met4citizen/TalkingHead,HyperTwist,,,,,interface / visualization / shell surface,subsystem donor,interface donor,donor bench,repurpose,moderate modification,"Retain the reusable avatar, lip-sync, and retargeting layers, but replace the demo shell, asset assumptions, and voice-service integration with HyperTwist-owned surfaces.",,"Repurpose selected subsystems rather than the whole product. Mine the repo for embodied coach avatar runtime, lip-sync and subtitle timing, avatar-only embedding, retargeting, and streamed speech playback; keep what shortens build time, but rebind assets, voice services, and UI shell to the HyperTwist architecture.",,Repurpose here means: turn it into a browser-side embodied coach or companion layer.,,,,Inspect talkinghead runtime; speech queueing and streaming; viseme and blendshape flow; avatarOnly embedding; retargeting; and audio worklet behavior.,"Inspect modules, examples, tests, site config, streaming demos, retargeter, and playback worklet code. Look for embodied-coach embedding, lip-sync, subtitle timing, gesture and expression surfaces, and asset assumptions.","Audit met4citizen/TalkingHead as a browser embodied-coach candidate for HyperTwist. Inspect the avatar runtime, streaming lip-sync, subtitle timing, avatarOnly embedding, retargeting, and audio worklet behavior. Decide which seams can be used directly and which must remain bounded behind the HyperTwist coaching shell.",,,,,,,,,,,,,,medium,"Canonized Markdown dossier exists and the repo has been source-backed, but CSV backfill is later than the original v6.3 board generation.",medium,Source-backed dossier exists and the repo has been reconciled into the later Markdown authority stack.,,,,,,,,,,,,HT_browser_surface,HT_browser_surface_0001,browser / 3D / XR / presentation,"Repurpose selectively for HyperTwist. Its source-backed role is an embodied coach and companion presentation donor, not a generic avatar product shell.",HyperTwist,browser / 3D / XR / presentation,repurpose,moderate modification,medium,met4citizen/talkinghead,,,,,,,,,,,,,,,,,,MIT,known_from_reference_material,uploaded_reference_docs,,,,,,,,,,,,,,Donor Bench,Browser embodied coach surface,Included,P2,permissive_or_noncopyleft_known,direct_incorporation_ok,The code license is MIT and direct use is allowed. Treat it as a bounded browser-side donor for embodied coach presentation rather than as a product shell.,"Use directly as a bounded browser-side dependency or adapter layer; keep voice services, product logic, and asset provenance outside the upstream shell.","Typically preserve notices, attribution, and license text where required; review sample avatars or media separately from the code license.",Usually unnecessary unless you later replace a narrow upstream layer for product-shaping reasons.,high,standard-notice-review,yes,,,,,,,,,,,,,v6.3_markdown_backfill,Backfilled from canonized Markdown dossier pass on 2026-04-24.,implemented_live_permissive,landed_permissive_preserve,"Phase 3R-E closed. Preserve as the landed first-party embodied companion, narration, lip-sync, gesture, subtitle, and avatar-embed lane; start future widening from the live-lane audit, then the 3R-E implementation packet, then REPO_LICENSE_TRACKING.md." +,apache/echarts,https://github.com/apache/echarts,HyperTwist,,,,,analytics / visualization / reporting,subsystem donor,interface donor,donor bench,repurpose,moderate modification,"Retain the reusable chart runtime and reporting patterns, but keep HyperTwist domain schemas, page shell, and training logic outside the upstream system.",,"Repurpose selected subsystems rather than the whole product. Mine the repo for chart runtime, option and data-store patterns, export and save-as-image behavior, zoom and history handling, and SSR reporting surfaces; keep what shortens build time, but rebind analytics schemas and application shell to the HyperTwist architecture.",,"Repurpose here means: turn it into a bounded browser analytics and reporting layer for dashboards, replay summaries, and coaching views.",,,,"Inspect OptionManager, DataStore, zoom and history behavior, thumbnail and export features, SSR and hydration seams, and accessibility surface.","Inspect manifests, README/docs, src core, model, data, component, export, and SSR folders. Look for modular chart runtime, data-store abstractions, export surfaces, and reporting-specific UI behavior.","Audit apache/echarts as a browser analytics and reporting candidate for HyperTwist. Inspect the modular chart runtime, OptionManager and DataStore, export surfaces, zoom and history behavior, SSR path, and accessibility seams. Decide which parts should remain direct dependencies versus concept-only references.",,,,,,,,,,,,,,medium,"Canonized Markdown dossier exists and the repo has been source-backed, but CSV backfill is later than the original v6.3 board generation.",medium,Source-backed dossier exists and the repo has been reconciled into the later Markdown authority stack.,,,,,,,,,,,,HT_browser_surface,HT_browser_surface_0002,analytics / visualization / reporting,Repurpose selectively for HyperTwist. Its source-backed role is a bounded analytics and reporting donor rather than a generic dashboard widget.,HyperTwist,analytics / visualization / reporting,repurpose,moderate modification,medium,apache/echarts,,,,,,,,,,,,,,,,,,Apache-2.0,known_from_reference_material,uploaded_reference_docs,,,,,,,,,,,,,,Donor Bench,Browser analytics and reporting surface,Included,P2,permissive_or_noncopyleft_known,direct_incorporation_ok,The code license is Apache-2.0 and direct use is allowed. Treat it as a bounded reporting and analytics donor.,Use directly as a bounded browser analytics dependency; keep HyperTwist data contracts and product logic outside the upstream shell.,Preserve LICENSE and NOTICE materials where required and review redistributed assets separately from the code license.,Usually unnecessary unless you later replace a narrow upstream layer for product-shaping reasons.,high,notice-file-review,yes,,,,,,,,,,,,,v6.3_markdown_backfill,Backfilled from canonized Markdown dossier pass on 2026-04-24.,implemented_live_permissive,landed_permissive_preserve,"Phase 3R-E closed. Preserve as the landed first-party embodied companion, narration, lip-sync, gesture, subtitle, and avatar-embed lane; start future widening from the live-lane audit, then the 3R-E implementation packet, then REPO_LICENSE_TRACKING.md." +,ecomfe/echarts-gl,https://github.com/ecomfe/echarts-gl,HyperTwist,,,,,interface / visualization / shell surface,subsystem donor,visualization donor,merge bench,integrate,moderate modification,"Retain selective 3D analytics surfaces, but keep HyperTwist domain models, scene ownership, and broader product shell outside the upstream package.",,"Integrate selected subsystems rather than the whole product. Mine the repo for 3D analytics and explainer surfaces, GL layer mounting, and view helper behavior; keep what shortens build time, but bind it to HyperTwist analytics schemas and browser companion UI.",,Integrate here means: merge bounded 3D analytics and explainer surfaces into the browser reporting stack.,,,,"Inspect 3D and GL chart exports, GL layer mounting, graph and flow surfaces, view helper behavior, and chart-space interaction handling.","Inspect manifests, README/docs, src chart and component exports, GL helper modules, and integration points with echarts and zrender.","Audit ecomfe/echarts-gl as a browser 3D analytics companion to apache/echarts. Inspect the 3D chart exports, GL view handling, and interaction seams. Decide which pieces deserve direct dependency use versus conceptual guidance only.",,,,,,,,,,,,,,medium,"Canonized Markdown dossier exists and the repo has been source-backed, but CSV backfill is later than the original v6.3 board generation.",medium,Source-backed dossier exists and the repo has been reconciled into the later Markdown authority stack.,,,,,,,,,,,,HT_browser_surface,HT_browser_surface_0003,browser / 3D / XR / presentation,Integrate selectively for HyperTwist. Its source-backed role is a 3D analytics and explainer extension beneath echarts rather than a standalone simulation lane.,HyperTwist,browser / 3D / XR / presentation,integrate,moderate modification,medium,ecomfe/echarts-gl,,,,,,,,,,,,,,,,,,BSD-3-Clause,known_from_reference_material,uploaded_reference_docs,,,,,,,,,,,,,,Merge Bench,Browser 3D analytics and explainer surface,Included,P3,permissive_or_noncopyleft_known,direct_incorporation_ok,The code license is BSD-3-Clause and direct use is allowed. Treat it as a bounded 3D analytics extension rather than a runtime foundation.,Use directly as a bounded browser-side dependency beneath the reporting stack; keep HyperTwist scene ownership and product logic outside the upstream shell.,"Typically preserve notices, attribution, and license text where required.",Usually unnecessary unless you later replace a narrow upstream layer for product-shaping reasons.,high,standard-notice-review,yes,,,,,,,,,,,,,v6.3_markdown_backfill,Backfilled from canonized Markdown dossier pass on 2026-04-24.,implemented_live_permissive,landed_permissive_preserve,"Phase 3R-E closed. Preserve as the landed first-party embodied companion, narration, lip-sync, gesture, subtitle, and avatar-embed lane; start future widening from the live-lane audit, then the 3R-E implementation packet, then REPO_LICENSE_TRACKING.md." ,KhronosGroup/glTF-Sample-Viewer,https://github.com/KhronosGroup/glTF-Sample-Viewer,HyperTwist,,,,,interface / visualization / shell surface,subsystem donor,viewer donor,donor bench,repurpose,moderate modification,"Retain the useful asset-validation and viewer surfaces, but keep HyperTwist asset flows, editor shell, and product logic outside the upstream viewer.",,"Repurpose selected subsystems rather than the whole product. Mine the repo for standards-aware asset preview, validation, capture, environment control, and viewer-shell behavior; keep what shortens build time, but bind it to HyperTwist asset tooling and browser companion surfaces.",,Repurpose here means: turn it into a bounded asset-validation and preview donor for browser tooling.,,,,"Inspect validator integration, material-variant support, environment and tone-mapping controls, capture behavior, and the relationship to glTF-Sample-Renderer.","Inspect manifests, README/docs, src main and UI logic, bundled renderer submodule, and validation-related surfaces.","Audit KhronosGroup/glTF-Sample-Viewer as a browser asset-validation and inspection candidate for HyperTwist. Inspect validator integration, capture flow, material variants, environment controls, and the renderer handoff. Decide which surfaces deserve direct use or selective extraction.",,,,,,,,,,,,,,medium,"Canonized Markdown dossier exists and the repo has been source-backed, but CSV backfill is later than the original v6.3 board generation.",medium,Source-backed dossier exists and the repo has been reconciled into the later Markdown authority stack.,,,,,,,,,,,,HT_browser_surface,HT_browser_surface_0004,browser / 3D / XR / presentation,Repurpose selectively for HyperTwist. Its source-backed role is a bounded asset-validation and standards-viewer donor rather than a runtime foundation.,HyperTwist,browser / 3D / XR / presentation,repurpose,moderate modification,medium,khronosgroup/gltf-sample-viewer,,,,,,,,,,,,,,,,,,Apache-2.0,known_from_reference_material,uploaded_reference_docs,,,,,,,,,,,,,,Donor Bench,Browser asset validation and viewer surface,Included,P3,permissive_or_noncopyleft_known,direct_incorporation_ok,The code license is Apache-2.0 and direct use is allowed. Treat it as a bounded standards-viewer and asset-QA donor.,Use directly as a bounded asset-validation dependency or sidecar; keep HyperTwist asset workflows and product logic outside the upstream viewer shell.,Preserve LICENSE and NOTICE materials where required.,Usually unnecessary unless you later replace a narrow upstream layer for product-shaping reasons.,high,notice-file-review,yes,,,,,,,,,,,,,v6.3_markdown_backfill,Backfilled from canonized Markdown dossier pass on 2026-04-24.,selected_not_live_permissive_candidate,phase0r_permissive_eval_then_implement,"Phase 3R-D closed for the anchor. Retain as the subordinate standards-aware asset QA and validation sidecar beneath the landed google/model-viewer lane; do not treat it as separately live." ,google/model-viewer,https://github.com/google/model-viewer,HyperTwist,,,,,interface / visualization / shell surface,subsystem donor,viewer donor,donor bench,repurpose,moderate modification,"Retain the useful browser presentation and inspection layers, but keep HyperTwist product logic, page shell, and owned runtime direction outside the upstream project.",,"Repurpose selected subsystems rather than the whole product. Mine the repo for browser 3D presentation, annotations, inspection, snippet and export behavior, hotspot editing, and fidelity tooling; keep what shortens build time, but bind it to HyperTwist browser companion surfaces and asset workflows.",,"Repurpose here means: turn it into a bounded browser 3D presentation, inspection, and editor donor.",,,,"Inspect model-viewer runtime mixins, annotation and AR behavior, scene-graph access, space-opera editor surfaces, and render-fidelity support.","Inspect manifests, README/docs, packages/model-viewer runtime, space-opera, render-fidelity-tools, model-viewer-effects, and docs/example surfaces.","Audit google/model-viewer as a browser 3D presentation and inspection candidate for HyperTwist. Inspect the custom element runtime, annotation and AR behavior, scene-graph access, bundled editor and fidelity packages, and docs/demo tooling. Decide which surfaces merit direct use versus selective extraction.",,,,,,,,,,,,,,medium,"Canonized Markdown dossier exists and the repo has been source-backed, but CSV backfill is later than the original v6.3 board generation.",medium,Source-backed dossier exists and the repo has been reconciled into the later Markdown authority stack.,,,,,,,,,,,,HT_browser_surface,HT_browser_surface_0005,browser / 3D / XR / presentation,Repurpose selectively for HyperTwist. Its source-backed role is a bounded browser 3D presentation and inspection donor rather than a runtime foundation.,HyperTwist,browser / 3D / XR / presentation,repurpose,moderate modification,medium,google/model-viewer,,,,,,,,,,,,,,,,,,Apache-2.0,known_from_reference_material,uploaded_reference_docs,,,,,,,,,,,,,,Donor Bench,Browser 3D presentation and inspection surface,Included,P2,permissive_or_noncopyleft_known,direct_incorporation_ok,The code license is Apache-2.0 and direct use is allowed. Treat it as a bounded browser presentation and inspection donor.,"Use directly as a bounded browser-side dependency or adapter layer; keep HyperTwist runtime ownership, asset workflows, and product logic outside the upstream shell.",Preserve LICENSE and NOTICE materials where required and review bundled assets separately from the code license.,Usually unnecessary unless you later replace a narrow upstream layer for product-shaping reasons.,high,notice-file-review,yes,,,,,,,,,,,,,v6.3_markdown_backfill,Backfilled from canonized Markdown dossier pass on 2026-04-24.,implemented_live_permissive,landed_permissive_preserve,"Phase 3R-D closed. Preserve as the landed first-party browser presentation, compact editor, and standards-aware asset-QA lane; start future widening from the live-lane audit, then the 3R-D implementation packet, then REPO_LICENSE_TRACKING.md." -,mrdoob/three.js,https://github.com/mrdoob/three.js,HyperTwist,,,,,interface / visualization / shell surface,subsystem donor,dependency donor,donor bench,repurpose,moderate modification,Retain it mainly as a dependency substrate. Do not treat it as the owned gameplay foundation or let it reshape the Unreal-first runtime direction.,,"Repurpose selected subsystems rather than the whole product. Mine the repo for the browser 3D substrate, loader and exporter behavior, WebXR runtime hooks, and utility layers; keep what shortens build time, but leave HyperTwist gameplay and owned runtime direction outside the upstream engine.",,Repurpose here means: use it as the bounded browser-side 3D substrate and keep HyperTwist product logic above it.,,,,"Inspect core renderer and scene stack, loaders and exporters, WebXR manager, addons surface, and editor shell.","Inspect manifests, README/docs, src core and renderer folders, WebXR manager, addons, examples references, and editor shell.","Audit mrdoob/three.js as the browser 3D substrate beneath HyperTwist companion surfaces. Inspect renderer, scene, camera, math, loader, WebXR, and editor behavior. Decide what should be used directly as dependency substrate versus what should remain conceptual.",,,,,,,,,,,,,,medium,"Canonized Markdown dossier exists and the repo has been source-backed, but CSV backfill is later than the original v6.3 board generation.",medium,Source-backed dossier exists and the repo has been reconciled into the later Markdown authority stack.,,,,,,,,,,,,HT_browser_surface,HT_browser_surface_0006,browser / 3D / XR / presentation,"Repurpose selectively for HyperTwist. Its source-backed role is the commodity browser 3D substrate beneath the browser companion stack, not the owned runtime foundation.",HyperTwist,browser / 3D / XR / presentation,repurpose,moderate modification,medium,mrdoob/three.js,,,,,,,,,,,,,,,,,,MIT,known_from_reference_material,uploaded_reference_docs,,,,,,,,,,,,,,Donor Bench,Browser 3D substrate,Included,P2,permissive_or_noncopyleft_known,direct_incorporation_ok,The code license is MIT and direct use is allowed. Treat it as a bounded browser 3D substrate rather than as an owned runtime foundation.,"Use directly as a bounded browser-side dependency; keep HyperTwist gameplay, puzzle logic, and owned runtime direction outside the upstream engine.","Typically preserve notices, attribution, and license text where required.",Usually unnecessary unless you later replace a narrow upstream layer for product-shaping reasons.,high,standard-notice-review,yes,,,,,,,,,,,,,v6.3_markdown_backfill,Backfilled from canonized Markdown dossier pass on 2026-04-24.,selected_not_live_permissive_candidate,phase0r_permissive_eval_then_implement,"Phase 1R closed. Retain as a Phase 3R permissive implementation candidate; implement only from its packet authority and the retained-set contract, not by reopening Phase 0R." -,pmndrs/postprocessing,https://github.com/pmndrs/postprocessing,HyperTwist,,,,,interface / visualization / shell surface,subsystem donor,dependency donor,merge bench,integrate,moderate modification,"Retain selective effect infrastructure, but keep HyperTwist scene ownership, domain logic, and product shell outside the upstream package.",,"Integrate selected subsystems rather than the whole product. Mine the repo for effect-composer, outline, SSAO, and bounded browser emphasis behavior; keep what shortens build time, but bind it to HyperTwist browser viewers and coach surfaces.",,Integrate here means: merge bounded browser-side effect and emphasis infrastructure into the companion stack.,,,,"Inspect EffectComposer and EffectPass, outline and SSAO effect behavior, effect catalog breadth, and performance assumptions.","Inspect manifests, README/docs, core composer and pass code, major effects, and integration seams with three.js.","Audit pmndrs/postprocessing as a bounded browser post-processing substrate for HyperTwist. Inspect composer, pass, outline, and SSAO behavior and decide what should remain direct dependency use versus conceptual reference.",,,,,,,,,,,,,,medium,"Canonized Markdown dossier exists and the repo has been source-backed, but CSV backfill is later than the original v6.3 board generation.",medium,Source-backed dossier exists and the repo has been reconciled into the later Markdown authority stack.,,,,,,,,,,,,HT_browser_surface,HT_browser_surface_0007,browser / 3D / XR / presentation,Integrate selectively for HyperTwist. Its source-backed role is a bounded browser post-processing substrate beneath three.js rather than a product lane.,HyperTwist,browser / 3D / XR / presentation,integrate,moderate modification,medium,pmndrs/postprocessing,,,,,,,,,,,,,,,,,,Zlib,known_from_reference_material,uploaded_reference_docs,,,,,,,,,,,,,,Merge Bench,Browser post-processing substrate,Included,P3,permissive_or_noncopyleft_known,direct_incorporation_ok,The code license is Zlib and direct use is allowed. Treat it as a bounded browser post-processing dependency.,Use directly as a bounded browser-side dependency beneath three.js-based viewers; keep HyperTwist product logic outside the upstream package.,"Typically preserve notices, attribution, and license text where required.",Usually unnecessary unless you later replace a narrow upstream layer for product-shaping reasons.,high,standard-notice-review,yes,,,,,,,,,,,,,v6.3_markdown_backfill,Backfilled from canonized Markdown dossier pass on 2026-04-24.,selected_not_live_permissive_candidate,phase0r_permissive_eval_then_implement,"Phase 1R closed. Retain as a Phase 3R permissive implementation candidate; implement only from its packet authority and the retained-set contract, not by reopening Phase 0R." -,pmndrs/react-three-fiber,https://github.com/pmndrs/react-three-fiber,HyperTwist,,,,,interface / visualization / shell surface,subsystem donor,dependency donor,donor bench,repurpose,moderate modification,"Retain it mainly as a dependency substrate. Keep HyperTwist domain logic, product shell, and runtime ownership above the upstream renderer.",,"Repurpose selected subsystems rather than the whole product. Mine the repo for React renderer and event behavior, scene hook patterns, and browser companion ergonomics; keep what shortens build time, but leave HyperTwist product logic and owned runtime direction outside the upstream layer.",,Repurpose here means: use it as the bounded React renderer substrate for browser-side 3D and XR surfaces.,,,,"Inspect Canvas and createRoot behavior, reconciler and store wiring, event system, hooks, and the native path.","Inspect manifests, README/docs, fiber package runtime, core renderer code, event handling, hooks, and native entry points.","Audit pmndrs/react-three-fiber as the React renderer substrate for HyperTwist browser companion scenes. Inspect Canvas, createRoot, event handling, hooks, and runtime boundaries. Decide which parts should remain direct dependency use versus conceptual reference.",,,,,,,,,,,,,,medium,"Canonized Markdown dossier exists and the repo has been source-backed, but CSV backfill is later than the original v6.3 board generation.",medium,Source-backed dossier exists and the repo has been reconciled into the later Markdown authority stack.,,,,,,,,,,,,HT_browser_surface,HT_browser_surface_0008,browser / 3D / XR / presentation,Repurpose selectively for HyperTwist. Its source-backed role is the commodity React renderer substrate above three.js for browser companion surfaces.,HyperTwist,browser / 3D / XR / presentation,repurpose,moderate modification,medium,pmndrs/react-three-fiber,,,,,,,,,,,,,,,,,,MIT,known_from_reference_material,uploaded_reference_docs,,,,,,,,,,,,,,Donor Bench,Browser React 3D substrate,Included,P2,permissive_or_noncopyleft_known,direct_incorporation_ok,The code license is MIT and direct use is allowed. Treat it as a bounded browser React renderer substrate.,Use directly as a bounded browser-side dependency above three.js; keep HyperTwist product logic and runtime ownership outside the upstream layer.,"Typically preserve notices, attribution, and license text where required.",Usually unnecessary unless you later replace a narrow upstream layer for product-shaping reasons.,high,standard-notice-review,yes,,,,,,,,,,,,,v6.3_markdown_backfill,Backfilled from canonized Markdown dossier pass on 2026-04-24.,selected_not_live_permissive_candidate,phase0r_permissive_eval_then_implement,"Phase 1R closed. Retain as a Phase 3R permissive implementation candidate; implement only from its packet authority and the retained-set contract, not by reopening Phase 0R." -,pmndrs/drei,https://github.com/pmndrs/drei,HyperTwist,,,,,interface / visualization / shell surface,subsystem donor,interface donor,merge bench,integrate,moderate modification,Retain only the helpers with direct product leverage. Keep HyperTwist product architecture outside the upstream abstraction sprawl.,,"Integrate selected helpers rather than the whole package surface. Mine the repo for Html overlays, split-view handling, transform controls, staging, and selective asset helper behavior; keep what shortens build time, but avoid inheriting abstraction sprawl.",,Integrate here means: merge bounded browser helper abstractions into the companion stack where they materially reduce implementation cost.,,,,"Inspect Html overlay behavior, View split rendering, TransformControls, Environment setup, Gltf helpers, and staging utilities.","Inspect manifests, README/docs, core and web helper components, TransformControls, Html, View, Environment, and Gltf wrappers.","Audit pmndrs/drei as a bounded helper layer for HyperTwist browser companion scenes. Inspect Html, View, TransformControls, Environment, and Gltf helper behavior. Decide which utilities deserve active use and which should stay out to avoid abstraction sprawl.",,,,,,,,,,,,,,medium,"Canonized Markdown dossier exists and the repo has been source-backed, but CSV backfill is later than the original v6.3 board generation.",medium,Source-backed dossier exists and the repo has been reconciled into the later Markdown authority stack.,,,,,,,,,,,,HT_browser_surface,HT_browser_surface_0009,browser / 3D / XR / presentation,"Integrate selectively for HyperTwist. Its source-backed role is a high-leverage helper and abstraction layer above react-three-fiber, not a product lane.",HyperTwist,browser / 3D / XR / presentation,integrate,moderate modification,medium,pmndrs/drei,,,,,,,,,,,,,,,,,,MIT,known_from_reference_material,uploaded_reference_docs,,,,,,,,,,,,,,Merge Bench,Browser 3D helper and abstraction layer,Included,P3,permissive_or_noncopyleft_known,direct_incorporation_ok,The code license is MIT and direct use is allowed. Treat it as a bounded browser helper layer above react-three-fiber.,Use directly as a bounded browser-side helper layer; keep HyperTwist product logic and architectural ownership outside the upstream package.,"Typically preserve notices, attribution, and license text where required.",Usually unnecessary unless you later replace a narrow upstream layer for product-shaping reasons.,high,standard-notice-review,yes,,,,,,,,,,,,,v6.3_markdown_backfill,Backfilled from canonized Markdown dossier pass on 2026-04-24.,selected_not_live_permissive_candidate,phase0r_permissive_eval_then_implement,"Phase 1R closed. Retain as a Phase 3R permissive implementation candidate; implement only from its packet authority and the retained-set contract, not by reopening Phase 0R." -,pmndrs/xr,https://github.com/pmndrs/xr,HyperTwist,,,,,interface / visualization / shell surface,subsystem donor,interaction donor,donor bench,repurpose,moderate modification,"Retain the useful XR interaction substrate, but keep HyperTwist product logic, permissions, and owned runtime direction outside the upstream stack.",,"Repurpose selected subsystems rather than the whole product. Mine the repo for XR session state, dom-overlay, pointer interaction, locomotion, and manipulation behavior; keep what shortens build time, but bind it to HyperTwist browser companion flows and permissions.",,Repurpose here means: turn it into the bounded browser XR interaction substrate for immersive companion surfaces.,,,,"Inspect XR store/runtime, dom-overlay support, locomotion hooks, pointer-event model, and handle/manipulation behavior.","Inspect manifests, README/docs, xr store package, React bridge, dom-overlay, locomotion, pointer-events, and handle packages.","Audit pmndrs/xr as the browser XR interaction substrate for HyperTwist companion surfaces. Inspect XR store/runtime, dom-overlay, locomotion, pointer-events, and handle behavior. Decide which pieces should remain direct use and which should stay conceptual.",,,,,,,,,,,,,,medium,"Canonized Markdown dossier exists and the repo has been source-backed, but CSV backfill is later than the original v6.3 board generation.",medium,Source-backed dossier exists and the repo has been reconciled into the later Markdown authority stack.,,,,,,,,,,,,HT_browser_surface,HT_browser_surface_0010,browser / 3D / XR / presentation,"Repurpose selectively for HyperTwist. Its source-backed role is the strongest browser XR interaction and immersive UI donor, not a product foundation.",HyperTwist,browser / 3D / XR / presentation,repurpose,moderate modification,medium,pmndrs/xr,,,,,,,,,,,,,,,,,,MIT,known_from_reference_material,uploaded_reference_docs,,,,,,,,,,,,,,Donor Bench,Browser XR and immersive UI substrate,Included,P2,permissive_or_noncopyleft_known,direct_incorporation_ok,The code license is MIT and direct use is allowed. Treat it as a bounded browser XR interaction donor.,Use directly as a bounded browser-side XR dependency; keep HyperTwist product logic and runtime ownership outside the upstream stack.,"Typically preserve notices, attribution, and license text where required.",Usually unnecessary unless you later replace a narrow upstream layer for product-shaping reasons.,high,standard-notice-review,yes,,,,,,,,,,,,,v6.3_markdown_backfill,Backfilled from canonized Markdown dossier pass on 2026-04-24.,selected_not_live_permissive_candidate,phase0r_permissive_eval_then_implement,"Phase 1R closed. Retain as a Phase 3R permissive implementation candidate; implement only from its packet authority and the retained-set contract, not by reopening Phase 0R." -,pmndrs/uikit,https://github.com/pmndrs/uikit,HyperTwist,,,,,interface / visualization / shell surface,subsystem donor,interface donor,donor bench,repurpose,moderate modification,"Retain the useful spatial UI substrate, but keep HyperTwist product logic, styling language, and runtime ownership outside the upstream package.",,"Repurpose selected subsystems rather than the whole product. Mine the repo for spatial layout, clipping, scrolling, text, and fullscreen panel behavior; keep what shortens build time, but bind it to HyperTwist browser companion surfaces and interface design.",,"Repurpose here means: turn it into the bounded browser spatial UI layer for dashboards, coach panels, and immersive menus.",,,,"Inspect spatial layout runtime, clipping and scrolling behavior, text and media components, Fullscreen, Container, and React bridge behavior.","Inspect manifests, README/docs, react package, build runtime, core uikit components, Fullscreen, Container, and layout-related code.","Audit pmndrs/uikit as the browser spatial UI donor for HyperTwist companion surfaces. Inspect layout, clipping, scrolling, text/media components, and Fullscreen/Container behavior. Decide which parts deserve direct use and which should stay conceptual.",,,,,,,,,,,,,,medium,"Canonized Markdown dossier exists and the repo has been source-backed, but CSV backfill is later than the original v6.3 board generation.",medium,Source-backed dossier exists and the repo has been reconciled into the later Markdown authority stack.,,,,,,,,,,,,HT_browser_surface,HT_browser_surface_0011,browser / 3D / XR / presentation,"Repurpose selectively for HyperTwist. Its source-backed role is the browser spatial UI and 3D interface donor, not a product foundation.",HyperTwist,browser / 3D / XR / presentation,repurpose,moderate modification,medium,pmndrs/uikit,,,,,,,,,,,,,,,,,,MIT,known_from_reference_material,uploaded_reference_docs,,,,,,,,,,,,,,Donor Bench,Browser spatial UI surface,Included,P2,permissive_or_noncopyleft_known,direct_incorporation_ok,The code license is MIT and direct use is allowed. Treat it as a bounded browser spatial UI donor.,Use directly as a bounded browser-side dependency; keep HyperTwist product logic and styling ownership outside the upstream stack.,"Typically preserve notices, attribution, and license text where required.",Usually unnecessary unless you later replace a narrow upstream layer for product-shaping reasons.,high,standard-notice-review,yes,,,,,,,,,,,,,v6.3_markdown_backfill,Backfilled from canonized Markdown dossier pass on 2026-04-24.,selected_not_live_permissive_candidate,phase0r_permissive_eval_then_implement,"Phase 1R closed. Retain as a Phase 3R permissive implementation candidate; implement only from its packet authority and the retained-set contract, not by reopening Phase 0R." -,pmndrs/react-spring,https://github.com/pmndrs/react-spring,HyperTwist,,,,,interface / visualization / shell surface,subsystem donor,interaction donor,merge bench,integrate,moderate modification,"Retain selective motion infrastructure, but keep HyperTwist product logic, page flows, and interface ownership outside the upstream package.",,"Integrate selected motion subsystems rather than the whole product. Mine the repo for spring motion runtime, scheduling, and layered explainer behavior; keep what shortens build time, but bind it to HyperTwist browser companion surfaces and interaction design.",,Integrate here means: merge bounded motion and layered explainer behavior into browser companion surfaces.,,,,"Inspect Controller and SpringValue runtime, scheduler behavior, parallax and layered motion, and browser integration patterns.","Inspect manifests, README/docs, core runtime, scheduler package, parallax package, and animated host behavior.","Audit pmndrs/react-spring as a browser motion substrate for HyperTwist companion surfaces. Inspect core motion runtime, scheduling, layered explainer behavior, and browser integration patterns. Decide which parts deserve active use and which should stay conceptual.",,,,,,,,,,,,,,medium,"Canonized Markdown dossier exists and the repo has been source-backed, but CSV backfill is later than the original v6.3 board generation.",medium,Source-backed dossier exists and the repo has been reconciled into the later Markdown authority stack.,,,,,,,,,,,,HT_browser_surface,HT_browser_surface_0012,browser / 3D / XR / presentation,"Integrate selectively for HyperTwist. Its source-backed role is a browser motion and animation substrate for companion surfaces, not a product lane.",HyperTwist,browser / 3D / XR / presentation,integrate,moderate modification,medium,pmndrs/react-spring,,,,,,,,,,,,,,,,,,MIT,known_from_reference_material,uploaded_reference_docs,,,,,,,,,,,,,,Merge Bench,Browser motion and animation layer,Included,P3,permissive_or_noncopyleft_known,direct_incorporation_ok,The code license is MIT and direct use is allowed. Treat it as a bounded browser motion substrate.,Use directly as a bounded browser-side dependency; keep HyperTwist product logic and page-flow ownership outside the upstream package.,"Typically preserve notices, attribution, and license text where required.",Usually unnecessary unless you later replace a narrow upstream layer for product-shaping reasons.,high,standard-notice-review,yes,,,,,,,,,,,,,v6.3_markdown_backfill,Backfilled from canonized Markdown dossier pass on 2026-04-24.,selected_not_live_permissive_candidate,phase0r_permissive_eval_then_implement,"Phase 1R closed. Retain as a Phase 3R permissive implementation candidate; implement only from its packet authority and the retained-set contract, not by reopening Phase 0R." +,mrdoob/three.js,https://github.com/mrdoob/three.js,HyperTwist,,,,,interface / visualization / shell surface,subsystem donor,dependency donor,donor bench,repurpose,moderate modification,Retain it mainly as a dependency substrate. Do not treat it as the owned gameplay foundation or let it reshape the Unreal-first runtime direction.,,"Repurpose selected subsystems rather than the whole product. Mine the repo for the browser 3D substrate, loader and exporter behavior, WebXR runtime hooks, and utility layers; keep what shortens build time, but leave HyperTwist gameplay and owned runtime direction outside the upstream engine.",,Repurpose here means: use it as the bounded browser-side 3D substrate and keep HyperTwist product logic above it.,,,,"Inspect core renderer and scene stack, loaders and exporters, WebXR manager, addons surface, and editor shell.","Inspect manifests, README/docs, src core and renderer folders, WebXR manager, addons, examples references, and editor shell.","Audit mrdoob/three.js as the browser 3D substrate beneath HyperTwist companion surfaces. Inspect renderer, scene, camera, math, loader, WebXR, and editor behavior. Decide what should be used directly as dependency substrate versus what should remain conceptual.",,,,,,,,,,,,,,medium,"Canonized Markdown dossier exists and the repo has been source-backed, but CSV backfill is later than the original v6.3 board generation.",medium,Source-backed dossier exists and the repo has been reconciled into the later Markdown authority stack.,,,,,,,,,,,,HT_browser_surface,HT_browser_surface_0006,browser / 3D / XR / presentation,"Repurpose selectively for HyperTwist. Its source-backed role is the commodity browser 3D substrate beneath the browser companion stack, not the owned runtime foundation.",HyperTwist,browser / 3D / XR / presentation,repurpose,moderate modification,medium,mrdoob/three.js,,,,,,,,,,,,,,,,,,MIT,known_from_reference_material,uploaded_reference_docs,,,,,,,,,,,,,,Donor Bench,Browser 3D substrate,Included,P2,permissive_or_noncopyleft_known,direct_incorporation_ok,The code license is MIT and direct use is allowed. Treat it as a bounded browser 3D substrate rather than as an owned runtime foundation.,"Use directly as a bounded browser-side dependency; keep HyperTwist gameplay, puzzle logic, and owned runtime direction outside the upstream engine.","Typically preserve notices, attribution, and license text where required.",Usually unnecessary unless you later replace a narrow upstream layer for product-shaping reasons.,high,standard-notice-review,yes,,,,,,,,,,,,,v6.3_markdown_backfill,Backfilled from canonized Markdown dossier pass on 2026-04-24.,implemented_live_permissive,landed_permissive_preserve,"Phase 3R-E closed. Preserve as the landed first-party embodied companion, narration, lip-sync, gesture, subtitle, and avatar-embed lane; start future widening from the live-lane audit, then the 3R-E implementation packet, then REPO_LICENSE_TRACKING.md." +,pmndrs/postprocessing,https://github.com/pmndrs/postprocessing,HyperTwist,,,,,interface / visualization / shell surface,subsystem donor,dependency donor,merge bench,integrate,moderate modification,"Retain selective effect infrastructure, but keep HyperTwist scene ownership, domain logic, and product shell outside the upstream package.",,"Integrate selected subsystems rather than the whole product. Mine the repo for effect-composer, outline, SSAO, and bounded browser emphasis behavior; keep what shortens build time, but bind it to HyperTwist browser viewers and coach surfaces.",,Integrate here means: merge bounded browser-side effect and emphasis infrastructure into the companion stack.,,,,"Inspect EffectComposer and EffectPass, outline and SSAO effect behavior, effect catalog breadth, and performance assumptions.","Inspect manifests, README/docs, core composer and pass code, major effects, and integration seams with three.js.","Audit pmndrs/postprocessing as a bounded browser post-processing substrate for HyperTwist. Inspect composer, pass, outline, and SSAO behavior and decide what should remain direct dependency use versus conceptual reference.",,,,,,,,,,,,,,medium,"Canonized Markdown dossier exists and the repo has been source-backed, but CSV backfill is later than the original v6.3 board generation.",medium,Source-backed dossier exists and the repo has been reconciled into the later Markdown authority stack.,,,,,,,,,,,,HT_browser_surface,HT_browser_surface_0007,browser / 3D / XR / presentation,Integrate selectively for HyperTwist. Its source-backed role is a bounded browser post-processing substrate beneath three.js rather than a product lane.,HyperTwist,browser / 3D / XR / presentation,integrate,moderate modification,medium,pmndrs/postprocessing,,,,,,,,,,,,,,,,,,Zlib,known_from_reference_material,uploaded_reference_docs,,,,,,,,,,,,,,Merge Bench,Browser post-processing substrate,Included,P3,permissive_or_noncopyleft_known,direct_incorporation_ok,The code license is Zlib and direct use is allowed. Treat it as a bounded browser post-processing dependency.,Use directly as a bounded browser-side dependency beneath three.js-based viewers; keep HyperTwist product logic outside the upstream package.,"Typically preserve notices, attribution, and license text where required.",Usually unnecessary unless you later replace a narrow upstream layer for product-shaping reasons.,high,standard-notice-review,yes,,,,,,,,,,,,,v6.3_markdown_backfill,Backfilled from canonized Markdown dossier pass on 2026-04-24.,implemented_live_permissive,landed_permissive_preserve,"Phase 3R-E closed. Preserve as the landed first-party embodied companion, narration, lip-sync, gesture, subtitle, and avatar-embed lane; start future widening from the live-lane audit, then the 3R-E implementation packet, then REPO_LICENSE_TRACKING.md." +,pmndrs/react-three-fiber,https://github.com/pmndrs/react-three-fiber,HyperTwist,,,,,interface / visualization / shell surface,subsystem donor,dependency donor,donor bench,repurpose,moderate modification,"Retain it mainly as a dependency substrate. Keep HyperTwist domain logic, product shell, and runtime ownership above the upstream renderer.",,"Repurpose selected subsystems rather than the whole product. Mine the repo for React renderer and event behavior, scene hook patterns, and browser companion ergonomics; keep what shortens build time, but leave HyperTwist product logic and owned runtime direction outside the upstream layer.",,Repurpose here means: use it as the bounded React renderer substrate for browser-side 3D and XR surfaces.,,,,"Inspect Canvas and createRoot behavior, reconciler and store wiring, event system, hooks, and the native path.","Inspect manifests, README/docs, fiber package runtime, core renderer code, event handling, hooks, and native entry points.","Audit pmndrs/react-three-fiber as the React renderer substrate for HyperTwist browser companion scenes. Inspect Canvas, createRoot, event handling, hooks, and runtime boundaries. Decide which parts should remain direct dependency use versus conceptual reference.",,,,,,,,,,,,,,medium,"Canonized Markdown dossier exists and the repo has been source-backed, but CSV backfill is later than the original v6.3 board generation.",medium,Source-backed dossier exists and the repo has been reconciled into the later Markdown authority stack.,,,,,,,,,,,,HT_browser_surface,HT_browser_surface_0008,browser / 3D / XR / presentation,Repurpose selectively for HyperTwist. Its source-backed role is the commodity React renderer substrate above three.js for browser companion surfaces.,HyperTwist,browser / 3D / XR / presentation,repurpose,moderate modification,medium,pmndrs/react-three-fiber,,,,,,,,,,,,,,,,,,MIT,known_from_reference_material,uploaded_reference_docs,,,,,,,,,,,,,,Donor Bench,Browser React 3D substrate,Included,P2,permissive_or_noncopyleft_known,direct_incorporation_ok,The code license is MIT and direct use is allowed. Treat it as a bounded browser React renderer substrate.,Use directly as a bounded browser-side dependency above three.js; keep HyperTwist product logic and runtime ownership outside the upstream layer.,"Typically preserve notices, attribution, and license text where required.",Usually unnecessary unless you later replace a narrow upstream layer for product-shaping reasons.,high,standard-notice-review,yes,,,,,,,,,,,,,v6.3_markdown_backfill,Backfilled from canonized Markdown dossier pass on 2026-04-24.,implemented_live_permissive,landed_permissive_preserve,"Phase 3R-E closed. Preserve as the landed first-party embodied companion, narration, lip-sync, gesture, subtitle, and avatar-embed lane; start future widening from the live-lane audit, then the 3R-E implementation packet, then REPO_LICENSE_TRACKING.md." +,pmndrs/drei,https://github.com/pmndrs/drei,HyperTwist,,,,,interface / visualization / shell surface,subsystem donor,interface donor,merge bench,integrate,moderate modification,Retain only the helpers with direct product leverage. Keep HyperTwist product architecture outside the upstream abstraction sprawl.,,"Integrate selected helpers rather than the whole package surface. Mine the repo for Html overlays, split-view handling, transform controls, staging, and selective asset helper behavior; keep what shortens build time, but avoid inheriting abstraction sprawl.",,Integrate here means: merge bounded browser helper abstractions into the companion stack where they materially reduce implementation cost.,,,,"Inspect Html overlay behavior, View split rendering, TransformControls, Environment setup, Gltf helpers, and staging utilities.","Inspect manifests, README/docs, core and web helper components, TransformControls, Html, View, Environment, and Gltf wrappers.","Audit pmndrs/drei as a bounded helper layer for HyperTwist browser companion scenes. Inspect Html, View, TransformControls, Environment, and Gltf helper behavior. Decide which utilities deserve active use and which should stay out to avoid abstraction sprawl.",,,,,,,,,,,,,,medium,"Canonized Markdown dossier exists and the repo has been source-backed, but CSV backfill is later than the original v6.3 board generation.",medium,Source-backed dossier exists and the repo has been reconciled into the later Markdown authority stack.,,,,,,,,,,,,HT_browser_surface,HT_browser_surface_0009,browser / 3D / XR / presentation,"Integrate selectively for HyperTwist. Its source-backed role is a high-leverage helper and abstraction layer above react-three-fiber, not a product lane.",HyperTwist,browser / 3D / XR / presentation,integrate,moderate modification,medium,pmndrs/drei,,,,,,,,,,,,,,,,,,MIT,known_from_reference_material,uploaded_reference_docs,,,,,,,,,,,,,,Merge Bench,Browser 3D helper and abstraction layer,Included,P3,permissive_or_noncopyleft_known,direct_incorporation_ok,The code license is MIT and direct use is allowed. Treat it as a bounded browser helper layer above react-three-fiber.,Use directly as a bounded browser-side helper layer; keep HyperTwist product logic and architectural ownership outside the upstream package.,"Typically preserve notices, attribution, and license text where required.",Usually unnecessary unless you later replace a narrow upstream layer for product-shaping reasons.,high,standard-notice-review,yes,,,,,,,,,,,,,v6.3_markdown_backfill,Backfilled from canonized Markdown dossier pass on 2026-04-24.,implemented_live_permissive,landed_permissive_preserve,"Phase 3R-E closed. Preserve as the landed first-party embodied companion, narration, lip-sync, gesture, subtitle, and avatar-embed lane; start future widening from the live-lane audit, then the 3R-E implementation packet, then REPO_LICENSE_TRACKING.md." +,pmndrs/xr,https://github.com/pmndrs/xr,HyperTwist,,,,,interface / visualization / shell surface,subsystem donor,interaction donor,donor bench,repurpose,moderate modification,"Retain the useful XR interaction substrate, but keep HyperTwist product logic, permissions, and owned runtime direction outside the upstream stack.",,"Repurpose selected subsystems rather than the whole product. Mine the repo for XR session state, dom-overlay, pointer interaction, locomotion, and manipulation behavior; keep what shortens build time, but bind it to HyperTwist browser companion flows and permissions.",,Repurpose here means: turn it into the bounded browser XR interaction substrate for immersive companion surfaces.,,,,"Inspect XR store/runtime, dom-overlay support, locomotion hooks, pointer-event model, and handle/manipulation behavior.","Inspect manifests, README/docs, xr store package, React bridge, dom-overlay, locomotion, pointer-events, and handle packages.","Audit pmndrs/xr as the browser XR interaction substrate for HyperTwist companion surfaces. Inspect XR store/runtime, dom-overlay, locomotion, pointer-events, and handle behavior. Decide which pieces should remain direct use and which should stay conceptual.",,,,,,,,,,,,,,medium,"Canonized Markdown dossier exists and the repo has been source-backed, but CSV backfill is later than the original v6.3 board generation.",medium,Source-backed dossier exists and the repo has been reconciled into the later Markdown authority stack.,,,,,,,,,,,,HT_browser_surface,HT_browser_surface_0010,browser / 3D / XR / presentation,"Repurpose selectively for HyperTwist. Its source-backed role is the strongest browser XR interaction and immersive UI donor, not a product foundation.",HyperTwist,browser / 3D / XR / presentation,repurpose,moderate modification,medium,pmndrs/xr,,,,,,,,,,,,,,,,,,MIT,known_from_reference_material,uploaded_reference_docs,,,,,,,,,,,,,,Donor Bench,Browser XR and immersive UI substrate,Included,P2,permissive_or_noncopyleft_known,direct_incorporation_ok,The code license is MIT and direct use is allowed. Treat it as a bounded browser XR interaction donor.,Use directly as a bounded browser-side XR dependency; keep HyperTwist product logic and runtime ownership outside the upstream stack.,"Typically preserve notices, attribution, and license text where required.",Usually unnecessary unless you later replace a narrow upstream layer for product-shaping reasons.,high,standard-notice-review,yes,,,,,,,,,,,,,v6.3_markdown_backfill,Backfilled from canonized Markdown dossier pass on 2026-04-24.,implemented_live_permissive,landed_permissive_preserve,"Phase 3R-E closed. Preserve as the landed first-party embodied companion, narration, lip-sync, gesture, subtitle, and avatar-embed lane; start future widening from the live-lane audit, then the 3R-E implementation packet, then REPO_LICENSE_TRACKING.md." +,pmndrs/uikit,https://github.com/pmndrs/uikit,HyperTwist,,,,,interface / visualization / shell surface,subsystem donor,interface donor,donor bench,repurpose,moderate modification,"Retain the useful spatial UI substrate, but keep HyperTwist product logic, styling language, and runtime ownership outside the upstream package.",,"Repurpose selected subsystems rather than the whole product. Mine the repo for spatial layout, clipping, scrolling, text, and fullscreen panel behavior; keep what shortens build time, but bind it to HyperTwist browser companion surfaces and interface design.",,"Repurpose here means: turn it into the bounded browser spatial UI layer for dashboards, coach panels, and immersive menus.",,,,"Inspect spatial layout runtime, clipping and scrolling behavior, text and media components, Fullscreen, Container, and React bridge behavior.","Inspect manifests, README/docs, react package, build runtime, core uikit components, Fullscreen, Container, and layout-related code.","Audit pmndrs/uikit as the browser spatial UI donor for HyperTwist companion surfaces. Inspect layout, clipping, scrolling, text/media components, and Fullscreen/Container behavior. Decide which parts deserve direct use and which should stay conceptual.",,,,,,,,,,,,,,medium,"Canonized Markdown dossier exists and the repo has been source-backed, but CSV backfill is later than the original v6.3 board generation.",medium,Source-backed dossier exists and the repo has been reconciled into the later Markdown authority stack.,,,,,,,,,,,,HT_browser_surface,HT_browser_surface_0011,browser / 3D / XR / presentation,"Repurpose selectively for HyperTwist. Its source-backed role is the browser spatial UI and 3D interface donor, not a product foundation.",HyperTwist,browser / 3D / XR / presentation,repurpose,moderate modification,medium,pmndrs/uikit,,,,,,,,,,,,,,,,,,MIT,known_from_reference_material,uploaded_reference_docs,,,,,,,,,,,,,,Donor Bench,Browser spatial UI surface,Included,P2,permissive_or_noncopyleft_known,direct_incorporation_ok,The code license is MIT and direct use is allowed. Treat it as a bounded browser spatial UI donor.,Use directly as a bounded browser-side dependency; keep HyperTwist product logic and styling ownership outside the upstream stack.,"Typically preserve notices, attribution, and license text where required.",Usually unnecessary unless you later replace a narrow upstream layer for product-shaping reasons.,high,standard-notice-review,yes,,,,,,,,,,,,,v6.3_markdown_backfill,Backfilled from canonized Markdown dossier pass on 2026-04-24.,implemented_live_permissive,landed_permissive_preserve,"Phase 3R-E closed. Preserve as the landed first-party embodied companion, narration, lip-sync, gesture, subtitle, and avatar-embed lane; start future widening from the live-lane audit, then the 3R-E implementation packet, then REPO_LICENSE_TRACKING.md." +,pmndrs/react-spring,https://github.com/pmndrs/react-spring,HyperTwist,,,,,interface / visualization / shell surface,subsystem donor,interaction donor,merge bench,integrate,moderate modification,"Retain selective motion infrastructure, but keep HyperTwist product logic, page flows, and interface ownership outside the upstream package.",,"Integrate selected motion subsystems rather than the whole product. Mine the repo for spring motion runtime, scheduling, and layered explainer behavior; keep what shortens build time, but bind it to HyperTwist browser companion surfaces and interaction design.",,Integrate here means: merge bounded motion and layered explainer behavior into browser companion surfaces.,,,,"Inspect Controller and SpringValue runtime, scheduler behavior, parallax and layered motion, and browser integration patterns.","Inspect manifests, README/docs, core runtime, scheduler package, parallax package, and animated host behavior.","Audit pmndrs/react-spring as a browser motion substrate for HyperTwist companion surfaces. Inspect core motion runtime, scheduling, layered explainer behavior, and browser integration patterns. Decide which parts deserve active use and which should stay conceptual.",,,,,,,,,,,,,,medium,"Canonized Markdown dossier exists and the repo has been source-backed, but CSV backfill is later than the original v6.3 board generation.",medium,Source-backed dossier exists and the repo has been reconciled into the later Markdown authority stack.,,,,,,,,,,,,HT_browser_surface,HT_browser_surface_0012,browser / 3D / XR / presentation,"Integrate selectively for HyperTwist. Its source-backed role is a browser motion and animation substrate for companion surfaces, not a product lane.",HyperTwist,browser / 3D / XR / presentation,integrate,moderate modification,medium,pmndrs/react-spring,,,,,,,,,,,,,,,,,,MIT,known_from_reference_material,uploaded_reference_docs,,,,,,,,,,,,,,Merge Bench,Browser motion and animation layer,Included,P3,permissive_or_noncopyleft_known,direct_incorporation_ok,The code license is MIT and direct use is allowed. Treat it as a bounded browser motion substrate.,Use directly as a bounded browser-side dependency; keep HyperTwist product logic and page-flow ownership outside the upstream package.,"Typically preserve notices, attribution, and license text where required.",Usually unnecessary unless you later replace a narrow upstream layer for product-shaping reasons.,high,standard-notice-review,yes,,,,,,,,,,,,,v6.3_markdown_backfill,Backfilled from canonized Markdown dossier pass on 2026-04-24.,implemented_live_permissive,landed_permissive_preserve,"Phase 3R-E closed. Preserve as the landed first-party embodied companion, narration, lip-sync, gesture, subtitle, and avatar-embed lane; start future widening from the live-lane audit, then the 3R-E implementation packet, then REPO_LICENSE_TRACKING.md." ,screenpipe/screenpipe,https://github.com/screenpipe/screenpipe,HyperTwist,,,,,capture / replay / support-plane,subsystem donor,support donor,donor bench,repurpose,moderate modification,"Retain the valuable internal layer, but expect to replace upstream shell assumptions and rebind boundaries so it fits the HyperTwist architecture.",,"Repurpose selected subsystems rather than the whole product. Mine the repo for local capture and replay architecture, permission-aware tooling, timeline behavior, vault storage, and notification support surfaces; keep what materially shortens build time, but bind it to HyperTwist-owned data contracts, UI shell, and runtime boundaries.",,Repurpose here means: extract bounded support surfaces from this repo without inheriting the full upstream shell.,,,,"the recording lifecycle, engine and database crates, permission model, rewind timeline behavior, notification routes, and vault handling.","Inspect manifests, README/docs, engine/database/vault crates, app tauri surfaces, timeline UI, notification routes, and permission middleware.","Audit screenpipe/screenpipe as a Support-plane capture, history, and replay sidecar candidate for HyperTwist. Inspect the recording lifecycle, engine and database crates, permission model, rewind timeline behavior, notification routes, and vault handling. Decide whether the retained value should remain active and what should stay bounded outside the HyperTwist core.",,,,,,,,,,,,,,medium,"Canonized Markdown dossier exists and the repo has been source-backed, but CSV backfill is later than the original v6.3 board generation.",medium,Source-backed dossier exists and the repo has been reconciled into the later Markdown authority stack.,,,,,,,,,,,,HT_support_sidecars,HT_support_sidecars_0001,support plane / capture / replay,"Repurpose selectively for HyperTwist. Its source-backed role is a strategic donor with care for local capture/history/replay, permissions-aware agents, encrypted vaults, and notification support surfaces, not a gameplay or vision foundation.",HyperTwist,support plane / capture / replay,repurpose,moderate modification,medium,screenpipe/screenpipe,,,,,,,,,,,,,,,,,,MIT OR Apache-2.0 core; enterprise-restricted ee/,known_from_reference_material,uploaded_reference_docs,,,,,,,,,,Backfilled from canonized Markdown dossier pass on 2026-04-25: 52-screenpipe-screenpipe-upstream-dossier.md,,,,Donor Bench,"Support-plane capture, history, and replay sidecar",Included,P2,mixed_or_boundary_sensitive_known,bounded_sidecar_or_selective_reimplementation,The repo is permissive in its core paths but includes enterprise-restricted ee/ content. Use only clearly permissive core paths as bounded capture/history/replay donor material and exclude or reimplement enterprise-gated paths.,Use only clearly permissive core paths as bounded support-plane donor surfaces; exclude enterprise paths or reimplement equivalent seams.,Preserve permissive notices for reused core paths and do not incorporate ee/ without separate commercial rights.,"Sometimes useful for enterprise-gated slices, but not required for clearly permissive core paths.",high,mixed-license-path-review-required,no,,,,,,,,,,,,,v6.3_markdown_backfill,Backfilled from canonized Markdown dossier pass on 2026-04-25: 52-screenpipe-screenpipe-upstream-dossier.md,selected_not_live_boundary_sensitive,phase0r_boundary_sensitive_eval_then_adapter_or_sidecar,"Phase 1R closed. Retain as a Phase 4R bounded capture, history, and replay sidecar candidate; keep ee/ excluded and permissive-core use narrowly allowlisted." ,remotion-dev/remotion,https://github.com/remotion-dev/remotion,HyperTwist,,,,,media / rendering / export,subsystem donor,media donor,donor bench,repurpose,moderate modification,"Retain the valuable internal layer, but expect to replace upstream shell assumptions and rebind boundaries so it fits the HyperTwist architecture.",,"Repurpose selected subsystems rather than the whole product. Mine the repo for media export, explainer rendering, embedded player behavior, and bounded browser or server-side export workflows; keep what materially shortens build time, but bind it to HyperTwist-owned data contracts, UI shell, and runtime boundaries.",,Repurpose here means: extract bounded support surfaces from this repo without inheriting the full upstream shell.,,,,"the player and renderer packages, studio/editor package, media-parser surfaces, export workflow, and custom commercial license boundaries.","Inspect manifests, LICENSE, README/docs, player package, renderer package, studio package, media-parser package, and major export/render entry points.","Audit remotion-dev/remotion as a Media export and explainer sidecar candidate for HyperTwist. Inspect the player and renderer packages, studio/editor package, media-parser surfaces, export workflow, and custom commercial license boundaries. Decide whether the retained value should remain active and what should stay bounded outside the HyperTwist core.",,,,,,,,,,,,,,medium,"Canonized Markdown dossier exists and the repo has been source-backed, but CSV backfill is later than the original v6.3 board generation.",medium,Source-backed dossier exists and the repo has been reconciled into the later Markdown authority stack.,,,,,,,,,,,,HT_support_sidecars,HT_support_sidecars_0002,media / rendering / export,"Repurpose selectively for HyperTwist. Its source-backed role is a bounded commercially licensed media-export and explainer sidecar, not a product foundation.",HyperTwist,media / rendering / export,repurpose,moderate modification,medium,remotion-dev/remotion,,,,,,,,,,,,,,,,,,Custom two-tier commercial license,known_from_reference_material,uploaded_reference_docs,,,,,,,,,,Backfilled from canonized Markdown dossier pass on 2026-04-25: 53-remotion-dev-remotion-upstream-dossier.md,,,,Donor Bench,Commercially licensed media-export and explainer sidecar,Included,P3,mixed_or_boundary_sensitive_known,bounded_sidecar_or_selective_reimplementation,The repo uses a custom two-tier commercial license and should remain a bounded media-export and explainer sidecar. Review the commercial terms before direct use and do not treat it as a carefree donor.,Keep behind a bounded media-render/export seam; do not let it become a runtime foundation.,Preserve upstream license materials and satisfy the applicable commercial terms before shipping or internal deployment.,Sometimes useful only if later commercial terms or deployment constraints make direct use less attractive.,high,commercial-license-sidecar-review,no,,,,,,,,,,,,,v6.3_markdown_backfill,Refined on 2026-04-25 to the dossier-backed commercially licensed media-export and explainer sidecar posture.,selected_not_live_boundary_sensitive,phase0r_boundary_sensitive_eval_then_adapter_or_sidecar,Phase 1R closed. Retain as a Phase 4R commercially sensitive media-export and explainer sidecar candidate; make an explicit package-level license decision before any use. -,ecomfe/zrender,https://github.com/ecomfe/zrender,HyperTwist,,,,,interface / visualization / shell surface,subsystem donor,dependency donor,merge bench,integrate,moderate modification,"Retain the reusable internal layer, but replace shell assumptions and rebind boundaries so it plugs into HyperTwist cleanly.",,"Integrate selected subsystems rather than the whole product. Mine the repo for 2D rendering, scene-graph, animation, and event-handling substrate behavior beneath browser reporting surfaces; keep what materially shortens build time, but bind it to HyperTwist-owned data contracts, UI shell, and runtime boundaries.",,Integrate here means: merge bounded support surfaces from this repo into the HyperTwist companion stack.,,,,"the zrender runtime entry, scene storage, canvas and SVG painters, handler proxy, and animation behavior.","Inspect manifests, README/docs, runtime entry, storage, painter implementations, event proxy, animation modules, and core graphic primitives.","Audit ecomfe/zrender as a Browser 2D render substrate candidate for HyperTwist. Inspect the zrender runtime entry, scene storage, canvas and SVG painters, handler proxy, and animation behavior. Decide whether the retained value should remain active and what should stay bounded outside the HyperTwist core.",,,,,,,,,,,,,,medium,"Canonized Markdown dossier exists and the repo has been source-backed, but CSV backfill is later than the original v6.3 board generation.",medium,Source-backed dossier exists and the repo has been reconciled into the later Markdown authority stack.,,,,,,,,,,,,HT_browser_support,HT_browser_support_0001,browser / 2D / visualization,"Integrate selectively for HyperTwist. Its source-backed role is a lower-level 2D rendering and interaction substrate beneath echarts, not a separate strategic product lane.",HyperTwist,browser / 2D / visualization,integrate,moderate modification,medium,ecomfe/zrender,,,,,,,,,,,,,,,,,,BSD-3-Clause,known_from_reference_material,uploaded_reference_docs,,,,,,,,,,Backfilled from canonized Markdown dossier pass on 2026-04-25: 56-ecomfe-zrender-upstream-dossier.md,,,,Merge Bench,Browser 2D render substrate,Included,P3,permissive_or_noncopyleft_known,direct_incorporation_ok,The code license is BSD-3-Clause and direct use is allowed. Treat it as a bounded 2D render substrate beneath the reporting stack.,Use directly as a bounded browser-side dependency beneath analytics and reporting layers.,"Typically preserve notices, attribution, and license text where required.",Usually unnecessary unless you later replace a narrow utility layer for product-shaping reasons.,high,standard-notice-review,yes,,,,,,,,,,,,,v6.3_markdown_backfill,Backfilled from canonized Markdown dossier pass on 2026-04-25: 56-ecomfe-zrender-upstream-dossier.md,selected_not_live_permissive_candidate,phase0r_permissive_eval_then_implement,"Phase 1R closed. Retain as a Phase 3R permissive implementation candidate; implement only from its packet authority and the retained-set contract, not by reopening Phase 0R." -,pissang/claygl,https://github.com/pissang/claygl,HyperTwist,,,,,interface / visualization / shell surface,subsystem donor,dependency donor,merge bench,integrate,moderate modification,"Retain the reusable internal layer, but replace shell assumptions and rebind boundaries so it plugs into HyperTwist cleanly.",,"Integrate selected subsystems rather than the whole product. Mine the repo for browser WebGL substrate, picking, controls, compositor behavior, and lightweight scene infrastructure; keep what materially shortens build time, but bind it to HyperTwist-owned data contracts, UI shell, and runtime boundaries.",,Integrate here means: merge bounded support surfaces from this repo into the HyperTwist companion stack.,,,,"the renderer and application shell, scene behavior, camera and control plugins, picking, compositor, and loader surfaces.","Inspect manifests, README/docs, renderer, application, scene, controls, compositor, loader, and core geometry/material modules.","Audit pissang/claygl as a Browser WebGL substrate candidate for HyperTwist. Inspect the renderer and application shell, scene behavior, camera and control plugins, picking, compositor, and loader surfaces. Decide whether the retained value should remain active and what should stay bounded outside the HyperTwist core.",,,,,,,,,,,,,,medium,"Canonized Markdown dossier exists and the repo has been source-backed, but CSV backfill is later than the original v6.3 board generation.",medium,Source-backed dossier exists and the repo has been reconciled into the later Markdown authority stack.,,,,,,,,,,,,HT_browser_support,HT_browser_support_0002,browser / 3D / XR / presentation,"Integrate selectively for HyperTwist. Its source-backed role is a lower-level WebGL substrate beneath browser viewer and analytics surfaces, not a runtime foundation.",HyperTwist,browser / 3D / XR / presentation,integrate,moderate modification,medium,pissang/claygl,,,,,,,,,,,,,,,,,,BSD-style permissive (see LICENSE),known_from_reference_material,uploaded_reference_docs,,,,,,,,,,Backfilled from canonized Markdown dossier pass on 2026-04-25: 58-pissang-claygl-upstream-dossier.md,,,,Merge Bench,Browser WebGL substrate,Included,P3,permissive_or_noncopyleft_known,direct_incorporation_ok,The repo carries a BSD-style permissive license in its LICENSE file and direct use is viable. Treat it as a bounded WebGL substrate rather than a product lane.,Use directly as a bounded browser-side dependency after preserving the upstream license text.,Preserve the exact upstream LICENSE text and notices when redistributed or vendored.,Usually unnecessary unless you later replace a narrow low-level utility layer.,medium,license-text-normalization-review,yes,,,,,,,,,,,,,v6.3_markdown_backfill,Backfilled from canonized Markdown dossier pass on 2026-04-25: 58-pissang-claygl-upstream-dossier.md,selected_not_live_permissive_candidate,phase0r_permissive_eval_then_implement,"Phase 1R closed. Retain as a Phase 3R permissive implementation candidate; implement only from its packet authority and the retained-set contract, not by reopening Phase 0R." -,pissang/clay-viewer,https://github.com/pissang/clay-viewer,HyperTwist,,,,,interface / visualization / shell surface,subsystem donor,viewer donor,merge bench,integrate,moderate modification,"Retain the reusable internal layer, but replace shell assumptions and rebind boundaries so it plugs into HyperTwist cleanly.",,"Integrate selected subsystems rather than the whole product. Mine the repo for browser viewer/editor behavior, hotspot handling, post-effects, lighting presets, and animation-preview support; keep what materially shortens build time, but bind it to HyperTwist-owned data contracts, UI shell, and runtime boundaries.",,Integrate here means: merge bounded support surfaces from this repo into the HyperTwist companion stack.,,,,"the viewer shell, hotspot and picking behavior, default scene config, effect compositor, and animation-preview surfaces.","Inspect manifests, README/docs, viewer runtime, default scene config, graphic effect compositor, and associated editor or UI shells.","Audit pissang/clay-viewer as a Browser viewer and editor sidecar candidate for HyperTwist. Inspect the viewer shell, hotspot and picking behavior, default scene config, effect compositor, and animation-preview surfaces. Decide whether the retained value should remain active and what should stay bounded outside the HyperTwist core.",,,,,,,,,,,,,,medium,"Canonized Markdown dossier exists and the repo has been source-backed, but CSV backfill is later than the original v6.3 board generation.",medium,Source-backed dossier exists and the repo has been reconciled into the later Markdown authority stack.,,,,,,,,,,,,HT_browser_support,HT_browser_support_0003,browser / 3D / XR / presentation,"Integrate selectively for HyperTwist. Its source-backed role is a bounded browser viewer/editor sidecar with hotspot, environment, and post-effect surfaces, not a gameplay or runtime foundation.",HyperTwist,browser / 3D / XR / presentation,integrate,moderate modification,medium,pissang/clay-viewer,,,,,,,,,,,,,,,,,,BSD-3-Clause,known_from_reference_material,uploaded_reference_docs,,,,,,,,,,Backfilled from canonized Markdown dossier pass on 2026-04-25: 59-pissang-clay-viewer-upstream-dossier.md,,,,Merge Bench,Browser viewer and editor sidecar,Included,P3,permissive_or_noncopyleft_known,direct_incorporation_ok,The code license is BSD-3-Clause and direct use is allowed. Treat it as a bounded browser viewer/editor sidecar.,Use directly as a bounded browser-side dependency or sidecar for viewer/editor surfaces.,"Typically preserve notices, attribution, and license text where required.",Usually unnecessary unless later product-shaping concerns make selective replacement attractive.,high,standard-notice-review,yes,,,,,,,,,,,,,v6.3_markdown_backfill,Backfilled from canonized Markdown dossier pass on 2026-04-25: 59-pissang-clay-viewer-upstream-dossier.md,selected_not_live_permissive_candidate,phase0r_permissive_eval_then_implement,"Phase 1R closed. Retain as a Phase 3R permissive implementation candidate; implement only from its packet authority and the retained-set contract, not by reopening Phase 0R." +,ecomfe/zrender,https://github.com/ecomfe/zrender,HyperTwist,,,,,interface / visualization / shell surface,subsystem donor,dependency donor,merge bench,integrate,moderate modification,"Retain the reusable internal layer, but replace shell assumptions and rebind boundaries so it plugs into HyperTwist cleanly.",,"Integrate selected subsystems rather than the whole product. Mine the repo for 2D rendering, scene-graph, animation, and event-handling substrate behavior beneath browser reporting surfaces; keep what materially shortens build time, but bind it to HyperTwist-owned data contracts, UI shell, and runtime boundaries.",,Integrate here means: merge bounded support surfaces from this repo into the HyperTwist companion stack.,,,,"the zrender runtime entry, scene storage, canvas and SVG painters, handler proxy, and animation behavior.","Inspect manifests, README/docs, runtime entry, storage, painter implementations, event proxy, animation modules, and core graphic primitives.","Audit ecomfe/zrender as a Browser 2D render substrate candidate for HyperTwist. Inspect the zrender runtime entry, scene storage, canvas and SVG painters, handler proxy, and animation behavior. Decide whether the retained value should remain active and what should stay bounded outside the HyperTwist core.",,,,,,,,,,,,,,medium,"Canonized Markdown dossier exists and the repo has been source-backed, but CSV backfill is later than the original v6.3 board generation.",medium,Source-backed dossier exists and the repo has been reconciled into the later Markdown authority stack.,,,,,,,,,,,,HT_browser_support,HT_browser_support_0001,browser / 2D / visualization,"Integrate selectively for HyperTwist. Its source-backed role is a lower-level 2D rendering and interaction substrate beneath echarts, not a separate strategic product lane.",HyperTwist,browser / 2D / visualization,integrate,moderate modification,medium,ecomfe/zrender,,,,,,,,,,,,,,,,,,BSD-3-Clause,known_from_reference_material,uploaded_reference_docs,,,,,,,,,,Backfilled from canonized Markdown dossier pass on 2026-04-25: 56-ecomfe-zrender-upstream-dossier.md,,,,Merge Bench,Browser 2D render substrate,Included,P3,permissive_or_noncopyleft_known,direct_incorporation_ok,The code license is BSD-3-Clause and direct use is allowed. Treat it as a bounded 2D render substrate beneath the reporting stack.,Use directly as a bounded browser-side dependency beneath analytics and reporting layers.,"Typically preserve notices, attribution, and license text where required.",Usually unnecessary unless you later replace a narrow utility layer for product-shaping reasons.,high,standard-notice-review,yes,,,,,,,,,,,,,v6.3_markdown_backfill,Backfilled from canonized Markdown dossier pass on 2026-04-25: 56-ecomfe-zrender-upstream-dossier.md,implemented_live_permissive,landed_permissive_preserve,"Phase 3R-E closed. Preserve as the landed first-party embodied companion, narration, lip-sync, gesture, subtitle, and avatar-embed lane; start future widening from the live-lane audit, then the 3R-E implementation packet, then REPO_LICENSE_TRACKING.md." +,pissang/claygl,https://github.com/pissang/claygl,HyperTwist,,,,,interface / visualization / shell surface,subsystem donor,dependency donor,merge bench,integrate,moderate modification,"Retain the reusable internal layer, but replace shell assumptions and rebind boundaries so it plugs into HyperTwist cleanly.",,"Integrate selected subsystems rather than the whole product. Mine the repo for browser WebGL substrate, picking, controls, compositor behavior, and lightweight scene infrastructure; keep what materially shortens build time, but bind it to HyperTwist-owned data contracts, UI shell, and runtime boundaries.",,Integrate here means: merge bounded support surfaces from this repo into the HyperTwist companion stack.,,,,"the renderer and application shell, scene behavior, camera and control plugins, picking, compositor, and loader surfaces.","Inspect manifests, README/docs, renderer, application, scene, controls, compositor, loader, and core geometry/material modules.","Audit pissang/claygl as a Browser WebGL substrate candidate for HyperTwist. Inspect the renderer and application shell, scene behavior, camera and control plugins, picking, compositor, and loader surfaces. Decide whether the retained value should remain active and what should stay bounded outside the HyperTwist core.",,,,,,,,,,,,,,medium,"Canonized Markdown dossier exists and the repo has been source-backed, but CSV backfill is later than the original v6.3 board generation.",medium,Source-backed dossier exists and the repo has been reconciled into the later Markdown authority stack.,,,,,,,,,,,,HT_browser_support,HT_browser_support_0002,browser / 3D / XR / presentation,"Integrate selectively for HyperTwist. Its source-backed role is a lower-level WebGL substrate beneath browser viewer and analytics surfaces, not a runtime foundation.",HyperTwist,browser / 3D / XR / presentation,integrate,moderate modification,medium,pissang/claygl,,,,,,,,,,,,,,,,,,BSD-style permissive (see LICENSE),known_from_reference_material,uploaded_reference_docs,,,,,,,,,,Backfilled from canonized Markdown dossier pass on 2026-04-25: 58-pissang-claygl-upstream-dossier.md,,,,Merge Bench,Browser WebGL substrate,Included,P3,permissive_or_noncopyleft_known,direct_incorporation_ok,The repo carries a BSD-style permissive license in its LICENSE file and direct use is viable. Treat it as a bounded WebGL substrate rather than a product lane.,Use directly as a bounded browser-side dependency after preserving the upstream license text.,Preserve the exact upstream LICENSE text and notices when redistributed or vendored.,Usually unnecessary unless you later replace a narrow low-level utility layer.,medium,license-text-normalization-review,yes,,,,,,,,,,,,,v6.3_markdown_backfill,Backfilled from canonized Markdown dossier pass on 2026-04-25: 58-pissang-claygl-upstream-dossier.md,implemented_live_permissive,landed_permissive_preserve,"Phase 3R-E closed. Preserve as the landed first-party embodied companion, narration, lip-sync, gesture, subtitle, and avatar-embed lane; start future widening from the live-lane audit, then the 3R-E implementation packet, then REPO_LICENSE_TRACKING.md." +,pissang/clay-viewer,https://github.com/pissang/clay-viewer,HyperTwist,,,,,interface / visualization / shell surface,subsystem donor,viewer donor,merge bench,integrate,moderate modification,"Retain the reusable internal layer, but replace shell assumptions and rebind boundaries so it plugs into HyperTwist cleanly.",,"Integrate selected subsystems rather than the whole product. Mine the repo for browser viewer/editor behavior, hotspot handling, post-effects, lighting presets, and animation-preview support; keep what materially shortens build time, but bind it to HyperTwist-owned data contracts, UI shell, and runtime boundaries.",,Integrate here means: merge bounded support surfaces from this repo into the HyperTwist companion stack.,,,,"the viewer shell, hotspot and picking behavior, default scene config, effect compositor, and animation-preview surfaces.","Inspect manifests, README/docs, viewer runtime, default scene config, graphic effect compositor, and associated editor or UI shells.","Audit pissang/clay-viewer as a Browser viewer and editor sidecar candidate for HyperTwist. Inspect the viewer shell, hotspot and picking behavior, default scene config, effect compositor, and animation-preview surfaces. Decide whether the retained value should remain active and what should stay bounded outside the HyperTwist core.",,,,,,,,,,,,,,medium,"Canonized Markdown dossier exists and the repo has been source-backed, but CSV backfill is later than the original v6.3 board generation.",medium,Source-backed dossier exists and the repo has been reconciled into the later Markdown authority stack.,,,,,,,,,,,,HT_browser_support,HT_browser_support_0003,browser / 3D / XR / presentation,"Integrate selectively for HyperTwist. Its source-backed role is a bounded browser viewer/editor sidecar with hotspot, environment, and post-effect surfaces, not a gameplay or runtime foundation.",HyperTwist,browser / 3D / XR / presentation,integrate,moderate modification,medium,pissang/clay-viewer,,,,,,,,,,,,,,,,,,BSD-3-Clause,known_from_reference_material,uploaded_reference_docs,,,,,,,,,,Backfilled from canonized Markdown dossier pass on 2026-04-25: 59-pissang-clay-viewer-upstream-dossier.md,,,,Merge Bench,Browser viewer and editor sidecar,Included,P3,permissive_or_noncopyleft_known,direct_incorporation_ok,The code license is BSD-3-Clause and direct use is allowed. Treat it as a bounded browser viewer/editor sidecar.,Use directly as a bounded browser-side dependency or sidecar for viewer/editor surfaces.,"Typically preserve notices, attribution, and license text where required.",Usually unnecessary unless later product-shaping concerns make selective replacement attractive.,high,standard-notice-review,yes,,,,,,,,,,,,,v6.3_markdown_backfill,Backfilled from canonized Markdown dossier pass on 2026-04-25: 59-pissang-clay-viewer-upstream-dossier.md,implemented_live_permissive,landed_permissive_preserve,"Phase 3R-E closed. Preserve as the landed first-party embodied companion, narration, lip-sync, gesture, subtitle, and avatar-embed lane; start future widening from the live-lane audit, then the 3R-E implementation packet, then REPO_LICENSE_TRACKING.md." ,KhronosGroup/glTF-Sample-Renderer,https://github.com/KhronosGroup/glTF-Sample-Renderer,HyperTwist,,,,,interface / visualization / shell surface,subsystem donor,dependency donor,merge bench,integrate,moderate modification,"Retain the reusable internal layer, but replace shell assumptions and rebind boundaries so it plugs into HyperTwist cleanly.",,"Integrate selected subsystems rather than the whole product. Mine the repo for standards-aware glTF loading, renderer substrate, camera state, and resource-loading behavior beneath asset viewers; keep what materially shortens build time, but bind it to HyperTwist-owned data contracts, UI shell, and runtime boundaries.",,Integrate here means: merge bounded support surfaces from this repo into the HyperTwist companion stack.,,,,"the GltfView and GltfState API surface, resource loader, renderer core, and user-camera behavior.","Inspect manifests, README/docs, renderer source tree, resource loader, GltfView, GltfState, user camera, and renderer integration points.","Audit KhronosGroup/glTF-Sample-Renderer as a Browser asset renderer substrate candidate for HyperTwist. Inspect the GltfView and GltfState API surface, resource loader, renderer core, and user-camera behavior. Decide whether the retained value should remain active and what should stay bounded outside the HyperTwist core.",,,,,,,,,,,,,,medium,"Canonized Markdown dossier exists and the repo has been source-backed, but CSV backfill is later than the original v6.3 board generation.",medium,Source-backed dossier exists and the repo has been reconciled into the later Markdown authority stack.,,,,,,,,,,,,HT_browser_support,HT_browser_support_0004,browser / 3D / XR / presentation,"Integrate selectively for HyperTwist. Its source-backed role is the lower-level official glTF renderer substrate beneath glTF-Sample-Viewer, not a separate strategic lane.",HyperTwist,browser / 3D / XR / presentation,integrate,moderate modification,medium,khronosgroup/gltf-sample-renderer,,,,,,,,,,,,,,,,,,Apache-2.0,known_from_reference_material,uploaded_reference_docs,,,,,,,,,,Backfilled from canonized Markdown dossier pass on 2026-04-25: 61-khronosgroup-gltf-sample-renderer-upstream-dossier.md,,,,Merge Bench,Browser asset renderer substrate,Included,P3,permissive_or_noncopyleft_known,direct_incorporation_ok,The code license is Apache-2.0 and direct use is allowed. Treat it as a bounded renderer substrate beneath asset viewers.,Use directly as a bounded browser-side dependency beneath asset inspection and preview tooling.,Preserve LICENSE and NOTICE materials where required.,Usually unnecessary unless later product-shaping concerns make selective replacement attractive.,high,notice-file-review,yes,,,,,,,,,,,,,v6.3_markdown_backfill,Backfilled from canonized Markdown dossier pass on 2026-04-25: 61-khronosgroup-gltf-sample-renderer-upstream-dossier.md,selected_not_live_permissive_candidate,phase0r_permissive_eval_then_implement,"Phase 3R-D closed for the anchor. Retain as the subordinate renderer/reference substrate beneath the landed google/model-viewer asset-QA lane; do not treat it as separately live." ,google/model-viewer/packages/space-opera,https://github.com/google/model-viewer/tree/main/packages/space-opera,HyperTwist,,,,,interface / visualization / shell surface,subsystem donor,editor donor,merge bench,integrate,moderate modification,"Retain the reusable internal layer, but replace shell assumptions and rebind boundaries so it plugs into HyperTwist cleanly.",,"Integrate selected subsystems rather than the whole product. Mine the repo for browser editor, inspection, hotspot editing, snippet export, and lightweight asset-authoring behavior; keep what materially shortens build time, but bind it to HyperTwist-owned data contracts, UI shell, and runtime boundaries.",,Integrate here means: merge bounded support surfaces from this repo into the HyperTwist companion stack.,,,,"the app shell, reducer and state structure, hotspot editing flow, snippet export surfaces, and inspector behavior.","Inspect manifests, README/docs, app shell, reducers, hotspot panel, snippet generator, inspector components, and editor-adjacent modules.","Audit google/model-viewer/packages/space-opera as a Browser asset editor and inspection surface candidate for HyperTwist. Inspect the app shell, reducer and state structure, hotspot editing flow, snippet export surfaces, and inspector behavior. Decide whether the retained value should remain active and what should stay bounded outside the HyperTwist core.",,,,,,,,,,,,,,medium,"Canonized Markdown dossier exists and the repo has been source-backed, but CSV backfill is later than the original v6.3 board generation.",medium,Source-backed dossier exists and the repo has been reconciled into the later Markdown authority stack.,,,,,,,,,,,,HT_browser_support,HT_browser_support_0005,browser / 3D / XR / presentation,"Integrate selectively for HyperTwist. Its source-backed role is a bounded browser editor and inspection donor beneath model-viewer, not a standalone product lane.",HyperTwist,browser / 3D / XR / presentation,integrate,moderate modification,medium,google/model-viewer/packages/space-opera,,,,,,,,,,,,,,,,,,Apache-2.0,known_from_reference_material,uploaded_reference_docs,,,,,,,,,,Backfilled from canonized Markdown dossier pass on 2026-04-25: 63-google-space-opera-upstream-dossier.md,,,,Merge Bench,Browser asset editor and inspection surface,Included,P3,permissive_or_noncopyleft_known,direct_incorporation_ok,The code license is Apache-2.0 and direct use is allowed. Treat it as a bounded browser editor and inspection donor beneath model-viewer.,Use directly as a bounded browser-side dependency or concept donor beneath browser asset tooling.,Preserve LICENSE and NOTICE materials where required.,Usually unnecessary unless later product-shaping concerns make selective replacement attractive.,high,notice-file-review,yes,,,,,,,,,,,,,v6.3_markdown_backfill,Backfilled from canonized Markdown dossier pass on 2026-04-25: 63-google-space-opera-upstream-dossier.md,selected_not_live_permissive_candidate,phase0r_permissive_eval_then_implement,"Phase 3R-D closed for the anchor. Retain as the subordinate browser editor and inspection package beneath the landed google/model-viewer lane; do not treat it as separately live." ,google/model-viewer/packages/render-fidelity-tools,https://github.com/google/model-viewer/tree/main/packages/render-fidelity-tools,HyperTwist,,,,,analytics / visualization / reporting,subsystem donor,qa donor,merge bench,integrate,moderate modification,"Retain the reusable internal layer, but replace shell assumptions and rebind boundaries so it plugs into HyperTwist cleanly.",,"Integrate selected subsystems rather than the whole product. Mine the repo for browser visual-regression workflows, golden rendering, fidelity thresholds, and harness configuration behavior; keep what materially shortens build time, but bind it to HyperTwist-owned data contracts, UI shell, and runtime boundaries.",,Integrate here means: merge bounded support surfaces from this repo into the HyperTwist companion stack.,,,,"the test-fidelity and render-goldens workflows, renderer harness behavior, image-comparison worker, and artifact generation.","Inspect manifests, README/docs, workflow scripts, renderer harness, image comparison worker, and fidelity-testing utilities.","Audit google/model-viewer/packages/render-fidelity-tools as a Browser fidelity QA harness candidate for HyperTwist. Inspect the test-fidelity and render-goldens workflows, renderer harness behavior, image-comparison worker, and artifact generation. Decide whether the retained value should remain active and what should stay bounded outside the HyperTwist core.",,,,,,,,,,,,,,medium,"Canonized Markdown dossier exists and the repo has been source-backed, but CSV backfill is later than the original v6.3 board generation.",medium,Source-backed dossier exists and the repo has been reconciled into the later Markdown authority stack.,,,,,,,,,,,,HT_browser_support,HT_browser_support_0006,browser / QA / visual regression,"Integrate selectively for HyperTwist. Its source-backed role is a bounded fidelity oracle and QA harness donor beneath model-viewer, not a runtime lane.",HyperTwist,browser / QA / visual regression,integrate,moderate modification,medium,google/model-viewer/packages/render-fidelity-tools,,,,,,,,,,,,,,,,,,Apache-2.0,known_from_reference_material,uploaded_reference_docs,,,,,,,,,,Backfilled from canonized Markdown dossier pass on 2026-04-25: 64-google-render-fidelity-tools-upstream-dossier.md,,,,Merge Bench,Browser fidelity QA harness,Included,P3,permissive_or_noncopyleft_known,direct_incorporation_ok,The code license is Apache-2.0 and direct use is allowed. Treat it as a bounded QA and fidelity-testing donor.,Use directly as a bounded browser-side QA dependency or concept donor for visual regression tooling.,Preserve LICENSE and NOTICE materials where required.,Usually unnecessary unless later product-shaping concerns make selective replacement attractive.,high,notice-file-review,yes,,,,,,,,,,,,,v6.3_markdown_backfill,Backfilled from canonized Markdown dossier pass on 2026-04-25: 64-google-render-fidelity-tools-upstream-dossier.md,selected_not_live_permissive_candidate,phase0r_permissive_eval_then_implement,"Phase 3R-D closed for the anchor. Retain as the subordinate fidelity-oracle and regression sidecar beneath the landed google/model-viewer lane; do not treat it as separately live." ,google/model-viewer/packages/model-viewer-effects,https://github.com/google/model-viewer/tree/main/packages/model-viewer-effects,HyperTwist,,,,,interface / visualization / shell surface,subsystem donor,effect donor,merge bench,integrate,moderate modification,"Retain the reusable internal layer, but replace shell assumptions and rebind boundaries so it plugs into HyperTwist cleanly.",,"Integrate selected subsystems rather than the whole product. Mine the repo for browser emphasis, outline and SSAO behavior, and effect-composer integration beneath browser model presentation; keep what materially shortens build time, but bind it to HyperTwist-owned data contracts, UI shell, and runtime boundaries.",,Integrate here means: merge bounded support surfaces from this repo into the HyperTwist companion stack.,,,,"the effect-composer integration, custom-element surface, outline effect, SSAO effect, and emphasis behavior.","Inspect manifests, README/docs, effect-composer integration, custom-element wrapper, outline and SSAO effects, and related extension code.","Audit google/model-viewer/packages/model-viewer-effects as a Browser emphasis and post-processing extension candidate for HyperTwist. Inspect the effect-composer integration, custom-element surface, outline effect, SSAO effect, and emphasis behavior. Decide whether the retained value should remain active and what should stay bounded outside the HyperTwist core.",,,,,,,,,,,,,,medium,"Canonized Markdown dossier exists and the repo has been source-backed, but CSV backfill is later than the original v6.3 board generation.",medium,Source-backed dossier exists and the repo has been reconciled into the later Markdown authority stack.,,,,,,,,,,,,HT_browser_support,HT_browser_support_0007,browser / 3D / XR / presentation,"Integrate selectively for HyperTwist. Its source-backed role is a bounded browser post-processing and emphasis donor beneath model-viewer, not a standalone product lane.",HyperTwist,browser / 3D / XR / presentation,integrate,moderate modification,medium,google/model-viewer/packages/model-viewer-effects,,,,,,,,,,,,,,,,,,Apache-2.0,known_from_reference_material,uploaded_reference_docs,,,,,,,,,,Backfilled from canonized Markdown dossier pass on 2026-04-25: 65-google-model-viewer-effects-upstream-dossier.md,,,,Merge Bench,Browser emphasis and post-processing extension,Included,P3,permissive_or_noncopyleft_known,direct_incorporation_ok,The code license is Apache-2.0 and direct use is allowed. Treat it as a bounded browser emphasis and effect donor beneath model-viewer.,Use directly as a bounded browser-side dependency or concept donor beneath browser model presentation.,Preserve LICENSE and NOTICE materials where required.,Usually unnecessary unless later product-shaping concerns make selective replacement attractive.,high,notice-file-review,yes,,,,,,,,,,,,,v6.3_markdown_backfill,Backfilled from canonized Markdown dossier pass on 2026-04-25: 65-google-model-viewer-effects-upstream-dossier.md,selected_not_live_permissive_candidate,phase0r_permissive_eval_then_implement,"Phase 3R-D closed for the anchor. Retain as a subordinate emphasis and effects package beneath the landed google/model-viewer lane; do not treat it as separately live." ,google/model-viewer/packages/modelviewer.dev,https://github.com/google/model-viewer/tree/main/packages/modelviewer.dev,HyperTwist,,,,,interface / visualization / shell surface,subsystem donor,docs donor,merge bench,integrate,moderate modification,"Retain the reusable internal layer, but replace shell assumptions and rebind boundaries so it plugs into HyperTwist cleanly.",,"Integrate selected subsystems rather than the whole product. Mine the repo for live docs and demo generation, snippet-to-demo coupling, and documentation information architecture; keep what materially shortens build time, but bind it to HyperTwist-owned data contracts, UI shell, and runtime boundaries.",,Integrate here means: merge bounded support surfaces from this repo into the HyperTwist companion stack.,,,,"the docs-and-examples flow, example-snippet behavior, sidebar generation, and HTML generation surfaces.","Inspect manifests, README/docs, docs-and-examples code, example-snippet component, sidebar builder, and HTML generation utilities.","Audit google/model-viewer/packages/modelviewer.dev as a Browser docs and demo surface candidate for HyperTwist. Inspect the docs-and-examples flow, example-snippet behavior, sidebar generation, and HTML generation surfaces. Decide whether the retained value should remain active and what should stay bounded outside the HyperTwist core.",,,,,,,,,,,,,,medium,"Canonized Markdown dossier exists and the repo has been source-backed, but CSV backfill is later than the original v6.3 board generation.",medium,Source-backed dossier exists and the repo has been reconciled into the later Markdown authority stack.,,,,,,,,,,,,HT_browser_support,HT_browser_support_0008,documentation / demos / examples,"Integrate selectively for HyperTwist. Its source-backed role is a bounded docs and demo donor beneath model-viewer, not a runtime lane.",HyperTwist,documentation / demos / examples,integrate,moderate modification,medium,google/model-viewer/packages/modelviewer.dev,,,,,,,,,,,,,,,,,,Apache-2.0,known_from_reference_material,uploaded_reference_docs,,,,,,,,,,Backfilled from canonized Markdown dossier pass on 2026-04-25: 66-google-modelviewer-dev-upstream-dossier.md,,,,Merge Bench,Browser docs and demo surface,Included,P4,permissive_or_noncopyleft_known,direct_incorporation_ok,The code license is Apache-2.0 and direct use is allowed. Treat it as a bounded docs and demo donor.,Use directly as a bounded docs/demo dependency or concept donor for documentation surfaces.,Preserve LICENSE and NOTICE materials where required.,Usually unnecessary unless later product-shaping concerns make selective replacement attractive.,high,notice-file-review,yes,,,,,,,,,,,,,v6.3_markdown_backfill,Backfilled from canonized Markdown dossier pass on 2026-04-25: 66-google-modelviewer-dev-upstream-dossier.md,selected_not_live_permissive_candidate,phase0r_permissive_eval_then_implement,"Phase 3R-D closed for the anchor. Retain as subordinate docs and demo infrastructure beneath the landed google/model-viewer lane; do not treat it as separately live or as a product-shell owner." ,google/model-viewer/packages/shared-assets,https://github.com/google/model-viewer/tree/main/packages/shared-assets,HyperTwist,,,,,asset / fixture / sample pack,subsystem donor,fixture donor,donor bench,repurpose,architecture only,"Retain the reusable internal layer, but replace shell assumptions and rebind boundaries so it plugs into HyperTwist cleanly.",,"Integrate selected subsystems rather than the whole product. Mine the repo for sample-model and environment-fixture selection, visual QA assets, and per-asset provenance handling; keep what materially shortens build time, but bind it to HyperTwist-owned data contracts, UI shell, and runtime boundaries.",,Integrate here means: merge bounded support surfaces from this repo into the HyperTwist companion stack.,,,,"the attribution file, mixed per-asset terms, sample-model and environment fixture role, and fetch-script behavior.","Inspect manifests, README/docs, LICENSE, ATTRIBUTIONS, fixture assets, and asset-fetch scripts. Verify container license versus per-asset terms.","Audit google/model-viewer/packages/shared-assets as a Browser sample-asset and fixture pack candidate for HyperTwist. Inspect the attribution file, mixed per-asset terms, sample-model and environment fixture role, and fetch-script behavior. Decide whether the retained value should remain active and what should stay bounded outside the HyperTwist core.",,,,,,,,,,,,,,medium,"Canonized Markdown dossier exists and the repo has been source-backed, but CSV backfill is later than the original v6.3 board generation.",medium,Source-backed dossier exists and the repo has been reconciled into the later Markdown authority stack.,,,,,,,,,,,,HT_browser_support,HT_browser_support_0009,asset / fixture / sample pack,"Integrate selectively for HyperTwist. Its source-backed role is a boundary-sensitive sample-asset and test-fixture pack with mixed per-asset terms, not a blanket shippable asset bundle.",HyperTwist,asset / fixture / sample pack,integrate,moderate modification,medium,google/model-viewer/packages/shared-assets,,,,,,,,,,,,,,,,,,Apache-2.0 container; mixed per-asset terms,known_from_reference_material,uploaded_reference_docs,,,,,,,,,,Backfilled from canonized Markdown dossier pass on 2026-04-25: 67-google-shared-assets-upstream-dossier.md,,,,Donor Bench,Boundary-sensitive sample-asset and test-fixture pack,Included,P3,mixed_or_boundary_sensitive_known,bounded_sidecar_or_selective_reimplementation,"The package container is Apache-2.0, but the actual payloads carry mixed per-asset terms. Treat it as a whitelisted fixture pack, not a blanket shippable asset source.",Whitelist individual acceptable assets only; do not assume the container license overrides per-asset terms.,Preserve container notices and review each selected asset attribution or usage condition separately before shipping.,"Usually unnecessary; the main issue is per-asset provenance and selection, not code replacement.",high,mixed-asset-whitelist-review,no,,,,,,,,,,,,,v6.3_markdown_backfill,Corrected on 2026-04-25 from stale merge posture to dossier-backed boundary-sensitive fixture-pack status.,selected_not_live_boundary_sensitive,phase0r_boundary_sensitive_eval_then_adapter_or_sidecar,Phase 1R closed. Retain as a Phase 4R fixture and QA pack only; allowlist each asset before any shipping use. -,pmndrs/react-postprocessing,https://github.com/pmndrs/react-postprocessing,HyperTwist,,,,,interface / visualization / shell surface,subsystem donor,dependency donor,merge bench,integrate,moderate modification,"Retain the reusable internal layer, but replace shell assumptions and rebind boundaries so it plugs into HyperTwist cleanly.",,"Integrate selected subsystems rather than the whole product. Mine the repo for React-side effect orchestration, selection-based emphasis behavior, and wrapper ergonomics above browser post-processing; keep what materially shortens build time, but bind it to HyperTwist-owned data contracts, UI shell, and runtime boundaries.",,Integrate here means: merge bounded support surfaces from this repo into the HyperTwist companion stack.,,,,"the React EffectComposer wrapper, Selection model, and integration assumptions on top of postprocessing and react-three-fiber.","Inspect manifests, README/docs, EffectComposer wrapper, Selection support, and the narrow React integration layer.","Audit pmndrs/react-postprocessing as a Browser React effect-wrapper layer candidate for HyperTwist. Inspect the React EffectComposer wrapper, Selection model, and integration assumptions on top of postprocessing and react-three-fiber. Decide whether the retained value should remain active and what should stay bounded outside the HyperTwist core.",,,,,,,,,,,,,,medium,"Canonized Markdown dossier exists and the repo has been source-backed, but CSV backfill is later than the original v6.3 board generation.",medium,Source-backed dossier exists and the repo has been reconciled into the later Markdown authority stack.,,,,,,,,,,,,HT_browser_support,HT_browser_support_0010,browser / 3D / XR / presentation,"Integrate selectively for HyperTwist. Its source-backed role is a bounded React wrapper for the browser post-processing lane, not a standalone product lane.",HyperTwist,browser / 3D / XR / presentation,integrate,moderate modification,medium,pmndrs/react-postprocessing,,,,,,,,,,,,,,,,,,MIT,known_from_reference_material,uploaded_reference_docs,,,,,,,,,,Backfilled from canonized Markdown dossier pass on 2026-04-25: 70-pmndrs-react-postprocessing-upstream-dossier.md,,,,Merge Bench,Browser React effect-wrapper layer,Included,P4,permissive_or_noncopyleft_known,direct_incorporation_ok,The code license is MIT and direct use is allowed. Treat it as a bounded React wrapper layer above browser post-processing.,Use directly as a bounded browser-side wrapper dependency above the core post-processing substrate.,"Typically preserve notices, attribution, and license text where required.",Usually unnecessary unless later product-shaping concerns make selective replacement attractive.,high,standard-notice-review,yes,,,,,,,,,,,,,v6.3_markdown_backfill,Backfilled from canonized Markdown dossier pass on 2026-04-25: 70-pmndrs-react-postprocessing-upstream-dossier.md,selected_not_live_permissive_candidate,phase0r_permissive_eval_then_implement,"Phase 1R closed. Retain as a Phase 3R permissive implementation candidate; implement only from its packet authority and the retained-set contract, not by reopening Phase 0R." -,pmndrs/three-stdlib,https://github.com/pmndrs/three-stdlib,HyperTwist,,,,,interface / visualization / shell surface,subsystem donor,dependency donor,merge bench,integrate,moderate modification,"Retain the reusable internal layer, but replace shell assumptions and rebind boundaries so it plugs into HyperTwist cleanly.",,"Integrate selected subsystems rather than the whole product. Mine the repo for browser-side utility helpers, controls, loaders, and XR-adjacent primitives beneath the browser companion stack; keep what materially shortens build time, but bind it to HyperTwist-owned data contracts, UI shell, and runtime boundaries.",,Integrate here means: merge bounded support surfaces from this repo into the HyperTwist companion stack.,,,,"the utility export surface, controls, loaders, WebXR helpers, post-processing helpers, and packaging of three/examples behavior.","Inspect manifests, README/docs, utility index, controls, WebXR helpers, loaders, and exported utility modules.","Audit pmndrs/three-stdlib as a Browser 3D utility substrate candidate for HyperTwist. Inspect the utility export surface, controls, loaders, WebXR helpers, post-processing helpers, and packaging of three/examples behavior. Decide whether the retained value should remain active and what should stay bounded outside the HyperTwist core.",,,,,,,,,,,,,,medium,"Canonized Markdown dossier exists and the repo has been source-backed, but CSV backfill is later than the original v6.3 board generation.",medium,Source-backed dossier exists and the repo has been reconciled into the later Markdown authority stack.,,,,,,,,,,,,HT_browser_support,HT_browser_support_0011,browser / 3D / XR / presentation,"Integrate selectively for HyperTwist. Its source-backed role is a lower-level browser utility substrate beneath three.js, drei, and XR-adjacent lanes, not a product lane.",HyperTwist,browser / 3D / XR / presentation,integrate,moderate modification,medium,pmndrs/three-stdlib,,,,,,,,,,,,,,,,,,MIT,known_from_reference_material,uploaded_reference_docs,,,,,,,,,,Backfilled from canonized Markdown dossier pass on 2026-04-25: 75-pmndrs-three-stdlib-upstream-dossier.md,,,,Merge Bench,Browser 3D utility substrate,Included,P4,permissive_or_noncopyleft_known,direct_incorporation_ok,The code license is MIT and direct use is allowed. Treat it as a bounded utility substrate beneath three.js-adjacent browser lanes.,Use directly as a bounded browser-side utility dependency beneath higher-level viewer and XR layers.,"Typically preserve notices, attribution, and license text where required.",Usually unnecessary unless later product-shaping concerns make selective replacement attractive.,high,standard-notice-review,yes,,,,,,,,,,,,,v6.3_markdown_backfill,Backfilled from canonized Markdown dossier pass on 2026-04-25: 75-pmndrs-three-stdlib-upstream-dossier.md,selected_not_live_permissive_candidate,phase0r_permissive_eval_then_implement,"Phase 1R closed. Retain as a Phase 3R permissive implementation candidate; implement only from its packet authority and the retained-set contract, not by reopening Phase 0R." -,pmndrs/maath,https://github.com/pmndrs/maath,HyperTwist,,,,,interface / visualization / shell surface,subsystem donor,dependency donor,merge bench,integrate,moderate modification,"Retain the reusable internal layer, but replace shell assumptions and rebind boundaries so it plugs into HyperTwist cleanly.",,"Integrate selected subsystems rather than the whole product. Mine the repo for browser-side easing, damping, sampling, and geometry helper behavior beneath interactive surfaces; keep what materially shortens build time, but bind it to HyperTwist-owned data contracts, UI shell, and runtime boundaries.",,Integrate here means: merge bounded support surfaces from this repo into the HyperTwist companion stack.,,,,"the easing runtime, random helpers, geometry utilities, and three.js-oriented math surfaces.","Inspect manifests, README/docs, math package exports, easing, geometry, and random helper modules.","Audit pmndrs/maath as a Browser math-helper substrate candidate for HyperTwist. Inspect the easing runtime, random helpers, geometry utilities, and three.js-oriented math surfaces. Decide whether the retained value should remain active and what should stay bounded outside the HyperTwist core.",,,,,,,,,,,,,,medium,"Canonized Markdown dossier exists and the repo has been source-backed, but CSV backfill is later than the original v6.3 board generation.",medium,Source-backed dossier exists and the repo has been reconciled into the later Markdown authority stack.,,,,,,,,,,,,HT_browser_support,HT_browser_support_0012,browser / utilities / math,"Integrate selectively for HyperTwist. Its source-backed role is a lower-level browser math-helper substrate beneath viewer and XR-adjacent lanes, not a product lane.",HyperTwist,browser / utilities / math,integrate,moderate modification,medium,pmndrs/maath,,,,,,,,,,,,,,,,,,MIT,known_from_reference_material,uploaded_reference_docs,,,,,,,,,,Backfilled from canonized Markdown dossier pass on 2026-04-25: 76-pmndrs-maath-upstream-dossier.md,,,,Merge Bench,Browser math-helper substrate,Included,P4,permissive_or_noncopyleft_known,direct_incorporation_ok,The code license is MIT and direct use is allowed. Treat it as a bounded math-helper substrate.,Use directly as a bounded browser-side utility dependency beneath higher-level interactive layers.,"Typically preserve notices, attribution, and license text where required.",Usually unnecessary unless later product-shaping concerns make selective replacement attractive.,high,standard-notice-review,yes,,,,,,,,,,,,,v6.3_markdown_backfill,Backfilled from canonized Markdown dossier pass on 2026-04-25: 76-pmndrs-maath-upstream-dossier.md,selected_not_live_permissive_candidate,phase0r_permissive_eval_then_implement,"Phase 1R closed. Retain as a Phase 3R permissive implementation candidate; implement only from its packet authority and the retained-set contract, not by reopening Phase 0R." -,pmndrs/zustand,https://github.com/pmndrs/zustand,HyperTwist,,,,,interface / visualization / shell surface,subsystem donor,dependency donor,donor bench,repurpose,moderate modification,"Retain the valuable internal layer, but expect to replace upstream shell assumptions and rebind boundaries so it fits the HyperTwist architecture.",,"Repurpose selected subsystems rather than the whole product. Mine the repo for browser-side state management, selector subscriptions, hydration, and bridging between non-React logic and React views; keep what materially shortens build time, but bind it to HyperTwist-owned data contracts, UI shell, and runtime boundaries.",,Repurpose here means: extract bounded support surfaces from this repo without inheriting the full upstream shell.,,,,"the vanilla store kernel, React bridge, selector subscriptions, persist middleware, devtools integration, and equality-aware selection behavior.","Inspect manifests, README/docs, vanilla store, react bindings, traditional selector helpers, and middleware modules.","Audit pmndrs/zustand as a Browser state-management substrate candidate for HyperTwist. Inspect the vanilla store kernel, React bridge, selector subscriptions, persist middleware, devtools integration, and equality-aware selection behavior. Decide whether the retained value should remain active and what should stay bounded outside the HyperTwist core.",,,,,,,,,,,,,,medium,"Canonized Markdown dossier exists and the repo has been source-backed, but CSV backfill is later than the original v6.3 board generation.",medium,Source-backed dossier exists and the repo has been reconciled into the later Markdown authority stack.,,,,,,,,,,,,HT_browser_support,HT_browser_support_0013,browser / state / interaction,"Repurpose selectively for HyperTwist. Its source-backed role is a commodity strategic dependency for browser-side state management and selector subscriptions, not product differentiation.",HyperTwist,browser / state / interaction,repurpose,moderate modification,medium,pmndrs/zustand,,,,,,,,,,,,,,,,,,MIT,known_from_reference_material,uploaded_reference_docs,,,,,,,,,,Backfilled from canonized Markdown dossier pass on 2026-04-25: 77-pmndrs-zustand-upstream-dossier.md,,,,Donor Bench,Browser state-management substrate,Included,P3,permissive_or_noncopyleft_known,direct_incorporation_ok,The code license is MIT and direct use is allowed. Treat it as a bounded browser state-management substrate.,"Use directly as a bounded browser-side dependency for local state, selector subscriptions, and hydration behavior.","Typically preserve notices, attribution, and license text where required.",Usually unnecessary unless later product-shaping concerns make selective replacement attractive.,high,standard-notice-review,yes,,,,,,,,,,,,,v6.3_markdown_backfill,Backfilled from canonized Markdown dossier pass on 2026-04-25: 77-pmndrs-zustand-upstream-dossier.md,selected_not_live_permissive_candidate,phase0r_permissive_eval_then_implement,"Phase 1R closed. Retain as a Phase 3R permissive implementation candidate; implement only from its packet authority and the retained-set contract, not by reopening Phase 0R." -,pmndrs/leva,https://github.com/pmndrs/leva,HyperTwist,,,,,interface / visualization / shell surface,subsystem donor,interface donor,merge bench,integrate,moderate modification,"Retain the reusable internal layer, but replace shell assumptions and rebind boundaries so it plugs into HyperTwist cleanly.",,"Integrate selected subsystems rather than the whole product. Mine the repo for parameter editing, control-panel behavior, headless control surfaces, and companion-surface tuning workflows; keep what materially shortens build time, but bind it to HyperTwist-owned data contracts, UI shell, and runtime boundaries.",,Integrate here means: merge bounded support surfaces from this repo into the HyperTwist companion stack.,,,,"the control store, useControls schema parsing, plugin system, multi-panel behavior, and headless mode.","Inspect manifests, README/docs, store layer, useControls, panel components, plugin registration, and headless mode docs.","Audit pmndrs/leva as a Browser control-panel and parameter UI layer candidate for HyperTwist. Inspect the control store, useControls schema parsing, plugin system, multi-panel behavior, and headless mode. Decide whether the retained value should remain active and what should stay bounded outside the HyperTwist core.",,,,,,,,,,,,,,medium,"Canonized Markdown dossier exists and the repo has been source-backed, but CSV backfill is later than the original v6.3 board generation.",medium,Source-backed dossier exists and the repo has been reconciled into the later Markdown authority stack.,,,,,,,,,,,,HT_browser_support,HT_browser_support_0014,browser / state / interaction,"Integrate selectively for HyperTwist. Its source-backed role is a bounded control-panel and headless parameter-UI donor for browser companion surfaces, not a runtime foundation.",HyperTwist,browser / state / interaction,integrate,moderate modification,medium,pmndrs/leva,,,,,,,,,,,,,,,,,,MIT,known_from_reference_material,uploaded_reference_docs,,,,,,,,,,Backfilled from canonized Markdown dossier pass on 2026-04-25: 78-pmndrs-leva-upstream-dossier.md,,,,Merge Bench,Browser control-panel and parameter UI layer,Included,P4,permissive_or_noncopyleft_known,direct_incorporation_ok,The code license is MIT and direct use is allowed. Treat it as a bounded browser parameter-UI donor.,Use directly as a bounded browser-side dependency or concept donor for control panels and tuning UI.,"Typically preserve notices, attribution, and license text where required.",Usually unnecessary unless later product-shaping concerns make selective replacement attractive.,high,standard-notice-review,yes,,,,,,,,,,,,,v6.3_markdown_backfill,Backfilled from canonized Markdown dossier pass on 2026-04-25: 78-pmndrs-leva-upstream-dossier.md,selected_not_live_permissive_candidate,phase0r_permissive_eval_then_implement,"Phase 1R closed. Retain as a Phase 3R permissive implementation candidate; implement only from its packet authority and the retained-set contract, not by reopening Phase 0R." -,pmndrs/use-gesture,https://github.com/pmndrs/use-gesture,HyperTwist,,,,,interface / visualization / shell surface,subsystem donor,dependency donor,donor bench,repurpose,moderate modification,"Retain the valuable internal layer, but expect to replace upstream shell assumptions and rebind boundaries so it fits the HyperTwist architecture.",,"Repurpose selected subsystems rather than the whole product. Mine the repo for browser gesture handling, richer pointer input, drag and scroll behavior, and bounded interaction substrate; keep what materially shortens build time, but bind it to HyperTwist-owned data contracts, UI shell, and runtime boundaries.",,Repurpose here means: extract bounded support surfaces from this repo without inheriting the full upstream shell.,,,,"the core controller, drag engine, pointer capture and lock behavior, scroll prevention, and React versus vanilla bindings.","Inspect manifests, README/docs, controller, gesture engines, React bindings, vanilla bindings, and input config parsing.","Audit pmndrs/use-gesture as a Browser gesture and pointer-input substrate candidate for HyperTwist. Inspect the core controller, drag engine, pointer capture and lock behavior, scroll prevention, and React versus vanilla bindings. Decide whether the retained value should remain active and what should stay bounded outside the HyperTwist core.",,,,,,,,,,,,,,medium,"Canonized Markdown dossier exists and the repo has been source-backed, but CSV backfill is later than the original v6.3 board generation.",medium,Source-backed dossier exists and the repo has been reconciled into the later Markdown authority stack.,,,,,,,,,,,,HT_browser_support,HT_browser_support_0015,browser / state / interaction,"Repurpose selectively for HyperTwist. Its source-backed role is a commodity browser gesture and richer pointer-input substrate, not product differentiation.",HyperTwist,browser / state / interaction,repurpose,moderate modification,medium,pmndrs/use-gesture,,,,,,,,,,,,,,,,,,MIT,known_from_reference_material,uploaded_reference_docs,,,,,,,,,,Backfilled from canonized Markdown dossier pass on 2026-04-25: 79-pmndrs-use-gesture-upstream-dossier.md,,,,Donor Bench,Browser gesture and pointer-input substrate,Included,P3,permissive_or_noncopyleft_known,direct_incorporation_ok,The code license is MIT and direct use is allowed. Treat it as a bounded browser gesture and pointer-input substrate.,"Use directly as a bounded browser-side dependency for custom viewers, panels, and interaction surfaces.","Typically preserve notices, attribution, and license text where required.",Usually unnecessary unless later product-shaping concerns make selective replacement attractive.,high,standard-notice-review,yes,,,,,,,,,,,,,v6.3_markdown_backfill,Backfilled from canonized Markdown dossier pass on 2026-04-25: 79-pmndrs-use-gesture-upstream-dossier.md,selected_not_live_permissive_candidate,phase0r_permissive_eval_then_implement,"Phase 1R closed. Retain as a Phase 3R permissive implementation candidate; implement only from its packet authority and the retained-set contract, not by reopening Phase 0R." -,@react-spring/parallax,https://github.com/pmndrs/react-spring/tree/main/packages/parallax,HyperTwist,,,,,interface / visualization / shell surface,subsystem donor,interface donor,merge bench,integrate,moderate modification,"Retain the reusable internal layer, but replace shell assumptions and rebind boundaries so it plugs into HyperTwist cleanly.",,"Integrate selected subsystems rather than the whole product. Mine the repo for layered explainer behavior, scroll-driven motion, sticky layers, and narrative browser presentation; keep what materially shortens build time, but bind it to HyperTwist-owned data contracts, UI shell, and runtime boundaries.",,Integrate here means: merge bounded support surfaces from this repo into the HyperTwist companion stack.,,,,"the parallax runtime, sticky-layer behavior, scroll-driven spring motion, and imperative scrollTo flow.","Inspect manifests, README/docs, parallax package runtime, layer behavior, and scroll-controller code.","Audit @react-spring/parallax as a Browser layered-motion and explainer sidecar candidate for HyperTwist. Inspect the parallax runtime, sticky-layer behavior, scroll-driven spring motion, and imperative scrollTo flow. Decide whether the retained value should remain active and what should stay bounded outside the HyperTwist core.",,,,,,,,,,,,,,medium,"Canonized Markdown dossier exists and the repo has been source-backed, but CSV backfill is later than the original v6.3 board generation.",medium,Source-backed dossier exists and the repo has been reconciled into the later Markdown authority stack.,,,,,,,,,,,,HT_browser_support,HT_browser_support_0016,browser / 3D / XR / presentation,"Integrate selectively for HyperTwist. Its source-backed role is a bounded layered-motion and explainer sidecar beneath react-spring, not a runtime lane.",HyperTwist,browser / 3D / XR / presentation,integrate,moderate modification,medium,@react-spring/parallax,,,,,,,,,,,,,,,,,,MIT,known_from_reference_material,uploaded_reference_docs,,,,,,,,,,Backfilled from canonized Markdown dossier pass on 2026-04-25: 81-react-spring-parallax-upstream-dossier.md,,,,Merge Bench,Browser layered-motion and explainer sidecar,Included,P4,permissive_or_noncopyleft_known,direct_incorporation_ok,The code license is MIT and direct use is allowed. Treat it as a bounded layered-motion and explainer sidecar.,Use directly as a bounded browser-side dependency for explainer and narrative surfaces.,"Typically preserve notices, attribution, and license text where required.",Usually unnecessary unless later product-shaping concerns make selective replacement attractive.,high,standard-notice-review,yes,,,,,,,,,,,,,v6.3_markdown_backfill,Backfilled from canonized Markdown dossier pass on 2026-04-25: 81-react-spring-parallax-upstream-dossier.md,selected_not_live_permissive_candidate,phase0r_permissive_eval_then_implement,"Phase 1R closed. Retain as a Phase 3R permissive implementation candidate; implement only from its packet authority and the retained-set contract, not by reopening Phase 0R." -,@react-spring/rafz,https://github.com/pmndrs/react-spring/tree/main/packages/rafz,HyperTwist,,,,,interface / visualization / shell surface,subsystem donor,dependency donor,merge bench,integrate,moderate modification,"Retain the reusable internal layer, but replace shell assumptions and rebind boundaries so it plugs into HyperTwist cleanly.",,"Integrate selected subsystems rather than the whole product. Mine the repo for browser scheduling, phased queues, timeout handling, and motion-frame orchestration beneath higher-level UI motion; keep what materially shortens build time, but bind it to HyperTwist-owned data contracts, UI shell, and runtime boundaries.",,Integrate here means: merge bounded support surfaces from this repo into the HyperTwist companion stack.,,,,"the frame-loop phases, timeout scheduling, throttling, batched updates hook, and demand versus always control behavior.","Inspect manifests, README/docs, rafz package runtime, frame-loop scheduling, timeout handling, and queue behavior.","Audit @react-spring/rafz as a Browser frame-loop and scheduling utility candidate for HyperTwist. Inspect the frame-loop phases, timeout scheduling, throttling, batched updates hook, and demand versus always control behavior. Decide whether the retained value should remain active and what should stay bounded outside the HyperTwist core.",,,,,,,,,,,,,,medium,"Canonized Markdown dossier exists and the repo has been source-backed, but CSV backfill is later than the original v6.3 board generation.",medium,Source-backed dossier exists and the repo has been reconciled into the later Markdown authority stack.,,,,,,,,,,,,HT_browser_support,HT_browser_support_0017,browser / utilities / scheduling,"Integrate selectively for HyperTwist. Its source-backed role is a lower-level browser frame-loop and scheduling utility beneath react-spring, not a product lane.",HyperTwist,browser / utilities / scheduling,integrate,moderate modification,medium,@react-spring/rafz,,,,,,,,,,,,,,,,,,MIT,known_from_reference_material,uploaded_reference_docs,,,,,,,,,,Backfilled from canonized Markdown dossier pass on 2026-04-25: 82-react-spring-rafz-upstream-dossier.md,,,,Merge Bench,Browser frame-loop and scheduling utility,Included,P4,permissive_or_noncopyleft_known,direct_incorporation_ok,The code license is MIT and direct use is allowed. Treat it as a bounded browser scheduling utility.,Use directly as a bounded browser-side dependency beneath higher-level motion or interaction layers.,"Typically preserve notices, attribution, and license text where required.",Usually unnecessary unless later product-shaping concerns make selective replacement attractive.,high,standard-notice-review,yes,,,,,,,,,,,,,v6.3_markdown_backfill,Backfilled from canonized Markdown dossier pass on 2026-04-25: 82-react-spring-rafz-upstream-dossier.md,selected_not_live_permissive_candidate,phase0r_permissive_eval_then_implement,"Phase 1R closed. Retain as a Phase 3R permissive implementation candidate; implement only from its packet authority and the retained-set contract, not by reopening Phase 0R." -,@react-spring/animated,https://github.com/pmndrs/react-spring/tree/main/packages/animated,HyperTwist,,,,,interface / visualization / shell surface,subsystem donor,dependency donor,merge bench,integrate,moderate modification,"Retain the reusable internal layer, but replace shell assumptions and rebind boundaries so it plugs into HyperTwist cleanly.",,"Integrate selected subsystems rather than the whole product. Mine the repo for animatable-component hosting, animated-props observation, and low-level motion binding beneath higher-level browser motion; keep what materially shortens build time, but bind it to HyperTwist-owned data contracts, UI shell, and runtime boundaries.",,Integrate here means: merge bounded support surfaces from this repo into the HyperTwist companion stack.,,,,"the host-creation runtime, withAnimated wrapper, dependency observation, and native-update versus rerender behavior.","Inspect manifests, README/docs, animated package runtime, host creation, animated wrapper, and animated base-node behavior.","Audit @react-spring/animated as a Browser animatable-component substrate candidate for HyperTwist. Inspect the host-creation runtime, withAnimated wrapper, dependency observation, and native-update versus rerender behavior. Decide whether the retained value should remain active and what should stay bounded outside the HyperTwist core.",,,,,,,,,,,,,,medium,"Canonized Markdown dossier exists and the repo has been source-backed, but CSV backfill is later than the original v6.3 board generation.",medium,Source-backed dossier exists and the repo has been reconciled into the later Markdown authority stack.,,,,,,,,,,,,HT_browser_support,HT_browser_support_0018,browser / utilities / animation,"Integrate selectively for HyperTwist. Its source-backed role is a lower-level animatable-component host and animated-props substrate beneath react-spring, not a product lane.",HyperTwist,browser / utilities / animation,integrate,moderate modification,medium,@react-spring/animated,,,,,,,,,,,,,,,,,,MIT,known_from_reference_material,uploaded_reference_docs,,,,,,,,,,Backfilled from canonized Markdown dossier pass on 2026-04-25: 83-react-spring-animated-upstream-dossier.md,,,,Merge Bench,Browser animatable-component substrate,Included,P4,permissive_or_noncopyleft_known,direct_incorporation_ok,The code license is MIT and direct use is allowed. Treat it as a bounded animatable-component substrate.,Use directly as a bounded browser-side dependency beneath higher-level motion and UI layers.,"Typically preserve notices, attribution, and license text where required.",Usually unnecessary unless later product-shaping concerns make selective replacement attractive.,high,standard-notice-review,yes,,,,,,,,,,,,,v6.3_markdown_backfill,Backfilled from canonized Markdown dossier pass on 2026-04-25: 83-react-spring-animated-upstream-dossier.md,selected_not_live_permissive_candidate,phase0r_permissive_eval_then_implement,"Phase 1R closed. Retain as a Phase 3R permissive implementation candidate; implement only from its packet authority and the retained-set contract, not by reopening Phase 0R." -,@react-spring/core,https://github.com/pmndrs/react-spring/tree/main/packages/core,HyperTwist,,,,,interface / visualization / shell surface,subsystem donor,dependency donor,donor bench,repurpose,moderate modification,"Retain the valuable internal layer, but expect to replace upstream shell assumptions and rebind boundaries so it fits the HyperTwist architecture.",,"Repurpose selected subsystems rather than the whole product. Mine the repo for browser motion runtime, spring orchestration, frame advancement, and reusable motion-core behavior beneath higher-level UI layers; keep what materially shortens build time, but bind it to HyperTwist-owned data contracts, UI shell, and runtime boundaries.",,Repurpose here means: extract bounded support surfaces from this repo without inheriting the full upstream shell.,,,,"the Controller runtime, SpringValue motion engine, useSprings lifecycle, queueing, start-stop behavior, and frame advancement.","Inspect manifests, README/docs, core package runtime, Controller, SpringValue, and hook lifecycle behavior.","Audit @react-spring/core as a Browser spring-runtime core candidate for HyperTwist. Inspect the Controller runtime, SpringValue motion engine, useSprings lifecycle, queueing, start-stop behavior, and frame advancement. Decide whether the retained value should remain active and what should stay bounded outside the HyperTwist core.",,,,,,,,,,,,,,medium,"Canonized Markdown dossier exists and the repo has been source-backed, but CSV backfill is later than the original v6.3 board generation.",medium,Source-backed dossier exists and the repo has been reconciled into the later Markdown authority stack.,,,,,,,,,,,,HT_browser_support,HT_browser_support_0019,browser / utilities / animation,"Repurpose selectively for HyperTwist. Its source-backed role is the platform-agnostic spring-runtime core beneath react-spring, not a product foundation.",HyperTwist,browser / utilities / animation,repurpose,moderate modification,medium,@react-spring/core,,,,,,,,,,,,,,,,,,MIT,known_from_reference_material,uploaded_reference_docs,,,,,,,,,,Backfilled from canonized Markdown dossier pass on 2026-04-25: 84-react-spring-core-upstream-dossier.md,,,,Donor Bench,Browser spring-runtime core,Included,P3,permissive_or_noncopyleft_known,direct_incorporation_ok,The code license is MIT and direct use is allowed. Treat it as a bounded spring-runtime core beneath higher-level motion layers.,Use directly as a bounded browser-side dependency beneath higher-level motion and interaction layers.,"Typically preserve notices, attribution, and license text where required.",Usually unnecessary unless later product-shaping concerns make selective replacement attractive.,high,standard-notice-review,yes,,,,,,,,,,,,,v6.3_markdown_backfill,Backfilled from canonized Markdown dossier pass on 2026-04-25: 84-react-spring-core-upstream-dossier.md,selected_not_live_permissive_candidate,phase0r_permissive_eval_then_implement,"Phase 1R closed. Retain as a Phase 3R permissive implementation candidate; implement only from its packet authority and the retained-set contract, not by reopening Phase 0R." -,@react-spring/shared,https://github.com/pmndrs/react-spring/tree/main/packages/shared,HyperTwist,,,,,interface / visualization / shell surface,subsystem donor,dependency donor,merge bench,integrate,moderate modification,"Retain the reusable internal layer, but replace shell assumptions and rebind boundaries so it plugs into HyperTwist cleanly.",,"Integrate selected subsystems rather than the whole product. Mine the repo for motion utilities, frame-loop customization, interpolation, and fluid observation beneath higher-level browser motion; keep what materially shortens build time, but bind it to HyperTwist-owned data contracts, UI shell, and runtime boundaries.",,Integrate here means: merge bounded support surfaces from this repo into the HyperTwist companion stack.,,,,"the globals customization seams, frame-loop behavior, interpolation helpers, and fluid observer substrate.","Inspect manifests, README/docs, shared package exports, globals, frame loop, interpolation, and fluid observer modules.","Audit @react-spring/shared as a Browser motion utility substrate candidate for HyperTwist. Inspect the globals customization seams, frame-loop behavior, interpolation helpers, and fluid observer substrate. Decide whether the retained value should remain active and what should stay bounded outside the HyperTwist core.",,,,,,,,,,,,,,medium,"Canonized Markdown dossier exists and the repo has been source-backed, but CSV backfill is later than the original v6.3 board generation.",medium,Source-backed dossier exists and the repo has been reconciled into the later Markdown authority stack.,,,,,,,,,,,,HT_browser_support,HT_browser_support_0020,browser / utilities / animation,"Integrate selectively for HyperTwist. Its source-backed role is a lower-level motion utility and fluid-observer substrate beneath react-spring, not a product lane.",HyperTwist,browser / utilities / animation,integrate,moderate modification,medium,@react-spring/shared,,,,,,,,,,,,,,,,,,MIT,known_from_reference_material,uploaded_reference_docs,,,,,,,,,,Backfilled from canonized Markdown dossier pass on 2026-04-25: 85-react-spring-shared-upstream-dossier.md,,,,Merge Bench,Browser motion utility substrate,Included,P4,permissive_or_noncopyleft_known,direct_incorporation_ok,The code license is MIT and direct use is allowed. Treat it as a bounded motion utility substrate.,Use directly as a bounded browser-side dependency beneath higher-level motion layers.,"Typically preserve notices, attribution, and license text where required.",Usually unnecessary unless later product-shaping concerns make selective replacement attractive.,high,standard-notice-review,yes,,,,,,,,,,,,,v6.3_markdown_backfill,Backfilled from canonized Markdown dossier pass on 2026-04-25: 85-react-spring-shared-upstream-dossier.md,selected_not_live_permissive_candidate,phase0r_permissive_eval_then_implement,"Phase 1R closed. Retain as a Phase 3R permissive implementation candidate; implement only from its packet authority and the retained-set contract, not by reopening Phase 0R." -,@react-spring/types,https://github.com/pmndrs/react-spring/tree/main/packages/types,HyperTwist,,,,,interface / visualization / shell surface,subsystem donor,dependency donor,merge bench,integrate,moderate modification,"Retain the reusable internal layer, but replace shell assumptions and rebind boundaries so it plugs into HyperTwist cleanly.",,"Integrate selected subsystems rather than the whole product. Mine the repo for shared type contracts and package-design substrate beneath browser motion layers; keep what materially shortens build time, but bind it to HyperTwist-owned data contracts, UI shell, and runtime boundaries.",,Integrate here means: merge bounded support surfaces from this repo into the HyperTwist companion stack.,,,,"the shared type-contract surface, animatable and interpolation types, and utility-type exports used across react-spring packages.","Inspect manifests, type package exports, shared type files, interpolation type definitions, and utility-type modules.","Audit @react-spring/types as a Browser motion type-contract substrate candidate for HyperTwist. Inspect the shared type-contract surface, animatable and interpolation types, and utility-type exports used across react-spring packages. Decide whether the retained value should remain active and what should stay bounded outside the HyperTwist core.",,,,,,,,,,,,,,medium,"Canonized Markdown dossier exists and the repo has been source-backed, but CSV backfill is later than the original v6.3 board generation.",medium,Source-backed dossier exists and the repo has been reconciled into the later Markdown authority stack.,,,,,,,,,,,,HT_browser_support,HT_browser_support_0021,browser / utilities / animation,"Integrate selectively for HyperTwist. Its source-backed role is a narrow type-contract substrate beneath react-spring, not a behavior-heavy donor or product lane.",HyperTwist,browser / utilities / animation,integrate,moderate modification,medium,@react-spring/types,,,,,,,,,,,,,,,,,,MIT,known_from_reference_material,uploaded_reference_docs,,,,,,,,,,Backfilled from canonized Markdown dossier pass on 2026-04-25: 86-react-spring-types-upstream-dossier.md,,,,Merge Bench,Browser motion type-contract substrate,Included,P4,permissive_or_noncopyleft_known,direct_incorporation_ok,The code license is MIT and direct use is allowed. Treat it as a bounded type-contract substrate.,Use directly as a bounded browser-side dependency where those contracts are actually needed.,"Typically preserve notices, attribution, and license text where required.",Usually unnecessary unless later product-shaping concerns make selective replacement attractive.,high,standard-notice-review,yes,,,,,,,,,,,,,v6.3_markdown_backfill,Backfilled from canonized Markdown dossier pass on 2026-04-25: 86-react-spring-types-upstream-dossier.md,selected_not_live_permissive_candidate,phase0r_permissive_eval_then_implement,"Phase 1R closed. Retain as a Phase 3R permissive implementation candidate; implement only from its packet authority and the retained-set contract, not by reopening Phase 0R." +,pmndrs/react-postprocessing,https://github.com/pmndrs/react-postprocessing,HyperTwist,,,,,interface / visualization / shell surface,subsystem donor,dependency donor,merge bench,integrate,moderate modification,"Retain the reusable internal layer, but replace shell assumptions and rebind boundaries so it plugs into HyperTwist cleanly.",,"Integrate selected subsystems rather than the whole product. Mine the repo for React-side effect orchestration, selection-based emphasis behavior, and wrapper ergonomics above browser post-processing; keep what materially shortens build time, but bind it to HyperTwist-owned data contracts, UI shell, and runtime boundaries.",,Integrate here means: merge bounded support surfaces from this repo into the HyperTwist companion stack.,,,,"the React EffectComposer wrapper, Selection model, and integration assumptions on top of postprocessing and react-three-fiber.","Inspect manifests, README/docs, EffectComposer wrapper, Selection support, and the narrow React integration layer.","Audit pmndrs/react-postprocessing as a Browser React effect-wrapper layer candidate for HyperTwist. Inspect the React EffectComposer wrapper, Selection model, and integration assumptions on top of postprocessing and react-three-fiber. Decide whether the retained value should remain active and what should stay bounded outside the HyperTwist core.",,,,,,,,,,,,,,medium,"Canonized Markdown dossier exists and the repo has been source-backed, but CSV backfill is later than the original v6.3 board generation.",medium,Source-backed dossier exists and the repo has been reconciled into the later Markdown authority stack.,,,,,,,,,,,,HT_browser_support,HT_browser_support_0010,browser / 3D / XR / presentation,"Integrate selectively for HyperTwist. Its source-backed role is a bounded React wrapper for the browser post-processing lane, not a standalone product lane.",HyperTwist,browser / 3D / XR / presentation,integrate,moderate modification,medium,pmndrs/react-postprocessing,,,,,,,,,,,,,,,,,,MIT,known_from_reference_material,uploaded_reference_docs,,,,,,,,,,Backfilled from canonized Markdown dossier pass on 2026-04-25: 70-pmndrs-react-postprocessing-upstream-dossier.md,,,,Merge Bench,Browser React effect-wrapper layer,Included,P4,permissive_or_noncopyleft_known,direct_incorporation_ok,The code license is MIT and direct use is allowed. Treat it as a bounded React wrapper layer above browser post-processing.,Use directly as a bounded browser-side wrapper dependency above the core post-processing substrate.,"Typically preserve notices, attribution, and license text where required.",Usually unnecessary unless later product-shaping concerns make selective replacement attractive.,high,standard-notice-review,yes,,,,,,,,,,,,,v6.3_markdown_backfill,Backfilled from canonized Markdown dossier pass on 2026-04-25: 70-pmndrs-react-postprocessing-upstream-dossier.md,implemented_live_permissive,landed_permissive_preserve,"Phase 3R-E closed. Preserve as the landed first-party embodied companion, narration, lip-sync, gesture, subtitle, and avatar-embed lane; start future widening from the live-lane audit, then the 3R-E implementation packet, then REPO_LICENSE_TRACKING.md." +,pmndrs/three-stdlib,https://github.com/pmndrs/three-stdlib,HyperTwist,,,,,interface / visualization / shell surface,subsystem donor,dependency donor,merge bench,integrate,moderate modification,"Retain the reusable internal layer, but replace shell assumptions and rebind boundaries so it plugs into HyperTwist cleanly.",,"Integrate selected subsystems rather than the whole product. Mine the repo for browser-side utility helpers, controls, loaders, and XR-adjacent primitives beneath the browser companion stack; keep what materially shortens build time, but bind it to HyperTwist-owned data contracts, UI shell, and runtime boundaries.",,Integrate here means: merge bounded support surfaces from this repo into the HyperTwist companion stack.,,,,"the utility export surface, controls, loaders, WebXR helpers, post-processing helpers, and packaging of three/examples behavior.","Inspect manifests, README/docs, utility index, controls, WebXR helpers, loaders, and exported utility modules.","Audit pmndrs/three-stdlib as a Browser 3D utility substrate candidate for HyperTwist. Inspect the utility export surface, controls, loaders, WebXR helpers, post-processing helpers, and packaging of three/examples behavior. Decide whether the retained value should remain active and what should stay bounded outside the HyperTwist core.",,,,,,,,,,,,,,medium,"Canonized Markdown dossier exists and the repo has been source-backed, but CSV backfill is later than the original v6.3 board generation.",medium,Source-backed dossier exists and the repo has been reconciled into the later Markdown authority stack.,,,,,,,,,,,,HT_browser_support,HT_browser_support_0011,browser / 3D / XR / presentation,"Integrate selectively for HyperTwist. Its source-backed role is a lower-level browser utility substrate beneath three.js, drei, and XR-adjacent lanes, not a product lane.",HyperTwist,browser / 3D / XR / presentation,integrate,moderate modification,medium,pmndrs/three-stdlib,,,,,,,,,,,,,,,,,,MIT,known_from_reference_material,uploaded_reference_docs,,,,,,,,,,Backfilled from canonized Markdown dossier pass on 2026-04-25: 75-pmndrs-three-stdlib-upstream-dossier.md,,,,Merge Bench,Browser 3D utility substrate,Included,P4,permissive_or_noncopyleft_known,direct_incorporation_ok,The code license is MIT and direct use is allowed. Treat it as a bounded utility substrate beneath three.js-adjacent browser lanes.,Use directly as a bounded browser-side utility dependency beneath higher-level viewer and XR layers.,"Typically preserve notices, attribution, and license text where required.",Usually unnecessary unless later product-shaping concerns make selective replacement attractive.,high,standard-notice-review,yes,,,,,,,,,,,,,v6.3_markdown_backfill,Backfilled from canonized Markdown dossier pass on 2026-04-25: 75-pmndrs-three-stdlib-upstream-dossier.md,implemented_live_permissive,landed_permissive_preserve,"Phase 3R-E closed. Preserve as the landed first-party embodied companion, narration, lip-sync, gesture, subtitle, and avatar-embed lane; start future widening from the live-lane audit, then the 3R-E implementation packet, then REPO_LICENSE_TRACKING.md." +,pmndrs/maath,https://github.com/pmndrs/maath,HyperTwist,,,,,interface / visualization / shell surface,subsystem donor,dependency donor,merge bench,integrate,moderate modification,"Retain the reusable internal layer, but replace shell assumptions and rebind boundaries so it plugs into HyperTwist cleanly.",,"Integrate selected subsystems rather than the whole product. Mine the repo for browser-side easing, damping, sampling, and geometry helper behavior beneath interactive surfaces; keep what materially shortens build time, but bind it to HyperTwist-owned data contracts, UI shell, and runtime boundaries.",,Integrate here means: merge bounded support surfaces from this repo into the HyperTwist companion stack.,,,,"the easing runtime, random helpers, geometry utilities, and three.js-oriented math surfaces.","Inspect manifests, README/docs, math package exports, easing, geometry, and random helper modules.","Audit pmndrs/maath as a Browser math-helper substrate candidate for HyperTwist. Inspect the easing runtime, random helpers, geometry utilities, and three.js-oriented math surfaces. Decide whether the retained value should remain active and what should stay bounded outside the HyperTwist core.",,,,,,,,,,,,,,medium,"Canonized Markdown dossier exists and the repo has been source-backed, but CSV backfill is later than the original v6.3 board generation.",medium,Source-backed dossier exists and the repo has been reconciled into the later Markdown authority stack.,,,,,,,,,,,,HT_browser_support,HT_browser_support_0012,browser / utilities / math,"Integrate selectively for HyperTwist. Its source-backed role is a lower-level browser math-helper substrate beneath viewer and XR-adjacent lanes, not a product lane.",HyperTwist,browser / utilities / math,integrate,moderate modification,medium,pmndrs/maath,,,,,,,,,,,,,,,,,,MIT,known_from_reference_material,uploaded_reference_docs,,,,,,,,,,Backfilled from canonized Markdown dossier pass on 2026-04-25: 76-pmndrs-maath-upstream-dossier.md,,,,Merge Bench,Browser math-helper substrate,Included,P4,permissive_or_noncopyleft_known,direct_incorporation_ok,The code license is MIT and direct use is allowed. Treat it as a bounded math-helper substrate.,Use directly as a bounded browser-side utility dependency beneath higher-level interactive layers.,"Typically preserve notices, attribution, and license text where required.",Usually unnecessary unless later product-shaping concerns make selective replacement attractive.,high,standard-notice-review,yes,,,,,,,,,,,,,v6.3_markdown_backfill,Backfilled from canonized Markdown dossier pass on 2026-04-25: 76-pmndrs-maath-upstream-dossier.md,implemented_live_permissive,landed_permissive_preserve,"Phase 3R-E closed. Preserve as the landed first-party embodied companion, narration, lip-sync, gesture, subtitle, and avatar-embed lane; start future widening from the live-lane audit, then the 3R-E implementation packet, then REPO_LICENSE_TRACKING.md." +,pmndrs/zustand,https://github.com/pmndrs/zustand,HyperTwist,,,,,interface / visualization / shell surface,subsystem donor,dependency donor,donor bench,repurpose,moderate modification,"Retain the valuable internal layer, but expect to replace upstream shell assumptions and rebind boundaries so it fits the HyperTwist architecture.",,"Repurpose selected subsystems rather than the whole product. Mine the repo for browser-side state management, selector subscriptions, hydration, and bridging between non-React logic and React views; keep what materially shortens build time, but bind it to HyperTwist-owned data contracts, UI shell, and runtime boundaries.",,Repurpose here means: extract bounded support surfaces from this repo without inheriting the full upstream shell.,,,,"the vanilla store kernel, React bridge, selector subscriptions, persist middleware, devtools integration, and equality-aware selection behavior.","Inspect manifests, README/docs, vanilla store, react bindings, traditional selector helpers, and middleware modules.","Audit pmndrs/zustand as a Browser state-management substrate candidate for HyperTwist. Inspect the vanilla store kernel, React bridge, selector subscriptions, persist middleware, devtools integration, and equality-aware selection behavior. Decide whether the retained value should remain active and what should stay bounded outside the HyperTwist core.",,,,,,,,,,,,,,medium,"Canonized Markdown dossier exists and the repo has been source-backed, but CSV backfill is later than the original v6.3 board generation.",medium,Source-backed dossier exists and the repo has been reconciled into the later Markdown authority stack.,,,,,,,,,,,,HT_browser_support,HT_browser_support_0013,browser / state / interaction,"Repurpose selectively for HyperTwist. Its source-backed role is a commodity strategic dependency for browser-side state management and selector subscriptions, not product differentiation.",HyperTwist,browser / state / interaction,repurpose,moderate modification,medium,pmndrs/zustand,,,,,,,,,,,,,,,,,,MIT,known_from_reference_material,uploaded_reference_docs,,,,,,,,,,Backfilled from canonized Markdown dossier pass on 2026-04-25: 77-pmndrs-zustand-upstream-dossier.md,,,,Donor Bench,Browser state-management substrate,Included,P3,permissive_or_noncopyleft_known,direct_incorporation_ok,The code license is MIT and direct use is allowed. Treat it as a bounded browser state-management substrate.,"Use directly as a bounded browser-side dependency for local state, selector subscriptions, and hydration behavior.","Typically preserve notices, attribution, and license text where required.",Usually unnecessary unless later product-shaping concerns make selective replacement attractive.,high,standard-notice-review,yes,,,,,,,,,,,,,v6.3_markdown_backfill,Backfilled from canonized Markdown dossier pass on 2026-04-25: 77-pmndrs-zustand-upstream-dossier.md,implemented_live_permissive,landed_permissive_preserve,"Phase 3R-E closed. Preserve as the landed first-party embodied companion, narration, lip-sync, gesture, subtitle, and avatar-embed lane; start future widening from the live-lane audit, then the 3R-E implementation packet, then REPO_LICENSE_TRACKING.md." +,pmndrs/leva,https://github.com/pmndrs/leva,HyperTwist,,,,,interface / visualization / shell surface,subsystem donor,interface donor,merge bench,integrate,moderate modification,"Retain the reusable internal layer, but replace shell assumptions and rebind boundaries so it plugs into HyperTwist cleanly.",,"Integrate selected subsystems rather than the whole product. Mine the repo for parameter editing, control-panel behavior, headless control surfaces, and companion-surface tuning workflows; keep what materially shortens build time, but bind it to HyperTwist-owned data contracts, UI shell, and runtime boundaries.",,Integrate here means: merge bounded support surfaces from this repo into the HyperTwist companion stack.,,,,"the control store, useControls schema parsing, plugin system, multi-panel behavior, and headless mode.","Inspect manifests, README/docs, store layer, useControls, panel components, plugin registration, and headless mode docs.","Audit pmndrs/leva as a Browser control-panel and parameter UI layer candidate for HyperTwist. Inspect the control store, useControls schema parsing, plugin system, multi-panel behavior, and headless mode. Decide whether the retained value should remain active and what should stay bounded outside the HyperTwist core.",,,,,,,,,,,,,,medium,"Canonized Markdown dossier exists and the repo has been source-backed, but CSV backfill is later than the original v6.3 board generation.",medium,Source-backed dossier exists and the repo has been reconciled into the later Markdown authority stack.,,,,,,,,,,,,HT_browser_support,HT_browser_support_0014,browser / state / interaction,"Integrate selectively for HyperTwist. Its source-backed role is a bounded control-panel and headless parameter-UI donor for browser companion surfaces, not a runtime foundation.",HyperTwist,browser / state / interaction,integrate,moderate modification,medium,pmndrs/leva,,,,,,,,,,,,,,,,,,MIT,known_from_reference_material,uploaded_reference_docs,,,,,,,,,,Backfilled from canonized Markdown dossier pass on 2026-04-25: 78-pmndrs-leva-upstream-dossier.md,,,,Merge Bench,Browser control-panel and parameter UI layer,Included,P4,permissive_or_noncopyleft_known,direct_incorporation_ok,The code license is MIT and direct use is allowed. Treat it as a bounded browser parameter-UI donor.,Use directly as a bounded browser-side dependency or concept donor for control panels and tuning UI.,"Typically preserve notices, attribution, and license text where required.",Usually unnecessary unless later product-shaping concerns make selective replacement attractive.,high,standard-notice-review,yes,,,,,,,,,,,,,v6.3_markdown_backfill,Backfilled from canonized Markdown dossier pass on 2026-04-25: 78-pmndrs-leva-upstream-dossier.md,implemented_live_permissive,landed_permissive_preserve,"Phase 3R-E closed. Preserve as the landed first-party embodied companion, narration, lip-sync, gesture, subtitle, and avatar-embed lane; start future widening from the live-lane audit, then the 3R-E implementation packet, then REPO_LICENSE_TRACKING.md." +,pmndrs/use-gesture,https://github.com/pmndrs/use-gesture,HyperTwist,,,,,interface / visualization / shell surface,subsystem donor,dependency donor,donor bench,repurpose,moderate modification,"Retain the valuable internal layer, but expect to replace upstream shell assumptions and rebind boundaries so it fits the HyperTwist architecture.",,"Repurpose selected subsystems rather than the whole product. Mine the repo for browser gesture handling, richer pointer input, drag and scroll behavior, and bounded interaction substrate; keep what materially shortens build time, but bind it to HyperTwist-owned data contracts, UI shell, and runtime boundaries.",,Repurpose here means: extract bounded support surfaces from this repo without inheriting the full upstream shell.,,,,"the core controller, drag engine, pointer capture and lock behavior, scroll prevention, and React versus vanilla bindings.","Inspect manifests, README/docs, controller, gesture engines, React bindings, vanilla bindings, and input config parsing.","Audit pmndrs/use-gesture as a Browser gesture and pointer-input substrate candidate for HyperTwist. Inspect the core controller, drag engine, pointer capture and lock behavior, scroll prevention, and React versus vanilla bindings. Decide whether the retained value should remain active and what should stay bounded outside the HyperTwist core.",,,,,,,,,,,,,,medium,"Canonized Markdown dossier exists and the repo has been source-backed, but CSV backfill is later than the original v6.3 board generation.",medium,Source-backed dossier exists and the repo has been reconciled into the later Markdown authority stack.,,,,,,,,,,,,HT_browser_support,HT_browser_support_0015,browser / state / interaction,"Repurpose selectively for HyperTwist. Its source-backed role is a commodity browser gesture and richer pointer-input substrate, not product differentiation.",HyperTwist,browser / state / interaction,repurpose,moderate modification,medium,pmndrs/use-gesture,,,,,,,,,,,,,,,,,,MIT,known_from_reference_material,uploaded_reference_docs,,,,,,,,,,Backfilled from canonized Markdown dossier pass on 2026-04-25: 79-pmndrs-use-gesture-upstream-dossier.md,,,,Donor Bench,Browser gesture and pointer-input substrate,Included,P3,permissive_or_noncopyleft_known,direct_incorporation_ok,The code license is MIT and direct use is allowed. Treat it as a bounded browser gesture and pointer-input substrate.,"Use directly as a bounded browser-side dependency for custom viewers, panels, and interaction surfaces.","Typically preserve notices, attribution, and license text where required.",Usually unnecessary unless later product-shaping concerns make selective replacement attractive.,high,standard-notice-review,yes,,,,,,,,,,,,,v6.3_markdown_backfill,Backfilled from canonized Markdown dossier pass on 2026-04-25: 79-pmndrs-use-gesture-upstream-dossier.md,implemented_live_permissive,landed_permissive_preserve,"Phase 3R-E closed. Preserve as the landed first-party embodied companion, narration, lip-sync, gesture, subtitle, and avatar-embed lane; start future widening from the live-lane audit, then the 3R-E implementation packet, then REPO_LICENSE_TRACKING.md." +,@react-spring/parallax,https://github.com/pmndrs/react-spring/tree/main/packages/parallax,HyperTwist,,,,,interface / visualization / shell surface,subsystem donor,interface donor,merge bench,integrate,moderate modification,"Retain the reusable internal layer, but replace shell assumptions and rebind boundaries so it plugs into HyperTwist cleanly.",,"Integrate selected subsystems rather than the whole product. Mine the repo for layered explainer behavior, scroll-driven motion, sticky layers, and narrative browser presentation; keep what materially shortens build time, but bind it to HyperTwist-owned data contracts, UI shell, and runtime boundaries.",,Integrate here means: merge bounded support surfaces from this repo into the HyperTwist companion stack.,,,,"the parallax runtime, sticky-layer behavior, scroll-driven spring motion, and imperative scrollTo flow.","Inspect manifests, README/docs, parallax package runtime, layer behavior, and scroll-controller code.","Audit @react-spring/parallax as a Browser layered-motion and explainer sidecar candidate for HyperTwist. Inspect the parallax runtime, sticky-layer behavior, scroll-driven spring motion, and imperative scrollTo flow. Decide whether the retained value should remain active and what should stay bounded outside the HyperTwist core.",,,,,,,,,,,,,,medium,"Canonized Markdown dossier exists and the repo has been source-backed, but CSV backfill is later than the original v6.3 board generation.",medium,Source-backed dossier exists and the repo has been reconciled into the later Markdown authority stack.,,,,,,,,,,,,HT_browser_support,HT_browser_support_0016,browser / 3D / XR / presentation,"Integrate selectively for HyperTwist. Its source-backed role is a bounded layered-motion and explainer sidecar beneath react-spring, not a runtime lane.",HyperTwist,browser / 3D / XR / presentation,integrate,moderate modification,medium,@react-spring/parallax,,,,,,,,,,,,,,,,,,MIT,known_from_reference_material,uploaded_reference_docs,,,,,,,,,,Backfilled from canonized Markdown dossier pass on 2026-04-25: 81-react-spring-parallax-upstream-dossier.md,,,,Merge Bench,Browser layered-motion and explainer sidecar,Included,P4,permissive_or_noncopyleft_known,direct_incorporation_ok,The code license is MIT and direct use is allowed. Treat it as a bounded layered-motion and explainer sidecar.,Use directly as a bounded browser-side dependency for explainer and narrative surfaces.,"Typically preserve notices, attribution, and license text where required.",Usually unnecessary unless later product-shaping concerns make selective replacement attractive.,high,standard-notice-review,yes,,,,,,,,,,,,,v6.3_markdown_backfill,Backfilled from canonized Markdown dossier pass on 2026-04-25: 81-react-spring-parallax-upstream-dossier.md,implemented_live_permissive,landed_permissive_preserve,"Phase 3R-E closed. Preserve as the landed first-party embodied companion, narration, lip-sync, gesture, subtitle, and avatar-embed lane; start future widening from the live-lane audit, then the 3R-E implementation packet, then REPO_LICENSE_TRACKING.md." +,@react-spring/rafz,https://github.com/pmndrs/react-spring/tree/main/packages/rafz,HyperTwist,,,,,interface / visualization / shell surface,subsystem donor,dependency donor,merge bench,integrate,moderate modification,"Retain the reusable internal layer, but replace shell assumptions and rebind boundaries so it plugs into HyperTwist cleanly.",,"Integrate selected subsystems rather than the whole product. Mine the repo for browser scheduling, phased queues, timeout handling, and motion-frame orchestration beneath higher-level UI motion; keep what materially shortens build time, but bind it to HyperTwist-owned data contracts, UI shell, and runtime boundaries.",,Integrate here means: merge bounded support surfaces from this repo into the HyperTwist companion stack.,,,,"the frame-loop phases, timeout scheduling, throttling, batched updates hook, and demand versus always control behavior.","Inspect manifests, README/docs, rafz package runtime, frame-loop scheduling, timeout handling, and queue behavior.","Audit @react-spring/rafz as a Browser frame-loop and scheduling utility candidate for HyperTwist. Inspect the frame-loop phases, timeout scheduling, throttling, batched updates hook, and demand versus always control behavior. Decide whether the retained value should remain active and what should stay bounded outside the HyperTwist core.",,,,,,,,,,,,,,medium,"Canonized Markdown dossier exists and the repo has been source-backed, but CSV backfill is later than the original v6.3 board generation.",medium,Source-backed dossier exists and the repo has been reconciled into the later Markdown authority stack.,,,,,,,,,,,,HT_browser_support,HT_browser_support_0017,browser / utilities / scheduling,"Integrate selectively for HyperTwist. Its source-backed role is a lower-level browser frame-loop and scheduling utility beneath react-spring, not a product lane.",HyperTwist,browser / utilities / scheduling,integrate,moderate modification,medium,@react-spring/rafz,,,,,,,,,,,,,,,,,,MIT,known_from_reference_material,uploaded_reference_docs,,,,,,,,,,Backfilled from canonized Markdown dossier pass on 2026-04-25: 82-react-spring-rafz-upstream-dossier.md,,,,Merge Bench,Browser frame-loop and scheduling utility,Included,P4,permissive_or_noncopyleft_known,direct_incorporation_ok,The code license is MIT and direct use is allowed. Treat it as a bounded browser scheduling utility.,Use directly as a bounded browser-side dependency beneath higher-level motion or interaction layers.,"Typically preserve notices, attribution, and license text where required.",Usually unnecessary unless later product-shaping concerns make selective replacement attractive.,high,standard-notice-review,yes,,,,,,,,,,,,,v6.3_markdown_backfill,Backfilled from canonized Markdown dossier pass on 2026-04-25: 82-react-spring-rafz-upstream-dossier.md,implemented_live_permissive,landed_permissive_preserve,"Phase 3R-E closed. Preserve as the landed first-party embodied companion, narration, lip-sync, gesture, subtitle, and avatar-embed lane; start future widening from the live-lane audit, then the 3R-E implementation packet, then REPO_LICENSE_TRACKING.md." +,@react-spring/animated,https://github.com/pmndrs/react-spring/tree/main/packages/animated,HyperTwist,,,,,interface / visualization / shell surface,subsystem donor,dependency donor,merge bench,integrate,moderate modification,"Retain the reusable internal layer, but replace shell assumptions and rebind boundaries so it plugs into HyperTwist cleanly.",,"Integrate selected subsystems rather than the whole product. Mine the repo for animatable-component hosting, animated-props observation, and low-level motion binding beneath higher-level browser motion; keep what materially shortens build time, but bind it to HyperTwist-owned data contracts, UI shell, and runtime boundaries.",,Integrate here means: merge bounded support surfaces from this repo into the HyperTwist companion stack.,,,,"the host-creation runtime, withAnimated wrapper, dependency observation, and native-update versus rerender behavior.","Inspect manifests, README/docs, animated package runtime, host creation, animated wrapper, and animated base-node behavior.","Audit @react-spring/animated as a Browser animatable-component substrate candidate for HyperTwist. Inspect the host-creation runtime, withAnimated wrapper, dependency observation, and native-update versus rerender behavior. Decide whether the retained value should remain active and what should stay bounded outside the HyperTwist core.",,,,,,,,,,,,,,medium,"Canonized Markdown dossier exists and the repo has been source-backed, but CSV backfill is later than the original v6.3 board generation.",medium,Source-backed dossier exists and the repo has been reconciled into the later Markdown authority stack.,,,,,,,,,,,,HT_browser_support,HT_browser_support_0018,browser / utilities / animation,"Integrate selectively for HyperTwist. Its source-backed role is a lower-level animatable-component host and animated-props substrate beneath react-spring, not a product lane.",HyperTwist,browser / utilities / animation,integrate,moderate modification,medium,@react-spring/animated,,,,,,,,,,,,,,,,,,MIT,known_from_reference_material,uploaded_reference_docs,,,,,,,,,,Backfilled from canonized Markdown dossier pass on 2026-04-25: 83-react-spring-animated-upstream-dossier.md,,,,Merge Bench,Browser animatable-component substrate,Included,P4,permissive_or_noncopyleft_known,direct_incorporation_ok,The code license is MIT and direct use is allowed. Treat it as a bounded animatable-component substrate.,Use directly as a bounded browser-side dependency beneath higher-level motion and UI layers.,"Typically preserve notices, attribution, and license text where required.",Usually unnecessary unless later product-shaping concerns make selective replacement attractive.,high,standard-notice-review,yes,,,,,,,,,,,,,v6.3_markdown_backfill,Backfilled from canonized Markdown dossier pass on 2026-04-25: 83-react-spring-animated-upstream-dossier.md,implemented_live_permissive,landed_permissive_preserve,"Phase 3R-E closed. Preserve as the landed first-party embodied companion, narration, lip-sync, gesture, subtitle, and avatar-embed lane; start future widening from the live-lane audit, then the 3R-E implementation packet, then REPO_LICENSE_TRACKING.md." +,@react-spring/core,https://github.com/pmndrs/react-spring/tree/main/packages/core,HyperTwist,,,,,interface / visualization / shell surface,subsystem donor,dependency donor,donor bench,repurpose,moderate modification,"Retain the valuable internal layer, but expect to replace upstream shell assumptions and rebind boundaries so it fits the HyperTwist architecture.",,"Repurpose selected subsystems rather than the whole product. Mine the repo for browser motion runtime, spring orchestration, frame advancement, and reusable motion-core behavior beneath higher-level UI layers; keep what materially shortens build time, but bind it to HyperTwist-owned data contracts, UI shell, and runtime boundaries.",,Repurpose here means: extract bounded support surfaces from this repo without inheriting the full upstream shell.,,,,"the Controller runtime, SpringValue motion engine, useSprings lifecycle, queueing, start-stop behavior, and frame advancement.","Inspect manifests, README/docs, core package runtime, Controller, SpringValue, and hook lifecycle behavior.","Audit @react-spring/core as a Browser spring-runtime core candidate for HyperTwist. Inspect the Controller runtime, SpringValue motion engine, useSprings lifecycle, queueing, start-stop behavior, and frame advancement. Decide whether the retained value should remain active and what should stay bounded outside the HyperTwist core.",,,,,,,,,,,,,,medium,"Canonized Markdown dossier exists and the repo has been source-backed, but CSV backfill is later than the original v6.3 board generation.",medium,Source-backed dossier exists and the repo has been reconciled into the later Markdown authority stack.,,,,,,,,,,,,HT_browser_support,HT_browser_support_0019,browser / utilities / animation,"Repurpose selectively for HyperTwist. Its source-backed role is the platform-agnostic spring-runtime core beneath react-spring, not a product foundation.",HyperTwist,browser / utilities / animation,repurpose,moderate modification,medium,@react-spring/core,,,,,,,,,,,,,,,,,,MIT,known_from_reference_material,uploaded_reference_docs,,,,,,,,,,Backfilled from canonized Markdown dossier pass on 2026-04-25: 84-react-spring-core-upstream-dossier.md,,,,Donor Bench,Browser spring-runtime core,Included,P3,permissive_or_noncopyleft_known,direct_incorporation_ok,The code license is MIT and direct use is allowed. Treat it as a bounded spring-runtime core beneath higher-level motion layers.,Use directly as a bounded browser-side dependency beneath higher-level motion and interaction layers.,"Typically preserve notices, attribution, and license text where required.",Usually unnecessary unless later product-shaping concerns make selective replacement attractive.,high,standard-notice-review,yes,,,,,,,,,,,,,v6.3_markdown_backfill,Backfilled from canonized Markdown dossier pass on 2026-04-25: 84-react-spring-core-upstream-dossier.md,implemented_live_permissive,landed_permissive_preserve,"Phase 3R-E closed. Preserve as the landed first-party embodied companion, narration, lip-sync, gesture, subtitle, and avatar-embed lane; start future widening from the live-lane audit, then the 3R-E implementation packet, then REPO_LICENSE_TRACKING.md." +,@react-spring/shared,https://github.com/pmndrs/react-spring/tree/main/packages/shared,HyperTwist,,,,,interface / visualization / shell surface,subsystem donor,dependency donor,merge bench,integrate,moderate modification,"Retain the reusable internal layer, but replace shell assumptions and rebind boundaries so it plugs into HyperTwist cleanly.",,"Integrate selected subsystems rather than the whole product. Mine the repo for motion utilities, frame-loop customization, interpolation, and fluid observation beneath higher-level browser motion; keep what materially shortens build time, but bind it to HyperTwist-owned data contracts, UI shell, and runtime boundaries.",,Integrate here means: merge bounded support surfaces from this repo into the HyperTwist companion stack.,,,,"the globals customization seams, frame-loop behavior, interpolation helpers, and fluid observer substrate.","Inspect manifests, README/docs, shared package exports, globals, frame loop, interpolation, and fluid observer modules.","Audit @react-spring/shared as a Browser motion utility substrate candidate for HyperTwist. Inspect the globals customization seams, frame-loop behavior, interpolation helpers, and fluid observer substrate. Decide whether the retained value should remain active and what should stay bounded outside the HyperTwist core.",,,,,,,,,,,,,,medium,"Canonized Markdown dossier exists and the repo has been source-backed, but CSV backfill is later than the original v6.3 board generation.",medium,Source-backed dossier exists and the repo has been reconciled into the later Markdown authority stack.,,,,,,,,,,,,HT_browser_support,HT_browser_support_0020,browser / utilities / animation,"Integrate selectively for HyperTwist. Its source-backed role is a lower-level motion utility and fluid-observer substrate beneath react-spring, not a product lane.",HyperTwist,browser / utilities / animation,integrate,moderate modification,medium,@react-spring/shared,,,,,,,,,,,,,,,,,,MIT,known_from_reference_material,uploaded_reference_docs,,,,,,,,,,Backfilled from canonized Markdown dossier pass on 2026-04-25: 85-react-spring-shared-upstream-dossier.md,,,,Merge Bench,Browser motion utility substrate,Included,P4,permissive_or_noncopyleft_known,direct_incorporation_ok,The code license is MIT and direct use is allowed. Treat it as a bounded motion utility substrate.,Use directly as a bounded browser-side dependency beneath higher-level motion layers.,"Typically preserve notices, attribution, and license text where required.",Usually unnecessary unless later product-shaping concerns make selective replacement attractive.,high,standard-notice-review,yes,,,,,,,,,,,,,v6.3_markdown_backfill,Backfilled from canonized Markdown dossier pass on 2026-04-25: 85-react-spring-shared-upstream-dossier.md,implemented_live_permissive,landed_permissive_preserve,"Phase 3R-E closed. Preserve as the landed first-party embodied companion, narration, lip-sync, gesture, subtitle, and avatar-embed lane; start future widening from the live-lane audit, then the 3R-E implementation packet, then REPO_LICENSE_TRACKING.md." +,@react-spring/types,https://github.com/pmndrs/react-spring/tree/main/packages/types,HyperTwist,,,,,interface / visualization / shell surface,subsystem donor,dependency donor,merge bench,integrate,moderate modification,"Retain the reusable internal layer, but replace shell assumptions and rebind boundaries so it plugs into HyperTwist cleanly.",,"Integrate selected subsystems rather than the whole product. Mine the repo for shared type contracts and package-design substrate beneath browser motion layers; keep what materially shortens build time, but bind it to HyperTwist-owned data contracts, UI shell, and runtime boundaries.",,Integrate here means: merge bounded support surfaces from this repo into the HyperTwist companion stack.,,,,"the shared type-contract surface, animatable and interpolation types, and utility-type exports used across react-spring packages.","Inspect manifests, type package exports, shared type files, interpolation type definitions, and utility-type modules.","Audit @react-spring/types as a Browser motion type-contract substrate candidate for HyperTwist. Inspect the shared type-contract surface, animatable and interpolation types, and utility-type exports used across react-spring packages. Decide whether the retained value should remain active and what should stay bounded outside the HyperTwist core.",,,,,,,,,,,,,,medium,"Canonized Markdown dossier exists and the repo has been source-backed, but CSV backfill is later than the original v6.3 board generation.",medium,Source-backed dossier exists and the repo has been reconciled into the later Markdown authority stack.,,,,,,,,,,,,HT_browser_support,HT_browser_support_0021,browser / utilities / animation,"Integrate selectively for HyperTwist. Its source-backed role is a narrow type-contract substrate beneath react-spring, not a behavior-heavy donor or product lane.",HyperTwist,browser / utilities / animation,integrate,moderate modification,medium,@react-spring/types,,,,,,,,,,,,,,,,,,MIT,known_from_reference_material,uploaded_reference_docs,,,,,,,,,,Backfilled from canonized Markdown dossier pass on 2026-04-25: 86-react-spring-types-upstream-dossier.md,,,,Merge Bench,Browser motion type-contract substrate,Included,P4,permissive_or_noncopyleft_known,direct_incorporation_ok,The code license is MIT and direct use is allowed. Treat it as a bounded type-contract substrate.,Use directly as a bounded browser-side dependency where those contracts are actually needed.,"Typically preserve notices, attribution, and license text where required.",Usually unnecessary unless later product-shaping concerns make selective replacement attractive.,high,standard-notice-review,yes,,,,,,,,,,,,,v6.3_markdown_backfill,Backfilled from canonized Markdown dossier pass on 2026-04-25: 86-react-spring-types-upstream-dossier.md,implemented_live_permissive,landed_permissive_preserve,"Phase 3R-E closed. Preserve as the landed first-party embodied companion, narration, lip-sync, gesture, subtitle, and avatar-embed lane; start future widening from the live-lane audit, then the 3R-E implementation packet, then REPO_LICENSE_TRACKING.md." diff --git a/docs/repo_portfolio_unified_phase_g_v6_3.csv b/docs/repo_portfolio_unified_phase_g_v6_3.csv index 099ca4b..8d89030 100644 --- a/docs/repo_portfolio_unified_phase_g_v6_3.csv +++ b/docs/repo_portfolio_unified_phase_g_v6_3.csv @@ -1,30 +1,30 @@ execution_queue_order,repo,primary_url,best_fit_project_v2,project_rank,portfolio_priority_score,execution_priority_score_v3,priority_band,taxonomy_hardened,archetype_primary,archetype_secondary,portfolio_role_v3,recommended_action_v2,repurposing_potential_v2,modification_scope_detail_v3,capability_extract,integration_realization_detail,consolidation_detail,repurpose_detail,realization_checklist,inspection_depth_recommendation,hidden_value_hypothesis,source_inspection_questions,source_code_audit_targets,coding_model_instruction_v3,merger_partner_1,merger_type_1,merger_rationale_1,merger_partner_2,merger_type_2,merger_rationale_2,merger_partner_3,merger_type_3,merger_rationale_3,cross_project_transfer_targets,cross_project_transfer_rationale,exclusion_discipline,exclusion_reasoning_v3,confidence_v3,confidence_rationale_v3,confidence_reassessed,confidence_rationale,licensing_filter_status,bookmark_project_sections,bookmark_heading_paths_top,bookmark_description_sample,memo_signal_sample,expanded_reasoning,source_attachments,in_bookmarks,in_memo,bookmark_occurrences,memo_mentions,cluster_tag,source_audit_packet_id,category_guess_v2,reasoning,best_fit_project,category_guess,recommended_action,repurposing_potential,confidence,canonical_repo_key,alias_group_size,phase_g_bucket,phase_g_bucket_rank,phase_g_bucket_reason,phase_g_project_stack_layer,phase_g_inclusion_status,phase_g_source_audit_priority,phase_g_master_list_rationale,phase_g_project_rank,phase_g_conf_rank,phase_g_action_rank,phase_g_global_order,phase_g_project_order,phase_g_anomaly_flag,_repo_norm,v5_primary_eval_project,v5_runtime_project,v5_scriptorium_override_status,v5_scriptorium_phase_g_bucket,v5_scriptorium_phase_g_stack_layer,v5_scriptorium_phase_g_source_audit_priority,v5_scriptorium_current_reality_status,v5_scriptorium_actual_role,v5_scriptorium_evidence_summary,v5_scriptorium_supersedes_prior_assessment,v5_source_of_truth,v6_license_annotation,v6_license_annotation_status,v6_license_annotation_source,v6_supplemental_intake_present,v6_supplemental_source_groups,v6_supplemental_source_sections,v6_supplemental_source_files,v6_reference_material_position,v6_kali_agent_access_relevance,v6_branch_seed_prompt_included,v6_branch_seed_scope,v6_intake_wave,v6_notes,v6_source_of_truth,project_rank_num,audit_rank_num,bucket_rank_num,priority_num,copyleft_relevance_v6_1,copyleft_strategy_v6_1,copyleft_rationale_v6_1,preferred_boundary_model_v6_1,open_compliance_if_used_as_is_v6_1,reverse_engineer_if_proprietary_core_needed_v6_1,copyleft_strategy_confidence_v6_1,copyleft_manual_review_trigger_v6_1,as_is_incorporation_sensible_v6_1,v6_2_sre_layer,v6_2_sre_stratum,v6_2_sre_role,v6_2_sre_family,v6_2_related_kali_package,v6_2_related_upstream_repo,v6_2_kali_package_suffices_for_tool_execution,v6_2_upstream_repo_preferred_for_deep_eval,v6_2_index_page_followup_useful,v6_2_index_page_followup_reason,v6_2_sre_notes,v6_2_dnspy_ilspy_relevance,v6_3_source_of_truth,v6_3_merge_note,v6_3_live_state_2026_05_11,v6_3_reset_lane_2026_05_11,v6_3_reset_next_step_2026_05_11 -1.0,HactarCE/Hyperspeedcube,https://github.com/HactarCE/Hyperspeedcube,HyperTwist,1.0,160.0,193.0,A,hypercubing / nD engine,foundation engine,simulation donor,locked core candidate,integrate,direct,"Keep the core engine or major subsystem mostly intact; change wrappers, branding, storage/auth, and integration seams so it becomes a first-class part of the target stack. For this repo class, that usually means preserving generalized puzzle/state/render logic while building a new application shell around it.",HactarCE/Hyperspeedcube — MIT OR Apache-2.0 — Modern 3D/4D puzzle simulator (thousands of puzzles). | This makes CubeForge the first true hypercubing training platform — solving every pain point while keeping the 3D core rock-solid.Exten...,"Integrate as a hypercubing / nD simulation subsystem for HyperTwist. Preserve the strongest existing pieces — nD state model, move notation, renderer, projection controls, solver/traversal logic, puzzle serialization, replay — and expose them behind a portfolio-stable interface. Wire first into cubing/cubing.js, then into tao-yu/Alg-Trainer for orchestration, visualization, or data exchange.","Consolidate under the Hyperspeedcube + cubing.js + qbr nucleus, not beside it as a separate silo. Normalize data contracts, auth/permissions, storage, and telemetry; then attach as a service, plugin, canvas layer, trainer, or analysis module. Descending combination order: cubing/cubing.js, tao-yu/Alg-Trainer, poliva/cubedex.",Repurpose here means: turn it into a higher-dimensional renderer/simulator donor and shared interaction grammar for HyperTwist and long-horizon VectorShell.,Map module boundaries; Identify hidden reusable internals; Define adapter/API boundary to target anchors; Write extraction tests against upstream behavior; Isolate puzzle/state core; Extract render/input abstractions; Document notation and save format,full subsystem extraction review,"Hidden value is likely in generalized puzzle/state representations, higher-dimensional transforms, notation systems, save formats, puzzle generators, and rendering abstractions.",Inspect generalized puzzle/state model; notation parser; transform math; rendering abstraction; save/load format; puzzle generator; input mapping; performance optimizations.,"Inspect package manifests, README/docs, src tree, examples, tests, CI workflows, config files, migrations/schemas, and hidden feature flags or experimental modules. Look for higher-dimensional state/notation representations, projection math, renderer abstractions, puzzle serialization, controls, and replay/training hooks.","Audit HactarCE/Hyperspeedcube as a hypercubing / nD engine candidate for HyperTwist. Do not stop at README-level features. Inspect: Inspect generalized puzzle/state model; notation parser; transform math; rendering abstraction; save/load format; puzzle generator; input mapping; performance optimizations. Decide whether the best extraction path is direct and whether it belongs as foundation engine / simulation donor. Test the three merger paths in order: 1) cubing/cubing.js [3D engine + notation/state donor]; 2) tao-yu/Alg-Trainer [training UX donor]; 3) cross-project transfer candidate [future merger]. Return hidden modules, reusable schemas, protocol layers, plugin hooks, render/state models, datasets/test fixtures, and any subsystem stronger than the visible product shell.",cubing/cubing.js,3D engine + notation/state donor,Use the partner for canonical state or rendering abstractions and merge this repo's specialized logic on top.,tao-yu/Alg-Trainer,training UX donor,Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.,cross-project transfer candidate,future merger,Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.,VectorShell | ScriptoriumAI,VectorShell can borrow spatial/rendering and perception primitives; ScriptoriumAI can borrow tutorial/educational visualization patterns rather than the full engine.,do not exclude,Keep in active merge-set and force full source audit before any demotion.,high,single-source signal; clear taxonomy; active integration value; foundation-level fit,high,portfolio anchor or repeatedly surfaced core candidate; memo mentions: 6,"Licensing intentionally ignored as a decision filter in this canonical evaluation; assess only architecture, capability, donor value, and concept transfer.",,,,"HactarCE/Hyperspeedcube — MIT OR Apache-2.0 — Modern 3D/4D puzzle simulator (thousands of puzzles). | This makes CubeForge the first true hypercubing training platform — solving every pain point while keeping the 3D core rock-solid.Extended Comprehensive Open-Source Building Blocks (April 2026)Updated exhaustive scan — focused on high-value for your codebase (simulators, trainers, vision, hyper).MIT or Apache Licensed (Fully permissive — fork/abs",HactarCE/Hyperspeedcube is treated as integrate for HyperTwist because visible metadata points to the hypercubing / nD simulation layer. Surface signal: HactarCE/Hyperspeedcube — MIT OR Apache-2.0 — Modern 3D/4D puzzle simulator (thousands of puzzles). | This makes CubeForge the first true hypercubing training platform — solving every pain point while keeping the 3D core rock-solid.Exten... The likely value is substantial enough to preserve as a named subsystem rather than just mining isolated ideas.,memo,False,True,0.0,6.0,HT_hyper_engine,HT_hyper_engine_0001,hypercubing / nD simulation,Integrate as a shared building block across at least two projects. Its memo and bookmark signals place it in the hypercubing / nD simulation layer.,multi-project,hypercubing / nD simulation,integrate,direct,medium,hactarce/hyperspeedcube,1.0,Locked Foundation,1.0,Primary architectural anchor for HyperTwist; strongest current fit in corpus for the 'nD / hypercubing simulation substrate' role and should be source-audited before alternative bases.,nD / hypercubing simulation substrate,Included,P0,"HactarCE/Hyperspeedcube is placed in Locked Foundation for HyperTwist because it best serves the 'nD / hypercubing simulation substrate' role; recommended action is 'integrate' with repurposing scope 'direct'. Confidence is high because this remains a metadata-level judgment until source audit confirms hidden modules, plugin points, adapters, or architectural strengths.",2.0,5.0,3.0,2.0,2.0,,hactarce/hyperspeedcube,HyperTwist,,,,,,,,,,Original global Phase G v4 retained,MIT,known_from_reference_material,uploaded_reference_docs,yes,hypertwist_and_scriptoriumai,HyperTwist,HyperTwist & ScriptoriumAI.txt,Supplemental intake references are advisory only; v6 adjudication remains the source of truth.,Potentially relevant,yes,v6 unified all-project source-of-truth pack,v5_carry_forward,Existing v5 row reaffirmed or widened by v6 supplemental intake.,v6_unified_source_of_truth_pack,1.0,1,1.0,160.0,permissive_or_noncopyleft_known,direct_incorporation_ok,"This repo is aligned with a direct integration path for HyperTwist because it is either already implemented, strategically central, or donor-grade without a visible copyleft constraint in the current materials. Deep incorporation is sensible if the source audit confirms architectural cleanliness.","Direct embed, vendored module, package dependency, or tightly integrated adapter as the architecture requires.","Typically preserve notices, attribution, and license text where required; no special copyleft-driven disclosure posture is normally needed.",Usually unnecessary unless you later decide the existing implementation is too constraining architecturally.,high,strategic-or-implemented-component,yes,,,,,,,,,,,,,v6.3_final_source_of_truth,Merged v6.1 copyleft layer and v6.2 SRE layer; use v6.3 docs + workbook as canonical handoff.,selected_not_live_permissive_candidate,phase0r_permissive_eval_then_implement,"Phase 1R closed. Retain as a Phase 3R permissive implementation candidate; implement only from its packet authority and the retained-set contract, not by reopening Phase 0R." +1.0,HactarCE/Hyperspeedcube,https://github.com/HactarCE/Hyperspeedcube,HyperTwist,1.0,160.0,193.0,A,hypercubing / nD engine,foundation engine,simulation donor,locked core candidate,integrate,direct,"Keep the core engine or major subsystem mostly intact; change wrappers, branding, storage/auth, and integration seams so it becomes a first-class part of the target stack. For this repo class, that usually means preserving generalized puzzle/state/render logic while building a new application shell around it.",HactarCE/Hyperspeedcube — MIT OR Apache-2.0 — Modern 3D/4D puzzle simulator (thousands of puzzles). | This makes CubeForge the first true hypercubing training platform — solving every pain point while keeping the 3D core rock-solid.Exten...,"Integrate as a hypercubing / nD simulation subsystem for HyperTwist. Preserve the strongest existing pieces — nD state model, move notation, renderer, projection controls, solver/traversal logic, puzzle serialization, replay — and expose them behind a portfolio-stable interface. Wire first into cubing/cubing.js, then into tao-yu/Alg-Trainer for orchestration, visualization, or data exchange.","Consolidate under the Hyperspeedcube + cubing.js + qbr nucleus, not beside it as a separate silo. Normalize data contracts, auth/permissions, storage, and telemetry; then attach as a service, plugin, canvas layer, trainer, or analysis module. Descending combination order: cubing/cubing.js, tao-yu/Alg-Trainer, poliva/cubedex.",Repurpose here means: turn it into a higher-dimensional renderer/simulator donor and shared interaction grammar for HyperTwist and long-horizon VectorShell.,Map module boundaries; Identify hidden reusable internals; Define adapter/API boundary to target anchors; Write extraction tests against upstream behavior; Isolate puzzle/state core; Extract render/input abstractions; Document notation and save format,full subsystem extraction review,"Hidden value is likely in generalized puzzle/state representations, higher-dimensional transforms, notation systems, save formats, puzzle generators, and rendering abstractions.",Inspect generalized puzzle/state model; notation parser; transform math; rendering abstraction; save/load format; puzzle generator; input mapping; performance optimizations.,"Inspect package manifests, README/docs, src tree, examples, tests, CI workflows, config files, migrations/schemas, and hidden feature flags or experimental modules. Look for higher-dimensional state/notation representations, projection math, renderer abstractions, puzzle serialization, controls, and replay/training hooks.","Audit HactarCE/Hyperspeedcube as a hypercubing / nD engine candidate for HyperTwist. Do not stop at README-level features. Inspect: Inspect generalized puzzle/state model; notation parser; transform math; rendering abstraction; save/load format; puzzle generator; input mapping; performance optimizations. Decide whether the best extraction path is direct and whether it belongs as foundation engine / simulation donor. Test the three merger paths in order: 1) cubing/cubing.js [3D engine + notation/state donor]; 2) tao-yu/Alg-Trainer [training UX donor]; 3) cross-project transfer candidate [future merger]. Return hidden modules, reusable schemas, protocol layers, plugin hooks, render/state models, datasets/test fixtures, and any subsystem stronger than the visible product shell.",cubing/cubing.js,3D engine + notation/state donor,Use the partner for canonical state or rendering abstractions and merge this repo's specialized logic on top.,tao-yu/Alg-Trainer,training UX donor,Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.,cross-project transfer candidate,future merger,Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.,VectorShell | ScriptoriumAI,VectorShell can borrow spatial/rendering and perception primitives; ScriptoriumAI can borrow tutorial/educational visualization patterns rather than the full engine.,do not exclude,Keep in active merge-set and force full source audit before any demotion.,high,single-source signal; clear taxonomy; active integration value; foundation-level fit,high,portfolio anchor or repeatedly surfaced core candidate; memo mentions: 6,"Licensing intentionally ignored as a decision filter in this canonical evaluation; assess only architecture, capability, donor value, and concept transfer.",,,,"HactarCE/Hyperspeedcube — MIT OR Apache-2.0 — Modern 3D/4D puzzle simulator (thousands of puzzles). | This makes CubeForge the first true hypercubing training platform — solving every pain point while keeping the 3D core rock-solid.Extended Comprehensive Open-Source Building Blocks (April 2026)Updated exhaustive scan — focused on high-value for your codebase (simulators, trainers, vision, hyper).MIT or Apache Licensed (Fully permissive — fork/abs",HactarCE/Hyperspeedcube is treated as integrate for HyperTwist because visible metadata points to the hypercubing / nD simulation layer. Surface signal: HactarCE/Hyperspeedcube — MIT OR Apache-2.0 — Modern 3D/4D puzzle simulator (thousands of puzzles). | This makes CubeForge the first true hypercubing training platform — solving every pain point while keeping the 3D core rock-solid.Exten... The likely value is substantial enough to preserve as a named subsystem rather than just mining isolated ideas.,memo,False,True,0.0,6.0,HT_hyper_engine,HT_hyper_engine_0001,hypercubing / nD simulation,Integrate as a shared building block across at least two projects. Its memo and bookmark signals place it in the hypercubing / nD simulation layer.,multi-project,hypercubing / nD simulation,integrate,direct,medium,hactarce/hyperspeedcube,1.0,Locked Foundation,1.0,Primary architectural anchor for HyperTwist; strongest current fit in corpus for the 'nD / hypercubing simulation substrate' role and should be source-audited before alternative bases.,nD / hypercubing simulation substrate,Included,P0,"HactarCE/Hyperspeedcube is placed in Locked Foundation for HyperTwist because it best serves the 'nD / hypercubing simulation substrate' role; recommended action is 'integrate' with repurposing scope 'direct'. Confidence is high because this remains a metadata-level judgment until source audit confirms hidden modules, plugin points, adapters, or architectural strengths.",2.0,5.0,3.0,2.0,2.0,,hactarce/hyperspeedcube,HyperTwist,,,,,,,,,,Original global Phase G v4 retained,MIT,known_from_reference_material,uploaded_reference_docs,yes,hypertwist_and_scriptoriumai,HyperTwist,HyperTwist & ScriptoriumAI.txt,Supplemental intake references are advisory only; v6 adjudication remains the source of truth.,Potentially relevant,yes,v6 unified all-project source-of-truth pack,v5_carry_forward,Existing v5 row reaffirmed or widened by v6 supplemental intake.,v6_unified_source_of_truth_pack,1.0,1,1.0,160.0,permissive_or_noncopyleft_known,direct_incorporation_ok,"This repo is aligned with a direct integration path for HyperTwist because it is either already implemented, strategically central, or donor-grade without a visible copyleft constraint in the current materials. Deep incorporation is sensible if the source audit confirms architectural cleanliness.","Direct embed, vendored module, package dependency, or tightly integrated adapter as the architecture requires.","Typically preserve notices, attribution, and license text where required; no special copyleft-driven disclosure posture is normally needed.",Usually unnecessary unless you later decide the existing implementation is too constraining architecturally.,high,strategic-or-implemented-component,yes,,,,,,,,,,,,,v6.3_final_source_of_truth,Merged v6.1 copyleft layer and v6.2 SRE layer; use v6.3 docs + workbook as canonical handoff.,implemented_live_permissive,landed_permissive_preserve,"Phase 3R-E closed. Preserve as the landed first-party embodied companion, narration, lip-sync, gesture, subtitle, and avatar-embed lane; start future widening from the live-lane audit, then the 3R-E implementation packet, then REPO_LICENSE_TRACKING.md." 1746.0,SYSTRAN/faster-whisper,https://github.com/SYSTRAN/faster-whisper,multi-project,1.0,71.0,80.0,C,voice / multimodal I/O,subsystem donor,multimodal donor,donor bench,repurpose,moderate modification,"Retain the valuable internal engine, but expect to replace UI/product shell, adapt schemas/APIs, and refactor boundaries so it can plug into the target anchors cleanly. For this repo class, that usually means preserving parsers/graph schema/indexing while swapping layout, storage, or UX layers.",huggingface/faster-whisper – https://github.com/SYSTRAN/faster-whisper – MIT – Fast Whisper STT.,"Repurpose selected subsystems rather than the whole product. Mine the repo for VAD-aware segmentation, batch transcription, timestamps, hotword and prefix conditioning, and Python service ergonomics; keep what materially shortens build time, but rebind data contracts, permissions, storage, and deployment to the target architecture. Best first pairing order: ggml-org/whisper.cpp, rhasspy/piper, coqui-ai/TTS.","Consolidate under the project-specific anchor stack, not beside it as a separate silo. Normalize data contracts, auth/permissions, storage, and telemetry; then attach as a service, plugin, canvas layer, trainer, or analysis module. Descending combination order: sentrux/sentrux, HactarCE/Hyperspeedcube, outline/outline.","Repurpose here means: turn it into a Python STT service, timestamped speech pipeline, or batch transcription donor.",Map module boundaries; Identify hidden reusable internals; Define adapter/API boundary to target anchors; Write extraction tests against upstream behavior; Normalize graph schema; Decouple parser/indexer from UI; Expose query and layout services,deep source audit,"Hidden value may sit in AST/indexing pipelines, call/dependency graph schema, incremental refresh, layout heuristics, graph query APIs, and serialization formats that can be lifted into VectorShell.",Inspect transcription API and dataclasses; batched inference; VAD chunking; word timestamps; hotwords and prefix conditioning; service-layer boundaries; benchmark and test coverage.,"Inspect package manifests, README/docs, src tree, examples, tests, CI workflows, benchmark scripts, and hidden experimental modules. Look for VAD, batch inference, timestamps, hotwords, model/runtime constraints, and service-layer boundaries.","Audit SYSTRAN/faster-whisper as a voice / multimodal I/O candidate for multi-project. Do not stop at README-level features. Inspect: transcription API and dataclasses, batched inference, VAD chunking, word timestamps, hotwords and prefix conditioning, service-layer boundaries, and benchmark/test coverage. Decide whether it should remain the primary Python STT donor and what should stay behind a bounded Python service seam. Test the three merger paths in order: 1) project-local anchor [base + donor]; 2) shared portfolio utility [augmenter]; 3) cross-project transfer candidate [future merger]. Return hidden modules, reusable schemas, protocol layers, runtime boundaries, tests/benchmarks, and any subsystem stronger than the visible shell.",project-local anchor,base + donor,Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.,shared portfolio utility,augmenter,Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.,cross-project transfer candidate,future merger,Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.,project-local first,"Cross-project transfer is possible, but the value is clearest inside the assigned project until source audit exposes more reusable primitives.","exclude from core, keep as donor","Do not let it consume roadmap as a full product shell; mine reusable engines, adapters, schemas, UX patterns, or datasets.",medium-low,single-source signal; clear taxonomy; mostly donor/reference role,medium,memo mentions: 1,"Licensing intentionally ignored as a decision filter in this canonical evaluation; assess only architecture, capability, donor value, and concept transfer.",,,,huggingface/faster-whisper – https://github.com/SYSTRAN/faster-whisper – MIT – Fast Whisper STT.,"SYSTRAN/faster-whisper is treated as repurpose for multi-project because visible metadata points to the voice / speech / audio layer. Surface signal: huggingface/faster-whisper – https://github.com/SYSTRAN/faster-whisper – MIT – Fast Whisper STT. The fit looks real, but more as a donor/augmenter than as a standalone foundation.",memo,False,True,0.0,1.0,MU_misc,MU_misc_0001,voice / speech / audio,"Repurpose selectively for multi-project. Its source-backed role is a bounded Python STT donor and service-layer candidate, not an exclusion-only adjunct.",future/adjacent use,voice / speech / audio,repurpose,moderate modification,medium,systran/faster-whisper,1.0,Donor Bench,4.0,"Useful subsystem donor for multi-project, primarily in the 'Cross-project / future-adjacent' role; strongest current Python STT donor and service-layer candidate in the voice stack.",Cross-project / future-adjacent,Included,P2,"SYSTRAN/faster-whisper is placed in Donor Bench for multi-project because it provides the clearest Python STT service-layer path in the voice stack. Recommended action remains repurpose, but the real retained value is batch transcription, VAD-aware chunking, timestamps, and Python-side service integration rather than any code-intelligence or graph role.",4.0,2.0,2.0,60.0,2.0,,systran/faster-whisper,multi-project,,,,,,,,,,Original global Phase G v4 retained,MIT,known_from_reference_material,uploaded_reference_docs,no,,,,Supplemental intake references are advisory only; v6 adjudication remains the source of truth.,Usually indirect,yes,v6 unified all-project source-of-truth pack,v5_carry_forward,,v6_unified_source_of_truth_pack,1.0,3,4.0,71.0,permissive_or_noncopyleft_known,direct_incorporation_ok,"The code license is MIT and direct use is allowed. Treat it as a bounded Python STT donor/service candidate; review chosen model checkpoints separately, but no clean-room path is required by default.",Use directly as a bounded Python STT service or adapter layer; keep model/runtime selection and deployment behind a speech-input seam.,"Typically preserve notices, attribution, and license text where required; review selected model checkpoints separately from the code license.",Usually unnecessary unless you later decide to replace a narrow hot path or remove Python/CTranslate2 dependencies.,high,model-artifact-review-required,yes,,,,,,,,,,,,,v6.3_final_source_of_truth,Merged v6.1 copyleft layer and v6.2 SRE layer; use v6.3 docs + workbook as canonical handoff.,,, -2.0,kkoomen/qbr,https://github.com/kkoomen/qbr,HyperTwist,2.0,158.0,191.0,A,vision / perception / AR,foundation engine,vision donor,locked core candidate,integrate,direct,"Keep the core engine or major subsystem mostly intact; change wrappers, branding, storage/auth, and integration seams so it becomes a first-class part of the target stack. For this repo class, that usually means preserving calibration/detection/state-reconstruction logic while replacing camera UX and integration surfaces.","kkoomen/qbr — MIT — Webcam-based 3x3 solver with accurate OpenCV color detection (perfect vision starter). | kkoomen/qbr — MIT — Webcam CV solver (base for 3D vision). | kkoomen/qbr — MIT — Webcam CV color detection. | poliva/cubedex, ta...","Integrate as a computer vision / AR subsystem for HyperTwist. Preserve the strongest existing pieces — camera ingest, calibration, segmentation/detection, pose or facelet extraction, state normalization, solver bridge, replay overlay, AR anchors — and expose them behind a portfolio-stable interface. Wire first into vivaansinghvi07/rubix-cube-solver, then into cubing/cubing.js for orchestration, visualization, or data exchange.","Consolidate under the Hyperspeedcube + cubing.js + qbr nucleus, not beside it as a separate silo. Normalize data contracts, auth/permissions, storage, and telemetry; then attach as a service, plugin, canvas layer, trainer, or analysis module. Descending combination order: vivaansinghvi07/rubix-cube-solver, cubing/cubing.js, HactarCE/Hyperspeedcube.","Repurpose here means: turn it into a perception microservice, cube-state API, replay generator, or AR overlay donor for HyperTwist.",Map module boundaries; Identify hidden reusable internals; Define adapter/API boundary to target anchors; Write extraction tests against upstream behavior; Benchmark calibration pipeline; Extract state reconstruction; Wrap with camera/AR adapter,full subsystem extraction review,"Hidden value often sits in calibration, preprocessing, stabilization, object/state reconstruction, replay artifacts, and camera-to-domain state pipelines that are not obvious from demos.",Inspect preprocessing/calibration; tracking stabilization; state reconstruction; replay/event model; camera abstraction; fallback heuristics; testing assets/videos; performance shortcuts.,"Inspect package manifests, README/docs, src tree, examples, tests, CI workflows, config files, migrations/schemas, and hidden feature flags or experimental modules. Look for calibration routines, detection heuristics/models, color/state normalization, replay serialization, solver bridges, camera abstraction layers, and debug visualizations.","Audit kkoomen/qbr as a vision / perception / AR candidate for HyperTwist. Do not stop at README-level features. Inspect: Inspect preprocessing/calibration; tracking stabilization; state reconstruction; replay/event model; camera abstraction; fallback heuristics; testing assets/videos; performance shortcuts. Decide whether the best extraction path is direct and whether it belongs as foundation engine / vision donor. Test the three merger paths in order: 1) vivaansinghvi07/rubix-cube-solver [perception + replay donor]; 2) cubing/cubing.js [state/render backend]; 3) cross-project transfer candidate [future merger]. Return hidden modules, reusable schemas, protocol layers, plugin hooks, render/state models, datasets/test fixtures, and any subsystem stronger than the visible product shell.",vivaansinghvi07/rubix-cube-solver,perception + replay donor,Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.,cubing/cubing.js,state/render backend,Use the partner for canonical state or rendering abstractions and merge this repo's specialized logic on top.,cross-project transfer candidate,future merger,Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.,VectorShell | ScriptoriumAI,VectorShell can borrow spatial/rendering and perception primitives; ScriptoriumAI can borrow tutorial/educational visualization patterns rather than the full engine.,do not exclude,Keep in active merge-set and force full source audit before any demotion.,high,single-source signal; clear taxonomy; active integration value; foundation-level fit,high,portfolio anchor or repeatedly surfaced core candidate; memo mentions: 5,"Licensing intentionally ignored as a decision filter in this canonical evaluation; assess only architecture, capability, donor value, and concept transfer.",,,,"kkoomen/qbr — MIT — Webcam-based 3x3 solver with accurate OpenCV color detection (perfect vision starter). | kkoomen/qbr — MIT — Webcam CV solver (base for 3D vision). | kkoomen/qbr — MIT — Webcam CV color detection. | poliva/cubedex, tao-yu/Alg-Trainer, kkoomen/qbr, vivaansinghvi07/rubix-cube-solver, NuiLab/code-vr, molgenis/Graph2VR (core permissive parts), brianpeiris/RiftSketch, aMonteSl/CodeXR.","kkoomen/qbr is treated as integrate for HyperTwist because visible metadata points to the computer vision / AR layer. Surface signal: kkoomen/qbr — MIT — Webcam-based 3x3 solver with accurate OpenCV color detection (perfect vision starter). | kkoomen/qbr — MIT — Webcam CV solver (base for 3D vision). | kkoomen/qbr — MIT — Webcam CV color detection. | poliva/cubedex, ta... The likely value is substantial enough to preserve as a named subsystem rather than just mining isolated ideas.",memo,False,True,0.0,5.0,HT_cube_vision,HT_cube_vision_0001,computer vision / AR,Integrate as a shared building block across at least two projects. Its memo and bookmark signals place it in the computer vision / AR layer.,multi-project,computer vision / AR,integrate,heavy modification,medium,kkoomen/qbr,1.0,Locked Foundation,1.0,Primary architectural anchor for HyperTwist; strongest current fit in corpus for the 'Live cube-recognition substrate' role and should be source-audited before alternative bases.,Live cube-recognition substrate,Included,P0,"kkoomen/qbr is placed in Locked Foundation for HyperTwist because it best serves the 'Live cube-recognition substrate' role; recommended action is 'integrate' with repurposing scope 'direct'. Confidence is high because this remains a metadata-level judgment until source audit confirms hidden modules, plugin points, adapters, or architectural strengths.",2.0,5.0,3.0,7705.0,4.0,,kkoomen/qbr,HyperTwist,,,,,,,,,,Original global Phase G v4 retained,MIT,known_from_reference_material,uploaded_reference_docs,no,,,,Supplemental intake references are advisory only; v6 adjudication remains the source of truth.,Potentially relevant,yes,v6 unified all-project source-of-truth pack,v5_carry_forward,,v6_unified_source_of_truth_pack,2.0,1,1.0,158.0,permissive_or_noncopyleft_known,direct_incorporation_ok,"This repo is aligned with a direct integration path for HyperTwist because it is either already implemented, strategically central, or donor-grade without a visible copyleft constraint in the current materials. Deep incorporation is sensible if the source audit confirms architectural cleanliness.","Direct embed, vendored module, package dependency, or tightly integrated adapter as the architecture requires.","Typically preserve notices, attribution, and license text where required; no special copyleft-driven disclosure posture is normally needed.",Usually unnecessary unless you later decide the existing implementation is too constraining architecturally.,high,strategic-or-implemented-component,yes,,,,,,,,,,,,,v6.3_final_source_of_truth,Merged v6.1 copyleft layer and v6.2 SRE layer; use v6.3 docs + workbook as canonical handoff.,selected_not_live_permissive_candidate,phase0r_permissive_eval_then_implement,"Phase 1R closed. Retain as a Phase 3R permissive implementation candidate; implement only from its packet authority and the retained-set contract, not by reopening Phase 0R." +2.0,kkoomen/qbr,https://github.com/kkoomen/qbr,HyperTwist,2.0,158.0,191.0,A,vision / perception / AR,foundation engine,vision donor,locked core candidate,integrate,direct,"Keep the core engine or major subsystem mostly intact; change wrappers, branding, storage/auth, and integration seams so it becomes a first-class part of the target stack. For this repo class, that usually means preserving calibration/detection/state-reconstruction logic while replacing camera UX and integration surfaces.","kkoomen/qbr — MIT — Webcam-based 3x3 solver with accurate OpenCV color detection (perfect vision starter). | kkoomen/qbr — MIT — Webcam CV solver (base for 3D vision). | kkoomen/qbr — MIT — Webcam CV color detection. | poliva/cubedex, ta...","Integrate as a computer vision / AR subsystem for HyperTwist. Preserve the strongest existing pieces — camera ingest, calibration, segmentation/detection, pose or facelet extraction, state normalization, solver bridge, replay overlay, AR anchors — and expose them behind a portfolio-stable interface. Wire first into vivaansinghvi07/rubix-cube-solver, then into cubing/cubing.js for orchestration, visualization, or data exchange.","Consolidate under the Hyperspeedcube + cubing.js + qbr nucleus, not beside it as a separate silo. Normalize data contracts, auth/permissions, storage, and telemetry; then attach as a service, plugin, canvas layer, trainer, or analysis module. Descending combination order: vivaansinghvi07/rubix-cube-solver, cubing/cubing.js, HactarCE/Hyperspeedcube.","Repurpose here means: turn it into a perception microservice, cube-state API, replay generator, or AR overlay donor for HyperTwist.",Map module boundaries; Identify hidden reusable internals; Define adapter/API boundary to target anchors; Write extraction tests against upstream behavior; Benchmark calibration pipeline; Extract state reconstruction; Wrap with camera/AR adapter,full subsystem extraction review,"Hidden value often sits in calibration, preprocessing, stabilization, object/state reconstruction, replay artifacts, and camera-to-domain state pipelines that are not obvious from demos.",Inspect preprocessing/calibration; tracking stabilization; state reconstruction; replay/event model; camera abstraction; fallback heuristics; testing assets/videos; performance shortcuts.,"Inspect package manifests, README/docs, src tree, examples, tests, CI workflows, config files, migrations/schemas, and hidden feature flags or experimental modules. Look for calibration routines, detection heuristics/models, color/state normalization, replay serialization, solver bridges, camera abstraction layers, and debug visualizations.","Audit kkoomen/qbr as a vision / perception / AR candidate for HyperTwist. Do not stop at README-level features. Inspect: Inspect preprocessing/calibration; tracking stabilization; state reconstruction; replay/event model; camera abstraction; fallback heuristics; testing assets/videos; performance shortcuts. Decide whether the best extraction path is direct and whether it belongs as foundation engine / vision donor. Test the three merger paths in order: 1) vivaansinghvi07/rubix-cube-solver [perception + replay donor]; 2) cubing/cubing.js [state/render backend]; 3) cross-project transfer candidate [future merger]. Return hidden modules, reusable schemas, protocol layers, plugin hooks, render/state models, datasets/test fixtures, and any subsystem stronger than the visible product shell.",vivaansinghvi07/rubix-cube-solver,perception + replay donor,Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.,cubing/cubing.js,state/render backend,Use the partner for canonical state or rendering abstractions and merge this repo's specialized logic on top.,cross-project transfer candidate,future merger,Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.,VectorShell | ScriptoriumAI,VectorShell can borrow spatial/rendering and perception primitives; ScriptoriumAI can borrow tutorial/educational visualization patterns rather than the full engine.,do not exclude,Keep in active merge-set and force full source audit before any demotion.,high,single-source signal; clear taxonomy; active integration value; foundation-level fit,high,portfolio anchor or repeatedly surfaced core candidate; memo mentions: 5,"Licensing intentionally ignored as a decision filter in this canonical evaluation; assess only architecture, capability, donor value, and concept transfer.",,,,"kkoomen/qbr — MIT — Webcam-based 3x3 solver with accurate OpenCV color detection (perfect vision starter). | kkoomen/qbr — MIT — Webcam CV solver (base for 3D vision). | kkoomen/qbr — MIT — Webcam CV color detection. | poliva/cubedex, tao-yu/Alg-Trainer, kkoomen/qbr, vivaansinghvi07/rubix-cube-solver, NuiLab/code-vr, molgenis/Graph2VR (core permissive parts), brianpeiris/RiftSketch, aMonteSl/CodeXR.","kkoomen/qbr is treated as integrate for HyperTwist because visible metadata points to the computer vision / AR layer. Surface signal: kkoomen/qbr — MIT — Webcam-based 3x3 solver with accurate OpenCV color detection (perfect vision starter). | kkoomen/qbr — MIT — Webcam CV solver (base for 3D vision). | kkoomen/qbr — MIT — Webcam CV color detection. | poliva/cubedex, ta... The likely value is substantial enough to preserve as a named subsystem rather than just mining isolated ideas.",memo,False,True,0.0,5.0,HT_cube_vision,HT_cube_vision_0001,computer vision / AR,Integrate as a shared building block across at least two projects. Its memo and bookmark signals place it in the computer vision / AR layer.,multi-project,computer vision / AR,integrate,heavy modification,medium,kkoomen/qbr,1.0,Locked Foundation,1.0,Primary architectural anchor for HyperTwist; strongest current fit in corpus for the 'Live cube-recognition substrate' role and should be source-audited before alternative bases.,Live cube-recognition substrate,Included,P0,"kkoomen/qbr is placed in Locked Foundation for HyperTwist because it best serves the 'Live cube-recognition substrate' role; recommended action is 'integrate' with repurposing scope 'direct'. Confidence is high because this remains a metadata-level judgment until source audit confirms hidden modules, plugin points, adapters, or architectural strengths.",2.0,5.0,3.0,7705.0,4.0,,kkoomen/qbr,HyperTwist,,,,,,,,,,Original global Phase G v4 retained,MIT,known_from_reference_material,uploaded_reference_docs,no,,,,Supplemental intake references are advisory only; v6 adjudication remains the source of truth.,Potentially relevant,yes,v6 unified all-project source-of-truth pack,v5_carry_forward,,v6_unified_source_of_truth_pack,2.0,1,1.0,158.0,permissive_or_noncopyleft_known,direct_incorporation_ok,"This repo is aligned with a direct integration path for HyperTwist because it is either already implemented, strategically central, or donor-grade without a visible copyleft constraint in the current materials. Deep incorporation is sensible if the source audit confirms architectural cleanliness.","Direct embed, vendored module, package dependency, or tightly integrated adapter as the architecture requires.","Typically preserve notices, attribution, and license text where required; no special copyleft-driven disclosure posture is normally needed.",Usually unnecessary unless you later decide the existing implementation is too constraining architecturally.,high,strategic-or-implemented-component,yes,,,,,,,,,,,,,v6.3_final_source_of_truth,Merged v6.1 copyleft layer and v6.2 SRE layer; use v6.3 docs + workbook as canonical handoff.,implemented_live_permissive,landed_permissive_preserve,"Phase 3R-E closed. Preserve as the landed first-party embodied companion, narration, lip-sync, gesture, subtitle, and avatar-embed lane; start future widening from the live-lane audit, then the 3R-E implementation packet, then REPO_LICENSE_TRACKING.md." ,cubing/alg.js,https://github.com/cubing/alg.js,HyperTwist,2.0,95.0,95.0,P0,puzzle_simulation_training_donor,puzzle_simulation_training_donor,geometry_renderer_or_binding,donor bench,repurpose,architecture only,"Moderate modification. Treat cubing/alg.js as a family-level donor for HyperTwist: extract the implementation layer that matches its strongest domain contribution, preserve its protocols/data models/CLI or renderer boundaries, and adapt only the surface integration needed for HyperTwist rather than rewriting it wholesale.","HyperTwist family. Likely value lies in puzzle logic, scrambler design, algorithm representations, n-dimensional geometry, rendering, bindings, or XR/game-engine surfaces relevant to hypercube and cube-training workflows.","Primary realization path: use as a simulation, training, renderer, binding, or integration donor inside HyperTwist's dual stack of physical-cube analysis and higher-dimensional virtual training.","Consolidate by HyperTwist layer: core puzzle logic, scramblers/algs, renderer/bindings, XR/game-engine surfaces, experiments/comparators.","Repurpose toward renderer abstractions, puzzle-logic libraries, solver bindings, training UIs, or XR/engine adapters.",Validate actual implementation breadth and hidden donor subsystems before promotion.,P0 tier source audit.,cubing/alg.js may contain stronger reusable internals than its surface description suggests.,"Inspect state representations, move/alg parsers, scrambler generators, geometry/math cores, renderer abstractions, engine bindings, and XR/web surfaces.","Inspect state representations, move/alg parsers, scrambler generators, geometry/math cores, renderer abstractions, engine bindings, and XR/web surfaces.","Audit cubing/alg.js directly in source. Preserve distinctions between foundation, donor, reserve, comparator, and exclusion.",HactarCE/Hyperspeedcube,foundation repo + feature donor,"Use cubing/alg.js as a HyperTwist donor into HactarCE/Hyperspeedcube for puzzle logic, bindings, renderer ideas, or training/runtime augmentation.",cubing/cubing.js,engine repo + interface donor,"Use cubing/alg.js as a HyperTwist donor into cubing/cubing.js for puzzle logic, bindings, renderer ideas, or training/runtime augmentation.",kkoomen/qbr,feature extraction only,"Use cubing/alg.js as a HyperTwist donor into kkoomen/qbr for puzzle logic, bindings, renderer ideas, or training/runtime augmentation.",multi-project,Many supplemental repos may reveal transferable abstractions after source inspection.,Exclude only after source audit proves weak or purely documentary value.,Supplemental intake row. Current exclusion posture is provisional.,medium,Supplemental intake heuristic.,medium,Pending direct source inspection.,Licensing intentionally ignored as a decision filter per canonical directive.,HyperTwist,HyperTwist,,Supplemental intake; reference docs advisory only.,cubing/alg.js is introduced in v6 so the portfolio reflects the complete repo picture before exclusions.,HyperTwist & ScriptoriumAI.txt,0,0,1.0,0.0,HT_cube_semantics,HT_cube_semantics_0002,puzzle_simulation_training_donor,Supplemental v6 intake from hypertwist_and_scriptoriumai.,HyperTwist,puzzle_simulation_training_donor,donor candidate,moderate modification,medium,cubing/alg.js,1.0,Donor Bench,4.0,Standalone GPL parser/AST package with focused semantics value best preserved through Model A / Model B separation.,Focused restrictive clean-room donor target,included_in_v6_supplemental_intake,P2,"Keep as its own clean-room donor lane because it isolates parser, AST, traversal, validation, keyboard-move, and URL/interchange semantics.",2.0,2.0,2.0,7708.0,1.0,,cubing/alg.js,HyperTwist,supplemental_v6_not_runtime_anchored,,,,,,,,no,v6_unified_source_of_truth_pack,GPL-3.0-or-later,known_from_reference_material,uploaded_reference_docs,,,,,,,,,,,,2.0,1,4.0,95.0,mixed_or_boundary_sensitive_known,reverse_engineer_preferred,The repo is GPL-3.0-or-later and should remain a focused clean-room donor lane rather than direct donor code. Preserve the parser/AST/traversal semantics through a scrubbed Model A handoff only.,Model A may inspect the restrictive source; Model B should implement only from a scrubbed first-party specification.,Direct incorporation would require GPL-compatible distribution/compliance and is not the planned HyperTwist path.,Yes — preferred path for reproducing parser/AST/traversal semantics in first-party code.,high,gpl-clean-room-donor,no,,,,,,,,,,,,,v6.3_final_source_of_truth,Assigned to HT_cube_semantics during cluster normalization on 2026-04-25.,selected_not_live_clean_room_candidate,phase0r_clean_room_eval_then_model_a_model_b,Phase 1R closed. Retain as a Phase 5R clean-room-only algorithm-language candidate; implement only from the scrubbed Model A dossier and retained-set contract. ,cubing/twisty.js,https://github.com/cubing/twisty.js,HyperTwist,2.0,95.0,95.0,P0,puzzle_simulation_training_donor,puzzle_simulation_training_donor,geometry_renderer_or_binding,donor bench,repurpose,architecture only,"Moderate modification. Treat cubing/twisty.js as a family-level donor for HyperTwist: extract the implementation layer that matches its strongest domain contribution, preserve its protocols/data models/CLI or renderer boundaries, and adapt only the surface integration needed for HyperTwist rather than rewriting it wholesale.","HyperTwist family. Likely value lies in puzzle logic, scrambler design, algorithm representations, n-dimensional geometry, rendering, bindings, or XR/game-engine surfaces relevant to hypercube and cube-training workflows.","Primary realization path: use as a simulation, training, renderer, binding, or integration donor inside HyperTwist's dual stack of physical-cube analysis and higher-dimensional virtual training.","Consolidate by HyperTwist layer: core puzzle logic, scramblers/algs, renderer/bindings, XR/game-engine surfaces, experiments/comparators.","Repurpose toward renderer abstractions, puzzle-logic libraries, solver bindings, training UIs, or XR/engine adapters.",Validate actual implementation breadth and hidden donor subsystems before promotion.,P0 tier source audit.,cubing/twisty.js may contain stronger reusable internals than its surface description suggests.,"Inspect state representations, move/alg parsers, scrambler generators, geometry/math cores, renderer abstractions, engine bindings, and XR/web surfaces.","Inspect state representations, move/alg parsers, scrambler generators, geometry/math cores, renderer abstractions, engine bindings, and XR/web surfaces.","Audit cubing/twisty.js directly in source. Preserve distinctions between foundation, donor, reserve, comparator, and exclusion.",HactarCE/Hyperspeedcube,foundation repo + feature donor,"Use cubing/twisty.js as a HyperTwist donor into HactarCE/Hyperspeedcube for puzzle logic, bindings, renderer ideas, or training/runtime augmentation.",cubing/cubing.js,engine repo + interface donor,"Use cubing/twisty.js as a HyperTwist donor into cubing/cubing.js for puzzle logic, bindings, renderer ideas, or training/runtime augmentation.",kkoomen/qbr,feature extraction only,"Use cubing/twisty.js as a HyperTwist donor into kkoomen/qbr for puzzle logic, bindings, renderer ideas, or training/runtime augmentation.",multi-project,Many supplemental repos may reveal transferable abstractions after source inspection.,Exclude only after source audit proves weak or purely documentary value.,Supplemental intake row. Current exclusion posture is provisional.,medium,Supplemental intake heuristic.,medium,Pending direct source inspection.,Licensing intentionally ignored as a decision filter per canonical directive.,HyperTwist,HyperTwist,,Supplemental intake; reference docs advisory only.,cubing/twisty.js is introduced in v6 so the portfolio reflects the complete repo picture before exclusions.,HyperTwist & ScriptoriumAI.txt,0,0,1.0,0.0,HT_cube_semantics,HT_cube_semantics_0003,puzzle_simulation_training_donor,Supplemental v6 intake from hypertwist_and_scriptoriumai.,HyperTwist,puzzle_simulation_training_donor,donor candidate,moderate modification,medium,cubing/twisty.js,1.0,Donor Bench,4.0,Standalone GPL viewer/player shell with focused browser twisty behavior best preserved through Model A / Model B separation.,Focused restrictive clean-room donor target,included_in_v6_supplemental_intake,P2,Keep as its own clean-room donor lane because it isolates browser twisty-viewer/player shell behavior and control-bar semantics.,2.0,2.0,2.0,7710.0,3.0,,cubing/twisty.js,HyperTwist,supplemental_v6_not_runtime_anchored,,,,,,,,no,v6_unified_source_of_truth_pack,GPL-3.0-or-later,known_from_reference_material,uploaded_reference_docs,,,,,,,,,,,,2.0,1,4.0,95.0,mixed_or_boundary_sensitive_known,reverse_engineer_preferred,"The repo is GPL-3.0-or-later and should remain a focused clean-room donor lane rather than direct donor code. Preserve viewer/player shell, scrubber, and twisty-element behavior through a scrubbed Model A handoff only.",Model A may inspect the restrictive source; Model B should implement only from a scrubbed first-party specification.,Direct incorporation would require GPL-compatible distribution/compliance and is not the planned HyperTwist path.,Yes — preferred path for reproducing compact twisty-viewer behavior in first-party code.,high,gpl-clean-room-donor,no,,,,,,,,,,,,,v6.3_final_source_of_truth,Assigned to HT_cube_semantics during cluster normalization on 2026-04-25.,selected_not_live_clean_room_candidate,phase0r_clean_room_eval_then_model_a_model_b,Phase 1R closed. Retain as a Phase 5R clean-room-only embedded viewer candidate; implement only from the scrubbed Model A dossier and retained-set contract. 1747.0,coqui-ai/TTS,https://github.com/coqui-ai/TTS,multi-project,2.0,71.0,80.0,C,voice / multimodal I/O,subsystem donor,multimodal donor,donor bench,repurpose,moderate modification,"Retain the valuable internal engine, but expect to replace UI/product shell, adapt schemas/APIs, and refactor boundaries so it can plug into the target anchors cleanly. For this repo class, that usually means preserving streaming/audio pipeline logic while adapting commands, wake flows, and assistant integration.",https://github.com/coqui-ai/TTS – Coqui XTTS v2.,"Repurpose selected subsystems rather than the whole product. Mine the repo for synthesis orchestration, multilingual and speaker handling, local service wrappers, voice-conversion paths, and model-registry/license handling; keep what materially shortens build time, but rebind data contracts, permissions, storage, and deployment to the target architecture. Best first pairing order: rhasspy/piper, ggml-org/whisper.cpp, SYSTRAN/faster-whisper.","Consolidate under the project-specific anchor stack, not beside it as a separate silo. Normalize data contracts, auth/permissions, storage, and telemetry; then attach as a service, plugin, canvas layer, trainer, or analysis module. Descending combination order: sentrux/sentrux, HactarCE/Hyperspeedcube, outline/outline.","Repurpose here means: turn it into a bounded voice-service seam, coach narration donor, or multilingual TTS and cloning donor.",Map module boundaries; Identify hidden reusable internals; Define adapter/API boundary to target anchors; Write extraction tests against upstream behavior; Isolate streaming/audio pipeline; Normalize command schema; Add local/offline fallback layer,deep source audit,"Hidden value often lives in streaming segmentation, VAD, device abstraction, latency mitigation, translation chains, and local/offline fallback paths.","Inspect public API, synthesis and orchestration spine, server boundary, multilingual and speaker handling, XTTS path, model registry and license metadata, and optional voice conversion.","Inspect package manifests, README/docs, src tree, examples, tests, CI workflows, model registry files, and hidden experimental modules. Look for synthesis orchestration, sentence splitting, multilingual and speaker handling, voice conversion, server deployment patterns, and model-license metadata.","Audit coqui-ai/TTS as a voice / multimodal I/O candidate for multi-project. Do not stop at README-level features. Inspect: public API surface, synthesis/orchestration spine, server boundary, multilingual and speaker handling, XTTS path, model registry and license metadata, and optional voice conversion. Decide whether it should remain the strongest voice/coaching donor and what should stay behind a bounded voice-service seam. Test the three merger paths in order: 1) project-local anchor [base + donor]; 2) shared portfolio utility [augmenter]; 3) cross-project transfer candidate [future merger]. Return hidden modules, reusable schemas, protocol layers, runtime boundaries, tests/fixtures, and any subsystem stronger than the visible shell.",project-local anchor,base + donor,Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.,shared portfolio utility,augmenter,Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.,cross-project transfer candidate,future merger,Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.,VectorShell | HyperTwist | ScriptoriumAI,"This capability is broadly portable across the portfolio because interaction, orchestration, and shell/UI patterns can be shared with thin domain adapters.","exclude from core, keep as donor","Do not let it consume roadmap as a full product shell; mine reusable engines, adapters, schemas, UX patterns, or datasets.",medium-low,single-source signal; clear taxonomy; mostly donor/reference role,medium,memo mentions: 1,"Licensing intentionally ignored as a decision filter in this canonical evaluation; assess only architecture, capability, donor value, and concept transfer.",,,,https://github.com/coqui-ai/TTS – Coqui XTTS v2.,"coqui-ai/TTS is treated as repurpose for multi-project because visible metadata points to the voice / speech / audio layer. Surface signal: https://github.com/coqui-ai/TTS – Coqui XTTS v2. The fit looks real, but more as a donor/augmenter than as a standalone foundation.",memo,False,True,0.0,1.0,MU_misc,MU_misc_0002,voice / speech / audio,"Repurpose selectively for multi-project. Its source-backed role is the richest current voice-output and coaching donor, but it should stay behind a bounded voice-service seam because code and model payload licensing diverge.",future/adjacent use,voice / speech / audio,repurpose,moderate modification,medium,coqui-ai/tts,1.0,Donor Bench,4.0,"Useful subsystem donor for multi-project, primarily in the 'Cross-project / future-adjacent' role; strongest current voice and coaching donor, but boundary-sensitive because code and model payload licensing must be separated.",Cross-project / future-adjacent,Included,P2,"coqui-ai/TTS is placed in Donor Bench for multi-project because it provides the richest current voice-output and coaching architecture in the stack. Recommended action remains repurpose, but the real retained value is synthesis orchestration, multilingual and speaker handling, XTTS/voice-conversion paths, and model-registry discipline rather than broad assistant scope.",4.0,2.0,2.0,7713.0,4.0,,coqui-ai/tts,multi-project,,,,,,,,,,Original global Phase G v4 retained,MPL-2.0 code; mixed model payload licenses,known_from_reference_material,uploaded_reference_docs,no,,,,Supplemental intake references are advisory only; v6 adjudication remains the source of truth.,Usually indirect,yes,v6 unified all-project source-of-truth pack,v5_carry_forward,,v6_unified_source_of_truth_pack,2.0,3,4.0,71.0,mixed_or_boundary_sensitive_known,bounded_sidecar_or_selective_reimplementation,"Code is usable under MPL-2.0, but selected model weights carry mixed per-model licenses and some require separate terms. Keep the repo behind a bounded voice-service seam and decide model adoption case by case rather than treating it as a blanket permissive dependency.",Use the code behind a bounded voice-service seam; select model weights individually and keep model-license decisions separate from code adoption.,"Preserve MPL notices and file-level obligations where applicable, and review each chosen model license or ToS separately before shipping.",Sometimes useful only if you later need a fully proprietary embedded voice stack or want to avoid model-license entanglement; not the default path.,medium,model-license-selection-required,yes,,,,,,,,,,,,,v6.3_final_source_of_truth,Merged v6.1 copyleft layer and v6.2 SRE layer; use v6.3 docs + workbook as canonical handoff.,,, ,HactarCE/2x2x2x2-Scrambler,https://github.com/HactarCE/2x2x2x2-Scrambler,HyperTwist,2.0,63.0,63.0,P2,puzzle_simulation_training_donor,puzzle_simulation_training_donor,geometry_renderer_or_binding,donor bench,repurpose,architecture only,"Architecture only. Treat HactarCE/2x2x2x2-Scrambler as a design and subsystem reference first; source audit should look for transplantable patterns, adapters, data contracts, pipeline ideas, or UI/control abstractions before any decision to operationalize.","HyperTwist family. Likely value lies in puzzle logic, scrambler design, algorithm representations, n-dimensional geometry, rendering, bindings, or XR/game-engine surfaces relevant to hypercube and cube-training workflows.","Primary realization path: use as a simulation, training, renderer, binding, or integration donor inside HyperTwist's dual stack of physical-cube analysis and higher-dimensional virtual training.","Consolidate by HyperTwist layer: core puzzle logic, scramblers/algs, renderer/bindings, XR/game-engine surfaces, experiments/comparators.","Repurpose toward renderer abstractions, puzzle-logic libraries, solver bindings, training UIs, or XR/engine adapters.",Validate actual implementation breadth and hidden donor subsystems before promotion.,P2 tier source audit.,HactarCE/2x2x2x2-Scrambler may contain stronger reusable internals than its surface description suggests.,"Inspect state representations, move/alg parsers, scrambler generators, geometry/math cores, renderer abstractions, engine bindings, and XR/web surfaces.","Inspect state representations, move/alg parsers, scrambler generators, geometry/math cores, renderer abstractions, engine bindings, and XR/web surfaces.","Audit HactarCE/2x2x2x2-Scrambler directly in source. Preserve distinctions between foundation, donor, reserve, comparator, and exclusion.",HactarCE/Hyperspeedcube,foundation repo + feature donor,"Use HactarCE/2x2x2x2-Scrambler as a HyperTwist donor into HactarCE/Hyperspeedcube for puzzle logic, bindings, renderer ideas, or training/runtime augmentation.",cubing/cubing.js,engine repo + interface donor,"Use HactarCE/2x2x2x2-Scrambler as a HyperTwist donor into cubing/cubing.js for puzzle logic, bindings, renderer ideas, or training/runtime augmentation.",kkoomen/qbr,feature extraction only,"Use HactarCE/2x2x2x2-Scrambler as a HyperTwist donor into kkoomen/qbr for puzzle logic, bindings, renderer ideas, or training/runtime augmentation.",multi-project,Many supplemental repos may reveal transferable abstractions after source inspection.,Exclude only after source audit proves weak or purely documentary value.,Supplemental intake row. Current exclusion posture is provisional.,low-to-medium,Supplemental intake heuristic.,low-to-medium,Pending direct source inspection.,Licensing intentionally ignored as a decision filter per canonical directive.,HyperTwist,HyperTwist,,Supplemental intake; reference docs advisory only.,HactarCE/2x2x2x2-Scrambler is introduced in v6 so the portfolio reflects the complete repo picture before exclusions.,HyperTwist & ScriptoriumAI.txt,0,0,1.0,0.0,HT_cube_semantics,HT_cube_semantics_0004,puzzle_simulation_training_donor,Supplemental v6 intake from hypertwist_and_scriptoriumai.,HyperTwist,puzzle_simulation_training_donor,future candidate,architecture only,low-to-medium,hactarce/2x2x2x2-scrambler,1.0,Donor Bench,6.0,"GPL scrambler with copied-port lineage notes; valuable only through restrictive clean-room extraction, not donor use.",Focused restrictive clean-room donor target,included_in_v6_supplemental_intake,P2,"Keep as a narrow but real clean-room donor for Melinda 2x2x2x2 state encoding, handedness/parity repair, random-state generation, move-family representation, and flat debug/teaching views.",2.0,3.0,3.0,7714.0,5.0,,hactarce/2x2x2x2-scrambler,HyperTwist,supplemental_v6_not_runtime_anchored,,,,,,,,no,v6_unified_source_of_truth_pack,GPL-3.0,known_from_reference_material,uploaded_reference_docs,,,,,,,,,,,,2.0,3,6.0,63.0,mixed_or_boundary_sensitive_known,reverse_engineer_preferred,The repo is GPL-3.0 and the source explicitly notes a ported lineage from an earlier scrambler. Retain it only as a focused clean-room donor target and implement any valuable behavior through a scrubbed first-party specification.,Model A may inspect the restrictive source; Model B should implement only from a scrubbed first-party specification.,Direct incorporation would require GPL-compatible distribution/compliance and is not the planned HyperTwist path.,Yes — this is the preferred path for reproducing the 2x2x2x2 scrambler/state behaviors in first-party code.,high,gpl-clean-room-donor,no,,,,,,,,,,,,,v6.3_final_source_of_truth,Assigned to HT_cube_semantics during cluster normalization on 2026-04-25.,selected_not_live_clean_room_candidate,phase0r_clean_room_eval_then_model_a_model_b,Phase 1R closed. Retain as a Phase 5R clean-room-only Melinda 2x2x2x2 candidate; keep copied-port lineage explicit and implement only from the scrubbed Model A dossier. -3.0,vivaansinghvi07/rubix-cube-solver,https://github.com/vivaansinghvi07/rubix-cube-solver,HyperTwist,3.0,158.0,191.0,A,vision / perception / AR,foundation engine,vision donor,locked core candidate,integrate,direct,"Keep the core engine or major subsystem mostly intact; change wrappers, branding, storage/auth, and integration seams so it becomes a first-class part of the target stack. For this repo class, that usually means preserving calibration/detection/state-reconstruction logic while replacing camera UX and integration surfaces.","Yes — 100% possible to consolidate everything into one no-compromises, enterprise-grade platform. You're not half-arsing it, and neither am I. Modern vision models (and even classical OpenCV pipelines refined over the last decade) are mo...","Integrate as a computer vision / AR subsystem for HyperTwist. Preserve the strongest existing pieces — camera ingest, calibration, segmentation/detection, pose or facelet extraction, state normalization, solver bridge, replay overlay, AR anchors — and expose them behind a portfolio-stable interface. Wire first into kkoomen/qbr, then into cubing/cubing.js for orchestration, visualization, or data exchange.","Consolidate under the Hyperspeedcube + cubing.js + qbr nucleus, not beside it as a separate silo. Normalize data contracts, auth/permissions, storage, and telemetry; then attach as a service, plugin, canvas layer, trainer, or analysis module. Descending combination order: kkoomen/qbr, cubing/cubing.js, HactarCE/Hyperspeedcube.","Repurpose here means: turn it into a perception microservice, cube-state API, replay generator, or AR overlay donor for HyperTwist.",Map module boundaries; Identify hidden reusable internals; Define adapter/API boundary to target anchors; Write extraction tests against upstream behavior; Benchmark calibration pipeline; Extract state reconstruction; Wrap with camera/AR adapter,full subsystem extraction review,"Hidden value often sits in calibration, preprocessing, stabilization, object/state reconstruction, replay artifacts, and camera-to-domain state pipelines that are not obvious from demos.",Inspect preprocessing/calibration; tracking stabilization; state reconstruction; replay/event model; camera abstraction; fallback heuristics; testing assets/videos; performance shortcuts.,"Inspect package manifests, README/docs, src tree, examples, tests, CI workflows, config files, migrations/schemas, and hidden feature flags or experimental modules. Look for calibration routines, detection heuristics/models, color/state normalization, replay serialization, solver bridges, camera abstraction layers, and debug visualizations.","Audit vivaansinghvi07/rubix-cube-solver as a vision / perception / AR candidate for HyperTwist. Do not stop at README-level features. Inspect: Inspect preprocessing/calibration; tracking stabilization; state reconstruction; replay/event model; camera abstraction; fallback heuristics; testing assets/videos; performance shortcuts. Decide whether the best extraction path is direct and whether it belongs as foundation engine / vision donor. Test the three merger paths in order: 1) kkoomen/qbr [foundation + perception donor]; 2) cubing/cubing.js [state/render backend]; 3) cross-project transfer candidate [future merger]. Return hidden modules, reusable schemas, protocol layers, plugin hooks, render/state models, datasets/test fixtures, and any subsystem stronger than the visible product shell.",kkoomen/qbr,foundation + perception donor,"Use this repo against the partner as an augmenting layer; preserve the partner as the likely base and mine this repo for capabilities that improve breadth, UX, or specialization.",cubing/cubing.js,state/render backend,Use the partner for canonical state or rendering abstractions and merge this repo's specialized logic on top.,cross-project transfer candidate,future merger,Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.,VectorShell | ScriptoriumAI,VectorShell can borrow spatial/rendering and perception primitives; ScriptoriumAI can borrow tutorial/educational visualization patterns rather than the full engine.,do not exclude,Keep in active merge-set and force full source audit before any demotion.,high,single-source signal; clear taxonomy; active integration value; foundation-level fit,high,portfolio anchor or repeatedly surfaced core candidate; memo mentions: 10,"Licensing intentionally ignored as a decision filter in this canonical evaluation; assess only architecture, capability, donor value, and concept transfer.",,,,"Yes — 100% possible to consolidate everything into one no-compromises, enterprise-grade platform. You're not half-arsing it, and neither am I. Modern vision models (and even classical OpenCV pipelines refined over the last decade) are more than accurate enough in 2026 for reliable small-square/facelet color recognition on a standard 3x3 (or larger) Rubik's Cube under normal lighting. Production examples prove it:Multiple MIT-licensed projects (qb",vivaansinghvi07/rubix-cube-solver is treated as integrate for HyperTwist because current dossier work keeps it in the committed vision path as the strongest reconstruction and replay-oriented companion to qbr rather than as a generic donor.,memo,False,True,0.0,10.0,HT_cube_vision,HT_cube_vision_0002,computer vision / AR,Integrate primarily for HyperTwist. Its memo and bookmark signals place it in the computer vision / AR layer.,HyperTwist,computer vision / AR,integrate,heavy modification,medium,vivaansinghvi07/rubix-cube-solver,1.0,Locked Parallel Foundation,2.0,Part of the irreducible core stack for HyperTwist; kept as the parallel foundation and strongest reconstruction companion to qbr.,Parallel foundation and reconstruction companion donor,Included,P0,"vivaansinghvi07/rubix-cube-solver is placed in Locked Parallel Foundation for HyperTwist because it best serves the 'Parallel foundation and reconstruction companion donor' role; recommended action is 'integrate' with repurposing scope 'direct'. Confidence is high because this remains a metadata-level judgment until source audit confirms hidden modules, plugin points, adapters, or architectural strengths.",2.0,5.0,3.0,7819.0,110.0,,vivaansinghvi07/rubix-cube-solver,HyperTwist,,,,,,,,,,Original global Phase G v4 retained,MIT,known_from_reference_material,uploaded_reference_docs,no,,,,Supplemental intake references are advisory only; v6 adjudication remains the source of truth.,Usually indirect,yes,v6 unified all-project source-of-truth pack,v5_carry_forward,,v6_unified_source_of_truth_pack,3.0,1,2.0,158.0,permissive_or_noncopyleft_known,direct_incorporation_ok,"This repo is aligned with a direct integration path for HyperTwist because it is either already implemented, strategically central, or donor-grade without a visible copyleft constraint in the current materials. Deep incorporation is sensible if the source audit confirms architectural cleanliness.","Direct embed, vendored module, package dependency, or tightly integrated adapter as the architecture requires.","Typically preserve notices, attribution, and license text where required; no special copyleft-driven disclosure posture is normally needed.",Usually unnecessary unless you later decide the existing implementation is too constraining architecturally.,high,strategic-or-implemented-component,yes,,,,,,,,,,,,,v6.3_final_source_of_truth,Normalized legacy wording to dossier-backed parallel-foundation posture on 2026-04-25.,selected_not_live_permissive_candidate,phase0r_permissive_eval_then_implement,"Phase 1R closed. Retain as a Phase 3R permissive implementation candidate; implement only from its packet authority and the retained-set contract, not by reopening Phase 0R." +3.0,vivaansinghvi07/rubix-cube-solver,https://github.com/vivaansinghvi07/rubix-cube-solver,HyperTwist,3.0,158.0,191.0,A,vision / perception / AR,foundation engine,vision donor,locked core candidate,integrate,direct,"Keep the core engine or major subsystem mostly intact; change wrappers, branding, storage/auth, and integration seams so it becomes a first-class part of the target stack. For this repo class, that usually means preserving calibration/detection/state-reconstruction logic while replacing camera UX and integration surfaces.","Yes — 100% possible to consolidate everything into one no-compromises, enterprise-grade platform. You're not half-arsing it, and neither am I. Modern vision models (and even classical OpenCV pipelines refined over the last decade) are mo...","Integrate as a computer vision / AR subsystem for HyperTwist. Preserve the strongest existing pieces — camera ingest, calibration, segmentation/detection, pose or facelet extraction, state normalization, solver bridge, replay overlay, AR anchors — and expose them behind a portfolio-stable interface. Wire first into kkoomen/qbr, then into cubing/cubing.js for orchestration, visualization, or data exchange.","Consolidate under the Hyperspeedcube + cubing.js + qbr nucleus, not beside it as a separate silo. Normalize data contracts, auth/permissions, storage, and telemetry; then attach as a service, plugin, canvas layer, trainer, or analysis module. Descending combination order: kkoomen/qbr, cubing/cubing.js, HactarCE/Hyperspeedcube.","Repurpose here means: turn it into a perception microservice, cube-state API, replay generator, or AR overlay donor for HyperTwist.",Map module boundaries; Identify hidden reusable internals; Define adapter/API boundary to target anchors; Write extraction tests against upstream behavior; Benchmark calibration pipeline; Extract state reconstruction; Wrap with camera/AR adapter,full subsystem extraction review,"Hidden value often sits in calibration, preprocessing, stabilization, object/state reconstruction, replay artifacts, and camera-to-domain state pipelines that are not obvious from demos.",Inspect preprocessing/calibration; tracking stabilization; state reconstruction; replay/event model; camera abstraction; fallback heuristics; testing assets/videos; performance shortcuts.,"Inspect package manifests, README/docs, src tree, examples, tests, CI workflows, config files, migrations/schemas, and hidden feature flags or experimental modules. Look for calibration routines, detection heuristics/models, color/state normalization, replay serialization, solver bridges, camera abstraction layers, and debug visualizations.","Audit vivaansinghvi07/rubix-cube-solver as a vision / perception / AR candidate for HyperTwist. Do not stop at README-level features. Inspect: Inspect preprocessing/calibration; tracking stabilization; state reconstruction; replay/event model; camera abstraction; fallback heuristics; testing assets/videos; performance shortcuts. Decide whether the best extraction path is direct and whether it belongs as foundation engine / vision donor. Test the three merger paths in order: 1) kkoomen/qbr [foundation + perception donor]; 2) cubing/cubing.js [state/render backend]; 3) cross-project transfer candidate [future merger]. Return hidden modules, reusable schemas, protocol layers, plugin hooks, render/state models, datasets/test fixtures, and any subsystem stronger than the visible product shell.",kkoomen/qbr,foundation + perception donor,"Use this repo against the partner as an augmenting layer; preserve the partner as the likely base and mine this repo for capabilities that improve breadth, UX, or specialization.",cubing/cubing.js,state/render backend,Use the partner for canonical state or rendering abstractions and merge this repo's specialized logic on top.,cross-project transfer candidate,future merger,Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.,VectorShell | ScriptoriumAI,VectorShell can borrow spatial/rendering and perception primitives; ScriptoriumAI can borrow tutorial/educational visualization patterns rather than the full engine.,do not exclude,Keep in active merge-set and force full source audit before any demotion.,high,single-source signal; clear taxonomy; active integration value; foundation-level fit,high,portfolio anchor or repeatedly surfaced core candidate; memo mentions: 10,"Licensing intentionally ignored as a decision filter in this canonical evaluation; assess only architecture, capability, donor value, and concept transfer.",,,,"Yes — 100% possible to consolidate everything into one no-compromises, enterprise-grade platform. You're not half-arsing it, and neither am I. Modern vision models (and even classical OpenCV pipelines refined over the last decade) are more than accurate enough in 2026 for reliable small-square/facelet color recognition on a standard 3x3 (or larger) Rubik's Cube under normal lighting. Production examples prove it:Multiple MIT-licensed projects (qb",vivaansinghvi07/rubix-cube-solver is treated as integrate for HyperTwist because current dossier work keeps it in the committed vision path as the strongest reconstruction and replay-oriented companion to qbr rather than as a generic donor.,memo,False,True,0.0,10.0,HT_cube_vision,HT_cube_vision_0002,computer vision / AR,Integrate primarily for HyperTwist. Its memo and bookmark signals place it in the computer vision / AR layer.,HyperTwist,computer vision / AR,integrate,heavy modification,medium,vivaansinghvi07/rubix-cube-solver,1.0,Locked Parallel Foundation,2.0,Part of the irreducible core stack for HyperTwist; kept as the parallel foundation and strongest reconstruction companion to qbr.,Parallel foundation and reconstruction companion donor,Included,P0,"vivaansinghvi07/rubix-cube-solver is placed in Locked Parallel Foundation for HyperTwist because it best serves the 'Parallel foundation and reconstruction companion donor' role; recommended action is 'integrate' with repurposing scope 'direct'. Confidence is high because this remains a metadata-level judgment until source audit confirms hidden modules, plugin points, adapters, or architectural strengths.",2.0,5.0,3.0,7819.0,110.0,,vivaansinghvi07/rubix-cube-solver,HyperTwist,,,,,,,,,,Original global Phase G v4 retained,MIT,known_from_reference_material,uploaded_reference_docs,no,,,,Supplemental intake references are advisory only; v6 adjudication remains the source of truth.,Usually indirect,yes,v6 unified all-project source-of-truth pack,v5_carry_forward,,v6_unified_source_of_truth_pack,3.0,1,2.0,158.0,permissive_or_noncopyleft_known,direct_incorporation_ok,"This repo is aligned with a direct integration path for HyperTwist because it is either already implemented, strategically central, or donor-grade without a visible copyleft constraint in the current materials. Deep incorporation is sensible if the source audit confirms architectural cleanliness.","Direct embed, vendored module, package dependency, or tightly integrated adapter as the architecture requires.","Typically preserve notices, attribution, and license text where required; no special copyleft-driven disclosure posture is normally needed.",Usually unnecessary unless you later decide the existing implementation is too constraining architecturally.,high,strategic-or-implemented-component,yes,,,,,,,,,,,,,v6.3_final_source_of_truth,Normalized legacy wording to dossier-backed parallel-foundation posture on 2026-04-25.,implemented_live_permissive,landed_permissive_preserve,"Phase 3R-E closed. Preserve as the landed first-party embodied companion, narration, lip-sync, gesture, subtitle, and avatar-embed lane; start future widening from the live-lane audit, then the 3R-E implementation packet, then REPO_LICENSE_TRACKING.md." 1748.0,ggml-org/whisper.cpp,https://github.com/ggml-org/whisper.cpp,multi-project,3.0,71.0,80.0,C,voice / multimodal I/O,subsystem donor,multimodal donor,donor bench,repurpose,moderate modification,"Retain the valuable internal engine, but expect to replace UI/product shell, adapt schemas/APIs, and refactor boundaries so it can plug into the target anchors cleanly. For this repo class, that usually means preserving streaming/audio pipeline logic while adapting commands, wake flows, and assistant integration.",7. Speech / Voice Models (STT + TTS)ggml-org/whisper.cpp – https://github.com/ggml-org/whisper.cpp – MIT – Native C++ Whisper for STT.,"Repurpose selected subsystems rather than the whole product. Mine the repo for native STT runtime seams, VAD, grammar-constrained decoding, segmented speech capture, and server-side deployment patterns; keep what materially shortens build time, but rebind data contracts, permissions, storage, and deployment to the target architecture. Best first pairing order: SYSTRAN/faster-whisper, rhasspy/piper, coqui-ai/TTS.","Consolidate under the project-specific anchor stack, not beside it as a separate silo. Normalize data contracts, auth/permissions, storage, and telemetry; then attach as a service, plugin, canvas layer, trainer, or analysis module. Descending combination order: sentrux/sentrux, HactarCE/Hyperspeedcube, outline/outline.","Repurpose here means: turn it into an offline STT sidecar, grammar-constrained command surface, or native speech-input donor.",Map module boundaries; Identify hidden reusable internals; Define adapter/API boundary to target anchors; Write extraction tests against upstream behavior; Isolate streaming/audio pipeline; Normalize command schema; Add local/offline fallback layer,deep source audit,"Hidden value often lives in streaming segmentation, VAD, device abstraction, latency mitigation, translation chains, and local/offline fallback paths.",Inspect C/C++ API surface; VAD path; grammar-constrained decoding; server/runtime examples; model loading and portability seams; tests and benchmarks.,"Inspect package manifests, README/docs, src/include tree, examples, tests, CI workflows, build configs, model tooling, and hidden experimental modules. Look for VAD, grammar support, streaming/segmentation, server boundaries, device/runtime abstraction, and performance shortcuts.","Audit ggml-org/whisper.cpp as a voice / multimodal I/O candidate for multi-project. Do not stop at README-level features. Inspect: C/C++ API surface, VAD, grammar-constrained decoding, server/runtime examples, model loading and portability seams, and benchmark/test coverage. Decide whether it should remain the primary offline STT sidecar candidate and what should stay behind a bounded native seam. Test the three merger paths in order: 1) project-local anchor [base + donor]; 2) shared portfolio utility [augmenter]; 3) cross-project transfer candidate [future merger]. Return hidden modules, reusable schemas, protocol layers, runtime boundaries, tests/benchmarks, and any subsystem stronger than the visible shell.",project-local anchor,base + donor,Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.,shared portfolio utility,augmenter,Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.,cross-project transfer candidate,future merger,Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.,VectorShell | HyperTwist | ScriptoriumAI,"This capability is broadly portable across the portfolio because interaction, orchestration, and shell/UI patterns can be shared with thin domain adapters.","exclude from core, keep as donor","Do not let it consume roadmap as a full product shell; mine reusable engines, adapters, schemas, UX patterns, or datasets.",medium-low,single-source signal; clear taxonomy; mostly donor/reference role,medium,memo mentions: 1,"Licensing intentionally ignored as a decision filter in this canonical evaluation; assess only architecture, capability, donor value, and concept transfer.",,,,7. Speech / Voice Models (STT + TTS)ggml-org/whisper.cpp – https://github.com/ggml-org/whisper.cpp – MIT – Native C++ Whisper for STT.,"ggml-org/whisper.cpp is treated as repurpose for multi-project because visible metadata points to the voice / speech / audio layer. Surface signal: 7. Speech / Voice Models (STT + TTS)ggml-org/whisper.cpp – https://github.com/ggml-org/whisper.cpp – MIT – Native C++ Whisper for STT. The fit looks real, but more as a donor/augmenter than as a standalone foundation.",memo,False,True,0.0,1.0,MU_misc,MU_misc_0003,voice / speech / audio,"Repurpose selectively for multi-project. Its source-backed role is a bounded speech-input donor and offline/native STT sidecar candidate, not an exclusion-only adjunct.",future/adjacent use,voice / speech / audio,repurpose,moderate modification,medium,ggml-org/whisper.cpp,1.0,Donor Bench,4.0,"Useful subsystem donor for multi-project, primarily in the 'Cross-project / future-adjacent' role; strongest current native/offline STT sidecar candidate in the voice stack.",Cross-project / future-adjacent,Included,P2,"ggml-org/whisper.cpp is placed in Donor Bench for multi-project because it is the clearest native/offline STT anchor in the voice stack. Recommended action remains repurpose, but the real retained value is a bounded speech-input runtime, VAD, grammar-constrained decoding, and portable deployment rather than a full product shell.",4.0,2.0,2.0,7850.0,6.0,,ggml-org/whisper.cpp,multi-project,,,,,,,,,,Original global Phase G v4 retained,MIT,known_from_reference_material,uploaded_reference_docs,no,,,,Supplemental intake references are advisory only; v6 adjudication remains the source of truth.,Usually indirect,yes,v6 unified all-project source-of-truth pack,v5_carry_forward,,v6_unified_source_of_truth_pack,3.0,3,4.0,71.0,permissive_or_noncopyleft_known,direct_incorporation_ok,The code license is MIT and direct use is allowed. This repo is best used as a bounded offline STT sidecar or native speech-input seam; no clean-room path is required by default.,"Use directly as a bounded native STT sidecar or library adapter; keep grammar, VAD, and model/runtime choices behind a speech-input seam.","Typically preserve notices, attribution, and license text where required; review selected model files or distributions separately from the code license.",Usually unnecessary unless you later choose to replace a narrow hot path or fully internalize the runtime.,high,model-artifact-review-recommended,yes,,,,,,,,,,,,,v6.3_final_source_of_truth,Merged v6.1 copyleft layer and v6.2 SRE layer; use v6.3 docs + workbook as canonical handoff.,,, 4.0,tao-yu/Alg-Trainer,https://github.com/tao-yu/Alg-Trainer,HyperTwist,4.0,156.0,189.0,A,cubing trainer / solver / timing,foundation engine,training donor,locked core candidate,integrate,direct,"Keep the core engine or major subsystem mostly intact; change wrappers, branding, storage/auth, and integration seams so it becomes a first-class part of the target stack. For this repo class, that usually means preserving cube-state, scramble, scheduling, or timer internals while adapting pedagogy, analytics, and UI.","Alg-Trainer (tao-yu/Alg-Trainer) | tao-yu/Alg-Trainer — MIT — Most powerful multi-set alg trainer (ZBLL, full custom sets, smartcube/virtual cube). Live: https://tao-yu.github.io/Alg-Trainer/. | tao-yu/Alg-Trainer — MIT — Multi-set alg t...","Integrate as a cubing / algorithm training subsystem for HyperTwist. Preserve the strongest existing pieces — scramble generation, algorithm database, recognition/training loop, timing/statistics, virtual cube, smartcube hooks, spaced repetition — and expose them behind a portfolio-stable interface. Wire first into poliva/cubedex, then into Lykos/cube_trainer for orchestration, visualization, or data exchange.","Consolidate under the Hyperspeedcube + cubing.js + qbr nucleus, not beside it as a separate silo. Normalize data contracts, auth/permissions, storage, and telemetry; then attach as a service, plugin, canvas layer, trainer, or analysis module. Descending combination order: poliva/cubedex, Lykos/cube_trainer, cubing/cubing.js.","Repurpose here means: turn it into a trainer engine, solver/timer backend, recognition drill module, or method-specific practice mode for HyperTwist.",Map module boundaries; Identify hidden reusable internals; Define adapter/API boundary to target anchors; Write extraction tests against upstream behavior; Extract cube-state model; Normalize trainer/case schema; Expose analytics and replay hooks,full subsystem extraction review,"Hidden value often sits in cube-state representation, scramble generation, weighted drill scheduling, recognition datasets, replay/timer internals, and case database schemas.",Inspect cube-state model; scramble generator; trainer weighting/scheduling; case database and metadata; replay/timer model; import/export of alg sets; smartcube or sensor adapters.,"Inspect package manifests, README/docs, src tree, examples, tests, CI workflows, config files, migrations/schemas, and hidden feature flags or experimental modules. Look for algorithm databases, spaced-repetition logic, scramble generation, timer/stat code, virtual cube components, smartcube adapters, and custom-trainer configuration support.","Audit tao-yu/Alg-Trainer as a cubing trainer / solver / timing candidate for HyperTwist. Do not stop at README-level features. Inspect: Inspect cube-state model; scramble generator; trainer weighting/scheduling; case database and metadata; replay/timer model; import/export of alg sets; smartcube or sensor adapters. Decide whether the best extraction path is direct and whether it belongs as foundation engine / training donor. Test the three merger paths in order: 1) poliva/cubedex [specialized training UX donor]; 2) Lykos/cube_trainer [sampling/analytics donor]; 3) cross-project transfer candidate [future merger]. Return hidden modules, reusable schemas, protocol layers, plugin hooks, render/state models, datasets/test fixtures, and any subsystem stronger than the visible product shell.",poliva/cubedex,specialized training UX donor,Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.,Lykos/cube_trainer,sampling/analytics donor,Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.,cross-project transfer candidate,future merger,Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.,project-local first,"Cross-project transfer is possible, but the value is clearest inside the assigned project until source audit exposes more reusable primitives.",do not exclude,Keep in active merge-set and force full source audit before any demotion.,high,single-source signal; clear taxonomy; active integration value; foundation-level fit,high,portfolio anchor or repeatedly surfaced core candidate; memo mentions: 5,"Licensing intentionally ignored as a decision filter in this canonical evaluation; assess only architecture, capability, donor value, and concept transfer.",,,,"Alg-Trainer (tao-yu/Alg-Trainer) | tao-yu/Alg-Trainer — MIT — Most powerful multi-set alg trainer (ZBLL, full custom sets, smartcube/virtual cube). Live: https://tao-yu.github.io/Alg-Trainer/. | tao-yu/Alg-Trainer — MIT — Multi-set alg trainer (extend to hyper commutators). | tao-yu/Alg-Trainer — MIT — Multi-set alg trainer.","tao-yu/Alg-Trainer is treated as integrate for HyperTwist because visible metadata points to the cubing / algorithm training layer. Surface signal: Alg-Trainer (tao-yu/Alg-Trainer) | tao-yu/Alg-Trainer — MIT — Most powerful multi-set alg trainer (ZBLL, full custom sets, smartcube/virtual cube). Live: https://tao-yu.github.io/Alg-Trainer/. | tao-yu/Alg-Trainer — MIT — Multi-set alg t... The likely value is substantial enough to preserve as a named subsystem rather than just mining isolated ideas.",memo,False,True,0.0,5.0,HT_training_stack,HT_training_stack_0001,cubing / algorithm training,Integrate primarily for HyperTwist. Its memo and bookmark signals place it in the cubing / algorithm training layer.,HyperTwist,cubing / algorithm training,integrate,moderate modification,medium,tao-yu/alg-trainer,1.0,Locked Parallel Foundation,2.0,Part of the irreducible core stack for HyperTwist; complements a primary foundation in the 'Training / timing layer' role and should be preserved in the committed build path.,Training / timing layer,Included,P0,"tao-yu/Alg-Trainer is placed in Locked Parallel Foundation for HyperTwist because it best serves the 'Training / timing layer' role; recommended action is 'integrate' with repurposing scope 'direct'. Confidence is high because this remains a metadata-level judgment until source audit confirms hidden modules, plugin points, adapters, or architectural strengths.",2.0,5.0,3.0,8548.0,111.0,,tao-yu/alg-trainer,HyperTwist,,,,,,,,,,Original global Phase G v4 retained,MIT,known_from_reference_material,uploaded_reference_docs,no,,,,Supplemental intake references are advisory only; v6 adjudication remains the source of truth.,Usually indirect,yes,v6 unified all-project source-of-truth pack,v5_carry_forward,,v6_unified_source_of_truth_pack,4.0,1,2.0,156.0,permissive_or_noncopyleft_known,direct_incorporation_ok,"This repo is aligned with a direct integration path for HyperTwist because it is either already implemented, strategically central, or donor-grade without a visible copyleft constraint in the current materials. Deep incorporation is sensible if the source audit confirms architectural cleanliness.","Direct embed, vendored module, package dependency, or tightly integrated adapter as the architecture requires.","Typically preserve notices, attribution, and license text where required; no special copyleft-driven disclosure posture is normally needed.",Usually unnecessary unless you later decide the existing implementation is too constraining architecturally.,high,strategic-or-implemented-component,yes,,,,,,,,,,,,,v6.3_final_source_of_truth,Merged v6.1 copyleft layer and v6.2 SRE layer; use v6.3 docs + workbook as canonical handoff.,implemented_live_permissive,landed_permissive_preserve,Phase 1R closed. Preserve as a landed first-party permissive lane; keep notices and attribution visible and widen only through ordinary owned enhancement work. 1749.0,rhasspy/piper,https://github.com/rhasspy/piper,multi-project,4.0,71.0,80.0,C,voice / multimodal I/O,subsystem donor,multimodal donor,donor bench,repurpose,moderate modification,"Retain the valuable internal engine, but expect to replace UI/product shell, adapt schemas/APIs, and refactor boundaries so it can plug into the target anchors cleanly. For this repo class, that usually means preserving streaming/audio pipeline logic while adapting commands, wake flows, and assistant integration.",rhasspy/piper – https://github.com/rhasspy/piper – MIT – Real-time TTS (recommended).,"Repurpose selected subsystems rather than the whole product. Mine the repo for lean local TTS runtime, HTTP wrapping, voice loading and download logic, streaming WAV and raw output, and ONNX/eSpeak integration; keep what materially shortens build time, but rebind data contracts, permissions, storage, and deployment to the target architecture. Best first pairing order: coqui-ai/TTS, ggml-org/whisper.cpp, SYSTRAN/faster-whisper.","Consolidate under the project-specific anchor stack, not beside it as a separate silo. Normalize data contracts, auth/permissions, storage, and telemetry; then attach as a service, plugin, canvas layer, trainer, or analysis module. Descending combination order: sentrux/sentrux, HactarCE/Hyperspeedcube, outline/outline.",Repurpose here means: turn it into a lean offline TTS sidecar or direct local narration donor.,Map module boundaries; Identify hidden reusable internals; Define adapter/API boundary to target anchors; Write extraction tests against upstream behavior; Isolate streaming/audio pipeline; Normalize command schema; Add local/offline fallback layer,deep source audit,"Hidden value often lives in streaming segmentation, VAD, device abstraction, latency mitigation, translation chains, and local/offline fallback paths.",Inspect C++ runtime core; voice loading and download path; streaming output; HTTP service boundary; speaker and phonemization config; selected voice artifact constraints.,"Inspect package manifests, README/docs, src tree, examples, tests, build configs, voice catalog files, and hidden runtime switches. Look for ONNX runtime integration, phonemization, lightweight service boundaries, audio streaming, voice acquisition, and deployment constraints.","Audit rhasspy/piper as a voice / multimodal I/O candidate for multi-project. Do not stop at README-level features. Inspect: C++ runtime core, voice loading and download path, streaming output, HTTP service boundary, speaker and phonemization config, and selected voice artifact constraints. Decide whether it should remain the lean direct local TTS sidecar candidate and what should stay behind a bounded local voice seam. Test the three merger paths in order: 1) project-local anchor [base + donor]; 2) shared portfolio utility [augmenter]; 3) cross-project transfer candidate [future merger]. Return hidden modules, reusable schemas, protocol layers, runtime boundaries, tests/fixtures, and any subsystem stronger than the visible shell.",project-local anchor,base + donor,Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.,shared portfolio utility,augmenter,Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.,cross-project transfer candidate,future merger,Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.,VectorShell | HyperTwist | ScriptoriumAI,"This capability is broadly portable across the portfolio because interaction, orchestration, and shell/UI patterns can be shared with thin domain adapters.","exclude from core, keep as donor","Do not let it consume roadmap as a full product shell; mine reusable engines, adapters, schemas, UX patterns, or datasets.",medium-low,single-source signal; clear taxonomy; mostly donor/reference role,medium,memo mentions: 1,"Licensing intentionally ignored as a decision filter in this canonical evaluation; assess only architecture, capability, donor value, and concept transfer.",,,,rhasspy/piper – https://github.com/rhasspy/piper – MIT – Real-time TTS (recommended).,"rhasspy/piper is treated as repurpose for multi-project because visible metadata points to the voice / speech / audio layer. Surface signal: rhasspy/piper – https://github.com/rhasspy/piper – MIT – Real-time TTS (recommended). The fit looks real, but more as a donor/augmenter than as a standalone foundation.",memo,False,True,0.0,1.0,MU_misc,MU_misc_0004,voice / speech / audio,"Repurpose selectively for multi-project. Its source-backed role is a lean local TTS sidecar candidate, not an exclusion-only adjunct.",future/adjacent use,voice / speech / audio,repurpose,moderate modification,medium,rhasspy/piper,1.0,Donor Bench,4.0,"Useful subsystem donor for multi-project, primarily in the 'Cross-project / future-adjacent' role; lean direct local TTS sidecar candidate.",Cross-project / future-adjacent,Included,P2,"rhasspy/piper is placed in Donor Bench for multi-project because it provides the leanest current local TTS runtime seam in the voice stack. Recommended action remains repurpose, but the real retained value is ONNX and eSpeak runtime simplicity, streaming output, and deployable local HTTP wrapping rather than broad voice-platform scope.",4.0,2.0,2.0,8565.0,8.0,,rhasspy/piper,multi-project,,,,,,,,,,Original global Phase G v4 retained,MIT code; voice artifacts reviewed separately,known_from_reference_material,uploaded_reference_docs,no,,,,Supplemental intake references are advisory only; v6 adjudication remains the source of truth.,Usually indirect,yes,v6 unified all-project source-of-truth pack,v5_carry_forward,,v6_unified_source_of_truth_pack,4.0,3,4.0,71.0,permissive_or_noncopyleft_known,direct_incorporation_ok,"The code license is MIT and direct use is allowed. The real review point is selected voice artifacts, not the runtime code; keep voice selection separate from code adoption.",Use directly as a bounded local TTS sidecar or simple HTTP service; keep selected voice artifacts under separate review.,"Typically preserve notices, attribution, and license text where required; review chosen voices or model cards separately from the code license.",Usually unnecessary unless you later replace the runtime for packaging or architecture reasons.,high,voice-artifact-review-required,yes,,,,,,,,,,,,,v6.3_final_source_of_truth,Merged v6.1 copyleft layer and v6.2 SRE layer; use v6.3 docs + workbook as canonical handoff.,,, 5.0,cubing/cubing.js,https://github.com/cubing/cubing.js,HyperTwist,5.0,152.0,185.0,A,interface / visualization / shell surface,foundation engine,visualization donor,locked strategic donor,integrate,direct,"Keep the core engine or major subsystem mostly intact; change wrappers, branding, storage/auth, and integration seams so it becomes a first-class part of the target stack. For this repo class, that usually means preserving scene/layout primitives and replacing surrounding data models or backend assumptions.",Other Notable ResourcesCubing.js library (for building your own tools): https://github.com/cubing/cubing.js – Open-source core used in many trainers above.,"Integrate as a ui / design / frontend subsystem for HyperTwist. Preserve the strongest existing pieces — component library, canvas/animation engine, interaction patterns, layout/state models, accessibility hooks, theming, editor widgets — and expose them behind a portfolio-stable interface. Wire first into HactarCE/Hyperspeedcube, then into kkoomen/qbr for orchestration, visualization, or data exchange.","Consolidate under the Hyperspeedcube + cubing.js + qbr nucleus, not beside it as a separate silo. Normalize data contracts, auth/permissions, storage, and telemetry; then attach as a service, plugin, canvas layer, trainer, or analysis module. Descending combination order: HactarCE/Hyperspeedcube, kkoomen/qbr.","Repurpose here means: turn it into a frontend interaction donor, canvas/editor pattern library, or polished shell layer on top of existing anchors.",Map module boundaries; Identify hidden reusable internals; Define adapter/API boundary to target anchors; Write extraction tests against upstream behavior; Extract layout/scene primitives; Map import/export schema; Detach UI shell from backend assumptions,full subsystem extraction review,"Hidden value often sits in scene graph/canvas model, component primitives, import/export schema, gesture/keyboard interactions, and plugin-ready layout abstractions.",Inspect scene graph/canvas data model; layout primitives; component library; keyboard/gesture interactions; import/export schema; theming; plugin or extension hooks.,"Inspect package manifests, README/docs, src tree, examples, tests, CI workflows, config files, migrations/schemas, and hidden feature flags or experimental modules. Look for reusable canvas/editor components, design tokens, state models, keyboard shortcuts, drag/drop, accessibility, virtualization, and polished interaction patterns.","Audit cubing/cubing.js as a interface / visualization / shell surface candidate for HyperTwist. Do not stop at README-level features. Inspect: Inspect scene graph/canvas data model; layout primitives; component library; keyboard/gesture interactions; import/export schema; theming; plugin or extension hooks. Decide whether the best extraction path is direct and whether it belongs as foundation engine / visualization donor. Test the three merger paths in order: 1) project-local anchor [base + donor]; 2) shared portfolio utility [augmenter]; 3) cross-project transfer candidate [future merger]. Return hidden modules, reusable schemas, protocol layers, plugin hooks, render/state models, datasets/test fixtures, and any subsystem stronger than the visible product shell.",project-local anchor,base + donor,Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.,shared portfolio utility,augmenter,Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.,cross-project transfer candidate,future merger,Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.,VectorShell | HyperTwist | ScriptoriumAI,"This capability is broadly portable across the portfolio because interaction, orchestration, and shell/UI patterns can be shared with thin domain adapters.",do not exclude,Keep in active merge-set and force full source audit before any demotion.,medium-high,single-source signal; clear taxonomy; active integration value; foundation-level fit,high,portfolio anchor or repeatedly surfaced core candidate; memo mentions: 1,"Licensing intentionally ignored as a decision filter in this canonical evaluation; assess only architecture, capability, donor value, and concept transfer.",,,,Other Notable ResourcesCubing.js library (for building your own tools): https://github.com/cubing/cubing.js – Open-source core used in many trainers above.,cubing/cubing.js is treated as integrate for HyperTwist because visible metadata points to the ui / design / frontend layer. Surface signal: Other Notable ResourcesCubing.js library (for building your own tools): https://github.com/cubing/cubing.js – Open-source core used in many trainers above. The likely value is substantial enough to preserve as a named subsystem rather than just mining isolated ideas.,memo,False,True,0.0,1.0,HT_cube_semantics,HT_cube_semantics_0001,cubing / algorithm training,Integrate primarily for HyperTwist. Its memo and bookmark signals place it in the cubing / algorithm training layer.,HyperTwist,cubing / algorithm training,integrate,moderate modification,medium,cubing/cubing.js,1.0,Locked Strategic Donor,1.0,"Dual MPL/GPL classic-cubing anchor with strong donor value, but not a carefree private-source fork candidate.",Boundary-sensitive classic-cubing semantics and rendering donor,Included,P1,"Keep as the canonical classic-cubing semantics and interop donor, but only through its practical MPL path or bounded adapter/package consumption.",2.0,4.0,3.0,11771.0,112.0,,cubing/cubing.js,HyperTwist,,,,,,,,,,Original global Phase G v4 retained,MPL-2.0 OR GPL-3.0-or-later,known_from_reference_material,uploaded_reference_docs,yes,hypertwist_and_scriptoriumai,HyperTwist,HyperTwist & ScriptoriumAI.txt,Supplemental intake references are advisory only; v6 adjudication remains the source of truth.,Usually indirect,yes,v6 unified all-project source-of-truth pack,v5_carry_forward,Existing v5 row reaffirmed or widened by v6 supplemental intake.,v6_unified_source_of_truth_pack,5.0,1,1.0,152.0,mixed_or_boundary_sensitive_known,bounded_sidecar_or_selective_reimplementation,"The repo is dual-licensed MPL-2.0 OR GPL-3.0-or-later. HyperTwist can consume it as a package or bounded adapter under the MPL side, but should avoid a carefree deep private source fork of upstream files.",Prefer package/dependency consumption or a bounded adapter seam under the MPL side; avoid deep private forks of upstream source files.,Preserve MPL notices and publish modifications to MPL-covered files when distribution obligations apply; avoid assuming the GPL side is the intended operational path.,Only if you later need to replace narrow upstream-covered seams with first-party equivalents or avoid carrying MPL-governed source modifications.,high,dual-license-boundary-review,yes,,,,,,,,,,,,,v6.3_final_source_of_truth,Assigned to HT_cube_semantics during cluster normalization on 2026-04-25.,selected_not_live_boundary_sensitive,phase0r_boundary_sensitive_eval_then_adapter_or_sidecar,Phase 1R closed. Retain as a Phase 4R boundary-sensitive candidate through MPL-side dependency or adapter use; avoid deep private forks unless publication obligations are acceptable. -6.0,cahidenes/rubiks-cube-solver,https://github.com/cahidenes/rubiks-cube-solver,HyperTwist,6.0,148.0,174.0,A,vision / perception / AR,foundation engine,vision donor,locked strategic donor,integrate,direct,"Keep the core engine or major subsystem mostly intact; change wrappers, branding, storage/auth, and integration seams so it becomes a first-class part of the target stack. For this repo class, that usually means preserving calibration/detection/state-reconstruction logic while replacing camera UX and integration surfaces.",cahidenes/rubiks-cube-solver — MIT — OpenCV cube detection + Kociemba solver. | cahidenes/rubiks-cube-solver — MIT — OpenCV + solver. | Yes — we already have several strong open-source visual models for cube recognition from earlier in o...,"Integrate as a computer vision / AR subsystem for HyperTwist. Preserve the strongest existing pieces — camera ingest, calibration, segmentation/detection, pose or facelet extraction, state normalization, solver bridge, replay overlay, AR anchors — and expose them behind a portfolio-stable interface. Wire first into kkoomen/qbr, then into vivaansinghvi07/rubix-cube-solver for orchestration, visualization, or data exchange.","Consolidate under the Hyperspeedcube + cubing.js + qbr nucleus, not beside it as a separate silo. Normalize data contracts, auth/permissions, storage, and telemetry; then attach as a service, plugin, canvas layer, trainer, or analysis module. Descending combination order: kkoomen/qbr, vivaansinghvi07/rubix-cube-solver, cubing/cubing.js.","Repurpose here means: turn it into a perception microservice, cube-state API, replay generator, or AR overlay donor for HyperTwist.",Map module boundaries; Identify hidden reusable internals; Define adapter/API boundary to target anchors; Write extraction tests against upstream behavior; Benchmark calibration pipeline; Extract state reconstruction; Wrap with camera/AR adapter,full subsystem extraction review,"Hidden value often sits in calibration, preprocessing, stabilization, object/state reconstruction, replay artifacts, and camera-to-domain state pipelines that are not obvious from demos.",Inspect preprocessing/calibration; tracking stabilization; state reconstruction; replay/event model; camera abstraction; fallback heuristics; testing assets/videos; performance shortcuts.,"Inspect package manifests, README/docs, src tree, examples, tests, CI workflows, config files, migrations/schemas, and hidden feature flags or experimental modules. Look for calibration routines, detection heuristics/models, color/state normalization, replay serialization, solver bridges, camera abstraction layers, and debug visualizations.","Audit cahidenes/rubiks-cube-solver as a vision / perception / AR candidate for HyperTwist. Do not stop at README-level features. Inspect: Inspect preprocessing/calibration; tracking stabilization; state reconstruction; replay/event model; camera abstraction; fallback heuristics; testing assets/videos; performance shortcuts. Decide whether the best extraction path is direct and whether it belongs as foundation engine / vision donor. Test the three merger paths in order: 1) kkoomen/qbr [foundation + perception donor]; 2) vivaansinghvi07/rubix-cube-solver [perception + replay donor]; 3) cubing/cubing.js [state/render backend]. Return hidden modules, reusable schemas, protocol layers, plugin hooks, render/state models, datasets/test fixtures, and any subsystem stronger than the visible product shell.",kkoomen/qbr,foundation + perception donor,"Use this repo against the partner as an augmenting layer; preserve the partner as the likely base and mine this repo for capabilities that improve breadth, UX, or specialization.",vivaansinghvi07/rubix-cube-solver,perception + replay donor,Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.,cubing/cubing.js,state/render backend,Use the partner for canonical state or rendering abstractions and merge this repo's specialized logic on top.,VectorShell | ScriptoriumAI,VectorShell can borrow spatial/rendering and perception primitives; ScriptoriumAI can borrow tutorial/educational visualization patterns rather than the full engine.,do not exclude,Keep in active merge-set and force full source audit before any demotion.,high,single-source signal; clear taxonomy; active integration value; foundation-level fit,high,memo mentions: 5,"Licensing intentionally ignored as a decision filter in this canonical evaluation; assess only architecture, capability, donor value, and concept transfer.",,,,"cahidenes/rubiks-cube-solver — MIT — OpenCV cube detection + Kociemba solver. | cahidenes/rubiks-cube-solver — MIT — OpenCV + solver. | Yes — we already have several strong open-source visual models for cube recognition from earlier in our conversation. I went back through the entire history and pulled the exact ones we discussed (qbr, vivaansinghvi07/rubix-cube-solver, tentone/rubix-solver, cahidenes/rubiks-cube-solver). These are still the high","cahidenes/rubiks-cube-solver is treated as integrate for HyperTwist because the current dossier keeps it active as a strategic donor for constrained capture flow, stickerless-friendly grouping, face-placement logic, and solver-handoff normalization behind the two vision anchors.",memo,False,True,0.0,5.0,HT_cube_vision,HT_cube_vision_0003,computer vision / AR,Integrate primarily for HyperTwist. Its memo and bookmark signals place it in the computer vision / AR layer.,HyperTwist,computer vision / AR,integrate,heavy modification,medium,cahidenes/rubiks-cube-solver,1.0,Locked Strategic Donor,3.0,"High-value active vision donor for recognition heuristics, solver-bridge normalization, and validation behind qbr and vivaansinghvi07; not a foundation anchor.",Active recognition-heuristics and validation donor,Included,P1,"cahidenes/rubiks-cube-solver is placed in Locked Strategic Donor for HyperTwist because it best serves the 'Active recognition-heuristics and validation donor' role; recommended action is 'integrate' with repurposing scope 'direct'. Confidence is high because this remains a metadata-level judgment until source audit confirms hidden modules, plugin points, adapters, or architectural strengths.",2.0,5.0,3.0,11849.0,113.0,,cahidenes/rubiks-cube-solver,HyperTwist,,,,,,,,,,Original global Phase G v4 retained,MIT,known_from_reference_material,uploaded_reference_docs,no,,,,Supplemental intake references are advisory only; v6 adjudication remains the source of truth.,Usually indirect,yes,v6 unified all-project source-of-truth pack,v5_carry_forward,,v6_unified_source_of_truth_pack,6.0,2,3.0,148.0,permissive_or_noncopyleft_known,direct_incorporation_ok,"This repo is aligned with a direct integration path for HyperTwist because it is either already implemented, strategically central, or donor-grade without a visible copyleft constraint in the current materials. Deep incorporation is sensible if the source audit confirms architectural cleanliness.","Direct embed, vendored module, package dependency, or tightly integrated adapter as the architecture requires.","Typically preserve notices, attribution, and license text where required; no special copyleft-driven disclosure posture is normally needed.",Usually unnecessary unless you later decide the existing implementation is too constraining architecturally.,high,strategic-or-implemented-component,yes,,,,,,,,,,,,,v6.3_final_source_of_truth,Normalized legacy candidate-core wording to dossier-backed strategic-donor posture on 2026-04-25.,selected_not_live_permissive_candidate,phase0r_permissive_eval_then_implement,"Phase 1R closed. Retain as a Phase 3R permissive implementation candidate; implement only from its packet authority and the retained-set contract, not by reopening Phase 0R." -7.0,tentone/rubix-solver,https://github.com/tentone/rubix-solver,HyperTwist,7.0,148.0,174.0,A,vision / perception / AR,foundation engine,vision donor,locked strategic donor,integrate,direct,"Keep the core engine or major subsystem mostly intact; change wrappers, branding, storage/auth, and integration seams so it becomes a first-class part of the target stack. For this repo class, that usually means preserving calibration/detection/state-reconstruction logic while replacing camera UX and integration surfaces.","tentone/rubix-solver — MIT — OpenCV cube detection. | Yes — 100% possible to consolidate everything into one no-compromises, enterprise-grade platform. You're not half-arsing it, and neither am I. Modern vision models (and even classical...","Integrate as a computer vision / AR subsystem for HyperTwist. Preserve the strongest existing pieces — camera ingest, calibration, segmentation/detection, pose or facelet extraction, state normalization, solver bridge, replay overlay, AR anchors — and expose them behind a portfolio-stable interface. Wire first into kkoomen/qbr, then into vivaansinghvi07/rubix-cube-solver for orchestration, visualization, or data exchange.","Consolidate under the Hyperspeedcube + cubing.js + qbr nucleus, not beside it as a separate silo. Normalize data contracts, auth/permissions, storage, and telemetry; then attach as a service, plugin, canvas layer, trainer, or analysis module. Descending combination order: kkoomen/qbr, vivaansinghvi07/rubix-cube-solver, cubing/cubing.js.","Repurpose here means: turn it into a perception microservice, cube-state API, replay generator, or AR overlay donor for HyperTwist.",Map module boundaries; Identify hidden reusable internals; Define adapter/API boundary to target anchors; Write extraction tests against upstream behavior; Benchmark calibration pipeline; Extract state reconstruction; Wrap with camera/AR adapter,full subsystem extraction review,"Hidden value often sits in calibration, preprocessing, stabilization, object/state reconstruction, replay artifacts, and camera-to-domain state pipelines that are not obvious from demos.",Inspect preprocessing/calibration; tracking stabilization; state reconstruction; replay/event model; camera abstraction; fallback heuristics; testing assets/videos; performance shortcuts.,"Inspect package manifests, README/docs, src tree, examples, tests, CI workflows, config files, migrations/schemas, and hidden feature flags or experimental modules. Look for calibration routines, detection heuristics/models, color/state normalization, replay serialization, solver bridges, camera abstraction layers, and debug visualizations.","Audit tentone/rubix-solver as a vision / perception / AR candidate for HyperTwist. Do not stop at README-level features. Inspect: Inspect preprocessing/calibration; tracking stabilization; state reconstruction; replay/event model; camera abstraction; fallback heuristics; testing assets/videos; performance shortcuts. Decide whether the best extraction path is direct and whether it belongs as foundation engine / vision donor. Test the three merger paths in order: 1) kkoomen/qbr [foundation + perception donor]; 2) vivaansinghvi07/rubix-cube-solver [perception + replay donor]; 3) cubing/cubing.js [state/render backend]. Return hidden modules, reusable schemas, protocol layers, plugin hooks, render/state models, datasets/test fixtures, and any subsystem stronger than the visible product shell.",kkoomen/qbr,foundation + perception donor,"Use this repo against the partner as an augmenting layer; preserve the partner as the likely base and mine this repo for capabilities that improve breadth, UX, or specialization.",vivaansinghvi07/rubix-cube-solver,perception + replay donor,Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.,cubing/cubing.js,state/render backend,Use the partner for canonical state or rendering abstractions and merge this repo's specialized logic on top.,VectorShell | ScriptoriumAI,VectorShell can borrow spatial/rendering and perception primitives; ScriptoriumAI can borrow tutorial/educational visualization patterns rather than the full engine.,do not exclude,Keep in active merge-set and force full source audit before any demotion.,high,single-source signal; clear taxonomy; active integration value; foundation-level fit,high,memo mentions: 7,"Licensing intentionally ignored as a decision filter in this canonical evaluation; assess only architecture, capability, donor value, and concept transfer.",,,,"tentone/rubix-solver — MIT — OpenCV cube detection. | Yes — 100% possible to consolidate everything into one no-compromises, enterprise-grade platform. You're not half-arsing it, and neither am I. Modern vision models (and even classical OpenCV pipelines refined over the last decade) are more than accurate enough in 2026 for reliable small-square/facelet color recognition on a standard 3x3 (or larger) Rubik's Cube under normal lighting. Productio","tentone/rubix-solver is treated as integrate for HyperTwist because the current dossier keeps it active as a strategic donor for compact C++ and OpenCV detection heuristics and comparison-bench value, not for its brute-force solver shell.",memo,False,True,0.0,7.0,HT_cube_vision,HT_cube_vision_0004,computer vision / AR,Integrate primarily for HyperTwist. Its memo and bookmark signals place it in the computer vision / AR layer.,HyperTwist,computer vision / AR,integrate,heavy modification,medium,tentone/rubix-solver,1.0,Locked Strategic Donor,3.0,High-value active native-CV donor for detection heuristics and comparison benchmarking behind the vision anchors; not a foundation anchor.,Active native-CV donor and comparison bench,Included,P1,"tentone/rubix-solver is placed in Locked Strategic Donor for HyperTwist because it best serves the 'Active native-CV donor and comparison bench' role; recommended action is 'integrate' with repurposing scope 'direct'. Confidence is high because this remains a metadata-level judgment until source audit confirms hidden modules, plugin points, adapters, or architectural strengths.",2.0,5.0,3.0,11852.0,114.0,,tentone/rubix-solver,HyperTwist,,,,,,,,,,Original global Phase G v4 retained,MIT,known_from_reference_material,uploaded_reference_docs,no,,,,Supplemental intake references are advisory only; v6 adjudication remains the source of truth.,Usually indirect,yes,v6 unified all-project source-of-truth pack,v5_carry_forward,,v6_unified_source_of_truth_pack,7.0,2,3.0,148.0,permissive_or_noncopyleft_known,direct_incorporation_ok,"This repo is aligned with a direct integration path for HyperTwist because it is either already implemented, strategically central, or donor-grade without a visible copyleft constraint in the current materials. Deep incorporation is sensible if the source audit confirms architectural cleanliness.","Direct embed, vendored module, package dependency, or tightly integrated adapter as the architecture requires.","Typically preserve notices, attribution, and license text where required; no special copyleft-driven disclosure posture is normally needed.",Usually unnecessary unless you later decide the existing implementation is too constraining architecturally.,high,strategic-or-implemented-component,yes,,,,,,,,,,,,,v6.3_final_source_of_truth,Normalized legacy candidate-core wording to dossier-backed strategic-donor posture on 2026-04-25.,selected_not_live_permissive_candidate,phase0r_permissive_eval_then_implement,"Phase 1R closed. Retain as a Phase 3R permissive implementation candidate; implement only from its packet authority and the retained-set contract, not by reopening Phase 0R." +6.0,cahidenes/rubiks-cube-solver,https://github.com/cahidenes/rubiks-cube-solver,HyperTwist,6.0,148.0,174.0,A,vision / perception / AR,foundation engine,vision donor,locked strategic donor,integrate,direct,"Keep the core engine or major subsystem mostly intact; change wrappers, branding, storage/auth, and integration seams so it becomes a first-class part of the target stack. For this repo class, that usually means preserving calibration/detection/state-reconstruction logic while replacing camera UX and integration surfaces.",cahidenes/rubiks-cube-solver — MIT — OpenCV cube detection + Kociemba solver. | cahidenes/rubiks-cube-solver — MIT — OpenCV + solver. | Yes — we already have several strong open-source visual models for cube recognition from earlier in o...,"Integrate as a computer vision / AR subsystem for HyperTwist. Preserve the strongest existing pieces — camera ingest, calibration, segmentation/detection, pose or facelet extraction, state normalization, solver bridge, replay overlay, AR anchors — and expose them behind a portfolio-stable interface. Wire first into kkoomen/qbr, then into vivaansinghvi07/rubix-cube-solver for orchestration, visualization, or data exchange.","Consolidate under the Hyperspeedcube + cubing.js + qbr nucleus, not beside it as a separate silo. Normalize data contracts, auth/permissions, storage, and telemetry; then attach as a service, plugin, canvas layer, trainer, or analysis module. Descending combination order: kkoomen/qbr, vivaansinghvi07/rubix-cube-solver, cubing/cubing.js.","Repurpose here means: turn it into a perception microservice, cube-state API, replay generator, or AR overlay donor for HyperTwist.",Map module boundaries; Identify hidden reusable internals; Define adapter/API boundary to target anchors; Write extraction tests against upstream behavior; Benchmark calibration pipeline; Extract state reconstruction; Wrap with camera/AR adapter,full subsystem extraction review,"Hidden value often sits in calibration, preprocessing, stabilization, object/state reconstruction, replay artifacts, and camera-to-domain state pipelines that are not obvious from demos.",Inspect preprocessing/calibration; tracking stabilization; state reconstruction; replay/event model; camera abstraction; fallback heuristics; testing assets/videos; performance shortcuts.,"Inspect package manifests, README/docs, src tree, examples, tests, CI workflows, config files, migrations/schemas, and hidden feature flags or experimental modules. Look for calibration routines, detection heuristics/models, color/state normalization, replay serialization, solver bridges, camera abstraction layers, and debug visualizations.","Audit cahidenes/rubiks-cube-solver as a vision / perception / AR candidate for HyperTwist. Do not stop at README-level features. Inspect: Inspect preprocessing/calibration; tracking stabilization; state reconstruction; replay/event model; camera abstraction; fallback heuristics; testing assets/videos; performance shortcuts. Decide whether the best extraction path is direct and whether it belongs as foundation engine / vision donor. Test the three merger paths in order: 1) kkoomen/qbr [foundation + perception donor]; 2) vivaansinghvi07/rubix-cube-solver [perception + replay donor]; 3) cubing/cubing.js [state/render backend]. Return hidden modules, reusable schemas, protocol layers, plugin hooks, render/state models, datasets/test fixtures, and any subsystem stronger than the visible product shell.",kkoomen/qbr,foundation + perception donor,"Use this repo against the partner as an augmenting layer; preserve the partner as the likely base and mine this repo for capabilities that improve breadth, UX, or specialization.",vivaansinghvi07/rubix-cube-solver,perception + replay donor,Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.,cubing/cubing.js,state/render backend,Use the partner for canonical state or rendering abstractions and merge this repo's specialized logic on top.,VectorShell | ScriptoriumAI,VectorShell can borrow spatial/rendering and perception primitives; ScriptoriumAI can borrow tutorial/educational visualization patterns rather than the full engine.,do not exclude,Keep in active merge-set and force full source audit before any demotion.,high,single-source signal; clear taxonomy; active integration value; foundation-level fit,high,memo mentions: 5,"Licensing intentionally ignored as a decision filter in this canonical evaluation; assess only architecture, capability, donor value, and concept transfer.",,,,"cahidenes/rubiks-cube-solver — MIT — OpenCV cube detection + Kociemba solver. | cahidenes/rubiks-cube-solver — MIT — OpenCV + solver. | Yes — we already have several strong open-source visual models for cube recognition from earlier in our conversation. I went back through the entire history and pulled the exact ones we discussed (qbr, vivaansinghvi07/rubix-cube-solver, tentone/rubix-solver, cahidenes/rubiks-cube-solver). These are still the high","cahidenes/rubiks-cube-solver is treated as integrate for HyperTwist because the current dossier keeps it active as a strategic donor for constrained capture flow, stickerless-friendly grouping, face-placement logic, and solver-handoff normalization behind the two vision anchors.",memo,False,True,0.0,5.0,HT_cube_vision,HT_cube_vision_0003,computer vision / AR,Integrate primarily for HyperTwist. Its memo and bookmark signals place it in the computer vision / AR layer.,HyperTwist,computer vision / AR,integrate,heavy modification,medium,cahidenes/rubiks-cube-solver,1.0,Locked Strategic Donor,3.0,"High-value active vision donor for recognition heuristics, solver-bridge normalization, and validation behind qbr and vivaansinghvi07; not a foundation anchor.",Active recognition-heuristics and validation donor,Included,P1,"cahidenes/rubiks-cube-solver is placed in Locked Strategic Donor for HyperTwist because it best serves the 'Active recognition-heuristics and validation donor' role; recommended action is 'integrate' with repurposing scope 'direct'. Confidence is high because this remains a metadata-level judgment until source audit confirms hidden modules, plugin points, adapters, or architectural strengths.",2.0,5.0,3.0,11849.0,113.0,,cahidenes/rubiks-cube-solver,HyperTwist,,,,,,,,,,Original global Phase G v4 retained,MIT,known_from_reference_material,uploaded_reference_docs,no,,,,Supplemental intake references are advisory only; v6 adjudication remains the source of truth.,Usually indirect,yes,v6 unified all-project source-of-truth pack,v5_carry_forward,,v6_unified_source_of_truth_pack,6.0,2,3.0,148.0,permissive_or_noncopyleft_known,direct_incorporation_ok,"This repo is aligned with a direct integration path for HyperTwist because it is either already implemented, strategically central, or donor-grade without a visible copyleft constraint in the current materials. Deep incorporation is sensible if the source audit confirms architectural cleanliness.","Direct embed, vendored module, package dependency, or tightly integrated adapter as the architecture requires.","Typically preserve notices, attribution, and license text where required; no special copyleft-driven disclosure posture is normally needed.",Usually unnecessary unless you later decide the existing implementation is too constraining architecturally.,high,strategic-or-implemented-component,yes,,,,,,,,,,,,,v6.3_final_source_of_truth,Normalized legacy candidate-core wording to dossier-backed strategic-donor posture on 2026-04-25.,implemented_live_permissive,landed_permissive_preserve,"Phase 3R-E closed. Preserve as the landed first-party embodied companion, narration, lip-sync, gesture, subtitle, and avatar-embed lane; start future widening from the live-lane audit, then the 3R-E implementation packet, then REPO_LICENSE_TRACKING.md." +7.0,tentone/rubix-solver,https://github.com/tentone/rubix-solver,HyperTwist,7.0,148.0,174.0,A,vision / perception / AR,foundation engine,vision donor,locked strategic donor,integrate,direct,"Keep the core engine or major subsystem mostly intact; change wrappers, branding, storage/auth, and integration seams so it becomes a first-class part of the target stack. For this repo class, that usually means preserving calibration/detection/state-reconstruction logic while replacing camera UX and integration surfaces.","tentone/rubix-solver — MIT — OpenCV cube detection. | Yes — 100% possible to consolidate everything into one no-compromises, enterprise-grade platform. You're not half-arsing it, and neither am I. Modern vision models (and even classical...","Integrate as a computer vision / AR subsystem for HyperTwist. Preserve the strongest existing pieces — camera ingest, calibration, segmentation/detection, pose or facelet extraction, state normalization, solver bridge, replay overlay, AR anchors — and expose them behind a portfolio-stable interface. Wire first into kkoomen/qbr, then into vivaansinghvi07/rubix-cube-solver for orchestration, visualization, or data exchange.","Consolidate under the Hyperspeedcube + cubing.js + qbr nucleus, not beside it as a separate silo. Normalize data contracts, auth/permissions, storage, and telemetry; then attach as a service, plugin, canvas layer, trainer, or analysis module. Descending combination order: kkoomen/qbr, vivaansinghvi07/rubix-cube-solver, cubing/cubing.js.","Repurpose here means: turn it into a perception microservice, cube-state API, replay generator, or AR overlay donor for HyperTwist.",Map module boundaries; Identify hidden reusable internals; Define adapter/API boundary to target anchors; Write extraction tests against upstream behavior; Benchmark calibration pipeline; Extract state reconstruction; Wrap with camera/AR adapter,full subsystem extraction review,"Hidden value often sits in calibration, preprocessing, stabilization, object/state reconstruction, replay artifacts, and camera-to-domain state pipelines that are not obvious from demos.",Inspect preprocessing/calibration; tracking stabilization; state reconstruction; replay/event model; camera abstraction; fallback heuristics; testing assets/videos; performance shortcuts.,"Inspect package manifests, README/docs, src tree, examples, tests, CI workflows, config files, migrations/schemas, and hidden feature flags or experimental modules. Look for calibration routines, detection heuristics/models, color/state normalization, replay serialization, solver bridges, camera abstraction layers, and debug visualizations.","Audit tentone/rubix-solver as a vision / perception / AR candidate for HyperTwist. Do not stop at README-level features. Inspect: Inspect preprocessing/calibration; tracking stabilization; state reconstruction; replay/event model; camera abstraction; fallback heuristics; testing assets/videos; performance shortcuts. Decide whether the best extraction path is direct and whether it belongs as foundation engine / vision donor. Test the three merger paths in order: 1) kkoomen/qbr [foundation + perception donor]; 2) vivaansinghvi07/rubix-cube-solver [perception + replay donor]; 3) cubing/cubing.js [state/render backend]. Return hidden modules, reusable schemas, protocol layers, plugin hooks, render/state models, datasets/test fixtures, and any subsystem stronger than the visible product shell.",kkoomen/qbr,foundation + perception donor,"Use this repo against the partner as an augmenting layer; preserve the partner as the likely base and mine this repo for capabilities that improve breadth, UX, or specialization.",vivaansinghvi07/rubix-cube-solver,perception + replay donor,Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.,cubing/cubing.js,state/render backend,Use the partner for canonical state or rendering abstractions and merge this repo's specialized logic on top.,VectorShell | ScriptoriumAI,VectorShell can borrow spatial/rendering and perception primitives; ScriptoriumAI can borrow tutorial/educational visualization patterns rather than the full engine.,do not exclude,Keep in active merge-set and force full source audit before any demotion.,high,single-source signal; clear taxonomy; active integration value; foundation-level fit,high,memo mentions: 7,"Licensing intentionally ignored as a decision filter in this canonical evaluation; assess only architecture, capability, donor value, and concept transfer.",,,,"tentone/rubix-solver — MIT — OpenCV cube detection. | Yes — 100% possible to consolidate everything into one no-compromises, enterprise-grade platform. You're not half-arsing it, and neither am I. Modern vision models (and even classical OpenCV pipelines refined over the last decade) are more than accurate enough in 2026 for reliable small-square/facelet color recognition on a standard 3x3 (or larger) Rubik's Cube under normal lighting. Productio","tentone/rubix-solver is treated as integrate for HyperTwist because the current dossier keeps it active as a strategic donor for compact C++ and OpenCV detection heuristics and comparison-bench value, not for its brute-force solver shell.",memo,False,True,0.0,7.0,HT_cube_vision,HT_cube_vision_0004,computer vision / AR,Integrate primarily for HyperTwist. Its memo and bookmark signals place it in the computer vision / AR layer.,HyperTwist,computer vision / AR,integrate,heavy modification,medium,tentone/rubix-solver,1.0,Locked Strategic Donor,3.0,High-value active native-CV donor for detection heuristics and comparison benchmarking behind the vision anchors; not a foundation anchor.,Active native-CV donor and comparison bench,Included,P1,"tentone/rubix-solver is placed in Locked Strategic Donor for HyperTwist because it best serves the 'Active native-CV donor and comparison bench' role; recommended action is 'integrate' with repurposing scope 'direct'. Confidence is high because this remains a metadata-level judgment until source audit confirms hidden modules, plugin points, adapters, or architectural strengths.",2.0,5.0,3.0,11852.0,114.0,,tentone/rubix-solver,HyperTwist,,,,,,,,,,Original global Phase G v4 retained,MIT,known_from_reference_material,uploaded_reference_docs,no,,,,Supplemental intake references are advisory only; v6 adjudication remains the source of truth.,Usually indirect,yes,v6 unified all-project source-of-truth pack,v5_carry_forward,,v6_unified_source_of_truth_pack,7.0,2,3.0,148.0,permissive_or_noncopyleft_known,direct_incorporation_ok,"This repo is aligned with a direct integration path for HyperTwist because it is either already implemented, strategically central, or donor-grade without a visible copyleft constraint in the current materials. Deep incorporation is sensible if the source audit confirms architectural cleanliness.","Direct embed, vendored module, package dependency, or tightly integrated adapter as the architecture requires.","Typically preserve notices, attribution, and license text where required; no special copyleft-driven disclosure posture is normally needed.",Usually unnecessary unless you later decide the existing implementation is too constraining architecturally.,high,strategic-or-implemented-component,yes,,,,,,,,,,,,,v6.3_final_source_of_truth,Normalized legacy candidate-core wording to dossier-backed strategic-donor posture on 2026-04-25.,implemented_live_permissive,landed_permissive_preserve,"Phase 3R-E closed. Preserve as the landed first-party embodied companion, narration, lip-sync, gesture, subtitle, and avatar-embed lane; start future widening from the live-lane audit, then the 3R-E implementation packet, then REPO_LICENSE_TRACKING.md." 8.0,Lykos/cube_trainer,https://github.com/Lykos/cube_trainer,HyperTwist,8.0,145.0,171.0,A,cubing trainer / solver / timing,foundation engine,training donor,locked strategic donor,integrate,direct,"Keep the core engine or major subsystem mostly intact; change wrappers, branding, storage/auth, and integration seams so it becomes a first-class part of the target stack. For this repo class, that usually means preserving cube-state, scramble, scheduling, or timer internals while adapting pedagogy, analytics, and UI.",Lykos/cube_trainer — MIT — Smart-sampled training. | CubeTrainer (Lykos/cube_trainer) | Lykos/cube_trainer — MIT — Smart-sampled alg/BLD trainer. Live: https://www.cubetrainer.org.,"Integrate as a cubing / algorithm training subsystem for HyperTwist. Preserve the strongest existing pieces — scramble generation, algorithm database, recognition/training loop, timing/statistics, virtual cube, smartcube hooks, spaced repetition — and expose them behind a portfolio-stable interface. Wire first into tao-yu/Alg-Trainer, then into poliva/cubedex for orchestration, visualization, or data exchange.","Consolidate under the Hyperspeedcube + cubing.js + qbr nucleus, not beside it as a separate silo. Normalize data contracts, auth/permissions, storage, and telemetry; then attach as a service, plugin, canvas layer, trainer, or analysis module. Descending combination order: tao-yu/Alg-Trainer, poliva/cubedex, cubing/cubing.js.","Repurpose here means: turn it into a trainer engine, solver/timer backend, recognition drill module, or method-specific practice mode for HyperTwist.",Map module boundaries; Identify hidden reusable internals; Define adapter/API boundary to target anchors; Write extraction tests against upstream behavior; Extract cube-state model; Normalize trainer/case schema; Expose analytics and replay hooks,full subsystem extraction review,"Hidden value often sits in cube-state representation, scramble generation, weighted drill scheduling, recognition datasets, replay/timer internals, and case database schemas.",Inspect cube-state model; scramble generator; trainer weighting/scheduling; case database and metadata; replay/timer model; import/export of alg sets; smartcube or sensor adapters.,"Inspect package manifests, README/docs, src tree, examples, tests, CI workflows, config files, migrations/schemas, and hidden feature flags or experimental modules. Look for algorithm databases, spaced-repetition logic, scramble generation, timer/stat code, virtual cube components, smartcube adapters, and custom-trainer configuration support.","Audit Lykos/cube_trainer as a cubing trainer / solver / timing candidate for HyperTwist. Do not stop at README-level features. Inspect: Inspect cube-state model; scramble generator; trainer weighting/scheduling; case database and metadata; replay/timer model; import/export of alg sets; smartcube or sensor adapters. Decide whether the best extraction path is direct and whether it belongs as foundation engine / training donor. Test the three merger paths in order: 1) tao-yu/Alg-Trainer [base + donor swarm]; 2) poliva/cubedex [specialized training UX donor]; 3) cross-project transfer candidate [future merger]. Return hidden modules, reusable schemas, protocol layers, plugin hooks, render/state models, datasets/test fixtures, and any subsystem stronger than the visible product shell.",tao-yu/Alg-Trainer,base + donor swarm,Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.,poliva/cubedex,specialized training UX donor,Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.,cross-project transfer candidate,future merger,Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.,project-local first,"Cross-project transfer is possible, but the value is clearest inside the assigned project until source audit exposes more reusable primitives.",do not exclude,Keep in active merge-set and force full source audit before any demotion.,high,single-source signal; clear taxonomy; active integration value; foundation-level fit,high,strong adjacency to identified core stack; memo mentions: 4,"Licensing intentionally ignored as a decision filter in this canonical evaluation; assess only architecture, capability, donor value, and concept transfer.",,,,Lykos/cube_trainer — MIT — Smart-sampled training. | CubeTrainer (Lykos/cube_trainer) | Lykos/cube_trainer — MIT — Smart-sampled alg/BLD trainer. Live: https://www.cubetrainer.org.,"Lykos/cube_trainer is treated as integrate for HyperTwist because the current dossier keeps it as a top-tier strategic donor for persisted sessions, results and statistics, personalization, and advanced BLD-oriented training-domain concepts rather than as a shell to transplant wholesale.",memo,False,True,0.0,4.0,HT_training_stack,HT_training_stack_0002,cubing / algorithm training,Integrate primarily for HyperTwist. Its memo and bookmark signals place it in the cubing / algorithm training layer.,HyperTwist,cubing / algorithm training,integrate,moderate modification,medium,lykos/cube_trainer,1.0,Locked Strategic Donor,3.0,"Top-tier strategic donor for the persistent training-session, statistics, personalization, and advanced BLD-oriented coaching-backend domain.",Top-tier persistent training-domain donor,Included,P1,"Lykos/cube_trainer is placed in Locked Strategic Donor for HyperTwist because it best serves the 'Top-tier persistent training-domain donor' role; recommended action is 'integrate' with repurposing scope 'direct'. Confidence is high because this remains a metadata-level judgment until source audit confirms hidden modules, plugin points, adapters, or architectural strengths.",2.0,5.0,3.0,11857.0,115.0,,lykos/cube_trainer,HyperTwist,,,,,,,,,,Original global Phase G v4 retained,MIT,known_from_reference_material,uploaded_reference_docs,no,,,,Supplemental intake references are advisory only; v6 adjudication remains the source of truth.,Usually indirect,yes,v6 unified all-project source-of-truth pack,v5_carry_forward,,v6_unified_source_of_truth_pack,8.0,2,3.0,145.0,permissive_or_noncopyleft_known,direct_incorporation_ok,"This repo is aligned with a direct integration path for HyperTwist because it is either already implemented, strategically central, or donor-grade without a visible copyleft constraint in the current materials. Deep incorporation is sensible if the source audit confirms architectural cleanliness.","Direct embed, vendored module, package dependency, or tightly integrated adapter as the architecture requires.","Typically preserve notices, attribution, and license text where required; no special copyleft-driven disclosure posture is normally needed.",Usually unnecessary unless you later decide the existing implementation is too constraining architecturally.,high,strategic-or-implemented-component,yes,,,,,,,,,,,,,v6.3_final_source_of_truth,Normalized legacy candidate-core wording to dossier-backed strategic-donor posture on 2026-04-25.,implemented_live_permissive,landed_permissive_preserve,Phase 1R closed. Preserve as a landed first-party permissive lane; keep notices and attribution visible and widen only through ordinary owned enhancement work. 10.0,poliva/cubedex,https://github.com/poliva/cubedex,HyperTwist,9.0,145.0,171.0,A,interface / visualization / shell surface,foundation engine,visualization donor,locked strategic donor,integrate,direct,"Keep the core engine or major subsystem mostly intact; change wrappers, branding, storage/auth, and integration seams so it becomes a first-class part of the target stack. For this repo class, that usually means preserving scene/layout primitives and replacing surrounding data models or backend assumptions.","poliva/cubedex — MIT — Smartcube alg trainer. | Open source repositories and software specifically designed to drill (""hammer"") Rubik's Cube algorithms into muscle memory through repeated practice, timing, smart sampling, real scrambles,...","Integrate as a cubing / algorithm training subsystem for HyperTwist. Preserve the strongest existing pieces — scramble generation, algorithm database, recognition/training loop, timing/statistics, virtual cube, smartcube hooks, spaced repetition — and expose them behind a portfolio-stable interface. Wire first into tao-yu/Alg-Trainer, then into Lykos/cube_trainer for orchestration, visualization, or data exchange.","Consolidate under the Hyperspeedcube + cubing.js + qbr nucleus, not beside it as a separate silo. Normalize data contracts, auth/permissions, storage, and telemetry; then attach as a service, plugin, canvas layer, trainer, or analysis module. Descending combination order: tao-yu/Alg-Trainer, Lykos/cube_trainer, cubing/cubing.js.","Repurpose here means: turn it into a trainer engine, solver/timer backend, recognition drill module, or method-specific practice mode for HyperTwist.",Map module boundaries; Identify hidden reusable internals; Define adapter/API boundary to target anchors; Write extraction tests against upstream behavior; Extract layout/scene primitives; Map import/export schema; Detach UI shell from backend assumptions,full subsystem extraction review,"Hidden value often sits in scene graph/canvas model, component primitives, import/export schema, gesture/keyboard interactions, and plugin-ready layout abstractions.",Inspect scene graph/canvas data model; layout primitives; component library; keyboard/gesture interactions; import/export schema; theming; plugin or extension hooks.,"Inspect package manifests, README/docs, src tree, examples, tests, CI workflows, config files, migrations/schemas, and hidden feature flags or experimental modules. Look for algorithm databases, spaced-repetition logic, scramble generation, timer/stat code, virtual cube components, smartcube adapters, and custom-trainer configuration support.","Audit poliva/cubedex as a interface / visualization / shell surface candidate for HyperTwist. Do not stop at README-level features. Inspect: Inspect scene graph/canvas data model; layout primitives; component library; keyboard/gesture interactions; import/export schema; theming; plugin or extension hooks. Decide whether the best extraction path is direct and whether it belongs as foundation engine / visualization donor. Test the three merger paths in order: 1) project-local anchor [base + donor]; 2) shared portfolio utility [augmenter]; 3) cross-project transfer candidate [future merger]. Return hidden modules, reusable schemas, protocol layers, plugin hooks, render/state models, datasets/test fixtures, and any subsystem stronger than the visible product shell.",project-local anchor,base + donor,Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.,shared portfolio utility,augmenter,Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.,cross-project transfer candidate,future merger,Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.,VectorShell | HyperTwist | ScriptoriumAI,"This capability is broadly portable across the portfolio because interaction, orchestration, and shell/UI patterns can be shared with thin domain adapters.",do not exclude,Keep in active merge-set and force full source audit before any demotion.,high,single-source signal; clear taxonomy; active integration value; foundation-level fit,high,strong adjacency to identified core stack; memo mentions: 4,"Licensing intentionally ignored as a decision filter in this canonical evaluation; assess only architecture, capability, donor value, and concept transfer.",,,,"poliva/cubedex — MIT — Smartcube alg trainer. | Open source repositories and software specifically designed to drill (""hammer"") Rubik's Cube algorithms into muscle memory through repeated practice, timing, smart sampling, real scrambles, virtual cubes, and/or smartcube integration.These tools focus on repetitive training for sets like PLL, OLL, ZBLL, etc., rather than just solving the whole cube.Cubedex (poliva/cubedex) | poliva/cubedex, tao-yu/A","poliva/cubedex is treated as integrate for HyperTwist because the current dossier keeps it as a top-tier strategic donor for smartcube-aware, offline-first training UX, case-card design, and drill ergonomics without promoting it to training-lane foundation status.",memo,False,True,0.0,4.0,HT_training_stack,HT_training_stack_0016,cubing / algorithm training,Integrate primarily for HyperTwist. Its memo and bookmark signals place it in the cubing / algorithm training layer.,HyperTwist,cubing / algorithm training,integrate,moderate modification,medium,poliva/cubedex,1.0,Locked Strategic Donor,3.0,"Top-tier strategic donor for smartcube-aware, offline-first training UX and practical drill ergonomics, but not the owner of the long-term training backend.",Top-tier training UX and smartcube donor,Included,P1,"poliva/cubedex is placed in Locked Strategic Donor for HyperTwist because it best serves the 'Top-tier training UX and smartcube donor' role; recommended action is 'integrate' with repurposing scope 'direct'. Confidence is high because this remains a metadata-level judgment until source audit confirms hidden modules, plugin points, adapters, or architectural strengths.",2.0,5.0,3.0,11861.0,116.0,,poliva/cubedex,HyperTwist,,,,,,,,,,Original global Phase G v4 retained,MIT,known_from_reference_material,uploaded_reference_docs,no,,,,Supplemental intake references are advisory only; v6 adjudication remains the source of truth.,Usually indirect,yes,v6 unified all-project source-of-truth pack,v5_carry_forward,,v6_unified_source_of_truth_pack,9.0,2,3.0,145.0,permissive_or_noncopyleft_known,direct_incorporation_ok,"This repo is aligned with a direct integration path for HyperTwist because it is either already implemented, strategically central, or donor-grade without a visible copyleft constraint in the current materials. Deep incorporation is sensible if the source audit confirms architectural cleanliness.","Direct embed, vendored module, package dependency, or tightly integrated adapter as the architecture requires.","Typically preserve notices, attribution, and license text where required; no special copyleft-driven disclosure posture is normally needed.",Usually unnecessary unless you later decide the existing implementation is too constraining architecturally.,high,strategic-or-implemented-component,yes,,,,,,,,,,,,,v6.3_final_source_of_truth,Assigned from legacy HY_misc to HT_training_stack during cluster normalization on 2026-04-25.,implemented_live_permissive,landed_permissive_preserve,Phase 1R closed. Preserve as a landed first-party permissive lane; keep notices and attribution visible and widen only through ordinary owned enhancement work. 9.0,kash/cubedesk,https://github.com/kash/cubedesk,HyperTwist,10.0,145.0,171.0,A,hypercubing / nD engine,foundation engine,simulation donor,locked strategic donor,repurpose,architecture only,"Keep the core engine or major subsystem mostly intact; change wrappers, branding, storage/auth, and integration seams so it becomes a first-class part of the target stack. For this repo class, that usually means preserving generalized puzzle/state/render logic while building a new application shell around it.",AGPL / GPL / Strong Copyleft (Forces open-sourcing derivatives — study/reference only or use as backend/service; avoid for closed-source core)kash/cubedesk — GPL-3.0 — Full timer + 750+ alg trainers + analytics/community platform. Live: ...,"Integrate as a hypercubing / nD simulation subsystem for HyperTwist. Preserve the strongest existing pieces — nD state model, move notation, renderer, projection controls, solver/traversal logic, puzzle serialization, replay — and expose them behind a portfolio-stable interface. Wire first into HactarCE/Hyperspeedcube, then into cubing/cubing.js for orchestration, visualization, or data exchange.","Consolidate under the Hyperspeedcube + cubing.js + qbr nucleus, not beside it as a separate silo. Normalize data contracts, auth/permissions, storage, and telemetry; then attach as a service, plugin, canvas layer, trainer, or analysis module. Descending combination order: HactarCE/Hyperspeedcube, cubing/cubing.js, tao-yu/Alg-Trainer.",Repurpose here means: turn it into a higher-dimensional renderer/simulator donor and shared interaction grammar for HyperTwist and long-horizon VectorShell.,Map module boundaries; Identify hidden reusable internals; Define adapter/API boundary to target anchors; Write extraction tests against upstream behavior; Isolate puzzle/state core; Extract render/input abstractions; Document notation and save format,full subsystem extraction review,"Hidden value is likely in generalized puzzle/state representations, higher-dimensional transforms, notation systems, save formats, puzzle generators, and rendering abstractions.",Inspect generalized puzzle/state model; notation parser; transform math; rendering abstraction; save/load format; puzzle generator; input mapping; performance optimizations.,"Inspect package manifests, README/docs, src tree, examples, tests, CI workflows, config files, migrations/schemas, and hidden feature flags or experimental modules. Look for higher-dimensional state/notation representations, projection math, renderer abstractions, puzzle serialization, controls, and replay/training hooks.","Audit kash/cubedesk as a hypercubing / nD engine candidate for HyperTwist. Do not stop at README-level features. Inspect: Inspect generalized puzzle/state model; notation parser; transform math; rendering abstraction; save/load format; puzzle generator; input mapping; performance optimizations. Decide whether the best extraction path is direct and whether it belongs as foundation engine / simulation donor. Test the three merger paths in order: 1) HactarCE/Hyperspeedcube [foundation + donor]; 2) cubing/cubing.js [3D engine + notation/state donor]; 3) tao-yu/Alg-Trainer [training UX donor]. Return hidden modules, reusable schemas, protocol layers, plugin hooks, render/state models, datasets/test fixtures, and any subsystem stronger than the visible product shell.",HactarCE/Hyperspeedcube,foundation + donor,"Use this repo against the partner as an augmenting layer; preserve the partner as the likely base and mine this repo for capabilities that improve breadth, UX, or specialization.",cubing/cubing.js,3D engine + notation/state donor,Use the partner for canonical state or rendering abstractions and merge this repo's specialized logic on top.,tao-yu/Alg-Trainer,training UX donor,Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.,VectorShell | ScriptoriumAI,VectorShell can borrow spatial/rendering and perception primitives; ScriptoriumAI can borrow tutorial/educational visualization patterns rather than the full engine.,do not exclude,Keep in active merge-set and force full source audit before any demotion.,high,single-source signal; clear taxonomy; active integration value; foundation-level fit,high,memo mentions: 4,"Licensing intentionally ignored as a decision filter in this canonical evaluation; assess only architecture, capability, donor value, and concept transfer.",,,,AGPL / GPL / Strong Copyleft (Forces open-sourcing derivatives — study/reference only or use as backend/service; avoid for closed-source core)kash/cubedesk — GPL-3.0 — Full timer + 750+ alg trainers + analytics/community platform. Live: https://www.cubedesk.io. | cubing.js (MPL with MIT-vendored parts) remains the 3D foundation — pair with Hyperspeedcube for nD.AGPL / GPL / Strong Copyleft (Study/reference only or backend; avoid for closed-source,"kash/cubedesk is treated as repurpose for HyperTwist because the current dossier keeps it as a restrictive clean-room donor target for timer, trainer, solve/session/stat, smart-device, membership-gating, and broader cubing-platform architecture rather than as a direct donor or foundation.",memo,False,True,0.0,4.0,HT_hyper_engine,HT_hyper_engine_0002,cubing / algorithm training,"Integrate primarily for HyperTwist. The memo context explicitly treats it as a nucleus, foundation, or unusually high-value building block.",HyperTwist,hypercubing / nD simulation,integrate,direct,medium,kash/cubedesk,1.0,Locked Strategic Donor,3.0,"Broad cubing product platform with high strategic value, but the repo must stay in restrictive clean-room custody because README/LICENSE say GPL while package.json says All Rights Reserved.",Restrictive clean-room donor target,Included,P1,"Keep as a strategic clean-room donor because the product breadth is unusually strong, but the conflicting license signals block carefree donor treatment.",2.0,5.0,3.0,11865.0,117.0,,kash/cubedesk,HyperTwist,,,,,,,,,,Original global Phase G v4 retained,GPLv3-or-later in README/LICENSE; package.json says All Rights Reserved,known_from_reference_material,uploaded_reference_docs,no,,,,Supplemental intake references are advisory only; v6 adjudication remains the source of truth.,Usually indirect,yes,v6 unified all-project source-of-truth pack,v5_carry_forward,,v6_unified_source_of_truth_pack,10.0,2,3.0,145.0,mixed_or_boundary_sensitive_known,reverse_engineer_preferred,"The repo has conflicting license signals and should remain in restrictive clean-room custody. Treat it as a strategic product-pattern and subsystem extraction target, not as direct donor code.",Model A may inspect and extract product/subsystem behavior; Model B should implement only from a scrubbed first-party specification.,Do not incorporate directly until the license contradiction is fully resolved; current HyperTwist posture is clean-room donor only.,Yes — this is the preferred path because the strategic value is broad but direct reuse is blocked by the contradictory license posture.,high,license-contradiction-clean-room-donor,no,,,,,,,,,,,,,v6.3_final_source_of_truth,Corrected on 2026-04-25 from stale direct-donor posture to dossier-backed restrictive clean-room strategic donor status.,selected_not_live_clean_room_candidate,phase0r_clean_room_eval_then_model_a_model_b,"Phase 1R closed. Retain as a Phase 5R clean-room-only timer, trainer, stats, and smart-cube product-pattern candidate; implement only from the scrubbed Model A dossier." 12.0,cutelyaware/magiccube4d,https://github.com/cutelyaware/magiccube4d/tree/master,HyperTwist,11.0,122.0,137.0,A,hypercubing / nD engine,subsystem donor,simulation donor,locked strategic donor,repurpose,moderate modification,"Retain the valuable internal engine, but expect to replace UI/product shell, adapt schemas/APIs, and refactor boundaries so it can plug into the target anchors cleanly. For this repo class, that usually means preserving generalized puzzle/state/render logic while building a new application shell around it.",Automatically exported from code.google.com/p/magiccube4d,"Integrate as a hypercubing / nD simulation subsystem for HyperTwist. Preserve the strongest existing pieces — nD state model, move notation, renderer, projection controls, solver/traversal logic, puzzle serialization, replay — and expose them behind a portfolio-stable interface. Wire first into HactarCE/Hyperspeedcube, then into cubing/cubing.js for orchestration, visualization, or data exchange.","Consolidate under the Hyperspeedcube + cubing.js + qbr nucleus, not beside it as a separate silo. Normalize data contracts, auth/permissions, storage, and telemetry; then attach as a service, plugin, canvas layer, trainer, or analysis module. Descending combination order: HactarCE/Hyperspeedcube, cubing/cubing.js, tao-yu/Alg-Trainer.",Repurpose here means: turn it into a higher-dimensional renderer/simulator donor and shared interaction grammar for HyperTwist and long-horizon VectorShell.,Map module boundaries; Identify hidden reusable internals; Define adapter/API boundary to target anchors; Write extraction tests against upstream behavior; Isolate puzzle/state core; Extract render/input abstractions; Document notation and save format,deep source audit,"Hidden value is likely in generalized puzzle/state representations, higher-dimensional transforms, notation systems, save formats, puzzle generators, and rendering abstractions.",Inspect generalized puzzle/state model; notation parser; transform math; rendering abstraction; save/load format; puzzle generator; input mapping; performance optimizations.,"Inspect package manifests, README/docs, src tree, examples, tests, CI workflows, config files, migrations/schemas, and hidden feature flags or experimental modules. Look for higher-dimensional state/notation representations, projection math, renderer abstractions, puzzle serialization, controls, and replay/training hooks.","Audit cutelyaware/magiccube4d as a hypercubing / nD engine candidate for HyperTwist. Do not stop at README-level features. Inspect: Inspect generalized puzzle/state model; notation parser; transform math; rendering abstraction; save/load format; puzzle generator; input mapping; performance optimizations. Decide whether the best extraction path is moderate modification and whether it belongs as subsystem donor / simulation donor. Test the three merger paths in order: 1) HactarCE/Hyperspeedcube [foundation + donor]; 2) cubing/cubing.js [3D engine + notation/state donor]; 3) tao-yu/Alg-Trainer [training UX donor]. Return hidden modules, reusable schemas, protocol layers, plugin hooks, render/state models, datasets/test fixtures, and any subsystem stronger than the visible product shell.",HactarCE/Hyperspeedcube,foundation + donor,"Use this repo against the partner as an augmenting layer; preserve the partner as the likely base and mine this repo for capabilities that improve breadth, UX, or specialization.",cubing/cubing.js,3D engine + notation/state donor,Use the partner for canonical state or rendering abstractions and merge this repo's specialized logic on top.,tao-yu/Alg-Trainer,training UX donor,Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.,VectorShell | ScriptoriumAI,VectorShell can borrow spatial/rendering and perception primitives; ScriptoriumAI can borrow tutorial/educational visualization patterns rather than the full engine.,exclude from standalone? no,"Not necessarily the final base, but keep as an active subsystem candidate or major donor.",medium,single-source signal; clear taxonomy; active integration value,medium,explicit bookmark description available,"Licensing intentionally ignored as a decision filter in this canonical evaluation; assess only architecture, capability, donor value, and concept transfer.",HyperTwist(1),HyperTwist Consider,Automatically exported from code.google.com/p/magiccube4d,,"cutelyaware/magiccube4d is treated as repurpose for HyperTwist because the current dossier keeps it as one of the most important legacy 4D interaction donors, with operationally usable custom licensing but explicit attribution and provenance obligations.",bookmarks,True,False,1.0,0.0,HT_hyper_engine,HT_hyper_engine_0003,hypercubing / nD simulation,"Integrate primarily for HyperTwist. Its description and bookmark placement under ""HyperTwist Consider"" place it in the cubing / algorithm training layer.",HyperTwist,cubing / algorithm training,integrate,moderate modification,medium,cutelyaware/magiccube4d,1.0,Locked Strategic Donor,5.0,Custom broad-use donor with strong 4D interaction/history/macro value and explicit attribution/provenance obligations.,"Top-tier 4D interaction, history, and macro donor with attribution obligations",Included,P1,"Keep as one of the most important legacy 4D interaction donors; the dossier-backed custom broad-use license is operationally usable, but attribution and provenance obligations must stay explicit.",2.0,3.0,3.0,11871.0,118.0,,cutelyaware/magiccube4d,HyperTwist,,,,,,,,,,Original global Phase G v4 retained,Custom broad-use license with attribution requested,known_from_reference_material,uploaded_reference_docs,no,,,,Supplemental intake references are advisory only; v6 adjudication remains the source of truth.,Usually indirect,yes,v6 unified all-project source-of-truth pack,v5_carry_forward,,v6_unified_source_of_truth_pack,11.0,3,5.0,122.0,mixed_or_boundary_sensitive_known,direct_incorporation_ok,"The repo is operationally usable because the custom license explicitly allows use, modification, and redistribution, but attribution and provenance obligations must be preserved and tracked.",Direct donor use is acceptable with explicit attribution and provenance tracking; keep the MyMath.java provenance note visible in license tracking.,"Preserve the custom license text, requested attribution, and the provenance note for utility code with referenced GPL lineage.",Usually unnecessary unless later isolating a narrow seam is cleaner than carrying the legacy code directly.,medium,custom-license-attribution-review,yes,,,,,,,,,,,,,v6.3_final_source_of_truth,Corrected on 2026-04-25 from stale unknown-license merge-bench posture to dossier-backed usable custom-license donor status.,selected_not_live_boundary_sensitive,phase0r_boundary_sensitive_eval_then_adapter_or_sidecar,Phase 1R closed. Retain as a Phase 4R attributed donor beneath the Hyperspeedcube anchor; preserve attribution and provenance explicitly. -13.0,roice3/Magic120Cell,https://github.com/roice3/Magic120Cell,HyperTwist,12.0,122.0,137.0,A,hypercubing / nD engine,subsystem donor,simulation donor,locked strategic donor,repurpose,moderate modification,"Retain the valuable internal engine, but expect to replace UI/product shell, adapt schemas/APIs, and refactor boundaries so it can plug into the target anchors cleanly. For this repo class, that usually means preserving generalized puzzle/state/render logic while building a new application shell around it.",4D Megaminx Analogue,"Integrate as a hypercubing / nD simulation subsystem for HyperTwist. Preserve the strongest existing pieces — nD state model, move notation, renderer, projection controls, solver/traversal logic, puzzle serialization, replay — and expose them behind a portfolio-stable interface. Wire first into HactarCE/Hyperspeedcube, then into cubing/cubing.js for orchestration, visualization, or data exchange.","Consolidate under the Hyperspeedcube + cubing.js + qbr nucleus, not beside it as a separate silo. Normalize data contracts, auth/permissions, storage, and telemetry; then attach as a service, plugin, canvas layer, trainer, or analysis module. Descending combination order: HactarCE/Hyperspeedcube, cubing/cubing.js, tao-yu/Alg-Trainer.",Repurpose here means: turn it into a higher-dimensional renderer/simulator donor and shared interaction grammar for HyperTwist and long-horizon VectorShell.,Map module boundaries; Identify hidden reusable internals; Define adapter/API boundary to target anchors; Write extraction tests against upstream behavior; Isolate puzzle/state core; Extract render/input abstractions; Document notation and save format,deep source audit,"Hidden value is likely in generalized puzzle/state representations, higher-dimensional transforms, notation systems, save formats, puzzle generators, and rendering abstractions.",Inspect generalized puzzle/state model; notation parser; transform math; rendering abstraction; save/load format; puzzle generator; input mapping; performance optimizations.,"Inspect package manifests, README/docs, src tree, examples, tests, CI workflows, config files, migrations/schemas, and hidden feature flags or experimental modules. Look for higher-dimensional state/notation representations, projection math, renderer abstractions, puzzle serialization, controls, and replay/training hooks.","Audit roice3/Magic120Cell as a hypercubing / nD engine candidate for HyperTwist. Do not stop at README-level features. Inspect: Inspect generalized puzzle/state model; notation parser; transform math; rendering abstraction; save/load format; puzzle generator; input mapping; performance optimizations. Decide whether the best extraction path is moderate modification and whether it belongs as subsystem donor / simulation donor. Test the three merger paths in order: 1) HactarCE/Hyperspeedcube [foundation + donor]; 2) cubing/cubing.js [3D engine + notation/state donor]; 3) tao-yu/Alg-Trainer [training UX donor]. Return hidden modules, reusable schemas, protocol layers, plugin hooks, render/state models, datasets/test fixtures, and any subsystem stronger than the visible product shell.",HactarCE/Hyperspeedcube,foundation + donor,"Use this repo against the partner as an augmenting layer; preserve the partner as the likely base and mine this repo for capabilities that improve breadth, UX, or specialization.",cubing/cubing.js,3D engine + notation/state donor,Use the partner for canonical state or rendering abstractions and merge this repo's specialized logic on top.,tao-yu/Alg-Trainer,training UX donor,Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.,VectorShell | ScriptoriumAI,VectorShell can borrow spatial/rendering and perception primitives; ScriptoriumAI can borrow tutorial/educational visualization patterns rather than the full engine.,exclude from standalone? no,"Not necessarily the final base, but keep as an active subsystem candidate or major donor.",medium,single-source signal; clear taxonomy; active integration value,medium,explicit bookmark description available,"Licensing intentionally ignored as a decision filter in this canonical evaluation; assess only architecture, capability, donor value, and concept transfer.",HyperTwist(1),HyperTwist Consider,4D Megaminx Analogue,,"roice3/Magic120Cell is treated as repurpose for HyperTwist because the current dossier keeps it as a specialized 4D interaction and puzzle-UX donor with real save/load, visibility, filtering, and navigation value rather than as a foundation shell.",bookmarks,True,False,1.0,0.0,HT_hyper_engine,HT_hyper_engine_0004,hypercubing / nD simulation,"Integrate primarily for HyperTwist. Its description and bookmark placement under ""HyperTwist Consider"" place it in the hypercubing / nD simulation layer.",HyperTwist,hypercubing / nD simulation,integrate,heavy modification,medium,roice3/magic120cell,1.0,Locked Strategic Donor,5.0,"MIT specialized 4D donor with real interaction, visibility/filtering, save/load, and puzzle-UX value.",Specialized 4D interaction and puzzle-UX donor,Included,P1,Keep as a specialized 4D interaction and puzzle-UX donor; the dossier-backed MIT posture and source richness justify promotion above the old merge-bench treatment.,2.0,3.0,3.0,11875.0,119.0,,roice3/magic120cell,HyperTwist,,,,,,,,,,Original global Phase G v4 retained,MIT,known_from_reference_material,uploaded_reference_docs,no,,,,Supplemental intake references are advisory only; v6 adjudication remains the source of truth.,Usually indirect,yes,v6 unified all-project source-of-truth pack,v5_carry_forward,,v6_unified_source_of_truth_pack,12.0,3,5.0,122.0,permissive_or_noncopyleft_known,direct_incorporation_ok,The repo is MIT and should remain a specialized 4D interaction donor. Direct donor use is legally straightforward if HyperTwist wants to preserve its dedicated UX and puzzle-handling surfaces.,Direct donor use or bounded extraction are both acceptable; choose the seam that best preserves specialized 4D interaction behavior.,Preserve MIT notices and attribution where required.,Usually unnecessary unless later replacing a narrow seam is cleaner than carrying the upstream code.,high,permissive-specialized-donor,yes,,,,,,,,,,,,,v6.3_final_source_of_truth,Corrected on 2026-04-25 from stale unknown-license merge-bench posture to dossier-backed MIT specialized donor status.,selected_not_live_permissive_candidate,phase0r_permissive_eval_then_implement,"Phase 1R closed. Retain as a Phase 3R permissive implementation candidate; implement only from its packet authority and the retained-set contract, not by reopening Phase 0R." -14.0,roice3/MagicCube5D,https://github.com/roice3/MagicCube5D,HyperTwist,13.0,122.0,137.0,A,hypercubing / nD engine,subsystem donor,simulation donor,locked strategic donor,repurpose,moderate modification,"Retain the valuable internal engine, but expect to replace UI/product shell, adapt schemas/APIs, and refactor boundaries so it can plug into the target anchors cleanly. For this repo class, that usually means preserving generalized puzzle/state/render logic while building a new application shell around it.",5D Rubik's Cube Analogue,"Integrate as a hypercubing / nD simulation subsystem for HyperTwist. Preserve the strongest existing pieces — nD state model, move notation, renderer, projection controls, solver/traversal logic, puzzle serialization, replay — and expose them behind a portfolio-stable interface. Wire first into HactarCE/Hyperspeedcube, then into cubing/cubing.js for orchestration, visualization, or data exchange.","Consolidate under the Hyperspeedcube + cubing.js + qbr nucleus, not beside it as a separate silo. Normalize data contracts, auth/permissions, storage, and telemetry; then attach as a service, plugin, canvas layer, trainer, or analysis module. Descending combination order: HactarCE/Hyperspeedcube, cubing/cubing.js, tao-yu/Alg-Trainer.",Repurpose here means: turn it into a higher-dimensional renderer/simulator donor and shared interaction grammar for HyperTwist and long-horizon VectorShell.,Map module boundaries; Identify hidden reusable internals; Define adapter/API boundary to target anchors; Write extraction tests against upstream behavior; Isolate puzzle/state core; Extract render/input abstractions; Document notation and save format,deep source audit,"Hidden value is likely in generalized puzzle/state representations, higher-dimensional transforms, notation systems, save formats, puzzle generators, and rendering abstractions.",Inspect generalized puzzle/state model; notation parser; transform math; rendering abstraction; save/load format; puzzle generator; input mapping; performance optimizations.,"Inspect package manifests, README/docs, src tree, examples, tests, CI workflows, config files, migrations/schemas, and hidden feature flags or experimental modules. Look for higher-dimensional state/notation representations, projection math, renderer abstractions, puzzle serialization, controls, and replay/training hooks.","Audit roice3/MagicCube5D as a hypercubing / nD engine candidate for HyperTwist. Do not stop at README-level features. Inspect: Inspect generalized puzzle/state model; notation parser; transform math; rendering abstraction; save/load format; puzzle generator; input mapping; performance optimizations. Decide whether the best extraction path is moderate modification and whether it belongs as subsystem donor / simulation donor. Test the three merger paths in order: 1) HactarCE/Hyperspeedcube [foundation + donor]; 2) cubing/cubing.js [3D engine + notation/state donor]; 3) tao-yu/Alg-Trainer [training UX donor]. Return hidden modules, reusable schemas, protocol layers, plugin hooks, render/state models, datasets/test fixtures, and any subsystem stronger than the visible product shell.",HactarCE/Hyperspeedcube,foundation + donor,"Use this repo against the partner as an augmenting layer; preserve the partner as the likely base and mine this repo for capabilities that improve breadth, UX, or specialization.",cubing/cubing.js,3D engine + notation/state donor,Use the partner for canonical state or rendering abstractions and merge this repo's specialized logic on top.,tao-yu/Alg-Trainer,training UX donor,Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.,VectorShell | ScriptoriumAI,VectorShell can borrow spatial/rendering and perception primitives; ScriptoriumAI can borrow tutorial/educational visualization patterns rather than the full engine.,exclude from standalone? no,"Not necessarily the final base, but keep as an active subsystem candidate or major donor.",medium,single-source signal; clear taxonomy; active integration value,medium,explicit bookmark description available,"Licensing intentionally ignored as a decision filter in this canonical evaluation; assess only architecture, capability, donor value, and concept transfer.",HyperTwist(1),HyperTwist Consider,5D Rubik's Cube Analogue,,"roice3/MagicCube5D is treated as repurpose for HyperTwist because the current dossier keeps it as a specialized 5D interaction, macro, progress, and slice donor rather than as a foundation shell.",bookmarks,True,False,1.0,0.0,HT_hyper_engine,HT_hyper_engine_0005,hypercubing / nD simulation,"Integrate primarily for HyperTwist. Its description and bookmark placement under ""HyperTwist Consider"" place it in the cubing / algorithm training layer.",HyperTwist,cubing / algorithm training,integrate,moderate modification,medium,roice3/magiccube5d,1.0,Locked Strategic Donor,5.0,"MIT specialized 5D donor with real macro, progress, slice, and advanced interaction value.","Specialized 5D cube interaction, progress, and macro donor",Included,P1,Keep as a specialized 5D cube interaction and macro donor; the dossier-backed MIT posture and source richness justify promotion above the old merge-bench treatment.,2.0,3.0,3.0,11879.0,120.0,,roice3/magiccube5d,HyperTwist,,,,,,,,,,Original global Phase G v4 retained,MIT,known_from_reference_material,uploaded_reference_docs,no,,,,Supplemental intake references are advisory only; v6 adjudication remains the source of truth.,Usually indirect,yes,v6 unified all-project source-of-truth pack,v5_carry_forward,,v6_unified_source_of_truth_pack,13.0,3,5.0,122.0,permissive_or_noncopyleft_known,direct_incorporation_ok,The repo is MIT and should remain a specialized 5D interaction donor. Direct donor use is legally straightforward if HyperTwist wants to preserve its advanced cube-specific UX and macro behavior.,Direct donor use or bounded extraction are both acceptable; choose the seam that best preserves specialized 5D interaction and macro behavior.,Preserve MIT notices and attribution where required.,Usually unnecessary unless later replacing a narrow seam is cleaner than carrying the upstream code.,high,permissive-specialized-donor,yes,,,,,,,,,,,,,v6.3_final_source_of_truth,Corrected on 2026-04-25 from stale unknown-license merge-bench posture to dossier-backed MIT specialized donor status.,selected_not_live_permissive_candidate,phase0r_permissive_eval_then_implement,"Phase 1R closed. Retain as a Phase 3R permissive implementation candidate; implement only from its packet authority and the retained-set contract, not by reopening Phase 0R." +13.0,roice3/Magic120Cell,https://github.com/roice3/Magic120Cell,HyperTwist,12.0,122.0,137.0,A,hypercubing / nD engine,subsystem donor,simulation donor,locked strategic donor,repurpose,moderate modification,"Retain the valuable internal engine, but expect to replace UI/product shell, adapt schemas/APIs, and refactor boundaries so it can plug into the target anchors cleanly. For this repo class, that usually means preserving generalized puzzle/state/render logic while building a new application shell around it.",4D Megaminx Analogue,"Integrate as a hypercubing / nD simulation subsystem for HyperTwist. Preserve the strongest existing pieces — nD state model, move notation, renderer, projection controls, solver/traversal logic, puzzle serialization, replay — and expose them behind a portfolio-stable interface. Wire first into HactarCE/Hyperspeedcube, then into cubing/cubing.js for orchestration, visualization, or data exchange.","Consolidate under the Hyperspeedcube + cubing.js + qbr nucleus, not beside it as a separate silo. Normalize data contracts, auth/permissions, storage, and telemetry; then attach as a service, plugin, canvas layer, trainer, or analysis module. Descending combination order: HactarCE/Hyperspeedcube, cubing/cubing.js, tao-yu/Alg-Trainer.",Repurpose here means: turn it into a higher-dimensional renderer/simulator donor and shared interaction grammar for HyperTwist and long-horizon VectorShell.,Map module boundaries; Identify hidden reusable internals; Define adapter/API boundary to target anchors; Write extraction tests against upstream behavior; Isolate puzzle/state core; Extract render/input abstractions; Document notation and save format,deep source audit,"Hidden value is likely in generalized puzzle/state representations, higher-dimensional transforms, notation systems, save formats, puzzle generators, and rendering abstractions.",Inspect generalized puzzle/state model; notation parser; transform math; rendering abstraction; save/load format; puzzle generator; input mapping; performance optimizations.,"Inspect package manifests, README/docs, src tree, examples, tests, CI workflows, config files, migrations/schemas, and hidden feature flags or experimental modules. Look for higher-dimensional state/notation representations, projection math, renderer abstractions, puzzle serialization, controls, and replay/training hooks.","Audit roice3/Magic120Cell as a hypercubing / nD engine candidate for HyperTwist. Do not stop at README-level features. Inspect: Inspect generalized puzzle/state model; notation parser; transform math; rendering abstraction; save/load format; puzzle generator; input mapping; performance optimizations. Decide whether the best extraction path is moderate modification and whether it belongs as subsystem donor / simulation donor. Test the three merger paths in order: 1) HactarCE/Hyperspeedcube [foundation + donor]; 2) cubing/cubing.js [3D engine + notation/state donor]; 3) tao-yu/Alg-Trainer [training UX donor]. Return hidden modules, reusable schemas, protocol layers, plugin hooks, render/state models, datasets/test fixtures, and any subsystem stronger than the visible product shell.",HactarCE/Hyperspeedcube,foundation + donor,"Use this repo against the partner as an augmenting layer; preserve the partner as the likely base and mine this repo for capabilities that improve breadth, UX, or specialization.",cubing/cubing.js,3D engine + notation/state donor,Use the partner for canonical state or rendering abstractions and merge this repo's specialized logic on top.,tao-yu/Alg-Trainer,training UX donor,Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.,VectorShell | ScriptoriumAI,VectorShell can borrow spatial/rendering and perception primitives; ScriptoriumAI can borrow tutorial/educational visualization patterns rather than the full engine.,exclude from standalone? no,"Not necessarily the final base, but keep as an active subsystem candidate or major donor.",medium,single-source signal; clear taxonomy; active integration value,medium,explicit bookmark description available,"Licensing intentionally ignored as a decision filter in this canonical evaluation; assess only architecture, capability, donor value, and concept transfer.",HyperTwist(1),HyperTwist Consider,4D Megaminx Analogue,,"roice3/Magic120Cell is treated as repurpose for HyperTwist because the current dossier keeps it as a specialized 4D interaction and puzzle-UX donor with real save/load, visibility, filtering, and navigation value rather than as a foundation shell.",bookmarks,True,False,1.0,0.0,HT_hyper_engine,HT_hyper_engine_0004,hypercubing / nD simulation,"Integrate primarily for HyperTwist. Its description and bookmark placement under ""HyperTwist Consider"" place it in the hypercubing / nD simulation layer.",HyperTwist,hypercubing / nD simulation,integrate,heavy modification,medium,roice3/magic120cell,1.0,Locked Strategic Donor,5.0,"MIT specialized 4D donor with real interaction, visibility/filtering, save/load, and puzzle-UX value.",Specialized 4D interaction and puzzle-UX donor,Included,P1,Keep as a specialized 4D interaction and puzzle-UX donor; the dossier-backed MIT posture and source richness justify promotion above the old merge-bench treatment.,2.0,3.0,3.0,11875.0,119.0,,roice3/magic120cell,HyperTwist,,,,,,,,,,Original global Phase G v4 retained,MIT,known_from_reference_material,uploaded_reference_docs,no,,,,Supplemental intake references are advisory only; v6 adjudication remains the source of truth.,Usually indirect,yes,v6 unified all-project source-of-truth pack,v5_carry_forward,,v6_unified_source_of_truth_pack,12.0,3,5.0,122.0,permissive_or_noncopyleft_known,direct_incorporation_ok,The repo is MIT and should remain a specialized 4D interaction donor. Direct donor use is legally straightforward if HyperTwist wants to preserve its dedicated UX and puzzle-handling surfaces.,Direct donor use or bounded extraction are both acceptable; choose the seam that best preserves specialized 4D interaction behavior.,Preserve MIT notices and attribution where required.,Usually unnecessary unless later replacing a narrow seam is cleaner than carrying the upstream code.,high,permissive-specialized-donor,yes,,,,,,,,,,,,,v6.3_final_source_of_truth,Corrected on 2026-04-25 from stale unknown-license merge-bench posture to dossier-backed MIT specialized donor status.,implemented_live_permissive,landed_permissive_preserve,"Phase 3R-E closed. Preserve as the landed first-party embodied companion, narration, lip-sync, gesture, subtitle, and avatar-embed lane; start future widening from the live-lane audit, then the 3R-E implementation packet, then REPO_LICENSE_TRACKING.md." +14.0,roice3/MagicCube5D,https://github.com/roice3/MagicCube5D,HyperTwist,13.0,122.0,137.0,A,hypercubing / nD engine,subsystem donor,simulation donor,locked strategic donor,repurpose,moderate modification,"Retain the valuable internal engine, but expect to replace UI/product shell, adapt schemas/APIs, and refactor boundaries so it can plug into the target anchors cleanly. For this repo class, that usually means preserving generalized puzzle/state/render logic while building a new application shell around it.",5D Rubik's Cube Analogue,"Integrate as a hypercubing / nD simulation subsystem for HyperTwist. Preserve the strongest existing pieces — nD state model, move notation, renderer, projection controls, solver/traversal logic, puzzle serialization, replay — and expose them behind a portfolio-stable interface. Wire first into HactarCE/Hyperspeedcube, then into cubing/cubing.js for orchestration, visualization, or data exchange.","Consolidate under the Hyperspeedcube + cubing.js + qbr nucleus, not beside it as a separate silo. Normalize data contracts, auth/permissions, storage, and telemetry; then attach as a service, plugin, canvas layer, trainer, or analysis module. Descending combination order: HactarCE/Hyperspeedcube, cubing/cubing.js, tao-yu/Alg-Trainer.",Repurpose here means: turn it into a higher-dimensional renderer/simulator donor and shared interaction grammar for HyperTwist and long-horizon VectorShell.,Map module boundaries; Identify hidden reusable internals; Define adapter/API boundary to target anchors; Write extraction tests against upstream behavior; Isolate puzzle/state core; Extract render/input abstractions; Document notation and save format,deep source audit,"Hidden value is likely in generalized puzzle/state representations, higher-dimensional transforms, notation systems, save formats, puzzle generators, and rendering abstractions.",Inspect generalized puzzle/state model; notation parser; transform math; rendering abstraction; save/load format; puzzle generator; input mapping; performance optimizations.,"Inspect package manifests, README/docs, src tree, examples, tests, CI workflows, config files, migrations/schemas, and hidden feature flags or experimental modules. Look for higher-dimensional state/notation representations, projection math, renderer abstractions, puzzle serialization, controls, and replay/training hooks.","Audit roice3/MagicCube5D as a hypercubing / nD engine candidate for HyperTwist. Do not stop at README-level features. Inspect: Inspect generalized puzzle/state model; notation parser; transform math; rendering abstraction; save/load format; puzzle generator; input mapping; performance optimizations. Decide whether the best extraction path is moderate modification and whether it belongs as subsystem donor / simulation donor. Test the three merger paths in order: 1) HactarCE/Hyperspeedcube [foundation + donor]; 2) cubing/cubing.js [3D engine + notation/state donor]; 3) tao-yu/Alg-Trainer [training UX donor]. Return hidden modules, reusable schemas, protocol layers, plugin hooks, render/state models, datasets/test fixtures, and any subsystem stronger than the visible product shell.",HactarCE/Hyperspeedcube,foundation + donor,"Use this repo against the partner as an augmenting layer; preserve the partner as the likely base and mine this repo for capabilities that improve breadth, UX, or specialization.",cubing/cubing.js,3D engine + notation/state donor,Use the partner for canonical state or rendering abstractions and merge this repo's specialized logic on top.,tao-yu/Alg-Trainer,training UX donor,Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.,VectorShell | ScriptoriumAI,VectorShell can borrow spatial/rendering and perception primitives; ScriptoriumAI can borrow tutorial/educational visualization patterns rather than the full engine.,exclude from standalone? no,"Not necessarily the final base, but keep as an active subsystem candidate or major donor.",medium,single-source signal; clear taxonomy; active integration value,medium,explicit bookmark description available,"Licensing intentionally ignored as a decision filter in this canonical evaluation; assess only architecture, capability, donor value, and concept transfer.",HyperTwist(1),HyperTwist Consider,5D Rubik's Cube Analogue,,"roice3/MagicCube5D is treated as repurpose for HyperTwist because the current dossier keeps it as a specialized 5D interaction, macro, progress, and slice donor rather than as a foundation shell.",bookmarks,True,False,1.0,0.0,HT_hyper_engine,HT_hyper_engine_0005,hypercubing / nD simulation,"Integrate primarily for HyperTwist. Its description and bookmark placement under ""HyperTwist Consider"" place it in the cubing / algorithm training layer.",HyperTwist,cubing / algorithm training,integrate,moderate modification,medium,roice3/magiccube5d,1.0,Locked Strategic Donor,5.0,"MIT specialized 5D donor with real macro, progress, slice, and advanced interaction value.","Specialized 5D cube interaction, progress, and macro donor",Included,P1,Keep as a specialized 5D cube interaction and macro donor; the dossier-backed MIT posture and source richness justify promotion above the old merge-bench treatment.,2.0,3.0,3.0,11879.0,120.0,,roice3/magiccube5d,HyperTwist,,,,,,,,,,Original global Phase G v4 retained,MIT,known_from_reference_material,uploaded_reference_docs,no,,,,Supplemental intake references are advisory only; v6 adjudication remains the source of truth.,Usually indirect,yes,v6 unified all-project source-of-truth pack,v5_carry_forward,,v6_unified_source_of_truth_pack,13.0,3,5.0,122.0,permissive_or_noncopyleft_known,direct_incorporation_ok,The repo is MIT and should remain a specialized 5D interaction donor. Direct donor use is legally straightforward if HyperTwist wants to preserve its advanced cube-specific UX and macro behavior.,Direct donor use or bounded extraction are both acceptable; choose the seam that best preserves specialized 5D interaction and macro behavior.,Preserve MIT notices and attribution where required.,Usually unnecessary unless later replacing a narrow seam is cleaner than carrying the upstream code.,high,permissive-specialized-donor,yes,,,,,,,,,,,,,v6.3_final_source_of_truth,Corrected on 2026-04-25 from stale unknown-license merge-bench posture to dossier-backed MIT specialized donor status.,implemented_live_permissive,landed_permissive_preserve,"Phase 3R-E closed. Preserve as the landed first-party embodied companion, narration, lip-sync, gesture, subtitle, and avatar-embed lane; start future widening from the live-lane audit, then the 3R-E implementation packet, then REPO_LICENSE_TRACKING.md." 11.0,cs0x7f/cstimer,https://github.com/cs0x7f/cstimer,HyperTwist,14.0,121.0,147.0,A,gold-standard timer benchmark,benchmark,Gold-standard timer benchmark,Reserve Bench,future candidate,architecture only,"Retain the valuable internal engine, but expect to replace UI/product shell, adapt schemas/APIs, and refactor boundaries so it can plug into the target anchors cleanly. For this repo class, that usually means preserving cube-state, scramble, scheduling, or timer internals while adapting pedagogy, analytics, and UI.","Benchmark-only retained value: mature timer-state handling, persistence, statistics, reconstruction tooling, scramble generation, and smart-device expectations. Study behavior and category expectations only.","Keep as a restrictive benchmark. Use it as the timer behavior reference point for HyperTwist, not as donor code.",Do not merge this repo into the HyperTwist core. Translate only high-level timer and stats expectations into first-party implementations.,"Repurpose here means: derive acceptance-test targets and product expectations for timer flow, persistence, statistics, and hardware support.",Map module boundaries; Identify hidden reusable internals; Define adapter/API boundary to target anchors; Write extraction tests against upstream behavior; Extract cube-state model; Normalize trainer/case schema; Expose analytics and replay hooks,behavior and acceptance-test benchmark review,"Hidden value sits in timer edge cases, persistence behavior, reconstruction/statistics expectations, and mature product-surface decisions.","Which timer behaviors, persistence expectations, and solve-analysis surfaces should become first-party acceptance criteria?","Inspect timer-state transitions, solve/session persistence, statistics/reconstruction surfaces, scramble integration, and smart-device behavior as benchmark material only.","Audit cs0x7f/cstimer only as a restrictive gold-standard timer benchmark for HyperTwist. Extract behavior expectations and acceptance criteria, not donor code.",tao-yu/Alg-Trainer,base + donor swarm,Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.,poliva/cubedex,specialized training UX donor,Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.,Lykos/cube_trainer,sampling/analytics donor,Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.,Reference only,"Retain only as benchmark, oracle, acceptance-test, or clean-room planning input.",exclude from donor lane,The repo is GPL timer/training software and should remain the behavior/category benchmark in the timer lane rather than a donor codebase.,high,"Dossier-backed classification is stable: the retained value is benchmark authority, not source incorporation.",high,"Dossier-backed classification is stable: the retained value is benchmark authority, not source incorporation.","Licensing intentionally ignored as a decision filter in this canonical evaluation; assess only architecture, capability, donor value, and concept transfer.",,,,cs0x7f/cstimer — GPL timer/training platform; keep only as the gold-standard timer benchmark.,"cs0x7f/cstimer remains valuable because it defines the product-behavior ceiling for timer flow, persistence, and statistics. That value is benchmark authority, not donor code.",memo,False,True,0.0,5.0,HT_timer_training,HT_timer_training_0001,Gold-standard timer benchmark,"Gold-standard timer benchmark for HyperTwist; retained for behavior calibration, not donor use.",HyperTwist,Gold-standard timer benchmark,future candidate,architecture only,medium,cs0x7f/cstimer,1.0,Reserve Bench,3.0,"GPL timer/training platform whose value is product expectations, acceptance tests, and behavior benchmarking rather than donor use.",Gold-standard timer benchmark,Included,P2,Keep in canon as the strongest restrictive timer benchmark; use it to calibrate first-party timer and stats behavior.,2.0,5.0,3.0,11881.0,121.0,,cs0x7f/cstimer,HyperTwist,,,,,,,,,,Original global Phase G v4 retained,GPL-3.0,known_from_reference_material,uploaded_reference_docs,no,,,,Supplemental intake references are advisory only; v6 adjudication remains the source of truth.,Usually indirect,yes,v6 unified all-project source-of-truth pack,v5_carry_forward,,v6_unified_source_of_truth_pack,14.0,2,3.0,121.0,mixed_or_boundary_sensitive_known,pattern_only_preferred,"The repo is GPL-3.0 and remains the primary restrictive timer, stats, scramble, and smart-device benchmark. Use it for behavioral parity and acceptance criteria, not direct source incorporation.","Reference only: benchmark timer, statistics, scramble, and smart-device behavior without direct source incorporation.",Direct incorporation would require GPL-compatible distribution/compliance and is not the planned HyperTwist path.,Only if a narrow timer behavior later proves strategically necessary to recreate in first-party code; otherwise keep this as a benchmark.,high,gpl-timer-benchmark,no,,,,,,,,,,,,,v6.3_final_source_of_truth,Corrected on 2026-04-25 from stale donor posture to dossier-backed gold-standard timer benchmark status.,not_live_reference_or_discard_candidate,phase0r_reference_benchmark_or_discard_eval,Packet 0R-E closed. Retain as the primary restrictive timer/stats/scramble/smart-device benchmark and future clean-room timer-pattern oracle. 16.0,aMonteSl/CodeXR,https://github.com/aMonteSl/CodeXR,HyperTwist,16.0,119.0,134.0,B,reference-only XR benchmark,benchmark,Reference-only XR benchmark,Reserve Bench,future candidate,architecture only,"Retain the valuable internal engine, but expect to replace UI/product shell, adapt schemas/APIs, and refactor boundaries so it can plug into the target anchors cleanly. For this repo class, that usually means preserving calibration/detection/state-reconstruction logic while replacing camera UX and integration surfaces.","Benchmark-only retained value: immersive interaction, collaboration-room, virtual-screen, and scene-launch patterns. Study behavior and workflow ideas only; do not plan direct product incorporation.",Keep in restrictive/reference custody. Use only as a benchmark for XR interaction ideas and immersive UI patterns; do not merge source into HyperTwist.,"Do not treat this repo as part of the HyperTwist merge nucleus. If useful, translate isolated interaction ideas into first-party designs without inheriting the code-analysis shell.",Repurpose here means: abstract useful XR interaction ideas into first-party browser/XR surfaces without reusing source.,Map module boundaries; Identify hidden reusable internals; Define adapter/API boundary to target anchors; Write extraction tests against upstream behavior; Benchmark calibration pipeline; Extract state reconstruction; Wrap with camera/AR adapter,behavior-level benchmark review,"Hidden value sits in collaboration-room flow, scene-launch orchestration, virtual-screen components, and immersive inspection patterns.",Which interaction patterns are reusable at the behavior level without inheriting the code-analysis product identity or GPL source?,"Inspect XR launch flow, collaboration-room server patterns, virtual-screen behavior, and immersive UI choreography as benchmark material only.","Audit aMonteSl/CodeXR only as a reference-only XR benchmark for HyperTwist. Do not recommend direct incorporation. Extract interaction patterns, collaboration metaphors, and virtual-screen ideas only.",kkoomen/qbr,foundation + perception donor,"Use this repo against the partner as an augmenting layer; preserve the partner as the likely base and mine this repo for capabilities that improve breadth, UX, or specialization.",vivaansinghvi07/rubix-cube-solver,perception + replay donor,Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.,cubing/cubing.js,state/render backend,Use the partner for canonical state or rendering abstractions and merge this repo's specialized logic on top.,Reference only,"Retain only as benchmark, oracle, acceptance-test, or clean-room planning input.",exclude from donor lane,The repo is a GPL-3.0-only VS Code XR analysis extension and materially off-mission for HyperTwist; retain only as a reference benchmark.,high,Source-backed dossier and license verification collapse the old donor thesis.,high,Source-backed dossier and license verification collapse the old donor thesis.,"Licensing intentionally ignored as a decision filter in this canonical evaluation; assess only architecture, capability, donor value, and concept transfer.",,,,aMonteSl/CodeXR — GPL-3.0-only VS Code XR analysis extension; keep only as a reference-only XR benchmark for interaction ideas.,"aMonteSl/CodeXR is retained only as a reference-only XR benchmark. It is a legitimate immersive code-analysis product, but the GPL-3.0-only license and domain mismatch rule out donor treatment for HyperTwist.",memo,False,True,0.0,3.0,HT_cube_vision,HT_cube_vision_0005,Reference-only XR benchmark,Reference-only XR benchmark for HyperTwist; not a donor lane.,HyperTwist,Reference-only XR benchmark,future candidate,architecture only,medium,amontesl/code-xr,1.0,Reserve Bench,5.0,GPL-3.0-only code-analysis XR extension with narrow benchmark value for immersive interaction patterns.,Reference-only XR benchmark,Included,P3,"Keep in canon only as a reference-only XR benchmark; its value is in interaction ideas, not donor code.",2.0,3.0,3.0,11890.0,3226.0,,amontesl/codexr,HyperTwist,,,,,,,,,,Original global Phase G v4 retained,GPL-3.0-only,known_from_reference_material,uploaded_reference_docs,no,,,,Supplemental intake references are advisory only; v6 adjudication remains the source of truth.,Potentially relevant,yes,v6 unified all-project source-of-truth pack,v5_carry_forward,,v6_unified_source_of_truth_pack,16.0,3,5.0,119.0,mixed_or_boundary_sensitive_known,pattern_only_preferred,The repo is GPL-3.0-only and was discarded from the active HyperTwist retained set because its strongest XR collaboration value is off-domain and already superseded by stronger retained rows.,Reference only: discarded historical comparison context for XR collaboration patterns; do not plan direct incorporation.,Direct incorporation would require GPL-compatible distribution/compliance and is not the planned HyperTwist path.,Only if a uniquely valuable interaction pattern later needs first-party recreation; otherwise keep this as a benchmark.,high,gpl-reference-only-benchmark,no,,,,,,,,,,,,,v6.3_final_source_of_truth,Corrected on 2026-04-25 from stale pre-dossier donor posture to dossier-backed GPL reference-only benchmark status.,not_live_reference_or_discard_candidate,phase0r_reference_benchmark_or_discard_eval,Packet 0R-E closed. Discard from the active retained set; its XR collaboration value is off-domain and already superseded by stronger retained rows. 17.0,brianpeiris/RiftSketch,https://github.com/brianpeiris/RiftSketch,HyperTwist,17.0,119.0,134.0,B,vision / perception / AR,subsystem donor,vision donor,Reserve Bench,future candidate,architecture only,"Retain the valuable internal engine, but expect to replace UI/product shell, adapt schemas/APIs, and refactor boundaries so it can plug into the target anchors cleanly. For this repo class, that usually means preserving calibration/detection/state-reconstruction logic while replacing camera UX and integration surfaces.","brianpeiris/RiftSketch — https://github.com/brianpeiris/RiftSketch | brianpeiris/RiftSketch — MIT — WebVR live coding. | poliva/cubedex, tao-yu/Alg-Trainer, kkoomen/qbr, vivaansinghvi07/rubix-cube-solver, NuiLab/code-vr, molgenis/Graph2V...","Integrate as a cubing / algorithm training subsystem for HyperTwist. Preserve the strongest existing pieces — scramble generation, algorithm database, recognition/training loop, timing/statistics, virtual cube, smartcube hooks, spaced repetition — and expose them behind a portfolio-stable interface. Wire first into tao-yu/Alg-Trainer, then into poliva/cubedex for orchestration, visualization, or data exchange.","Consolidate under the Hyperspeedcube + cubing.js + qbr nucleus, not beside it as a separate silo. Normalize data contracts, auth/permissions, storage, and telemetry; then attach as a service, plugin, canvas layer, trainer, or analysis module. Descending combination order: tao-yu/Alg-Trainer, poliva/cubedex, Lykos/cube_trainer.","Repurpose here means: turn it into a trainer engine, solver/timer backend, recognition drill module, or method-specific practice mode for HyperTwist.",Map module boundaries; Identify hidden reusable internals; Define adapter/API boundary to target anchors; Write extraction tests against upstream behavior; Benchmark calibration pipeline; Extract state reconstruction; Wrap with camera/AR adapter,deep source audit,"Hidden value often sits in calibration, preprocessing, stabilization, object/state reconstruction, replay artifacts, and camera-to-domain state pipelines that are not obvious from demos.",Inspect preprocessing/calibration; tracking stabilization; state reconstruction; replay/event model; camera abstraction; fallback heuristics; testing assets/videos; performance shortcuts.,"Inspect package manifests, README/docs, src tree, examples, tests, CI workflows, config files, migrations/schemas, and hidden feature flags or experimental modules. Look for algorithm databases, spaced-repetition logic, scramble generation, timer/stat code, virtual cube components, smartcube adapters, and custom-trainer configuration support.","Audit brianpeiris/RiftSketch as a vision / perception / AR candidate for HyperTwist. Do not stop at README-level features. Inspect: Inspect preprocessing/calibration; tracking stabilization; state reconstruction; replay/event model; camera abstraction; fallback heuristics; testing assets/videos; performance shortcuts. Decide whether the best extraction path is moderate modification and whether it belongs as subsystem donor / vision donor. Test the three merger paths in order: 1) kkoomen/qbr [foundation + perception donor]; 2) vivaansinghvi07/rubix-cube-solver [perception + replay donor]; 3) cubing/cubing.js [state/render backend]. Return hidden modules, reusable schemas, protocol layers, plugin hooks, render/state models, datasets/test fixtures, and any subsystem stronger than the visible product shell.",kkoomen/qbr,foundation + perception donor,"Use this repo against the partner as an augmenting layer; preserve the partner as the likely base and mine this repo for capabilities that improve breadth, UX, or specialization.",vivaansinghvi07/rubix-cube-solver,perception + replay donor,Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.,cubing/cubing.js,state/render backend,Use the partner for canonical state or rendering abstractions and merge this repo's specialized logic on top.,VectorShell | ScriptoriumAI,VectorShell can borrow spatial/rendering and perception primitives; ScriptoriumAI can borrow tutorial/educational visualization patterns rather than the full engine.,exclude from standalone? no,"Not necessarily the final base, but keep as an active subsystem candidate or major donor.",medium,single-source signal; clear taxonomy; active integration value,medium,memo mentions: 3,"Licensing intentionally ignored as a decision filter in this canonical evaluation; assess only architecture, capability, donor value, and concept transfer.",,,,"brianpeiris/RiftSketch — https://github.com/brianpeiris/RiftSketch | brianpeiris/RiftSketch — MIT — WebVR live coding. | poliva/cubedex, tao-yu/Alg-Trainer, kkoomen/qbr, vivaansinghvi07/rubix-cube-solver, NuiLab/code-vr, molgenis/Graph2VR (core permissive parts), brianpeiris/RiftSketch, aMonteSl/CodeXR.","brianpeiris/RiftSketch is treated as a future candidate for HyperTwist because the current dossier retains it mainly for WebXR spatial-UI, world-space monitor, and immersive tooling patterns rather than as a cubing-specific core or active merge donor.",memo,False,True,0.0,3.0,HT_cube_vision,HT_cube_vision_0006,cubing / algorithm training,Integrate as a shared building block across at least two projects. Its memo and bookmark signals place it in the computer vision / AR layer.,multi-project,computer vision / AR,integrate,heavy modification,medium,brianpeiris/riftsketch,1.0,Reserve Bench,5.0,"Useful MIT WebXR interaction benchmark for spatial editor panels, world-space monitors, and keyboard-first immersive tooling, but explicitly below the HyperTwist core tier.",XR interaction and spatial-UI bench,Included,P2,"brianpeiris/RiftSketch is placed in Reserve Bench for HyperTwist because it best serves the 'XR interaction and spatial-UI bench' role; recommended action is 'future candidate' with repurposing scope 'architecture only'. Confidence is medium because this remains a metadata-level judgment until source audit confirms hidden modules, plugin points, adapters, or architectural strengths.",2.0,3.0,3.0,11894.0,3227.0,,brianpeiris/riftsketch,HyperTwist,,,,,,,,,,Original global Phase G v4 retained,MIT,known_from_reference_material,uploaded_reference_docs,no,,,,Supplemental intake references are advisory only; v6 adjudication remains the source of truth.,Potentially relevant,yes,v6 unified all-project source-of-truth pack,v5_carry_forward,,v6_unified_source_of_truth_pack,17.0,3,5.0,119.0,permissive_or_noncopyleft_known,pattern_only_preferred,The repo is MIT but was discarded from the active retained set because its immersive live-coding shell is off topic to HyperTwist's retained product scope.,Reference only: discarded historical comparison context for immersive live-coding patterns; do not plan direct incorporation.,"Typically preserve notices, attribution, and license text where required; no special copyleft-driven disclosure posture is normally needed.",Usually unnecessary unless you later decide the existing implementation is too constraining architecturally.,high,strategic-or-implemented-component,yes,,,,,,,,,,,,,v6.3_final_source_of_truth,Normalized legacy merge-bench wording to dossier-backed below-core benchmark posture on 2026-04-25.,not_live_reference_or_discard_candidate,phase0r_reference_benchmark_or_discard_eval,Packet 0R-E closed. Discard from the active retained set; immersive live-coding is off topic to HyperTwist's retained product scope. 21.0,abunickabhi/5style-Trainer,https://github.com/abunickabhi/5style-Trainer,HyperTwist,18.0,118.0,133.0,B,cubing trainer / solver / timing,subsystem donor,training donor,donor bench,repurpose,moderate modification,"Retain the valuable internal engine, but expect to replace UI/product shell, adapt schemas/APIs, and refactor boundaries so it can plug into the target anchors cleanly. For this repo class, that usually means preserving cube-state, scramble, scheduling, or timer internals while adapting pedagogy, analytics, and UI.",abunickabhi/5style-Trainer — MIT — 5-style BLD trainer (fork of Alg-Trainer). | abunickabhi/5style-Trainer — MIT (BLD extension).,"Integrate as a cubing / algorithm training subsystem for HyperTwist. Preserve the strongest existing pieces — scramble generation, algorithm database, recognition/training loop, timing/statistics, virtual cube, smartcube hooks, spaced repetition — and expose them behind a portfolio-stable interface. Wire first into tao-yu/Alg-Trainer, then into poliva/cubedex for orchestration, visualization, or data exchange.","Consolidate under the Hyperspeedcube + cubing.js + qbr nucleus, not beside it as a separate silo. Normalize data contracts, auth/permissions, storage, and telemetry; then attach as a service, plugin, canvas layer, trainer, or analysis module. Descending combination order: tao-yu/Alg-Trainer, poliva/cubedex, Lykos/cube_trainer.","Repurpose here means: turn it into a trainer engine, solver/timer backend, recognition drill module, or method-specific practice mode for HyperTwist.",Map module boundaries; Identify hidden reusable internals; Define adapter/API boundary to target anchors; Write extraction tests against upstream behavior; Extract cube-state model; Normalize trainer/case schema; Expose analytics and replay hooks,deep source audit,"Hidden value often sits in cube-state representation, scramble generation, weighted drill scheduling, recognition datasets, replay/timer internals, and case database schemas.",Inspect cube-state model; scramble generator; trainer weighting/scheduling; case database and metadata; replay/timer model; import/export of alg sets; smartcube or sensor adapters.,"Inspect package manifests, README/docs, src tree, examples, tests, CI workflows, config files, migrations/schemas, and hidden feature flags or experimental modules. Look for algorithm databases, spaced-repetition logic, scramble generation, timer/stat code, virtual cube components, smartcube adapters, and custom-trainer configuration support.","Audit abunickabhi/5style-Trainer as a cubing trainer / solver / timing candidate for HyperTwist. Do not stop at README-level features. Inspect: Inspect cube-state model; scramble generator; trainer weighting/scheduling; case database and metadata; replay/timer model; import/export of alg sets; smartcube or sensor adapters. Decide whether the best extraction path is moderate modification and whether it belongs as subsystem donor / training donor. Test the three merger paths in order: 1) tao-yu/Alg-Trainer [base + donor swarm]; 2) poliva/cubedex [specialized training UX donor]; 3) Lykos/cube_trainer [sampling/analytics donor]. Return hidden modules, reusable schemas, protocol layers, plugin hooks, render/state models, datasets/test fixtures, and any subsystem stronger than the visible product shell.",tao-yu/Alg-Trainer,base + donor swarm,Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.,poliva/cubedex,specialized training UX donor,Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.,Lykos/cube_trainer,sampling/analytics donor,Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.,project-local first,"Cross-project transfer is possible, but the value is clearest inside the assigned project until source audit exposes more reusable primitives.",exclude from standalone? no,"Not necessarily the final base, but keep as an active subsystem candidate or major donor.",medium,single-source signal; clear taxonomy; active integration value,medium,strong adjacency to identified core stack; memo mentions: 2,"Licensing intentionally ignored as a decision filter in this canonical evaluation; assess only architecture, capability, donor value, and concept transfer.",,,,abunickabhi/5style-Trainer — MIT — 5-style BLD trainer (fork of Alg-Trainer). | abunickabhi/5style-Trainer — MIT (BLD extension).,"abunickabhi/5style-Trainer is treated as repurpose for HyperTwist because the current dossier keeps it as a focused advanced-training donor for 5-style edge-cycle drilling, subset practice, Giiker-aware flow, and high-skill BLD-oriented practice patterns rather than as a separate platform lane.",memo,False,True,0.0,2.0,HT_training_stack,HT_training_stack_0006,cubing / algorithm training,Integrate primarily for HyperTwist. Its memo and bookmark signals place it in the cubing / algorithm training layer.,HyperTwist,cubing / algorithm training,integrate,direct,medium,abunickabhi/5style-trainer,1.0,Donor Bench,5.0,"Focused advanced-training donor for 5-style and BLD-specific case packs, subset structures, and niche practice flow rather than a broader training-platform shell.",Focused advanced-training donor,Included,P2,"abunickabhi/5style-Trainer is placed in Donor Bench for HyperTwist because it best serves the 'Focused advanced-training donor' role; recommended action is 'repurpose' with repurposing scope 'moderate modification'. Confidence is medium because this remains a metadata-level judgment until source audit confirms hidden modules, plugin points, adapters, or architectural strengths.",2.0,3.0,3.0,11898.0,122.0,,abunickabhi/5style-trainer,HyperTwist,,,,,,,,,,Original global Phase G v4 retained,MIT,known_from_reference_material,uploaded_reference_docs,no,,,,Supplemental intake references are advisory only; v6 adjudication remains the source of truth.,Usually indirect,yes,v6 unified all-project source-of-truth pack,v5_carry_forward,,v6_unified_source_of_truth_pack,18.0,3,5.0,118.0,permissive_or_noncopyleft_known,direct_incorporation_ok,"This repo is aligned with a direct integration path for HyperTwist because it is either already implemented, strategically central, or donor-grade without a visible copyleft constraint in the current materials. Deep incorporation is sensible if the source audit confirms architectural cleanliness.","Direct embed, vendored module, package dependency, or tightly integrated adapter as the architecture requires.","Typically preserve notices, attribution, and license text where required; no special copyleft-driven disclosure posture is normally needed.",Usually unnecessary unless you later decide the existing implementation is too constraining architecturally.,high,strategic-or-implemented-component,yes,,,,,,,,,,,,,v6.3_final_source_of_truth,Normalized legacy merge-bench wording to dossier-backed focused advanced-training donor posture on 2026-04-25.,implemented_live_permissive,landed_permissive_preserve,Phase 1R closed. Preserve as a landed first-party permissive lane; keep notices and attribution visible and widen only through ordinary owned enhancement work. 18.0,MathewKJ2048/Rubiks-cube-simulator,https://github.com/MathewKJ2048/Rubiks-cube-simulator,HyperTwist,19.0,118.0,133.0,B,clean-room simulator benchmark,benchmark,Clean-room simulator benchmark,Reserve Bench,future candidate,architecture only,"Retain the valuable internal engine, but expect to replace UI/product shell, adapt schemas/APIs, and refactor boundaries so it can plug into the target anchors cleanly. For this repo class, that usually means preserving cube-state, scramble, scheduling, or timer internals while adapting pedagogy, analytics, and UI.","Benchmark-only retained value: lightweight simulator flow, text-command grammar, move-history UX, and timed step-playback behavior suitable for first-party clean-room reimplementation.",Keep only as a clean-room benchmark. Use it to shape lightweight simulator behavior; do not incorporate source.,Do not treat this repo as a merge candidate. Convert useful simulator behaviors into a scrubbed Model A spec only.,Repurpose here means: derive first-party lightweight simulator behavior through a clean-room process.,Map module boundaries; Identify hidden reusable internals; Define adapter/API boundary to target anchors; Write extraction tests against upstream behavior; Extract cube-state model; Normalize trainer/case schema; Expose analytics and replay hooks,clean-room benchmark review,"Hidden value sits in text-command grammar, move-history logging, and timed step playback.",Which lightweight simulator behaviors are worth preserving through a scrubbed Model A handoff?,"Inspect command grammar, move-history handling, beginner-solver flow, and timed step playback as clean-room benchmark material only.",Audit MathewKJ2048/Rubiks-cube-simulator only as a clean-room simulator benchmark. Extract behaviors into a scrubbed spec; do not recommend direct source incorporation.,tao-yu/Alg-Trainer,base + donor swarm,Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.,poliva/cubedex,specialized training UX donor,Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.,Lykos/cube_trainer,sampling/analytics donor,Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.,Reference only,"Retain only as benchmark, oracle, acceptance-test, or clean-room planning input.",exclude from donor lane,The repo is GPL simulator code and should remain only as a low-priority clean-room simulator benchmark.,high,The dossier-backed classification is stable: retain only the lightweight simulator behaviors through a clean-room path.,high,The dossier-backed classification is stable: retain only the lightweight simulator behaviors through a clean-room path.,"Licensing intentionally ignored as a decision filter in this canonical evaluation; assess only architecture, capability, donor value, and concept transfer.",,,,MathewKJ2048/Rubiks-cube-simulator — GPL-3.0 simulator; keep only as a clean-room simulator benchmark.,"MathewKJ2048/Rubiks-cube-simulator is retained only as a clean-room simulator benchmark. Its value is in small simulator behaviors, not donor code.",memo,False,True,0.0,2.0,HT_training_clean_room,HT_training_clean_room_0004,Clean-room simulator benchmark,Clean-room simulator benchmark for HyperTwist; retained for behavior extraction only.,HyperTwist,Clean-room simulator benchmark,future candidate,architecture only,medium,mathewkj2048/rubiks-cube-simulator,1.0,Reserve Bench,5.0,GPL simulator with narrow lightweight-behavior value; retain only as clean-room benchmark material.,Clean-room simulator benchmark,Included,P3,Keep in canon only as a low-priority clean-room simulator benchmark for lightweight simulator behaviors.,2.0,3.0,3.0,11901.0,123.0,,mathewkj2048/rubiks-cube-simulator,HyperTwist,,,,,,,,,,Original global Phase G v4 retained,GPL-3.0,known_from_reference_material,uploaded_reference_docs,no,,,,Supplemental intake references are advisory only; v6 adjudication remains the source of truth.,Usually indirect,yes,v6 unified all-project source-of-truth pack,v5_carry_forward,,v6_unified_source_of_truth_pack,19.0,3,5.0,118.0,mixed_or_boundary_sensitive_known,pattern_only_preferred,"The repo is GPL simulator code and was discarded from the active retained set as an inferior duplicate of stronger pedagogy, planner, and history benchmarks.",Reference only: discarded historical comparison context for simulator pedagogy and history flow; do not plan direct incorporation.,Direct incorporation would require GPL-compatible distribution/compliance and is not the planned HyperTwist path.,Yes — this is the preferred path if lightweight simulator behavior later proves strategically necessary.,high,gpl-clean-room-benchmark,no,,,,,,,,,,,,,v6.3_final_source_of_truth,Corrected on 2026-04-25 from stale donor posture to dossier-backed clean-room simulator benchmark status.,not_live_reference_or_discard_candidate,phase0r_reference_benchmark_or_discard_eval,"Packet 0R-E closed. Discard from the active retained set as an inferior duplicate of stronger pedagogy, planner, and history benchmarks." -19.0,NuiLab/code-vr,https://github.com/NuiLab/code-vr,HyperTwist,20.0,118.0,133.0,B,vision / perception / AR,subsystem donor,vision donor,donor bench,repurpose,moderate modification,"Retain the valuable internal engine, but expect to replace UI/product shell, adapt schemas/APIs, and refactor boundaries so it can plug into the target anchors cleanly. For this repo class, that usually means preserving calibration/detection/state-reconstruction logic while replacing camera UX and integration surfaces.","NuiLab/code-vr — (license permissive per repo) — VR codebase explorer. | poliva/cubedex, tao-yu/Alg-Trainer, kkoomen/qbr, vivaansinghvi07/rubix-cube-solver, NuiLab/code-vr, molgenis/Graph2VR (core permissive parts), brianpeiris/RiftSketc...","Integrate as a cubing / algorithm training subsystem for HyperTwist. Preserve the strongest existing pieces — scramble generation, algorithm database, recognition/training loop, timing/statistics, virtual cube, smartcube hooks, spaced repetition — and expose them behind a portfolio-stable interface. Wire first into tao-yu/Alg-Trainer, then into poliva/cubedex for orchestration, visualization, or data exchange.","Consolidate under the Hyperspeedcube + cubing.js + qbr nucleus, not beside it as a separate silo. Normalize data contracts, auth/permissions, storage, and telemetry; then attach as a service, plugin, canvas layer, trainer, or analysis module. Descending combination order: tao-yu/Alg-Trainer, poliva/cubedex, Lykos/cube_trainer.","Repurpose here means: turn it into a trainer engine, solver/timer backend, recognition drill module, or method-specific practice mode for HyperTwist.",Map module boundaries; Identify hidden reusable internals; Define adapter/API boundary to target anchors; Write extraction tests against upstream behavior; Benchmark calibration pipeline; Extract state reconstruction; Wrap with camera/AR adapter,deep source audit,"Hidden value often sits in calibration, preprocessing, stabilization, object/state reconstruction, replay artifacts, and camera-to-domain state pipelines that are not obvious from demos.",Inspect preprocessing/calibration; tracking stabilization; state reconstruction; replay/event model; camera abstraction; fallback heuristics; testing assets/videos; performance shortcuts.,"Inspect package manifests, README/docs, src tree, examples, tests, CI workflows, config files, migrations/schemas, and hidden feature flags or experimental modules. Look for algorithm databases, spaced-repetition logic, scramble generation, timer/stat code, virtual cube components, smartcube adapters, and custom-trainer configuration support.","Audit NuiLab/code-vr as a vision / perception / AR candidate for HyperTwist. Do not stop at README-level features. Inspect: Inspect preprocessing/calibration; tracking stabilization; state reconstruction; replay/event model; camera abstraction; fallback heuristics; testing assets/videos; performance shortcuts. Decide whether the best extraction path is moderate modification and whether it belongs as subsystem donor / vision donor. Test the three merger paths in order: 1) kkoomen/qbr [foundation + perception donor]; 2) vivaansinghvi07/rubix-cube-solver [perception + replay donor]; 3) cubing/cubing.js [state/render backend]. Return hidden modules, reusable schemas, protocol layers, plugin hooks, render/state models, datasets/test fixtures, and any subsystem stronger than the visible product shell.",kkoomen/qbr,foundation + perception donor,"Use this repo against the partner as an augmenting layer; preserve the partner as the likely base and mine this repo for capabilities that improve breadth, UX, or specialization.",vivaansinghvi07/rubix-cube-solver,perception + replay donor,Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.,cubing/cubing.js,state/render backend,Use the partner for canonical state or rendering abstractions and merge this repo's specialized logic on top.,VectorShell | ScriptoriumAI,VectorShell can borrow spatial/rendering and perception primitives; ScriptoriumAI can borrow tutorial/educational visualization patterns rather than the full engine.,exclude from standalone? no,"Not necessarily the final base, but keep as an active subsystem candidate or major donor.",medium,single-source signal; clear taxonomy; active integration value,medium,memo mentions: 2,"Licensing intentionally ignored as a decision filter in this canonical evaluation; assess only architecture, capability, donor value, and concept transfer.",,,,"NuiLab/code-vr — (license permissive per repo) — VR codebase explorer. | poliva/cubedex, tao-yu/Alg-Trainer, kkoomen/qbr, vivaansinghvi07/rubix-cube-solver, NuiLab/code-vr, molgenis/Graph2VR (core permissive parts), brianpeiris/RiftSketch, aMonteSl/CodeXR.",NuiLab/code-vr is treated as repurpose for HyperTwist because the current dossier keeps it below core tier as an XR pedagogy and code-to-scene representation donor rather than as an active merge-set candidate or product shell.,memo,False,True,0.0,2.0,HT_cube_vision,HT_cube_vision_0007,cubing / algorithm training,Integrate as a shared building block across at least two projects. Its memo and bookmark signals place it in the computer vision / AR layer.,multi-project,computer vision / AR,integrate,heavy modification,medium,nuilab/code-vr,1.0,Donor Bench,5.0,"MIT XR pedagogy repo with interesting teaching and code-to-scene patterns, but too under-construction and off-domain to justify merge-bench treatment.",XR pedagogy and code-to-scene representation donor,Included,P2,Keep below core tier as an XR pedagogy and code-to-scene representation donor; the teaching frame and app/service split matter more than the under-construction product shell.,2.0,3.0,3.0,11904.0,3228.0,,nuilab/code-vr,HyperTwist,,,,,,,,,,Original global Phase G v4 retained,MIT,known_from_reference_material,uploaded_reference_docs,no,,,,Supplemental intake references are advisory only; v6 adjudication remains the source of truth.,Potentially relevant,yes,v6 unified all-project source-of-truth pack,v5_carry_forward,,v6_unified_source_of_truth_pack,20.0,3,5.0,118.0,permissive_or_noncopyleft_known,direct_incorporation_ok,"The repo is MIT and direct use is legally straightforward, but the current HyperTwist posture is still below-core donor use because the strongest value is in XR pedagogy, embodied onboarding, and code-to-scene boundary ideas rather than product-core ownership.",Use selectively as a donor or bounded adapter where the XR pedagogy and code-to-scene representation ideas materially shorten build time.,Preserve MIT notices and attribution where required.,Usually unnecessary unless later replacing a narrow implementation seam is architecturally cleaner than carrying the upstream code.,high,below-core-mit-donor,yes,,,,,,,,,,,,,v6.3_final_source_of_truth,Corrected on 2026-04-25 from stale merge-bench posture to dossier-backed below-core XR pedagogy donor status.,selected_not_live_permissive_candidate,phase0r_permissive_eval_then_implement,"Phase 1R closed. Retain as a Phase 3R permissive implementation candidate; implement only from its packet authority and the retained-set contract, not by reopening Phase 0R." +19.0,NuiLab/code-vr,https://github.com/NuiLab/code-vr,HyperTwist,20.0,118.0,133.0,B,vision / perception / AR,subsystem donor,vision donor,donor bench,repurpose,moderate modification,"Retain the valuable internal engine, but expect to replace UI/product shell, adapt schemas/APIs, and refactor boundaries so it can plug into the target anchors cleanly. For this repo class, that usually means preserving calibration/detection/state-reconstruction logic while replacing camera UX and integration surfaces.","NuiLab/code-vr — (license permissive per repo) — VR codebase explorer. | poliva/cubedex, tao-yu/Alg-Trainer, kkoomen/qbr, vivaansinghvi07/rubix-cube-solver, NuiLab/code-vr, molgenis/Graph2VR (core permissive parts), brianpeiris/RiftSketc...","Integrate as a cubing / algorithm training subsystem for HyperTwist. Preserve the strongest existing pieces — scramble generation, algorithm database, recognition/training loop, timing/statistics, virtual cube, smartcube hooks, spaced repetition — and expose them behind a portfolio-stable interface. Wire first into tao-yu/Alg-Trainer, then into poliva/cubedex for orchestration, visualization, or data exchange.","Consolidate under the Hyperspeedcube + cubing.js + qbr nucleus, not beside it as a separate silo. Normalize data contracts, auth/permissions, storage, and telemetry; then attach as a service, plugin, canvas layer, trainer, or analysis module. Descending combination order: tao-yu/Alg-Trainer, poliva/cubedex, Lykos/cube_trainer.","Repurpose here means: turn it into a trainer engine, solver/timer backend, recognition drill module, or method-specific practice mode for HyperTwist.",Map module boundaries; Identify hidden reusable internals; Define adapter/API boundary to target anchors; Write extraction tests against upstream behavior; Benchmark calibration pipeline; Extract state reconstruction; Wrap with camera/AR adapter,deep source audit,"Hidden value often sits in calibration, preprocessing, stabilization, object/state reconstruction, replay artifacts, and camera-to-domain state pipelines that are not obvious from demos.",Inspect preprocessing/calibration; tracking stabilization; state reconstruction; replay/event model; camera abstraction; fallback heuristics; testing assets/videos; performance shortcuts.,"Inspect package manifests, README/docs, src tree, examples, tests, CI workflows, config files, migrations/schemas, and hidden feature flags or experimental modules. Look for algorithm databases, spaced-repetition logic, scramble generation, timer/stat code, virtual cube components, smartcube adapters, and custom-trainer configuration support.","Audit NuiLab/code-vr as a vision / perception / AR candidate for HyperTwist. Do not stop at README-level features. Inspect: Inspect preprocessing/calibration; tracking stabilization; state reconstruction; replay/event model; camera abstraction; fallback heuristics; testing assets/videos; performance shortcuts. Decide whether the best extraction path is moderate modification and whether it belongs as subsystem donor / vision donor. Test the three merger paths in order: 1) kkoomen/qbr [foundation + perception donor]; 2) vivaansinghvi07/rubix-cube-solver [perception + replay donor]; 3) cubing/cubing.js [state/render backend]. Return hidden modules, reusable schemas, protocol layers, plugin hooks, render/state models, datasets/test fixtures, and any subsystem stronger than the visible product shell.",kkoomen/qbr,foundation + perception donor,"Use this repo against the partner as an augmenting layer; preserve the partner as the likely base and mine this repo for capabilities that improve breadth, UX, or specialization.",vivaansinghvi07/rubix-cube-solver,perception + replay donor,Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.,cubing/cubing.js,state/render backend,Use the partner for canonical state or rendering abstractions and merge this repo's specialized logic on top.,VectorShell | ScriptoriumAI,VectorShell can borrow spatial/rendering and perception primitives; ScriptoriumAI can borrow tutorial/educational visualization patterns rather than the full engine.,exclude from standalone? no,"Not necessarily the final base, but keep as an active subsystem candidate or major donor.",medium,single-source signal; clear taxonomy; active integration value,medium,memo mentions: 2,"Licensing intentionally ignored as a decision filter in this canonical evaluation; assess only architecture, capability, donor value, and concept transfer.",,,,"NuiLab/code-vr — (license permissive per repo) — VR codebase explorer. | poliva/cubedex, tao-yu/Alg-Trainer, kkoomen/qbr, vivaansinghvi07/rubix-cube-solver, NuiLab/code-vr, molgenis/Graph2VR (core permissive parts), brianpeiris/RiftSketch, aMonteSl/CodeXR.",NuiLab/code-vr is treated as repurpose for HyperTwist because the current dossier keeps it below core tier as an XR pedagogy and code-to-scene representation donor rather than as an active merge-set candidate or product shell.,memo,False,True,0.0,2.0,HT_cube_vision,HT_cube_vision_0007,cubing / algorithm training,Integrate as a shared building block across at least two projects. Its memo and bookmark signals place it in the computer vision / AR layer.,multi-project,computer vision / AR,integrate,heavy modification,medium,nuilab/code-vr,1.0,Donor Bench,5.0,"MIT XR pedagogy repo with interesting teaching and code-to-scene patterns, but too under-construction and off-domain to justify merge-bench treatment.",XR pedagogy and code-to-scene representation donor,Included,P2,Keep below core tier as an XR pedagogy and code-to-scene representation donor; the teaching frame and app/service split matter more than the under-construction product shell.,2.0,3.0,3.0,11904.0,3228.0,,nuilab/code-vr,HyperTwist,,,,,,,,,,Original global Phase G v4 retained,MIT,known_from_reference_material,uploaded_reference_docs,no,,,,Supplemental intake references are advisory only; v6 adjudication remains the source of truth.,Potentially relevant,yes,v6 unified all-project source-of-truth pack,v5_carry_forward,,v6_unified_source_of_truth_pack,20.0,3,5.0,118.0,permissive_or_noncopyleft_known,direct_incorporation_ok,"The repo is MIT and direct use is legally straightforward, but the current HyperTwist posture is still below-core donor use because the strongest value is in XR pedagogy, embodied onboarding, and code-to-scene boundary ideas rather than product-core ownership.",Use selectively as a donor or bounded adapter where the XR pedagogy and code-to-scene representation ideas materially shorten build time.,Preserve MIT notices and attribution where required.,Usually unnecessary unless later replacing a narrow implementation seam is architecturally cleaner than carrying the upstream code.,high,below-core-mit-donor,yes,,,,,,,,,,,,,v6.3_final_source_of_truth,Corrected on 2026-04-25 from stale merge-bench posture to dossier-backed below-core XR pedagogy donor status.,implemented_live_permissive,landed_permissive_preserve,"Phase 3R-E closed. Preserve as the landed first-party embodied companion, narration, lip-sync, gesture, subtitle, and avatar-embed lane; start future widening from the live-lane audit, then the 3R-E implementation packet, then REPO_LICENSE_TRACKING.md." 20.0,ShellPuppy/RCube,https://github.com/ShellPuppy/RCube,HyperTwist,21.0,118.0,133.0,B,large-N solver benchmark,benchmark,Large-N solver benchmark,Reserve Bench,future candidate,architecture only,"Retain the valuable internal engine, but expect to replace UI/product shell, adapt schemas/APIs, and refactor boundaries so it can plug into the target anchors cleanly. For this repo class, that usually means preserving cube-state, scramble, scheduling, or timer internals while adapting pedagogy, analytics, and UI.","Benchmark-only retained value: large-N orientation tricks, stage framing, and big-cube algorithm expectations. Study the algorithm/reference behavior only.","Keep as a restrictive large-N solver benchmark. Use it for algorithm/reference comparison, not as donor code.",Do not treat this repo as a merge candidate. Translate only large-cube orientation and stage-framing ideas into first-party work if later needed.,Repurpose here means: use as an algorithm/reference benchmark for large-cube state and orientation tricks.,Map module boundaries; Identify hidden reusable internals; Define adapter/API boundary to target anchors; Write extraction tests against upstream behavior; Extract cube-state model; Normalize trainer/case schema; Expose analytics and replay hooks,algorithm benchmark review,Hidden value sits in orientation shortcuts and stage framing for extremely large cubes.,Which large-cube orientation and stage strategies are worth preserving as benchmark knowledge?,"Inspect large-cube orientation logic, stage structure, and output/reporting surfaces as benchmark material only.","Audit ShellPuppy/RCube only as a restrictive large-N solver benchmark. Extract algorithm ideas and acceptance-test expectations, not donor code.",tao-yu/Alg-Trainer,base + donor swarm,Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.,poliva/cubedex,specialized training UX donor,Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.,Lykos/cube_trainer,sampling/analytics donor,Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.,Reference only,"Retain only as benchmark, oracle, acceptance-test, or clean-room planning input.",exclude from donor lane,The repo is GPL large-N solver code and should remain only as an algorithm/reference benchmark for big-cube behavior.,high,Dossier-backed classification is stable: the retained value is algorithm/reference benchmarking for large-N cubes.,high,Dossier-backed classification is stable: the retained value is algorithm/reference benchmarking for large-N cubes.,"Licensing intentionally ignored as a decision filter in this canonical evaluation; assess only architecture, capability, donor value, and concept transfer.",,,,ShellPuppy/RCube — GPL large-N cube solver; keep only as a large-N solver benchmark.,ShellPuppy/RCube remains useful only because it captures a narrow large-N solver lane that HyperTwist may later benchmark against. It is not a donor candidate.,memo,False,True,0.0,2.0,HT_solver_oracles,HT_solver_oracles_0001,Large-N solver benchmark,"Large-N solver benchmark for HyperTwist; retained for reference value, not donor use.",HyperTwist,Large-N solver benchmark,future candidate,architecture only,medium,shellpuppy/rcube,1.0,Reserve Bench,5.0,GPL large-N solver with narrow algorithm/reference value and no donor-case for the HyperTwist product core.,Large-N solver benchmark,Included,P3,Keep in canon only as a restrictive benchmark for large-N state/orientation techniques.,2.0,3.0,3.0,11907.0,124.0,,shellpuppy/rcube,HyperTwist,,,,,,,,,,Original global Phase G v4 retained,GPL-3.0,known_from_reference_material,uploaded_reference_docs,no,,,,Supplemental intake references are advisory only; v6 adjudication remains the source of truth.,Usually indirect,yes,v6 unified all-project source-of-truth pack,v5_carry_forward,,v6_unified_source_of_truth_pack,21.0,3,5.0,118.0,mixed_or_boundary_sensitive_known,pattern_only_preferred,"The repo is GPL large-N solver code and remains a benchmark/reference lane for centers, edges, parity, and later clean-room research rather than donor use.","Reference only: use as a large-N centers, edges, and parity benchmark without direct source incorporation.",Direct incorporation would require GPL-compatible distribution/compliance and is not the planned HyperTwist path.,Only if a later first-party large-N lane needs recreation of a narrow behavior or algorithmic framing; otherwise keep this as a benchmark.,high,gpl-large-n-benchmark,no,,,,,,,,,,,,,v6.3_final_source_of_truth,Corrected on 2026-04-25 from stale donor posture to dossier-backed large-N solver benchmark status.,not_live_reference_or_discard_candidate,phase0r_reference_benchmark_or_discard_eval,"Packet 0R-E closed. Retain as a large-N centers/edges/parity benchmark and later clean-room research input, not as an active product donor." 22.0,brownan/Rubiks-Cube-Solver,https://github.com/brownan/Rubiks-Cube-Solver,HyperTwist,22.0,118.0,133.0,B,cubing trainer / solver / timing,subsystem donor,training donor,Reserve Bench,future candidate,architecture only,"Retain the valuable internal engine, but expect to replace UI/product shell, adapt schemas/APIs, and refactor boundaries so it can plug into the target anchors cleanly. For this repo class, that usually means preserving cube-state, scramble, scheduling, or timer internals while adapting pedagogy, analytics, and UI.",brownan/Rubiks-Cube-Solver — GPL-3.0 — Optimal pattern-database solver. | brownan/Rubiks-Cube-Solver — GPL-3.0.,"Integrate as a cubing / algorithm training subsystem for HyperTwist. Preserve the strongest existing pieces — scramble generation, algorithm database, recognition/training loop, timing/statistics, virtual cube, smartcube hooks, spaced repetition — and expose them behind a portfolio-stable interface. Wire first into tao-yu/Alg-Trainer, then into poliva/cubedex for orchestration, visualization, or data exchange.","Consolidate under the Hyperspeedcube + cubing.js + qbr nucleus, not beside it as a separate silo. Normalize data contracts, auth/permissions, storage, and telemetry; then attach as a service, plugin, canvas layer, trainer, or analysis module. Descending combination order: tao-yu/Alg-Trainer, poliva/cubedex, Lykos/cube_trainer.","Repurpose here means: turn it into a trainer engine, solver/timer backend, recognition drill module, or method-specific practice mode for HyperTwist.",Map module boundaries; Identify hidden reusable internals; Define adapter/API boundary to target anchors; Write extraction tests against upstream behavior; Extract cube-state model; Normalize trainer/case schema; Expose analytics and replay hooks,deep source audit,"Hidden value often sits in cube-state representation, scramble generation, weighted drill scheduling, recognition datasets, replay/timer internals, and case database schemas.",Inspect cube-state model; scramble generator; trainer weighting/scheduling; case database and metadata; replay/timer model; import/export of alg sets; smartcube or sensor adapters.,"Inspect package manifests, README/docs, src tree, examples, tests, CI workflows, config files, migrations/schemas, and hidden feature flags or experimental modules. Look for algorithm databases, spaced-repetition logic, scramble generation, timer/stat code, virtual cube components, smartcube adapters, and custom-trainer configuration support.","Audit brownan/Rubiks-Cube-Solver as a cubing trainer / solver / timing candidate for HyperTwist. Do not stop at README-level features. Inspect: Inspect cube-state model; scramble generator; trainer weighting/scheduling; case database and metadata; replay/timer model; import/export of alg sets; smartcube or sensor adapters. Decide whether the best extraction path is moderate modification and whether it belongs as subsystem donor / training donor. Test the three merger paths in order: 1) tao-yu/Alg-Trainer [base + donor swarm]; 2) poliva/cubedex [specialized training UX donor]; 3) Lykos/cube_trainer [sampling/analytics donor]. Return hidden modules, reusable schemas, protocol layers, plugin hooks, render/state models, datasets/test fixtures, and any subsystem stronger than the visible product shell.",tao-yu/Alg-Trainer,base + donor swarm,Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.,poliva/cubedex,specialized training UX donor,Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.,Lykos/cube_trainer,sampling/analytics donor,Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.,project-local first,"Cross-project transfer is possible, but the value is clearest inside the assigned project until source audit exposes more reusable primitives.",exclude from standalone? no,"Not necessarily the final base, but keep as an active subsystem candidate or major donor.",medium,single-source signal; clear taxonomy; active integration value,medium,memo mentions: 2,"Licensing intentionally ignored as a decision filter in this canonical evaluation; assess only architecture, capability, donor value, and concept transfer.",,,,brownan/Rubiks-Cube-Solver — GPL-3.0 — Optimal pattern-database solver. | brownan/Rubiks-Cube-Solver — GPL-3.0.,brownan/Rubiks-Cube-Solver is treated as a future candidate for HyperTwist because the current dossier keeps it as a benchmark oracle and later clean-room optimal-solver target rather than as a direct donor.,memo,False,True,0.0,2.0,HT_training_stack,HT_training_stack_0007,cubing / algorithm training,Integrate primarily for HyperTwist. Its memo and bookmark signals place it in the cubing / algorithm training layer.,HyperTwist,cubing / algorithm training,integrate,moderate modification,medium,brownan/rubiks-cube-solver,1.0,Reserve Bench,5.0,GPL solver/oracle repo whose retained value is correctness/oracle behavior plus a later clean-room optimal-solver lane.,Benchmark oracle and clean-room optimal-solver candidate,Included,P2,Keep as a primary benchmark oracle and secondary clean-room optimal-solver candidate; the dossier-backed GPL posture blocks donor treatment but not benchmark/oracle and Model A value.,2.0,3.0,3.0,11910.0,125.0,,brownan/rubiks-cube-solver,HyperTwist,,,,,,,,,,Original global Phase G v4 retained,GPL-3.0,known_from_reference_material,uploaded_reference_docs,no,,,,Supplemental intake references are advisory only; v6 adjudication remains the source of truth.,Usually indirect,yes,v6 unified all-project source-of-truth pack,v5_carry_forward,,v6_unified_source_of_truth_pack,22.0,3,5.0,118.0,mixed_or_boundary_sensitive_known,reverse_engineer_preferred,The repo is GPL-3.0 and remains the primary compact solver oracle and clean-room-later heuristic/search benchmark. Preserve correctness and search behavior through scrubbed first-party specifications only.,Use as an oracle and Model A source only; Model B should implement any solver work from a scrubbed first-party specification.,Direct incorporation would require GPL-compatible distribution/compliance and is not the planned HyperTwist path.,Yes — this is the preferred path for any later first-party optimal-solver effort.,high,gpl-oracle-clean-room-review,no,,,,,,,,,,,,,v6.3_final_source_of_truth,Corrected on 2026-04-25 from stale unknown-license merge-bench posture to dossier-backed benchmark-oracle and clean-room optimal-solver status.,not_live_reference_or_discard_candidate,phase0r_reference_benchmark_or_discard_eval,"Packet 0R-E closed. Retain as the primary compact solver oracle and clean-room-later heuristic/search benchmark; use for correctness, not donor code." 24.0,newyork-anthonyng/rubiks-cross-trainer,https://github.com/newyork-anthonyng/rubiks-cross-trainer,HyperTwist,24.0,118.0,133.0,B,cubing trainer / solver / timing,subsystem donor,training donor,donor bench,repurpose,moderate modification,"Retain the valuable internal engine, but expect to replace UI/product shell, adapt schemas/APIs, and refactor boundaries so it can plug into the target anchors cleanly. For this repo class, that usually means preserving cube-state, scramble, scheduling, or timer internals while adapting pedagogy, analytics, and UI.",newyork-anthonyng/rubiks-cross-trainer — MIT — Cross trainer library (scramble generator). | newyork-anthonyng/rubiks-cross-trainer — MIT.,"Integrate as a cubing / algorithm training subsystem for HyperTwist. Preserve the strongest existing pieces — scramble generation, algorithm database, recognition/training loop, timing/statistics, virtual cube, smartcube hooks, spaced repetition — and expose them behind a portfolio-stable interface. Wire first into tao-yu/Alg-Trainer, then into poliva/cubedex for orchestration, visualization, or data exchange.","Consolidate under the Hyperspeedcube + cubing.js + qbr nucleus, not beside it as a separate silo. Normalize data contracts, auth/permissions, storage, and telemetry; then attach as a service, plugin, canvas layer, trainer, or analysis module. Descending combination order: tao-yu/Alg-Trainer, poliva/cubedex, Lykos/cube_trainer.","Repurpose here means: turn it into a trainer engine, solver/timer backend, recognition drill module, or method-specific practice mode for HyperTwist.",Map module boundaries; Identify hidden reusable internals; Define adapter/API boundary to target anchors; Write extraction tests against upstream behavior; Extract cube-state model; Normalize trainer/case schema; Expose analytics and replay hooks,deep source audit,"Hidden value often sits in cube-state representation, scramble generation, weighted drill scheduling, recognition datasets, replay/timer internals, and case database schemas.",Inspect cube-state model; scramble generator; trainer weighting/scheduling; case database and metadata; replay/timer model; import/export of alg sets; smartcube or sensor adapters.,"Inspect package manifests, README/docs, src tree, examples, tests, CI workflows, config files, migrations/schemas, and hidden feature flags or experimental modules. Look for algorithm databases, spaced-repetition logic, scramble generation, timer/stat code, virtual cube components, smartcube adapters, and custom-trainer configuration support.","Audit newyork-anthonyng/rubiks-cross-trainer as a cubing trainer / solver / timing candidate for HyperTwist. Do not stop at README-level features. Inspect: Inspect cube-state model; scramble generator; trainer weighting/scheduling; case database and metadata; replay/timer model; import/export of alg sets; smartcube or sensor adapters. Decide whether the best extraction path is moderate modification and whether it belongs as subsystem donor / training donor. Test the three merger paths in order: 1) tao-yu/Alg-Trainer [base + donor swarm]; 2) poliva/cubedex [specialized training UX donor]; 3) Lykos/cube_trainer [sampling/analytics donor]. Return hidden modules, reusable schemas, protocol layers, plugin hooks, render/state models, datasets/test fixtures, and any subsystem stronger than the visible product shell.",tao-yu/Alg-Trainer,base + donor swarm,Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.,poliva/cubedex,specialized training UX donor,Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.,Lykos/cube_trainer,sampling/analytics donor,Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.,project-local first,"Cross-project transfer is possible, but the value is clearest inside the assigned project until source audit exposes more reusable primitives.",exclude from standalone? no,"Not necessarily the final base, but keep as an active subsystem candidate or major donor.",medium,single-source signal; clear taxonomy; active integration value,medium,memo mentions: 2,"Licensing intentionally ignored as a decision filter in this canonical evaluation; assess only architecture, capability, donor value, and concept transfer.",,,,newyork-anthonyng/rubiks-cross-trainer — MIT — Cross trainer library (scramble generator). | newyork-anthonyng/rubiks-cross-trainer — MIT.,newyork-anthonyng/rubiks-cross-trainer is treated as repurpose for HyperTwist because the current dossier keeps it as a focused donor for its precomputed one-to-eight-move cross corpus and cross-specific drill progression rather than as a platform lane.,memo,False,True,0.0,2.0,HT_training_stack,HT_training_stack_0008,cubing / algorithm training,Integrate primarily for HyperTwist. Its memo and bookmark signals place it in the cubing / algorithm training layer.,HyperTwist,cubing / algorithm training,integrate,moderate modification,medium,newyork-anthonyng/rubiks-cross-trainer,1.0,Donor Bench,5.0,Focused donor for the precomputed cross-difficulty corpus and CFOP micro-drill progression rather than a broader training-platform shell.,Focused donor,Included,P2,"newyork-anthonyng/rubiks-cross-trainer is placed in Donor Bench for HyperTwist because it best serves the 'Focused donor' role; recommended action is 'repurpose' with repurposing scope 'moderate modification'. Confidence is medium because this remains a metadata-level judgment until source audit confirms hidden modules, plugin points, adapters, or architectural strengths.",2.0,3.0,3.0,11916.0,126.0,,newyork-anthonyng/rubiks-cross-trainer,HyperTwist,,,,,,,,,,Original global Phase G v4 retained,MIT,known_from_reference_material,uploaded_reference_docs,no,,,,Supplemental intake references are advisory only; v6 adjudication remains the source of truth.,Usually indirect,yes,v6 unified all-project source-of-truth pack,v5_carry_forward,,v6_unified_source_of_truth_pack,24.0,3,5.0,118.0,permissive_or_noncopyleft_known,direct_incorporation_ok,"This repo is aligned with a direct integration path for HyperTwist because it is either already implemented, strategically central, or donor-grade without a visible copyleft constraint in the current materials. Deep incorporation is sensible if the source audit confirms architectural cleanliness.","Direct embed, vendored module, package dependency, or tightly integrated adapter as the architecture requires.","Typically preserve notices, attribution, and license text where required; no special copyleft-driven disclosure posture is normally needed.",Usually unnecessary unless you later decide the existing implementation is too constraining architecturally.,high,strategic-or-implemented-component,yes,,,,,,,,,,,,,v6.3_final_source_of_truth,Normalized legacy merge-bench wording to dossier-backed focused-donor posture on 2026-04-25.,implemented_live_permissive,landed_permissive_preserve,Phase 1R closed. Preserve as a landed first-party permissive lane; keep notices and attribution visible and widen only through ordinary owned enhancement work. @@ -37,40 +37,40 @@ execution_queue_order,repo,primary_url,best_fit_project_v2,project_rank,portfoli 31.0,yakupbilen/drl-rubiks-cube,https://github.com/yakupbilen/drl-rubiks-cube,HyperTwist,31.0,117.0,132.0,B,vision / perception / AR,subsystem donor,vision donor,Reserve Bench,future candidate,architecture only,"Retain the valuable internal engine, but expect to replace UI/product shell, adapt schemas/APIs, and refactor boundaries so it can plug into the target anchors cleanly. For this repo class, that usually means preserving calibration/detection/state-reconstruction logic while replacing camera UX and integration surfaces.",yakupbilen/drl-rubiks-cube — MIT — RL solver with PyQt5 + webcam input.,"Integrate as a cubing / algorithm training subsystem for HyperTwist. Preserve the strongest existing pieces — scramble generation, algorithm database, recognition/training loop, timing/statistics, virtual cube, smartcube hooks, spaced repetition — and expose them behind a portfolio-stable interface. Wire first into tao-yu/Alg-Trainer, then into poliva/cubedex for orchestration, visualization, or data exchange.","Consolidate under the Hyperspeedcube + cubing.js + qbr nucleus, not beside it as a separate silo. Normalize data contracts, auth/permissions, storage, and telemetry; then attach as a service, plugin, canvas layer, trainer, or analysis module. Descending combination order: tao-yu/Alg-Trainer, poliva/cubedex, Lykos/cube_trainer.","Repurpose here means: turn it into a trainer engine, solver/timer backend, recognition drill module, or method-specific practice mode for HyperTwist.",Map module boundaries; Identify hidden reusable internals; Define adapter/API boundary to target anchors; Write extraction tests against upstream behavior; Benchmark calibration pipeline; Extract state reconstruction; Wrap with camera/AR adapter,deep source audit,"Hidden value often sits in calibration, preprocessing, stabilization, object/state reconstruction, replay artifacts, and camera-to-domain state pipelines that are not obvious from demos.",Inspect preprocessing/calibration; tracking stabilization; state reconstruction; replay/event model; camera abstraction; fallback heuristics; testing assets/videos; performance shortcuts.,"Inspect package manifests, README/docs, src tree, examples, tests, CI workflows, config files, migrations/schemas, and hidden feature flags or experimental modules. Look for algorithm databases, spaced-repetition logic, scramble generation, timer/stat code, virtual cube components, smartcube adapters, and custom-trainer configuration support.","Audit yakupbilen/drl-rubiks-cube as a vision / perception / AR candidate for HyperTwist. Do not stop at README-level features. Inspect: Inspect preprocessing/calibration; tracking stabilization; state reconstruction; replay/event model; camera abstraction; fallback heuristics; testing assets/videos; performance shortcuts. Decide whether the best extraction path is moderate modification and whether it belongs as subsystem donor / vision donor. Test the three merger paths in order: 1) kkoomen/qbr [foundation + perception donor]; 2) vivaansinghvi07/rubix-cube-solver [perception + replay donor]; 3) cubing/cubing.js [state/render backend]. Return hidden modules, reusable schemas, protocol layers, plugin hooks, render/state models, datasets/test fixtures, and any subsystem stronger than the visible product shell.",kkoomen/qbr,foundation + perception donor,"Use this repo against the partner as an augmenting layer; preserve the partner as the likely base and mine this repo for capabilities that improve breadth, UX, or specialization.",vivaansinghvi07/rubix-cube-solver,perception + replay donor,Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.,cubing/cubing.js,state/render backend,Use the partner for canonical state or rendering abstractions and merge this repo's specialized logic on top.,VectorShell | ScriptoriumAI,VectorShell can borrow spatial/rendering and perception primitives; ScriptoriumAI can borrow tutorial/educational visualization patterns rather than the full engine.,exclude from standalone? no,"Not necessarily the final base, but keep as an active subsystem candidate or major donor.",medium,single-source signal; clear taxonomy; active integration value,medium,memo mentions: 1,"Licensing intentionally ignored as a decision filter in this canonical evaluation; assess only architecture, capability, donor value, and concept transfer.",,,,yakupbilen/drl-rubiks-cube — MIT — RL solver with PyQt5 + webcam input.,"yakupbilen/drl-rubiks-cube is treated as a future candidate for HyperTwist because the current dossier retains it mainly for learned-heuristic search, batched A-star style experimentation, and training-loop ideas, not as part of the committed perception core.",memo,False,True,0.0,1.0,HT_cube_vision,HT_cube_vision_0008,cubing / algorithm training,Integrate primarily for HyperTwist. Its memo and bookmark signals place it in the cubing / algorithm training layer.,HyperTwist,cubing / algorithm training,integrate,moderate modification,medium,yakupbilen/drl-rubiks-cube,1.0,Reserve Bench,5.0,"Useful MIT search and training benchmark for learned-heuristic search, state generation, and experimentation loops, but explicitly below the committed perception and training core.",Search/training systems bench,Included,P2,"yakupbilen/drl-rubiks-cube is placed in Reserve Bench for HyperTwist because it best serves the 'Search/training systems bench' role; recommended action is 'future candidate' with repurposing scope 'architecture only'. Confidence is medium because this remains a metadata-level judgment until source audit confirms hidden modules, plugin points, adapters, or architectural strengths.",2.0,3.0,3.0,11937.0,133.0,,yakupbilen/drl-rubiks-cube,HyperTwist,,,,,,,,,,Original global Phase G v4 retained,MIT,known_from_reference_material,uploaded_reference_docs,no,,,,Supplemental intake references are advisory only; v6 adjudication remains the source of truth.,Usually indirect,yes,v6 unified all-project source-of-truth pack,v5_carry_forward,,v6_unified_source_of_truth_pack,31.0,3,5.0,117.0,permissive_or_noncopyleft_known,pattern_only_preferred,"The repo is MIT and remains a research benchmark for learned heuristic search, ADI state generation, and offline experimentation rather than a near-term product donor.",Reference only: benchmark learned heuristic search and training experiments without near-term direct incorporation.,"Typically preserve notices, attribution, and license text where required; no special copyleft-driven disclosure posture is normally needed.",Usually unnecessary unless you later decide the existing implementation is too constraining architecturally.,high,strategic-or-implemented-component,yes,,,,,,,,,,,,,v6.3_final_source_of_truth,Normalized legacy merge-bench wording to dossier-backed below-core benchmark posture on 2026-04-25.,not_live_reference_or_discard_candidate,phase0r_reference_benchmark_or_discard_eval,"Packet 0R-E closed. Retain as an MIT research benchmark for learned heuristic search, ADI training loops, and offline experimentation rather than near-term product implementation." 32.0,Hypercubers/hypercubing.xyz,https://github.com/Hypercubers/hypercubing.xyz,HyperTwist,32.0,92.0,101.0,C,hypercubing / nD engine,subsystem donor,simulation donor,locked strategic donor,repurpose,moderate modification,"Treat this as a mineable codebase: keep selected internals (algorithms, renderers, adapters, parsers, schedulers) while replacing the surrounding product assumptions and architecture. For this repo class, that usually means preserving generalized puzzle/state/render logic while building a new application shell around it.",Website for the Hypercubing community,"Repurpose selected subsystems rather than the whole product. Mine the repo for nD state model, move notation, renderer, projection controls, solver/traversal logic, puzzle serialization, replay; keep what materially shortens build time, but rebind data contracts, permissions, UI shell, storage, and deployment to the HyperTwist architecture. Best first pairing order: HactarCE/Hyperspeedcube, cubing/cubing.js, tao-yu/Alg-Trainer.","Consolidate under the Hyperspeedcube + cubing.js + qbr nucleus, not beside it as a separate silo. Normalize data contracts, auth/permissions, storage, and telemetry; then attach as a service, plugin, canvas layer, trainer, or analysis module. Descending combination order: HactarCE/Hyperspeedcube, cubing/cubing.js, tao-yu/Alg-Trainer.",Repurpose here means: turn it into a higher-dimensional renderer/simulator donor and shared interaction grammar for HyperTwist and long-horizon VectorShell.,Map module boundaries; Identify hidden reusable internals; Define adapter/API boundary to target anchors; Write extraction tests against upstream behavior; Isolate puzzle/state core; Extract render/input abstractions; Document notation and save format,deep source audit,"Hidden value is likely in generalized puzzle/state representations, higher-dimensional transforms, notation systems, save formats, puzzle generators, and rendering abstractions.",Inspect generalized puzzle/state model; notation parser; transform math; rendering abstraction; save/load format; puzzle generator; input mapping; performance optimizations.,"Inspect package manifests, README/docs, src tree, examples, tests, CI workflows, config files, migrations/schemas, and hidden feature flags or experimental modules. Look for higher-dimensional state/notation representations, projection math, renderer abstractions, puzzle serialization, controls, and replay/training hooks.","Audit Hypercubers/hypercubing.xyz as a hypercubing / nD engine candidate for HyperTwist. Do not stop at README-level features. Inspect: Inspect generalized puzzle/state model; notation parser; transform math; rendering abstraction; save/load format; puzzle generator; input mapping; performance optimizations. Decide whether the best extraction path is heavy modification and whether it belongs as subsystem donor / simulation donor. Test the three merger paths in order: 1) HactarCE/Hyperspeedcube [foundation + donor]; 2) cubing/cubing.js [3D engine + notation/state donor]; 3) tao-yu/Alg-Trainer [training UX donor]. Return hidden modules, reusable schemas, protocol layers, plugin hooks, render/state models, datasets/test fixtures, and any subsystem stronger than the visible product shell.",HactarCE/Hyperspeedcube,foundation + donor,"Use this repo against the partner as an augmenting layer; preserve the partner as the likely base and mine this repo for capabilities that improve breadth, UX, or specialization.",cubing/cubing.js,3D engine + notation/state donor,Use the partner for canonical state or rendering abstractions and merge this repo's specialized logic on top.,tao-yu/Alg-Trainer,training UX donor,Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.,VectorShell | ScriptoriumAI,VectorShell can borrow spatial/rendering and perception primitives; ScriptoriumAI can borrow tutorial/educational visualization patterns rather than the full engine.,"exclude from core, keep as donor","Do not let it consume roadmap as a full product shell; mine reusable engines, adapters, schemas, UX patterns, or datasets.",medium-low,single-source signal; clear taxonomy; mostly donor/reference role,medium,explicit bookmark description available,"Licensing intentionally ignored as a decision filter in this canonical evaluation; assess only architecture, capability, donor value, and concept transfer.",HyperTwist(1),HyperTwist Consider,Website for the Hypercubing community,,"Hypercubers/hypercubing.xyz is treated as repurpose for HyperTwist because visible metadata points to the hypercubing / nD simulation layer. Surface signal: Website for the Hypercubing community The fit looks real, but more as a donor/augmenter than as a standalone foundation.",bookmarks,True,False,1.0,0.0,HT_hyper_engine,HT_hyper_engine_0006,hypercubing / nD simulation,"Integrate primarily for HyperTwist. Its description and bookmark placement under ""HyperTwist Consider"" place it in the hypercubing / nD simulation layer.",HyperTwist,hypercubing / nD simulation,integrate,heavy modification,medium,hypercubers/hypercubing.xyz,1.0,Locked Strategic Donor,4.0,"MIT knowledge/curriculum donor with canonical notation, progression, taxonomy, and leaderboard-generation value.",Knowledge and curriculum donor,Included,P1,Keep as one of the strongest non-runtime donors in the hypercubing half of HyperTwist; the dossier-backed MIT posture and content value justify promotion above the old donor-bench treatment.,2.0,2.0,2.0,11938.0,134.0,Thin-fit assignment; verify project mapping during source audit,hypercubers/hypercubing.xyz,HyperTwist,,,,,,,,,,Original global Phase G v4 retained,MIT,known_from_reference_material,uploaded_reference_docs,no,,,,Supplemental intake references are advisory only; v6 adjudication remains the source of truth.,Usually indirect,yes,v6 unified all-project source-of-truth pack,v5_carry_forward,,v6_unified_source_of_truth_pack,32.0,3,4.0,92.0,permissive_or_noncopyleft_known,direct_incorporation_ok,The repo is MIT and is retained as a high-value knowledge and curriculum donor. Direct use of code/content structures is legally straightforward where it materially helps HyperTwist.,"Use selectively as a donor for knowledge structures, notation, taxonomy, and leaderboard-generation logic; do not confuse the site snapshot with the canonical repo.",Preserve MIT notices and attribution where required.,Usually unnecessary unless later replacing a narrow implementation seam is cleaner than carrying the upstream code.,high,permissive-knowledge-donor,yes,,,,,,,,,,,,,v6.3_final_source_of_truth,Corrected on 2026-04-25 from stale unknown-license donor-bench posture to dossier-backed MIT knowledge/curriculum donor status.,implemented_live_permissive,landed_permissive_preserve,"Phase 3R-B closed. Preserve as the landed first-party hypercubing knowledge, notation, progression, software-reference, and leaderboard-contract lane; start future widening from the live-lane audit, then the 3R-B implementation packet, then REPO_LICENSE_TRACKING.md." 34.0,Aarav2709/KubeTimr,https://github.com/Aarav2709/KubeTimr,HyperTwist,34.0,88.0,97.0,C,cubing trainer / solver / timing,subsystem donor,training donor,donor bench,repurpose,moderate modification,"Retain the valuable internal engine, but expect to replace UI/product shell, adapt schemas/APIs, and refactor boundaries so it can plug into the target anchors cleanly. For this repo class, that usually means preserving cube-state, scramble, scheduling, or timer internals while adapting pedagogy, analytics, and UI.",Aarav2709/KubeTimr — MIT — Keyboard-first offline timer. | Aarav2709/KubeTimr — MIT — Offline timer.,"Repurpose selected subsystems rather than the whole product. Mine the repo for scramble generation, algorithm database, recognition/training loop, timing/statistics, virtual cube, smartcube hooks, spaced repetition; keep what materially shortens build time, but rebind data contracts, permissions, UI shell, storage, and deployment to the HyperTwist architecture. Best first pairing order: tao-yu/Alg-Trainer, poliva/cubedex, Lykos/cube_trainer.","Consolidate under the Hyperspeedcube + cubing.js + qbr nucleus, not beside it as a separate silo. Normalize data contracts, auth/permissions, storage, and telemetry; then attach as a service, plugin, canvas layer, trainer, or analysis module. Descending combination order: tao-yu/Alg-Trainer, poliva/cubedex, Lykos/cube_trainer.","Repurpose here means: turn it into a trainer engine, solver/timer backend, recognition drill module, or method-specific practice mode for HyperTwist.",Map module boundaries; Identify hidden reusable internals; Define adapter/API boundary to target anchors; Write extraction tests against upstream behavior; Extract cube-state model; Normalize trainer/case schema; Expose analytics and replay hooks,deep source audit,"Hidden value often sits in cube-state representation, scramble generation, weighted drill scheduling, recognition datasets, replay/timer internals, and case database schemas.",Inspect cube-state model; scramble generator; trainer weighting/scheduling; case database and metadata; replay/timer model; import/export of alg sets; smartcube or sensor adapters.,"Inspect package manifests, README/docs, src tree, examples, tests, CI workflows, config files, migrations/schemas, and hidden feature flags or experimental modules. Look for algorithm databases, spaced-repetition logic, scramble generation, timer/stat code, virtual cube components, smartcube adapters, and custom-trainer configuration support.","Audit Aarav2709/KubeTimr as a cubing trainer / solver / timing candidate for HyperTwist. Do not stop at README-level features. Inspect: Inspect cube-state model; scramble generator; trainer weighting/scheduling; case database and metadata; replay/timer model; import/export of alg sets; smartcube or sensor adapters. Decide whether the best extraction path is moderate modification and whether it belongs as subsystem donor / training donor. Test the three merger paths in order: 1) tao-yu/Alg-Trainer [base + donor swarm]; 2) poliva/cubedex [specialized training UX donor]; 3) Lykos/cube_trainer [sampling/analytics donor]. Return hidden modules, reusable schemas, protocol layers, plugin hooks, render/state models, datasets/test fixtures, and any subsystem stronger than the visible product shell.",tao-yu/Alg-Trainer,base + donor swarm,Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.,poliva/cubedex,specialized training UX donor,Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.,Lykos/cube_trainer,sampling/analytics donor,Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.,project-local first,"Cross-project transfer is possible, but the value is clearest inside the assigned project until source audit exposes more reusable primitives.","exclude from core, keep as donor","Do not let it consume roadmap as a full product shell; mine reusable engines, adapters, schemas, UX patterns, or datasets.",medium,single-source signal; clear taxonomy; mostly donor/reference role,medium,strong adjacency to identified core stack; memo mentions: 2,"Licensing intentionally ignored as a decision filter in this canonical evaluation; assess only architecture, capability, donor value, and concept transfer.",,,,Aarav2709/KubeTimr — MIT — Keyboard-first offline timer. | Aarav2709/KubeTimr — MIT — Offline timer.,"Aarav2709/KubeTimr is treated as repurpose for HyperTwist because the current dossier keeps it as a focused subsystem donor for timer-state logic, split-phase handling, local persistence, rolling stats, and keyboard-first offline practice flow rather than as a broader training-platform anchor.",memo,False,True,0.0,2.0,HT_training_stack,HT_training_stack_0015,cubing / algorithm training,Integrate primarily for HyperTwist. Its memo and bookmark signals place it in the cubing / algorithm training layer.,HyperTwist,cubing / algorithm training,integrate,moderate modification,medium,aarav2709/kubetimr,1.0,Donor Bench,4.0,"Useful subsystem donor for timer-state logic, split-phase handling, local persistence, rolling stats, and keyboard-first offline practice flow.",Focused subsystem donor,Included,P2,"Aarav2709/KubeTimr is placed in Donor Bench for HyperTwist because it best serves the 'Focused subsystem donor' role; recommended action is 'repurpose' with repurposing scope 'moderate modification'. Confidence is medium because this remains a metadata-level judgment until source audit confirms hidden modules, plugin points, adapters, or architectural strengths.",2.0,3.0,2.0,11944.0,135.0,,aarav2709/kubetimr,HyperTwist,,,,,,,,,,Original global Phase G v4 retained,MIT,known_from_reference_material,uploaded_reference_docs,no,,,,Supplemental intake references are advisory only; v6 adjudication remains the source of truth.,Usually indirect,yes,v6 unified all-project source-of-truth pack,v5_carry_forward,,v6_unified_source_of_truth_pack,34.0,3,4.0,88.0,permissive_or_noncopyleft_known,direct_incorporation_ok,"This repo is permissively licensed and currently best treated as a focused subsystem donor for timer-state logic, split-phase handling, local persistence, and keyboard-first practice flow. Selective incorporation is legally straightforward, but the product shell should still be reshaped to fit HyperTwist.","Direct embed, vendored module, package dependency, or tightly integrated adapter as the architecture requires.","Typically preserve notices, attribution, and license text where required; no special copyleft-driven disclosure posture is normally needed.",Usually unnecessary unless you later decide the existing implementation is too constraining architecturally.,high,routine-review-only,yes,,,,,,,,,,,,,v6.3_final_source_of_truth,Normalized legacy adjacency wording and stale clean-room boundary posture to dossier-backed focused subsystem donor on 2026-04-25.,implemented_live_permissive,landed_permissive_preserve,"Phase 3R-A closed. Preserve as the landed first-party timer, inspection, splits, stats, persistence, and timer-scoped replay lane; start future widening from the live-lane audit, then the 3R-A implementation packet, then REPO_LICENSE_TRACKING.md." -36.0,roice3/MagicTile,https://github.com/roice3/MagicTile,HyperTwist,36.0,88.0,97.0,C,infra / runtime / observability / integration,subsystem donor,integration utility,locked strategic donor,repurpose,moderate modification,"Retain the valuable internal engine, but expect to replace UI/product shell, adapt schemas/APIs, and refactor boundaries so it can plug into the target anchors cleanly. For this repo class, that usually means preserving collectors/adapters/runtime topology logic while integrating into a larger control plane.",Non-euclidean Rubik's Cube Analogues,"Repurpose selected subsystems rather than the whole product. Mine the repo for scramble generation, algorithm database, recognition/training loop, timing/statistics, virtual cube, smartcube hooks, spaced repetition; keep what materially shortens build time, but rebind data contracts, permissions, UI shell, storage, and deployment to the HyperTwist architecture. Best first pairing order: tao-yu/Alg-Trainer, poliva/cubedex, Lykos/cube_trainer.","Consolidate under the Hyperspeedcube + cubing.js + qbr nucleus, not beside it as a separate silo. Normalize data contracts, auth/permissions, storage, and telemetry; then attach as a service, plugin, canvas layer, trainer, or analysis module. Descending combination order: tao-yu/Alg-Trainer, poliva/cubedex, Lykos/cube_trainer.","Repurpose here means: turn it into a trainer engine, solver/timer backend, recognition drill module, or method-specific practice mode for HyperTwist.",Map module boundaries; Identify hidden reusable internals; Define adapter/API boundary to target anchors; Write extraction tests against upstream behavior; Extract collectors/adapters; Normalize topology/config schema; Bridge into control-plane API,deep source audit,"Hidden value usually sits in service topology schemas, collector agents, auth/integration adapters, caching, deployment abstractions, and metrics/event correlation.",Inspect topology/service schema; collectors/agents; auth/integration adapters; caching/state sync; deployment/runtime abstractions; metrics/event correlation; config layering.,"Inspect package manifests, README/docs, src tree, examples, tests, CI workflows, config files, migrations/schemas, and hidden feature flags or experimental modules. Look for algorithm databases, spaced-repetition logic, scramble generation, timer/stat code, virtual cube components, smartcube adapters, and custom-trainer configuration support.","Audit roice3/MagicTile as a infra / runtime / observability / integration candidate for HyperTwist. Do not stop at README-level features. Inspect: Inspect topology/service schema; collectors/agents; auth/integration adapters; caching/state sync; deployment/runtime abstractions; metrics/event correlation; config layering. Decide whether the best extraction path is moderate modification and whether it belongs as subsystem donor / integration utility. Test the three merger paths in order: 1) project-local anchor [base + donor]; 2) shared portfolio utility [augmenter]; 3) cross-project transfer candidate [future merger]. Return hidden modules, reusable schemas, protocol layers, plugin hooks, render/state models, datasets/test fixtures, and any subsystem stronger than the visible product shell.",project-local anchor,base + donor,Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.,shared portfolio utility,augmenter,Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.,cross-project transfer candidate,future merger,Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.,project-local first,"Cross-project transfer is possible, but the value is clearest inside the assigned project until source audit exposes more reusable primitives.","exclude from core, keep as donor","Do not let it consume roadmap as a full product shell; mine reusable engines, adapters, schemas, UX patterns, or datasets.",medium-low,single-source signal; clear taxonomy; mostly donor/reference role,medium,explicit bookmark description available,"Licensing intentionally ignored as a decision filter in this canonical evaluation; assess only architecture, capability, donor value, and concept transfer.",HyperTwist(1),HyperTwist Consider,Non-euclidean Rubik's Cube Analogues,,"roice3/MagicTile is treated as repurpose for HyperTwist because visible metadata points to the cubing / algorithm training layer. Surface signal: Non-euclidean Rubik's Cube Analogues The fit looks real, but more as a donor/augmenter than as a standalone foundation.",bookmarks,True,False,1.0,0.0,HT_hyper_engine,HT_hyper_engine_0007,cubing / algorithm training,"Integrate primarily for HyperTwist. Its description and bookmark placement under ""HyperTwist Consider"" place it in the cubing / algorithm training layer.",HyperTwist,cubing / algorithm training,integrate,moderate modification,medium,roice3/magictile,1.0,Locked Strategic Donor,4.0,"MIT donor with unusually strong non-Euclidean tiling, topology, and generalized twist infrastructure value.",Top-tier non-Euclidean geometry and topology donor,Included,P1,Keep as a top-tier non-Euclidean geometry and topology donor for HyperTwist; the dossier-backed MIT posture and source richness justify promotion above the old donor-bench treatment.,2.0,2.0,2.0,11950.0,136.0,Thin-fit assignment; verify project mapping during source audit,roice3/magictile,HyperTwist,,,,,,,,,,Original global Phase G v4 retained,MIT,known_from_reference_material,uploaded_reference_docs,no,,,,Supplemental intake references are advisory only; v6 adjudication remains the source of truth.,Usually indirect,yes,v6 unified all-project source-of-truth pack,v5_carry_forward,,v6_unified_source_of_truth_pack,36.0,3,4.0,88.0,permissive_or_noncopyleft_known,direct_incorporation_ok,The repo is MIT and is explicitly retained as a top-tier geometry/topology donor. Direct donor use is legally straightforward if the architecture benefits from it.,Direct donor use or bounded adapter extraction are both acceptable; choose the seam that best preserves the topology and twist infrastructure.,Preserve MIT notices and attribution where required.,Usually unnecessary unless later replacing a narrow seam is cleaner than carrying the upstream code.,high,permissive-top-tier-donor,yes,,,,,,,,,,,,,v6.3_final_source_of_truth,Assigned from legacy HY_misc to HT_hyper_engine during cluster normalization on 2026-04-25.,selected_not_live_permissive_candidate,phase0r_permissive_eval_then_implement,"Phase 1R closed. Retain as a Phase 3R permissive implementation candidate; implement only from its packet authority and the retained-set contract, not by reopening Phase 0R." +36.0,roice3/MagicTile,https://github.com/roice3/MagicTile,HyperTwist,36.0,88.0,97.0,C,infra / runtime / observability / integration,subsystem donor,integration utility,locked strategic donor,repurpose,moderate modification,"Retain the valuable internal engine, but expect to replace UI/product shell, adapt schemas/APIs, and refactor boundaries so it can plug into the target anchors cleanly. For this repo class, that usually means preserving collectors/adapters/runtime topology logic while integrating into a larger control plane.",Non-euclidean Rubik's Cube Analogues,"Repurpose selected subsystems rather than the whole product. Mine the repo for scramble generation, algorithm database, recognition/training loop, timing/statistics, virtual cube, smartcube hooks, spaced repetition; keep what materially shortens build time, but rebind data contracts, permissions, UI shell, storage, and deployment to the HyperTwist architecture. Best first pairing order: tao-yu/Alg-Trainer, poliva/cubedex, Lykos/cube_trainer.","Consolidate under the Hyperspeedcube + cubing.js + qbr nucleus, not beside it as a separate silo. Normalize data contracts, auth/permissions, storage, and telemetry; then attach as a service, plugin, canvas layer, trainer, or analysis module. Descending combination order: tao-yu/Alg-Trainer, poliva/cubedex, Lykos/cube_trainer.","Repurpose here means: turn it into a trainer engine, solver/timer backend, recognition drill module, or method-specific practice mode for HyperTwist.",Map module boundaries; Identify hidden reusable internals; Define adapter/API boundary to target anchors; Write extraction tests against upstream behavior; Extract collectors/adapters; Normalize topology/config schema; Bridge into control-plane API,deep source audit,"Hidden value usually sits in service topology schemas, collector agents, auth/integration adapters, caching, deployment abstractions, and metrics/event correlation.",Inspect topology/service schema; collectors/agents; auth/integration adapters; caching/state sync; deployment/runtime abstractions; metrics/event correlation; config layering.,"Inspect package manifests, README/docs, src tree, examples, tests, CI workflows, config files, migrations/schemas, and hidden feature flags or experimental modules. Look for algorithm databases, spaced-repetition logic, scramble generation, timer/stat code, virtual cube components, smartcube adapters, and custom-trainer configuration support.","Audit roice3/MagicTile as a infra / runtime / observability / integration candidate for HyperTwist. Do not stop at README-level features. Inspect: Inspect topology/service schema; collectors/agents; auth/integration adapters; caching/state sync; deployment/runtime abstractions; metrics/event correlation; config layering. Decide whether the best extraction path is moderate modification and whether it belongs as subsystem donor / integration utility. Test the three merger paths in order: 1) project-local anchor [base + donor]; 2) shared portfolio utility [augmenter]; 3) cross-project transfer candidate [future merger]. Return hidden modules, reusable schemas, protocol layers, plugin hooks, render/state models, datasets/test fixtures, and any subsystem stronger than the visible product shell.",project-local anchor,base + donor,Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.,shared portfolio utility,augmenter,Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.,cross-project transfer candidate,future merger,Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.,project-local first,"Cross-project transfer is possible, but the value is clearest inside the assigned project until source audit exposes more reusable primitives.","exclude from core, keep as donor","Do not let it consume roadmap as a full product shell; mine reusable engines, adapters, schemas, UX patterns, or datasets.",medium-low,single-source signal; clear taxonomy; mostly donor/reference role,medium,explicit bookmark description available,"Licensing intentionally ignored as a decision filter in this canonical evaluation; assess only architecture, capability, donor value, and concept transfer.",HyperTwist(1),HyperTwist Consider,Non-euclidean Rubik's Cube Analogues,,"roice3/MagicTile is treated as repurpose for HyperTwist because visible metadata points to the cubing / algorithm training layer. Surface signal: Non-euclidean Rubik's Cube Analogues The fit looks real, but more as a donor/augmenter than as a standalone foundation.",bookmarks,True,False,1.0,0.0,HT_hyper_engine,HT_hyper_engine_0007,cubing / algorithm training,"Integrate primarily for HyperTwist. Its description and bookmark placement under ""HyperTwist Consider"" place it in the cubing / algorithm training layer.",HyperTwist,cubing / algorithm training,integrate,moderate modification,medium,roice3/magictile,1.0,Locked Strategic Donor,4.0,"MIT donor with unusually strong non-Euclidean tiling, topology, and generalized twist infrastructure value.",Top-tier non-Euclidean geometry and topology donor,Included,P1,Keep as a top-tier non-Euclidean geometry and topology donor for HyperTwist; the dossier-backed MIT posture and source richness justify promotion above the old donor-bench treatment.,2.0,2.0,2.0,11950.0,136.0,Thin-fit assignment; verify project mapping during source audit,roice3/magictile,HyperTwist,,,,,,,,,,Original global Phase G v4 retained,MIT,known_from_reference_material,uploaded_reference_docs,no,,,,Supplemental intake references are advisory only; v6 adjudication remains the source of truth.,Usually indirect,yes,v6 unified all-project source-of-truth pack,v5_carry_forward,,v6_unified_source_of_truth_pack,36.0,3,4.0,88.0,permissive_or_noncopyleft_known,direct_incorporation_ok,The repo is MIT and is explicitly retained as a top-tier geometry/topology donor. Direct donor use is legally straightforward if the architecture benefits from it.,Direct donor use or bounded adapter extraction are both acceptable; choose the seam that best preserves the topology and twist infrastructure.,Preserve MIT notices and attribution where required.,Usually unnecessary unless later replacing a narrow seam is cleaner than carrying the upstream code.,high,permissive-top-tier-donor,yes,,,,,,,,,,,,,v6.3_final_source_of_truth,Assigned from legacy HY_misc to HT_hyper_engine during cluster normalization on 2026-04-25.,implemented_live_permissive,landed_permissive_preserve,"Phase 3R-E closed. Preserve as the landed first-party embodied companion, narration, lip-sync, gesture, subtitle, and avatar-embed lane; start future widening from the live-lane audit, then the 3R-E implementation packet, then REPO_LICENSE_TRACKING.md." 41.0,PostHog/posthog,https://github.com/PostHog/posthog,HyperTwist,41.0,72.0,81.0,C,telemetry / replay / feature governance,subsystem donor,telemetry donor,donor bench,repurpose,moderate modification,"Retain the valuable internal engine, but expect to replace UI/product shell, adapt schemas/APIs, and refactor boundaries so it can plug into the target anchors cleanly. For this repo class, that usually means preserving calibration/detection/state-reconstruction logic while replacing camera UX and integration surfaces.","🦔 PostHog is an all-in-one developer platform for building successful products. We offer product analytics, web analytics, session replay, error tracking, feature flags, experimentation, surveys, data warehouse, a CDP, and an AI product ...","Repurpose selected subsystems rather than the whole product. Mine the repo for telemetry and event schemas, replay diagnostics, replay query surfaces, feature-flag governance, activity logs, and product/service boundary patterns; keep what materially shortens build time, but rebind data contracts, permissions, storage, and deployment to the HyperTwist architecture. Best first pairing order: HactarCE/Hyperspeedcube, cubing/cubing.js, kkoomen/qbr.","Consolidate under the Hyperspeedcube + cubing.js + qbr nucleus, not beside it as a separate silo. Normalize data contracts, auth/permissions, storage, and telemetry; then attach as a service, plugin, canvas layer, trainer, or analysis module. Descending combination order: HactarCE/Hyperspeedcube, cubing/cubing.js, kkoomen/qbr.","Repurpose here means: turn it into a telemetry spine, replay diagnostics donor, feature-governance donor, or control-plane integration layer.",Map module boundaries; Identify hidden reusable internals; Define adapter/API boundary to target anchors; Write extraction tests against upstream behavior; Benchmark calibration pipeline; Extract state reconstruction; Wrap with camera/AR adapter,deep source audit,"Hidden value often sits in calibration, preprocessing, stabilization, object/state reconstruction, replay artifacts, and camera-to-domain state pipelines that are not obvious from demos.","Inspect replay routes and deep links; replay diagnostics; feature-flag CRUD, dependencies, and evaluation; telemetry and event schemas; product and service boundaries; MIT versus ee path splits.","Inspect package manifests, README/docs, product slices, services, tests, migrations/schemas, and hidden feature flags or experimental modules. Look for replay diagnostics, replay query surfaces, feature-flag governance, activity logs, event schemas, service boundaries, and MIT versus ee/ path splits.","Audit PostHog/posthog as a telemetry / replay / feature-governance candidate for HyperTwist. Do not stop at README-level features. Inspect: replay routes and deep links, replay diagnostics, feature-flag CRUD/dependencies/evaluation, telemetry and event schemas, product/service boundaries, and MIT versus ee/ path splits. Decide whether the best extraction path remains moderate modification and which seams should stay bounded due mixed licensing or mission misfit. Return hidden modules, reusable schemas, protocol layers, plugin hooks, replay/debugging surfaces, and any subsystem stronger than the visible product shell.",kkoomen/qbr,foundation + perception donor,"Use this repo against the partner as an augmenting layer; preserve the partner as the likely base and mine this repo for capabilities that improve breadth, UX, or specialization.",vivaansinghvi07/rubix-cube-solver,perception + replay donor,Treat this pairing as a candidate donor merge rather than a replacement decision; inspect module boundaries to determine which side owns the final shell.,cubing/cubing.js,state/render backend,Use the partner for canonical state or rendering abstractions and merge this repo's specialized logic on top.,VectorShell | ScriptoriumAI,VectorShell can borrow spatial/rendering and perception primitives; ScriptoriumAI can borrow tutorial/educational visualization patterns rather than the full engine.,"exclude from core, keep as donor","Do not let it consume roadmap as a full product shell; mine reusable engines, adapters, schemas, UX patterns, or datasets.",medium-low,single-source signal; clear taxonomy; mostly donor/reference role,medium,explicit bookmark description available,"Licensing intentionally ignored as a decision filter in this canonical evaluation; assess only architecture, capability, donor value, and concept transfer.",HyperTwist(1),HyperTwist Consider,"🦔 PostHog is an all-in-one developer platform for building successful products. We offer product analytics, web analytics, session replay, error tracking, feature flags, experimentation, surveys, data warehouse, a CDP, and an AI product assistant to help debug your code, ship features faster, and keep all your usage and customer data in one stack.",,"PostHog/posthog is treated as repurpose for HyperTwist because visible metadata points to the cloud / infra / observability / api layer. Surface signal: 🦔 PostHog is an all-in-one developer platform for building successful products. We offer product analytics, web analytics, session replay, error tracking, feature flags, experimentation, surveys, data warehouse, a CDP, and an AI product ... The fit looks real, but more as a donor/augmenter than as a standalone foundation.",bookmarks,True,False,1.0,0.0,HT_control_plane,HT_control_plane_0001,cloud / infra / observability / api,"Repurpose selectively for HyperTwist. Its visible platform signal and source audit place it in telemetry, replay, and feature-governance rather than computer vision or AR.",HyperTwist,telemetry / replay / feature governance,repurpose,moderate modification,medium,posthog/posthog,1.0,Donor Bench,4.0,"Useful subsystem donor for HyperTwist in telemetry, replay diagnostics, feature flags, event-schema design, and vertical-slice control-plane patterns rather than the core runtime or product shell.",Telemetry / replay / feature-governance donor,Included,P2,"PostHog/posthog is placed in Donor Bench for HyperTwist because it best serves the 'Telemetry / replay / feature-governance donor' role; recommended action remains 'repurpose' with repurposing scope 'moderate modification'. Its real retained value is replay diagnostics, flag governance, event-schema thinking, and service-boundary patterns rather than any vision or perception role.",2.0,2.0,2.0,11966.0,139.0,Thin-fit assignment; verify project mapping during source audit,posthog/posthog,HyperTwist,,,,,,,,,,Original global Phase G v4 retained,MIT outside ee/; enterprise-restricted in ee/,known_from_reference_material,uploaded_reference_docs,no,,,,Supplemental intake references are advisory only; v6 adjudication remains the source of truth.,Usually indirect,yes,v6 unified all-project source-of-truth pack,v5_carry_forward,,v6_unified_source_of_truth_pack,41.0,3,4.0,72.0,mixed_or_boundary_sensitive_known,bounded_sidecar_or_selective_reimplementation,"The repo is mixed-license: MIT outside ee/ and enterprise-restricted inside ee/. Use only clearly MIT paths as bounded telemetry, replay, and feature-governance donor material, and exclude or reimplement enterprise-gated paths.","Use only clearly MIT paths outside ee/ as bounded telemetry, replay, and feature-governance donor surfaces; exclude enterprise paths or reimplement equivalent seams.",Keep MIT notices for reused paths and do not incorporate ee/ without separate commercial rights; verify path provenance before shipping.,"Sometimes useful for enterprise-gated or off-mission slices, but not required for clearly MIT paths.",high,mixed-license-path-review-required,no,,,,,,,,,,,,,v6.3_final_source_of_truth,Assigned to HT_control_plane and normalized telemetry/replay/feature-governance wording on 2026-04-25.,selected_not_live_boundary_sensitive,phase0r_boundary_sensitive_eval_then_adapter_or_sidecar,Phase 1R closed. Retain as a Phase 4R bounded telemetry and replay sidecar candidate; keep ee/ excluded and use explicit allowlists or first-party reimplementation where needed. -,met4citizen/TalkingHead,https://github.com/met4citizen/TalkingHead,HyperTwist,,,,,interface / visualization / shell surface,subsystem donor,interface donor,donor bench,repurpose,moderate modification,"Retain the reusable avatar, lip-sync, and retargeting layers, but replace the demo shell, asset assumptions, and voice-service integration with HyperTwist-owned surfaces.",,"Repurpose selected subsystems rather than the whole product. Mine the repo for embodied coach avatar runtime, lip-sync and subtitle timing, avatar-only embedding, retargeting, and streamed speech playback; keep what shortens build time, but rebind assets, voice services, and UI shell to the HyperTwist architecture.",,Repurpose here means: turn it into a browser-side embodied coach or companion layer.,,,,Inspect talkinghead runtime; speech queueing and streaming; viseme and blendshape flow; avatarOnly embedding; retargeting; and audio worklet behavior.,"Inspect modules, examples, tests, site config, streaming demos, retargeter, and playback worklet code. Look for embodied-coach embedding, lip-sync, subtitle timing, gesture and expression surfaces, and asset assumptions.","Audit met4citizen/TalkingHead as a browser embodied-coach candidate for HyperTwist. Inspect the avatar runtime, streaming lip-sync, subtitle timing, avatarOnly embedding, retargeting, and audio worklet behavior. Decide which seams can be used directly and which must remain bounded behind the HyperTwist coaching shell.",,,,,,,,,,,,,,medium,"Canonized Markdown dossier exists and the repo has been source-backed, but CSV backfill is later than the original v6.3 board generation.",medium,Source-backed dossier exists and the repo has been reconciled into the later Markdown authority stack.,,,,,,,,,,,,HT_browser_surface,HT_browser_surface_0001,browser / 3D / XR / presentation,"Repurpose selectively for HyperTwist. Its source-backed role is an embodied coach and companion presentation donor, not a generic avatar product shell.",HyperTwist,browser / 3D / XR / presentation,repurpose,moderate modification,medium,met4citizen/talkinghead,,Donor Bench,4.0,"Useful subsystem donor for HyperTwist, primarily in the browser companion layer; strongest embodied coach and avatar presentation donor in the current stack.",Browser embodied coach surface,Included,P2,"met4citizen/TalkingHead is placed in Donor Bench for HyperTwist because it provides embodied coach UI, streaming lip-sync, retargeting, and avatar-only embedding behavior. Recommended action remains repurpose, but the retained value is a bounded browser coach surface rather than a general avatar product.",,,,,,,met4citizen/talkinghead,,,,,,,,,,,,MIT,known_from_reference_material,uploaded_reference_docs,,,,,,,,,,,v6_unified_source_of_truth_pack,,,,,permissive_or_noncopyleft_known,direct_incorporation_ok,The code license is MIT and direct use is allowed. Treat it as a bounded browser-side donor for embodied coach presentation rather than as a product shell.,"Use directly as a bounded browser-side dependency or adapter layer; keep voice services, product logic, and asset provenance outside the upstream shell.","Typically preserve notices, attribution, and license text where required; review sample avatars or media separately from the code license.",Usually unnecessary unless you later replace a narrow upstream layer for product-shaping reasons.,high,standard-notice-review,yes,,,,,,,,,,,,,v6.3_markdown_backfill,Backfilled from canonized Markdown dossier pass on 2026-04-24.,selected_not_live_permissive_candidate,phase0r_permissive_eval_then_implement,"Phase 1R closed. Retain as a Phase 3R permissive implementation candidate; implement only from its packet authority and the retained-set contract, not by reopening Phase 0R." -,apache/echarts,https://github.com/apache/echarts,HyperTwist,,,,,analytics / visualization / reporting,subsystem donor,interface donor,donor bench,repurpose,moderate modification,"Retain the reusable chart runtime and reporting patterns, but keep HyperTwist domain schemas, page shell, and training logic outside the upstream system.",,"Repurpose selected subsystems rather than the whole product. Mine the repo for chart runtime, option and data-store patterns, export and save-as-image behavior, zoom and history handling, and SSR reporting surfaces; keep what shortens build time, but rebind analytics schemas and application shell to the HyperTwist architecture.",,"Repurpose here means: turn it into a bounded browser analytics and reporting layer for dashboards, replay summaries, and coaching views.",,,,"Inspect OptionManager, DataStore, zoom and history behavior, thumbnail and export features, SSR and hydration seams, and accessibility surface.","Inspect manifests, README/docs, src core, model, data, component, export, and SSR folders. Look for modular chart runtime, data-store abstractions, export surfaces, and reporting-specific UI behavior.","Audit apache/echarts as a browser analytics and reporting candidate for HyperTwist. Inspect the modular chart runtime, OptionManager and DataStore, export surfaces, zoom and history behavior, SSR path, and accessibility seams. Decide which parts should remain direct dependencies versus concept-only references.",,,,,,,,,,,,,,medium,"Canonized Markdown dossier exists and the repo has been source-backed, but CSV backfill is later than the original v6.3 board generation.",medium,Source-backed dossier exists and the repo has been reconciled into the later Markdown authority stack.,,,,,,,,,,,,HT_browser_surface,HT_browser_surface_0002,analytics / visualization / reporting,Repurpose selectively for HyperTwist. Its source-backed role is a bounded analytics and reporting donor rather than a generic dashboard widget.,HyperTwist,analytics / visualization / reporting,repurpose,moderate modification,medium,apache/echarts,,Donor Bench,4.0,"Useful subsystem donor for HyperTwist, primarily in the browser companion layer; strongest current analytics and reporting donor in the browser stack.",Browser analytics and reporting surface,Included,P2,"apache/echarts is placed in Donor Bench for HyperTwist because it provides the strongest current browser analytics and reporting stack with SSR, export, and serious data-store behavior. Recommended action remains repurpose, but the retained value is bounded reporting and coaching analytics rather than a product shell.",,,,,,,apache/echarts,,,,,,,,,,,,Apache-2.0,known_from_reference_material,uploaded_reference_docs,,,,,,,,,,,v6_unified_source_of_truth_pack,,,,,permissive_or_noncopyleft_known,direct_incorporation_ok,The code license is Apache-2.0 and direct use is allowed. Treat it as a bounded reporting and analytics donor.,Use directly as a bounded browser analytics dependency; keep HyperTwist data contracts and product logic outside the upstream shell.,Preserve LICENSE and NOTICE materials where required and review redistributed assets separately from the code license.,Usually unnecessary unless you later replace a narrow upstream layer for product-shaping reasons.,high,notice-file-review,yes,,,,,,,,,,,,,v6.3_markdown_backfill,Backfilled from canonized Markdown dossier pass on 2026-04-24.,selected_not_live_permissive_candidate,phase0r_permissive_eval_then_implement,"Phase 1R closed. Retain as a Phase 3R permissive implementation candidate; implement only from its packet authority and the retained-set contract, not by reopening Phase 0R." -,ecomfe/echarts-gl,https://github.com/ecomfe/echarts-gl,HyperTwist,,,,,interface / visualization / shell surface,subsystem donor,visualization donor,merge bench,integrate,moderate modification,"Retain selective 3D analytics surfaces, but keep HyperTwist domain models, scene ownership, and broader product shell outside the upstream package.",,"Integrate selected subsystems rather than the whole product. Mine the repo for 3D analytics and explainer surfaces, GL layer mounting, and view helper behavior; keep what shortens build time, but bind it to HyperTwist analytics schemas and browser companion UI.",,Integrate here means: merge bounded 3D analytics and explainer surfaces into the browser reporting stack.,,,,"Inspect 3D and GL chart exports, GL layer mounting, graph and flow surfaces, view helper behavior, and chart-space interaction handling.","Inspect manifests, README/docs, src chart and component exports, GL helper modules, and integration points with echarts and zrender.","Audit ecomfe/echarts-gl as a browser 3D analytics companion to apache/echarts. Inspect the 3D chart exports, GL view handling, and interaction seams. Decide which pieces deserve direct dependency use versus conceptual guidance only.",,,,,,,,,,,,,,medium,"Canonized Markdown dossier exists and the repo has been source-backed, but CSV backfill is later than the original v6.3 board generation.",medium,Source-backed dossier exists and the repo has been reconciled into the later Markdown authority stack.,,,,,,,,,,,,HT_browser_surface,HT_browser_surface_0003,browser / 3D / XR / presentation,Integrate selectively for HyperTwist. Its source-backed role is a 3D analytics and explainer extension beneath echarts rather than a standalone simulation lane.,HyperTwist,browser / 3D / XR / presentation,integrate,moderate modification,medium,ecomfe/echarts-gl,,Merge Bench,5.0,"Useful merge candidate for HyperTwist, primarily in the browser companion layer; strongest value sits in 3D chart and GL explainer surfaces beneath the echarts lane.",Browser 3D analytics and explainer surface,Included,P3,"ecomfe/echarts-gl is placed in Merge Bench for HyperTwist because it adds bounded 3D analytics and explainer value on top of echarts. Recommended action remains integrate, but the retained value is selective 3D reporting and graph surface behavior rather than a product runtime.",,,,,,,ecomfe/echarts-gl,,,,,,,,,,,,BSD-3-Clause,known_from_reference_material,uploaded_reference_docs,,,,,,,,,,,v6_unified_source_of_truth_pack,,,,,permissive_or_noncopyleft_known,direct_incorporation_ok,The code license is BSD-3-Clause and direct use is allowed. Treat it as a bounded 3D analytics extension rather than a runtime foundation.,Use directly as a bounded browser-side dependency beneath the reporting stack; keep HyperTwist scene ownership and product logic outside the upstream shell.,"Typically preserve notices, attribution, and license text where required.",Usually unnecessary unless you later replace a narrow upstream layer for product-shaping reasons.,high,standard-notice-review,yes,,,,,,,,,,,,,v6.3_markdown_backfill,Backfilled from canonized Markdown dossier pass on 2026-04-24.,selected_not_live_permissive_candidate,phase0r_permissive_eval_then_implement,"Phase 1R closed. Retain as a Phase 3R permissive implementation candidate; implement only from its packet authority and the retained-set contract, not by reopening Phase 0R." +,met4citizen/TalkingHead,https://github.com/met4citizen/TalkingHead,HyperTwist,,,,,interface / visualization / shell surface,subsystem donor,interface donor,donor bench,repurpose,moderate modification,"Retain the reusable avatar, lip-sync, and retargeting layers, but replace the demo shell, asset assumptions, and voice-service integration with HyperTwist-owned surfaces.",,"Repurpose selected subsystems rather than the whole product. Mine the repo for embodied coach avatar runtime, lip-sync and subtitle timing, avatar-only embedding, retargeting, and streamed speech playback; keep what shortens build time, but rebind assets, voice services, and UI shell to the HyperTwist architecture.",,Repurpose here means: turn it into a browser-side embodied coach or companion layer.,,,,Inspect talkinghead runtime; speech queueing and streaming; viseme and blendshape flow; avatarOnly embedding; retargeting; and audio worklet behavior.,"Inspect modules, examples, tests, site config, streaming demos, retargeter, and playback worklet code. Look for embodied-coach embedding, lip-sync, subtitle timing, gesture and expression surfaces, and asset assumptions.","Audit met4citizen/TalkingHead as a browser embodied-coach candidate for HyperTwist. Inspect the avatar runtime, streaming lip-sync, subtitle timing, avatarOnly embedding, retargeting, and audio worklet behavior. Decide which seams can be used directly and which must remain bounded behind the HyperTwist coaching shell.",,,,,,,,,,,,,,medium,"Canonized Markdown dossier exists and the repo has been source-backed, but CSV backfill is later than the original v6.3 board generation.",medium,Source-backed dossier exists and the repo has been reconciled into the later Markdown authority stack.,,,,,,,,,,,,HT_browser_surface,HT_browser_surface_0001,browser / 3D / XR / presentation,"Repurpose selectively for HyperTwist. Its source-backed role is an embodied coach and companion presentation donor, not a generic avatar product shell.",HyperTwist,browser / 3D / XR / presentation,repurpose,moderate modification,medium,met4citizen/talkinghead,,Donor Bench,4.0,"Useful subsystem donor for HyperTwist, primarily in the browser companion layer; strongest embodied coach and avatar presentation donor in the current stack.",Browser embodied coach surface,Included,P2,"met4citizen/TalkingHead is placed in Donor Bench for HyperTwist because it provides embodied coach UI, streaming lip-sync, retargeting, and avatar-only embedding behavior. Recommended action remains repurpose, but the retained value is a bounded browser coach surface rather than a general avatar product.",,,,,,,met4citizen/talkinghead,,,,,,,,,,,,MIT,known_from_reference_material,uploaded_reference_docs,,,,,,,,,,,v6_unified_source_of_truth_pack,,,,,permissive_or_noncopyleft_known,direct_incorporation_ok,The code license is MIT and direct use is allowed. Treat it as a bounded browser-side donor for embodied coach presentation rather than as a product shell.,"Use directly as a bounded browser-side dependency or adapter layer; keep voice services, product logic, and asset provenance outside the upstream shell.","Typically preserve notices, attribution, and license text where required; review sample avatars or media separately from the code license.",Usually unnecessary unless you later replace a narrow upstream layer for product-shaping reasons.,high,standard-notice-review,yes,,,,,,,,,,,,,v6.3_markdown_backfill,Backfilled from canonized Markdown dossier pass on 2026-04-24.,implemented_live_permissive,landed_permissive_preserve,"Phase 3R-E closed. Preserve as the landed first-party embodied companion, narration, lip-sync, gesture, subtitle, and avatar-embed lane; start future widening from the live-lane audit, then the 3R-E implementation packet, then REPO_LICENSE_TRACKING.md." +,apache/echarts,https://github.com/apache/echarts,HyperTwist,,,,,analytics / visualization / reporting,subsystem donor,interface donor,donor bench,repurpose,moderate modification,"Retain the reusable chart runtime and reporting patterns, but keep HyperTwist domain schemas, page shell, and training logic outside the upstream system.",,"Repurpose selected subsystems rather than the whole product. Mine the repo for chart runtime, option and data-store patterns, export and save-as-image behavior, zoom and history handling, and SSR reporting surfaces; keep what shortens build time, but rebind analytics schemas and application shell to the HyperTwist architecture.",,"Repurpose here means: turn it into a bounded browser analytics and reporting layer for dashboards, replay summaries, and coaching views.",,,,"Inspect OptionManager, DataStore, zoom and history behavior, thumbnail and export features, SSR and hydration seams, and accessibility surface.","Inspect manifests, README/docs, src core, model, data, component, export, and SSR folders. Look for modular chart runtime, data-store abstractions, export surfaces, and reporting-specific UI behavior.","Audit apache/echarts as a browser analytics and reporting candidate for HyperTwist. Inspect the modular chart runtime, OptionManager and DataStore, export surfaces, zoom and history behavior, SSR path, and accessibility seams. Decide which parts should remain direct dependencies versus concept-only references.",,,,,,,,,,,,,,medium,"Canonized Markdown dossier exists and the repo has been source-backed, but CSV backfill is later than the original v6.3 board generation.",medium,Source-backed dossier exists and the repo has been reconciled into the later Markdown authority stack.,,,,,,,,,,,,HT_browser_surface,HT_browser_surface_0002,analytics / visualization / reporting,Repurpose selectively for HyperTwist. Its source-backed role is a bounded analytics and reporting donor rather than a generic dashboard widget.,HyperTwist,analytics / visualization / reporting,repurpose,moderate modification,medium,apache/echarts,,Donor Bench,4.0,"Useful subsystem donor for HyperTwist, primarily in the browser companion layer; strongest current analytics and reporting donor in the browser stack.",Browser analytics and reporting surface,Included,P2,"apache/echarts is placed in Donor Bench for HyperTwist because it provides the strongest current browser analytics and reporting stack with SSR, export, and serious data-store behavior. Recommended action remains repurpose, but the retained value is bounded reporting and coaching analytics rather than a product shell.",,,,,,,apache/echarts,,,,,,,,,,,,Apache-2.0,known_from_reference_material,uploaded_reference_docs,,,,,,,,,,,v6_unified_source_of_truth_pack,,,,,permissive_or_noncopyleft_known,direct_incorporation_ok,The code license is Apache-2.0 and direct use is allowed. Treat it as a bounded reporting and analytics donor.,Use directly as a bounded browser analytics dependency; keep HyperTwist data contracts and product logic outside the upstream shell.,Preserve LICENSE and NOTICE materials where required and review redistributed assets separately from the code license.,Usually unnecessary unless you later replace a narrow upstream layer for product-shaping reasons.,high,notice-file-review,yes,,,,,,,,,,,,,v6.3_markdown_backfill,Backfilled from canonized Markdown dossier pass on 2026-04-24.,implemented_live_permissive,landed_permissive_preserve,"Phase 3R-E closed. Preserve as the landed first-party embodied companion, narration, lip-sync, gesture, subtitle, and avatar-embed lane; start future widening from the live-lane audit, then the 3R-E implementation packet, then REPO_LICENSE_TRACKING.md." +,ecomfe/echarts-gl,https://github.com/ecomfe/echarts-gl,HyperTwist,,,,,interface / visualization / shell surface,subsystem donor,visualization donor,merge bench,integrate,moderate modification,"Retain selective 3D analytics surfaces, but keep HyperTwist domain models, scene ownership, and broader product shell outside the upstream package.",,"Integrate selected subsystems rather than the whole product. Mine the repo for 3D analytics and explainer surfaces, GL layer mounting, and view helper behavior; keep what shortens build time, but bind it to HyperTwist analytics schemas and browser companion UI.",,Integrate here means: merge bounded 3D analytics and explainer surfaces into the browser reporting stack.,,,,"Inspect 3D and GL chart exports, GL layer mounting, graph and flow surfaces, view helper behavior, and chart-space interaction handling.","Inspect manifests, README/docs, src chart and component exports, GL helper modules, and integration points with echarts and zrender.","Audit ecomfe/echarts-gl as a browser 3D analytics companion to apache/echarts. Inspect the 3D chart exports, GL view handling, and interaction seams. Decide which pieces deserve direct dependency use versus conceptual guidance only.",,,,,,,,,,,,,,medium,"Canonized Markdown dossier exists and the repo has been source-backed, but CSV backfill is later than the original v6.3 board generation.",medium,Source-backed dossier exists and the repo has been reconciled into the later Markdown authority stack.,,,,,,,,,,,,HT_browser_surface,HT_browser_surface_0003,browser / 3D / XR / presentation,Integrate selectively for HyperTwist. Its source-backed role is a 3D analytics and explainer extension beneath echarts rather than a standalone simulation lane.,HyperTwist,browser / 3D / XR / presentation,integrate,moderate modification,medium,ecomfe/echarts-gl,,Merge Bench,5.0,"Useful merge candidate for HyperTwist, primarily in the browser companion layer; strongest value sits in 3D chart and GL explainer surfaces beneath the echarts lane.",Browser 3D analytics and explainer surface,Included,P3,"ecomfe/echarts-gl is placed in Merge Bench for HyperTwist because it adds bounded 3D analytics and explainer value on top of echarts. Recommended action remains integrate, but the retained value is selective 3D reporting and graph surface behavior rather than a product runtime.",,,,,,,ecomfe/echarts-gl,,,,,,,,,,,,BSD-3-Clause,known_from_reference_material,uploaded_reference_docs,,,,,,,,,,,v6_unified_source_of_truth_pack,,,,,permissive_or_noncopyleft_known,direct_incorporation_ok,The code license is BSD-3-Clause and direct use is allowed. Treat it as a bounded 3D analytics extension rather than a runtime foundation.,Use directly as a bounded browser-side dependency beneath the reporting stack; keep HyperTwist scene ownership and product logic outside the upstream shell.,"Typically preserve notices, attribution, and license text where required.",Usually unnecessary unless you later replace a narrow upstream layer for product-shaping reasons.,high,standard-notice-review,yes,,,,,,,,,,,,,v6.3_markdown_backfill,Backfilled from canonized Markdown dossier pass on 2026-04-24.,implemented_live_permissive,landed_permissive_preserve,"Phase 3R-E closed. Preserve as the landed first-party embodied companion, narration, lip-sync, gesture, subtitle, and avatar-embed lane; start future widening from the live-lane audit, then the 3R-E implementation packet, then REPO_LICENSE_TRACKING.md." ,KhronosGroup/glTF-Sample-Viewer,https://github.com/KhronosGroup/glTF-Sample-Viewer,HyperTwist,,,,,interface / visualization / shell surface,subsystem donor,viewer donor,donor bench,repurpose,moderate modification,"Retain the useful asset-validation and viewer surfaces, but keep HyperTwist asset flows, editor shell, and product logic outside the upstream viewer.",,"Repurpose selected subsystems rather than the whole product. Mine the repo for standards-aware asset preview, validation, capture, environment control, and viewer-shell behavior; keep what shortens build time, but bind it to HyperTwist asset tooling and browser companion surfaces.",,Repurpose here means: turn it into a bounded asset-validation and preview donor for browser tooling.,,,,"Inspect validator integration, material-variant support, environment and tone-mapping controls, capture behavior, and the relationship to glTF-Sample-Renderer.","Inspect manifests, README/docs, src main and UI logic, bundled renderer submodule, and validation-related surfaces.","Audit KhronosGroup/glTF-Sample-Viewer as a browser asset-validation and inspection candidate for HyperTwist. Inspect validator integration, capture flow, material variants, environment controls, and the renderer handoff. Decide which surfaces deserve direct use or selective extraction.",,,,,,,,,,,,,,medium,"Canonized Markdown dossier exists and the repo has been source-backed, but CSV backfill is later than the original v6.3 board generation.",medium,Source-backed dossier exists and the repo has been reconciled into the later Markdown authority stack.,,,,,,,,,,,,HT_browser_surface,HT_browser_surface_0004,browser / 3D / XR / presentation,Repurpose selectively for HyperTwist. Its source-backed role is a bounded asset-validation and standards-viewer donor rather than a runtime foundation.,HyperTwist,browser / 3D / XR / presentation,repurpose,moderate modification,medium,khronosgroup/gltf-sample-viewer,,Donor Bench,4.0,"Useful subsystem donor for HyperTwist, primarily in the browser companion layer; strongest value sits in official glTF standards validation and inspection tooling.",Browser asset validation and viewer surface,Included,P3,"KhronosGroup/glTF-Sample-Viewer is placed in Donor Bench for HyperTwist because it provides standards-aware asset validation, inspection, and viewer behavior. Recommended action remains repurpose, but the retained value is bounded asset QA and preview tooling rather than gameplay or runtime ownership.",,,,,,,khronosgroup/gltf-sample-viewer,,,,,,,,,,,,Apache-2.0,known_from_reference_material,uploaded_reference_docs,,,,,,,,,,,v6_unified_source_of_truth_pack,,,,,permissive_or_noncopyleft_known,direct_incorporation_ok,The code license is Apache-2.0 and direct use is allowed. Treat it as a bounded standards-viewer and asset-QA donor.,Use directly as a bounded asset-validation dependency or sidecar; keep HyperTwist asset workflows and product logic outside the upstream viewer shell.,Preserve LICENSE and NOTICE materials where required.,Usually unnecessary unless you later replace a narrow upstream layer for product-shaping reasons.,high,notice-file-review,yes,,,,,,,,,,,,,v6.3_markdown_backfill,Backfilled from canonized Markdown dossier pass on 2026-04-24.,selected_not_live_permissive_candidate,phase0r_permissive_eval_then_implement,"Phase 3R-D closed for the anchor. Retain as the subordinate standards-aware asset QA and validation sidecar beneath the landed google/model-viewer lane; do not treat it as separately live." ,google/model-viewer,https://github.com/google/model-viewer,HyperTwist,,,,,interface / visualization / shell surface,subsystem donor,viewer donor,donor bench,repurpose,moderate modification,"Retain the useful browser presentation and inspection layers, but keep HyperTwist product logic, page shell, and owned runtime direction outside the upstream project.",,"Repurpose selected subsystems rather than the whole product. Mine the repo for browser 3D presentation, annotations, inspection, snippet and export behavior, hotspot editing, and fidelity tooling; keep what shortens build time, but bind it to HyperTwist browser companion surfaces and asset workflows.",,"Repurpose here means: turn it into a bounded browser 3D presentation, inspection, and editor donor.",,,,"Inspect model-viewer runtime mixins, annotation and AR behavior, scene-graph access, space-opera editor surfaces, and render-fidelity support.","Inspect manifests, README/docs, packages/model-viewer runtime, space-opera, render-fidelity-tools, model-viewer-effects, and docs/example surfaces.","Audit google/model-viewer as a browser 3D presentation and inspection candidate for HyperTwist. Inspect the custom element runtime, annotation and AR behavior, scene-graph access, bundled editor and fidelity packages, and docs/demo tooling. Decide which surfaces merit direct use versus selective extraction.",,,,,,,,,,,,,,medium,"Canonized Markdown dossier exists and the repo has been source-backed, but CSV backfill is later than the original v6.3 board generation.",medium,Source-backed dossier exists and the repo has been reconciled into the later Markdown authority stack.,,,,,,,,,,,,HT_browser_surface,HT_browser_surface_0005,browser / 3D / XR / presentation,Repurpose selectively for HyperTwist. Its source-backed role is a bounded browser 3D presentation and inspection donor rather than a runtime foundation.,HyperTwist,browser / 3D / XR / presentation,repurpose,moderate modification,medium,google/model-viewer,,Donor Bench,4.0,"Useful subsystem donor for HyperTwist, primarily in the browser companion layer; strongest current browser 3D presentation and inspection donor in the stack.",Browser 3D presentation and inspection surface,Included,P2,"google/model-viewer is placed in Donor Bench for HyperTwist because it provides the strongest current browser 3D presentation and inspection stack, plus bundled editor and fidelity packages. Recommended action remains repurpose, but the retained value is bounded web preview, inspection, and AR-friendly presentation rather than a gameplay runtime.",,,,,,,google/model-viewer,,,,,,,,,,,,Apache-2.0,known_from_reference_material,uploaded_reference_docs,,,,,,,,,,,v6_unified_source_of_truth_pack,,,,,permissive_or_noncopyleft_known,direct_incorporation_ok,The code license is Apache-2.0 and direct use is allowed. Treat it as a bounded browser presentation and inspection donor.,"Use directly as a bounded browser-side dependency or adapter layer; keep HyperTwist runtime ownership, asset workflows, and product logic outside the upstream shell.",Preserve LICENSE and NOTICE materials where required and review bundled assets separately from the code license.,Usually unnecessary unless you later replace a narrow upstream layer for product-shaping reasons.,high,notice-file-review,yes,,,,,,,,,,,,,v6.3_markdown_backfill,Backfilled from canonized Markdown dossier pass on 2026-04-24.,implemented_live_permissive,landed_permissive_preserve,"Phase 3R-D closed. Preserve as the landed first-party browser presentation, compact editor, and standards-aware asset-QA lane; start future widening from the live-lane audit, then the 3R-D implementation packet, then REPO_LICENSE_TRACKING.md." -,mrdoob/three.js,https://github.com/mrdoob/three.js,HyperTwist,,,,,interface / visualization / shell surface,subsystem donor,dependency donor,donor bench,repurpose,moderate modification,Retain it mainly as a dependency substrate. Do not treat it as the owned gameplay foundation or let it reshape the Unreal-first runtime direction.,,"Repurpose selected subsystems rather than the whole product. Mine the repo for the browser 3D substrate, loader and exporter behavior, WebXR runtime hooks, and utility layers; keep what shortens build time, but leave HyperTwist gameplay and owned runtime direction outside the upstream engine.",,Repurpose here means: use it as the bounded browser-side 3D substrate and keep HyperTwist product logic above it.,,,,"Inspect core renderer and scene stack, loaders and exporters, WebXR manager, addons surface, and editor shell.","Inspect manifests, README/docs, src core and renderer folders, WebXR manager, addons, examples references, and editor shell.","Audit mrdoob/three.js as the browser 3D substrate beneath HyperTwist companion surfaces. Inspect renderer, scene, camera, math, loader, WebXR, and editor behavior. Decide what should be used directly as dependency substrate versus what should remain conceptual.",,,,,,,,,,,,,,medium,"Canonized Markdown dossier exists and the repo has been source-backed, but CSV backfill is later than the original v6.3 board generation.",medium,Source-backed dossier exists and the repo has been reconciled into the later Markdown authority stack.,,,,,,,,,,,,HT_browser_surface,HT_browser_surface_0006,browser / 3D / XR / presentation,"Repurpose selectively for HyperTwist. Its source-backed role is the commodity browser 3D substrate beneath the browser companion stack, not the owned runtime foundation.",HyperTwist,browser / 3D / XR / presentation,repurpose,moderate modification,medium,mrdoob/three.js,,Donor Bench,4.0,"Useful subsystem donor for HyperTwist, primarily in the browser companion layer; strongest commodity browser 3D substrate in the current stack.",Browser 3D substrate,Included,P2,"mrdoob/three.js is placed in Donor Bench for HyperTwist because it is the core browser 3D substrate beneath the newer viewer, XR, and companion-surface repos. Recommended action remains repurpose, but the retained value is a bounded browser dependency layer rather than product differentiation.",,,,,,,mrdoob/three.js,,,,,,,,,,,,MIT,known_from_reference_material,uploaded_reference_docs,,,,,,,,,,,v6_unified_source_of_truth_pack,,,,,permissive_or_noncopyleft_known,direct_incorporation_ok,The code license is MIT and direct use is allowed. Treat it as a bounded browser 3D substrate rather than as an owned runtime foundation.,"Use directly as a bounded browser-side dependency; keep HyperTwist gameplay, puzzle logic, and owned runtime direction outside the upstream engine.","Typically preserve notices, attribution, and license text where required.",Usually unnecessary unless you later replace a narrow upstream layer for product-shaping reasons.,high,standard-notice-review,yes,,,,,,,,,,,,,v6.3_markdown_backfill,Backfilled from canonized Markdown dossier pass on 2026-04-24.,selected_not_live_permissive_candidate,phase0r_permissive_eval_then_implement,"Phase 1R closed. Retain as a Phase 3R permissive implementation candidate; implement only from its packet authority and the retained-set contract, not by reopening Phase 0R." -,pmndrs/postprocessing,https://github.com/pmndrs/postprocessing,HyperTwist,,,,,interface / visualization / shell surface,subsystem donor,dependency donor,merge bench,integrate,moderate modification,"Retain selective effect infrastructure, but keep HyperTwist scene ownership, domain logic, and product shell outside the upstream package.",,"Integrate selected subsystems rather than the whole product. Mine the repo for effect-composer, outline, SSAO, and bounded browser emphasis behavior; keep what shortens build time, but bind it to HyperTwist browser viewers and coach surfaces.",,Integrate here means: merge bounded browser-side effect and emphasis infrastructure into the companion stack.,,,,"Inspect EffectComposer and EffectPass, outline and SSAO effect behavior, effect catalog breadth, and performance assumptions.","Inspect manifests, README/docs, core composer and pass code, major effects, and integration seams with three.js.","Audit pmndrs/postprocessing as a bounded browser post-processing substrate for HyperTwist. Inspect composer, pass, outline, and SSAO behavior and decide what should remain direct dependency use versus conceptual reference.",,,,,,,,,,,,,,medium,"Canonized Markdown dossier exists and the repo has been source-backed, but CSV backfill is later than the original v6.3 board generation.",medium,Source-backed dossier exists and the repo has been reconciled into the later Markdown authority stack.,,,,,,,,,,,,HT_browser_surface,HT_browser_surface_0007,browser / 3D / XR / presentation,Integrate selectively for HyperTwist. Its source-backed role is a bounded browser post-processing substrate beneath three.js rather than a product lane.,HyperTwist,browser / 3D / XR / presentation,integrate,moderate modification,medium,pmndrs/postprocessing,,Merge Bench,5.0,"Useful merge candidate for HyperTwist, primarily in the browser companion layer; strongest value sits in outline, SSAO, and effect-composer infrastructure beneath browser viewers.",Browser post-processing substrate,Included,P3,"pmndrs/postprocessing is placed in Merge Bench for HyperTwist because it provides bounded browser post-processing infrastructure beneath three.js-based viewers and companion surfaces. Recommended action remains integrate, but the retained value is selective effect infrastructure rather than a standalone feature lane.",,,,,,,pmndrs/postprocessing,,,,,,,,,,,,Zlib,known_from_reference_material,uploaded_reference_docs,,,,,,,,,,,v6_unified_source_of_truth_pack,,,,,permissive_or_noncopyleft_known,direct_incorporation_ok,The code license is Zlib and direct use is allowed. Treat it as a bounded browser post-processing dependency.,Use directly as a bounded browser-side dependency beneath three.js-based viewers; keep HyperTwist product logic outside the upstream package.,"Typically preserve notices, attribution, and license text where required.",Usually unnecessary unless you later replace a narrow upstream layer for product-shaping reasons.,high,standard-notice-review,yes,,,,,,,,,,,,,v6.3_markdown_backfill,Backfilled from canonized Markdown dossier pass on 2026-04-24.,selected_not_live_permissive_candidate,phase0r_permissive_eval_then_implement,"Phase 1R closed. Retain as a Phase 3R permissive implementation candidate; implement only from its packet authority and the retained-set contract, not by reopening Phase 0R." -,pmndrs/react-three-fiber,https://github.com/pmndrs/react-three-fiber,HyperTwist,,,,,interface / visualization / shell surface,subsystem donor,dependency donor,donor bench,repurpose,moderate modification,"Retain it mainly as a dependency substrate. Keep HyperTwist domain logic, product shell, and runtime ownership above the upstream renderer.",,"Repurpose selected subsystems rather than the whole product. Mine the repo for React renderer and event behavior, scene hook patterns, and browser companion ergonomics; keep what shortens build time, but leave HyperTwist product logic and owned runtime direction outside the upstream layer.",,Repurpose here means: use it as the bounded React renderer substrate for browser-side 3D and XR surfaces.,,,,"Inspect Canvas and createRoot behavior, reconciler and store wiring, event system, hooks, and the native path.","Inspect manifests, README/docs, fiber package runtime, core renderer code, event handling, hooks, and native entry points.","Audit pmndrs/react-three-fiber as the React renderer substrate for HyperTwist browser companion scenes. Inspect Canvas, createRoot, event handling, hooks, and runtime boundaries. Decide which parts should remain direct dependency use versus conceptual reference.",,,,,,,,,,,,,,medium,"Canonized Markdown dossier exists and the repo has been source-backed, but CSV backfill is later than the original v6.3 board generation.",medium,Source-backed dossier exists and the repo has been reconciled into the later Markdown authority stack.,,,,,,,,,,,,HT_browser_surface,HT_browser_surface_0008,browser / 3D / XR / presentation,Repurpose selectively for HyperTwist. Its source-backed role is the commodity React renderer substrate above three.js for browser companion surfaces.,HyperTwist,browser / 3D / XR / presentation,repurpose,moderate modification,medium,pmndrs/react-three-fiber,,Donor Bench,4.0,"Useful subsystem donor for HyperTwist, primarily in the browser companion layer; strongest current React renderer substrate above three.js in the stack.",Browser React 3D substrate,Included,P2,"pmndrs/react-three-fiber is placed in Donor Bench for HyperTwist because it is the React runtime and event substrate above three.js for browser companion scenes. Recommended action remains repurpose, but the retained value is a bounded browser renderer layer rather than product differentiation.",,,,,,,pmndrs/react-three-fiber,,,,,,,,,,,,MIT,known_from_reference_material,uploaded_reference_docs,,,,,,,,,,,v6_unified_source_of_truth_pack,,,,,permissive_or_noncopyleft_known,direct_incorporation_ok,The code license is MIT and direct use is allowed. Treat it as a bounded browser React renderer substrate.,Use directly as a bounded browser-side dependency above three.js; keep HyperTwist product logic and runtime ownership outside the upstream layer.,"Typically preserve notices, attribution, and license text where required.",Usually unnecessary unless you later replace a narrow upstream layer for product-shaping reasons.,high,standard-notice-review,yes,,,,,,,,,,,,,v6.3_markdown_backfill,Backfilled from canonized Markdown dossier pass on 2026-04-24.,selected_not_live_permissive_candidate,phase0r_permissive_eval_then_implement,"Phase 1R closed. Retain as a Phase 3R permissive implementation candidate; implement only from its packet authority and the retained-set contract, not by reopening Phase 0R." -,pmndrs/drei,https://github.com/pmndrs/drei,HyperTwist,,,,,interface / visualization / shell surface,subsystem donor,interface donor,merge bench,integrate,moderate modification,Retain only the helpers with direct product leverage. Keep HyperTwist product architecture outside the upstream abstraction sprawl.,,"Integrate selected helpers rather than the whole package surface. Mine the repo for Html overlays, split-view handling, transform controls, staging, and selective asset helper behavior; keep what shortens build time, but avoid inheriting abstraction sprawl.",,Integrate here means: merge bounded browser helper abstractions into the companion stack where they materially reduce implementation cost.,,,,"Inspect Html overlay behavior, View split rendering, TransformControls, Environment setup, Gltf helpers, and staging utilities.","Inspect manifests, README/docs, core and web helper components, TransformControls, Html, View, Environment, and Gltf wrappers.","Audit pmndrs/drei as a bounded helper layer for HyperTwist browser companion scenes. Inspect Html, View, TransformControls, Environment, and Gltf helper behavior. Decide which utilities deserve active use and which should stay out to avoid abstraction sprawl.",,,,,,,,,,,,,,medium,"Canonized Markdown dossier exists and the repo has been source-backed, but CSV backfill is later than the original v6.3 board generation.",medium,Source-backed dossier exists and the repo has been reconciled into the later Markdown authority stack.,,,,,,,,,,,,HT_browser_surface,HT_browser_surface_0009,browser / 3D / XR / presentation,"Integrate selectively for HyperTwist. Its source-backed role is a high-leverage helper and abstraction layer above react-three-fiber, not a product lane.",HyperTwist,browser / 3D / XR / presentation,integrate,moderate modification,medium,pmndrs/drei,,Merge Bench,5.0,"Useful merge candidate for HyperTwist, primarily in the browser companion layer; strongest value sits in overlays, controls, split views, staging, and asset helper abstractions.",Browser 3D helper and abstraction layer,Included,P3,"pmndrs/drei is placed in Merge Bench for HyperTwist because it provides practical helper abstractions above react-three-fiber for browser companion surfaces. Recommended action remains integrate, but the retained value is selective helper and overlay behavior rather than a foundation.",,,,,,,pmndrs/drei,,,,,,,,,,,,MIT,known_from_reference_material,uploaded_reference_docs,,,,,,,,,,,v6_unified_source_of_truth_pack,,,,,permissive_or_noncopyleft_known,direct_incorporation_ok,The code license is MIT and direct use is allowed. Treat it as a bounded browser helper layer above react-three-fiber.,Use directly as a bounded browser-side helper layer; keep HyperTwist product logic and architectural ownership outside the upstream package.,"Typically preserve notices, attribution, and license text where required.",Usually unnecessary unless you later replace a narrow upstream layer for product-shaping reasons.,high,standard-notice-review,yes,,,,,,,,,,,,,v6.3_markdown_backfill,Backfilled from canonized Markdown dossier pass on 2026-04-24.,selected_not_live_permissive_candidate,phase0r_permissive_eval_then_implement,"Phase 1R closed. Retain as a Phase 3R permissive implementation candidate; implement only from its packet authority and the retained-set contract, not by reopening Phase 0R." -,pmndrs/xr,https://github.com/pmndrs/xr,HyperTwist,,,,,interface / visualization / shell surface,subsystem donor,interaction donor,donor bench,repurpose,moderate modification,"Retain the useful XR interaction substrate, but keep HyperTwist product logic, permissions, and owned runtime direction outside the upstream stack.",,"Repurpose selected subsystems rather than the whole product. Mine the repo for XR session state, dom-overlay, pointer interaction, locomotion, and manipulation behavior; keep what shortens build time, but bind it to HyperTwist browser companion flows and permissions.",,Repurpose here means: turn it into the bounded browser XR interaction substrate for immersive companion surfaces.,,,,"Inspect XR store/runtime, dom-overlay support, locomotion hooks, pointer-event model, and handle/manipulation behavior.","Inspect manifests, README/docs, xr store package, React bridge, dom-overlay, locomotion, pointer-events, and handle packages.","Audit pmndrs/xr as the browser XR interaction substrate for HyperTwist companion surfaces. Inspect XR store/runtime, dom-overlay, locomotion, pointer-events, and handle behavior. Decide which pieces should remain direct use and which should stay conceptual.",,,,,,,,,,,,,,medium,"Canonized Markdown dossier exists and the repo has been source-backed, but CSV backfill is later than the original v6.3 board generation.",medium,Source-backed dossier exists and the repo has been reconciled into the later Markdown authority stack.,,,,,,,,,,,,HT_browser_surface,HT_browser_surface_0010,browser / 3D / XR / presentation,"Repurpose selectively for HyperTwist. Its source-backed role is the strongest browser XR interaction and immersive UI donor, not a product foundation.",HyperTwist,browser / 3D / XR / presentation,repurpose,moderate modification,medium,pmndrs/xr,,Donor Bench,4.0,"Useful subsystem donor for HyperTwist, primarily in the browser companion layer; strongest current browser XR interaction and immersive UI donor in the stack.",Browser XR and immersive UI substrate,Included,P2,"pmndrs/xr is placed in Donor Bench for HyperTwist because it provides the strongest current browser XR interaction substrate, including session state, pointer interaction, locomotion, and dom-overlay behavior. Recommended action remains repurpose, but the retained value is bounded browser XR infrastructure rather than runtime ownership.",,,,,,,pmndrs/xr,,,,,,,,,,,,MIT,known_from_reference_material,uploaded_reference_docs,,,,,,,,,,,v6_unified_source_of_truth_pack,,,,,permissive_or_noncopyleft_known,direct_incorporation_ok,The code license is MIT and direct use is allowed. Treat it as a bounded browser XR interaction donor.,Use directly as a bounded browser-side XR dependency; keep HyperTwist product logic and runtime ownership outside the upstream stack.,"Typically preserve notices, attribution, and license text where required.",Usually unnecessary unless you later replace a narrow upstream layer for product-shaping reasons.,high,standard-notice-review,yes,,,,,,,,,,,,,v6.3_markdown_backfill,Backfilled from canonized Markdown dossier pass on 2026-04-24.,selected_not_live_permissive_candidate,phase0r_permissive_eval_then_implement,"Phase 1R closed. Retain as a Phase 3R permissive implementation candidate; implement only from its packet authority and the retained-set contract, not by reopening Phase 0R." -,pmndrs/uikit,https://github.com/pmndrs/uikit,HyperTwist,,,,,interface / visualization / shell surface,subsystem donor,interface donor,donor bench,repurpose,moderate modification,"Retain the useful spatial UI substrate, but keep HyperTwist product logic, styling language, and runtime ownership outside the upstream package.",,"Repurpose selected subsystems rather than the whole product. Mine the repo for spatial layout, clipping, scrolling, text, and fullscreen panel behavior; keep what shortens build time, but bind it to HyperTwist browser companion surfaces and interface design.",,"Repurpose here means: turn it into the bounded browser spatial UI layer for dashboards, coach panels, and immersive menus.",,,,"Inspect spatial layout runtime, clipping and scrolling behavior, text and media components, Fullscreen, Container, and React bridge behavior.","Inspect manifests, README/docs, react package, build runtime, core uikit components, Fullscreen, Container, and layout-related code.","Audit pmndrs/uikit as the browser spatial UI donor for HyperTwist companion surfaces. Inspect layout, clipping, scrolling, text/media components, and Fullscreen/Container behavior. Decide which parts deserve direct use and which should stay conceptual.",,,,,,,,,,,,,,medium,"Canonized Markdown dossier exists and the repo has been source-backed, but CSV backfill is later than the original v6.3 board generation.",medium,Source-backed dossier exists and the repo has been reconciled into the later Markdown authority stack.,,,,,,,,,,,,HT_browser_surface,HT_browser_surface_0011,browser / 3D / XR / presentation,"Repurpose selectively for HyperTwist. Its source-backed role is the browser spatial UI and 3D interface donor, not a product foundation.",HyperTwist,browser / 3D / XR / presentation,repurpose,moderate modification,medium,pmndrs/uikit,,Donor Bench,4.0,"Useful subsystem donor for HyperTwist, primarily in the browser companion layer; strongest current browser spatial UI and 3D interface donor in the stack.",Browser spatial UI surface,Included,P2,"pmndrs/uikit is placed in Donor Bench for HyperTwist because it provides the strongest current browser spatial UI layer with layout, clipping, text, scrolling, and panel behavior. Recommended action remains repurpose, but the retained value is bounded spatial interface infrastructure rather than runtime ownership.",,,,,,,pmndrs/uikit,,,,,,,,,,,,MIT,known_from_reference_material,uploaded_reference_docs,,,,,,,,,,,v6_unified_source_of_truth_pack,,,,,permissive_or_noncopyleft_known,direct_incorporation_ok,The code license is MIT and direct use is allowed. Treat it as a bounded browser spatial UI donor.,Use directly as a bounded browser-side dependency; keep HyperTwist product logic and styling ownership outside the upstream stack.,"Typically preserve notices, attribution, and license text where required.",Usually unnecessary unless you later replace a narrow upstream layer for product-shaping reasons.,high,standard-notice-review,yes,,,,,,,,,,,,,v6.3_markdown_backfill,Backfilled from canonized Markdown dossier pass on 2026-04-24.,selected_not_live_permissive_candidate,phase0r_permissive_eval_then_implement,"Phase 1R closed. Retain as a Phase 3R permissive implementation candidate; implement only from its packet authority and the retained-set contract, not by reopening Phase 0R." -,pmndrs/react-spring,https://github.com/pmndrs/react-spring,HyperTwist,,,,,interface / visualization / shell surface,subsystem donor,interaction donor,merge bench,integrate,moderate modification,"Retain selective motion infrastructure, but keep HyperTwist product logic, page flows, and interface ownership outside the upstream package.",,"Integrate selected motion subsystems rather than the whole product. Mine the repo for spring motion runtime, scheduling, and layered explainer behavior; keep what shortens build time, but bind it to HyperTwist browser companion surfaces and interaction design.",,Integrate here means: merge bounded motion and layered explainer behavior into browser companion surfaces.,,,,"Inspect Controller and SpringValue runtime, scheduler behavior, parallax and layered motion, and browser integration patterns.","Inspect manifests, README/docs, core runtime, scheduler package, parallax package, and animated host behavior.","Audit pmndrs/react-spring as a browser motion substrate for HyperTwist companion surfaces. Inspect core motion runtime, scheduling, layered explainer behavior, and browser integration patterns. Decide which parts deserve active use and which should stay conceptual.",,,,,,,,,,,,,,medium,"Canonized Markdown dossier exists and the repo has been source-backed, but CSV backfill is later than the original v6.3 board generation.",medium,Source-backed dossier exists and the repo has been reconciled into the later Markdown authority stack.,,,,,,,,,,,,HT_browser_surface,HT_browser_surface_0012,browser / 3D / XR / presentation,"Integrate selectively for HyperTwist. Its source-backed role is a browser motion and animation substrate for companion surfaces, not a product lane.",HyperTwist,browser / 3D / XR / presentation,integrate,moderate modification,medium,pmndrs/react-spring,,Merge Bench,5.0,"Useful merge candidate for HyperTwist, primarily in the browser companion layer; strongest value sits in spring motion, scheduling, and layered browser explainer behavior.",Browser motion and animation layer,Included,P3,"pmndrs/react-spring is placed in Merge Bench for HyperTwist because it provides the browser motion substrate beneath layered explainers and polished companion UI. Recommended action remains integrate, but the retained value is selective motion infrastructure rather than a product foundation.",,,,,,,pmndrs/react-spring,,,,,,,,,,,,MIT,known_from_reference_material,uploaded_reference_docs,,,,,,,,,,,v6_unified_source_of_truth_pack,,,,,permissive_or_noncopyleft_known,direct_incorporation_ok,The code license is MIT and direct use is allowed. Treat it as a bounded browser motion substrate.,Use directly as a bounded browser-side dependency; keep HyperTwist product logic and page-flow ownership outside the upstream package.,"Typically preserve notices, attribution, and license text where required.",Usually unnecessary unless you later replace a narrow upstream layer for product-shaping reasons.,high,standard-notice-review,yes,,,,,,,,,,,,,v6.3_markdown_backfill,Backfilled from canonized Markdown dossier pass on 2026-04-24.,selected_not_live_permissive_candidate,phase0r_permissive_eval_then_implement,"Phase 1R closed. Retain as a Phase 3R permissive implementation candidate; implement only from its packet authority and the retained-set contract, not by reopening Phase 0R." +,mrdoob/three.js,https://github.com/mrdoob/three.js,HyperTwist,,,,,interface / visualization / shell surface,subsystem donor,dependency donor,donor bench,repurpose,moderate modification,Retain it mainly as a dependency substrate. Do not treat it as the owned gameplay foundation or let it reshape the Unreal-first runtime direction.,,"Repurpose selected subsystems rather than the whole product. Mine the repo for the browser 3D substrate, loader and exporter behavior, WebXR runtime hooks, and utility layers; keep what shortens build time, but leave HyperTwist gameplay and owned runtime direction outside the upstream engine.",,Repurpose here means: use it as the bounded browser-side 3D substrate and keep HyperTwist product logic above it.,,,,"Inspect core renderer and scene stack, loaders and exporters, WebXR manager, addons surface, and editor shell.","Inspect manifests, README/docs, src core and renderer folders, WebXR manager, addons, examples references, and editor shell.","Audit mrdoob/three.js as the browser 3D substrate beneath HyperTwist companion surfaces. Inspect renderer, scene, camera, math, loader, WebXR, and editor behavior. Decide what should be used directly as dependency substrate versus what should remain conceptual.",,,,,,,,,,,,,,medium,"Canonized Markdown dossier exists and the repo has been source-backed, but CSV backfill is later than the original v6.3 board generation.",medium,Source-backed dossier exists and the repo has been reconciled into the later Markdown authority stack.,,,,,,,,,,,,HT_browser_surface,HT_browser_surface_0006,browser / 3D / XR / presentation,"Repurpose selectively for HyperTwist. Its source-backed role is the commodity browser 3D substrate beneath the browser companion stack, not the owned runtime foundation.",HyperTwist,browser / 3D / XR / presentation,repurpose,moderate modification,medium,mrdoob/three.js,,Donor Bench,4.0,"Useful subsystem donor for HyperTwist, primarily in the browser companion layer; strongest commodity browser 3D substrate in the current stack.",Browser 3D substrate,Included,P2,"mrdoob/three.js is placed in Donor Bench for HyperTwist because it is the core browser 3D substrate beneath the newer viewer, XR, and companion-surface repos. Recommended action remains repurpose, but the retained value is a bounded browser dependency layer rather than product differentiation.",,,,,,,mrdoob/three.js,,,,,,,,,,,,MIT,known_from_reference_material,uploaded_reference_docs,,,,,,,,,,,v6_unified_source_of_truth_pack,,,,,permissive_or_noncopyleft_known,direct_incorporation_ok,The code license is MIT and direct use is allowed. Treat it as a bounded browser 3D substrate rather than as an owned runtime foundation.,"Use directly as a bounded browser-side dependency; keep HyperTwist gameplay, puzzle logic, and owned runtime direction outside the upstream engine.","Typically preserve notices, attribution, and license text where required.",Usually unnecessary unless you later replace a narrow upstream layer for product-shaping reasons.,high,standard-notice-review,yes,,,,,,,,,,,,,v6.3_markdown_backfill,Backfilled from canonized Markdown dossier pass on 2026-04-24.,implemented_live_permissive,landed_permissive_preserve,"Phase 3R-E closed. Preserve as the landed first-party embodied companion, narration, lip-sync, gesture, subtitle, and avatar-embed lane; start future widening from the live-lane audit, then the 3R-E implementation packet, then REPO_LICENSE_TRACKING.md." +,pmndrs/postprocessing,https://github.com/pmndrs/postprocessing,HyperTwist,,,,,interface / visualization / shell surface,subsystem donor,dependency donor,merge bench,integrate,moderate modification,"Retain selective effect infrastructure, but keep HyperTwist scene ownership, domain logic, and product shell outside the upstream package.",,"Integrate selected subsystems rather than the whole product. Mine the repo for effect-composer, outline, SSAO, and bounded browser emphasis behavior; keep what shortens build time, but bind it to HyperTwist browser viewers and coach surfaces.",,Integrate here means: merge bounded browser-side effect and emphasis infrastructure into the companion stack.,,,,"Inspect EffectComposer and EffectPass, outline and SSAO effect behavior, effect catalog breadth, and performance assumptions.","Inspect manifests, README/docs, core composer and pass code, major effects, and integration seams with three.js.","Audit pmndrs/postprocessing as a bounded browser post-processing substrate for HyperTwist. Inspect composer, pass, outline, and SSAO behavior and decide what should remain direct dependency use versus conceptual reference.",,,,,,,,,,,,,,medium,"Canonized Markdown dossier exists and the repo has been source-backed, but CSV backfill is later than the original v6.3 board generation.",medium,Source-backed dossier exists and the repo has been reconciled into the later Markdown authority stack.,,,,,,,,,,,,HT_browser_surface,HT_browser_surface_0007,browser / 3D / XR / presentation,Integrate selectively for HyperTwist. Its source-backed role is a bounded browser post-processing substrate beneath three.js rather than a product lane.,HyperTwist,browser / 3D / XR / presentation,integrate,moderate modification,medium,pmndrs/postprocessing,,Merge Bench,5.0,"Useful merge candidate for HyperTwist, primarily in the browser companion layer; strongest value sits in outline, SSAO, and effect-composer infrastructure beneath browser viewers.",Browser post-processing substrate,Included,P3,"pmndrs/postprocessing is placed in Merge Bench for HyperTwist because it provides bounded browser post-processing infrastructure beneath three.js-based viewers and companion surfaces. Recommended action remains integrate, but the retained value is selective effect infrastructure rather than a standalone feature lane.",,,,,,,pmndrs/postprocessing,,,,,,,,,,,,Zlib,known_from_reference_material,uploaded_reference_docs,,,,,,,,,,,v6_unified_source_of_truth_pack,,,,,permissive_or_noncopyleft_known,direct_incorporation_ok,The code license is Zlib and direct use is allowed. Treat it as a bounded browser post-processing dependency.,Use directly as a bounded browser-side dependency beneath three.js-based viewers; keep HyperTwist product logic outside the upstream package.,"Typically preserve notices, attribution, and license text where required.",Usually unnecessary unless you later replace a narrow upstream layer for product-shaping reasons.,high,standard-notice-review,yes,,,,,,,,,,,,,v6.3_markdown_backfill,Backfilled from canonized Markdown dossier pass on 2026-04-24.,implemented_live_permissive,landed_permissive_preserve,"Phase 3R-E closed. Preserve as the landed first-party embodied companion, narration, lip-sync, gesture, subtitle, and avatar-embed lane; start future widening from the live-lane audit, then the 3R-E implementation packet, then REPO_LICENSE_TRACKING.md." +,pmndrs/react-three-fiber,https://github.com/pmndrs/react-three-fiber,HyperTwist,,,,,interface / visualization / shell surface,subsystem donor,dependency donor,donor bench,repurpose,moderate modification,"Retain it mainly as a dependency substrate. Keep HyperTwist domain logic, product shell, and runtime ownership above the upstream renderer.",,"Repurpose selected subsystems rather than the whole product. Mine the repo for React renderer and event behavior, scene hook patterns, and browser companion ergonomics; keep what shortens build time, but leave HyperTwist product logic and owned runtime direction outside the upstream layer.",,Repurpose here means: use it as the bounded React renderer substrate for browser-side 3D and XR surfaces.,,,,"Inspect Canvas and createRoot behavior, reconciler and store wiring, event system, hooks, and the native path.","Inspect manifests, README/docs, fiber package runtime, core renderer code, event handling, hooks, and native entry points.","Audit pmndrs/react-three-fiber as the React renderer substrate for HyperTwist browser companion scenes. Inspect Canvas, createRoot, event handling, hooks, and runtime boundaries. Decide which parts should remain direct dependency use versus conceptual reference.",,,,,,,,,,,,,,medium,"Canonized Markdown dossier exists and the repo has been source-backed, but CSV backfill is later than the original v6.3 board generation.",medium,Source-backed dossier exists and the repo has been reconciled into the later Markdown authority stack.,,,,,,,,,,,,HT_browser_surface,HT_browser_surface_0008,browser / 3D / XR / presentation,Repurpose selectively for HyperTwist. Its source-backed role is the commodity React renderer substrate above three.js for browser companion surfaces.,HyperTwist,browser / 3D / XR / presentation,repurpose,moderate modification,medium,pmndrs/react-three-fiber,,Donor Bench,4.0,"Useful subsystem donor for HyperTwist, primarily in the browser companion layer; strongest current React renderer substrate above three.js in the stack.",Browser React 3D substrate,Included,P2,"pmndrs/react-three-fiber is placed in Donor Bench for HyperTwist because it is the React runtime and event substrate above three.js for browser companion scenes. Recommended action remains repurpose, but the retained value is a bounded browser renderer layer rather than product differentiation.",,,,,,,pmndrs/react-three-fiber,,,,,,,,,,,,MIT,known_from_reference_material,uploaded_reference_docs,,,,,,,,,,,v6_unified_source_of_truth_pack,,,,,permissive_or_noncopyleft_known,direct_incorporation_ok,The code license is MIT and direct use is allowed. Treat it as a bounded browser React renderer substrate.,Use directly as a bounded browser-side dependency above three.js; keep HyperTwist product logic and runtime ownership outside the upstream layer.,"Typically preserve notices, attribution, and license text where required.",Usually unnecessary unless you later replace a narrow upstream layer for product-shaping reasons.,high,standard-notice-review,yes,,,,,,,,,,,,,v6.3_markdown_backfill,Backfilled from canonized Markdown dossier pass on 2026-04-24.,implemented_live_permissive,landed_permissive_preserve,"Phase 3R-E closed. Preserve as the landed first-party embodied companion, narration, lip-sync, gesture, subtitle, and avatar-embed lane; start future widening from the live-lane audit, then the 3R-E implementation packet, then REPO_LICENSE_TRACKING.md." +,pmndrs/drei,https://github.com/pmndrs/drei,HyperTwist,,,,,interface / visualization / shell surface,subsystem donor,interface donor,merge bench,integrate,moderate modification,Retain only the helpers with direct product leverage. Keep HyperTwist product architecture outside the upstream abstraction sprawl.,,"Integrate selected helpers rather than the whole package surface. Mine the repo for Html overlays, split-view handling, transform controls, staging, and selective asset helper behavior; keep what shortens build time, but avoid inheriting abstraction sprawl.",,Integrate here means: merge bounded browser helper abstractions into the companion stack where they materially reduce implementation cost.,,,,"Inspect Html overlay behavior, View split rendering, TransformControls, Environment setup, Gltf helpers, and staging utilities.","Inspect manifests, README/docs, core and web helper components, TransformControls, Html, View, Environment, and Gltf wrappers.","Audit pmndrs/drei as a bounded helper layer for HyperTwist browser companion scenes. Inspect Html, View, TransformControls, Environment, and Gltf helper behavior. Decide which utilities deserve active use and which should stay out to avoid abstraction sprawl.",,,,,,,,,,,,,,medium,"Canonized Markdown dossier exists and the repo has been source-backed, but CSV backfill is later than the original v6.3 board generation.",medium,Source-backed dossier exists and the repo has been reconciled into the later Markdown authority stack.,,,,,,,,,,,,HT_browser_surface,HT_browser_surface_0009,browser / 3D / XR / presentation,"Integrate selectively for HyperTwist. Its source-backed role is a high-leverage helper and abstraction layer above react-three-fiber, not a product lane.",HyperTwist,browser / 3D / XR / presentation,integrate,moderate modification,medium,pmndrs/drei,,Merge Bench,5.0,"Useful merge candidate for HyperTwist, primarily in the browser companion layer; strongest value sits in overlays, controls, split views, staging, and asset helper abstractions.",Browser 3D helper and abstraction layer,Included,P3,"pmndrs/drei is placed in Merge Bench for HyperTwist because it provides practical helper abstractions above react-three-fiber for browser companion surfaces. Recommended action remains integrate, but the retained value is selective helper and overlay behavior rather than a foundation.",,,,,,,pmndrs/drei,,,,,,,,,,,,MIT,known_from_reference_material,uploaded_reference_docs,,,,,,,,,,,v6_unified_source_of_truth_pack,,,,,permissive_or_noncopyleft_known,direct_incorporation_ok,The code license is MIT and direct use is allowed. Treat it as a bounded browser helper layer above react-three-fiber.,Use directly as a bounded browser-side helper layer; keep HyperTwist product logic and architectural ownership outside the upstream package.,"Typically preserve notices, attribution, and license text where required.",Usually unnecessary unless you later replace a narrow upstream layer for product-shaping reasons.,high,standard-notice-review,yes,,,,,,,,,,,,,v6.3_markdown_backfill,Backfilled from canonized Markdown dossier pass on 2026-04-24.,implemented_live_permissive,landed_permissive_preserve,"Phase 3R-E closed. Preserve as the landed first-party embodied companion, narration, lip-sync, gesture, subtitle, and avatar-embed lane; start future widening from the live-lane audit, then the 3R-E implementation packet, then REPO_LICENSE_TRACKING.md." +,pmndrs/xr,https://github.com/pmndrs/xr,HyperTwist,,,,,interface / visualization / shell surface,subsystem donor,interaction donor,donor bench,repurpose,moderate modification,"Retain the useful XR interaction substrate, but keep HyperTwist product logic, permissions, and owned runtime direction outside the upstream stack.",,"Repurpose selected subsystems rather than the whole product. Mine the repo for XR session state, dom-overlay, pointer interaction, locomotion, and manipulation behavior; keep what shortens build time, but bind it to HyperTwist browser companion flows and permissions.",,Repurpose here means: turn it into the bounded browser XR interaction substrate for immersive companion surfaces.,,,,"Inspect XR store/runtime, dom-overlay support, locomotion hooks, pointer-event model, and handle/manipulation behavior.","Inspect manifests, README/docs, xr store package, React bridge, dom-overlay, locomotion, pointer-events, and handle packages.","Audit pmndrs/xr as the browser XR interaction substrate for HyperTwist companion surfaces. Inspect XR store/runtime, dom-overlay, locomotion, pointer-events, and handle behavior. Decide which pieces should remain direct use and which should stay conceptual.",,,,,,,,,,,,,,medium,"Canonized Markdown dossier exists and the repo has been source-backed, but CSV backfill is later than the original v6.3 board generation.",medium,Source-backed dossier exists and the repo has been reconciled into the later Markdown authority stack.,,,,,,,,,,,,HT_browser_surface,HT_browser_surface_0010,browser / 3D / XR / presentation,"Repurpose selectively for HyperTwist. Its source-backed role is the strongest browser XR interaction and immersive UI donor, not a product foundation.",HyperTwist,browser / 3D / XR / presentation,repurpose,moderate modification,medium,pmndrs/xr,,Donor Bench,4.0,"Useful subsystem donor for HyperTwist, primarily in the browser companion layer; strongest current browser XR interaction and immersive UI donor in the stack.",Browser XR and immersive UI substrate,Included,P2,"pmndrs/xr is placed in Donor Bench for HyperTwist because it provides the strongest current browser XR interaction substrate, including session state, pointer interaction, locomotion, and dom-overlay behavior. Recommended action remains repurpose, but the retained value is bounded browser XR infrastructure rather than runtime ownership.",,,,,,,pmndrs/xr,,,,,,,,,,,,MIT,known_from_reference_material,uploaded_reference_docs,,,,,,,,,,,v6_unified_source_of_truth_pack,,,,,permissive_or_noncopyleft_known,direct_incorporation_ok,The code license is MIT and direct use is allowed. Treat it as a bounded browser XR interaction donor.,Use directly as a bounded browser-side XR dependency; keep HyperTwist product logic and runtime ownership outside the upstream stack.,"Typically preserve notices, attribution, and license text where required.",Usually unnecessary unless you later replace a narrow upstream layer for product-shaping reasons.,high,standard-notice-review,yes,,,,,,,,,,,,,v6.3_markdown_backfill,Backfilled from canonized Markdown dossier pass on 2026-04-24.,implemented_live_permissive,landed_permissive_preserve,"Phase 3R-E closed. Preserve as the landed first-party embodied companion, narration, lip-sync, gesture, subtitle, and avatar-embed lane; start future widening from the live-lane audit, then the 3R-E implementation packet, then REPO_LICENSE_TRACKING.md." +,pmndrs/uikit,https://github.com/pmndrs/uikit,HyperTwist,,,,,interface / visualization / shell surface,subsystem donor,interface donor,donor bench,repurpose,moderate modification,"Retain the useful spatial UI substrate, but keep HyperTwist product logic, styling language, and runtime ownership outside the upstream package.",,"Repurpose selected subsystems rather than the whole product. Mine the repo for spatial layout, clipping, scrolling, text, and fullscreen panel behavior; keep what shortens build time, but bind it to HyperTwist browser companion surfaces and interface design.",,"Repurpose here means: turn it into the bounded browser spatial UI layer for dashboards, coach panels, and immersive menus.",,,,"Inspect spatial layout runtime, clipping and scrolling behavior, text and media components, Fullscreen, Container, and React bridge behavior.","Inspect manifests, README/docs, react package, build runtime, core uikit components, Fullscreen, Container, and layout-related code.","Audit pmndrs/uikit as the browser spatial UI donor for HyperTwist companion surfaces. Inspect layout, clipping, scrolling, text/media components, and Fullscreen/Container behavior. Decide which parts deserve direct use and which should stay conceptual.",,,,,,,,,,,,,,medium,"Canonized Markdown dossier exists and the repo has been source-backed, but CSV backfill is later than the original v6.3 board generation.",medium,Source-backed dossier exists and the repo has been reconciled into the later Markdown authority stack.,,,,,,,,,,,,HT_browser_surface,HT_browser_surface_0011,browser / 3D / XR / presentation,"Repurpose selectively for HyperTwist. Its source-backed role is the browser spatial UI and 3D interface donor, not a product foundation.",HyperTwist,browser / 3D / XR / presentation,repurpose,moderate modification,medium,pmndrs/uikit,,Donor Bench,4.0,"Useful subsystem donor for HyperTwist, primarily in the browser companion layer; strongest current browser spatial UI and 3D interface donor in the stack.",Browser spatial UI surface,Included,P2,"pmndrs/uikit is placed in Donor Bench for HyperTwist because it provides the strongest current browser spatial UI layer with layout, clipping, text, scrolling, and panel behavior. Recommended action remains repurpose, but the retained value is bounded spatial interface infrastructure rather than runtime ownership.",,,,,,,pmndrs/uikit,,,,,,,,,,,,MIT,known_from_reference_material,uploaded_reference_docs,,,,,,,,,,,v6_unified_source_of_truth_pack,,,,,permissive_or_noncopyleft_known,direct_incorporation_ok,The code license is MIT and direct use is allowed. Treat it as a bounded browser spatial UI donor.,Use directly as a bounded browser-side dependency; keep HyperTwist product logic and styling ownership outside the upstream stack.,"Typically preserve notices, attribution, and license text where required.",Usually unnecessary unless you later replace a narrow upstream layer for product-shaping reasons.,high,standard-notice-review,yes,,,,,,,,,,,,,v6.3_markdown_backfill,Backfilled from canonized Markdown dossier pass on 2026-04-24.,implemented_live_permissive,landed_permissive_preserve,"Phase 3R-E closed. Preserve as the landed first-party embodied companion, narration, lip-sync, gesture, subtitle, and avatar-embed lane; start future widening from the live-lane audit, then the 3R-E implementation packet, then REPO_LICENSE_TRACKING.md." +,pmndrs/react-spring,https://github.com/pmndrs/react-spring,HyperTwist,,,,,interface / visualization / shell surface,subsystem donor,interaction donor,merge bench,integrate,moderate modification,"Retain selective motion infrastructure, but keep HyperTwist product logic, page flows, and interface ownership outside the upstream package.",,"Integrate selected motion subsystems rather than the whole product. Mine the repo for spring motion runtime, scheduling, and layered explainer behavior; keep what shortens build time, but bind it to HyperTwist browser companion surfaces and interaction design.",,Integrate here means: merge bounded motion and layered explainer behavior into browser companion surfaces.,,,,"Inspect Controller and SpringValue runtime, scheduler behavior, parallax and layered motion, and browser integration patterns.","Inspect manifests, README/docs, core runtime, scheduler package, parallax package, and animated host behavior.","Audit pmndrs/react-spring as a browser motion substrate for HyperTwist companion surfaces. Inspect core motion runtime, scheduling, layered explainer behavior, and browser integration patterns. Decide which parts deserve active use and which should stay conceptual.",,,,,,,,,,,,,,medium,"Canonized Markdown dossier exists and the repo has been source-backed, but CSV backfill is later than the original v6.3 board generation.",medium,Source-backed dossier exists and the repo has been reconciled into the later Markdown authority stack.,,,,,,,,,,,,HT_browser_surface,HT_browser_surface_0012,browser / 3D / XR / presentation,"Integrate selectively for HyperTwist. Its source-backed role is a browser motion and animation substrate for companion surfaces, not a product lane.",HyperTwist,browser / 3D / XR / presentation,integrate,moderate modification,medium,pmndrs/react-spring,,Merge Bench,5.0,"Useful merge candidate for HyperTwist, primarily in the browser companion layer; strongest value sits in spring motion, scheduling, and layered browser explainer behavior.",Browser motion and animation layer,Included,P3,"pmndrs/react-spring is placed in Merge Bench for HyperTwist because it provides the browser motion substrate beneath layered explainers and polished companion UI. Recommended action remains integrate, but the retained value is selective motion infrastructure rather than a product foundation.",,,,,,,pmndrs/react-spring,,,,,,,,,,,,MIT,known_from_reference_material,uploaded_reference_docs,,,,,,,,,,,v6_unified_source_of_truth_pack,,,,,permissive_or_noncopyleft_known,direct_incorporation_ok,The code license is MIT and direct use is allowed. Treat it as a bounded browser motion substrate.,Use directly as a bounded browser-side dependency; keep HyperTwist product logic and page-flow ownership outside the upstream package.,"Typically preserve notices, attribution, and license text where required.",Usually unnecessary unless you later replace a narrow upstream layer for product-shaping reasons.,high,standard-notice-review,yes,,,,,,,,,,,,,v6.3_markdown_backfill,Backfilled from canonized Markdown dossier pass on 2026-04-24.,implemented_live_permissive,landed_permissive_preserve,"Phase 3R-E closed. Preserve as the landed first-party embodied companion, narration, lip-sync, gesture, subtitle, and avatar-embed lane; start future widening from the live-lane audit, then the 3R-E implementation packet, then REPO_LICENSE_TRACKING.md." ,screenpipe/screenpipe,https://github.com/screenpipe/screenpipe,HyperTwist,,,,,capture / replay / support-plane,subsystem donor,support donor,donor bench,repurpose,moderate modification,"Retain the valuable internal layer, but expect to replace upstream shell assumptions and rebind boundaries so it fits the HyperTwist architecture.",,"Repurpose selected subsystems rather than the whole product. Mine the repo for local capture and replay architecture, permission-aware tooling, timeline behavior, vault storage, and notification support surfaces; keep what materially shortens build time, but bind it to HyperTwist-owned data contracts, UI shell, and runtime boundaries.",,Repurpose here means: extract bounded support surfaces from this repo without inheriting the full upstream shell.,,,,"the recording lifecycle, engine and database crates, permission model, rewind timeline behavior, notification routes, and vault handling.","Inspect manifests, README/docs, engine/database/vault crates, app tauri surfaces, timeline UI, notification routes, and permission middleware.","Audit screenpipe/screenpipe as a Support-plane capture, history, and replay sidecar candidate for HyperTwist. Inspect the recording lifecycle, engine and database crates, permission model, rewind timeline behavior, notification routes, and vault handling. Decide whether the retained value should remain active and what should stay bounded outside the HyperTwist core.",,,,,,,,,,,,,,medium,"Canonized Markdown dossier exists and the repo has been source-backed, but CSV backfill is later than the original v6.3 board generation.",medium,Source-backed dossier exists and the repo has been reconciled into the later Markdown authority stack.,,,,,,,,,,,,HT_support_sidecars,HT_support_sidecars_0001,support plane / capture / replay,"Repurpose selectively for HyperTwist. Its source-backed role is a strategic donor with care for local capture/history/replay, permissions-aware agents, encrypted vaults, and notification support surfaces, not a gameplay or vision foundation.",HyperTwist,support plane / capture / replay,repurpose,moderate modification,medium,screenpipe/screenpipe,,Donor Bench,4.0,"Useful donor bench candidate for HyperTwist, primarily in the 'Support-plane capture, history, and replay sidecar' lane; a strategic donor with care for local capture/history/replay, permissions-aware agents, encrypted vaults, and notification support surfaces, not a gameplay or vision foundation.","Support-plane capture, history, and replay sidecar",Included,P2,"screenpipe/screenpipe is placed in Donor Bench for HyperTwist because it provides a strategic donor with care for local capture/history/replay, permissions-aware agents, encrypted vaults, and notification support surfaces, not a gameplay or vision foundation. Recommended action remains repurpose, but it should stay bounded to the Support-plane capture, history, and replay sidecar lane rather than reshape the core runtime.",,,,,,,screenpipe/screenpipe,,,,,,,,,,,,MIT OR Apache-2.0 core; enterprise-restricted ee/,known_from_reference_material,uploaded_reference_docs,,,,,,,,,,Backfilled from canonized Markdown dossier pass on 2026-04-25: 52-screenpipe-screenpipe-upstream-dossier.md,v6_unified_source_of_truth_pack,,,,,mixed_or_boundary_sensitive_known,bounded_sidecar_or_selective_reimplementation,The repo is permissive in its core paths but includes enterprise-restricted ee/ content. Use only clearly permissive core paths as bounded capture/history/replay donor material and exclude or reimplement enterprise-gated paths.,Use only clearly permissive core paths as bounded support-plane donor surfaces; exclude enterprise paths or reimplement equivalent seams.,Preserve permissive notices for reused core paths and do not incorporate ee/ without separate commercial rights.,"Sometimes useful for enterprise-gated slices, but not required for clearly permissive core paths.",high,mixed-license-path-review-required,no,,,,,,,,,,,,,v6.3_markdown_backfill,Backfilled from canonized Markdown dossier pass on 2026-04-25: 52-screenpipe-screenpipe-upstream-dossier.md,selected_not_live_boundary_sensitive,phase0r_boundary_sensitive_eval_then_adapter_or_sidecar,"Phase 1R closed. Retain as a Phase 4R bounded capture, history, and replay sidecar candidate; keep ee/ excluded and permissive-core use narrowly allowlisted." ,remotion-dev/remotion,https://github.com/remotion-dev/remotion,HyperTwist,,,,,media / rendering / export,subsystem donor,media donor,donor bench,repurpose,moderate modification,"Retain the valuable internal layer, but expect to replace upstream shell assumptions and rebind boundaries so it fits the HyperTwist architecture.",,"Repurpose selected subsystems rather than the whole product. Mine the repo for media export, explainer rendering, embedded player behavior, and bounded browser or server-side export workflows; keep what materially shortens build time, but bind it to HyperTwist-owned data contracts, UI shell, and runtime boundaries.",,Repurpose here means: extract bounded support surfaces from this repo without inheriting the full upstream shell.,,,,"the player and renderer packages, studio/editor package, media-parser surfaces, export workflow, and custom commercial license boundaries.","Inspect manifests, LICENSE, README/docs, player package, renderer package, studio package, media-parser package, and major export/render entry points.","Audit remotion-dev/remotion as a Media export and explainer sidecar candidate for HyperTwist. Inspect the player and renderer packages, studio/editor package, media-parser surfaces, export workflow, and custom commercial license boundaries. Decide whether the retained value should remain active and what should stay bounded outside the HyperTwist core.",,,,,,,,,,,,,,medium,"Canonized Markdown dossier exists and the repo has been source-backed, but CSV backfill is later than the original v6.3 board generation.",medium,Source-backed dossier exists and the repo has been reconciled into the later Markdown authority stack.,,,,,,,,,,,,HT_support_sidecars,HT_support_sidecars_0002,media / rendering / export,"Repurpose selectively for HyperTwist. Its source-backed role is a bounded commercially licensed media-export and explainer sidecar, not a product foundation.",HyperTwist,media / rendering / export,repurpose,moderate modification,medium,remotion-dev/remotion,,Donor Bench,4.0,"Useful donor bench candidate for HyperTwist, primarily in the 'Media export and explainer sidecar' lane; a bounded commercially licensed media-export and explainer sidecar, not a product foundation.",Commercially licensed media-export and explainer sidecar,Included,P3,"remotion-dev/remotion is placed in Donor Bench for HyperTwist because it provides a bounded commercially licensed media-export and explainer sidecar, not a product foundation. Recommended action remains repurpose, but it should stay bounded to the Media export and explainer sidecar lane rather than reshape the core runtime.",,,,,,,remotion-dev/remotion,,,,,,,,,,,,Custom two-tier commercial license,known_from_reference_material,uploaded_reference_docs,,,,,,,,,,Backfilled from canonized Markdown dossier pass on 2026-04-25: 53-remotion-dev-remotion-upstream-dossier.md,v6_unified_source_of_truth_pack,,,,,mixed_or_boundary_sensitive_known,bounded_sidecar_or_selective_reimplementation,The repo uses a custom two-tier commercial license and should remain a bounded media-export and explainer sidecar. Review the commercial terms before direct use and do not treat it as a carefree donor.,Keep behind a bounded media-render/export seam; do not let it become a runtime foundation.,Preserve upstream license materials and satisfy the applicable commercial terms before shipping or internal deployment.,Sometimes useful only if later commercial terms or deployment constraints make direct use less attractive.,high,commercial-license-sidecar-review,no,,,,,,,,,,,,,v6.3_markdown_backfill,Refined on 2026-04-25 to the dossier-backed commercially licensed media-export and explainer sidecar posture.,selected_not_live_boundary_sensitive,phase0r_boundary_sensitive_eval_then_adapter_or_sidecar,Phase 1R closed. Retain as a Phase 4R commercially sensitive media-export and explainer sidecar candidate; make an explicit package-level license decision before any use. -,ecomfe/zrender,https://github.com/ecomfe/zrender,HyperTwist,,,,,interface / visualization / shell surface,subsystem donor,dependency donor,merge bench,integrate,moderate modification,"Retain the reusable internal layer, but replace shell assumptions and rebind boundaries so it plugs into HyperTwist cleanly.",,"Integrate selected subsystems rather than the whole product. Mine the repo for 2D rendering, scene-graph, animation, and event-handling substrate behavior beneath browser reporting surfaces; keep what materially shortens build time, but bind it to HyperTwist-owned data contracts, UI shell, and runtime boundaries.",,Integrate here means: merge bounded support surfaces from this repo into the HyperTwist companion stack.,,,,"the zrender runtime entry, scene storage, canvas and SVG painters, handler proxy, and animation behavior.","Inspect manifests, README/docs, runtime entry, storage, painter implementations, event proxy, animation modules, and core graphic primitives.","Audit ecomfe/zrender as a Browser 2D render substrate candidate for HyperTwist. Inspect the zrender runtime entry, scene storage, canvas and SVG painters, handler proxy, and animation behavior. Decide whether the retained value should remain active and what should stay bounded outside the HyperTwist core.",,,,,,,,,,,,,,medium,"Canonized Markdown dossier exists and the repo has been source-backed, but CSV backfill is later than the original v6.3 board generation.",medium,Source-backed dossier exists and the repo has been reconciled into the later Markdown authority stack.,,,,,,,,,,,,HT_browser_support,HT_browser_support_0001,browser / 2D / visualization,"Integrate selectively for HyperTwist. Its source-backed role is a lower-level 2D rendering and interaction substrate beneath echarts, not a separate strategic product lane.",HyperTwist,browser / 2D / visualization,integrate,moderate modification,medium,ecomfe/zrender,,Merge Bench,5.0,"Useful merge bench candidate for HyperTwist, primarily in the 'Browser 2D render substrate' lane; a lower-level 2D rendering and interaction substrate beneath echarts, not a separate strategic product lane.",Browser 2D render substrate,Included,P3,"ecomfe/zrender is placed in Merge Bench for HyperTwist because it provides a lower-level 2D rendering and interaction substrate beneath echarts, not a separate strategic product lane. Recommended action remains integrate, but it should stay bounded to the Browser 2D render substrate lane rather than reshape the core runtime.",,,,,,,ecomfe/zrender,,,,,,,,,,,,BSD-3-Clause,known_from_reference_material,uploaded_reference_docs,,,,,,,,,,Backfilled from canonized Markdown dossier pass on 2026-04-25: 56-ecomfe-zrender-upstream-dossier.md,v6_unified_source_of_truth_pack,,,,,permissive_or_noncopyleft_known,direct_incorporation_ok,The code license is BSD-3-Clause and direct use is allowed. Treat it as a bounded 2D render substrate beneath the reporting stack.,Use directly as a bounded browser-side dependency beneath analytics and reporting layers.,"Typically preserve notices, attribution, and license text where required.",Usually unnecessary unless you later replace a narrow utility layer for product-shaping reasons.,high,standard-notice-review,yes,,,,,,,,,,,,,v6.3_markdown_backfill,Backfilled from canonized Markdown dossier pass on 2026-04-25: 56-ecomfe-zrender-upstream-dossier.md,selected_not_live_permissive_candidate,phase0r_permissive_eval_then_implement,"Phase 1R closed. Retain as a Phase 3R permissive implementation candidate; implement only from its packet authority and the retained-set contract, not by reopening Phase 0R." -,pissang/claygl,https://github.com/pissang/claygl,HyperTwist,,,,,interface / visualization / shell surface,subsystem donor,dependency donor,merge bench,integrate,moderate modification,"Retain the reusable internal layer, but replace shell assumptions and rebind boundaries so it plugs into HyperTwist cleanly.",,"Integrate selected subsystems rather than the whole product. Mine the repo for browser WebGL substrate, picking, controls, compositor behavior, and lightweight scene infrastructure; keep what materially shortens build time, but bind it to HyperTwist-owned data contracts, UI shell, and runtime boundaries.",,Integrate here means: merge bounded support surfaces from this repo into the HyperTwist companion stack.,,,,"the renderer and application shell, scene behavior, camera and control plugins, picking, compositor, and loader surfaces.","Inspect manifests, README/docs, renderer, application, scene, controls, compositor, loader, and core geometry/material modules.","Audit pissang/claygl as a Browser WebGL substrate candidate for HyperTwist. Inspect the renderer and application shell, scene behavior, camera and control plugins, picking, compositor, and loader surfaces. Decide whether the retained value should remain active and what should stay bounded outside the HyperTwist core.",,,,,,,,,,,,,,medium,"Canonized Markdown dossier exists and the repo has been source-backed, but CSV backfill is later than the original v6.3 board generation.",medium,Source-backed dossier exists and the repo has been reconciled into the later Markdown authority stack.,,,,,,,,,,,,HT_browser_support,HT_browser_support_0002,browser / 3D / XR / presentation,"Integrate selectively for HyperTwist. Its source-backed role is a lower-level WebGL substrate beneath browser viewer and analytics surfaces, not a runtime foundation.",HyperTwist,browser / 3D / XR / presentation,integrate,moderate modification,medium,pissang/claygl,,Merge Bench,5.0,"Useful merge bench candidate for HyperTwist, primarily in the 'Browser WebGL substrate' lane; a lower-level WebGL substrate beneath browser viewer and analytics surfaces, not a runtime foundation.",Browser WebGL substrate,Included,P3,"pissang/claygl is placed in Merge Bench for HyperTwist because it provides a lower-level WebGL substrate beneath browser viewer and analytics surfaces, not a runtime foundation. Recommended action remains integrate, but it should stay bounded to the Browser WebGL substrate lane rather than reshape the core runtime.",,,,,,,pissang/claygl,,,,,,,,,,,,BSD-style permissive (see LICENSE),known_from_reference_material,uploaded_reference_docs,,,,,,,,,,Backfilled from canonized Markdown dossier pass on 2026-04-25: 58-pissang-claygl-upstream-dossier.md,v6_unified_source_of_truth_pack,,,,,permissive_or_noncopyleft_known,direct_incorporation_ok,The repo carries a BSD-style permissive license in its LICENSE file and direct use is viable. Treat it as a bounded WebGL substrate rather than a product lane.,Use directly as a bounded browser-side dependency after preserving the upstream license text.,Preserve the exact upstream LICENSE text and notices when redistributed or vendored.,Usually unnecessary unless you later replace a narrow low-level utility layer.,medium,license-text-normalization-review,yes,,,,,,,,,,,,,v6.3_markdown_backfill,Backfilled from canonized Markdown dossier pass on 2026-04-25: 58-pissang-claygl-upstream-dossier.md,selected_not_live_permissive_candidate,phase0r_permissive_eval_then_implement,"Phase 1R closed. Retain as a Phase 3R permissive implementation candidate; implement only from its packet authority and the retained-set contract, not by reopening Phase 0R." -,pissang/clay-viewer,https://github.com/pissang/clay-viewer,HyperTwist,,,,,interface / visualization / shell surface,subsystem donor,viewer donor,merge bench,integrate,moderate modification,"Retain the reusable internal layer, but replace shell assumptions and rebind boundaries so it plugs into HyperTwist cleanly.",,"Integrate selected subsystems rather than the whole product. Mine the repo for browser viewer/editor behavior, hotspot handling, post-effects, lighting presets, and animation-preview support; keep what materially shortens build time, but bind it to HyperTwist-owned data contracts, UI shell, and runtime boundaries.",,Integrate here means: merge bounded support surfaces from this repo into the HyperTwist companion stack.,,,,"the viewer shell, hotspot and picking behavior, default scene config, effect compositor, and animation-preview surfaces.","Inspect manifests, README/docs, viewer runtime, default scene config, graphic effect compositor, and associated editor or UI shells.","Audit pissang/clay-viewer as a Browser viewer and editor sidecar candidate for HyperTwist. Inspect the viewer shell, hotspot and picking behavior, default scene config, effect compositor, and animation-preview surfaces. Decide whether the retained value should remain active and what should stay bounded outside the HyperTwist core.",,,,,,,,,,,,,,medium,"Canonized Markdown dossier exists and the repo has been source-backed, but CSV backfill is later than the original v6.3 board generation.",medium,Source-backed dossier exists and the repo has been reconciled into the later Markdown authority stack.,,,,,,,,,,,,HT_browser_support,HT_browser_support_0003,browser / 3D / XR / presentation,"Integrate selectively for HyperTwist. Its source-backed role is a bounded browser viewer/editor sidecar with hotspot, environment, and post-effect surfaces, not a gameplay or runtime foundation.",HyperTwist,browser / 3D / XR / presentation,integrate,moderate modification,medium,pissang/clay-viewer,,Merge Bench,5.0,"Useful merge bench candidate for HyperTwist, primarily in the 'Browser viewer and editor sidecar' lane; a bounded browser viewer/editor sidecar with hotspot, environment, and post-effect surfaces, not a gameplay or runtime foundation.",Browser viewer and editor sidecar,Included,P3,"pissang/clay-viewer is placed in Merge Bench for HyperTwist because it provides a bounded browser viewer/editor sidecar with hotspot, environment, and post-effect surfaces, not a gameplay or runtime foundation. Recommended action remains integrate, but it should stay bounded to the Browser viewer and editor sidecar lane rather than reshape the core runtime.",,,,,,,pissang/clay-viewer,,,,,,,,,,,,BSD-3-Clause,known_from_reference_material,uploaded_reference_docs,,,,,,,,,,Backfilled from canonized Markdown dossier pass on 2026-04-25: 59-pissang-clay-viewer-upstream-dossier.md,v6_unified_source_of_truth_pack,,,,,permissive_or_noncopyleft_known,direct_incorporation_ok,The code license is BSD-3-Clause and direct use is allowed. Treat it as a bounded browser viewer/editor sidecar.,Use directly as a bounded browser-side dependency or sidecar for viewer/editor surfaces.,"Typically preserve notices, attribution, and license text where required.",Usually unnecessary unless later product-shaping concerns make selective replacement attractive.,high,standard-notice-review,yes,,,,,,,,,,,,,v6.3_markdown_backfill,Backfilled from canonized Markdown dossier pass on 2026-04-25: 59-pissang-clay-viewer-upstream-dossier.md,selected_not_live_permissive_candidate,phase0r_permissive_eval_then_implement,"Phase 1R closed. Retain as a Phase 3R permissive implementation candidate; implement only from its packet authority and the retained-set contract, not by reopening Phase 0R." +,ecomfe/zrender,https://github.com/ecomfe/zrender,HyperTwist,,,,,interface / visualization / shell surface,subsystem donor,dependency donor,merge bench,integrate,moderate modification,"Retain the reusable internal layer, but replace shell assumptions and rebind boundaries so it plugs into HyperTwist cleanly.",,"Integrate selected subsystems rather than the whole product. Mine the repo for 2D rendering, scene-graph, animation, and event-handling substrate behavior beneath browser reporting surfaces; keep what materially shortens build time, but bind it to HyperTwist-owned data contracts, UI shell, and runtime boundaries.",,Integrate here means: merge bounded support surfaces from this repo into the HyperTwist companion stack.,,,,"the zrender runtime entry, scene storage, canvas and SVG painters, handler proxy, and animation behavior.","Inspect manifests, README/docs, runtime entry, storage, painter implementations, event proxy, animation modules, and core graphic primitives.","Audit ecomfe/zrender as a Browser 2D render substrate candidate for HyperTwist. Inspect the zrender runtime entry, scene storage, canvas and SVG painters, handler proxy, and animation behavior. Decide whether the retained value should remain active and what should stay bounded outside the HyperTwist core.",,,,,,,,,,,,,,medium,"Canonized Markdown dossier exists and the repo has been source-backed, but CSV backfill is later than the original v6.3 board generation.",medium,Source-backed dossier exists and the repo has been reconciled into the later Markdown authority stack.,,,,,,,,,,,,HT_browser_support,HT_browser_support_0001,browser / 2D / visualization,"Integrate selectively for HyperTwist. Its source-backed role is a lower-level 2D rendering and interaction substrate beneath echarts, not a separate strategic product lane.",HyperTwist,browser / 2D / visualization,integrate,moderate modification,medium,ecomfe/zrender,,Merge Bench,5.0,"Useful merge bench candidate for HyperTwist, primarily in the 'Browser 2D render substrate' lane; a lower-level 2D rendering and interaction substrate beneath echarts, not a separate strategic product lane.",Browser 2D render substrate,Included,P3,"ecomfe/zrender is placed in Merge Bench for HyperTwist because it provides a lower-level 2D rendering and interaction substrate beneath echarts, not a separate strategic product lane. Recommended action remains integrate, but it should stay bounded to the Browser 2D render substrate lane rather than reshape the core runtime.",,,,,,,ecomfe/zrender,,,,,,,,,,,,BSD-3-Clause,known_from_reference_material,uploaded_reference_docs,,,,,,,,,,Backfilled from canonized Markdown dossier pass on 2026-04-25: 56-ecomfe-zrender-upstream-dossier.md,v6_unified_source_of_truth_pack,,,,,permissive_or_noncopyleft_known,direct_incorporation_ok,The code license is BSD-3-Clause and direct use is allowed. Treat it as a bounded 2D render substrate beneath the reporting stack.,Use directly as a bounded browser-side dependency beneath analytics and reporting layers.,"Typically preserve notices, attribution, and license text where required.",Usually unnecessary unless you later replace a narrow utility layer for product-shaping reasons.,high,standard-notice-review,yes,,,,,,,,,,,,,v6.3_markdown_backfill,Backfilled from canonized Markdown dossier pass on 2026-04-25: 56-ecomfe-zrender-upstream-dossier.md,implemented_live_permissive,landed_permissive_preserve,"Phase 3R-E closed. Preserve as the landed first-party embodied companion, narration, lip-sync, gesture, subtitle, and avatar-embed lane; start future widening from the live-lane audit, then the 3R-E implementation packet, then REPO_LICENSE_TRACKING.md." +,pissang/claygl,https://github.com/pissang/claygl,HyperTwist,,,,,interface / visualization / shell surface,subsystem donor,dependency donor,merge bench,integrate,moderate modification,"Retain the reusable internal layer, but replace shell assumptions and rebind boundaries so it plugs into HyperTwist cleanly.",,"Integrate selected subsystems rather than the whole product. Mine the repo for browser WebGL substrate, picking, controls, compositor behavior, and lightweight scene infrastructure; keep what materially shortens build time, but bind it to HyperTwist-owned data contracts, UI shell, and runtime boundaries.",,Integrate here means: merge bounded support surfaces from this repo into the HyperTwist companion stack.,,,,"the renderer and application shell, scene behavior, camera and control plugins, picking, compositor, and loader surfaces.","Inspect manifests, README/docs, renderer, application, scene, controls, compositor, loader, and core geometry/material modules.","Audit pissang/claygl as a Browser WebGL substrate candidate for HyperTwist. Inspect the renderer and application shell, scene behavior, camera and control plugins, picking, compositor, and loader surfaces. Decide whether the retained value should remain active and what should stay bounded outside the HyperTwist core.",,,,,,,,,,,,,,medium,"Canonized Markdown dossier exists and the repo has been source-backed, but CSV backfill is later than the original v6.3 board generation.",medium,Source-backed dossier exists and the repo has been reconciled into the later Markdown authority stack.,,,,,,,,,,,,HT_browser_support,HT_browser_support_0002,browser / 3D / XR / presentation,"Integrate selectively for HyperTwist. Its source-backed role is a lower-level WebGL substrate beneath browser viewer and analytics surfaces, not a runtime foundation.",HyperTwist,browser / 3D / XR / presentation,integrate,moderate modification,medium,pissang/claygl,,Merge Bench,5.0,"Useful merge bench candidate for HyperTwist, primarily in the 'Browser WebGL substrate' lane; a lower-level WebGL substrate beneath browser viewer and analytics surfaces, not a runtime foundation.",Browser WebGL substrate,Included,P3,"pissang/claygl is placed in Merge Bench for HyperTwist because it provides a lower-level WebGL substrate beneath browser viewer and analytics surfaces, not a runtime foundation. Recommended action remains integrate, but it should stay bounded to the Browser WebGL substrate lane rather than reshape the core runtime.",,,,,,,pissang/claygl,,,,,,,,,,,,BSD-style permissive (see LICENSE),known_from_reference_material,uploaded_reference_docs,,,,,,,,,,Backfilled from canonized Markdown dossier pass on 2026-04-25: 58-pissang-claygl-upstream-dossier.md,v6_unified_source_of_truth_pack,,,,,permissive_or_noncopyleft_known,direct_incorporation_ok,The repo carries a BSD-style permissive license in its LICENSE file and direct use is viable. Treat it as a bounded WebGL substrate rather than a product lane.,Use directly as a bounded browser-side dependency after preserving the upstream license text.,Preserve the exact upstream LICENSE text and notices when redistributed or vendored.,Usually unnecessary unless you later replace a narrow low-level utility layer.,medium,license-text-normalization-review,yes,,,,,,,,,,,,,v6.3_markdown_backfill,Backfilled from canonized Markdown dossier pass on 2026-04-25: 58-pissang-claygl-upstream-dossier.md,implemented_live_permissive,landed_permissive_preserve,"Phase 3R-E closed. Preserve as the landed first-party embodied companion, narration, lip-sync, gesture, subtitle, and avatar-embed lane; start future widening from the live-lane audit, then the 3R-E implementation packet, then REPO_LICENSE_TRACKING.md." +,pissang/clay-viewer,https://github.com/pissang/clay-viewer,HyperTwist,,,,,interface / visualization / shell surface,subsystem donor,viewer donor,merge bench,integrate,moderate modification,"Retain the reusable internal layer, but replace shell assumptions and rebind boundaries so it plugs into HyperTwist cleanly.",,"Integrate selected subsystems rather than the whole product. Mine the repo for browser viewer/editor behavior, hotspot handling, post-effects, lighting presets, and animation-preview support; keep what materially shortens build time, but bind it to HyperTwist-owned data contracts, UI shell, and runtime boundaries.",,Integrate here means: merge bounded support surfaces from this repo into the HyperTwist companion stack.,,,,"the viewer shell, hotspot and picking behavior, default scene config, effect compositor, and animation-preview surfaces.","Inspect manifests, README/docs, viewer runtime, default scene config, graphic effect compositor, and associated editor or UI shells.","Audit pissang/clay-viewer as a Browser viewer and editor sidecar candidate for HyperTwist. Inspect the viewer shell, hotspot and picking behavior, default scene config, effect compositor, and animation-preview surfaces. Decide whether the retained value should remain active and what should stay bounded outside the HyperTwist core.",,,,,,,,,,,,,,medium,"Canonized Markdown dossier exists and the repo has been source-backed, but CSV backfill is later than the original v6.3 board generation.",medium,Source-backed dossier exists and the repo has been reconciled into the later Markdown authority stack.,,,,,,,,,,,,HT_browser_support,HT_browser_support_0003,browser / 3D / XR / presentation,"Integrate selectively for HyperTwist. Its source-backed role is a bounded browser viewer/editor sidecar with hotspot, environment, and post-effect surfaces, not a gameplay or runtime foundation.",HyperTwist,browser / 3D / XR / presentation,integrate,moderate modification,medium,pissang/clay-viewer,,Merge Bench,5.0,"Useful merge bench candidate for HyperTwist, primarily in the 'Browser viewer and editor sidecar' lane; a bounded browser viewer/editor sidecar with hotspot, environment, and post-effect surfaces, not a gameplay or runtime foundation.",Browser viewer and editor sidecar,Included,P3,"pissang/clay-viewer is placed in Merge Bench for HyperTwist because it provides a bounded browser viewer/editor sidecar with hotspot, environment, and post-effect surfaces, not a gameplay or runtime foundation. Recommended action remains integrate, but it should stay bounded to the Browser viewer and editor sidecar lane rather than reshape the core runtime.",,,,,,,pissang/clay-viewer,,,,,,,,,,,,BSD-3-Clause,known_from_reference_material,uploaded_reference_docs,,,,,,,,,,Backfilled from canonized Markdown dossier pass on 2026-04-25: 59-pissang-clay-viewer-upstream-dossier.md,v6_unified_source_of_truth_pack,,,,,permissive_or_noncopyleft_known,direct_incorporation_ok,The code license is BSD-3-Clause and direct use is allowed. Treat it as a bounded browser viewer/editor sidecar.,Use directly as a bounded browser-side dependency or sidecar for viewer/editor surfaces.,"Typically preserve notices, attribution, and license text where required.",Usually unnecessary unless later product-shaping concerns make selective replacement attractive.,high,standard-notice-review,yes,,,,,,,,,,,,,v6.3_markdown_backfill,Backfilled from canonized Markdown dossier pass on 2026-04-25: 59-pissang-clay-viewer-upstream-dossier.md,implemented_live_permissive,landed_permissive_preserve,"Phase 3R-E closed. Preserve as the landed first-party embodied companion, narration, lip-sync, gesture, subtitle, and avatar-embed lane; start future widening from the live-lane audit, then the 3R-E implementation packet, then REPO_LICENSE_TRACKING.md." ,KhronosGroup/glTF-Sample-Renderer,https://github.com/KhronosGroup/glTF-Sample-Renderer,HyperTwist,,,,,interface / visualization / shell surface,subsystem donor,dependency donor,merge bench,integrate,moderate modification,"Retain the reusable internal layer, but replace shell assumptions and rebind boundaries so it plugs into HyperTwist cleanly.",,"Integrate selected subsystems rather than the whole product. Mine the repo for standards-aware glTF loading, renderer substrate, camera state, and resource-loading behavior beneath asset viewers; keep what materially shortens build time, but bind it to HyperTwist-owned data contracts, UI shell, and runtime boundaries.",,Integrate here means: merge bounded support surfaces from this repo into the HyperTwist companion stack.,,,,"the GltfView and GltfState API surface, resource loader, renderer core, and user-camera behavior.","Inspect manifests, README/docs, renderer source tree, resource loader, GltfView, GltfState, user camera, and renderer integration points.","Audit KhronosGroup/glTF-Sample-Renderer as a Browser asset renderer substrate candidate for HyperTwist. Inspect the GltfView and GltfState API surface, resource loader, renderer core, and user-camera behavior. Decide whether the retained value should remain active and what should stay bounded outside the HyperTwist core.",,,,,,,,,,,,,,medium,"Canonized Markdown dossier exists and the repo has been source-backed, but CSV backfill is later than the original v6.3 board generation.",medium,Source-backed dossier exists and the repo has been reconciled into the later Markdown authority stack.,,,,,,,,,,,,HT_browser_support,HT_browser_support_0004,browser / 3D / XR / presentation,"Integrate selectively for HyperTwist. Its source-backed role is the lower-level official glTF renderer substrate beneath glTF-Sample-Viewer, not a separate strategic lane.",HyperTwist,browser / 3D / XR / presentation,integrate,moderate modification,medium,khronosgroup/gltf-sample-renderer,,Merge Bench,5.0,"Useful merge bench candidate for HyperTwist, primarily in the 'Browser asset renderer substrate' lane; the lower-level official glTF renderer substrate beneath glTF-Sample-Viewer, not a separate strategic lane.",Browser asset renderer substrate,Included,P3,"KhronosGroup/glTF-Sample-Renderer is placed in Merge Bench for HyperTwist because it provides the lower-level official glTF renderer substrate beneath glTF-Sample-Viewer, not a separate strategic lane. Recommended action remains integrate, but it should stay bounded to the Browser asset renderer substrate lane rather than reshape the core runtime.",,,,,,,khronosgroup/gltf-sample-renderer,,,,,,,,,,,,Apache-2.0,known_from_reference_material,uploaded_reference_docs,,,,,,,,,,Backfilled from canonized Markdown dossier pass on 2026-04-25: 61-khronosgroup-gltf-sample-renderer-upstream-dossier.md,v6_unified_source_of_truth_pack,,,,,permissive_or_noncopyleft_known,direct_incorporation_ok,The code license is Apache-2.0 and direct use is allowed. Treat it as a bounded renderer substrate beneath asset viewers.,Use directly as a bounded browser-side dependency beneath asset inspection and preview tooling.,Preserve LICENSE and NOTICE materials where required.,Usually unnecessary unless later product-shaping concerns make selective replacement attractive.,high,notice-file-review,yes,,,,,,,,,,,,,v6.3_markdown_backfill,Backfilled from canonized Markdown dossier pass on 2026-04-25: 61-khronosgroup-gltf-sample-renderer-upstream-dossier.md,selected_not_live_permissive_candidate,phase0r_permissive_eval_then_implement,"Phase 3R-D closed for the anchor. Retain as the subordinate renderer/reference substrate beneath the landed google/model-viewer asset-QA lane; do not treat it as separately live." ,google/model-viewer/packages/space-opera,https://github.com/google/model-viewer/tree/main/packages/space-opera,HyperTwist,,,,,interface / visualization / shell surface,subsystem donor,editor donor,merge bench,integrate,moderate modification,"Retain the reusable internal layer, but replace shell assumptions and rebind boundaries so it plugs into HyperTwist cleanly.",,"Integrate selected subsystems rather than the whole product. Mine the repo for browser editor, inspection, hotspot editing, snippet export, and lightweight asset-authoring behavior; keep what materially shortens build time, but bind it to HyperTwist-owned data contracts, UI shell, and runtime boundaries.",,Integrate here means: merge bounded support surfaces from this repo into the HyperTwist companion stack.,,,,"the app shell, reducer and state structure, hotspot editing flow, snippet export surfaces, and inspector behavior.","Inspect manifests, README/docs, app shell, reducers, hotspot panel, snippet generator, inspector components, and editor-adjacent modules.","Audit google/model-viewer/packages/space-opera as a Browser asset editor and inspection surface candidate for HyperTwist. Inspect the app shell, reducer and state structure, hotspot editing flow, snippet export surfaces, and inspector behavior. Decide whether the retained value should remain active and what should stay bounded outside the HyperTwist core.",,,,,,,,,,,,,,medium,"Canonized Markdown dossier exists and the repo has been source-backed, but CSV backfill is later than the original v6.3 board generation.",medium,Source-backed dossier exists and the repo has been reconciled into the later Markdown authority stack.,,,,,,,,,,,,HT_browser_support,HT_browser_support_0005,browser / 3D / XR / presentation,"Integrate selectively for HyperTwist. Its source-backed role is a bounded browser editor and inspection donor beneath model-viewer, not a standalone product lane.",HyperTwist,browser / 3D / XR / presentation,integrate,moderate modification,medium,google/model-viewer/packages/space-opera,,Merge Bench,5.0,"Useful merge bench candidate for HyperTwist, primarily in the 'Browser asset editor and inspection surface' lane; a bounded browser editor and inspection donor beneath model-viewer, not a standalone product lane.",Browser asset editor and inspection surface,Included,P3,"google/model-viewer/packages/space-opera is placed in Merge Bench for HyperTwist because it provides a bounded browser editor and inspection donor beneath model-viewer, not a standalone product lane. Recommended action remains integrate, but it should stay bounded to the Browser asset editor and inspection surface lane rather than reshape the core runtime.",,,,,,,google/model-viewer/packages/space-opera,,,,,,,,,,,,Apache-2.0,known_from_reference_material,uploaded_reference_docs,,,,,,,,,,Backfilled from canonized Markdown dossier pass on 2026-04-25: 63-google-space-opera-upstream-dossier.md,v6_unified_source_of_truth_pack,,,,,permissive_or_noncopyleft_known,direct_incorporation_ok,The code license is Apache-2.0 and direct use is allowed. Treat it as a bounded browser editor and inspection donor beneath model-viewer.,Use directly as a bounded browser-side dependency or concept donor beneath browser asset tooling.,Preserve LICENSE and NOTICE materials where required.,Usually unnecessary unless later product-shaping concerns make selective replacement attractive.,high,notice-file-review,yes,,,,,,,,,,,,,v6.3_markdown_backfill,Backfilled from canonized Markdown dossier pass on 2026-04-25: 63-google-space-opera-upstream-dossier.md,selected_not_live_permissive_candidate,phase0r_permissive_eval_then_implement,"Phase 3R-D closed for the anchor. Retain as the subordinate browser editor and inspection package beneath the landed google/model-viewer lane; do not treat it as separately live." ,google/model-viewer/packages/render-fidelity-tools,https://github.com/google/model-viewer/tree/main/packages/render-fidelity-tools,HyperTwist,,,,,analytics / visualization / reporting,subsystem donor,qa donor,merge bench,integrate,moderate modification,"Retain the reusable internal layer, but replace shell assumptions and rebind boundaries so it plugs into HyperTwist cleanly.",,"Integrate selected subsystems rather than the whole product. Mine the repo for browser visual-regression workflows, golden rendering, fidelity thresholds, and harness configuration behavior; keep what materially shortens build time, but bind it to HyperTwist-owned data contracts, UI shell, and runtime boundaries.",,Integrate here means: merge bounded support surfaces from this repo into the HyperTwist companion stack.,,,,"the test-fidelity and render-goldens workflows, renderer harness behavior, image-comparison worker, and artifact generation.","Inspect manifests, README/docs, workflow scripts, renderer harness, image comparison worker, and fidelity-testing utilities.","Audit google/model-viewer/packages/render-fidelity-tools as a Browser fidelity QA harness candidate for HyperTwist. Inspect the test-fidelity and render-goldens workflows, renderer harness behavior, image-comparison worker, and artifact generation. Decide whether the retained value should remain active and what should stay bounded outside the HyperTwist core.",,,,,,,,,,,,,,medium,"Canonized Markdown dossier exists and the repo has been source-backed, but CSV backfill is later than the original v6.3 board generation.",medium,Source-backed dossier exists and the repo has been reconciled into the later Markdown authority stack.,,,,,,,,,,,,HT_browser_support,HT_browser_support_0006,browser / QA / visual regression,"Integrate selectively for HyperTwist. Its source-backed role is a bounded fidelity oracle and QA harness donor beneath model-viewer, not a runtime lane.",HyperTwist,browser / QA / visual regression,integrate,moderate modification,medium,google/model-viewer/packages/render-fidelity-tools,,Merge Bench,5.0,"Useful merge bench candidate for HyperTwist, primarily in the 'Browser fidelity QA harness' lane; a bounded fidelity oracle and QA harness donor beneath model-viewer, not a runtime lane.",Browser fidelity QA harness,Included,P3,"google/model-viewer/packages/render-fidelity-tools is placed in Merge Bench for HyperTwist because it provides a bounded fidelity oracle and QA harness donor beneath model-viewer, not a runtime lane. Recommended action remains integrate, but it should stay bounded to the Browser fidelity QA harness lane rather than reshape the core runtime.",,,,,,,google/model-viewer/packages/render-fidelity-tools,,,,,,,,,,,,Apache-2.0,known_from_reference_material,uploaded_reference_docs,,,,,,,,,,Backfilled from canonized Markdown dossier pass on 2026-04-25: 64-google-render-fidelity-tools-upstream-dossier.md,v6_unified_source_of_truth_pack,,,,,permissive_or_noncopyleft_known,direct_incorporation_ok,The code license is Apache-2.0 and direct use is allowed. Treat it as a bounded QA and fidelity-testing donor.,Use directly as a bounded browser-side QA dependency or concept donor for visual regression tooling.,Preserve LICENSE and NOTICE materials where required.,Usually unnecessary unless later product-shaping concerns make selective replacement attractive.,high,notice-file-review,yes,,,,,,,,,,,,,v6.3_markdown_backfill,Backfilled from canonized Markdown dossier pass on 2026-04-25: 64-google-render-fidelity-tools-upstream-dossier.md,selected_not_live_permissive_candidate,phase0r_permissive_eval_then_implement,"Phase 3R-D closed for the anchor. Retain as the subordinate fidelity-oracle and regression sidecar beneath the landed google/model-viewer lane; do not treat it as separately live." ,google/model-viewer/packages/model-viewer-effects,https://github.com/google/model-viewer/tree/main/packages/model-viewer-effects,HyperTwist,,,,,interface / visualization / shell surface,subsystem donor,effect donor,merge bench,integrate,moderate modification,"Retain the reusable internal layer, but replace shell assumptions and rebind boundaries so it plugs into HyperTwist cleanly.",,"Integrate selected subsystems rather than the whole product. Mine the repo for browser emphasis, outline and SSAO behavior, and effect-composer integration beneath browser model presentation; keep what materially shortens build time, but bind it to HyperTwist-owned data contracts, UI shell, and runtime boundaries.",,Integrate here means: merge bounded support surfaces from this repo into the HyperTwist companion stack.,,,,"the effect-composer integration, custom-element surface, outline effect, SSAO effect, and emphasis behavior.","Inspect manifests, README/docs, effect-composer integration, custom-element wrapper, outline and SSAO effects, and related extension code.","Audit google/model-viewer/packages/model-viewer-effects as a Browser emphasis and post-processing extension candidate for HyperTwist. Inspect the effect-composer integration, custom-element surface, outline effect, SSAO effect, and emphasis behavior. Decide whether the retained value should remain active and what should stay bounded outside the HyperTwist core.",,,,,,,,,,,,,,medium,"Canonized Markdown dossier exists and the repo has been source-backed, but CSV backfill is later than the original v6.3 board generation.",medium,Source-backed dossier exists and the repo has been reconciled into the later Markdown authority stack.,,,,,,,,,,,,HT_browser_support,HT_browser_support_0007,browser / 3D / XR / presentation,"Integrate selectively for HyperTwist. Its source-backed role is a bounded browser post-processing and emphasis donor beneath model-viewer, not a standalone product lane.",HyperTwist,browser / 3D / XR / presentation,integrate,moderate modification,medium,google/model-viewer/packages/model-viewer-effects,,Merge Bench,5.0,"Useful merge bench candidate for HyperTwist, primarily in the 'Browser emphasis and post-processing extension' lane; a bounded browser post-processing and emphasis donor beneath model-viewer, not a standalone product lane.",Browser emphasis and post-processing extension,Included,P3,"google/model-viewer/packages/model-viewer-effects is placed in Merge Bench for HyperTwist because it provides a bounded browser post-processing and emphasis donor beneath model-viewer, not a standalone product lane. Recommended action remains integrate, but it should stay bounded to the Browser emphasis and post-processing extension lane rather than reshape the core runtime.",,,,,,,google/model-viewer/packages/model-viewer-effects,,,,,,,,,,,,Apache-2.0,known_from_reference_material,uploaded_reference_docs,,,,,,,,,,Backfilled from canonized Markdown dossier pass on 2026-04-25: 65-google-model-viewer-effects-upstream-dossier.md,v6_unified_source_of_truth_pack,,,,,permissive_or_noncopyleft_known,direct_incorporation_ok,The code license is Apache-2.0 and direct use is allowed. Treat it as a bounded browser emphasis and effect donor beneath model-viewer.,Use directly as a bounded browser-side dependency or concept donor beneath browser model presentation.,Preserve LICENSE and NOTICE materials where required.,Usually unnecessary unless later product-shaping concerns make selective replacement attractive.,high,notice-file-review,yes,,,,,,,,,,,,,v6.3_markdown_backfill,Backfilled from canonized Markdown dossier pass on 2026-04-25: 65-google-model-viewer-effects-upstream-dossier.md,selected_not_live_permissive_candidate,phase0r_permissive_eval_then_implement,"Phase 3R-D closed for the anchor. Retain as a subordinate emphasis and effects package beneath the landed google/model-viewer lane; do not treat it as separately live." ,google/model-viewer/packages/modelviewer.dev,https://github.com/google/model-viewer/tree/main/packages/modelviewer.dev,HyperTwist,,,,,interface / visualization / shell surface,subsystem donor,docs donor,merge bench,integrate,moderate modification,"Retain the reusable internal layer, but replace shell assumptions and rebind boundaries so it plugs into HyperTwist cleanly.",,"Integrate selected subsystems rather than the whole product. Mine the repo for live docs and demo generation, snippet-to-demo coupling, and documentation information architecture; keep what materially shortens build time, but bind it to HyperTwist-owned data contracts, UI shell, and runtime boundaries.",,Integrate here means: merge bounded support surfaces from this repo into the HyperTwist companion stack.,,,,"the docs-and-examples flow, example-snippet behavior, sidebar generation, and HTML generation surfaces.","Inspect manifests, README/docs, docs-and-examples code, example-snippet component, sidebar builder, and HTML generation utilities.","Audit google/model-viewer/packages/modelviewer.dev as a Browser docs and demo surface candidate for HyperTwist. Inspect the docs-and-examples flow, example-snippet behavior, sidebar generation, and HTML generation surfaces. Decide whether the retained value should remain active and what should stay bounded outside the HyperTwist core.",,,,,,,,,,,,,,medium,"Canonized Markdown dossier exists and the repo has been source-backed, but CSV backfill is later than the original v6.3 board generation.",medium,Source-backed dossier exists and the repo has been reconciled into the later Markdown authority stack.,,,,,,,,,,,,HT_browser_support,HT_browser_support_0008,documentation / demos / examples,"Integrate selectively for HyperTwist. Its source-backed role is a bounded docs and demo donor beneath model-viewer, not a runtime lane.",HyperTwist,documentation / demos / examples,integrate,moderate modification,medium,google/model-viewer/packages/modelviewer.dev,,Merge Bench,5.0,"Useful merge bench candidate for HyperTwist, primarily in the 'Browser docs and demo surface' lane; a bounded docs and demo donor beneath model-viewer, not a runtime lane.",Browser docs and demo surface,Included,P4,"google/model-viewer/packages/modelviewer.dev is placed in Merge Bench for HyperTwist because it provides a bounded docs and demo donor beneath model-viewer, not a runtime lane. Recommended action remains integrate, but it should stay bounded to the Browser docs and demo surface lane rather than reshape the core runtime.",,,,,,,google/model-viewer/packages/modelviewer.dev,,,,,,,,,,,,Apache-2.0,known_from_reference_material,uploaded_reference_docs,,,,,,,,,,Backfilled from canonized Markdown dossier pass on 2026-04-25: 66-google-modelviewer-dev-upstream-dossier.md,v6_unified_source_of_truth_pack,,,,,permissive_or_noncopyleft_known,direct_incorporation_ok,The code license is Apache-2.0 and direct use is allowed. Treat it as a bounded docs and demo donor.,Use directly as a bounded docs/demo dependency or concept donor for documentation surfaces.,Preserve LICENSE and NOTICE materials where required.,Usually unnecessary unless later product-shaping concerns make selective replacement attractive.,high,notice-file-review,yes,,,,,,,,,,,,,v6.3_markdown_backfill,Backfilled from canonized Markdown dossier pass on 2026-04-25: 66-google-modelviewer-dev-upstream-dossier.md,selected_not_live_permissive_candidate,phase0r_permissive_eval_then_implement,"Phase 3R-D closed for the anchor. Retain as subordinate docs and demo infrastructure beneath the landed google/model-viewer lane; do not treat it as separately live or as a product-shell owner." ,google/model-viewer/packages/shared-assets,https://github.com/google/model-viewer/tree/main/packages/shared-assets,HyperTwist,,,,,asset / fixture / sample pack,subsystem donor,fixture donor,donor bench,repurpose,architecture only,"Retain the reusable internal layer, but replace shell assumptions and rebind boundaries so it plugs into HyperTwist cleanly.",,"Integrate selected subsystems rather than the whole product. Mine the repo for sample-model and environment-fixture selection, visual QA assets, and per-asset provenance handling; keep what materially shortens build time, but bind it to HyperTwist-owned data contracts, UI shell, and runtime boundaries.",,Integrate here means: merge bounded support surfaces from this repo into the HyperTwist companion stack.,,,,"the attribution file, mixed per-asset terms, sample-model and environment fixture role, and fetch-script behavior.","Inspect manifests, README/docs, LICENSE, ATTRIBUTIONS, fixture assets, and asset-fetch scripts. Verify container license versus per-asset terms.","Audit google/model-viewer/packages/shared-assets as a Browser sample-asset and fixture pack candidate for HyperTwist. Inspect the attribution file, mixed per-asset terms, sample-model and environment fixture role, and fetch-script behavior. Decide whether the retained value should remain active and what should stay bounded outside the HyperTwist core.",,,,,,,,,,,,,,medium,"Canonized Markdown dossier exists and the repo has been source-backed, but CSV backfill is later than the original v6.3 board generation.",medium,Source-backed dossier exists and the repo has been reconciled into the later Markdown authority stack.,,,,,,,,,,,,HT_browser_support,HT_browser_support_0009,asset / fixture / sample pack,"Integrate selectively for HyperTwist. Its source-backed role is a boundary-sensitive sample-asset and test-fixture pack with mixed per-asset terms, not a blanket shippable asset bundle.",HyperTwist,asset / fixture / sample pack,integrate,moderate modification,medium,google/model-viewer/packages/shared-assets,,Donor Bench,5.0,"Mixed-provenance assets are still useful for fixtures and QA, but they should not sit in an active merge posture.",Boundary-sensitive sample-asset and test-fixture pack,Included,P3,"Keep as a bounded fixture pack for local viewer tests, environment-lighting checks, and docs/examples, not as a normal code donor or blanket shippable asset source.",,,,,,,google/model-viewer/packages/shared-assets,,,,,,,,,,,,Apache-2.0 container; mixed per-asset terms,known_from_reference_material,uploaded_reference_docs,,,,,,,,,,Backfilled from canonized Markdown dossier pass on 2026-04-25: 67-google-shared-assets-upstream-dossier.md,v6_unified_source_of_truth_pack,,,,,mixed_or_boundary_sensitive_known,bounded_sidecar_or_selective_reimplementation,"The package container is Apache-2.0, but the actual payloads carry mixed per-asset terms. Treat it as a whitelisted fixture pack, not a blanket shippable asset source.",Whitelist individual acceptable assets only; do not assume the container license overrides per-asset terms.,Preserve container notices and review each selected asset attribution or usage condition separately before shipping.,"Usually unnecessary; the main issue is per-asset provenance and selection, not code replacement.",high,mixed-asset-whitelist-review,no,,,,,,,,,,,,,v6.3_markdown_backfill,Corrected on 2026-04-25 from stale merge posture to dossier-backed boundary-sensitive fixture-pack status.,selected_not_live_boundary_sensitive,phase0r_boundary_sensitive_eval_then_adapter_or_sidecar,Phase 1R closed. Retain as a Phase 4R fixture and QA pack only; allowlist each asset before any shipping use. -,pmndrs/react-postprocessing,https://github.com/pmndrs/react-postprocessing,HyperTwist,,,,,interface / visualization / shell surface,subsystem donor,dependency donor,merge bench,integrate,moderate modification,"Retain the reusable internal layer, but replace shell assumptions and rebind boundaries so it plugs into HyperTwist cleanly.",,"Integrate selected subsystems rather than the whole product. Mine the repo for React-side effect orchestration, selection-based emphasis behavior, and wrapper ergonomics above browser post-processing; keep what materially shortens build time, but bind it to HyperTwist-owned data contracts, UI shell, and runtime boundaries.",,Integrate here means: merge bounded support surfaces from this repo into the HyperTwist companion stack.,,,,"the React EffectComposer wrapper, Selection model, and integration assumptions on top of postprocessing and react-three-fiber.","Inspect manifests, README/docs, EffectComposer wrapper, Selection support, and the narrow React integration layer.","Audit pmndrs/react-postprocessing as a Browser React effect-wrapper layer candidate for HyperTwist. Inspect the React EffectComposer wrapper, Selection model, and integration assumptions on top of postprocessing and react-three-fiber. Decide whether the retained value should remain active and what should stay bounded outside the HyperTwist core.",,,,,,,,,,,,,,medium,"Canonized Markdown dossier exists and the repo has been source-backed, but CSV backfill is later than the original v6.3 board generation.",medium,Source-backed dossier exists and the repo has been reconciled into the later Markdown authority stack.,,,,,,,,,,,,HT_browser_support,HT_browser_support_0010,browser / 3D / XR / presentation,"Integrate selectively for HyperTwist. Its source-backed role is a bounded React wrapper for the browser post-processing lane, not a standalone product lane.",HyperTwist,browser / 3D / XR / presentation,integrate,moderate modification,medium,pmndrs/react-postprocessing,,Merge Bench,5.0,"Useful merge bench candidate for HyperTwist, primarily in the 'Browser React effect-wrapper layer' lane; a bounded React wrapper for the browser post-processing lane, not a standalone product lane.",Browser React effect-wrapper layer,Included,P4,"pmndrs/react-postprocessing is placed in Merge Bench for HyperTwist because it provides a bounded React wrapper for the browser post-processing lane, not a standalone product lane. Recommended action remains integrate, but it should stay bounded to the Browser React effect-wrapper layer lane rather than reshape the core runtime.",,,,,,,pmndrs/react-postprocessing,,,,,,,,,,,,MIT,known_from_reference_material,uploaded_reference_docs,,,,,,,,,,Backfilled from canonized Markdown dossier pass on 2026-04-25: 70-pmndrs-react-postprocessing-upstream-dossier.md,v6_unified_source_of_truth_pack,,,,,permissive_or_noncopyleft_known,direct_incorporation_ok,The code license is MIT and direct use is allowed. Treat it as a bounded React wrapper layer above browser post-processing.,Use directly as a bounded browser-side wrapper dependency above the core post-processing substrate.,"Typically preserve notices, attribution, and license text where required.",Usually unnecessary unless later product-shaping concerns make selective replacement attractive.,high,standard-notice-review,yes,,,,,,,,,,,,,v6.3_markdown_backfill,Backfilled from canonized Markdown dossier pass on 2026-04-25: 70-pmndrs-react-postprocessing-upstream-dossier.md,selected_not_live_permissive_candidate,phase0r_permissive_eval_then_implement,"Phase 1R closed. Retain as a Phase 3R permissive implementation candidate; implement only from its packet authority and the retained-set contract, not by reopening Phase 0R." -,pmndrs/three-stdlib,https://github.com/pmndrs/three-stdlib,HyperTwist,,,,,interface / visualization / shell surface,subsystem donor,dependency donor,merge bench,integrate,moderate modification,"Retain the reusable internal layer, but replace shell assumptions and rebind boundaries so it plugs into HyperTwist cleanly.",,"Integrate selected subsystems rather than the whole product. Mine the repo for browser-side utility helpers, controls, loaders, and XR-adjacent primitives beneath the browser companion stack; keep what materially shortens build time, but bind it to HyperTwist-owned data contracts, UI shell, and runtime boundaries.",,Integrate here means: merge bounded support surfaces from this repo into the HyperTwist companion stack.,,,,"the utility export surface, controls, loaders, WebXR helpers, post-processing helpers, and packaging of three/examples behavior.","Inspect manifests, README/docs, utility index, controls, WebXR helpers, loaders, and exported utility modules.","Audit pmndrs/three-stdlib as a Browser 3D utility substrate candidate for HyperTwist. Inspect the utility export surface, controls, loaders, WebXR helpers, post-processing helpers, and packaging of three/examples behavior. Decide whether the retained value should remain active and what should stay bounded outside the HyperTwist core.",,,,,,,,,,,,,,medium,"Canonized Markdown dossier exists and the repo has been source-backed, but CSV backfill is later than the original v6.3 board generation.",medium,Source-backed dossier exists and the repo has been reconciled into the later Markdown authority stack.,,,,,,,,,,,,HT_browser_support,HT_browser_support_0011,browser / 3D / XR / presentation,"Integrate selectively for HyperTwist. Its source-backed role is a lower-level browser utility substrate beneath three.js, drei, and XR-adjacent lanes, not a product lane.",HyperTwist,browser / 3D / XR / presentation,integrate,moderate modification,medium,pmndrs/three-stdlib,,Merge Bench,5.0,"Useful merge bench candidate for HyperTwist, primarily in the 'Browser 3D utility substrate' lane; a lower-level browser utility substrate beneath three.js, drei, and XR-adjacent lanes, not a product lane.",Browser 3D utility substrate,Included,P4,"pmndrs/three-stdlib is placed in Merge Bench for HyperTwist because it provides a lower-level browser utility substrate beneath three.js, drei, and XR-adjacent lanes, not a product lane. Recommended action remains integrate, but it should stay bounded to the Browser 3D utility substrate lane rather than reshape the core runtime.",,,,,,,pmndrs/three-stdlib,,,,,,,,,,,,MIT,known_from_reference_material,uploaded_reference_docs,,,,,,,,,,Backfilled from canonized Markdown dossier pass on 2026-04-25: 75-pmndrs-three-stdlib-upstream-dossier.md,v6_unified_source_of_truth_pack,,,,,permissive_or_noncopyleft_known,direct_incorporation_ok,The code license is MIT and direct use is allowed. Treat it as a bounded utility substrate beneath three.js-adjacent browser lanes.,Use directly as a bounded browser-side utility dependency beneath higher-level viewer and XR layers.,"Typically preserve notices, attribution, and license text where required.",Usually unnecessary unless later product-shaping concerns make selective replacement attractive.,high,standard-notice-review,yes,,,,,,,,,,,,,v6.3_markdown_backfill,Backfilled from canonized Markdown dossier pass on 2026-04-25: 75-pmndrs-three-stdlib-upstream-dossier.md,selected_not_live_permissive_candidate,phase0r_permissive_eval_then_implement,"Phase 1R closed. Retain as a Phase 3R permissive implementation candidate; implement only from its packet authority and the retained-set contract, not by reopening Phase 0R." -,pmndrs/maath,https://github.com/pmndrs/maath,HyperTwist,,,,,interface / visualization / shell surface,subsystem donor,dependency donor,merge bench,integrate,moderate modification,"Retain the reusable internal layer, but replace shell assumptions and rebind boundaries so it plugs into HyperTwist cleanly.",,"Integrate selected subsystems rather than the whole product. Mine the repo for browser-side easing, damping, sampling, and geometry helper behavior beneath interactive surfaces; keep what materially shortens build time, but bind it to HyperTwist-owned data contracts, UI shell, and runtime boundaries.",,Integrate here means: merge bounded support surfaces from this repo into the HyperTwist companion stack.,,,,"the easing runtime, random helpers, geometry utilities, and three.js-oriented math surfaces.","Inspect manifests, README/docs, math package exports, easing, geometry, and random helper modules.","Audit pmndrs/maath as a Browser math-helper substrate candidate for HyperTwist. Inspect the easing runtime, random helpers, geometry utilities, and three.js-oriented math surfaces. Decide whether the retained value should remain active and what should stay bounded outside the HyperTwist core.",,,,,,,,,,,,,,medium,"Canonized Markdown dossier exists and the repo has been source-backed, but CSV backfill is later than the original v6.3 board generation.",medium,Source-backed dossier exists and the repo has been reconciled into the later Markdown authority stack.,,,,,,,,,,,,HT_browser_support,HT_browser_support_0012,browser / utilities / math,"Integrate selectively for HyperTwist. Its source-backed role is a lower-level browser math-helper substrate beneath viewer and XR-adjacent lanes, not a product lane.",HyperTwist,browser / utilities / math,integrate,moderate modification,medium,pmndrs/maath,,Merge Bench,5.0,"Useful merge bench candidate for HyperTwist, primarily in the 'Browser math-helper substrate' lane; a lower-level browser math-helper substrate beneath viewer and XR-adjacent lanes, not a product lane.",Browser math-helper substrate,Included,P4,"pmndrs/maath is placed in Merge Bench for HyperTwist because it provides a lower-level browser math-helper substrate beneath viewer and XR-adjacent lanes, not a product lane. Recommended action remains integrate, but it should stay bounded to the Browser math-helper substrate lane rather than reshape the core runtime.",,,,,,,pmndrs/maath,,,,,,,,,,,,MIT,known_from_reference_material,uploaded_reference_docs,,,,,,,,,,Backfilled from canonized Markdown dossier pass on 2026-04-25: 76-pmndrs-maath-upstream-dossier.md,v6_unified_source_of_truth_pack,,,,,permissive_or_noncopyleft_known,direct_incorporation_ok,The code license is MIT and direct use is allowed. Treat it as a bounded math-helper substrate.,Use directly as a bounded browser-side utility dependency beneath higher-level interactive layers.,"Typically preserve notices, attribution, and license text where required.",Usually unnecessary unless later product-shaping concerns make selective replacement attractive.,high,standard-notice-review,yes,,,,,,,,,,,,,v6.3_markdown_backfill,Backfilled from canonized Markdown dossier pass on 2026-04-25: 76-pmndrs-maath-upstream-dossier.md,selected_not_live_permissive_candidate,phase0r_permissive_eval_then_implement,"Phase 1R closed. Retain as a Phase 3R permissive implementation candidate; implement only from its packet authority and the retained-set contract, not by reopening Phase 0R." -,pmndrs/zustand,https://github.com/pmndrs/zustand,HyperTwist,,,,,interface / visualization / shell surface,subsystem donor,dependency donor,donor bench,repurpose,moderate modification,"Retain the valuable internal layer, but expect to replace upstream shell assumptions and rebind boundaries so it fits the HyperTwist architecture.",,"Repurpose selected subsystems rather than the whole product. Mine the repo for browser-side state management, selector subscriptions, hydration, and bridging between non-React logic and React views; keep what materially shortens build time, but bind it to HyperTwist-owned data contracts, UI shell, and runtime boundaries.",,Repurpose here means: extract bounded support surfaces from this repo without inheriting the full upstream shell.,,,,"the vanilla store kernel, React bridge, selector subscriptions, persist middleware, devtools integration, and equality-aware selection behavior.","Inspect manifests, README/docs, vanilla store, react bindings, traditional selector helpers, and middleware modules.","Audit pmndrs/zustand as a Browser state-management substrate candidate for HyperTwist. Inspect the vanilla store kernel, React bridge, selector subscriptions, persist middleware, devtools integration, and equality-aware selection behavior. Decide whether the retained value should remain active and what should stay bounded outside the HyperTwist core.",,,,,,,,,,,,,,medium,"Canonized Markdown dossier exists and the repo has been source-backed, but CSV backfill is later than the original v6.3 board generation.",medium,Source-backed dossier exists and the repo has been reconciled into the later Markdown authority stack.,,,,,,,,,,,,HT_browser_support,HT_browser_support_0013,browser / state / interaction,"Repurpose selectively for HyperTwist. Its source-backed role is a commodity strategic dependency for browser-side state management and selector subscriptions, not product differentiation.",HyperTwist,browser / state / interaction,repurpose,moderate modification,medium,pmndrs/zustand,,Donor Bench,4.0,"Useful donor bench candidate for HyperTwist, primarily in the 'Browser state-management substrate' lane; a commodity strategic dependency for browser-side state management and selector subscriptions, not product differentiation.",Browser state-management substrate,Included,P3,"pmndrs/zustand is placed in Donor Bench for HyperTwist because it provides a commodity strategic dependency for browser-side state management and selector subscriptions, not product differentiation. Recommended action remains repurpose, but it should stay bounded to the Browser state-management substrate lane rather than reshape the core runtime.",,,,,,,pmndrs/zustand,,,,,,,,,,,,MIT,known_from_reference_material,uploaded_reference_docs,,,,,,,,,,Backfilled from canonized Markdown dossier pass on 2026-04-25: 77-pmndrs-zustand-upstream-dossier.md,v6_unified_source_of_truth_pack,,,,,permissive_or_noncopyleft_known,direct_incorporation_ok,The code license is MIT and direct use is allowed. Treat it as a bounded browser state-management substrate.,"Use directly as a bounded browser-side dependency for local state, selector subscriptions, and hydration behavior.","Typically preserve notices, attribution, and license text where required.",Usually unnecessary unless later product-shaping concerns make selective replacement attractive.,high,standard-notice-review,yes,,,,,,,,,,,,,v6.3_markdown_backfill,Backfilled from canonized Markdown dossier pass on 2026-04-25: 77-pmndrs-zustand-upstream-dossier.md,selected_not_live_permissive_candidate,phase0r_permissive_eval_then_implement,"Phase 1R closed. Retain as a Phase 3R permissive implementation candidate; implement only from its packet authority and the retained-set contract, not by reopening Phase 0R." -,pmndrs/leva,https://github.com/pmndrs/leva,HyperTwist,,,,,interface / visualization / shell surface,subsystem donor,interface donor,merge bench,integrate,moderate modification,"Retain the reusable internal layer, but replace shell assumptions and rebind boundaries so it plugs into HyperTwist cleanly.",,"Integrate selected subsystems rather than the whole product. Mine the repo for parameter editing, control-panel behavior, headless control surfaces, and companion-surface tuning workflows; keep what materially shortens build time, but bind it to HyperTwist-owned data contracts, UI shell, and runtime boundaries.",,Integrate here means: merge bounded support surfaces from this repo into the HyperTwist companion stack.,,,,"the control store, useControls schema parsing, plugin system, multi-panel behavior, and headless mode.","Inspect manifests, README/docs, store layer, useControls, panel components, plugin registration, and headless mode docs.","Audit pmndrs/leva as a Browser control-panel and parameter UI layer candidate for HyperTwist. Inspect the control store, useControls schema parsing, plugin system, multi-panel behavior, and headless mode. Decide whether the retained value should remain active and what should stay bounded outside the HyperTwist core.",,,,,,,,,,,,,,medium,"Canonized Markdown dossier exists and the repo has been source-backed, but CSV backfill is later than the original v6.3 board generation.",medium,Source-backed dossier exists and the repo has been reconciled into the later Markdown authority stack.,,,,,,,,,,,,HT_browser_support,HT_browser_support_0014,browser / state / interaction,"Integrate selectively for HyperTwist. Its source-backed role is a bounded control-panel and headless parameter-UI donor for browser companion surfaces, not a runtime foundation.",HyperTwist,browser / state / interaction,integrate,moderate modification,medium,pmndrs/leva,,Merge Bench,5.0,"Useful merge bench candidate for HyperTwist, primarily in the 'Browser control-panel and parameter UI layer' lane; a bounded control-panel and headless parameter-UI donor for browser companion surfaces, not a runtime foundation.",Browser control-panel and parameter UI layer,Included,P4,"pmndrs/leva is placed in Merge Bench for HyperTwist because it provides a bounded control-panel and headless parameter-UI donor for browser companion surfaces, not a runtime foundation. Recommended action remains integrate, but it should stay bounded to the Browser control-panel and parameter UI layer lane rather than reshape the core runtime.",,,,,,,pmndrs/leva,,,,,,,,,,,,MIT,known_from_reference_material,uploaded_reference_docs,,,,,,,,,,Backfilled from canonized Markdown dossier pass on 2026-04-25: 78-pmndrs-leva-upstream-dossier.md,v6_unified_source_of_truth_pack,,,,,permissive_or_noncopyleft_known,direct_incorporation_ok,The code license is MIT and direct use is allowed. Treat it as a bounded browser parameter-UI donor.,Use directly as a bounded browser-side dependency or concept donor for control panels and tuning UI.,"Typically preserve notices, attribution, and license text where required.",Usually unnecessary unless later product-shaping concerns make selective replacement attractive.,high,standard-notice-review,yes,,,,,,,,,,,,,v6.3_markdown_backfill,Backfilled from canonized Markdown dossier pass on 2026-04-25: 78-pmndrs-leva-upstream-dossier.md,selected_not_live_permissive_candidate,phase0r_permissive_eval_then_implement,"Phase 1R closed. Retain as a Phase 3R permissive implementation candidate; implement only from its packet authority and the retained-set contract, not by reopening Phase 0R." -,pmndrs/use-gesture,https://github.com/pmndrs/use-gesture,HyperTwist,,,,,interface / visualization / shell surface,subsystem donor,dependency donor,donor bench,repurpose,moderate modification,"Retain the valuable internal layer, but expect to replace upstream shell assumptions and rebind boundaries so it fits the HyperTwist architecture.",,"Repurpose selected subsystems rather than the whole product. Mine the repo for browser gesture handling, richer pointer input, drag and scroll behavior, and bounded interaction substrate; keep what materially shortens build time, but bind it to HyperTwist-owned data contracts, UI shell, and runtime boundaries.",,Repurpose here means: extract bounded support surfaces from this repo without inheriting the full upstream shell.,,,,"the core controller, drag engine, pointer capture and lock behavior, scroll prevention, and React versus vanilla bindings.","Inspect manifests, README/docs, controller, gesture engines, React bindings, vanilla bindings, and input config parsing.","Audit pmndrs/use-gesture as a Browser gesture and pointer-input substrate candidate for HyperTwist. Inspect the core controller, drag engine, pointer capture and lock behavior, scroll prevention, and React versus vanilla bindings. Decide whether the retained value should remain active and what should stay bounded outside the HyperTwist core.",,,,,,,,,,,,,,medium,"Canonized Markdown dossier exists and the repo has been source-backed, but CSV backfill is later than the original v6.3 board generation.",medium,Source-backed dossier exists and the repo has been reconciled into the later Markdown authority stack.,,,,,,,,,,,,HT_browser_support,HT_browser_support_0015,browser / state / interaction,"Repurpose selectively for HyperTwist. Its source-backed role is a commodity browser gesture and richer pointer-input substrate, not product differentiation.",HyperTwist,browser / state / interaction,repurpose,moderate modification,medium,pmndrs/use-gesture,,Donor Bench,4.0,"Useful donor bench candidate for HyperTwist, primarily in the 'Browser gesture and pointer-input substrate' lane; a commodity browser gesture and richer pointer-input substrate, not product differentiation.",Browser gesture and pointer-input substrate,Included,P3,"pmndrs/use-gesture is placed in Donor Bench for HyperTwist because it provides a commodity browser gesture and richer pointer-input substrate, not product differentiation. Recommended action remains repurpose, but it should stay bounded to the Browser gesture and pointer-input substrate lane rather than reshape the core runtime.",,,,,,,pmndrs/use-gesture,,,,,,,,,,,,MIT,known_from_reference_material,uploaded_reference_docs,,,,,,,,,,Backfilled from canonized Markdown dossier pass on 2026-04-25: 79-pmndrs-use-gesture-upstream-dossier.md,v6_unified_source_of_truth_pack,,,,,permissive_or_noncopyleft_known,direct_incorporation_ok,The code license is MIT and direct use is allowed. Treat it as a bounded browser gesture and pointer-input substrate.,"Use directly as a bounded browser-side dependency for custom viewers, panels, and interaction surfaces.","Typically preserve notices, attribution, and license text where required.",Usually unnecessary unless later product-shaping concerns make selective replacement attractive.,high,standard-notice-review,yes,,,,,,,,,,,,,v6.3_markdown_backfill,Backfilled from canonized Markdown dossier pass on 2026-04-25: 79-pmndrs-use-gesture-upstream-dossier.md,selected_not_live_permissive_candidate,phase0r_permissive_eval_then_implement,"Phase 1R closed. Retain as a Phase 3R permissive implementation candidate; implement only from its packet authority and the retained-set contract, not by reopening Phase 0R." -,@react-spring/parallax,https://github.com/pmndrs/react-spring/tree/main/packages/parallax,HyperTwist,,,,,interface / visualization / shell surface,subsystem donor,interface donor,merge bench,integrate,moderate modification,"Retain the reusable internal layer, but replace shell assumptions and rebind boundaries so it plugs into HyperTwist cleanly.",,"Integrate selected subsystems rather than the whole product. Mine the repo for layered explainer behavior, scroll-driven motion, sticky layers, and narrative browser presentation; keep what materially shortens build time, but bind it to HyperTwist-owned data contracts, UI shell, and runtime boundaries.",,Integrate here means: merge bounded support surfaces from this repo into the HyperTwist companion stack.,,,,"the parallax runtime, sticky-layer behavior, scroll-driven spring motion, and imperative scrollTo flow.","Inspect manifests, README/docs, parallax package runtime, layer behavior, and scroll-controller code.","Audit @react-spring/parallax as a Browser layered-motion and explainer sidecar candidate for HyperTwist. Inspect the parallax runtime, sticky-layer behavior, scroll-driven spring motion, and imperative scrollTo flow. Decide whether the retained value should remain active and what should stay bounded outside the HyperTwist core.",,,,,,,,,,,,,,medium,"Canonized Markdown dossier exists and the repo has been source-backed, but CSV backfill is later than the original v6.3 board generation.",medium,Source-backed dossier exists and the repo has been reconciled into the later Markdown authority stack.,,,,,,,,,,,,HT_browser_support,HT_browser_support_0016,browser / 3D / XR / presentation,"Integrate selectively for HyperTwist. Its source-backed role is a bounded layered-motion and explainer sidecar beneath react-spring, not a runtime lane.",HyperTwist,browser / 3D / XR / presentation,integrate,moderate modification,medium,@react-spring/parallax,,Merge Bench,5.0,"Useful merge bench candidate for HyperTwist, primarily in the 'Browser layered-motion and explainer sidecar' lane; a bounded layered-motion and explainer sidecar beneath react-spring, not a runtime lane.",Browser layered-motion and explainer sidecar,Included,P4,"@react-spring/parallax is placed in Merge Bench for HyperTwist because it provides a bounded layered-motion and explainer sidecar beneath react-spring, not a runtime lane. Recommended action remains integrate, but it should stay bounded to the Browser layered-motion and explainer sidecar lane rather than reshape the core runtime.",,,,,,,@react-spring/parallax,,,,,,,,,,,,MIT,known_from_reference_material,uploaded_reference_docs,,,,,,,,,,Backfilled from canonized Markdown dossier pass on 2026-04-25: 81-react-spring-parallax-upstream-dossier.md,v6_unified_source_of_truth_pack,,,,,permissive_or_noncopyleft_known,direct_incorporation_ok,The code license is MIT and direct use is allowed. Treat it as a bounded layered-motion and explainer sidecar.,Use directly as a bounded browser-side dependency for explainer and narrative surfaces.,"Typically preserve notices, attribution, and license text where required.",Usually unnecessary unless later product-shaping concerns make selective replacement attractive.,high,standard-notice-review,yes,,,,,,,,,,,,,v6.3_markdown_backfill,Backfilled from canonized Markdown dossier pass on 2026-04-25: 81-react-spring-parallax-upstream-dossier.md,selected_not_live_permissive_candidate,phase0r_permissive_eval_then_implement,"Phase 1R closed. Retain as a Phase 3R permissive implementation candidate; implement only from its packet authority and the retained-set contract, not by reopening Phase 0R." -,@react-spring/rafz,https://github.com/pmndrs/react-spring/tree/main/packages/rafz,HyperTwist,,,,,interface / visualization / shell surface,subsystem donor,dependency donor,merge bench,integrate,moderate modification,"Retain the reusable internal layer, but replace shell assumptions and rebind boundaries so it plugs into HyperTwist cleanly.",,"Integrate selected subsystems rather than the whole product. Mine the repo for browser scheduling, phased queues, timeout handling, and motion-frame orchestration beneath higher-level UI motion; keep what materially shortens build time, but bind it to HyperTwist-owned data contracts, UI shell, and runtime boundaries.",,Integrate here means: merge bounded support surfaces from this repo into the HyperTwist companion stack.,,,,"the frame-loop phases, timeout scheduling, throttling, batched updates hook, and demand versus always control behavior.","Inspect manifests, README/docs, rafz package runtime, frame-loop scheduling, timeout handling, and queue behavior.","Audit @react-spring/rafz as a Browser frame-loop and scheduling utility candidate for HyperTwist. Inspect the frame-loop phases, timeout scheduling, throttling, batched updates hook, and demand versus always control behavior. Decide whether the retained value should remain active and what should stay bounded outside the HyperTwist core.",,,,,,,,,,,,,,medium,"Canonized Markdown dossier exists and the repo has been source-backed, but CSV backfill is later than the original v6.3 board generation.",medium,Source-backed dossier exists and the repo has been reconciled into the later Markdown authority stack.,,,,,,,,,,,,HT_browser_support,HT_browser_support_0017,browser / utilities / scheduling,"Integrate selectively for HyperTwist. Its source-backed role is a lower-level browser frame-loop and scheduling utility beneath react-spring, not a product lane.",HyperTwist,browser / utilities / scheduling,integrate,moderate modification,medium,@react-spring/rafz,,Merge Bench,5.0,"Useful merge bench candidate for HyperTwist, primarily in the 'Browser frame-loop and scheduling utility' lane; a lower-level browser frame-loop and scheduling utility beneath react-spring, not a product lane.",Browser frame-loop and scheduling utility,Included,P4,"@react-spring/rafz is placed in Merge Bench for HyperTwist because it provides a lower-level browser frame-loop and scheduling utility beneath react-spring, not a product lane. Recommended action remains integrate, but it should stay bounded to the Browser frame-loop and scheduling utility lane rather than reshape the core runtime.",,,,,,,@react-spring/rafz,,,,,,,,,,,,MIT,known_from_reference_material,uploaded_reference_docs,,,,,,,,,,Backfilled from canonized Markdown dossier pass on 2026-04-25: 82-react-spring-rafz-upstream-dossier.md,v6_unified_source_of_truth_pack,,,,,permissive_or_noncopyleft_known,direct_incorporation_ok,The code license is MIT and direct use is allowed. Treat it as a bounded browser scheduling utility.,Use directly as a bounded browser-side dependency beneath higher-level motion or interaction layers.,"Typically preserve notices, attribution, and license text where required.",Usually unnecessary unless later product-shaping concerns make selective replacement attractive.,high,standard-notice-review,yes,,,,,,,,,,,,,v6.3_markdown_backfill,Backfilled from canonized Markdown dossier pass on 2026-04-25: 82-react-spring-rafz-upstream-dossier.md,selected_not_live_permissive_candidate,phase0r_permissive_eval_then_implement,"Phase 1R closed. Retain as a Phase 3R permissive implementation candidate; implement only from its packet authority and the retained-set contract, not by reopening Phase 0R." -,@react-spring/animated,https://github.com/pmndrs/react-spring/tree/main/packages/animated,HyperTwist,,,,,interface / visualization / shell surface,subsystem donor,dependency donor,merge bench,integrate,moderate modification,"Retain the reusable internal layer, but replace shell assumptions and rebind boundaries so it plugs into HyperTwist cleanly.",,"Integrate selected subsystems rather than the whole product. Mine the repo for animatable-component hosting, animated-props observation, and low-level motion binding beneath higher-level browser motion; keep what materially shortens build time, but bind it to HyperTwist-owned data contracts, UI shell, and runtime boundaries.",,Integrate here means: merge bounded support surfaces from this repo into the HyperTwist companion stack.,,,,"the host-creation runtime, withAnimated wrapper, dependency observation, and native-update versus rerender behavior.","Inspect manifests, README/docs, animated package runtime, host creation, animated wrapper, and animated base-node behavior.","Audit @react-spring/animated as a Browser animatable-component substrate candidate for HyperTwist. Inspect the host-creation runtime, withAnimated wrapper, dependency observation, and native-update versus rerender behavior. Decide whether the retained value should remain active and what should stay bounded outside the HyperTwist core.",,,,,,,,,,,,,,medium,"Canonized Markdown dossier exists and the repo has been source-backed, but CSV backfill is later than the original v6.3 board generation.",medium,Source-backed dossier exists and the repo has been reconciled into the later Markdown authority stack.,,,,,,,,,,,,HT_browser_support,HT_browser_support_0018,browser / utilities / animation,"Integrate selectively for HyperTwist. Its source-backed role is a lower-level animatable-component host and animated-props substrate beneath react-spring, not a product lane.",HyperTwist,browser / utilities / animation,integrate,moderate modification,medium,@react-spring/animated,,Merge Bench,5.0,"Useful merge bench candidate for HyperTwist, primarily in the 'Browser animatable-component substrate' lane; a lower-level animatable-component host and animated-props substrate beneath react-spring, not a product lane.",Browser animatable-component substrate,Included,P4,"@react-spring/animated is placed in Merge Bench for HyperTwist because it provides a lower-level animatable-component host and animated-props substrate beneath react-spring, not a product lane. Recommended action remains integrate, but it should stay bounded to the Browser animatable-component substrate lane rather than reshape the core runtime.",,,,,,,@react-spring/animated,,,,,,,,,,,,MIT,known_from_reference_material,uploaded_reference_docs,,,,,,,,,,Backfilled from canonized Markdown dossier pass on 2026-04-25: 83-react-spring-animated-upstream-dossier.md,v6_unified_source_of_truth_pack,,,,,permissive_or_noncopyleft_known,direct_incorporation_ok,The code license is MIT and direct use is allowed. Treat it as a bounded animatable-component substrate.,Use directly as a bounded browser-side dependency beneath higher-level motion and UI layers.,"Typically preserve notices, attribution, and license text where required.",Usually unnecessary unless later product-shaping concerns make selective replacement attractive.,high,standard-notice-review,yes,,,,,,,,,,,,,v6.3_markdown_backfill,Backfilled from canonized Markdown dossier pass on 2026-04-25: 83-react-spring-animated-upstream-dossier.md,selected_not_live_permissive_candidate,phase0r_permissive_eval_then_implement,"Phase 1R closed. Retain as a Phase 3R permissive implementation candidate; implement only from its packet authority and the retained-set contract, not by reopening Phase 0R." -,@react-spring/core,https://github.com/pmndrs/react-spring/tree/main/packages/core,HyperTwist,,,,,interface / visualization / shell surface,subsystem donor,dependency donor,donor bench,repurpose,moderate modification,"Retain the valuable internal layer, but expect to replace upstream shell assumptions and rebind boundaries so it fits the HyperTwist architecture.",,"Repurpose selected subsystems rather than the whole product. Mine the repo for browser motion runtime, spring orchestration, frame advancement, and reusable motion-core behavior beneath higher-level UI layers; keep what materially shortens build time, but bind it to HyperTwist-owned data contracts, UI shell, and runtime boundaries.",,Repurpose here means: extract bounded support surfaces from this repo without inheriting the full upstream shell.,,,,"the Controller runtime, SpringValue motion engine, useSprings lifecycle, queueing, start-stop behavior, and frame advancement.","Inspect manifests, README/docs, core package runtime, Controller, SpringValue, and hook lifecycle behavior.","Audit @react-spring/core as a Browser spring-runtime core candidate for HyperTwist. Inspect the Controller runtime, SpringValue motion engine, useSprings lifecycle, queueing, start-stop behavior, and frame advancement. Decide whether the retained value should remain active and what should stay bounded outside the HyperTwist core.",,,,,,,,,,,,,,medium,"Canonized Markdown dossier exists and the repo has been source-backed, but CSV backfill is later than the original v6.3 board generation.",medium,Source-backed dossier exists and the repo has been reconciled into the later Markdown authority stack.,,,,,,,,,,,,HT_browser_support,HT_browser_support_0019,browser / utilities / animation,"Repurpose selectively for HyperTwist. Its source-backed role is the platform-agnostic spring-runtime core beneath react-spring, not a product foundation.",HyperTwist,browser / utilities / animation,repurpose,moderate modification,medium,@react-spring/core,,Donor Bench,4.0,"Useful donor bench candidate for HyperTwist, primarily in the 'Browser spring-runtime core' lane; the platform-agnostic spring-runtime core beneath react-spring, not a product foundation.",Browser spring-runtime core,Included,P3,"@react-spring/core is placed in Donor Bench for HyperTwist because it provides the platform-agnostic spring-runtime core beneath react-spring, not a product foundation. Recommended action remains repurpose, but it should stay bounded to the Browser spring-runtime core lane rather than reshape the core runtime.",,,,,,,@react-spring/core,,,,,,,,,,,,MIT,known_from_reference_material,uploaded_reference_docs,,,,,,,,,,Backfilled from canonized Markdown dossier pass on 2026-04-25: 84-react-spring-core-upstream-dossier.md,v6_unified_source_of_truth_pack,,,,,permissive_or_noncopyleft_known,direct_incorporation_ok,The code license is MIT and direct use is allowed. Treat it as a bounded spring-runtime core beneath higher-level motion layers.,Use directly as a bounded browser-side dependency beneath higher-level motion and interaction layers.,"Typically preserve notices, attribution, and license text where required.",Usually unnecessary unless later product-shaping concerns make selective replacement attractive.,high,standard-notice-review,yes,,,,,,,,,,,,,v6.3_markdown_backfill,Backfilled from canonized Markdown dossier pass on 2026-04-25: 84-react-spring-core-upstream-dossier.md,selected_not_live_permissive_candidate,phase0r_permissive_eval_then_implement,"Phase 1R closed. Retain as a Phase 3R permissive implementation candidate; implement only from its packet authority and the retained-set contract, not by reopening Phase 0R." -,@react-spring/shared,https://github.com/pmndrs/react-spring/tree/main/packages/shared,HyperTwist,,,,,interface / visualization / shell surface,subsystem donor,dependency donor,merge bench,integrate,moderate modification,"Retain the reusable internal layer, but replace shell assumptions and rebind boundaries so it plugs into HyperTwist cleanly.",,"Integrate selected subsystems rather than the whole product. Mine the repo for motion utilities, frame-loop customization, interpolation, and fluid observation beneath higher-level browser motion; keep what materially shortens build time, but bind it to HyperTwist-owned data contracts, UI shell, and runtime boundaries.",,Integrate here means: merge bounded support surfaces from this repo into the HyperTwist companion stack.,,,,"the globals customization seams, frame-loop behavior, interpolation helpers, and fluid observer substrate.","Inspect manifests, README/docs, shared package exports, globals, frame loop, interpolation, and fluid observer modules.","Audit @react-spring/shared as a Browser motion utility substrate candidate for HyperTwist. Inspect the globals customization seams, frame-loop behavior, interpolation helpers, and fluid observer substrate. Decide whether the retained value should remain active and what should stay bounded outside the HyperTwist core.",,,,,,,,,,,,,,medium,"Canonized Markdown dossier exists and the repo has been source-backed, but CSV backfill is later than the original v6.3 board generation.",medium,Source-backed dossier exists and the repo has been reconciled into the later Markdown authority stack.,,,,,,,,,,,,HT_browser_support,HT_browser_support_0020,browser / utilities / animation,"Integrate selectively for HyperTwist. Its source-backed role is a lower-level motion utility and fluid-observer substrate beneath react-spring, not a product lane.",HyperTwist,browser / utilities / animation,integrate,moderate modification,medium,@react-spring/shared,,Merge Bench,5.0,"Useful merge bench candidate for HyperTwist, primarily in the 'Browser motion utility substrate' lane; a lower-level motion utility and fluid-observer substrate beneath react-spring, not a product lane.",Browser motion utility substrate,Included,P4,"@react-spring/shared is placed in Merge Bench for HyperTwist because it provides a lower-level motion utility and fluid-observer substrate beneath react-spring, not a product lane. Recommended action remains integrate, but it should stay bounded to the Browser motion utility substrate lane rather than reshape the core runtime.",,,,,,,@react-spring/shared,,,,,,,,,,,,MIT,known_from_reference_material,uploaded_reference_docs,,,,,,,,,,Backfilled from canonized Markdown dossier pass on 2026-04-25: 85-react-spring-shared-upstream-dossier.md,v6_unified_source_of_truth_pack,,,,,permissive_or_noncopyleft_known,direct_incorporation_ok,The code license is MIT and direct use is allowed. Treat it as a bounded motion utility substrate.,Use directly as a bounded browser-side dependency beneath higher-level motion layers.,"Typically preserve notices, attribution, and license text where required.",Usually unnecessary unless later product-shaping concerns make selective replacement attractive.,high,standard-notice-review,yes,,,,,,,,,,,,,v6.3_markdown_backfill,Backfilled from canonized Markdown dossier pass on 2026-04-25: 85-react-spring-shared-upstream-dossier.md,selected_not_live_permissive_candidate,phase0r_permissive_eval_then_implement,"Phase 1R closed. Retain as a Phase 3R permissive implementation candidate; implement only from its packet authority and the retained-set contract, not by reopening Phase 0R." -,@react-spring/types,https://github.com/pmndrs/react-spring/tree/main/packages/types,HyperTwist,,,,,interface / visualization / shell surface,subsystem donor,dependency donor,merge bench,integrate,moderate modification,"Retain the reusable internal layer, but replace shell assumptions and rebind boundaries so it plugs into HyperTwist cleanly.",,"Integrate selected subsystems rather than the whole product. Mine the repo for shared type contracts and package-design substrate beneath browser motion layers; keep what materially shortens build time, but bind it to HyperTwist-owned data contracts, UI shell, and runtime boundaries.",,Integrate here means: merge bounded support surfaces from this repo into the HyperTwist companion stack.,,,,"the shared type-contract surface, animatable and interpolation types, and utility-type exports used across react-spring packages.","Inspect manifests, type package exports, shared type files, interpolation type definitions, and utility-type modules.","Audit @react-spring/types as a Browser motion type-contract substrate candidate for HyperTwist. Inspect the shared type-contract surface, animatable and interpolation types, and utility-type exports used across react-spring packages. Decide whether the retained value should remain active and what should stay bounded outside the HyperTwist core.",,,,,,,,,,,,,,medium,"Canonized Markdown dossier exists and the repo has been source-backed, but CSV backfill is later than the original v6.3 board generation.",medium,Source-backed dossier exists and the repo has been reconciled into the later Markdown authority stack.,,,,,,,,,,,,HT_browser_support,HT_browser_support_0021,browser / utilities / animation,"Integrate selectively for HyperTwist. Its source-backed role is a narrow type-contract substrate beneath react-spring, not a behavior-heavy donor or product lane.",HyperTwist,browser / utilities / animation,integrate,moderate modification,medium,@react-spring/types,,Merge Bench,5.0,"Useful merge bench candidate for HyperTwist, primarily in the 'Browser motion type-contract substrate' lane; a narrow type-contract substrate beneath react-spring, not a behavior-heavy donor or product lane.",Browser motion type-contract substrate,Included,P4,"@react-spring/types is placed in Merge Bench for HyperTwist because it provides a narrow type-contract substrate beneath react-spring, not a behavior-heavy donor or product lane. Recommended action remains integrate, but it should stay bounded to the Browser motion type-contract substrate lane rather than reshape the core runtime.",,,,,,,@react-spring/types,,,,,,,,,,,,MIT,known_from_reference_material,uploaded_reference_docs,,,,,,,,,,Backfilled from canonized Markdown dossier pass on 2026-04-25: 86-react-spring-types-upstream-dossier.md,v6_unified_source_of_truth_pack,,,,,permissive_or_noncopyleft_known,direct_incorporation_ok,The code license is MIT and direct use is allowed. Treat it as a bounded type-contract substrate.,Use directly as a bounded browser-side dependency where those contracts are actually needed.,"Typically preserve notices, attribution, and license text where required.",Usually unnecessary unless later product-shaping concerns make selective replacement attractive.,high,standard-notice-review,yes,,,,,,,,,,,,,v6.3_markdown_backfill,Backfilled from canonized Markdown dossier pass on 2026-04-25: 86-react-spring-types-upstream-dossier.md,selected_not_live_permissive_candidate,phase0r_permissive_eval_then_implement,"Phase 1R closed. Retain as a Phase 3R permissive implementation candidate; implement only from its packet authority and the retained-set contract, not by reopening Phase 0R." +,pmndrs/react-postprocessing,https://github.com/pmndrs/react-postprocessing,HyperTwist,,,,,interface / visualization / shell surface,subsystem donor,dependency donor,merge bench,integrate,moderate modification,"Retain the reusable internal layer, but replace shell assumptions and rebind boundaries so it plugs into HyperTwist cleanly.",,"Integrate selected subsystems rather than the whole product. Mine the repo for React-side effect orchestration, selection-based emphasis behavior, and wrapper ergonomics above browser post-processing; keep what materially shortens build time, but bind it to HyperTwist-owned data contracts, UI shell, and runtime boundaries.",,Integrate here means: merge bounded support surfaces from this repo into the HyperTwist companion stack.,,,,"the React EffectComposer wrapper, Selection model, and integration assumptions on top of postprocessing and react-three-fiber.","Inspect manifests, README/docs, EffectComposer wrapper, Selection support, and the narrow React integration layer.","Audit pmndrs/react-postprocessing as a Browser React effect-wrapper layer candidate for HyperTwist. Inspect the React EffectComposer wrapper, Selection model, and integration assumptions on top of postprocessing and react-three-fiber. Decide whether the retained value should remain active and what should stay bounded outside the HyperTwist core.",,,,,,,,,,,,,,medium,"Canonized Markdown dossier exists and the repo has been source-backed, but CSV backfill is later than the original v6.3 board generation.",medium,Source-backed dossier exists and the repo has been reconciled into the later Markdown authority stack.,,,,,,,,,,,,HT_browser_support,HT_browser_support_0010,browser / 3D / XR / presentation,"Integrate selectively for HyperTwist. Its source-backed role is a bounded React wrapper for the browser post-processing lane, not a standalone product lane.",HyperTwist,browser / 3D / XR / presentation,integrate,moderate modification,medium,pmndrs/react-postprocessing,,Merge Bench,5.0,"Useful merge bench candidate for HyperTwist, primarily in the 'Browser React effect-wrapper layer' lane; a bounded React wrapper for the browser post-processing lane, not a standalone product lane.",Browser React effect-wrapper layer,Included,P4,"pmndrs/react-postprocessing is placed in Merge Bench for HyperTwist because it provides a bounded React wrapper for the browser post-processing lane, not a standalone product lane. Recommended action remains integrate, but it should stay bounded to the Browser React effect-wrapper layer lane rather than reshape the core runtime.",,,,,,,pmndrs/react-postprocessing,,,,,,,,,,,,MIT,known_from_reference_material,uploaded_reference_docs,,,,,,,,,,Backfilled from canonized Markdown dossier pass on 2026-04-25: 70-pmndrs-react-postprocessing-upstream-dossier.md,v6_unified_source_of_truth_pack,,,,,permissive_or_noncopyleft_known,direct_incorporation_ok,The code license is MIT and direct use is allowed. Treat it as a bounded React wrapper layer above browser post-processing.,Use directly as a bounded browser-side wrapper dependency above the core post-processing substrate.,"Typically preserve notices, attribution, and license text where required.",Usually unnecessary unless later product-shaping concerns make selective replacement attractive.,high,standard-notice-review,yes,,,,,,,,,,,,,v6.3_markdown_backfill,Backfilled from canonized Markdown dossier pass on 2026-04-25: 70-pmndrs-react-postprocessing-upstream-dossier.md,implemented_live_permissive,landed_permissive_preserve,"Phase 3R-E closed. Preserve as the landed first-party embodied companion, narration, lip-sync, gesture, subtitle, and avatar-embed lane; start future widening from the live-lane audit, then the 3R-E implementation packet, then REPO_LICENSE_TRACKING.md." +,pmndrs/three-stdlib,https://github.com/pmndrs/three-stdlib,HyperTwist,,,,,interface / visualization / shell surface,subsystem donor,dependency donor,merge bench,integrate,moderate modification,"Retain the reusable internal layer, but replace shell assumptions and rebind boundaries so it plugs into HyperTwist cleanly.",,"Integrate selected subsystems rather than the whole product. Mine the repo for browser-side utility helpers, controls, loaders, and XR-adjacent primitives beneath the browser companion stack; keep what materially shortens build time, but bind it to HyperTwist-owned data contracts, UI shell, and runtime boundaries.",,Integrate here means: merge bounded support surfaces from this repo into the HyperTwist companion stack.,,,,"the utility export surface, controls, loaders, WebXR helpers, post-processing helpers, and packaging of three/examples behavior.","Inspect manifests, README/docs, utility index, controls, WebXR helpers, loaders, and exported utility modules.","Audit pmndrs/three-stdlib as a Browser 3D utility substrate candidate for HyperTwist. Inspect the utility export surface, controls, loaders, WebXR helpers, post-processing helpers, and packaging of three/examples behavior. Decide whether the retained value should remain active and what should stay bounded outside the HyperTwist core.",,,,,,,,,,,,,,medium,"Canonized Markdown dossier exists and the repo has been source-backed, but CSV backfill is later than the original v6.3 board generation.",medium,Source-backed dossier exists and the repo has been reconciled into the later Markdown authority stack.,,,,,,,,,,,,HT_browser_support,HT_browser_support_0011,browser / 3D / XR / presentation,"Integrate selectively for HyperTwist. Its source-backed role is a lower-level browser utility substrate beneath three.js, drei, and XR-adjacent lanes, not a product lane.",HyperTwist,browser / 3D / XR / presentation,integrate,moderate modification,medium,pmndrs/three-stdlib,,Merge Bench,5.0,"Useful merge bench candidate for HyperTwist, primarily in the 'Browser 3D utility substrate' lane; a lower-level browser utility substrate beneath three.js, drei, and XR-adjacent lanes, not a product lane.",Browser 3D utility substrate,Included,P4,"pmndrs/three-stdlib is placed in Merge Bench for HyperTwist because it provides a lower-level browser utility substrate beneath three.js, drei, and XR-adjacent lanes, not a product lane. Recommended action remains integrate, but it should stay bounded to the Browser 3D utility substrate lane rather than reshape the core runtime.",,,,,,,pmndrs/three-stdlib,,,,,,,,,,,,MIT,known_from_reference_material,uploaded_reference_docs,,,,,,,,,,Backfilled from canonized Markdown dossier pass on 2026-04-25: 75-pmndrs-three-stdlib-upstream-dossier.md,v6_unified_source_of_truth_pack,,,,,permissive_or_noncopyleft_known,direct_incorporation_ok,The code license is MIT and direct use is allowed. Treat it as a bounded utility substrate beneath three.js-adjacent browser lanes.,Use directly as a bounded browser-side utility dependency beneath higher-level viewer and XR layers.,"Typically preserve notices, attribution, and license text where required.",Usually unnecessary unless later product-shaping concerns make selective replacement attractive.,high,standard-notice-review,yes,,,,,,,,,,,,,v6.3_markdown_backfill,Backfilled from canonized Markdown dossier pass on 2026-04-25: 75-pmndrs-three-stdlib-upstream-dossier.md,implemented_live_permissive,landed_permissive_preserve,"Phase 3R-E closed. Preserve as the landed first-party embodied companion, narration, lip-sync, gesture, subtitle, and avatar-embed lane; start future widening from the live-lane audit, then the 3R-E implementation packet, then REPO_LICENSE_TRACKING.md." +,pmndrs/maath,https://github.com/pmndrs/maath,HyperTwist,,,,,interface / visualization / shell surface,subsystem donor,dependency donor,merge bench,integrate,moderate modification,"Retain the reusable internal layer, but replace shell assumptions and rebind boundaries so it plugs into HyperTwist cleanly.",,"Integrate selected subsystems rather than the whole product. Mine the repo for browser-side easing, damping, sampling, and geometry helper behavior beneath interactive surfaces; keep what materially shortens build time, but bind it to HyperTwist-owned data contracts, UI shell, and runtime boundaries.",,Integrate here means: merge bounded support surfaces from this repo into the HyperTwist companion stack.,,,,"the easing runtime, random helpers, geometry utilities, and three.js-oriented math surfaces.","Inspect manifests, README/docs, math package exports, easing, geometry, and random helper modules.","Audit pmndrs/maath as a Browser math-helper substrate candidate for HyperTwist. Inspect the easing runtime, random helpers, geometry utilities, and three.js-oriented math surfaces. Decide whether the retained value should remain active and what should stay bounded outside the HyperTwist core.",,,,,,,,,,,,,,medium,"Canonized Markdown dossier exists and the repo has been source-backed, but CSV backfill is later than the original v6.3 board generation.",medium,Source-backed dossier exists and the repo has been reconciled into the later Markdown authority stack.,,,,,,,,,,,,HT_browser_support,HT_browser_support_0012,browser / utilities / math,"Integrate selectively for HyperTwist. Its source-backed role is a lower-level browser math-helper substrate beneath viewer and XR-adjacent lanes, not a product lane.",HyperTwist,browser / utilities / math,integrate,moderate modification,medium,pmndrs/maath,,Merge Bench,5.0,"Useful merge bench candidate for HyperTwist, primarily in the 'Browser math-helper substrate' lane; a lower-level browser math-helper substrate beneath viewer and XR-adjacent lanes, not a product lane.",Browser math-helper substrate,Included,P4,"pmndrs/maath is placed in Merge Bench for HyperTwist because it provides a lower-level browser math-helper substrate beneath viewer and XR-adjacent lanes, not a product lane. Recommended action remains integrate, but it should stay bounded to the Browser math-helper substrate lane rather than reshape the core runtime.",,,,,,,pmndrs/maath,,,,,,,,,,,,MIT,known_from_reference_material,uploaded_reference_docs,,,,,,,,,,Backfilled from canonized Markdown dossier pass on 2026-04-25: 76-pmndrs-maath-upstream-dossier.md,v6_unified_source_of_truth_pack,,,,,permissive_or_noncopyleft_known,direct_incorporation_ok,The code license is MIT and direct use is allowed. Treat it as a bounded math-helper substrate.,Use directly as a bounded browser-side utility dependency beneath higher-level interactive layers.,"Typically preserve notices, attribution, and license text where required.",Usually unnecessary unless later product-shaping concerns make selective replacement attractive.,high,standard-notice-review,yes,,,,,,,,,,,,,v6.3_markdown_backfill,Backfilled from canonized Markdown dossier pass on 2026-04-25: 76-pmndrs-maath-upstream-dossier.md,implemented_live_permissive,landed_permissive_preserve,"Phase 3R-E closed. Preserve as the landed first-party embodied companion, narration, lip-sync, gesture, subtitle, and avatar-embed lane; start future widening from the live-lane audit, then the 3R-E implementation packet, then REPO_LICENSE_TRACKING.md." +,pmndrs/zustand,https://github.com/pmndrs/zustand,HyperTwist,,,,,interface / visualization / shell surface,subsystem donor,dependency donor,donor bench,repurpose,moderate modification,"Retain the valuable internal layer, but expect to replace upstream shell assumptions and rebind boundaries so it fits the HyperTwist architecture.",,"Repurpose selected subsystems rather than the whole product. Mine the repo for browser-side state management, selector subscriptions, hydration, and bridging between non-React logic and React views; keep what materially shortens build time, but bind it to HyperTwist-owned data contracts, UI shell, and runtime boundaries.",,Repurpose here means: extract bounded support surfaces from this repo without inheriting the full upstream shell.,,,,"the vanilla store kernel, React bridge, selector subscriptions, persist middleware, devtools integration, and equality-aware selection behavior.","Inspect manifests, README/docs, vanilla store, react bindings, traditional selector helpers, and middleware modules.","Audit pmndrs/zustand as a Browser state-management substrate candidate for HyperTwist. Inspect the vanilla store kernel, React bridge, selector subscriptions, persist middleware, devtools integration, and equality-aware selection behavior. Decide whether the retained value should remain active and what should stay bounded outside the HyperTwist core.",,,,,,,,,,,,,,medium,"Canonized Markdown dossier exists and the repo has been source-backed, but CSV backfill is later than the original v6.3 board generation.",medium,Source-backed dossier exists and the repo has been reconciled into the later Markdown authority stack.,,,,,,,,,,,,HT_browser_support,HT_browser_support_0013,browser / state / interaction,"Repurpose selectively for HyperTwist. Its source-backed role is a commodity strategic dependency for browser-side state management and selector subscriptions, not product differentiation.",HyperTwist,browser / state / interaction,repurpose,moderate modification,medium,pmndrs/zustand,,Donor Bench,4.0,"Useful donor bench candidate for HyperTwist, primarily in the 'Browser state-management substrate' lane; a commodity strategic dependency for browser-side state management and selector subscriptions, not product differentiation.",Browser state-management substrate,Included,P3,"pmndrs/zustand is placed in Donor Bench for HyperTwist because it provides a commodity strategic dependency for browser-side state management and selector subscriptions, not product differentiation. Recommended action remains repurpose, but it should stay bounded to the Browser state-management substrate lane rather than reshape the core runtime.",,,,,,,pmndrs/zustand,,,,,,,,,,,,MIT,known_from_reference_material,uploaded_reference_docs,,,,,,,,,,Backfilled from canonized Markdown dossier pass on 2026-04-25: 77-pmndrs-zustand-upstream-dossier.md,v6_unified_source_of_truth_pack,,,,,permissive_or_noncopyleft_known,direct_incorporation_ok,The code license is MIT and direct use is allowed. Treat it as a bounded browser state-management substrate.,"Use directly as a bounded browser-side dependency for local state, selector subscriptions, and hydration behavior.","Typically preserve notices, attribution, and license text where required.",Usually unnecessary unless later product-shaping concerns make selective replacement attractive.,high,standard-notice-review,yes,,,,,,,,,,,,,v6.3_markdown_backfill,Backfilled from canonized Markdown dossier pass on 2026-04-25: 77-pmndrs-zustand-upstream-dossier.md,implemented_live_permissive,landed_permissive_preserve,"Phase 3R-E closed. Preserve as the landed first-party embodied companion, narration, lip-sync, gesture, subtitle, and avatar-embed lane; start future widening from the live-lane audit, then the 3R-E implementation packet, then REPO_LICENSE_TRACKING.md." +,pmndrs/leva,https://github.com/pmndrs/leva,HyperTwist,,,,,interface / visualization / shell surface,subsystem donor,interface donor,merge bench,integrate,moderate modification,"Retain the reusable internal layer, but replace shell assumptions and rebind boundaries so it plugs into HyperTwist cleanly.",,"Integrate selected subsystems rather than the whole product. Mine the repo for parameter editing, control-panel behavior, headless control surfaces, and companion-surface tuning workflows; keep what materially shortens build time, but bind it to HyperTwist-owned data contracts, UI shell, and runtime boundaries.",,Integrate here means: merge bounded support surfaces from this repo into the HyperTwist companion stack.,,,,"the control store, useControls schema parsing, plugin system, multi-panel behavior, and headless mode.","Inspect manifests, README/docs, store layer, useControls, panel components, plugin registration, and headless mode docs.","Audit pmndrs/leva as a Browser control-panel and parameter UI layer candidate for HyperTwist. Inspect the control store, useControls schema parsing, plugin system, multi-panel behavior, and headless mode. Decide whether the retained value should remain active and what should stay bounded outside the HyperTwist core.",,,,,,,,,,,,,,medium,"Canonized Markdown dossier exists and the repo has been source-backed, but CSV backfill is later than the original v6.3 board generation.",medium,Source-backed dossier exists and the repo has been reconciled into the later Markdown authority stack.,,,,,,,,,,,,HT_browser_support,HT_browser_support_0014,browser / state / interaction,"Integrate selectively for HyperTwist. Its source-backed role is a bounded control-panel and headless parameter-UI donor for browser companion surfaces, not a runtime foundation.",HyperTwist,browser / state / interaction,integrate,moderate modification,medium,pmndrs/leva,,Merge Bench,5.0,"Useful merge bench candidate for HyperTwist, primarily in the 'Browser control-panel and parameter UI layer' lane; a bounded control-panel and headless parameter-UI donor for browser companion surfaces, not a runtime foundation.",Browser control-panel and parameter UI layer,Included,P4,"pmndrs/leva is placed in Merge Bench for HyperTwist because it provides a bounded control-panel and headless parameter-UI donor for browser companion surfaces, not a runtime foundation. Recommended action remains integrate, but it should stay bounded to the Browser control-panel and parameter UI layer lane rather than reshape the core runtime.",,,,,,,pmndrs/leva,,,,,,,,,,,,MIT,known_from_reference_material,uploaded_reference_docs,,,,,,,,,,Backfilled from canonized Markdown dossier pass on 2026-04-25: 78-pmndrs-leva-upstream-dossier.md,v6_unified_source_of_truth_pack,,,,,permissive_or_noncopyleft_known,direct_incorporation_ok,The code license is MIT and direct use is allowed. Treat it as a bounded browser parameter-UI donor.,Use directly as a bounded browser-side dependency or concept donor for control panels and tuning UI.,"Typically preserve notices, attribution, and license text where required.",Usually unnecessary unless later product-shaping concerns make selective replacement attractive.,high,standard-notice-review,yes,,,,,,,,,,,,,v6.3_markdown_backfill,Backfilled from canonized Markdown dossier pass on 2026-04-25: 78-pmndrs-leva-upstream-dossier.md,implemented_live_permissive,landed_permissive_preserve,"Phase 3R-E closed. Preserve as the landed first-party embodied companion, narration, lip-sync, gesture, subtitle, and avatar-embed lane; start future widening from the live-lane audit, then the 3R-E implementation packet, then REPO_LICENSE_TRACKING.md." +,pmndrs/use-gesture,https://github.com/pmndrs/use-gesture,HyperTwist,,,,,interface / visualization / shell surface,subsystem donor,dependency donor,donor bench,repurpose,moderate modification,"Retain the valuable internal layer, but expect to replace upstream shell assumptions and rebind boundaries so it fits the HyperTwist architecture.",,"Repurpose selected subsystems rather than the whole product. Mine the repo for browser gesture handling, richer pointer input, drag and scroll behavior, and bounded interaction substrate; keep what materially shortens build time, but bind it to HyperTwist-owned data contracts, UI shell, and runtime boundaries.",,Repurpose here means: extract bounded support surfaces from this repo without inheriting the full upstream shell.,,,,"the core controller, drag engine, pointer capture and lock behavior, scroll prevention, and React versus vanilla bindings.","Inspect manifests, README/docs, controller, gesture engines, React bindings, vanilla bindings, and input config parsing.","Audit pmndrs/use-gesture as a Browser gesture and pointer-input substrate candidate for HyperTwist. Inspect the core controller, drag engine, pointer capture and lock behavior, scroll prevention, and React versus vanilla bindings. Decide whether the retained value should remain active and what should stay bounded outside the HyperTwist core.",,,,,,,,,,,,,,medium,"Canonized Markdown dossier exists and the repo has been source-backed, but CSV backfill is later than the original v6.3 board generation.",medium,Source-backed dossier exists and the repo has been reconciled into the later Markdown authority stack.,,,,,,,,,,,,HT_browser_support,HT_browser_support_0015,browser / state / interaction,"Repurpose selectively for HyperTwist. Its source-backed role is a commodity browser gesture and richer pointer-input substrate, not product differentiation.",HyperTwist,browser / state / interaction,repurpose,moderate modification,medium,pmndrs/use-gesture,,Donor Bench,4.0,"Useful donor bench candidate for HyperTwist, primarily in the 'Browser gesture and pointer-input substrate' lane; a commodity browser gesture and richer pointer-input substrate, not product differentiation.",Browser gesture and pointer-input substrate,Included,P3,"pmndrs/use-gesture is placed in Donor Bench for HyperTwist because it provides a commodity browser gesture and richer pointer-input substrate, not product differentiation. Recommended action remains repurpose, but it should stay bounded to the Browser gesture and pointer-input substrate lane rather than reshape the core runtime.",,,,,,,pmndrs/use-gesture,,,,,,,,,,,,MIT,known_from_reference_material,uploaded_reference_docs,,,,,,,,,,Backfilled from canonized Markdown dossier pass on 2026-04-25: 79-pmndrs-use-gesture-upstream-dossier.md,v6_unified_source_of_truth_pack,,,,,permissive_or_noncopyleft_known,direct_incorporation_ok,The code license is MIT and direct use is allowed. Treat it as a bounded browser gesture and pointer-input substrate.,"Use directly as a bounded browser-side dependency for custom viewers, panels, and interaction surfaces.","Typically preserve notices, attribution, and license text where required.",Usually unnecessary unless later product-shaping concerns make selective replacement attractive.,high,standard-notice-review,yes,,,,,,,,,,,,,v6.3_markdown_backfill,Backfilled from canonized Markdown dossier pass on 2026-04-25: 79-pmndrs-use-gesture-upstream-dossier.md,implemented_live_permissive,landed_permissive_preserve,"Phase 3R-E closed. Preserve as the landed first-party embodied companion, narration, lip-sync, gesture, subtitle, and avatar-embed lane; start future widening from the live-lane audit, then the 3R-E implementation packet, then REPO_LICENSE_TRACKING.md." +,@react-spring/parallax,https://github.com/pmndrs/react-spring/tree/main/packages/parallax,HyperTwist,,,,,interface / visualization / shell surface,subsystem donor,interface donor,merge bench,integrate,moderate modification,"Retain the reusable internal layer, but replace shell assumptions and rebind boundaries so it plugs into HyperTwist cleanly.",,"Integrate selected subsystems rather than the whole product. Mine the repo for layered explainer behavior, scroll-driven motion, sticky layers, and narrative browser presentation; keep what materially shortens build time, but bind it to HyperTwist-owned data contracts, UI shell, and runtime boundaries.",,Integrate here means: merge bounded support surfaces from this repo into the HyperTwist companion stack.,,,,"the parallax runtime, sticky-layer behavior, scroll-driven spring motion, and imperative scrollTo flow.","Inspect manifests, README/docs, parallax package runtime, layer behavior, and scroll-controller code.","Audit @react-spring/parallax as a Browser layered-motion and explainer sidecar candidate for HyperTwist. Inspect the parallax runtime, sticky-layer behavior, scroll-driven spring motion, and imperative scrollTo flow. Decide whether the retained value should remain active and what should stay bounded outside the HyperTwist core.",,,,,,,,,,,,,,medium,"Canonized Markdown dossier exists and the repo has been source-backed, but CSV backfill is later than the original v6.3 board generation.",medium,Source-backed dossier exists and the repo has been reconciled into the later Markdown authority stack.,,,,,,,,,,,,HT_browser_support,HT_browser_support_0016,browser / 3D / XR / presentation,"Integrate selectively for HyperTwist. Its source-backed role is a bounded layered-motion and explainer sidecar beneath react-spring, not a runtime lane.",HyperTwist,browser / 3D / XR / presentation,integrate,moderate modification,medium,@react-spring/parallax,,Merge Bench,5.0,"Useful merge bench candidate for HyperTwist, primarily in the 'Browser layered-motion and explainer sidecar' lane; a bounded layered-motion and explainer sidecar beneath react-spring, not a runtime lane.",Browser layered-motion and explainer sidecar,Included,P4,"@react-spring/parallax is placed in Merge Bench for HyperTwist because it provides a bounded layered-motion and explainer sidecar beneath react-spring, not a runtime lane. Recommended action remains integrate, but it should stay bounded to the Browser layered-motion and explainer sidecar lane rather than reshape the core runtime.",,,,,,,@react-spring/parallax,,,,,,,,,,,,MIT,known_from_reference_material,uploaded_reference_docs,,,,,,,,,,Backfilled from canonized Markdown dossier pass on 2026-04-25: 81-react-spring-parallax-upstream-dossier.md,v6_unified_source_of_truth_pack,,,,,permissive_or_noncopyleft_known,direct_incorporation_ok,The code license is MIT and direct use is allowed. Treat it as a bounded layered-motion and explainer sidecar.,Use directly as a bounded browser-side dependency for explainer and narrative surfaces.,"Typically preserve notices, attribution, and license text where required.",Usually unnecessary unless later product-shaping concerns make selective replacement attractive.,high,standard-notice-review,yes,,,,,,,,,,,,,v6.3_markdown_backfill,Backfilled from canonized Markdown dossier pass on 2026-04-25: 81-react-spring-parallax-upstream-dossier.md,implemented_live_permissive,landed_permissive_preserve,"Phase 3R-E closed. Preserve as the landed first-party embodied companion, narration, lip-sync, gesture, subtitle, and avatar-embed lane; start future widening from the live-lane audit, then the 3R-E implementation packet, then REPO_LICENSE_TRACKING.md." +,@react-spring/rafz,https://github.com/pmndrs/react-spring/tree/main/packages/rafz,HyperTwist,,,,,interface / visualization / shell surface,subsystem donor,dependency donor,merge bench,integrate,moderate modification,"Retain the reusable internal layer, but replace shell assumptions and rebind boundaries so it plugs into HyperTwist cleanly.",,"Integrate selected subsystems rather than the whole product. Mine the repo for browser scheduling, phased queues, timeout handling, and motion-frame orchestration beneath higher-level UI motion; keep what materially shortens build time, but bind it to HyperTwist-owned data contracts, UI shell, and runtime boundaries.",,Integrate here means: merge bounded support surfaces from this repo into the HyperTwist companion stack.,,,,"the frame-loop phases, timeout scheduling, throttling, batched updates hook, and demand versus always control behavior.","Inspect manifests, README/docs, rafz package runtime, frame-loop scheduling, timeout handling, and queue behavior.","Audit @react-spring/rafz as a Browser frame-loop and scheduling utility candidate for HyperTwist. Inspect the frame-loop phases, timeout scheduling, throttling, batched updates hook, and demand versus always control behavior. Decide whether the retained value should remain active and what should stay bounded outside the HyperTwist core.",,,,,,,,,,,,,,medium,"Canonized Markdown dossier exists and the repo has been source-backed, but CSV backfill is later than the original v6.3 board generation.",medium,Source-backed dossier exists and the repo has been reconciled into the later Markdown authority stack.,,,,,,,,,,,,HT_browser_support,HT_browser_support_0017,browser / utilities / scheduling,"Integrate selectively for HyperTwist. Its source-backed role is a lower-level browser frame-loop and scheduling utility beneath react-spring, not a product lane.",HyperTwist,browser / utilities / scheduling,integrate,moderate modification,medium,@react-spring/rafz,,Merge Bench,5.0,"Useful merge bench candidate for HyperTwist, primarily in the 'Browser frame-loop and scheduling utility' lane; a lower-level browser frame-loop and scheduling utility beneath react-spring, not a product lane.",Browser frame-loop and scheduling utility,Included,P4,"@react-spring/rafz is placed in Merge Bench for HyperTwist because it provides a lower-level browser frame-loop and scheduling utility beneath react-spring, not a product lane. Recommended action remains integrate, but it should stay bounded to the Browser frame-loop and scheduling utility lane rather than reshape the core runtime.",,,,,,,@react-spring/rafz,,,,,,,,,,,,MIT,known_from_reference_material,uploaded_reference_docs,,,,,,,,,,Backfilled from canonized Markdown dossier pass on 2026-04-25: 82-react-spring-rafz-upstream-dossier.md,v6_unified_source_of_truth_pack,,,,,permissive_or_noncopyleft_known,direct_incorporation_ok,The code license is MIT and direct use is allowed. Treat it as a bounded browser scheduling utility.,Use directly as a bounded browser-side dependency beneath higher-level motion or interaction layers.,"Typically preserve notices, attribution, and license text where required.",Usually unnecessary unless later product-shaping concerns make selective replacement attractive.,high,standard-notice-review,yes,,,,,,,,,,,,,v6.3_markdown_backfill,Backfilled from canonized Markdown dossier pass on 2026-04-25: 82-react-spring-rafz-upstream-dossier.md,implemented_live_permissive,landed_permissive_preserve,"Phase 3R-E closed. Preserve as the landed first-party embodied companion, narration, lip-sync, gesture, subtitle, and avatar-embed lane; start future widening from the live-lane audit, then the 3R-E implementation packet, then REPO_LICENSE_TRACKING.md." +,@react-spring/animated,https://github.com/pmndrs/react-spring/tree/main/packages/animated,HyperTwist,,,,,interface / visualization / shell surface,subsystem donor,dependency donor,merge bench,integrate,moderate modification,"Retain the reusable internal layer, but replace shell assumptions and rebind boundaries so it plugs into HyperTwist cleanly.",,"Integrate selected subsystems rather than the whole product. Mine the repo for animatable-component hosting, animated-props observation, and low-level motion binding beneath higher-level browser motion; keep what materially shortens build time, but bind it to HyperTwist-owned data contracts, UI shell, and runtime boundaries.",,Integrate here means: merge bounded support surfaces from this repo into the HyperTwist companion stack.,,,,"the host-creation runtime, withAnimated wrapper, dependency observation, and native-update versus rerender behavior.","Inspect manifests, README/docs, animated package runtime, host creation, animated wrapper, and animated base-node behavior.","Audit @react-spring/animated as a Browser animatable-component substrate candidate for HyperTwist. Inspect the host-creation runtime, withAnimated wrapper, dependency observation, and native-update versus rerender behavior. Decide whether the retained value should remain active and what should stay bounded outside the HyperTwist core.",,,,,,,,,,,,,,medium,"Canonized Markdown dossier exists and the repo has been source-backed, but CSV backfill is later than the original v6.3 board generation.",medium,Source-backed dossier exists and the repo has been reconciled into the later Markdown authority stack.,,,,,,,,,,,,HT_browser_support,HT_browser_support_0018,browser / utilities / animation,"Integrate selectively for HyperTwist. Its source-backed role is a lower-level animatable-component host and animated-props substrate beneath react-spring, not a product lane.",HyperTwist,browser / utilities / animation,integrate,moderate modification,medium,@react-spring/animated,,Merge Bench,5.0,"Useful merge bench candidate for HyperTwist, primarily in the 'Browser animatable-component substrate' lane; a lower-level animatable-component host and animated-props substrate beneath react-spring, not a product lane.",Browser animatable-component substrate,Included,P4,"@react-spring/animated is placed in Merge Bench for HyperTwist because it provides a lower-level animatable-component host and animated-props substrate beneath react-spring, not a product lane. Recommended action remains integrate, but it should stay bounded to the Browser animatable-component substrate lane rather than reshape the core runtime.",,,,,,,@react-spring/animated,,,,,,,,,,,,MIT,known_from_reference_material,uploaded_reference_docs,,,,,,,,,,Backfilled from canonized Markdown dossier pass on 2026-04-25: 83-react-spring-animated-upstream-dossier.md,v6_unified_source_of_truth_pack,,,,,permissive_or_noncopyleft_known,direct_incorporation_ok,The code license is MIT and direct use is allowed. Treat it as a bounded animatable-component substrate.,Use directly as a bounded browser-side dependency beneath higher-level motion and UI layers.,"Typically preserve notices, attribution, and license text where required.",Usually unnecessary unless later product-shaping concerns make selective replacement attractive.,high,standard-notice-review,yes,,,,,,,,,,,,,v6.3_markdown_backfill,Backfilled from canonized Markdown dossier pass on 2026-04-25: 83-react-spring-animated-upstream-dossier.md,implemented_live_permissive,landed_permissive_preserve,"Phase 3R-E closed. Preserve as the landed first-party embodied companion, narration, lip-sync, gesture, subtitle, and avatar-embed lane; start future widening from the live-lane audit, then the 3R-E implementation packet, then REPO_LICENSE_TRACKING.md." +,@react-spring/core,https://github.com/pmndrs/react-spring/tree/main/packages/core,HyperTwist,,,,,interface / visualization / shell surface,subsystem donor,dependency donor,donor bench,repurpose,moderate modification,"Retain the valuable internal layer, but expect to replace upstream shell assumptions and rebind boundaries so it fits the HyperTwist architecture.",,"Repurpose selected subsystems rather than the whole product. Mine the repo for browser motion runtime, spring orchestration, frame advancement, and reusable motion-core behavior beneath higher-level UI layers; keep what materially shortens build time, but bind it to HyperTwist-owned data contracts, UI shell, and runtime boundaries.",,Repurpose here means: extract bounded support surfaces from this repo without inheriting the full upstream shell.,,,,"the Controller runtime, SpringValue motion engine, useSprings lifecycle, queueing, start-stop behavior, and frame advancement.","Inspect manifests, README/docs, core package runtime, Controller, SpringValue, and hook lifecycle behavior.","Audit @react-spring/core as a Browser spring-runtime core candidate for HyperTwist. Inspect the Controller runtime, SpringValue motion engine, useSprings lifecycle, queueing, start-stop behavior, and frame advancement. Decide whether the retained value should remain active and what should stay bounded outside the HyperTwist core.",,,,,,,,,,,,,,medium,"Canonized Markdown dossier exists and the repo has been source-backed, but CSV backfill is later than the original v6.3 board generation.",medium,Source-backed dossier exists and the repo has been reconciled into the later Markdown authority stack.,,,,,,,,,,,,HT_browser_support,HT_browser_support_0019,browser / utilities / animation,"Repurpose selectively for HyperTwist. Its source-backed role is the platform-agnostic spring-runtime core beneath react-spring, not a product foundation.",HyperTwist,browser / utilities / animation,repurpose,moderate modification,medium,@react-spring/core,,Donor Bench,4.0,"Useful donor bench candidate for HyperTwist, primarily in the 'Browser spring-runtime core' lane; the platform-agnostic spring-runtime core beneath react-spring, not a product foundation.",Browser spring-runtime core,Included,P3,"@react-spring/core is placed in Donor Bench for HyperTwist because it provides the platform-agnostic spring-runtime core beneath react-spring, not a product foundation. Recommended action remains repurpose, but it should stay bounded to the Browser spring-runtime core lane rather than reshape the core runtime.",,,,,,,@react-spring/core,,,,,,,,,,,,MIT,known_from_reference_material,uploaded_reference_docs,,,,,,,,,,Backfilled from canonized Markdown dossier pass on 2026-04-25: 84-react-spring-core-upstream-dossier.md,v6_unified_source_of_truth_pack,,,,,permissive_or_noncopyleft_known,direct_incorporation_ok,The code license is MIT and direct use is allowed. Treat it as a bounded spring-runtime core beneath higher-level motion layers.,Use directly as a bounded browser-side dependency beneath higher-level motion and interaction layers.,"Typically preserve notices, attribution, and license text where required.",Usually unnecessary unless later product-shaping concerns make selective replacement attractive.,high,standard-notice-review,yes,,,,,,,,,,,,,v6.3_markdown_backfill,Backfilled from canonized Markdown dossier pass on 2026-04-25: 84-react-spring-core-upstream-dossier.md,implemented_live_permissive,landed_permissive_preserve,"Phase 3R-E closed. Preserve as the landed first-party embodied companion, narration, lip-sync, gesture, subtitle, and avatar-embed lane; start future widening from the live-lane audit, then the 3R-E implementation packet, then REPO_LICENSE_TRACKING.md." +,@react-spring/shared,https://github.com/pmndrs/react-spring/tree/main/packages/shared,HyperTwist,,,,,interface / visualization / shell surface,subsystem donor,dependency donor,merge bench,integrate,moderate modification,"Retain the reusable internal layer, but replace shell assumptions and rebind boundaries so it plugs into HyperTwist cleanly.",,"Integrate selected subsystems rather than the whole product. Mine the repo for motion utilities, frame-loop customization, interpolation, and fluid observation beneath higher-level browser motion; keep what materially shortens build time, but bind it to HyperTwist-owned data contracts, UI shell, and runtime boundaries.",,Integrate here means: merge bounded support surfaces from this repo into the HyperTwist companion stack.,,,,"the globals customization seams, frame-loop behavior, interpolation helpers, and fluid observer substrate.","Inspect manifests, README/docs, shared package exports, globals, frame loop, interpolation, and fluid observer modules.","Audit @react-spring/shared as a Browser motion utility substrate candidate for HyperTwist. Inspect the globals customization seams, frame-loop behavior, interpolation helpers, and fluid observer substrate. Decide whether the retained value should remain active and what should stay bounded outside the HyperTwist core.",,,,,,,,,,,,,,medium,"Canonized Markdown dossier exists and the repo has been source-backed, but CSV backfill is later than the original v6.3 board generation.",medium,Source-backed dossier exists and the repo has been reconciled into the later Markdown authority stack.,,,,,,,,,,,,HT_browser_support,HT_browser_support_0020,browser / utilities / animation,"Integrate selectively for HyperTwist. Its source-backed role is a lower-level motion utility and fluid-observer substrate beneath react-spring, not a product lane.",HyperTwist,browser / utilities / animation,integrate,moderate modification,medium,@react-spring/shared,,Merge Bench,5.0,"Useful merge bench candidate for HyperTwist, primarily in the 'Browser motion utility substrate' lane; a lower-level motion utility and fluid-observer substrate beneath react-spring, not a product lane.",Browser motion utility substrate,Included,P4,"@react-spring/shared is placed in Merge Bench for HyperTwist because it provides a lower-level motion utility and fluid-observer substrate beneath react-spring, not a product lane. Recommended action remains integrate, but it should stay bounded to the Browser motion utility substrate lane rather than reshape the core runtime.",,,,,,,@react-spring/shared,,,,,,,,,,,,MIT,known_from_reference_material,uploaded_reference_docs,,,,,,,,,,Backfilled from canonized Markdown dossier pass on 2026-04-25: 85-react-spring-shared-upstream-dossier.md,v6_unified_source_of_truth_pack,,,,,permissive_or_noncopyleft_known,direct_incorporation_ok,The code license is MIT and direct use is allowed. Treat it as a bounded motion utility substrate.,Use directly as a bounded browser-side dependency beneath higher-level motion layers.,"Typically preserve notices, attribution, and license text where required.",Usually unnecessary unless later product-shaping concerns make selective replacement attractive.,high,standard-notice-review,yes,,,,,,,,,,,,,v6.3_markdown_backfill,Backfilled from canonized Markdown dossier pass on 2026-04-25: 85-react-spring-shared-upstream-dossier.md,implemented_live_permissive,landed_permissive_preserve,"Phase 3R-E closed. Preserve as the landed first-party embodied companion, narration, lip-sync, gesture, subtitle, and avatar-embed lane; start future widening from the live-lane audit, then the 3R-E implementation packet, then REPO_LICENSE_TRACKING.md." +,@react-spring/types,https://github.com/pmndrs/react-spring/tree/main/packages/types,HyperTwist,,,,,interface / visualization / shell surface,subsystem donor,dependency donor,merge bench,integrate,moderate modification,"Retain the reusable internal layer, but replace shell assumptions and rebind boundaries so it plugs into HyperTwist cleanly.",,"Integrate selected subsystems rather than the whole product. Mine the repo for shared type contracts and package-design substrate beneath browser motion layers; keep what materially shortens build time, but bind it to HyperTwist-owned data contracts, UI shell, and runtime boundaries.",,Integrate here means: merge bounded support surfaces from this repo into the HyperTwist companion stack.,,,,"the shared type-contract surface, animatable and interpolation types, and utility-type exports used across react-spring packages.","Inspect manifests, type package exports, shared type files, interpolation type definitions, and utility-type modules.","Audit @react-spring/types as a Browser motion type-contract substrate candidate for HyperTwist. Inspect the shared type-contract surface, animatable and interpolation types, and utility-type exports used across react-spring packages. Decide whether the retained value should remain active and what should stay bounded outside the HyperTwist core.",,,,,,,,,,,,,,medium,"Canonized Markdown dossier exists and the repo has been source-backed, but CSV backfill is later than the original v6.3 board generation.",medium,Source-backed dossier exists and the repo has been reconciled into the later Markdown authority stack.,,,,,,,,,,,,HT_browser_support,HT_browser_support_0021,browser / utilities / animation,"Integrate selectively for HyperTwist. Its source-backed role is a narrow type-contract substrate beneath react-spring, not a behavior-heavy donor or product lane.",HyperTwist,browser / utilities / animation,integrate,moderate modification,medium,@react-spring/types,,Merge Bench,5.0,"Useful merge bench candidate for HyperTwist, primarily in the 'Browser motion type-contract substrate' lane; a narrow type-contract substrate beneath react-spring, not a behavior-heavy donor or product lane.",Browser motion type-contract substrate,Included,P4,"@react-spring/types is placed in Merge Bench for HyperTwist because it provides a narrow type-contract substrate beneath react-spring, not a behavior-heavy donor or product lane. Recommended action remains integrate, but it should stay bounded to the Browser motion type-contract substrate lane rather than reshape the core runtime.",,,,,,,@react-spring/types,,,,,,,,,,,,MIT,known_from_reference_material,uploaded_reference_docs,,,,,,,,,,Backfilled from canonized Markdown dossier pass on 2026-04-25: 86-react-spring-types-upstream-dossier.md,v6_unified_source_of_truth_pack,,,,,permissive_or_noncopyleft_known,direct_incorporation_ok,The code license is MIT and direct use is allowed. Treat it as a bounded type-contract substrate.,Use directly as a bounded browser-side dependency where those contracts are actually needed.,"Typically preserve notices, attribution, and license text where required.",Usually unnecessary unless later product-shaping concerns make selective replacement attractive.,high,standard-notice-review,yes,,,,,,,,,,,,,v6.3_markdown_backfill,Backfilled from canonized Markdown dossier pass on 2026-04-25: 86-react-spring-types-upstream-dossier.md,implemented_live_permissive,landed_permissive_preserve,"Phase 3R-E closed. Preserve as the landed first-party embodied companion, narration, lip-sync, gesture, subtitle, and avatar-embed lane; start future widening from the live-lane audit, then the 3R-E implementation packet, then REPO_LICENSE_TRACKING.md." diff --git a/docs/repo_portfolio_unified_source_audit_v6_3.csv b/docs/repo_portfolio_unified_source_audit_v6_3.csv index 8b81714..06d32c1 100644 --- a/docs/repo_portfolio_unified_source_audit_v6_3.csv +++ b/docs/repo_portfolio_unified_source_audit_v6_3.csv @@ -275,7 +275,7 @@ rhasspy/piper,https://github.com/rhasspy/piper,multi-project,Donor Bench,Cross-p 7) Reasons to promote / retain / demote 8) Confidence change after source audit 9) Open questions / blockers","Primary: Phase G v4 board (canonical ranking and current bucket); Operational v3 board filtered to this repo; Merger matrix rows involving this repo; VS Code packet row for this repo, if present. Optional: Cluster narratives row for matching cluster; Bookmark occurrence rows for this repo. Do not attach v1/v2 or preliminary memo unless a judgment conflict, lineage ambiguity, or rationale gap needs arbitration.","rhasspy/piper is placed in Donor Bench for multi-project because it provides the leanest current local TTS runtime seam in the voice stack. Recommended action remains repurpose, but the real retained value is ONNX and eSpeak runtime simplicity, streaming output, and deployable local HTTP wrapping rather than broad voice-platform scope.","Useful subsystem donor for multi-project, primarily in the 'Cross-project / future-adjacent' role; lean direct local TTS sidecar candidate.","Audit rhasspy/piper as a voice / multimodal I/O candidate for multi-project. Do not stop at README-level features. Inspect: C++ runtime core, voice loading and download path, streaming output, HTTP service boundary, speaker and phonemization config, and selected voice artifact constraints. Decide whether it should remain the lean direct local TTS sidecar candidate and what should stay behind a bounded local voice seam. Test the three merger paths in order: 1) project-local anchor [base + donor]; 2) shared portfolio utility [augmenter]; 3) cross-project transfer candidate [future merger]. Return hidden modules, reusable schemas, protocol layers, runtime boundaries, tests/fixtures, and any subsystem stronger than the visible shell.",MU_misc_0004,MU_misc,rhasspy/piper,,,,,,,Original global P0-P3 source audit retained,MIT code; voice artifacts reviewed separately,known_from_reference_material,uploaded_reference_docs,no,,,,Supplemental intake references are advisory only; v6 adjudication remains the source of truth.,Potentially relevant,yes,v6 unified all-project source-of-truth pack,v5_carry_forward,,v6_unified_source_of_truth_pack,4,3,71.0,permissive_or_noncopyleft_known,direct_incorporation_ok,"The code license is MIT and direct use is allowed. The real review point is selected voice artifacts, not the runtime code; keep voice selection separate from code adoption.",Use directly as a bounded local TTS sidecar or simple HTTP service; keep selected voice artifacts under separate review.,"Typically preserve notices, attribution, and license text where required; review chosen voices or model cards separately from the code license.",Usually unnecessary unless you later replace the runtime for packaging or architecture reasons.,high,voice-artifact-review-required,yes,,,,,,,,,,,,,v6.3_final_source_of_truth,Merged v6.1 copyleft layer and v6.2 SRE layer; use v6.3 docs + workbook as canonical handoff.,,, -met4citizen/TalkingHead,https://github.com/met4citizen/TalkingHead,HyperTwist,Donor Bench,Browser embodied coach surface,P2,,,,,,medium,"Retain the reusable avatar, lip-sync, and retargeting layers, but replace the demo shell, asset assumptions, and voice-service integration with HyperTwist-owned surfaces.",repurpose,moderate modification,Determine whether TalkingHead should remain the primary embodied coach donor and which runtime seams should stay bounded.,"avatar runtime, lip-sync queueing, streamed speech, subtitle timing, avatarOnly embedding, retargeting","Inspect modules, examples, tests, site config, streaming demos, retargeter, and playback worklet code. Look for embodied-coach embedding, lip-sync, subtitle timing, gesture and expression surfaces, and asset assumptions.",Inspect talkinghead runtime; speech queueing and streaming; viseme and blendshape flow; avatarOnly embedding; retargeting; and audio worklet behavior.,"Repurpose selected subsystems rather than the whole product. Mine the repo for embodied coach avatar runtime, lip-sync and subtitle timing, avatar-only embedding, retargeting, and streamed speech playback; keep what shortens build time, but rebind assets, voice services, and UI shell to the HyperTwist architecture.",,Repurpose here means: turn it into a browser-side embodied coach or companion layer.,,,,,,,,,,,,"Upgrade if source reveals unusually reusable browser-runtime seams, clean adapter boundaries, robust tests, and direct leverage for HyperTwist companion surfaces.","Demote if retained value is mostly commodity glue, tightly bound to upstream shell assumptions, or clearly dominated by stronger neighboring repos in the same lane.",Capability inventory + salvage targets + donor-tier verdict,1) Confirmed source-backed browser/XR capabilities; 2) Best retained modules; 3) Boundaries to keep outside HyperTwist core; 4) Recommended pairing or dependency posture; 5) Risks or licensing notes.,Primary: HT_browser_surface cluster packet plus the repo-specific Markdown dossier. Optional: companion browser/XR rows in the same cluster.,"met4citizen/TalkingHead is placed in Donor Bench for HyperTwist because it provides embodied coach UI, streaming lip-sync, retargeting, and avatar-only embedding behavior. Recommended action remains repurpose, but the retained value is a bounded browser coach surface rather than a general avatar product.","Useful subsystem donor for HyperTwist, primarily in the browser companion layer; strongest embodied coach and avatar presentation donor in the current stack.","Audit met4citizen/TalkingHead as a browser embodied-coach candidate for HyperTwist. Inspect the avatar runtime, streaming lip-sync, subtitle timing, avatarOnly embedding, retargeting, and audio worklet behavior. Decide which seams can be used directly and which must remain bounded behind the HyperTwist coaching shell.",HT_browser_surface_0001,HT_browser_surface,met4citizen/talkinghead,,,,,,,,MIT,known_from_reference_material,uploaded_reference_docs,,,,,,,,,,,v6_unified_source_of_truth_pack,,,,permissive_or_noncopyleft_known,direct_incorporation_ok,The code license is MIT and direct use is allowed. Treat it as a bounded browser-side donor for embodied coach presentation rather than as a product shell.,"Use directly as a bounded browser-side dependency or adapter layer; keep voice services, product logic, and asset provenance outside the upstream shell.","Typically preserve notices, attribution, and license text where required; review sample avatars or media separately from the code license.",Usually unnecessary unless you later replace a narrow upstream layer for product-shaping reasons.,high,standard-notice-review,yes,,,,,,,,,,,,,v6.3_markdown_backfill,Backfilled from canonized Markdown dossier pass on 2026-04-24.,selected_not_live_permissive_candidate,phase0r_permissive_eval_then_implement,"Phase 1R closed. Retain as a Phase 3R permissive implementation candidate; implement only from its packet authority and the retained-set contract, not by reopening Phase 0R." +met4citizen/TalkingHead,https://github.com/met4citizen/TalkingHead,HyperTwist,Donor Bench,Browser embodied coach surface,P2,,,,,,medium,"Retain the reusable avatar, lip-sync, and retargeting layers, but replace the demo shell, asset assumptions, and voice-service integration with HyperTwist-owned surfaces.",repurpose,moderate modification,Determine whether TalkingHead should remain the primary embodied coach donor and which runtime seams should stay bounded.,"avatar runtime, lip-sync queueing, streamed speech, subtitle timing, avatarOnly embedding, retargeting","Inspect modules, examples, tests, site config, streaming demos, retargeter, and playback worklet code. Look for embodied-coach embedding, lip-sync, subtitle timing, gesture and expression surfaces, and asset assumptions.",Inspect talkinghead runtime; speech queueing and streaming; viseme and blendshape flow; avatarOnly embedding; retargeting; and audio worklet behavior.,"Repurpose selected subsystems rather than the whole product. Mine the repo for embodied coach avatar runtime, lip-sync and subtitle timing, avatar-only embedding, retargeting, and streamed speech playback; keep what shortens build time, but rebind assets, voice services, and UI shell to the HyperTwist architecture.",,Repurpose here means: turn it into a browser-side embodied coach or companion layer.,,,,,,,,,,,,"Upgrade if source reveals unusually reusable browser-runtime seams, clean adapter boundaries, robust tests, and direct leverage for HyperTwist companion surfaces.","Demote if retained value is mostly commodity glue, tightly bound to upstream shell assumptions, or clearly dominated by stronger neighboring repos in the same lane.",Capability inventory + salvage targets + donor-tier verdict,1) Confirmed source-backed browser/XR capabilities; 2) Best retained modules; 3) Boundaries to keep outside HyperTwist core; 4) Recommended pairing or dependency posture; 5) Risks or licensing notes.,Primary: HT_browser_surface cluster packet plus the repo-specific Markdown dossier. Optional: companion browser/XR rows in the same cluster.,"met4citizen/TalkingHead is placed in Donor Bench for HyperTwist because it provides embodied coach UI, streaming lip-sync, retargeting, and avatar-only embedding behavior. Recommended action remains repurpose, but the retained value is a bounded browser coach surface rather than a general avatar product.","Useful subsystem donor for HyperTwist, primarily in the browser companion layer; strongest embodied coach and avatar presentation donor in the current stack.","Audit met4citizen/TalkingHead as a browser embodied-coach candidate for HyperTwist. Inspect the avatar runtime, streaming lip-sync, subtitle timing, avatarOnly embedding, retargeting, and audio worklet behavior. Decide which seams can be used directly and which must remain bounded behind the HyperTwist coaching shell.",HT_browser_surface_0001,HT_browser_surface,met4citizen/talkinghead,,,,,,,,MIT,known_from_reference_material,uploaded_reference_docs,,,,,,,,,,,v6_unified_source_of_truth_pack,,,,permissive_or_noncopyleft_known,direct_incorporation_ok,The code license is MIT and direct use is allowed. Treat it as a bounded browser-side donor for embodied coach presentation rather than as a product shell.,"Use directly as a bounded browser-side dependency or adapter layer; keep voice services, product logic, and asset provenance outside the upstream shell.","Typically preserve notices, attribution, and license text where required; review sample avatars or media separately from the code license.",Usually unnecessary unless you later replace a narrow upstream layer for product-shaping reasons.,high,standard-notice-review,yes,,,,,,,,,,,,,v6.3_markdown_backfill,Backfilled from canonized Markdown dossier pass on 2026-04-24.,implemented_live_permissive,landed_permissive_preserve,"Phase 3R-E closed. Preserve as the landed first-party embodied companion, narration, lip-sync, gesture, subtitle, and avatar-embed lane; start future widening from the live-lane audit, then the 3R-E implementation packet, then REPO_LICENSE_TRACKING.md." apache/echarts,https://github.com/apache/echarts,HyperTwist,Donor Bench,Browser analytics and reporting surface,P2,,,,,,medium,"Retain the reusable chart runtime and reporting patterns, but keep HyperTwist domain schemas, page shell, and training logic outside the upstream system.",repurpose,moderate modification,Determine whether echarts should remain the primary browser analytics and reporting donor for HyperTwist companion surfaces.,"option manager, datastore, zoom and history, thumbnail and export, SSR, chart modularity","Inspect manifests, README/docs, src core, model, data, component, export, and SSR folders. Look for modular chart runtime, data-store abstractions, export surfaces, and reporting-specific UI behavior.","Inspect OptionManager, DataStore, zoom and history behavior, thumbnail and export features, SSR and hydration seams, and accessibility surface.","Repurpose selected subsystems rather than the whole product. Mine the repo for chart runtime, option and data-store patterns, export and save-as-image behavior, zoom and history handling, and SSR reporting surfaces; keep what shortens build time, but rebind analytics schemas and application shell to the HyperTwist architecture.",,"Repurpose here means: turn it into a bounded browser analytics and reporting layer for dashboards, replay summaries, and coaching views.",,,,,,,,,,,,"Upgrade if source reveals unusually reusable browser-runtime seams, clean adapter boundaries, robust tests, and direct leverage for HyperTwist companion surfaces.","Demote if retained value is mostly commodity glue, tightly bound to upstream shell assumptions, or clearly dominated by stronger neighboring repos in the same lane.",Capability inventory + salvage targets + donor-tier verdict,1) Confirmed source-backed browser/XR capabilities; 2) Best retained modules; 3) Boundaries to keep outside HyperTwist core; 4) Recommended pairing or dependency posture; 5) Risks or licensing notes.,Primary: HT_browser_surface cluster packet plus the repo-specific Markdown dossier. Optional: companion browser/XR rows in the same cluster.,"apache/echarts is placed in Donor Bench for HyperTwist because it provides the strongest current browser analytics and reporting stack with SSR, export, and serious data-store behavior. Recommended action remains repurpose, but the retained value is bounded reporting and coaching analytics rather than a product shell.","Useful subsystem donor for HyperTwist, primarily in the browser companion layer; strongest current analytics and reporting donor in the browser stack.","Audit apache/echarts as a browser analytics and reporting candidate for HyperTwist. Inspect the modular chart runtime, OptionManager and DataStore, export surfaces, zoom and history behavior, SSR path, and accessibility seams. Decide which parts should remain direct dependencies versus concept-only references.",HT_browser_surface_0002,HT_browser_surface,apache/echarts,,,,,,,,Apache-2.0,known_from_reference_material,uploaded_reference_docs,,,,,,,,,,,v6_unified_source_of_truth_pack,,,,permissive_or_noncopyleft_known,direct_incorporation_ok,The code license is Apache-2.0 and direct use is allowed. Treat it as a bounded reporting and analytics donor.,Use directly as a bounded browser analytics dependency; keep HyperTwist data contracts and product logic outside the upstream shell.,Preserve LICENSE and NOTICE materials where required and review redistributed assets separately from the code license.,Usually unnecessary unless you later replace a narrow upstream layer for product-shaping reasons.,high,notice-file-review,yes,,,,,,,,,,,,,v6.3_markdown_backfill,Backfilled from canonized Markdown dossier pass on 2026-04-24.,implemented_live_permissive,landed_permissive_preserve,"Phase 3R-C closed. Preserve as the landed first-party analytics, reporting, export, and progress-visualization lane; start future widening from the live-lane audit, then the 3R-C implementation packet, then REPO_LICENSE_TRACKING.md." ecomfe/echarts-gl,https://github.com/ecomfe/echarts-gl,HyperTwist,Merge Bench,Browser 3D analytics and explainer surface,P3,,,,,,medium,"Retain selective 3D analytics surfaces, but keep HyperTwist domain models, scene ownership, and broader product shell outside the upstream package.",integrate,moderate modification,Determine whether echarts-gl should remain the bounded 3D analytics extension beneath echarts and what should stay outside HyperTwist core.,"3D chart exports, GL layer mounting, graph and flow surfaces, view helper behavior, interaction model","Inspect manifests, README/docs, src chart and component exports, GL helper modules, and integration points with echarts and zrender.","Inspect 3D and GL chart exports, GL layer mounting, graph and flow surfaces, view helper behavior, and chart-space interaction handling.","Integrate selected subsystems rather than the whole product. Mine the repo for 3D analytics and explainer surfaces, GL layer mounting, and view helper behavior; keep what shortens build time, but bind it to HyperTwist analytics schemas and browser companion UI.",,Integrate here means: merge bounded 3D analytics and explainer surfaces into the browser reporting stack.,,,,,,,,,,,,"Upgrade if source reveals unusually reusable browser-runtime seams, clean adapter boundaries, robust tests, and direct leverage for HyperTwist companion surfaces.","Demote if retained value is mostly commodity glue, tightly bound to upstream shell assumptions, or clearly dominated by stronger neighboring repos in the same lane.",Capability inventory + salvage targets + donor-tier verdict,1) Confirmed source-backed browser/XR capabilities; 2) Best retained modules; 3) Boundaries to keep outside HyperTwist core; 4) Recommended pairing or dependency posture; 5) Risks or licensing notes.,Primary: HT_browser_surface cluster packet plus the repo-specific Markdown dossier. Optional: companion browser/XR rows in the same cluster.,"ecomfe/echarts-gl is placed in Merge Bench for HyperTwist because it adds bounded 3D analytics and explainer value on top of echarts. Recommended action remains integrate, but the retained value is selective 3D reporting and graph surface behavior rather than a product runtime.","Useful merge candidate for HyperTwist, primarily in the browser companion layer; strongest value sits in 3D chart and GL explainer surfaces beneath the echarts lane.","Audit ecomfe/echarts-gl as a browser 3D analytics companion to apache/echarts. Inspect the 3D chart exports, GL view handling, and interaction seams. Decide which pieces deserve direct dependency use versus conceptual guidance only.",HT_browser_surface_0003,HT_browser_surface,ecomfe/echarts-gl,,,,,,,,BSD-3-Clause,known_from_reference_material,uploaded_reference_docs,,,,,,,,,,,v6_unified_source_of_truth_pack,,,,permissive_or_noncopyleft_known,direct_incorporation_ok,The code license is BSD-3-Clause and direct use is allowed. Treat it as a bounded 3D analytics extension rather than a runtime foundation.,Use directly as a bounded browser-side dependency beneath the reporting stack; keep HyperTwist scene ownership and product logic outside the upstream shell.,"Typically preserve notices, attribution, and license text where required.",Usually unnecessary unless you later replace a narrow upstream layer for product-shaping reasons.,high,standard-notice-review,yes,,,,,,,,,,,,,v6.3_markdown_backfill,Backfilled from canonized Markdown dossier pass on 2026-04-24.,selected_not_live_permissive_candidate,phase0r_permissive_eval_then_implement,"Phase 3R-C closed for the anchor. Retain as an optional subordinate 3D analytics and explainer sidecar beneath the landed apache/echarts lane; do not treat it as separately live." KhronosGroup/glTF-Sample-Viewer,https://github.com/KhronosGroup/glTF-Sample-Viewer,HyperTwist,Donor Bench,Browser asset validation and viewer surface,P3,,,,,,medium,"Retain the useful asset-validation and viewer surfaces, but keep HyperTwist asset flows, editor shell, and product logic outside the upstream viewer.",repurpose,moderate modification,Determine whether glTF-Sample-Viewer should remain the primary standards-validation viewer donor for browser asset tooling.,"validator integration, material variants, environment controls, capture flow, renderer handoff, viewer shell","Inspect manifests, README/docs, src main and UI logic, bundled renderer submodule, and validation-related surfaces.","Inspect validator integration, material-variant support, environment and tone-mapping controls, capture behavior, and the relationship to glTF-Sample-Renderer.","Repurpose selected subsystems rather than the whole product. Mine the repo for standards-aware asset preview, validation, capture, environment control, and viewer-shell behavior; keep what shortens build time, but bind it to HyperTwist asset tooling and browser companion surfaces.",,Repurpose here means: turn it into a bounded asset-validation and preview donor for browser tooling.,,,,,,,,,,,,"Upgrade if source reveals unusually reusable browser-runtime seams, clean adapter boundaries, robust tests, and direct leverage for HyperTwist companion surfaces.","Demote if retained value is mostly commodity glue, tightly bound to upstream shell assumptions, or clearly dominated by stronger neighboring repos in the same lane.",Capability inventory + salvage targets + donor-tier verdict,1) Confirmed source-backed browser/XR capabilities; 2) Best retained modules; 3) Boundaries to keep outside HyperTwist core; 4) Recommended pairing or dependency posture; 5) Risks or licensing notes.,Primary: HT_browser_surface cluster packet plus the repo-specific Markdown dossier. Optional: companion browser/XR rows in the same cluster.,"KhronosGroup/glTF-Sample-Viewer is placed in Donor Bench for HyperTwist because it provides standards-aware asset validation, inspection, and viewer behavior. Recommended action remains repurpose, but the retained value is bounded asset QA and preview tooling rather than gameplay or runtime ownership.","Useful subsystem donor for HyperTwist, primarily in the browser companion layer; strongest value sits in official glTF standards validation and inspection tooling.","Audit KhronosGroup/glTF-Sample-Viewer as a browser asset-validation and inspection candidate for HyperTwist. Inspect validator integration, capture flow, material variants, environment controls, and the renderer handoff. Decide which surfaces deserve direct use or selective extraction.",HT_browser_surface_0004,HT_browser_surface,khronosgroup/gltf-sample-viewer,,,,,,,,Apache-2.0,known_from_reference_material,uploaded_reference_docs,,,,,,,,,,,v6_unified_source_of_truth_pack,,,,permissive_or_noncopyleft_known,direct_incorporation_ok,The code license is Apache-2.0 and direct use is allowed. Treat it as a bounded standards-viewer and asset-QA donor.,Use directly as a bounded asset-validation dependency or sidecar; keep HyperTwist asset workflows and product logic outside the upstream viewer shell.,Preserve LICENSE and NOTICE materials where required.,Usually unnecessary unless you later replace a narrow upstream layer for product-shaping reasons.,high,notice-file-review,yes,,,,,,,,,,,,,v6.3_markdown_backfill,Backfilled from canonized Markdown dossier pass on 2026-04-24.,selected_not_live_permissive_candidate,phase0r_permissive_eval_then_implement,"Phase 3R-D closed for the anchor. Retain as the subordinate standards-aware asset QA and validation sidecar beneath the landed google/model-viewer lane; do not treat it as separately live." diff --git a/docs/v6_5_deep_manual_pack/HyperTwist/AGENTS.md b/docs/v6_5_deep_manual_pack/HyperTwist/AGENTS.md index db478c1..28fc481 100644 --- a/docs/v6_5_deep_manual_pack/HyperTwist/AGENTS.md +++ b/docs/v6_5_deep_manual_pack/HyperTwist/AGENTS.md @@ -75,8 +75,8 @@ For any HyperTwist repo, the coding model must determine: For HyperTwist, keep this explicit: - current shallow-eval set: `71` repos -- currently verified live/implemented in checked Unreal surfaces: `7` -- permissive live lanes: `6` +- currently verified live/implemented in checked Unreal surfaces: `11` +- permissive live lanes: `10` - 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 @@ -96,5 +96,5 @@ into: Before recommending new HyperTwist donor-shaped widening from the remaining `61` current non-live rows: - do not reopen the already closed `Phase 0R`, `Phase 1R`, or `Phase 2R` packets -- preserve the ten landed rows as current truth -- continue from the closed packet sequence, currently `Phase 3R-E` +- preserve the eleven landed rows as current truth +- continue from the closed packet sequence, currently `Phase 3R-F` diff --git a/docs/v6_5_deep_manual_pack/HyperTwist/DEVELOPMENT.md b/docs/v6_5_deep_manual_pack/HyperTwist/DEVELOPMENT.md index 5ee313a..3c9b01d 100644 --- a/docs/v6_5_deep_manual_pack/HyperTwist/DEVELOPMENT.md +++ b/docs/v6_5_deep_manual_pack/HyperTwist/DEVELOPMENT.md @@ -15,8 +15,8 @@ Do not reopen broad donor-driven widening as if the whole retained portfolio wer Current truth: -- `10` repos are currently verified live in checked Unreal surfaces -- `9` are permissive `MIT` or `Apache-2.0` +- `11` repos are currently verified live in checked Unreal surfaces +- `10` are permissive `MIT` or `Apache-2.0` - `1` is the restrictive `onionhoney/roux-trainers` lane that is already properly clean-roomed and implemented - `Phase 0R` is now closed for the remaining `61` non-live rows - `Phase 1R` is now closed as the retained-set contract and handoff overhaul @@ -25,13 +25,14 @@ Current truth: - `Phase 3R-B` is now closed as the landed `Hypercubers/hypercubing.xyz` widening packet - `Phase 3R-C` is now closed as the landed `apache/echarts` widening packet - `Phase 3R-D` is now closed as the landed `google/model-viewer` widening packet +- `Phase 3R-E` is now closed as the landed `met4citizen/TalkingHead` widening packet Next sequence: -1. preserve the ten landed lanes +1. preserve the eleven landed lanes 2. use the retained-set contract as the only legal/roadmap routing surface for non-live rows -3. keep `Aarav2709/KubeTimr`, `Hypercubers/hypercubing.xyz`, `apache/echarts`, and `google/model-viewer` on preserve-and-enhance footing through their landed packets -4. continue broader permissive widening from `Phase 3R-E` +3. keep `Aarav2709/KubeTimr`, `Hypercubers/hypercubing.xyz`, `apache/echarts`, `google/model-viewer`, and `met4citizen/TalkingHead` on preserve-and-enhance footing through their landed packets +4. continue broader permissive widening from `Phase 3R-F` ## Suggested repo structure diff --git a/docs/v6_5_deep_manual_pack/HyperTwist/LICENSETRACKING.md b/docs/v6_5_deep_manual_pack/HyperTwist/LICENSETRACKING.md index 5eaef16..501a812 100644 --- a/docs/v6_5_deep_manual_pack/HyperTwist/LICENSETRACKING.md +++ b/docs/v6_5_deep_manual_pack/HyperTwist/LICENSETRACKING.md @@ -42,18 +42,20 @@ They still must point back to `C:\HyperTwist\docs\REPO_LICENSE_TRACKING.md` for At the moment, HyperTwist should be described this way: - current curated shallow-eval set: `71` repos -- currently verified live/implemented in checked Unreal surfaces: `9` -- permissive live lanes: `8` +- currently verified live/implemented in checked Unreal surfaces: `11` +- permissive live lanes: `10` - restrictive live lanes: `1` -The eight permissive live lanes are: +The ten permissive live lanes are: - `Aarav2709/KubeTimr` - `apache/echarts` - `abunickabhi/5style-Trainer` +- `google/model-viewer` - `Hypercubers/hypercubing.xyz` - `tao-yu/Alg-Trainer` - `Lykos/cube_trainer` +- `met4citizen/TalkingHead` - `poliva/cubedex` - `newyork-anthonyng/rubiks-cross-trainer` @@ -114,7 +116,7 @@ Current practical interpretation: - `Phase 2R-B` is now fully closed for the primary retained permissive support-plane rows in scope - `Phase 2R-C` is now fully closed for the final residual `0R-B` permissive rows - `Phase 2R` is now fully closed for the retained permissive set -- the ten already-live rows now have source-backed preservation authority in `C:\HyperTwist\docs\HYPERTWIST_LIVE_LANES_SOURCE_AND_PRESERVATION_AUDIT_2026-05-13.md` +- the eleven already-live rows now have source-backed preservation authority in `C:\HyperTwist\docs\HYPERTWIST_LIVE_LANES_SOURCE_AND_PRESERVATION_AUDIT_2026-05-13.md` - the retained-set contract now lives in `C:\HyperTwist\docs\HYPERTWIST_PHASE_1R_RETAINED_SET_CONTRACT_AND_HANDOFF_2026-05-13.md` - the core ownership and acceptance packet now lives in `C:\HyperTwist\docs\HYPERTWIST_PHASE_2R_PACKET_2R_A_OWNERSHIP_AND_ACCEPTANCE_CONTRACT_2026-05-13.md` - the support-plane ownership and acceptance packet now lives in `C:\HyperTwist\docs\HYPERTWIST_PHASE_2R_PACKET_2R_B_OWNERSHIP_AND_ACCEPTANCE_CONTRACT_2026-05-13.md` @@ -123,7 +125,8 @@ Current practical interpretation: - the landed `Hypercubers/hypercubing.xyz` widening packet now lives in `C:\HyperTwist\docs\HYPERTWIST_PHASE_3R_PACKET_3R_B_HYPERCUBING_XYZ_IMPLEMENTATION_2026-05-13.md` - the landed `apache/echarts` widening packet now lives in `C:\HyperTwist\docs\HYPERTWIST_PHASE_3R_PACKET_3R_C_ECHARTS_IMPLEMENTATION_2026-05-13.md` - the landed `google/model-viewer` widening packet now lives in `C:\HyperTwist\docs\HYPERTWIST_PHASE_3R_PACKET_3R_D_MODEL_VIEWER_IMPLEMENTATION_2026-05-13.md` -- the next bounded move is `Phase 3R-E` +- the landed `met4citizen/TalkingHead` widening packet now lives in `C:\HyperTwist\docs\HYPERTWIST_PHASE_3R_PACKET_3R_E_TALKINGHEAD_IMPLEMENTATION_2026-05-13.md` +- the next bounded move is `Phase 3R-F` Read together with: diff --git a/docs/v6_5_deep_manual_pack/HyperTwist/ROADMAP.md b/docs/v6_5_deep_manual_pack/HyperTwist/ROADMAP.md index 630f201..96239bc 100644 --- a/docs/v6_5_deep_manual_pack/HyperTwist/ROADMAP.md +++ b/docs/v6_5_deep_manual_pack/HyperTwist/ROADMAP.md @@ -5,8 +5,8 @@ Before widening new HyperTwist donor-driven implementation beyond the already landed lanes, preserve this current truth: - current shallow-eval set: `71` repos -- currently verified live/implemented in checked Unreal surfaces: `10` -- permissive live lanes: `9` +- currently verified live/implemented in checked Unreal surfaces: `11` +- permissive live lanes: `10` - 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 - `Phase 0R` is now closed for the remaining `61` non-live rows @@ -16,15 +16,16 @@ Before widening new HyperTwist donor-driven implementation beyond the already la - `Phase 3R-B` is now closed as the landed `Hypercubers/hypercubing.xyz` knowledge and community-reference widening packet - `Phase 3R-C` is now closed as the landed `apache/echarts` analytics and reporting widening packet - `Phase 3R-D` is now closed as the landed `google/model-viewer` browser presentation, compact editor, and standards-aware asset-QA widening packet +- `Phase 3R-E` is now closed as the landed `met4citizen/TalkingHead` embodied companion, narration, lip-sync, gesture, subtitle, and avatar-embed widening packet Current routing truth: - retained rows total: `68` - discarded from the active retained set: `3` -- active non-live implementation-board rows: `49` +- active non-live implementation-board rows: `48` - retained benchmark, oracle, or clean-room-later rows outside the active implementation board: `9` -The next bounded move is `Phase 3R-E`, not renewed donor evaluation or pre-packet ratification. +The next bounded move is `Phase 3R-F`, not renewed donor evaluation or pre-packet ratification. ## Reset phases