packet_id,title,scope,top_repos_in_packet,primary_goal_for_coding_model,what_to_extract_first,decision_questions,required_outputs,grading_rubric,paste_ready_instruction,packet_scope_type,project_context,source_of_truth,repo,repo_key,scriptorium_bucket,source_audit_priority,current_reality_status,packet_prompt,must_inspect,integration_path,repurpose_path,merger_partner_1,merger_partner_2,merger_partner_3,success_condition,warning,_repo_norm,v6_source_of_truth,copyleft_strategy_layer_v6_1,copyleft_packet_note_v6_1,v6_3_source_of_truth
FU_misc,FU_misc,Miscellaneous cluster requiring source audit.,aws/eks-hybrid | kubernetes/kube-state-metrics | Azure/azure-sdk-for-net | GoogleCloudPlatform/cloud-profiler-python | grafana/beyla | Kong/insomnia | aws/aws-sdk-go-v2 | docker/cli | Azure/bicep | GoogleCloudPlatform/buildpacks | kubernetes/client-go | LaurieWired/tailslayer-bench,"Identify the strongest extractable engine(s), donor modules, hidden subsystems, and merger path(s) inside the FU_misc cluster.",Inspect parsers and language adapters; graph schema and storage; incremental indexing/update logic; layout engine; query API; export/import formats; test fixtures for graph correctness.; Inspect parsers and language adapters; graph schema and storage; incremental indexing/update logic; layout engine; query API; export/import formats; test fixtures for graph correctness.; Inspect topology/service schema; collectors/agents; auth/integration adapters; caching/state sync; deployment/runtime abstractions; metrics/event correlation; config layering.,Which repo actually owns the deepest engine? Which should remain shell-only? Which hidden modules are reusable even if the surface app is not?,module map; hidden feature list; reusable schemas; protocol/adapters; merge recommendation; estimated extraction boundary; tests/examples worth preserving,"Prefer concrete internal engines, schemas, adapters, and extension hooks over README claims or surface UI appeal.","Audit cluster FU_misc. Candidate repos: aws/eks-hybrid | kubernetes/kube-state-metrics | Azure/azure-sdk-for-net | GoogleCloudPlatform/cloud-profiler-python | grafana/beyla | Kong/insomnia | aws/aws-sdk-go-v2 | docker/cli | Azure/bicep | GoogleCloudPlatform/buildpacks | kubernetes/client-go | LaurieWired/tailslayer-bench. Identify base-vs-donor roles, hidden internal modules, schemas, adapter layers, plugin hooks, and the best clean-room reimplementation path.",Global cluster packet,Multi-project / global,Original global VS Code packets v3 retained,,,,,,,,,,,,,,,,v6_unified_source_of_truth_pack,"Before recommending direct code use, inspect the target repo row in the v6.1 operational/phase/source-audit boards. Respect copyleft_strategy_v6_1, preferred_boundary_model_v6_1, and open_compliance_if_used_as_is_v6_1. Do not assume reverse engineering is mandatory or that as-is use is always sensible.","If the repo-level strategy says bounded_sidecar_preferred or boundary_first_then_decide_as_is_vs_reimplementation, audit clean interfaces, protocol seams, subprocess/container boundaries, and what would be required to reimplement only the strategically necessary portions.",v6.3_final_source_of_truth
HT_cube_vision,HyperTwist Physical Cube Vision,"Extract camera calibration, cube-state reconstruction, replay, and AR handoff.",kkoomen/qbr | vivaansinghvi07/rubix-cube-solver | cahidenes/rubiks-cube-solver | tentone/rubix-solver | aMonteSl/Code-XR | brianpeiris/RiftSketch | NuiLab/code-vr | yakupbilen/drl-rubiks-cube | PostHog/posthog,"Identify the strongest extractable engine(s), donor modules, hidden subsystems, and merger path(s) inside the HT_cube_vision cluster.",Inspect preprocessing/calibration; tracking stabilization; state reconstruction; replay/event model; camera abstraction; fallback heuristics; testing assets/videos; performance shortcuts.; Inspect preprocessing/calibration; tracking stabilization; state reconstruction; replay/event model; camera abstraction; fallback heuristics; testing assets/videos; performance shortcuts.; Inspect preprocessing/calibration; tracking stabilization; state reconstruction; replay/event model; camera abstraction; fallback heuristics; testing assets/videos; performance shortcuts.,Which repo actually owns the deepest engine? Which should remain shell-only? Which hidden modules are reusable even if the surface app is not?,module map; hidden feature list; reusable schemas; protocol/adapters; merge recommendation; estimated extraction boundary; tests/examples worth preserving,"Prefer concrete internal engines, schemas, adapters, and extension hooks over README claims or surface UI appeal.","Audit cluster HT_cube_vision. Candidate repos: kkoomen/qbr | vivaansinghvi07/rubix-cube-solver | cahidenes/rubiks-cube-solver | tentone/rubix-solver | aMonteSl/Code-XR | brianpeiris/RiftSketch | NuiLab/code-vr | yakupbilen/drl-rubiks-cube | PostHog/posthog. Identify base-vs-donor roles, hidden internal modules, schemas, adapter layers, plugin hooks, and the best clean-room reimplementation path.",Global cluster packet,Multi-project / global,Original global VS Code packets v3 retained,,,,,,,,,,,,,,,,v6_unified_source_of_truth_pack,"Before recommending direct code use, inspect the target repo row in the v6.1 operational/phase/source-audit boards. Respect copyleft_strategy_v6_1, preferred_boundary_model_v6_1, and open_compliance_if_used_as_is_v6_1. Do not assume reverse engineering is mandatory or that as-is use is always sensible.","If the repo-level strategy says bounded_sidecar_preferred or boundary_first_then_decide_as_is_vs_reimplementation, audit clean interfaces, protocol seams, subprocess/container boundaries, and what would be required to reimplement only the strategically necessary portions.",v6.3_final_source_of_truth
HT_hyper_engine,HyperTwist Hypercubing Engine,Extract generalized puzzle/state/render abstractions for 3D–nD puzzles.,HactarCE/Hyperspeedcube | kash/cubedesk | cutelyaware/magiccube4d | roice3/Magic120Cell | roice3/MagicCube5D | Hypercubers/hypercubing.xyz,"Identify the strongest extractable engine(s), donor modules, hidden subsystems, and merger path(s) inside the HT_hyper_engine cluster.",Inspect generalized puzzle/state model; notation parser; transform math; rendering abstraction; save/load format; puzzle generator; input mapping; performance optimizations.; Inspect generalized puzzle/state model; notation parser; transform math; rendering abstraction; save/load format; puzzle generator; input mapping; performance optimizations.; Inspect generalized puzzle/state model; notation parser; transform math; rendering abstraction; save/load format; puzzle generator; input mapping; performance optimizations.,Which repo actually owns the deepest engine? Which should remain shell-only? Which hidden modules are reusable even if the surface app is not?,module map; hidden feature list; reusable schemas; protocol/adapters; merge recommendation; estimated extraction boundary; tests/examples worth preserving,"Prefer concrete internal engines, schemas, adapters, and extension hooks over README claims or surface UI appeal.","Audit cluster HT_hyper_engine. Candidate repos: HactarCE/Hyperspeedcube | kash/cubedesk | cutelyaware/magiccube4d | roice3/Magic120Cell | roice3/MagicCube5D | Hypercubers/hypercubing.xyz. Identify base-vs-donor roles, hidden internal modules, schemas, adapter layers, plugin hooks, and the best clean-room reimplementation path.",Global cluster packet,Multi-project / global,Original global VS Code packets v3 retained,,,,,,,,,,,,,,,,v6_unified_source_of_truth_pack,"Before recommending direct code use, inspect the target repo row in the v6.1 operational/phase/source-audit boards. Respect copyleft_strategy_v6_1, preferred_boundary_model_v6_1, and open_compliance_if_used_as_is_v6_1. Do not assume reverse engineering is mandatory or that as-is use is always sensible.","If the repo-level strategy says bounded_sidecar_preferred or boundary_first_then_decide_as_is_vs_reimplementation, audit clean interfaces, protocol seams, subprocess/container boundaries, and what would be required to reimplement only the strategically necessary portions.",v6.3_final_source_of_truth
HT_training_stack,HyperTwist Training Stack,"Extract trainer scheduling, timer/replay, case databases, and pedagogy UX.",tao-yu/Alg-Trainer | Lykos/cube_trainer | cs0x7f/cstimer | MathewKJ2048/Rubiks-cube-simulator | ShellPuppy/RCube | abunickabhi/5style-Trainer | brownan/Rubiks-Cube-Solver | newyork-anthonyng/rubiks-cross-trainer | vwcwong/CubeSim | AviKaufman/Rubix-cube-trainer | alinen/cube | ambisinister/blindsolve,"Identify the strongest extractable engine(s), donor modules, hidden subsystems, and merger path(s) inside the HT_training_stack cluster.",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 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 cube-state model; scramble generator; trainer weighting/scheduling; case database and metadata; replay/timer model; import/export of alg sets; smartcube or sensor adapters.,Which repo actually owns the deepest engine? Which should remain shell-only? Which hidden modules are reusable even if the surface app is not?,module map; hidden feature list; reusable schemas; protocol/adapters; merge recommendation; estimated extraction boundary; tests/examples worth preserving,"Prefer concrete internal engines, schemas, adapters, and extension hooks over README claims or surface UI appeal.","Audit cluster HT_training_stack. Candidate repos: tao-yu/Alg-Trainer | Lykos/cube_trainer | cs0x7f/cstimer | MathewKJ2048/Rubiks-cube-simulator | ShellPuppy/RCube | abunickabhi/5style-Trainer | brownan/Rubiks-Cube-Solver | newyork-anthonyng/rubiks-cross-trainer | vwcwong/CubeSim | AviKaufman/Rubix-cube-trainer | alinen/cube | ambisinister/blindsolve. Identify base-vs-donor roles, hidden internal modules, schemas, adapter layers, plugin hooks, and the best clean-room reimplementation path.",Global cluster packet,Multi-project / global,Original global VS Code packets v3 retained,,,,,,,,,,,,,,,,v6_unified_source_of_truth_pack,"Before recommending direct code use, inspect the target repo row in the v6.1 operational/phase/source-audit boards. Respect copyleft_strategy_v6_1, preferred_boundary_model_v6_1, and open_compliance_if_used_as_is_v6_1. Do not assume reverse engineering is mandatory or that as-is use is always sensible.","If the repo-level strategy says bounded_sidecar_preferred or boundary_first_then_decide_as_is_vs_reimplementation, audit clean interfaces, protocol seams, subprocess/container boundaries, and what would be required to reimplement only the strategically necessary portions.",v6.3_final_source_of_truth
HY_misc,HY_misc,Miscellaneous cluster requiring source audit.,cubing/cubing.js | poliva/cubedex | molgenis/Graph2VR | nealmick/Cube | kubernetes/ingress-nginx | grafana/alloy | roice3/MagicTile | Kong/kubernetes-ingress-controller | usestrix/strix | Eronred/aso-skills | HKUDS/DeepTutor | pocket-id/pocket-id,"Identify the strongest extractable engine(s), donor modules, hidden subsystems, and merger path(s) inside the HY_misc cluster.",Inspect scene graph/canvas data model; layout primitives; component library; keyboard/gesture interactions; import/export schema; theming; plugin or extension hooks.; Inspect scene graph/canvas data model; layout primitives; component library; keyboard/gesture interactions; import/export schema; theming; plugin or extension hooks.; Inspect parsers and language adapters; graph schema and storage; incremental indexing/update logic; layout engine; query API; export/import formats; test fixtures for graph correctness.,Which repo actually owns the deepest engine? Which should remain shell-only? Which hidden modules are reusable even if the surface app is not?,module map; hidden feature list; reusable schemas; protocol/adapters; merge recommendation; estimated extraction boundary; tests/examples worth preserving,"Prefer concrete internal engines, schemas, adapters, and extension hooks over README claims or surface UI appeal.","Audit cluster HY_misc. Candidate repos: cubing/cubing.js | poliva/cubedex | molgenis/Graph2VR | nealmick/Cube | kubernetes/ingress-nginx | grafana/alloy | roice3/MagicTile | Kong/kubernetes-ingress-controller | usestrix/strix | Eronred/aso-skills | HKUDS/DeepTutor | pocket-id/pocket-id. Identify base-vs-donor roles, hidden internal modules, schemas, adapter layers, plugin hooks, and the best clean-room reimplementation path.",Global cluster packet,Multi-project / global,Original global VS Code packets v3 retained,,,,,,,,,,,,,,,,v6_unified_source_of_truth_pack,"Before recommending direct code use, inspect the target repo row in the v6.1 operational/phase/source-audit boards. Respect copyleft_strategy_v6_1, preferred_boundary_model_v6_1, and open_compliance_if_used_as_is_v6_1. Do not assume reverse engineering is mandatory or that as-is use is always sensible.","If the repo-level strategy says bounded_sidecar_preferred or boundary_first_then_decide_as_is_vs_reimplementation, audit clean interfaces, protocol seams, subprocess/container boundaries, and what would be required to reimplement only the strategically necessary portions.",v6.3_final_source_of_truth
MU_misc,MU_misc,Miscellaneous cluster requiring source audit.,SYSTRAN/faster-whisper | coqui-ai/TTS | ggerganov/whisper.cpp | rhasspy/piper | yomazini/telegram-automation-bot-framework,"Identify the strongest extractable engine(s), donor modules, hidden subsystems, and merger path(s) inside the MU_misc cluster.",Inspect parsers and language adapters; graph schema and storage; incremental indexing/update logic; layout engine; query API; export/import formats; test fixtures for graph correctness.; Inspect streaming pipeline; VAD/segmentation; device abstraction; latency handling; multilingual or translation chain; local/offline fallback; API wrappers.; Inspect streaming pipeline; VAD/segmentation; device abstraction; latency handling; multilingual or translation chain; local/offline fallback; API wrappers.,Which repo actually owns the deepest engine? Which should remain shell-only? Which hidden modules are reusable even if the surface app is not?,module map; hidden feature list; reusable schemas; protocol/adapters; merge recommendation; estimated extraction boundary; tests/examples worth preserving,"Prefer concrete internal engines, schemas, adapters, and extension hooks over README claims or surface UI appeal.","Audit cluster MU_misc. Candidate repos: SYSTRAN/faster-whisper | coqui-ai/TTS | ggerganov/whisper.cpp | rhasspy/piper | yomazini/telegram-automation-bot-framework. Identify base-vs-donor roles, hidden internal modules, schemas, adapter layers, plugin hooks, and the best clean-room reimplementation path.",Global cluster packet,Multi-project / global,Original global VS Code packets v3 retained,,,,,,,,,,,,,,,,v6_unified_source_of_truth_pack,"Before recommending direct code use, inspect the target repo row in the v6.1 operational/phase/source-audit boards. Respect copyleft_strategy_v6_1, preferred_boundary_model_v6_1, and open_compliance_if_used_as_is_v6_1. Do not assume reverse engineering is mandatory or that as-is use is always sensible.","If the repo-level strategy says bounded_sidecar_preferred or boundary_first_then_decide_as_is_vs_reimplementation, audit clean interfaces, protocol seams, subprocess/container boundaries, and what would be required to reimplement only the strategically necessary portions.",v6.3_final_source_of_truth
SA_research_automation,ScriptoriumAI Research Automation,Extract agentic research/report-generation workflows and tool abstractions.,stanford-oval/storm | SakanaAI/AI-Scientist | hkuds/ai-researcher | sakanaai/ai-scientist | ResearAI/AutoFigure-Edit | excalidraw/excalidraw-mcp | calesthio/OpenMontage | CoplayDev/unity-mcp | 666ghj/BettaFish | CoderGamester/mcp-unity | Doriandarko/o1-engineer | EverMind-AI/EverMemOS,"Identify the strongest extractable engine(s), donor modules, hidden subsystems, and merger path(s) inside the SA_research_automation cluster.",Inspect planner/task graph; provider abstraction; tool registry or MCP bridges; memory/state schema; approvals/retries; telemetry/event bus; plugin or skill loading hooks.; Inspect planner/task graph; provider abstraction; tool registry or MCP bridges; memory/state schema; approvals/retries; telemetry/event bus; plugin or skill loading hooks.; Inspect planner/task graph; provider abstraction; tool registry or MCP bridges; memory/state schema; approvals/retries; telemetry/event bus; plugin or skill loading hooks.,Which repo actually owns the deepest engine? Which should remain shell-only? Which hidden modules are reusable even if the surface app is not?,module map; hidden feature list; reusable schemas; protocol/adapters; merge recommendation; estimated extraction boundary; tests/examples worth preserving,"Prefer concrete internal engines, schemas, adapters, and extension hooks over README claims or surface UI appeal.","Audit cluster SA_research_automation. Candidate repos: stanford-oval/storm | SakanaAI/AI-Scientist | hkuds/ai-researcher | sakanaai/ai-scientist | ResearAI/AutoFigure-Edit | excalidraw/excalidraw-mcp | calesthio/OpenMontage | CoplayDev/unity-mcp | 666ghj/BettaFish | CoderGamester/mcp-unity | Doriandarko/o1-engineer | EverMind-AI/EverMemOS. Identify base-vs-donor roles, hidden internal modules, schemas, adapter layers, plugin hooks, and the best clean-room reimplementation path.",Global cluster packet,Multi-project / global,Original global VS Code packets v3 retained,,,,,,,,,,,,,,,,v6_unified_source_of_truth_pack,"Before recommending direct code use, inspect the target repo row in the v6.1 operational/phase/source-audit boards. Respect copyleft_strategy_v6_1, preferred_boundary_model_v6_1, and open_compliance_if_used_as_is_v6_1. Do not assume reverse engineering is mandatory or that as-is use is always sensible.","If the repo-level strategy says bounded_sidecar_preferred or boundary_first_then_decide_as_is_vs_reimplementation, audit clean interfaces, protocol seams, subprocess/container boundaries, and what would be required to reimplement only the strategically necessary portions.",v6.3_final_source_of_truth
SA_visual_ideation,ScriptoriumAI Visual Ideation,Extract whiteboard/canvas models and automation bridges.,jsuarezruiz/awesome-dotnet-maui | Anduin2017/HowToCook | AvaloniaCommunity/Material.Avalonia | AvaloniaUI/Avalonia.Labs | AvaloniaUI/AvaloniaMauiHybrid | ByteByteGoHq/system-design-101 | CoderFoundry/BlazorRenderModes | FareedKhan-dev/complex-RAG-guide | Paidax01/math-curve-loaders | TimeWarpEngineering/timewarp-state | Unity-Technologies/EntityComponentSystemSamples | VulcanWM/saasheaven,"Identify the strongest extractable engine(s), donor modules, hidden subsystems, and merger path(s) inside the SA_visual_ideation cluster.",Inspect scene graph/canvas data model; layout primitives; component library; keyboard/gesture interactions; import/export schema; theming; plugin or extension hooks.; Inspect scene graph/canvas data model; layout primitives; component library; keyboard/gesture interactions; import/export schema; theming; plugin or extension hooks.; Inspect scene graph/canvas data model; layout primitives; component library; keyboard/gesture interactions; import/export schema; theming; plugin or extension hooks.,Which repo actually owns the deepest engine? Which should remain shell-only? Which hidden modules are reusable even if the surface app is not?,module map; hidden feature list; reusable schemas; protocol/adapters; merge recommendation; estimated extraction boundary; tests/examples worth preserving,"Prefer concrete internal engines, schemas, adapters, and extension hooks over README claims or surface UI appeal.","Audit cluster SA_visual_ideation. Candidate repos: jsuarezruiz/awesome-dotnet-maui | Anduin2017/HowToCook | AvaloniaCommunity/Material.Avalonia | AvaloniaUI/Avalonia.Labs | AvaloniaUI/AvaloniaMauiHybrid | ByteByteGoHq/system-design-101 | CoderFoundry/BlazorRenderModes | FareedKhan-dev/complex-RAG-guide | Paidax01/math-curve-loaders | TimeWarpEngineering/timewarp-state | Unity-Technologies/EntityComponentSystemSamples | VulcanWM/saasheaven. Identify base-vs-donor roles, hidden internal modules, schemas, adapter layers, plugin hooks, and the best clean-room reimplementation path.",Global cluster packet,Multi-project / global,Original global VS Code packets v3 retained,,,,,,,,,,,,,,,,v6_unified_source_of_truth_pack,"Before recommending direct code use, inspect the target repo row in the v6.1 operational/phase/source-audit boards. Respect copyleft_strategy_v6_1, preferred_boundary_model_v6_1, and open_compliance_if_used_as_is_v6_1. Do not assume reverse engineering is mandatory or that as-is use is always sensible.","If the repo-level strategy says bounded_sidecar_preferred or boundary_first_then_decide_as_is_vs_reimplementation, audit clean interfaces, protocol seams, subprocess/container boundaries, and what would be required to reimplement only the strategically necessary portions.",v6.3_final_source_of_truth
SA_workspace_research,ScriptoriumAI Workspace / Research,"Extract document schema, citation/report pipeline, workspace logic, and export adapters.",excalidraw/excalidraw | Prismer-AI/Prismer | AMDResearch/DRAM-Refresh-Research | 1jehuang/mermaid-rs-renderer | DangJin/pdf2video | HKUDS/Paper2Slides | JetBrains/resharper-fsharp | PDFCraftTool/pdfcraft | RuizeLyu/paper-dl | TapXWorld/ChinaTextbook | YuhangChen1/Paper2All | dotnet/templating,"Identify the strongest extractable engine(s), donor modules, hidden subsystems, and merger path(s) inside the SA_workspace_research cluster.",Inspect document/block schema; sync/persistence model; permissions and sharing; citation/external-source pipeline; import/export adapters; plugin/extension points; editor rendering model.; Inspect document/block schema; sync/persistence model; permissions and sharing; citation/external-source pipeline; import/export adapters; plugin/extension points; editor rendering model.; Inspect document/block schema; sync/persistence model; permissions and sharing; citation/external-source pipeline; import/export adapters; plugin/extension points; editor rendering model.,Which repo actually owns the deepest engine? Which should remain shell-only? Which hidden modules are reusable even if the surface app is not?,module map; hidden feature list; reusable schemas; protocol/adapters; merge recommendation; estimated extraction boundary; tests/examples worth preserving,"Prefer concrete internal engines, schemas, adapters, and extension hooks over README claims or surface UI appeal.","Audit cluster SA_workspace_research. Candidate repos: excalidraw/excalidraw | Prismer-AI/Prismer | AMDResearch/DRAM-Refresh-Research | 1jehuang/mermaid-rs-renderer | DangJin/pdf2video | HKUDS/Paper2Slides | JetBrains/resharper-fsharp | PDFCraftTool/pdfcraft | RuizeLyu/paper-dl | TapXWorld/ChinaTextbook | YuhangChen1/Paper2All | dotnet/templating. Identify base-vs-donor roles, hidden internal modules, schemas, adapter layers, plugin hooks, and the best clean-room reimplementation path.",Global cluster packet,Multi-project / global,Original global VS Code packets v3 retained,,,,,,,,,,,,,,,,v6_unified_source_of_truth_pack,"Before recommending direct code use, inspect the target repo row in the v6.1 operational/phase/source-audit boards. Respect copyleft_strategy_v6_1, preferred_boundary_model_v6_1, and open_compliance_if_used_as_is_v6_1. Do not assume reverse engineering is mandatory or that as-is use is always sensible.","If the repo-level strategy says bounded_sidecar_preferred or boundary_first_then_decide_as_is_vs_reimplementation, audit clean interfaces, protocol seams, subprocess/container boundaries, and what would be required to reimplement only the strategically necessary portions.",v6.3_final_source_of_truth
SC_misc,SC_misc,Miscellaneous cluster requiring source audit.,outline/outline | RocketChat/Rocket.Chat | 0x77dev/pdf-sign | AUTOMATIC1111/stable-diffusion-webui | AvaloniaUI/Avalonia | 0xsline/StoryGen-Atelier | AvaloniaUI/Avalonia.Xaml.Behaviors | Blaizzy/mlx-audio | D4Vinci/Scrapling | DrewThomasson/ebook2audiobook | JarodMica/audiobook_maker | JimmyLv/awesome-nano-banana,"Identify the strongest extractable engine(s), donor modules, hidden subsystems, and merger path(s) inside the SC_misc cluster.",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 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 generalized puzzle/state model; notation parser; transform math; rendering abstraction; save/load format; puzzle generator; input mapping; performance optimizations.,Which repo actually owns the deepest engine? Which should remain shell-only? Which hidden modules are reusable even if the surface app is not?,module map; hidden feature list; reusable schemas; protocol/adapters; merge recommendation; estimated extraction boundary; tests/examples worth preserving,"Prefer concrete internal engines, schemas, adapters, and extension hooks over README claims or surface UI appeal.","Audit cluster SC_misc. Candidate repos: outline/outline | RocketChat/Rocket.Chat | 0x77dev/pdf-sign | AUTOMATIC1111/stable-diffusion-webui | AvaloniaUI/Avalonia | 0xsline/StoryGen-Atelier | AvaloniaUI/Avalonia.Xaml.Behaviors | Blaizzy/mlx-audio | D4Vinci/Scrapling | DrewThomasson/ebook2audiobook | JarodMica/audiobook_maker | JimmyLv/awesome-nano-banana. Identify base-vs-donor roles, hidden internal modules, schemas, adapter layers, plugin hooks, and the best clean-room reimplementation path.",Global cluster packet,Multi-project / global,Original global VS Code packets v3 retained,,,,,,,,,,,,,,,,v6_unified_source_of_truth_pack,"Before recommending direct code use, inspect the target repo row in the v6.1 operational/phase/source-audit boards. Respect copyleft_strategy_v6_1, preferred_boundary_model_v6_1, and open_compliance_if_used_as_is_v6_1. Do not assume reverse engineering is mandatory or that as-is use is always sensible.","If the repo-level strategy says bounded_sidecar_preferred or boundary_first_then_decide_as_is_vs_reimplementation, audit clean interfaces, protocol seams, subprocess/container boundaries, and what would be required to reimplement only the strategically necessary portions.",v6.3_final_source_of_truth
VE_misc,VE_misc,Miscellaneous cluster requiring source audit.,sentrux/sentrux | anomalyco/opencode | BloodHoundAD/BloodHound | vasturiano/3d-force-graph | virtualgenius/codecohesion | docker/compose | Taskosaur/Taskosaur | archlinter/archlint | docker/scout-cli | raphaelmansuy/edgequake | dabit3/agent-replay | onyx-dot-app/onyx,"Identify the strongest extractable engine(s), donor modules, hidden subsystems, and merger path(s) inside the VE_misc cluster.",Inspect generalized puzzle/state model; notation parser; transform math; rendering abstraction; save/load format; puzzle generator; input mapping; performance optimizations.; Inspect generalized puzzle/state model; notation parser; transform math; rendering abstraction; save/load format; puzzle generator; input mapping; performance optimizations.; Inspect generalized puzzle/state model; notation parser; transform math; rendering abstraction; save/load format; puzzle generator; input mapping; performance optimizations.,Which repo actually owns the deepest engine? Which should remain shell-only? Which hidden modules are reusable even if the surface app is not?,module map; hidden feature list; reusable schemas; protocol/adapters; merge recommendation; estimated extraction boundary; tests/examples worth preserving,"Prefer concrete internal engines, schemas, adapters, and extension hooks over README claims or surface UI appeal.","Audit cluster VE_misc. Candidate repos: sentrux/sentrux | anomalyco/opencode | BloodHoundAD/BloodHound | vasturiano/3d-force-graph | virtualgenius/codecohesion | docker/compose | Taskosaur/Taskosaur | archlinter/archlint | docker/scout-cli | raphaelmansuy/edgequake | dabit3/agent-replay | onyx-dot-app/onyx. Identify base-vs-donor roles, hidden internal modules, schemas, adapter layers, plugin hooks, and the best clean-room reimplementation path.",Global cluster packet,Multi-project / global,Original global VS Code packets v3 retained,,,,,,,,,,,,,,,,v6_unified_source_of_truth_pack,"Before recommending direct code use, inspect the target repo row in the v6.1 operational/phase/source-audit boards. Respect copyleft_strategy_v6_1, preferred_boundary_model_v6_1, and open_compliance_if_used_as_is_v6_1. Do not assume reverse engineering is mandatory or that as-is use is always sensible.","If the repo-level strategy says bounded_sidecar_preferred or boundary_first_then_decide_as_is_vs_reimplementation, audit clean interfaces, protocol seams, subprocess/container boundaries, and what would be required to reimplement only the strategically necessary portions.",v6.3_final_source_of_truth
VS_agent_runtime,VectorShell Agent Runtime,"Extract planner, task graph, MCP/tool adapters, and coding-agent flows.",abhigyanpatwari/GitNexus | langchain-ai/open-swe | plandex-ai/plandex | AgnetLabs/Laddr | ArcadeAI/blueprint-mcp | harshkedia177/axon | ruvnet/ruflo | wangziqi06/724-office | yoanbernabeu/grepai | aMonteSl/CodeXR | 403errors/repomind | Cranot/roam-code,"Identify the strongest extractable engine(s), donor modules, hidden subsystems, and merger path(s) inside the VS_agent_runtime cluster.",Inspect planner/task graph; provider abstraction; tool registry or MCP bridges; memory/state schema; approvals/retries; telemetry/event bus; plugin or skill loading hooks.; Inspect planner/task graph; provider abstraction; tool registry or MCP bridges; memory/state schema; approvals/retries; telemetry/event bus; plugin or skill loading hooks.; Inspect planner/task graph; provider abstraction; tool registry or MCP bridges; memory/state schema; approvals/retries; telemetry/event bus; plugin or skill loading hooks.,Which repo actually owns the deepest engine? Which should remain shell-only? Which hidden modules are reusable even if the surface app is not?,module map; hidden feature list; reusable schemas; protocol/adapters; merge recommendation; estimated extraction boundary; tests/examples worth preserving,"Prefer concrete internal engines, schemas, adapters, and extension hooks over README claims or surface UI appeal.","Audit cluster VS_agent_runtime. Candidate repos: abhigyanpatwari/GitNexus | langchain-ai/open-swe | plandex-ai/plandex | AgnetLabs/Laddr | ArcadeAI/blueprint-mcp | harshkedia177/axon | ruvnet/ruflo | wangziqi06/724-office | yoanbernabeu/grepai | aMonteSl/CodeXR | 403errors/repomind | Cranot/roam-code. Identify base-vs-donor roles, hidden internal modules, schemas, adapter layers, plugin hooks, and the best clean-room reimplementation path.",Global cluster packet,Multi-project / global,Original global VS Code packets v3 retained,,,,,,,,,,,,,,,,v6_unified_source_of_truth_pack,"Before recommending direct code use, inspect the target repo row in the v6.1 operational/phase/source-audit boards. Respect copyleft_strategy_v6_1, preferred_boundary_model_v6_1, and open_compliance_if_used_as_is_v6_1. Do not assume reverse engineering is mandatory or that as-is use is always sensible.","If the repo-level strategy says bounded_sidecar_preferred or boundary_first_then_decide_as_is_vs_reimplementation, audit clean interfaces, protocol seams, subprocess/container boundaries, and what would be required to reimplement only the strategically necessary portions.",v6.3_final_source_of_truth
VS_graph_core,VectorShell Graph / Architecture Core,Build the structural substrate for code-space navigation and explanation.,ffuf/ffuf | projectdiscovery/nuclei | xalgord/xalgorix | wxtsky/CodeIsland | danish296/codevibes | DucPhamNgoc08/CodeVisualizer | ardalis/CleanArchitecture | brunoclz/br-acc | chaosprint/hindsight | coderamp-labs/gitingest | potpie-ai/potpie | productdevbook/ceviz,"Identify the strongest extractable engine(s), donor modules, hidden subsystems, and merger path(s) inside the VS_graph_core cluster.",Inspect parsers and language adapters; graph schema and storage; incremental indexing/update logic; layout engine; query API; export/import formats; test fixtures for graph correctness.; Inspect parsers and language adapters; graph schema and storage; incremental indexing/update logic; layout engine; query API; export/import formats; test fixtures for graph correctness.; Inspect parsers and language adapters; graph schema and storage; incremental indexing/update logic; layout engine; query API; export/import formats; test fixtures for graph correctness.,Which repo actually owns the deepest engine? Which should remain shell-only? Which hidden modules are reusable even if the surface app is not?,module map; hidden feature list; reusable schemas; protocol/adapters; merge recommendation; estimated extraction boundary; tests/examples worth preserving,"Prefer concrete internal engines, schemas, adapters, and extension hooks over README claims or surface UI appeal.","Audit cluster VS_graph_core. Candidate repos: ffuf/ffuf | projectdiscovery/nuclei | xalgord/xalgorix | wxtsky/CodeIsland | danish296/codevibes | DucPhamNgoc08/CodeVisualizer | ardalis/CleanArchitecture | brunoclz/br-acc | chaosprint/hindsight | coderamp-labs/gitingest | potpie-ai/potpie | productdevbook/ceviz. Identify base-vs-donor roles, hidden internal modules, schemas, adapter layers, plugin hooks, and the best clean-room reimplementation path.",Global cluster packet,Multi-project / global,Original global VS Code packets v3 retained,,,,,,,,,,,,,,,,v6_unified_source_of_truth_pack,"Before recommending direct code use, inspect the target repo row in the v6.1 operational/phase/source-audit boards. Respect copyleft_strategy_v6_1, preferred_boundary_model_v6_1, and open_compliance_if_used_as_is_v6_1. Do not assume reverse engineering is mandatory or that as-is use is always sensible.","If the repo-level strategy says bounded_sidecar_preferred or boundary_first_then_decide_as_is_vs_reimplementation, audit clean interfaces, protocol seams, subprocess/container boundaries, and what would be required to reimplement only the strategically necessary portions.",v6.3_final_source_of_truth
VS_multimodal_io,VectorShell Multimodal I/O,Extract voice/audio/local-assistant pipelines and command surfaces.,HumeAI/tada | HunxByts/GhostTrack | KittenML/KittenTTS | LarsenCundric/port-whisperer | QwenLM/Qwen3-TTS | TelegramMessenger/cocoon | TheStageAI/TheWhisper | Vanyoo/realtime-subtitle | XiaomiMiMo/MiMo | amywork777/CuteGhostty | antirez/voxtral.c | chrisgreg/fyi,"Identify the strongest extractable engine(s), donor modules, hidden subsystems, and merger path(s) inside the VS_multimodal_io cluster.",Inspect streaming pipeline; VAD/segmentation; device abstraction; latency handling; multilingual or translation chain; local/offline fallback; API wrappers.; Inspect streaming pipeline; VAD/segmentation; device abstraction; latency handling; multilingual or translation chain; local/offline fallback; API wrappers.; Inspect streaming pipeline; VAD/segmentation; device abstraction; latency handling; multilingual or translation chain; local/offline fallback; API wrappers.,Which repo actually owns the deepest engine? Which should remain shell-only? Which hidden modules are reusable even if the surface app is not?,module map; hidden feature list; reusable schemas; protocol/adapters; merge recommendation; estimated extraction boundary; tests/examples worth preserving,"Prefer concrete internal engines, schemas, adapters, and extension hooks over README claims or surface UI appeal.","Audit cluster VS_multimodal_io. Candidate repos: HumeAI/tada | HunxByts/GhostTrack | KittenML/KittenTTS | LarsenCundric/port-whisperer | QwenLM/Qwen3-TTS | TelegramMessenger/cocoon | TheStageAI/TheWhisper | Vanyoo/realtime-subtitle | XiaomiMiMo/MiMo | amywork777/CuteGhostty | antirez/voxtral.c | chrisgreg/fyi. Identify base-vs-donor roles, hidden internal modules, schemas, adapter layers, plugin hooks, and the best clean-room reimplementation path.",Global cluster packet,Multi-project / global,Original global VS Code packets v3 retained,,,,,,,,,,,,,,,,v6_unified_source_of_truth_pack,"Before recommending direct code use, inspect the target repo row in the v6.1 operational/phase/source-audit boards. Respect copyleft_strategy_v6_1, preferred_boundary_model_v6_1, and open_compliance_if_used_as_is_v6_1. Do not assume reverse engineering is mandatory or that as-is use is always sensible.","If the repo-level strategy says bounded_sidecar_preferred or boundary_first_then_decide_as_is_vs_reimplementation, audit clean interfaces, protocol seams, subprocess/container boundaries, and what would be required to reimplement only the strategically necessary portions.",v6.3_final_source_of_truth
VS_runtime_observability,VectorShell Runtime / Observability,"Extract collectors, topology schemas, service runtime adapters, and metrics surfaces.",AlpinDale/ssh-dashboard | AmanVarshney01/create-better-t-stack | AnswerDotAI/clipmd | BansheeTech/HomeDockOS | ClickHouse/ClickHouse | EvolutionAPI/evolution-api | Finsys/dockhand | Godzilla675/clip-js-copilot | GoogleCloudPlatform/kubectl-ai | Handfish/talos-pilot | IndAlok/rzweb | IronsideXXVI/Hacker-News,"Identify the strongest extractable engine(s), donor modules, hidden subsystems, and merger path(s) inside the VS_runtime_observability cluster.",Inspect topology/service schema; collectors/agents; auth/integration adapters; caching/state sync; deployment/runtime abstractions; metrics/event correlation; config layering.; Inspect topology/service schema; collectors/agents; auth/integration adapters; caching/state sync; deployment/runtime abstractions; metrics/event correlation; config layering.; Inspect topology/service schema; collectors/agents; auth/integration adapters; caching/state sync; deployment/runtime abstractions; metrics/event correlation; config layering.,Which repo actually owns the deepest engine? Which should remain shell-only? Which hidden modules are reusable even if the surface app is not?,module map; hidden feature list; reusable schemas; protocol/adapters; merge recommendation; estimated extraction boundary; tests/examples worth preserving,"Prefer concrete internal engines, schemas, adapters, and extension hooks over README claims or surface UI appeal.","Audit cluster VS_runtime_observability. Candidate repos: AlpinDale/ssh-dashboard | AmanVarshney01/create-better-t-stack | AnswerDotAI/clipmd | BansheeTech/HomeDockOS | ClickHouse/ClickHouse | EvolutionAPI/evolution-api | Finsys/dockhand | Godzilla675/clip-js-copilot | GoogleCloudPlatform/kubectl-ai | Handfish/talos-pilot | IndAlok/rzweb | IronsideXXVI/Hacker-News. Identify base-vs-donor roles, hidden internal modules, schemas, adapter layers, plugin hooks, and the best clean-room reimplementation path.",Global cluster packet,Multi-project / global,Original global VS Code packets v3 retained,,,,,,,,,,,,,,,,v6_unified_source_of_truth_pack,"Before recommending direct code use, inspect the target repo row in the v6.1 operational/phase/source-audit boards. Respect copyleft_strategy_v6_1, preferred_boundary_model_v6_1, and open_compliance_if_used_as_is_v6_1. Do not assume reverse engineering is mandatory or that as-is use is always sensible.","If the repo-level strategy says bounded_sidecar_preferred or boundary_first_then_decide_as_is_vs_reimplementation, audit clean interfaces, protocol seams, subprocess/container boundaries, and what would be required to reimplement only the strategically necessary portions.",v6.3_final_source_of_truth
VS_security_overlay,VectorShell Security Overlay,Fuse scanner outputs and attack-surface logic into one overlay/evidence model.,owasp-amass/amass | projectdiscovery/httpx | semgrep/semgrep | zaproxy/zaproxy | urbanadventurer/WhatWeb | aws/s2n-tls | grafana/loki | LaurieWired/tailslayer | Adversis/tailsnitch | Arcanum-Sec/sec-context | BlessedRebuS/Krawl | ChiChou/grapefruit,"Identify the strongest extractable engine(s), donor modules, hidden subsystems, and merger path(s) inside the VS_security_overlay cluster.",Inspect scan engine; rule/template packs; protocol handlers; result schema normalization; auth/session handling; enrichment/correlation pipeline; evidence/report exporters; distributed runner support.; Inspect scan engine; rule/template packs; protocol handlers; result schema normalization; auth/session handling; enrichment/correlation pipeline; evidence/report exporters; distributed runner support.; Inspect scan engine; rule/template packs; protocol handlers; result schema normalization; auth/session handling; enrichment/correlation pipeline; evidence/report exporters; distributed runner support.,Which repo actually owns the deepest engine? Which should remain shell-only? Which hidden modules are reusable even if the surface app is not?,module map; hidden feature list; reusable schemas; protocol/adapters; merge recommendation; estimated extraction boundary; tests/examples worth preserving,"Prefer concrete internal engines, schemas, adapters, and extension hooks over README claims or surface UI appeal.","Audit cluster VS_security_overlay. Candidate repos: owasp-amass/amass | projectdiscovery/httpx | semgrep/semgrep | zaproxy/zaproxy | urbanadventurer/WhatWeb | aws/s2n-tls | grafana/loki | LaurieWired/tailslayer | Adversis/tailsnitch | Arcanum-Sec/sec-context | BlessedRebuS/Krawl | ChiChou/grapefruit. Identify base-vs-donor roles, hidden internal modules, schemas, adapter layers, plugin hooks, and the best clean-room reimplementation path.",Global cluster packet,Multi-project / global,Original global VS Code packets v3 retained,,,,,,,,,,,,,,,,v6_unified_source_of_truth_pack,"Before recommending direct code use, inspect the target repo row in the v6.1 operational/phase/source-audit boards. Respect copyleft_strategy_v6_1, preferred_boundary_model_v6_1, and open_compliance_if_used_as_is_v6_1. Do not assume reverse engineering is mandatory or that as-is use is always sensible.","If the repo-level strategy says bounded_sidecar_preferred or boundary_first_then_decide_as_is_vs_reimplementation, audit clean interfaces, protocol seams, subprocess/container boundaries, and what would be required to reimplement only the strategically necessary portions.",v6.3_final_source_of_truth
VS_spatial_interface,VectorShell Spatial Interface,Mine scene/layout/canvas/3D interaction primitives for the shell surface.,open-webui/open-terminal | 2bitprince/react_chakra_portfolio | AnmolSaini16/mapcn | Dennis960/BackApp | DodoApps/dodotidy | EmuLnk/emulnk | Gaurav-Gosain/tuios | InterceptSuite/ProxyBridge | Jason-uxui/project-dashboard | Kamyil/work-tuimer | Leantime/leantime | Livsy90/IntelligenceGlow,"Identify the strongest extractable engine(s), donor modules, hidden subsystems, and merger path(s) inside the VS_spatial_interface cluster.",Inspect scene graph/canvas data model; layout primitives; component library; keyboard/gesture interactions; import/export schema; theming; plugin or extension hooks.; Inspect scene graph/canvas data model; layout primitives; component library; keyboard/gesture interactions; import/export schema; theming; plugin or extension hooks.; Inspect scene graph/canvas data model; layout primitives; component library; keyboard/gesture interactions; import/export schema; theming; plugin or extension hooks.,Which repo actually owns the deepest engine? Which should remain shell-only? Which hidden modules are reusable even if the surface app is not?,module map; hidden feature list; reusable schemas; protocol/adapters; merge recommendation; estimated extraction boundary; tests/examples worth preserving,"Prefer concrete internal engines, schemas, adapters, and extension hooks over README claims or surface UI appeal.","Audit cluster VS_spatial_interface. Candidate repos: open-webui/open-terminal | 2bitprince/react_chakra_portfolio | AnmolSaini16/mapcn | Dennis960/BackApp | DodoApps/dodotidy | EmuLnk/emulnk | Gaurav-Gosain/tuios | InterceptSuite/ProxyBridge | Jason-uxui/project-dashboard | Kamyil/work-tuimer | Leantime/leantime | Livsy90/IntelligenceGlow. Identify base-vs-donor roles, hidden internal modules, schemas, adapter layers, plugin hooks, and the best clean-room reimplementation path.",Global cluster packet,Multi-project / global,Original global VS Code packets v3 retained,,,,,,,,,,,,,,,,v6_unified_source_of_truth_pack,"Before recommending direct code use, inspect the target repo row in the v6.1 operational/phase/source-audit boards. Respect copyleft_strategy_v6_1, preferred_boundary_model_v6_1, and open_compliance_if_used_as_is_v6_1. Do not assume reverse engineering is mandatory or that as-is use is always sensible.","If the repo-level strategy says bounded_sidecar_preferred or boundary_first_then_decide_as_is_vs_reimplementation, audit clean interfaces, protocol seams, subprocess/container boundaries, and what would be required to reimplement only the strategically necessary portions.",v6.3_final_source_of_truth
SCR_0001,,,,,,,,,,ScriptoriumAI repo packet,ScriptoriumAI,ScriptoriumAI re-anchored VS Code packets v1,native/LaTeX-OCR-Service,native/latex-ocr-service,Locked Native Foundation,P0,production integrated,"Audit native/LaTeX-OCR-Service for ScriptoriumAI. Start from the reanchored bucket 'Locked Native Foundation' and current reality status 'production integrated'. Confirm actual implemented capability, hidden reusable modules, extension seams, and whether it strengthens the existing OCR perimeter and image-to-LaTeX adapter lane. Focus on: Which internal boundaries are stable? Which adapters are already abstracted? Which local modules are overloaded and should be split?","Inspect internal service boundaries, adapters, route-level dependencies, state stores, auth guards, compile coordination, tests, and extension seams.",Treat this as a non-external native anchor. External repo decisions should now be made around this anchor rather than replacing it.,Native anchor; repurpose logic does not apply except by splitting submodules into reusable internal services.,,,,"Return concrete files/modules/adapters worth reusing and a verdict on whether the current reanchored bucket should be kept, upgraded, or downgraded.",Do not treat licensing as a filter. Do not propose replacing native foundations unless source evidence is overwhelming.,native/latex-ocr-service,v6_unified_source_of_truth_pack,"Before recommending direct code use, inspect the target repo row in the v6.1 operational/phase/source-audit boards. Respect copyleft_strategy_v6_1, preferred_boundary_model_v6_1, and open_compliance_if_used_as_is_v6_1. Do not assume reverse engineering is mandatory or that as-is use is always sensible.","If the repo-level strategy says bounded_sidecar_preferred or boundary_first_then_decide_as_is_vs_reimplementation, audit clean interfaces, protocol seams, subprocess/container boundaries, and what would be required to reimplement only the strategically necessary portions.",v6.3_final_source_of_truth
SCR_0002,,,,,,,,,,ScriptoriumAI repo packet,ScriptoriumAI,ScriptoriumAI re-anchored VS Code packets v1,native/ScriptoriumAI-Server,native/scriptoriumai-server,Locked Native Foundation,P0,production integrated,"Audit native/ScriptoriumAI-Server for ScriptoriumAI. Start from the reanchored bucket 'Locked Native Foundation' and current reality status 'production integrated'. Confirm actual implemented capability, hidden reusable modules, extension seams, and whether it strengthens the existing API, corpus orchestration, compile, collaboration, memory, service fan-out lane. Focus on: Which internal boundaries are stable? Which adapters are already abstracted? Which local modules are overloaded and should be split?","Inspect internal service boundaries, adapters, route-level dependencies, state stores, auth guards, compile coordination, tests, and extension seams.",Treat this as a non-external native anchor. External repo decisions should now be made around this anchor rather than replacing it.,Native anchor; repurpose logic does not apply except by splitting submodules into reusable internal services.,sharelatex/sharelatex,berriai/litellm,tkenaz/smriti,"Return concrete files/modules/adapters worth reusing and a verdict on whether the current reanchored bucket should be kept, upgraded, or downgraded.",Do not treat licensing as a filter. Do not propose replacing native foundations unless source evidence is overwhelming.,native/scriptoriumai-server,v6_unified_source_of_truth_pack,"Before recommending direct code use, inspect the target repo row in the v6.1 operational/phase/source-audit boards. Respect copyleft_strategy_v6_1, preferred_boundary_model_v6_1, and open_compliance_if_used_as_is_v6_1. Do not assume reverse engineering is mandatory or that as-is use is always sensible.","If the repo-level strategy says bounded_sidecar_preferred or boundary_first_then_decide_as_is_vs_reimplementation, audit clean interfaces, protocol seams, subprocess/container boundaries, and what would be required to reimplement only the strategically necessary portions.",v6.3_final_source_of_truth
SCR_0003,,,,,,,,,,ScriptoriumAI repo packet,ScriptoriumAI,ScriptoriumAI re-anchored VS Code packets v1,native/ScriptoriumAI-Visualizer,native/scriptoriumai-visualizer,Locked Native Foundation,P0,production integrated,"Audit native/ScriptoriumAI-Visualizer for ScriptoriumAI. Start from the reanchored bucket 'Locked Native Foundation' and current reality status 'production integrated'. Confirm actual implemented capability, hidden reusable modules, extension seams, and whether it strengthens the existing Python visualization and Manim render perimeter lane. Focus on: Which internal boundaries are stable? Which adapters are already abstracted? Which local modules are overloaded and should be split?","Inspect internal service boundaries, adapters, route-level dependencies, state stores, auth guards, compile coordination, tests, and extension seams.",Treat this as a non-external native anchor. External repo decisions should now be made around this anchor rather than replacing it.,Native anchor; repurpose logic does not apply except by splitting submodules into reusable internal services.,,,,"Return concrete files/modules/adapters worth reusing and a verdict on whether the current reanchored bucket should be kept, upgraded, or downgraded.",Do not treat licensing as a filter. Do not propose replacing native foundations unless source evidence is overwhelming.,native/scriptoriumai-visualizer,v6_unified_source_of_truth_pack,"Before recommending direct code use, inspect the target repo row in the v6.1 operational/phase/source-audit boards. Respect copyleft_strategy_v6_1, preferred_boundary_model_v6_1, and open_compliance_if_used_as_is_v6_1. Do not assume reverse engineering is mandatory or that as-is use is always sensible.","If the repo-level strategy says bounded_sidecar_preferred or boundary_first_then_decide_as_is_vs_reimplementation, audit clean interfaces, protocol seams, subprocess/container boundaries, and what would be required to reimplement only the strategically necessary portions.",v6.3_final_source_of_truth
SCR_0004,,,,,,,,,,ScriptoriumAI repo packet,ScriptoriumAI,ScriptoriumAI re-anchored VS Code packets v1,native/scriptoriumai-ui,native/scriptoriumai-ui,Locked Native Foundation,P0,production integrated,"Audit native/scriptoriumai-ui for ScriptoriumAI. Start from the reanchored bucket 'Locked Native Foundation' and current reality status 'production integrated'. Confirm actual implemented capability, hidden reusable modules, extension seams, and whether it strengthens the existing Proprietary application shell and route orchestration lane. Focus on: Which internal boundaries are stable? Which adapters are already abstracted? Which local modules are overloaded and should be split?","Inspect internal service boundaries, adapters, route-level dependencies, state stores, auth guards, compile coordination, tests, and extension seams.",Treat this as a non-external native anchor. External repo decisions should now be made around this anchor rather than replacing it.,Native anchor; repurpose logic does not apply except by splitting submodules into reusable internal services.,,,tkenaz/smriti,"Return concrete files/modules/adapters worth reusing and a verdict on whether the current reanchored bucket should be kept, upgraded, or downgraded.",Do not treat licensing as a filter. Do not propose replacing native foundations unless source evidence is overwhelming.,native/scriptoriumai-ui,v6_unified_source_of_truth_pack,"Before recommending direct code use, inspect the target repo row in the v6.1 operational/phase/source-audit boards. Respect copyleft_strategy_v6_1, preferred_boundary_model_v6_1, and open_compliance_if_used_as_is_v6_1. Do not assume reverse engineering is mandatory or that as-is use is always sensible.","If the repo-level strategy says bounded_sidecar_preferred or boundary_first_then_decide_as_is_vs_reimplementation, audit clean interfaces, protocol seams, subprocess/container boundaries, and what would be required to reimplement only the strategically necessary portions.",v6.3_final_source_of_truth
SCR_0005,,,,,,,,,,ScriptoriumAI repo packet,ScriptoriumAI,ScriptoriumAI re-anchored VS Code packets v1,sharelatex/sharelatex,sharelatex/sharelatex,Locked Parallel Foundation,P0,Running at localhost:3001 (docker). MIT layer.,"Audit sharelatex/sharelatex for ScriptoriumAI. Start from the reanchored bucket 'Locked Parallel Foundation' and current reality status 'Running at localhost:3001 (docker). MIT layer.'. Confirm actual implemented capability, hidden reusable modules, extension seams, and whether it strengthens the existing LaTeX collaboration backend lane. Focus on: Inspect hidden modules, extension seams, data contracts, rendering paths, auth/storage coupling, and export/import boundaries.","HTTP API + WebSocket (excised-editor-client.ts, excised-editor-websocket.ts, overleaf-client.ts, overleaf-websocket.ts) ; Editor.tsx, EditorSimplified.tsx, file tree, compile artifacts, collaboration panel, history/review, SyncTeX","Ground this repo in the actual ScriptoriumAI architecture rather than treating it as speculative. Preserve the current integration boundary (HTTP API + WebSocket (excised-editor-client.ts, excised-editor-websocket.ts, overleaf-client.ts, overleaf-websocket.ts)) and audit for hidden reusable modules, extension points, and coupling risks. Existing powers: Editor.tsx, EditorSimplified.tsx, file tree, compile artifacts, collaboration panel, history/review, SyncTeX.","Repurpose means extracting hidden internals, adapters, schemas, UI patterns, or subservices that strengthen the existing implemented surfaces without destabilizing the current product shell.",native/scriptoriumai-ui,native/ScriptoriumAI-Server,sharelatex/sharelatex,"Return concrete files/modules/adapters worth reusing and a verdict on whether the current reanchored bucket should be kept, upgraded, or downgraded.",Do not treat licensing as a filter. Do not propose replacing native foundations unless source evidence is overwhelming.,sharelatex/sharelatex,v6_unified_source_of_truth_pack,"Before recommending direct code use, inspect the target repo row in the v6.1 operational/phase/source-audit boards. Respect copyleft_strategy_v6_1, preferred_boundary_model_v6_1, and open_compliance_if_used_as_is_v6_1. Do not assume reverse engineering is mandatory or that as-is use is always sensible.","If the repo-level strategy says bounded_sidecar_preferred or boundary_first_then_decide_as_is_vs_reimplementation, audit clean interfaces, protocol seams, subprocess/container boundaries, and what would be required to reimplement only the strategically necessary portions.",v6.3_final_source_of_truth
SCR_0006,,,,,,,,,,ScriptoriumAI repo packet,ScriptoriumAI,ScriptoriumAI re-anchored VS Code packets v1,abhigyanpatwari/gitnexus,abhigyanpatwari/gitnexus,Locked Strategic Donor,P0,Production — .gitnexus/ config present in all sub-services,"Audit abhigyanpatwari/gitnexus for ScriptoriumAI. Start from the reanchored bucket 'Locked Strategic Donor' and current reality status 'Production — .gitnexus/ config present in all sub-services'. Confirm actual implemented capability, hidden reusable modules, extension seams, and whether it strengthens the existing Provenance and repository analysis substrate lane. Focus on: Inspect hidden modules, extension seams, data contracts, rendering paths, auth/storage coupling, and export/import boundaries.",".gitnexus/ directory convention + mirrors/GitNexus/gitnexus/src/cli/analyze.ts ; Corpus governance analysis, integration boundary memory, provenance ledger","Ground this repo in the actual ScriptoriumAI architecture rather than treating it as speculative. Preserve the current integration boundary (.gitnexus/ directory convention + mirrors/GitNexus/gitnexus/src/cli/analyze.ts) and audit for hidden reusable modules, extension points, and coupling risks. Existing powers: Corpus governance analysis, integration boundary memory, provenance ledger.","Repurpose means extracting hidden internals, adapters, schemas, UI patterns, or subservices that strengthen the existing implemented surfaces without destabilizing the current product shell.",native/scriptoriumai-ui,native/ScriptoriumAI-Server,abhigyanpatwari/GitNexus,"Return concrete files/modules/adapters worth reusing and a verdict on whether the current reanchored bucket should be kept, upgraded, or downgraded.",Do not treat licensing as a filter. Do not propose replacing native foundations unless source evidence is overwhelming.,abhigyanpatwari/gitnexus,v6_unified_source_of_truth_pack,"Before recommending direct code use, inspect the target repo row in the v6.1 operational/phase/source-audit boards. Respect copyleft_strategy_v6_1, preferred_boundary_model_v6_1, and open_compliance_if_used_as_is_v6_1. Do not assume reverse engineering is mandatory or that as-is use is always sensible.","If the repo-level strategy says bounded_sidecar_preferred or boundary_first_then_decide_as_is_vs_reimplementation, audit clean interfaces, protocol seams, subprocess/container boundaries, and what would be required to reimplement only the strategically necessary portions.",v6.3_final_source_of_truth
SCR_0007,,,,,,,,,,ScriptoriumAI repo packet,ScriptoriumAI,ScriptoriumAI re-anchored VS Code packets v1,berriai/litellm,berriai/litellm,Locked Strategic Donor,P0,Configured (litellm_config.yaml); wired to ScriptoriumAI-Server LLM calls,"Audit berriai/litellm for ScriptoriumAI. Start from the reanchored bucket 'Locked Strategic Donor' and current reality status 'Configured (litellm_config.yaml); wired to ScriptoriumAI-Server LLM calls'. Confirm actual implemented capability, hidden reusable modules, extension seams, and whether it strengthens the existing Unified LLM routing substrate lane. Focus on: Inspect hidden modules, extension seams, data contracts, rendering paths, auth/storage coupling, and export/import boundaries.","HTTP proxy (llm-provider-resolver.js, llm-preferences.ts) ; OpenApiRouting.tsx (tier selectors, key vault), all AI analysis calls, BYOK provider support","Ground this repo in the actual ScriptoriumAI architecture rather than treating it as speculative. Preserve the current integration boundary (HTTP proxy (llm-provider-resolver.js, llm-preferences.ts)) and audit for hidden reusable modules, extension points, and coupling risks. Existing powers: OpenApiRouting.tsx (tier selectors, key vault), all AI analysis calls, BYOK provider support.","Repurpose means extracting hidden internals, adapters, schemas, UI patterns, or subservices that strengthen the existing implemented surfaces without destabilizing the current product shell.",native/scriptoriumai-ui,native/ScriptoriumAI-Server,sharelatex/sharelatex,"Return concrete files/modules/adapters worth reusing and a verdict on whether the current reanchored bucket should be kept, upgraded, or downgraded.",Do not treat licensing as a filter. Do not propose replacing native foundations unless source evidence is overwhelming.,berriai/litellm,v6_unified_source_of_truth_pack,"Before recommending direct code use, inspect the target repo row in the v6.1 operational/phase/source-audit boards. Respect copyleft_strategy_v6_1, preferred_boundary_model_v6_1, and open_compliance_if_used_as_is_v6_1. Do not assume reverse engineering is mandatory or that as-is use is always sensible.","If the repo-level strategy says bounded_sidecar_preferred or boundary_first_then_decide_as_is_vs_reimplementation, audit clean interfaces, protocol seams, subprocess/container boundaries, and what would be required to reimplement only the strategically necessary portions.",v6.3_final_source_of_truth
SCR_0008,,,,,,,,,,ScriptoriumAI repo packet,ScriptoriumAI,ScriptoriumAI re-anchored VS Code packets v1,lukas-blecher/latex-ocr,lukas-blecher/latex-ocr,Locked Strategic Donor,P0,"Production (Docker service, port 8503)","Audit lukas-blecher/latex-ocr for ScriptoriumAI. Start from the reanchored bucket 'Locked Strategic Donor' and current reality status 'Production (Docker service, port 8503)'. Confirm actual implemented capability, hidden reusable modules, extension seams, and whether it strengthens the existing OCR model substrate lane. Focus on: Inspect hidden modules, extension seams, data contracts, rendering paths, auth/storage coupling, and export/import boundaries.","LaTeX-OCR-Service/api_server.py, ScriptoriumAI-Server/routes/ocr.js, LATEX_OCR_URL env wiring ; PDF Intake OCR, editor image-to-LaTeX insertion","Ground this repo in the actual ScriptoriumAI architecture rather than treating it as speculative. Preserve the current integration boundary (LaTeX-OCR-Service/api_server.py, ScriptoriumAI-Server/routes/ocr.js, LATEX_OCR_URL env wiring) and audit for hidden reusable modules, extension points, and coupling risks. Existing powers: PDF Intake OCR, editor image-to-LaTeX insertion.","Repurpose means extracting hidden internals, adapters, schemas, UI patterns, or subservices that strengthen the existing implemented surfaces without destabilizing the current product shell.",pdfmd/pdfmd,lukas-blecher/latex-ocr,mli55/pdfdelta,"Return concrete files/modules/adapters worth reusing and a verdict on whether the current reanchored bucket should be kept, upgraded, or downgraded.",Do not treat licensing as a filter. Do not propose replacing native foundations unless source evidence is overwhelming.,lukas-blecher/latex-ocr,v6_unified_source_of_truth_pack,"Before recommending direct code use, inspect the target repo row in the v6.1 operational/phase/source-audit boards. Respect copyleft_strategy_v6_1, preferred_boundary_model_v6_1, and open_compliance_if_used_as_is_v6_1. Do not assume reverse engineering is mandatory or that as-is use is always sensible.","If the repo-level strategy says bounded_sidecar_preferred or boundary_first_then_decide_as_is_vs_reimplementation, audit clean interfaces, protocol seams, subprocess/container boundaries, and what would be required to reimplement only the strategically necessary portions.",v6.3_final_source_of_truth
SCR_0009,,,,,,,,,,ScriptoriumAI repo packet,ScriptoriumAI,ScriptoriumAI re-anchored VS Code packets v1,manimcommunity/manim,manimcommunity/manim,Locked Strategic Donor,P0,Production — rendered via LaTeX-OCR-Service / ScriptoriumAI-Visualizer,"Audit manimcommunity/manim for ScriptoriumAI. Start from the reanchored bucket 'Locked Strategic Donor' and current reality status 'Production — rendered via LaTeX-OCR-Service / ScriptoriumAI-Visualizer'. Confirm actual implemented capability, hidden reusable modules, extension seams, and whether it strengthens the existing Animation and visualization substrate lane. Focus on: Inspect hidden modules, extension seams, data contracts, rendering paths, auth/storage coupling, and export/import boundaries.","ManimSandbox.tsx UI, ScriptoriumAI-Visualizer/app.py render endpoint, uv-runtime-manager.js Python sandbox ; /app/manim-sandbox — Manim Sandbox surface; storyboard gallery; AI animation authoring","Ground this repo in the actual ScriptoriumAI architecture rather than treating it as speculative. Preserve the current integration boundary (ManimSandbox.tsx UI, ScriptoriumAI-Visualizer/app.py render endpoint, uv-runtime-manager.js Python sandbox) and audit for hidden reusable modules, extension points, and coupling risks. Existing powers: /app/manim-sandbox — Manim Sandbox surface; storyboard gallery; AI animation authoring.","Repurpose means extracting hidden internals, adapters, schemas, UI patterns, or subservices that strengthen the existing implemented surfaces without destabilizing the current product shell.",manimcommunity/manim,remotion-dev/remotion,native/ScriptoriumAI-Visualizer,"Return concrete files/modules/adapters worth reusing and a verdict on whether the current reanchored bucket should be kept, upgraded, or downgraded.",Do not treat licensing as a filter. Do not propose replacing native foundations unless source evidence is overwhelming.,manimcommunity/manim,v6_unified_source_of_truth_pack,"Before recommending direct code use, inspect the target repo row in the v6.1 operational/phase/source-audit boards. Respect copyleft_strategy_v6_1, preferred_boundary_model_v6_1, and open_compliance_if_used_as_is_v6_1. Do not assume reverse engineering is mandatory or that as-is use is always sensible.","If the repo-level strategy says bounded_sidecar_preferred or boundary_first_then_decide_as_is_vs_reimplementation, audit clean interfaces, protocol seams, subprocess/container boundaries, and what would be required to reimplement only the strategically necessary portions.",v6.3_final_source_of_truth
SCR_0010,,,,,,,,,,ScriptoriumAI repo packet,ScriptoriumAI,ScriptoriumAI re-anchored VS Code packets v1,remotion-dev/remotion,remotion-dev/remotion,Locked Strategic Donor,P0,Production,"Audit remotion-dev/remotion for ScriptoriumAI. Start from the reanchored bucket 'Locked Strategic Donor' and current reality status 'Production'. Confirm actual implemented capability, hidden reusable modules, extension seams, and whether it strengthens the existing Video composition substrate lane. Focus on: Inspect hidden modules, extension seams, data contracts, rendering paths, auth/storage coupling, and export/import boundaries.",RemotionView.tsx + ScriptoriumAI-Server/services/remotion-render-service.js + routes/paper2video.js ; /app/remotion — Video Studio surface; paper-to-video pipeline,"Ground this repo in the actual ScriptoriumAI architecture rather than treating it as speculative. Preserve the current integration boundary (RemotionView.tsx + ScriptoriumAI-Server/services/remotion-render-service.js + routes/paper2video.js) and audit for hidden reusable modules, extension points, and coupling risks. Existing powers: /app/remotion — Video Studio surface; paper-to-video pipeline.","Repurpose means extracting hidden internals, adapters, schemas, UI patterns, or subservices that strengthen the existing implemented surfaces without destabilizing the current product shell.",manimcommunity/manim,remotion-dev/remotion,native/ScriptoriumAI-Visualizer,"Return concrete files/modules/adapters worth reusing and a verdict on whether the current reanchored bucket should be kept, upgraded, or downgraded.",Do not treat licensing as a filter. Do not propose replacing native foundations unless source evidence is overwhelming.,remotion-dev/remotion,v6_unified_source_of_truth_pack,"Before recommending direct code use, inspect the target repo row in the v6.1 operational/phase/source-audit boards. Respect copyleft_strategy_v6_1, preferred_boundary_model_v6_1, and open_compliance_if_used_as_is_v6_1. Do not assume reverse engineering is mandatory or that as-is use is always sensible.","If the repo-level strategy says bounded_sidecar_preferred or boundary_first_then_decide_as_is_vs_reimplementation, audit clean interfaces, protocol seams, subprocess/container boundaries, and what would be required to reimplement only the strategically necessary portions.",v6.3_final_source_of_truth
SCR_0011,,,,,,,,,,ScriptoriumAI repo packet,ScriptoriumAI,ScriptoriumAI re-anchored VS Code packets v1,supertokens/supertokens-core,supertokens/supertokens-core,Locked Strategic Donor,P0,Production — fully wired,"Audit supertokens/supertokens-core for ScriptoriumAI. Start from the reanchored bucket 'Locked Strategic Donor' and current reality status 'Production — fully wired'. Confirm actual implemented capability, hidden reusable modules, extension seams, and whether it strengthens the existing Authentication substrate lane. Focus on: Inspect hidden modules, extension seams, data contracts, rendering paths, auth/storage coupling, and export/import boundaries.","supertokens-node middleware in ScriptoriumAI-Server; supertokens-web-js + supertokens-auth-react in UI ; All auth flows: LoginPage, RegisterPage, session cookies, route guards, tier enforcement","Ground this repo in the actual ScriptoriumAI architecture rather than treating it as speculative. Preserve the current integration boundary (supertokens-node middleware in ScriptoriumAI-Server; supertokens-web-js + supertokens-auth-react in UI) and audit for hidden reusable modules, extension points, and coupling risks. Existing powers: All auth flows: LoginPage, RegisterPage, session cookies, route guards, tier enforcement.","Repurpose means extracting hidden internals, adapters, schemas, UI patterns, or subservices that strengthen the existing implemented surfaces without destabilizing the current product shell.",native/scriptoriumai-ui,native/ScriptoriumAI-Server,sharelatex/sharelatex,"Return concrete files/modules/adapters worth reusing and a verdict on whether the current reanchored bucket should be kept, upgraded, or downgraded.",Do not treat licensing as a filter. Do not propose replacing native foundations unless source evidence is overwhelming.,supertokens/supertokens-core,v6_unified_source_of_truth_pack,"Before recommending direct code use, inspect the target repo row in the v6.1 operational/phase/source-audit boards. Respect copyleft_strategy_v6_1, preferred_boundary_model_v6_1, and open_compliance_if_used_as_is_v6_1. Do not assume reverse engineering is mandatory or that as-is use is always sensible.","If the repo-level strategy says bounded_sidecar_preferred or boundary_first_then_decide_as_is_vs_reimplementation, audit clean interfaces, protocol seams, subprocess/container boundaries, and what would be required to reimplement only the strategically necessary portions.",v6.3_final_source_of_truth
SCR_0012,,,,,,,,,,ScriptoriumAI repo packet,ScriptoriumAI,ScriptoriumAI re-anchored VS Code packets v1,supertokens/supertokens-web-js,supertokens/supertokens-web-js,Locked Strategic Donor,P0,Production — fully wired,"Audit supertokens/supertokens-web-js for ScriptoriumAI. Start from the reanchored bucket 'Locked Strategic Donor' and current reality status 'Production — fully wired'. Confirm actual implemented capability, hidden reusable modules, extension seams, and whether it strengthens the existing Authentication substrate lane. Focus on: Inspect hidden modules, extension seams, data contracts, rendering paths, auth/storage coupling, and export/import boundaries.","supertokens-node middleware in ScriptoriumAI-Server; supertokens-web-js + supertokens-auth-react in UI ; All auth flows: LoginPage, RegisterPage, session cookies, route guards, tier enforcement","Ground this repo in the actual ScriptoriumAI architecture rather than treating it as speculative. Preserve the current integration boundary (supertokens-node middleware in ScriptoriumAI-Server; supertokens-web-js + supertokens-auth-react in UI) and audit for hidden reusable modules, extension points, and coupling risks. Existing powers: All auth flows: LoginPage, RegisterPage, session cookies, route guards, tier enforcement.","Repurpose means extracting hidden internals, adapters, schemas, UI patterns, or subservices that strengthen the existing implemented surfaces without destabilizing the current product shell.",native/scriptoriumai-ui,native/ScriptoriumAI-Server,sharelatex/sharelatex,"Return concrete files/modules/adapters worth reusing and a verdict on whether the current reanchored bucket should be kept, upgraded, or downgraded.",Do not treat licensing as a filter. Do not propose replacing native foundations unless source evidence is overwhelming.,supertokens/supertokens-web-js,v6_unified_source_of_truth_pack,"Before recommending direct code use, inspect the target repo row in the v6.1 operational/phase/source-audit boards. Respect copyleft_strategy_v6_1, preferred_boundary_model_v6_1, and open_compliance_if_used_as_is_v6_1. Do not assume reverse engineering is mandatory or that as-is use is always sensible.","If the repo-level strategy says bounded_sidecar_preferred or boundary_first_then_decide_as_is_vs_reimplementation, audit clean interfaces, protocol seams, subprocess/container boundaries, and what would be required to reimplement only the strategically necessary portions.",v6.3_final_source_of_truth
SCR_0013,,,,,,,,,,ScriptoriumAI repo packet,ScriptoriumAI,ScriptoriumAI re-anchored VS Code packets v1,tkenaz/breathe-memory,tkenaz/breathe-memory,Locked Strategic Donor,P0,Production,"Audit tkenaz/breathe-memory for ScriptoriumAI. Start from the reanchored bucket 'Locked Strategic Donor' and current reality status 'Production'. Confirm actual implemented capability, hidden reusable modules, extension seams, and whether it strengthens the existing Corpus memory and governance substrate lane. Focus on: Inspect hidden modules, extension seams, data contracts, rendering paths, auth/storage coupling, and export/import boundaries.","smriti-service.js, smriti-repository.js, smriti-collaboration-bridge.js, smriti-client.ts, smriti-actor.ts, routes/smriti.js ; AI Memory panel in editor, REME memory export/import, collaboration memory anchors, breathe-memory domain all 8 modules","Ground this repo in the actual ScriptoriumAI architecture rather than treating it as speculative. Preserve the current integration boundary (smriti-service.js, smriti-repository.js, smriti-collaboration-bridge.js, smriti-client.ts, smriti-actor.ts, routes/smriti.js) and audit for hidden reusable modules, extension points, and coupling risks. Existing powers: AI Memory panel in editor, REME memory export/import, collaboration memory anchors, breathe-memory domain all 8 modules.","Repurpose means extracting hidden internals, adapters, schemas, UI patterns, or subservices that strengthen the existing implemented surfaces without destabilizing the current product shell.",native/ScriptoriumAI-Server,stanford-oval/storm,abhigyanpatwari/GitNexus,"Return concrete files/modules/adapters worth reusing and a verdict on whether the current reanchored bucket should be kept, upgraded, or downgraded.",Do not treat licensing as a filter. Do not propose replacing native foundations unless source evidence is overwhelming.,tkenaz/breathe-memory,v6_unified_source_of_truth_pack,"Before recommending direct code use, inspect the target repo row in the v6.1 operational/phase/source-audit boards. Respect copyleft_strategy_v6_1, preferred_boundary_model_v6_1, and open_compliance_if_used_as_is_v6_1. Do not assume reverse engineering is mandatory or that as-is use is always sensible.","If the repo-level strategy says bounded_sidecar_preferred or boundary_first_then_decide_as_is_vs_reimplementation, audit clean interfaces, protocol seams, subprocess/container boundaries, and what would be required to reimplement only the strategically necessary portions.",v6.3_final_source_of_truth
SCR_0014,,,,,,,,,,ScriptoriumAI repo packet,ScriptoriumAI,ScriptoriumAI re-anchored VS Code packets v1,tkenaz/smriti,tkenaz/smriti,Locked Strategic Donor,P0,"Production ; Smriti: **integrated** (see §3.11). ReMe: integrated (offline queue, session export). Supermemory: **monitor only** — future adapter candidate","Audit tkenaz/smriti for ScriptoriumAI. Start from the reanchored bucket 'Locked Strategic Donor' and current reality status 'Production ; Smriti: **integrated** (see §3.11). ReMe: integrated (offline queue, session export). Supermemory: **monitor only** — future adapter candidate'. Confirm actual implemented capability, hidden reusable modules, extension seams, and whether it strengthens the existing Session memory substrate lane. Focus on: Inspect hidden modules, extension seams, data contracts, rendering paths, auth/storage coupling, and export/import boundaries.","smriti-service.js, smriti-repository.js, smriti-collaboration-bridge.js, smriti-client.ts, smriti-actor.ts, routes/smriti.js ; AI Memory panel in editor, REME memory export/import, collaboration memory anchors, breathe-memory domain all 8 modules","Ground this repo in the actual ScriptoriumAI architecture rather than treating it as speculative. Preserve the current integration boundary (smriti-service.js, smriti-repository.js, smriti-collaboration-bridge.js, smriti-client.ts, smriti-actor.ts, routes/smriti.js) and audit for hidden reusable modules, extension points, and coupling risks. Existing powers: AI Memory panel in editor, REME memory export/import, collaboration memory anchors, breathe-memory domain all 8 modules ; Breathe-memory domain all 8 modules, AI Memory panel.","Repurpose means extracting hidden internals, adapters, schemas, UI patterns, or subservices that strengthen the existing implemented surfaces without destabilizing the current product shell.",native/ScriptoriumAI-Server,stanford-oval/storm,abhigyanpatwari/GitNexus,"Return concrete files/modules/adapters worth reusing and a verdict on whether the current reanchored bucket should be kept, upgraded, or downgraded.",Do not treat licensing as a filter. Do not propose replacing native foundations unless source evidence is overwhelming.,tkenaz/smriti,v6_unified_source_of_truth_pack,"Before recommending direct code use, inspect the target repo row in the v6.1 operational/phase/source-audit boards. Respect copyleft_strategy_v6_1, preferred_boundary_model_v6_1, and open_compliance_if_used_as_is_v6_1. Do not assume reverse engineering is mandatory or that as-is use is always sensible.","If the repo-level strategy says bounded_sidecar_preferred or boundary_first_then_decide_as_is_vs_reimplementation, audit clean interfaces, protocol seams, subprocess/container boundaries, and what would be required to reimplement only the strategically necessary portions.",v6.3_final_source_of_truth
SCR_0015,,,,,,,,,,ScriptoriumAI repo packet,ScriptoriumAI,ScriptoriumAI re-anchored VS Code packets v1,mli55/pdfdelta,mli55/pdfdelta,Locked Strategic Donor,P1,Production,"Audit mli55/pdfdelta for ScriptoriumAI. Start from the reanchored bucket 'Locked Strategic Donor' and current reality status 'Production'. Confirm actual implemented capability, hidden reusable modules, extension seams, and whether it strengthens the existing PDF structural diff substrate lane. Focus on: Inspect hidden modules, extension seams, data contracts, rendering paths, auth/storage coupling, and export/import boundaries.","ScriptoriumAI-Server/services/pdfdelta-p2.js + pdfdelta-p3.js + integration boundary memory ; Cross-document compare (V4), Runboard diff view","Ground this repo in the actual ScriptoriumAI architecture rather than treating it as speculative. Preserve the current integration boundary (ScriptoriumAI-Server/services/pdfdelta-p2.js + pdfdelta-p3.js + integration boundary memory) and audit for hidden reusable modules, extension points, and coupling risks. Existing powers: Cross-document compare (V4), Runboard diff view.","Repurpose means extracting hidden internals, adapters, schemas, UI patterns, or subservices that strengthen the existing implemented surfaces without destabilizing the current product shell.",pdfmd/pdfmd,lukas-blecher/latex-ocr,mli55/pdfdelta,"Return concrete files/modules/adapters worth reusing and a verdict on whether the current reanchored bucket should be kept, upgraded, or downgraded.",Do not treat licensing as a filter. Do not propose replacing native foundations unless source evidence is overwhelming.,mli55/pdfdelta,v6_unified_source_of_truth_pack,"Before recommending direct code use, inspect the target repo row in the v6.1 operational/phase/source-audit boards. Respect copyleft_strategy_v6_1, preferred_boundary_model_v6_1, and open_compliance_if_used_as_is_v6_1. Do not assume reverse engineering is mandatory or that as-is use is always sensible.","If the repo-level strategy says bounded_sidecar_preferred or boundary_first_then_decide_as_is_vs_reimplementation, audit clean interfaces, protocol seams, subprocess/container boundaries, and what would be required to reimplement only the strategically necessary portions.",v6.3_final_source_of_truth
SCR_0016,,,,,,,,,,ScriptoriumAI repo packet,ScriptoriumAI,ScriptoriumAI re-anchored VS Code packets v1,pdfmd/pdfmd,pdfmd/pdfmd,Locked Strategic Donor,P1,Production,"Audit pdfmd/pdfmd for ScriptoriumAI. Start from the reanchored bucket 'Locked Strategic Donor' and current reality status 'Production'. Confirm actual implemented capability, hidden reusable modules, extension seams, and whether it strengthens the existing PDF intake QA substrate lane. Focus on: Inspect hidden modules, extension seams, data contracts, rendering paths, auth/storage coupling, and export/import boundaries.",ScriptoriumAI-Server/services/pdfmd-qa-service.js ; /app/pdfmd — PDF Intake surface; compile artifact QA,"Ground this repo in the actual ScriptoriumAI architecture rather than treating it as speculative. Preserve the current integration boundary (ScriptoriumAI-Server/services/pdfmd-qa-service.js) and audit for hidden reusable modules, extension points, and coupling risks. Existing powers: /app/pdfmd — PDF Intake surface; compile artifact QA.","Repurpose means extracting hidden internals, adapters, schemas, UI patterns, or subservices that strengthen the existing implemented surfaces without destabilizing the current product shell.",pdfmd/pdfmd,lukas-blecher/latex-ocr,mli55/pdfdelta,"Return concrete files/modules/adapters worth reusing and a verdict on whether the current reanchored bucket should be kept, upgraded, or downgraded.",Do not treat licensing as a filter. Do not propose replacing native foundations unless source evidence is overwhelming.,pdfmd/pdfmd,v6_unified_source_of_truth_pack,"Before recommending direct code use, inspect the target repo row in the v6.1 operational/phase/source-audit boards. Respect copyleft_strategy_v6_1, preferred_boundary_model_v6_1, and open_compliance_if_used_as_is_v6_1. Do not assume reverse engineering is mandatory or that as-is use is always sensible.","If the repo-level strategy says bounded_sidecar_preferred or boundary_first_then_decide_as_is_vs_reimplementation, audit clean interfaces, protocol seams, subprocess/container boundaries, and what would be required to reimplement only the strategically necessary portions.",v6.3_final_source_of_truth
SCR_0017,,,,,,,,,,ScriptoriumAI repo packet,ScriptoriumAI,ScriptoriumAI re-anchored VS Code packets v1,tkenaz/reme,tkenaz/reme,Locked Strategic Donor,P1,"Smriti: **integrated** (see §3.11). ReMe: integrated (offline queue, session export). Supermemory: **monitor only** — future adapter candidate","Audit tkenaz/reme for ScriptoriumAI. Start from the reanchored bucket 'Locked Strategic Donor' and current reality status 'Smriti: **integrated** (see §3.11). ReMe: integrated (offline queue, session export). Supermemory: **monitor only** — future adapter candidate'. Confirm actual implemented capability, hidden reusable modules, extension seams, and whether it strengthens the existing Medium-horizon memory/export substrate lane. Focus on: Inspect hidden modules, extension seams, data contracts, rendering paths, auth/storage coupling, and export/import boundaries."," ; Breathe-memory domain all 8 modules, AI Memory panel","Ground this repo in the actual ScriptoriumAI architecture rather than treating it as speculative. Preserve the current integration boundary (see architecture snapshot) and audit for hidden reusable modules, extension points, and coupling risks. Existing powers: Breathe-memory domain all 8 modules, AI Memory panel.","Repurpose means extracting hidden internals, adapters, schemas, UI patterns, or subservices that strengthen the existing implemented surfaces without destabilizing the current product shell.",native/ScriptoriumAI-Server,stanford-oval/storm,abhigyanpatwari/GitNexus,"Return concrete files/modules/adapters worth reusing and a verdict on whether the current reanchored bucket should be kept, upgraded, or downgraded.",Do not treat licensing as a filter. Do not propose replacing native foundations unless source evidence is overwhelming.,tkenaz/reme,v6_unified_source_of_truth_pack,"Before recommending direct code use, inspect the target repo row in the v6.1 operational/phase/source-audit boards. Respect copyleft_strategy_v6_1, preferred_boundary_model_v6_1, and open_compliance_if_used_as_is_v6_1. Do not assume reverse engineering is mandatory or that as-is use is always sensible.","If the repo-level strategy says bounded_sidecar_preferred or boundary_first_then_decide_as_is_vs_reimplementation, audit clean interfaces, protocol seams, subprocess/container boundaries, and what would be required to reimplement only the strategically necessary portions.",v6.3_final_source_of_truth
SCR_0018,,,,,,,,,,ScriptoriumAI repo packet,ScriptoriumAI,ScriptoriumAI re-anchored VS Code packets v1,excalidraw/excalidraw,excalidraw/excalidraw,Integrated Product Surface,P0,Production,"Audit excalidraw/excalidraw for ScriptoriumAI. Start from the reanchored bucket 'Integrated Product Surface' and current reality status 'Production'. Confirm actual implemented capability, hidden reusable modules, extension seams, and whether it strengthens the existing Whiteboard surface lane. Focus on: Inspect document/block schema; sync/persistence model; permissions and sharing; citation/external-source pipeline; import/export adapters; plugin/extension points; editor rendering model.",Lazy-loaded React embed in ExcalidrawBoard.tsx ; /app/excalidraw — Whiteboard studio surface,"Ground this repo in the actual ScriptoriumAI architecture rather than treating it as speculative. Preserve the current integration boundary (Lazy-loaded React embed in ExcalidrawBoard.tsx) and audit for hidden reusable modules, extension points, and coupling risks. Existing powers: /app/excalidraw — Whiteboard studio surface.","Repurpose means extracting hidden internals, adapters, schemas, UI patterns, or subservices that strengthen the existing implemented surfaces without destabilizing the current product shell.",native/scriptoriumai-ui,excalidraw/excalidraw,jgraph/drawio,"Return concrete files/modules/adapters worth reusing and a verdict on whether the current reanchored bucket should be kept, upgraded, or downgraded.",Do not treat licensing as a filter. Do not propose replacing native foundations unless source evidence is overwhelming.,excalidraw/excalidraw,v6_unified_source_of_truth_pack,"Before recommending direct code use, inspect the target repo row in the v6.1 operational/phase/source-audit boards. Respect copyleft_strategy_v6_1, preferred_boundary_model_v6_1, and open_compliance_if_used_as_is_v6_1. Do not assume reverse engineering is mandatory or that as-is use is always sensible.","If the repo-level strategy says bounded_sidecar_preferred or boundary_first_then_decide_as_is_vs_reimplementation, audit clean interfaces, protocol seams, subprocess/container boundaries, and what would be required to reimplement only the strategically necessary portions.",v6.3_final_source_of_truth
SCR_0019,,,,,,,,,,ScriptoriumAI repo packet,ScriptoriumAI,ScriptoriumAI re-anchored VS Code packets v1,jgraph/drawio,jgraph/drawio,Integrated Product Surface,P1,Production,"Audit jgraph/drawio for ScriptoriumAI. Start from the reanchored bucket 'Integrated Product Surface' and current reality status 'Production'. Confirm actual implemented capability, hidden reusable modules, extension seams, and whether it strengthens the existing Diagram studio surface lane. Focus on: Inspect hidden modules, extension seams, data contracts, rendering paths, auth/storage coupling, and export/import boundaries.",Iframe embed in NextAiDrawIoView.tsx ; /app/nextaidrawio — AI Diagram Studio surface,"Ground this repo in the actual ScriptoriumAI architecture rather than treating it as speculative. Preserve the current integration boundary (Iframe embed in NextAiDrawIoView.tsx) and audit for hidden reusable modules, extension points, and coupling risks. Existing powers: /app/nextaidrawio — AI Diagram Studio surface.","Repurpose means extracting hidden internals, adapters, schemas, UI patterns, or subservices that strengthen the existing implemented surfaces without destabilizing the current product shell.",native/scriptoriumai-ui,native/ScriptoriumAI-Server,sharelatex/sharelatex,"Return concrete files/modules/adapters worth reusing and a verdict on whether the current reanchored bucket should be kept, upgraded, or downgraded.",Do not treat licensing as a filter. Do not propose replacing native foundations unless source evidence is overwhelming.,jgraph/drawio,v6_unified_source_of_truth_pack,"Before recommending direct code use, inspect the target repo row in the v6.1 operational/phase/source-audit boards. Respect copyleft_strategy_v6_1, preferred_boundary_model_v6_1, and open_compliance_if_used_as_is_v6_1. Do not assume reverse engineering is mandatory or that as-is use is always sensible.","If the repo-level strategy says bounded_sidecar_preferred or boundary_first_then_decide_as_is_vs_reimplementation, audit clean interfaces, protocol seams, subprocess/container boundaries, and what would be required to reimplement only the strategically necessary portions.",v6.3_final_source_of_truth
SCR_0020,,,,,,,,,,ScriptoriumAI repo packet,ScriptoriumAI,ScriptoriumAI re-anchored VS Code packets v1,veritas-kanban/veritas-kanban,veritas-kanban/veritas-kanban,Integrated Product Surface,P1,Production,"Audit veritas-kanban/veritas-kanban for ScriptoriumAI. Start from the reanchored bucket 'Integrated Product Surface' and current reality status 'Production'. Confirm actual implemented capability, hidden reusable modules, extension seams, and whether it strengthens the existing Kanban surface lane. Focus on: Inspect hidden modules, extension seams, data contracts, rendering paths, auth/storage coupling, and export/import boundaries.",KanbanPage.tsx ; /app/kanban — AI Kanban surface,"Ground this repo in the actual ScriptoriumAI architecture rather than treating it as speculative. Preserve the current integration boundary (KanbanPage.tsx) and audit for hidden reusable modules, extension points, and coupling risks. Existing powers: /app/kanban — AI Kanban surface.","Repurpose means extracting hidden internals, adapters, schemas, UI patterns, or subservices that strengthen the existing implemented surfaces without destabilizing the current product shell.",native/scriptoriumai-ui,excalidraw/excalidraw,jgraph/drawio,"Return concrete files/modules/adapters worth reusing and a verdict on whether the current reanchored bucket should be kept, upgraded, or downgraded.",Do not treat licensing as a filter. Do not propose replacing native foundations unless source evidence is overwhelming.,veritas-kanban/veritas-kanban,v6_unified_source_of_truth_pack,"Before recommending direct code use, inspect the target repo row in the v6.1 operational/phase/source-audit boards. Respect copyleft_strategy_v6_1, preferred_boundary_model_v6_1, and open_compliance_if_used_as_is_v6_1. Do not assume reverse engineering is mandatory or that as-is use is always sensible.","If the repo-level strategy says bounded_sidecar_preferred or boundary_first_then_decide_as_is_vs_reimplementation, audit clean interfaces, protocol seams, subprocess/container boundaries, and what would be required to reimplement only the strategically necessary portions.",v6.3_final_source_of_truth
SCR_0021,,,,,,,,,,ScriptoriumAI repo packet,ScriptoriumAI,ScriptoriumAI re-anchored VS Code packets v1,wanglin2/mind-map,wanglin2/mind-map,Integrated Product Surface,P1,Production,"Audit wanglin2/mind-map for ScriptoriumAI. Start from the reanchored bucket 'Integrated Product Surface' and current reality status 'Production'. Confirm actual implemented capability, hidden reusable modules, extension seams, and whether it strengthens the existing Mind-map surface lane. Focus on: Inspect hidden modules, extension seams, data contracts, rendering paths, auth/storage coupling, and export/import boundaries.",Iframe embed with postMessage bridge in MindMapView.tsx ; /app/mindmap — MindMap studio surface,"Ground this repo in the actual ScriptoriumAI architecture rather than treating it as speculative. Preserve the current integration boundary (Iframe embed with postMessage bridge in MindMapView.tsx) and audit for hidden reusable modules, extension points, and coupling risks. Existing powers: /app/mindmap — MindMap studio surface.","Repurpose means extracting hidden internals, adapters, schemas, UI patterns, or subservices that strengthen the existing implemented surfaces without destabilizing the current product shell.",native/scriptoriumai-ui,native/ScriptoriumAI-Server,sharelatex/sharelatex,"Return concrete files/modules/adapters worth reusing and a verdict on whether the current reanchored bucket should be kept, upgraded, or downgraded.",Do not treat licensing as a filter. Do not propose replacing native foundations unless source evidence is overwhelming.,wanglin2/mind-map,v6_unified_source_of_truth_pack,"Before recommending direct code use, inspect the target repo row in the v6.1 operational/phase/source-audit boards. Respect copyleft_strategy_v6_1, preferred_boundary_model_v6_1, and open_compliance_if_used_as_is_v6_1. Do not assume reverse engineering is mandatory or that as-is use is always sensible.","If the repo-level strategy says bounded_sidecar_preferred or boundary_first_then_decide_as_is_vs_reimplementation, audit clean interfaces, protocol seams, subprocess/container boundaries, and what would be required to reimplement only the strategically necessary portions.",v6.3_final_source_of_truth
SCR_0022,,,,,,,,,,ScriptoriumAI repo packet,ScriptoriumAI,ScriptoriumAI re-anchored VS Code packets v1,stanford-oval/storm,stanford-oval/storm,Implemented Pattern Source,P1,Pattern reference — not a live runtime dependency,"Audit stanford-oval/storm for ScriptoriumAI. Start from the reanchored bucket 'Implemented Pattern Source' and current reality status 'Pattern reference — not a live runtime dependency'. Confirm actual implemented capability, hidden reusable modules, extension seams, and whether it strengthens the existing Research swarm design pattern lane. Focus on: Inspect planner/task graph; provider abstraction; tool registry or MCP bridges; memory/state schema; approvals/retries; telemetry/event bus; plugin or skill loading hooks.","Swarm design patterns used in ResearchAgentDashboard.tsx and NewResearchTopic.tsx ; /app/research-agent design: depth strategies, multi-perspective coverage","Ground this repo in the actual ScriptoriumAI architecture rather than treating it as speculative. Preserve the current integration boundary (Swarm design patterns used in ResearchAgentDashboard.tsx and NewResearchTopic.tsx) and audit for hidden reusable modules, extension points, and coupling risks. Existing powers: /app/research-agent design: depth strategies, multi-perspective coverage.","Repurpose means extracting hidden internals, adapters, schemas, UI patterns, or subservices that strengthen the existing implemented surfaces without destabilizing the current product shell.",native/ScriptoriumAI-Server,stanford-oval/storm,abhigyanpatwari/GitNexus,"Return concrete files/modules/adapters worth reusing and a verdict on whether the current reanchored bucket should be kept, upgraded, or downgraded.",Do not treat licensing as a filter. Do not propose replacing native foundations unless source evidence is overwhelming.,stanford-oval/storm,v6_unified_source_of_truth_pack,"Before recommending direct code use, inspect the target repo row in the v6.1 operational/phase/source-audit boards. Respect copyleft_strategy_v6_1, preferred_boundary_model_v6_1, and open_compliance_if_used_as_is_v6_1. Do not assume reverse engineering is mandatory or that as-is use is always sensible.","If the repo-level strategy says bounded_sidecar_preferred or boundary_first_then_decide_as_is_vs_reimplementation, audit clean interfaces, protocol seams, subprocess/container boundaries, and what would be required to reimplement only the strategically necessary portions.",v6.3_final_source_of_truth
SCR_0023,,,,,,,,,,ScriptoriumAI repo packet,ScriptoriumAI,ScriptoriumAI re-anchored VS Code packets v1,aakashns/fabro,aakashns/fabro,Implemented Pattern Source,P2,UI polish patterns used in scriptoriumai-ui/,"Audit aakashns/fabro for ScriptoriumAI. Start from the reanchored bucket 'Implemented Pattern Source' and current reality status 'UI polish patterns used in scriptoriumai-ui/'. Confirm actual implemented capability, hidden reusable modules, extension seams, and whether it strengthens the existing UI polish / dashboard pattern source lane. Focus on: Inspect hidden modules, extension seams, data contracts, rendering paths, auth/storage coupling, and export/import boundaries.","Component patterns (no direct npm dependency — clean-room implementation) ; Marketing shell, public pages visual design","Ground this repo in the actual ScriptoriumAI architecture rather than treating it as speculative. Preserve the current integration boundary (Component patterns (no direct npm dependency — clean-room implementation)) and audit for hidden reusable modules, extension points, and coupling risks. Existing powers: Marketing shell, public pages visual design.","Repurpose means extracting hidden internals, adapters, schemas, UI patterns, or subservices that strengthen the existing implemented surfaces without destabilizing the current product shell.",native/scriptoriumai-ui,excalidraw/excalidraw,jgraph/drawio,"Return concrete files/modules/adapters worth reusing and a verdict on whether the current reanchored bucket should be kept, upgraded, or downgraded.",Do not treat licensing as a filter. Do not propose replacing native foundations unless source evidence is overwhelming.,aakashns/fabro,v6_unified_source_of_truth_pack,"Before recommending direct code use, inspect the target repo row in the v6.1 operational/phase/source-audit boards. Respect copyleft_strategy_v6_1, preferred_boundary_model_v6_1, and open_compliance_if_used_as_is_v6_1. Do not assume reverse engineering is mandatory or that as-is use is always sensible.","If the repo-level strategy says bounded_sidecar_preferred or boundary_first_then_decide_as_is_vs_reimplementation, audit clean interfaces, protocol seams, subprocess/container boundaries, and what would be required to reimplement only the strategically necessary portions.",v6.3_final_source_of_truth
SCR_0024,,,,,,,,,,ScriptoriumAI repo packet,ScriptoriumAI,ScriptoriumAI re-anchored VS Code packets v1,anthropics/awesome-claude-skills,anthropics/awesome-claude-skills,Implemented Pattern Source,P2,Pattern reference for SkillsManager.tsx design; fallback skill IDs sourced from claude-skills,"Audit anthropics/awesome-claude-skills for ScriptoriumAI. Start from the reanchored bucket 'Implemented Pattern Source' and current reality status 'Pattern reference for SkillsManager.tsx design; fallback skill IDs sourced from claude-skills'. Confirm actual implemented capability, hidden reusable modules, extension seams, and whether it strengthens the existing Skill naming and catalog pattern source lane. Focus on: Inspect hidden modules, extension seams, data contracts, rendering paths, auth/storage coupling, and export/import boundaries.","SkillsManager.tsx FALLBACK_SKILLS array uses gitnexus-exploring, latex-formatting, manim-compilation from this family ; /app/skills-manager","Ground this repo in the actual ScriptoriumAI architecture rather than treating it as speculative. Preserve the current integration boundary (SkillsManager.tsx FALLBACK_SKILLS array uses gitnexus-exploring, latex-formatting, manim-compilation from this family) and audit for hidden reusable modules, extension points, and coupling risks. Existing powers: /app/skills-manager.","Repurpose means extracting hidden internals, adapters, schemas, UI patterns, or subservices that strengthen the existing implemented surfaces without destabilizing the current product shell.",native/ScriptoriumAI-Server,stanford-oval/storm,abhigyanpatwari/GitNexus,"Return concrete files/modules/adapters worth reusing and a verdict on whether the current reanchored bucket should be kept, upgraded, or downgraded.",Do not treat licensing as a filter. Do not propose replacing native foundations unless source evidence is overwhelming.,anthropics/awesome-claude-skills,v6_unified_source_of_truth_pack,"Before recommending direct code use, inspect the target repo row in the v6.1 operational/phase/source-audit boards. Respect copyleft_strategy_v6_1, preferred_boundary_model_v6_1, and open_compliance_if_used_as_is_v6_1. Do not assume reverse engineering is mandatory or that as-is use is always sensible.","If the repo-level strategy says bounded_sidecar_preferred or boundary_first_then_decide_as_is_vs_reimplementation, audit clean interfaces, protocol seams, subprocess/container boundaries, and what would be required to reimplement only the strategically necessary portions.",v6.3_final_source_of_truth
SCR_0025,,,,,,,,,,ScriptoriumAI repo packet,ScriptoriumAI,ScriptoriumAI re-anchored VS Code packets v1,featurebaseapp/featurebase,featurebaseapp/featurebase,Implemented Pattern Source,P2,Pattern reference for ChangelogPage.tsx and SupportPage.tsx design,"Audit featurebaseapp/featurebase for ScriptoriumAI. Start from the reanchored bucket 'Implemented Pattern Source' and current reality status 'Pattern reference for ChangelogPage.tsx and SupportPage.tsx design'. Confirm actual implemented capability, hidden reusable modules, extension seams, and whether it strengthens the existing Changelog/feedback pattern source lane. Focus on: Inspect hidden modules, extension seams, data contracts, rendering paths, auth/storage coupling, and export/import boundaries.", ; Changelog page structure,"Ground this repo in the actual ScriptoriumAI architecture rather than treating it as speculative. Preserve the current integration boundary (see architecture snapshot) and audit for hidden reusable modules, extension points, and coupling risks. Existing powers: Changelog page structure.","Repurpose means extracting hidden internals, adapters, schemas, UI patterns, or subservices that strengthen the existing implemented surfaces without destabilizing the current product shell.",native/scriptoriumai-ui,excalidraw/excalidraw,jgraph/drawio,"Return concrete files/modules/adapters worth reusing and a verdict on whether the current reanchored bucket should be kept, upgraded, or downgraded.",Do not treat licensing as a filter. Do not propose replacing native foundations unless source evidence is overwhelming.,featurebaseapp/featurebase,v6_unified_source_of_truth_pack,"Before recommending direct code use, inspect the target repo row in the v6.1 operational/phase/source-audit boards. Respect copyleft_strategy_v6_1, preferred_boundary_model_v6_1, and open_compliance_if_used_as_is_v6_1. Do not assume reverse engineering is mandatory or that as-is use is always sensible.","If the repo-level strategy says bounded_sidecar_preferred or boundary_first_then_decide_as_is_vs_reimplementation, audit clean interfaces, protocol seams, subprocess/container boundaries, and what would be required to reimplement only the strategically necessary portions.",v6.3_final_source_of_truth
SCR_0026,,,,,,,,,,ScriptoriumAI repo packet,ScriptoriumAI,ScriptoriumAI re-anchored VS Code packets v1,iflytek/skillhub,iflytek/skillhub,Implemented Pattern Source,P2,Pattern reference for SkillsManager.tsx design; fallback skill IDs sourced from claude-skills,"Audit iflytek/skillhub for ScriptoriumAI. Start from the reanchored bucket 'Implemented Pattern Source' and current reality status 'Pattern reference for SkillsManager.tsx design; fallback skill IDs sourced from claude-skills'. Confirm actual implemented capability, hidden reusable modules, extension seams, and whether it strengthens the existing Skill registry pattern source lane. Focus on: Inspect hidden modules, extension seams, data contracts, rendering paths, auth/storage coupling, and export/import boundaries.","SkillsManager.tsx FALLBACK_SKILLS array uses gitnexus-exploring, latex-formatting, manim-compilation from this family ; /app/skills-manager","Ground this repo in the actual ScriptoriumAI architecture rather than treating it as speculative. Preserve the current integration boundary (SkillsManager.tsx FALLBACK_SKILLS array uses gitnexus-exploring, latex-formatting, manim-compilation from this family) and audit for hidden reusable modules, extension points, and coupling risks. Existing powers: /app/skills-manager.","Repurpose means extracting hidden internals, adapters, schemas, UI patterns, or subservices that strengthen the existing implemented surfaces without destabilizing the current product shell.",native/ScriptoriumAI-Server,stanford-oval/storm,abhigyanpatwari/GitNexus,"Return concrete files/modules/adapters worth reusing and a verdict on whether the current reanchored bucket should be kept, upgraded, or downgraded.",Do not treat licensing as a filter. Do not propose replacing native foundations unless source evidence is overwhelming.,iflytek/skillhub,v6_unified_source_of_truth_pack,"Before recommending direct code use, inspect the target repo row in the v6.1 operational/phase/source-audit boards. Respect copyleft_strategy_v6_1, preferred_boundary_model_v6_1, and open_compliance_if_used_as_is_v6_1. Do not assume reverse engineering is mandatory or that as-is use is always sensible.","If the repo-level strategy says bounded_sidecar_preferred or boundary_first_then_decide_as_is_vs_reimplementation, audit clean interfaces, protocol seams, subprocess/container boundaries, and what would be required to reimplement only the strategically necessary portions.",v6.3_final_source_of_truth
SCR_0027,,,,,,,,,,ScriptoriumAI repo packet,ScriptoriumAI,ScriptoriumAI re-anchored VS Code packets v1,itshover/itshover,itshover/itshover,Implemented Pattern Source,P2,UI polish patterns used in scriptoriumai-ui/,"Audit itshover/itshover for ScriptoriumAI. Start from the reanchored bucket 'Implemented Pattern Source' and current reality status 'UI polish patterns used in scriptoriumai-ui/'. Confirm actual implemented capability, hidden reusable modules, extension seams, and whether it strengthens the existing Hover/interaction pattern source lane. Focus on: Inspect scene graph/canvas data model; layout primitives; component library; keyboard/gesture interactions; import/export schema; theming; plugin or extension hooks.","Component patterns (no direct npm dependency — clean-room implementation) ; Marketing shell, public pages visual design","Ground this repo in the actual ScriptoriumAI architecture rather than treating it as speculative. Preserve the current integration boundary (Component patterns (no direct npm dependency — clean-room implementation)) and audit for hidden reusable modules, extension points, and coupling risks. Existing powers: Marketing shell, public pages visual design.","Repurpose means extracting hidden internals, adapters, schemas, UI patterns, or subservices that strengthen the existing implemented surfaces without destabilizing the current product shell.",native/scriptoriumai-ui,excalidraw/excalidraw,jgraph/drawio,"Return concrete files/modules/adapters worth reusing and a verdict on whether the current reanchored bucket should be kept, upgraded, or downgraded.",Do not treat licensing as a filter. Do not propose replacing native foundations unless source evidence is overwhelming.,itshover/itshover,v6_unified_source_of_truth_pack,"Before recommending direct code use, inspect the target repo row in the v6.1 operational/phase/source-audit boards. Respect copyleft_strategy_v6_1, preferred_boundary_model_v6_1, and open_compliance_if_used_as_is_v6_1. Do not assume reverse engineering is mandatory or that as-is use is always sensible.","If the repo-level strategy says bounded_sidecar_preferred or boundary_first_then_decide_as_is_vs_reimplementation, audit clean interfaces, protocol seams, subprocess/container boundaries, and what would be required to reimplement only the strategically necessary portions.",v6.3_final_source_of_truth
SCR_0028,,,,,,,,,,ScriptoriumAI repo packet,ScriptoriumAI,ScriptoriumAI re-anchored VS Code packets v1,open-webui/open-webui,open-webui/open-webui,Implemented Pattern Source,P2,Pattern reference,"Audit open-webui/open-webui for ScriptoriumAI. Start from the reanchored bucket 'Implemented Pattern Source' and current reality status 'Pattern reference'. Confirm actual implemented capability, hidden reusable modules, extension seams, and whether it strengthens the existing Chat layout and conversational UI pattern lane. Focus on: Inspect hidden modules, extension seams, data contracts, rendering paths, auth/storage coupling, and export/import boundaries.",UI pattern inspiration only — no code imported ; Global Chat layout component,"Ground this repo in the actual ScriptoriumAI architecture rather than treating it as speculative. Preserve the current integration boundary (UI pattern inspiration only — no code imported) and audit for hidden reusable modules, extension points, and coupling risks. Existing powers: Global Chat layout component.","Repurpose means extracting hidden internals, adapters, schemas, UI patterns, or subservices that strengthen the existing implemented surfaces without destabilizing the current product shell.",native/ScriptoriumAI-Server,stanford-oval/storm,abhigyanpatwari/GitNexus,"Return concrete files/modules/adapters worth reusing and a verdict on whether the current reanchored bucket should be kept, upgraded, or downgraded.",Do not treat licensing as a filter. Do not propose replacing native foundations unless source evidence is overwhelming.,open-webui/open-webui,v6_unified_source_of_truth_pack,"Before recommending direct code use, inspect the target repo row in the v6.1 operational/phase/source-audit boards. Respect copyleft_strategy_v6_1, preferred_boundary_model_v6_1, and open_compliance_if_used_as_is_v6_1. Do not assume reverse engineering is mandatory or that as-is use is always sensible.","If the repo-level strategy says bounded_sidecar_preferred or boundary_first_then_decide_as_is_vs_reimplementation, audit clean interfaces, protocol seams, subprocess/container boundaries, and what would be required to reimplement only the strategically necessary portions.",v6.3_final_source_of_truth
SCR_0029,,,,,,,,,,ScriptoriumAI repo packet,ScriptoriumAI,ScriptoriumAI re-anchored VS Code packets v1,uidotdev/liquid-glass-react,uidotdev/liquid-glass-react,Implemented Pattern Source,P2,UI polish patterns used in scriptoriumai-ui/,"Audit uidotdev/liquid-glass-react for ScriptoriumAI. Start from the reanchored bucket 'Implemented Pattern Source' and current reality status 'UI polish patterns used in scriptoriumai-ui/'. Confirm actual implemented capability, hidden reusable modules, extension seams, and whether it strengthens the existing Visual design pattern source lane. Focus on: Inspect hidden modules, extension seams, data contracts, rendering paths, auth/storage coupling, and export/import boundaries.","Component patterns (no direct npm dependency — clean-room implementation) ; Marketing shell, public pages visual design","Ground this repo in the actual ScriptoriumAI architecture rather than treating it as speculative. Preserve the current integration boundary (Component patterns (no direct npm dependency — clean-room implementation)) and audit for hidden reusable modules, extension points, and coupling risks. Existing powers: Marketing shell, public pages visual design.","Repurpose means extracting hidden internals, adapters, schemas, UI patterns, or subservices that strengthen the existing implemented surfaces without destabilizing the current product shell.",native/scriptoriumai-ui,excalidraw/excalidraw,jgraph/drawio,"Return concrete files/modules/adapters worth reusing and a verdict on whether the current reanchored bucket should be kept, upgraded, or downgraded.",Do not treat licensing as a filter. Do not propose replacing native foundations unless source evidence is overwhelming.,uidotdev/liquid-glass-react,v6_unified_source_of_truth_pack,"Before recommending direct code use, inspect the target repo row in the v6.1 operational/phase/source-audit boards. Respect copyleft_strategy_v6_1, preferred_boundary_model_v6_1, and open_compliance_if_used_as_is_v6_1. Do not assume reverse engineering is mandatory or that as-is use is always sensible.","If the repo-level strategy says bounded_sidecar_preferred or boundary_first_then_decide_as_is_vs_reimplementation, audit clean interfaces, protocol seams, subprocess/container boundaries, and what would be required to reimplement only the strategically necessary portions.",v6.3_final_source_of_truth
SCR_0030,,,,,,,,,,ScriptoriumAI repo packet,ScriptoriumAI,ScriptoriumAI re-anchored VS Code packets v1,roovetgit/roo-code,roovetgit/roo-code,Implemented Pattern Source,P3,Pattern reference,"Audit roovetgit/roo-code for ScriptoriumAI. Start from the reanchored bucket 'Implemented Pattern Source' and current reality status 'Pattern reference'. Confirm actual implemented capability, hidden reusable modules, extension seams, and whether it strengthens the existing Coding-agent loop pattern source lane. Focus on: Inspect hidden modules, extension seams, data contracts, rendering paths, auth/storage coupling, and export/import boundaries.", ; Research Agent swarm loop design,"Ground this repo in the actual ScriptoriumAI architecture rather than treating it as speculative. Preserve the current integration boundary (see architecture snapshot) and audit for hidden reusable modules, extension points, and coupling risks. Existing powers: Research Agent swarm loop design.","Repurpose means extracting hidden internals, adapters, schemas, UI patterns, or subservices that strengthen the existing implemented surfaces without destabilizing the current product shell.",native/ScriptoriumAI-Server,stanford-oval/storm,abhigyanpatwari/GitNexus,"Return concrete files/modules/adapters worth reusing and a verdict on whether the current reanchored bucket should be kept, upgraded, or downgraded.",Do not treat licensing as a filter. Do not propose replacing native foundations unless source evidence is overwhelming.,roovetgit/roo-code,v6_unified_source_of_truth_pack,"Before recommending direct code use, inspect the target repo row in the v6.1 operational/phase/source-audit boards. Respect copyleft_strategy_v6_1, preferred_boundary_model_v6_1, and open_compliance_if_used_as_is_v6_1. Do not assume reverse engineering is mandatory or that as-is use is always sensible.","If the repo-level strategy says bounded_sidecar_preferred or boundary_first_then_decide_as_is_vs_reimplementation, audit clean interfaces, protocol seams, subprocess/container boundaries, and what would be required to reimplement only the strategically necessary portions.",v6.3_final_source_of_truth
SCR_0031,,,,,,,,,,ScriptoriumAI repo packet,ScriptoriumAI,ScriptoriumAI re-anchored VS Code packets v1,manim-resources/code2video,manim-resources/code2video,Donor Bench,P1,Production (server routes wired),"Audit manim-resources/code2video for ScriptoriumAI. Start from the reanchored bucket 'Donor Bench' and current reality status 'Production (server routes wired)'. Confirm actual implemented capability, hidden reusable modules, extension seams, and whether it strengthens the existing Implemented subsystem or surface lane. Focus on: Inspect hidden modules, extension seams, data contracts, rendering paths, auth/storage coupling, and export/import boundaries.","ScriptoriumAI-Server/routes/code2video.js, routes/paper2video.js, services/paper2video.js, services/code2video.js ; Video Studio paper-to-video export, Remotion render pipeline","Ground this repo in the actual ScriptoriumAI architecture rather than treating it as speculative. Preserve the current integration boundary (ScriptoriumAI-Server/routes/code2video.js, routes/paper2video.js, services/paper2video.js, services/code2video.js) and audit for hidden reusable modules, extension points, and coupling risks. Existing powers: Video Studio paper-to-video export, Remotion render pipeline.","Repurpose means extracting hidden internals, adapters, schemas, UI patterns, or subservices that strengthen the existing implemented surfaces without destabilizing the current product shell.",manimcommunity/manim,remotion-dev/remotion,native/ScriptoriumAI-Visualizer,"Return concrete files/modules/adapters worth reusing and a verdict on whether the current reanchored bucket should be kept, upgraded, or downgraded.",Do not treat licensing as a filter. Do not propose replacing native foundations unless source evidence is overwhelming.,manim-resources/code2video,v6_unified_source_of_truth_pack,"Before recommending direct code use, inspect the target repo row in the v6.1 operational/phase/source-audit boards. Respect copyleft_strategy_v6_1, preferred_boundary_model_v6_1, and open_compliance_if_used_as_is_v6_1. Do not assume reverse engineering is mandatory or that as-is use is always sensible.","If the repo-level strategy says bounded_sidecar_preferred or boundary_first_then_decide_as_is_vs_reimplementation, audit clean interfaces, protocol seams, subprocess/container boundaries, and what would be required to reimplement only the strategically necessary portions.",v6.3_final_source_of_truth
SCR_0032,,,,,,,,,,ScriptoriumAI repo packet,ScriptoriumAI,ScriptoriumAI re-anchored VS Code packets v1,manim-resources/paper2video,manim-resources/paper2video,Donor Bench,P1,Production (server routes wired),"Audit manim-resources/paper2video for ScriptoriumAI. Start from the reanchored bucket 'Donor Bench' and current reality status 'Production (server routes wired)'. Confirm actual implemented capability, hidden reusable modules, extension seams, and whether it strengthens the existing Implemented subsystem or surface lane. Focus on: Inspect hidden modules, extension seams, data contracts, rendering paths, auth/storage coupling, and export/import boundaries.","ScriptoriumAI-Server/routes/code2video.js, routes/paper2video.js, services/paper2video.js, services/code2video.js ; Video Studio paper-to-video export, Remotion render pipeline","Ground this repo in the actual ScriptoriumAI architecture rather than treating it as speculative. Preserve the current integration boundary (ScriptoriumAI-Server/routes/code2video.js, routes/paper2video.js, services/paper2video.js, services/code2video.js) and audit for hidden reusable modules, extension points, and coupling risks. Existing powers: Video Studio paper-to-video export, Remotion render pipeline.","Repurpose means extracting hidden internals, adapters, schemas, UI patterns, or subservices that strengthen the existing implemented surfaces without destabilizing the current product shell.",manimcommunity/manim,remotion-dev/remotion,native/ScriptoriumAI-Visualizer,"Return concrete files/modules/adapters worth reusing and a verdict on whether the current reanchored bucket should be kept, upgraded, or downgraded.",Do not treat licensing as a filter. Do not propose replacing native foundations unless source evidence is overwhelming.,manim-resources/paper2video,v6_unified_source_of_truth_pack,"Before recommending direct code use, inspect the target repo row in the v6.1 operational/phase/source-audit boards. Respect copyleft_strategy_v6_1, preferred_boundary_model_v6_1, and open_compliance_if_used_as_is_v6_1. Do not assume reverse engineering is mandatory or that as-is use is always sensible.","If the repo-level strategy says bounded_sidecar_preferred or boundary_first_then_decide_as_is_vs_reimplementation, audit clean interfaces, protocol seams, subprocess/container boundaries, and what would be required to reimplement only the strategically necessary portions.",v6.3_final_source_of_truth
SCR_0033,,,,,,,,,,ScriptoriumAI repo packet,ScriptoriumAI,ScriptoriumAI re-anchored VS Code packets v1,AMAP-ML/Code2World,amap-ml/code2world,Reserve Bench,P3,bookmark candidate only,"Audit AMAP-ML/Code2World for ScriptoriumAI. Start from the reanchored bucket 'Reserve Bench' and current reality status 'bookmark candidate only'. Confirm actual implemented capability, hidden reusable modules, extension seams, and whether it strengthens the existing Weak or ambiguous adjacent candidate lane. Focus on: Inspect parsers and language adapters; graph schema and storage; incremental indexing/update logic; layout engine; query API; export/import formats; test fixtures for graph correctness.","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.","Treat as unimplemented ScriptoriumAI candidate only. Do not let it redefine the current stack. Integrate only if a later audit proves it fills a real gap in the existing surfaces such as Dashboard, Editor, Corpus Graph, Runboard, AI Kanban, Corpus Search, Patch Review Queue, Visualizations, Whiteboard, Mind Map, PDF Intake, AI Diagram Studio, Video Studio, Research Agent, New Research Topic, Skills Manager, OpenAPI Routing, Manim Sandbox, Settings.","Repurpose here means mining for specific modules, algorithms, UI patterns, ingestion logic, workflow ideas, or export formats rather than assuming a full product transplant.",native/scriptoriumai-ui,native/ScriptoriumAI-Server,abhigyanpatwari/GitNexus,"Return concrete files/modules/adapters worth reusing and a verdict on whether the current reanchored bucket should be kept, upgraded, or downgraded.",Do not treat licensing as a filter. Do not propose replacing native foundations unless source evidence is overwhelming.,amap-ml/code2world,v6_unified_source_of_truth_pack,"Before recommending direct code use, inspect the target repo row in the v6.1 operational/phase/source-audit boards. Respect copyleft_strategy_v6_1, preferred_boundary_model_v6_1, and open_compliance_if_used_as_is_v6_1. Do not assume reverse engineering is mandatory or that as-is use is always sensible.","If the repo-level strategy says bounded_sidecar_preferred or boundary_first_then_decide_as_is_vs_reimplementation, audit clean interfaces, protocol seams, subprocess/container boundaries, and what would be required to reimplement only the strategically necessary portions.",v6.3_final_source_of_truth
SCR_0034,,,,,,,,,,ScriptoriumAI repo packet,ScriptoriumAI,ScriptoriumAI re-anchored VS Code packets v1,AUTOMATIC1111/stable-diffusion-webui,automatic1111/stable-diffusion-webui,Reserve Bench,P3,bookmark candidate only,"Audit AUTOMATIC1111/stable-diffusion-webui for ScriptoriumAI. Start from the reanchored bucket 'Reserve Bench' and current reality status 'bookmark candidate only'. Confirm actual implemented capability, hidden reusable modules, extension seams, and whether it strengthens the existing Weak or ambiguous adjacent candidate lane. Focus on: 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.","Treat as unimplemented ScriptoriumAI candidate only. Do not let it redefine the current stack. Integrate only if a later audit proves it fills a real gap in the existing surfaces such as Dashboard, Editor, Corpus Graph, Runboard, AI Kanban, Corpus Search, Patch Review Queue, Visualizations, Whiteboard, Mind Map, PDF Intake, AI Diagram Studio, Video Studio, Research Agent, New Research Topic, Skills Manager, OpenAPI Routing, Manim Sandbox, Settings.","Repurpose here means mining for specific modules, algorithms, UI patterns, ingestion logic, workflow ideas, or export formats rather than assuming a full product transplant.",native/scriptoriumai-ui,native/ScriptoriumAI-Server,abhigyanpatwari/GitNexus,"Return concrete files/modules/adapters worth reusing and a verdict on whether the current reanchored bucket should be kept, upgraded, or downgraded.",Do not treat licensing as a filter. Do not propose replacing native foundations unless source evidence is overwhelming.,automatic1111/stable-diffusion-webui,v6_unified_source_of_truth_pack,"Before recommending direct code use, inspect the target repo row in the v6.1 operational/phase/source-audit boards. Respect copyleft_strategy_v6_1, preferred_boundary_model_v6_1, and open_compliance_if_used_as_is_v6_1. Do not assume reverse engineering is mandatory or that as-is use is always sensible.","If the repo-level strategy says bounded_sidecar_preferred or boundary_first_then_decide_as_is_vs_reimplementation, audit clean interfaces, protocol seams, subprocess/container boundaries, and what would be required to reimplement only the strategically necessary portions.",v6.3_final_source_of_truth
SCR_0035,,,,,,,,,,ScriptoriumAI repo packet,ScriptoriumAI,ScriptoriumAI re-anchored VS Code packets v1,BIT-DataLab/Edit-Banana,bit-datalab/edit-banana,Reserve Bench,P3,bookmark candidate only,"Audit BIT-DataLab/Edit-Banana for ScriptoriumAI. Start from the reanchored bucket 'Reserve Bench' and current reality status 'bookmark candidate only'. Confirm actual implemented capability, hidden reusable modules, extension seams, and whether it strengthens the existing Weak or ambiguous adjacent candidate lane. Focus on: Inspect package/module map; entrypoints; config and schema files; adapters/integrations; persistence model; tests/examples; hidden feature flags; plugin 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 hidden admin tools, reusable services, plugin systems, import/export, analytics, background jobs, and any engine more valuable than the public README suggests.","Treat as unimplemented ScriptoriumAI candidate only. Do not let it redefine the current stack. Integrate only if a later audit proves it fills a real gap in the existing surfaces such as Dashboard, Editor, Corpus Graph, Runboard, AI Kanban, Corpus Search, Patch Review Queue, Visualizations, Whiteboard, Mind Map, PDF Intake, AI Diagram Studio, Video Studio, Research Agent, New Research Topic, Skills Manager, OpenAPI Routing, Manim Sandbox, Settings.","Repurpose here means mining for specific modules, algorithms, UI patterns, ingestion logic, workflow ideas, or export formats rather than assuming a full product transplant.",native/scriptoriumai-ui,native/ScriptoriumAI-Server,abhigyanpatwari/GitNexus,"Return concrete files/modules/adapters worth reusing and a verdict on whether the current reanchored bucket should be kept, upgraded, or downgraded.",Do not treat licensing as a filter. Do not propose replacing native foundations unless source evidence is overwhelming.,bit-datalab/edit-banana,v6_unified_source_of_truth_pack,"Before recommending direct code use, inspect the target repo row in the v6.1 operational/phase/source-audit boards. Respect copyleft_strategy_v6_1, preferred_boundary_model_v6_1, and open_compliance_if_used_as_is_v6_1. Do not assume reverse engineering is mandatory or that as-is use is always sensible.","If the repo-level strategy says bounded_sidecar_preferred or boundary_first_then_decide_as_is_vs_reimplementation, audit clean interfaces, protocol seams, subprocess/container boundaries, and what would be required to reimplement only the strategically necessary portions.",v6.3_final_source_of_truth
SCR_0036,,,,,,,,,,ScriptoriumAI repo packet,ScriptoriumAI,ScriptoriumAI re-anchored VS Code packets v1,Blaizzy/mlx-audio,blaizzy/mlx-audio,Reserve Bench,P3,bookmark candidate only,"Audit Blaizzy/mlx-audio for ScriptoriumAI. Start from the reanchored bucket 'Reserve Bench' and current reality status 'bookmark candidate only'. Confirm actual implemented capability, hidden reusable modules, extension seams, and whether it strengthens the existing Weak or ambiguous adjacent candidate lane. Focus on: 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.","Treat as unimplemented ScriptoriumAI candidate only. Do not let it redefine the current stack. Integrate only if a later audit proves it fills a real gap in the existing surfaces such as Dashboard, Editor, Corpus Graph, Runboard, AI Kanban, Corpus Search, Patch Review Queue, Visualizations, Whiteboard, Mind Map, PDF Intake, AI Diagram Studio, Video Studio, Research Agent, New Research Topic, Skills Manager, OpenAPI Routing, Manim Sandbox, Settings.","Repurpose here means mining for specific modules, algorithms, UI patterns, ingestion logic, workflow ideas, or export formats rather than assuming a full product transplant.",native/scriptoriumai-ui,native/ScriptoriumAI-Server,abhigyanpatwari/GitNexus,"Return concrete files/modules/adapters worth reusing and a verdict on whether the current reanchored bucket should be kept, upgraded, or downgraded.",Do not treat licensing as a filter. Do not propose replacing native foundations unless source evidence is overwhelming.,blaizzy/mlx-audio,v6_unified_source_of_truth_pack,"Before recommending direct code use, inspect the target repo row in the v6.1 operational/phase/source-audit boards. Respect copyleft_strategy_v6_1, preferred_boundary_model_v6_1, and open_compliance_if_used_as_is_v6_1. Do not assume reverse engineering is mandatory or that as-is use is always sensible.","If the repo-level strategy says bounded_sidecar_preferred or boundary_first_then_decide_as_is_vs_reimplementation, audit clean interfaces, protocol seams, subprocess/container boundaries, and what would be required to reimplement only the strategically necessary portions.",v6.3_final_source_of_truth
SCR_0037,,,,,,,,,,ScriptoriumAI repo packet,ScriptoriumAI,ScriptoriumAI re-anchored VS Code packets v1,CoderFoundry/BlazorRenderModes,coderfoundry/blazorrendermodes,Reserve Bench,P3,bookmark candidate only,"Audit CoderFoundry/BlazorRenderModes for ScriptoriumAI. Start from the reanchored bucket 'Reserve Bench' and current reality status 'bookmark candidate only'. Confirm actual implemented capability, hidden reusable modules, extension seams, and whether it strengthens the existing Weak or ambiguous adjacent candidate lane. Focus on: 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.","Treat as unimplemented ScriptoriumAI candidate only. Do not let it redefine the current stack. Integrate only if a later audit proves it fills a real gap in the existing surfaces such as Dashboard, Editor, Corpus Graph, Runboard, AI Kanban, Corpus Search, Patch Review Queue, Visualizations, Whiteboard, Mind Map, PDF Intake, AI Diagram Studio, Video Studio, Research Agent, New Research Topic, Skills Manager, OpenAPI Routing, Manim Sandbox, Settings.","Repurpose here means mining for specific modules, algorithms, UI patterns, ingestion logic, workflow ideas, or export formats rather than assuming a full product transplant.",native/scriptoriumai-ui,native/ScriptoriumAI-Server,abhigyanpatwari/GitNexus,"Return concrete files/modules/adapters worth reusing and a verdict on whether the current reanchored bucket should be kept, upgraded, or downgraded.",Do not treat licensing as a filter. Do not propose replacing native foundations unless source evidence is overwhelming.,coderfoundry/blazorrendermodes,v6_unified_source_of_truth_pack,"Before recommending direct code use, inspect the target repo row in the v6.1 operational/phase/source-audit boards. Respect copyleft_strategy_v6_1, preferred_boundary_model_v6_1, and open_compliance_if_used_as_is_v6_1. Do not assume reverse engineering is mandatory or that as-is use is always sensible.","If the repo-level strategy says bounded_sidecar_preferred or boundary_first_then_decide_as_is_vs_reimplementation, audit clean interfaces, protocol seams, subprocess/container boundaries, and what would be required to reimplement only the strategically necessary portions.",v6.3_final_source_of_truth
SCR_0038,,,,,,,,,,ScriptoriumAI repo packet,ScriptoriumAI,ScriptoriumAI re-anchored VS Code packets v1,D4Vinci/Scrapling,d4vinci/scrapling,Reserve Bench,P3,bookmark candidate only,"Audit D4Vinci/Scrapling for ScriptoriumAI. Start from the reanchored bucket 'Reserve Bench' and current reality status 'bookmark candidate only'. Confirm actual implemented capability, hidden reusable modules, extension seams, and whether it strengthens the existing Weak or ambiguous adjacent candidate lane. Focus on: 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 event schemas, ingestion pipelines, queue/job workers, service adapters, deployment/runtime config, RBAC/auth, alerting, and API contract generators.","Treat as unimplemented ScriptoriumAI candidate only. Do not let it redefine the current stack. Integrate only if a later audit proves it fills a real gap in the existing surfaces such as Dashboard, Editor, Corpus Graph, Runboard, AI Kanban, Corpus Search, Patch Review Queue, Visualizations, Whiteboard, Mind Map, PDF Intake, AI Diagram Studio, Video Studio, Research Agent, New Research Topic, Skills Manager, OpenAPI Routing, Manim Sandbox, Settings.","Repurpose here means mining for specific modules, algorithms, UI patterns, ingestion logic, workflow ideas, or export formats rather than assuming a full product transplant.",native/scriptoriumai-ui,native/ScriptoriumAI-Server,abhigyanpatwari/GitNexus,"Return concrete files/modules/adapters worth reusing and a verdict on whether the current reanchored bucket should be kept, upgraded, or downgraded.",Do not treat licensing as a filter. Do not propose replacing native foundations unless source evidence is overwhelming.,d4vinci/scrapling,v6_unified_source_of_truth_pack,"Before recommending direct code use, inspect the target repo row in the v6.1 operational/phase/source-audit boards. Respect copyleft_strategy_v6_1, preferred_boundary_model_v6_1, and open_compliance_if_used_as_is_v6_1. Do not assume reverse engineering is mandatory or that as-is use is always sensible.","If the repo-level strategy says bounded_sidecar_preferred or boundary_first_then_decide_as_is_vs_reimplementation, audit clean interfaces, protocol seams, subprocess/container boundaries, and what would be required to reimplement only the strategically necessary portions.",v6.3_final_source_of_truth
SCR_0039,,,,,,,,,,ScriptoriumAI repo packet,ScriptoriumAI,ScriptoriumAI re-anchored VS Code packets v1,David20321/ProjectGibbon,david20321/projectgibbon,Reserve Bench,P3,bookmark candidate only,"Audit David20321/ProjectGibbon for ScriptoriumAI. Start from the reanchored bucket 'Reserve Bench' and current reality status 'bookmark candidate only'. Confirm actual implemented capability, hidden reusable modules, extension seams, and whether it strengthens the existing Weak or ambiguous adjacent candidate lane. Focus on: Inspect package/module map; entrypoints; config and schema files; adapters/integrations; persistence model; tests/examples; hidden feature flags; plugin 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 hidden admin tools, reusable services, plugin systems, import/export, analytics, background jobs, and any engine more valuable than the public README suggests.","Treat as unimplemented ScriptoriumAI candidate only. Do not let it redefine the current stack. Integrate only if a later audit proves it fills a real gap in the existing surfaces such as Dashboard, Editor, Corpus Graph, Runboard, AI Kanban, Corpus Search, Patch Review Queue, Visualizations, Whiteboard, Mind Map, PDF Intake, AI Diagram Studio, Video Studio, Research Agent, New Research Topic, Skills Manager, OpenAPI Routing, Manim Sandbox, Settings.","Repurpose here means mining for specific modules, algorithms, UI patterns, ingestion logic, workflow ideas, or export formats rather than assuming a full product transplant.",native/scriptoriumai-ui,native/ScriptoriumAI-Server,abhigyanpatwari/GitNexus,"Return concrete files/modules/adapters worth reusing and a verdict on whether the current reanchored bucket should be kept, upgraded, or downgraded.",Do not treat licensing as a filter. Do not propose replacing native foundations unless source evidence is overwhelming.,david20321/projectgibbon,v6_unified_source_of_truth_pack,"Before recommending direct code use, inspect the target repo row in the v6.1 operational/phase/source-audit boards. Respect copyleft_strategy_v6_1, preferred_boundary_model_v6_1, and open_compliance_if_used_as_is_v6_1. Do not assume reverse engineering is mandatory or that as-is use is always sensible.","If the repo-level strategy says bounded_sidecar_preferred or boundary_first_then_decide_as_is_vs_reimplementation, audit clean interfaces, protocol seams, subprocess/container boundaries, and what would be required to reimplement only the strategically necessary portions.",v6.3_final_source_of_truth
SCR_0040,,,,,,,,,,ScriptoriumAI repo packet,ScriptoriumAI,ScriptoriumAI re-anchored VS Code packets v1,Fody/Fody,fody/fody,Reserve Bench,P3,bookmark candidate only,"Audit Fody/Fody for ScriptoriumAI. Start from the reanchored bucket 'Reserve Bench' and current reality status 'bookmark candidate only'. Confirm actual implemented capability, hidden reusable modules, extension seams, and whether it strengthens the existing Weak or ambiguous adjacent candidate lane. Focus on: Inspect package/module map; entrypoints; config and schema files; adapters/integrations; persistence model; tests/examples; hidden feature flags; plugin 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 hidden admin tools, reusable services, plugin systems, import/export, analytics, background jobs, and any engine more valuable than the public README suggests.","Treat as unimplemented ScriptoriumAI candidate only. Do not let it redefine the current stack. Integrate only if a later audit proves it fills a real gap in the existing surfaces such as Dashboard, Editor, Corpus Graph, Runboard, AI Kanban, Corpus Search, Patch Review Queue, Visualizations, Whiteboard, Mind Map, PDF Intake, AI Diagram Studio, Video Studio, Research Agent, New Research Topic, Skills Manager, OpenAPI Routing, Manim Sandbox, Settings.","Repurpose here means mining for specific modules, algorithms, UI patterns, ingestion logic, workflow ideas, or export formats rather than assuming a full product transplant.",native/scriptoriumai-ui,native/ScriptoriumAI-Server,abhigyanpatwari/GitNexus,"Return concrete files/modules/adapters worth reusing and a verdict on whether the current reanchored bucket should be kept, upgraded, or downgraded.",Do not treat licensing as a filter. Do not propose replacing native foundations unless source evidence is overwhelming.,fody/fody,v6_unified_source_of_truth_pack,"Before recommending direct code use, inspect the target repo row in the v6.1 operational/phase/source-audit boards. Respect copyleft_strategy_v6_1, preferred_boundary_model_v6_1, and open_compliance_if_used_as_is_v6_1. Do not assume reverse engineering is mandatory or that as-is use is always sensible.","If the repo-level strategy says bounded_sidecar_preferred or boundary_first_then_decide_as_is_vs_reimplementation, audit clean interfaces, protocol seams, subprocess/container boundaries, and what would be required to reimplement only the strategically necessary portions.",v6.3_final_source_of_truth
SCR_0041,,,,,,,,,,ScriptoriumAI repo packet,ScriptoriumAI,ScriptoriumAI re-anchored VS Code packets v1,JimmyLv/awesome-nano-banana,jimmylv/awesome-nano-banana,Reserve Bench,P3,bookmark candidate only,"Audit JimmyLv/awesome-nano-banana for ScriptoriumAI. Start from the reanchored bucket 'Reserve Bench' and current reality status 'bookmark candidate only'. Confirm actual implemented capability, hidden reusable modules, extension seams, and whether it strengthens the existing Weak or ambiguous adjacent candidate lane. Focus on: 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 calibration routines, detection heuristics/models, color/state normalization, replay serialization, solver bridges, camera abstraction layers, and debug visualizations.","Treat as unimplemented ScriptoriumAI candidate only. Do not let it redefine the current stack. Integrate only if a later audit proves it fills a real gap in the existing surfaces such as Dashboard, Editor, Corpus Graph, Runboard, AI Kanban, Corpus Search, Patch Review Queue, Visualizations, Whiteboard, Mind Map, PDF Intake, AI Diagram Studio, Video Studio, Research Agent, New Research Topic, Skills Manager, OpenAPI Routing, Manim Sandbox, Settings.","Repurpose here means mining for specific modules, algorithms, UI patterns, ingestion logic, workflow ideas, or export formats rather than assuming a full product transplant.",native/scriptoriumai-ui,native/ScriptoriumAI-Server,abhigyanpatwari/GitNexus,"Return concrete files/modules/adapters worth reusing and a verdict on whether the current reanchored bucket should be kept, upgraded, or downgraded.",Do not treat licensing as a filter. Do not propose replacing native foundations unless source evidence is overwhelming.,jimmylv/awesome-nano-banana,v6_unified_source_of_truth_pack,"Before recommending direct code use, inspect the target repo row in the v6.1 operational/phase/source-audit boards. Respect copyleft_strategy_v6_1, preferred_boundary_model_v6_1, and open_compliance_if_used_as_is_v6_1. Do not assume reverse engineering is mandatory or that as-is use is always sensible.","If the repo-level strategy says bounded_sidecar_preferred or boundary_first_then_decide_as_is_vs_reimplementation, audit clean interfaces, protocol seams, subprocess/container boundaries, and what would be required to reimplement only the strategically necessary portions.",v6.3_final_source_of_truth
SCR_0042,,,,,,,,,,ScriptoriumAI repo packet,ScriptoriumAI,ScriptoriumAI re-anchored VS Code packets v1,KOSASIH/SynthAI,kosasih/synthai,Reserve Bench,P3,bookmark candidate only,"Audit KOSASIH/SynthAI for ScriptoriumAI. Start from the reanchored bucket 'Reserve Bench' and current reality status 'bookmark candidate only'. Confirm actual implemented capability, hidden reusable modules, extension seams, and whether it strengthens the existing Weak or ambiguous adjacent candidate lane. Focus on: Inspect package/module map; entrypoints; config and schema files; adapters/integrations; persistence model; tests/examples; hidden feature flags; plugin 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 hidden admin tools, reusable services, plugin systems, import/export, analytics, background jobs, and any engine more valuable than the public README suggests.","Treat as unimplemented ScriptoriumAI candidate only. Do not let it redefine the current stack. Integrate only if a later audit proves it fills a real gap in the existing surfaces such as Dashboard, Editor, Corpus Graph, Runboard, AI Kanban, Corpus Search, Patch Review Queue, Visualizations, Whiteboard, Mind Map, PDF Intake, AI Diagram Studio, Video Studio, Research Agent, New Research Topic, Skills Manager, OpenAPI Routing, Manim Sandbox, Settings.","Repurpose here means mining for specific modules, algorithms, UI patterns, ingestion logic, workflow ideas, or export formats rather than assuming a full product transplant.",native/scriptoriumai-ui,native/ScriptoriumAI-Server,abhigyanpatwari/GitNexus,"Return concrete files/modules/adapters worth reusing and a verdict on whether the current reanchored bucket should be kept, upgraded, or downgraded.",Do not treat licensing as a filter. Do not propose replacing native foundations unless source evidence is overwhelming.,kosasih/synthai,v6_unified_source_of_truth_pack,"Before recommending direct code use, inspect the target repo row in the v6.1 operational/phase/source-audit boards. Respect copyleft_strategy_v6_1, preferred_boundary_model_v6_1, and open_compliance_if_used_as_is_v6_1. Do not assume reverse engineering is mandatory or that as-is use is always sensible.","If the repo-level strategy says bounded_sidecar_preferred or boundary_first_then_decide_as_is_vs_reimplementation, audit clean interfaces, protocol seams, subprocess/container boundaries, and what would be required to reimplement only the strategically necessary portions.",v6.3_final_source_of_truth
SCR_0043,,,,,,,,,,ScriptoriumAI repo packet,ScriptoriumAI,ScriptoriumAI re-anchored VS Code packets v1,Levak/warfacebot,levak/warfacebot,Reserve Bench,P3,bookmark candidate only,"Audit Levak/warfacebot for ScriptoriumAI. Start from the reanchored bucket 'Reserve Bench' and current reality status 'bookmark candidate only'. Confirm actual implemented capability, hidden reusable modules, extension seams, and whether it strengthens the existing Weak or ambiguous adjacent candidate lane. Focus on: Inspect package/module map; entrypoints; config and schema files; adapters/integrations; persistence model; tests/examples; hidden feature flags; plugin 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 hidden admin tools, reusable services, plugin systems, import/export, analytics, background jobs, and any engine more valuable than the public README suggests.","Treat as unimplemented ScriptoriumAI candidate only. Do not let it redefine the current stack. Integrate only if a later audit proves it fills a real gap in the existing surfaces such as Dashboard, Editor, Corpus Graph, Runboard, AI Kanban, Corpus Search, Patch Review Queue, Visualizations, Whiteboard, Mind Map, PDF Intake, AI Diagram Studio, Video Studio, Research Agent, New Research Topic, Skills Manager, OpenAPI Routing, Manim Sandbox, Settings.","Repurpose here means mining for specific modules, algorithms, UI patterns, ingestion logic, workflow ideas, or export formats rather than assuming a full product transplant.",native/scriptoriumai-ui,native/ScriptoriumAI-Server,abhigyanpatwari/GitNexus,"Return concrete files/modules/adapters worth reusing and a verdict on whether the current reanchored bucket should be kept, upgraded, or downgraded.",Do not treat licensing as a filter. Do not propose replacing native foundations unless source evidence is overwhelming.,levak/warfacebot,v6_unified_source_of_truth_pack,"Before recommending direct code use, inspect the target repo row in the v6.1 operational/phase/source-audit boards. Respect copyleft_strategy_v6_1, preferred_boundary_model_v6_1, and open_compliance_if_used_as_is_v6_1. Do not assume reverse engineering is mandatory or that as-is use is always sensible.","If the repo-level strategy says bounded_sidecar_preferred or boundary_first_then_decide_as_is_vs_reimplementation, audit clean interfaces, protocol seams, subprocess/container boundaries, and what would be required to reimplement only the strategically necessary portions.",v6.3_final_source_of_truth
SCR_0044,,,,,,,,,,ScriptoriumAI repo packet,ScriptoriumAI,ScriptoriumAI re-anchored VS Code packets v1,Nasller/CodeGlancePro,nasller/codeglancepro,Reserve Bench,P3,bookmark candidate only,"Audit Nasller/CodeGlancePro for ScriptoriumAI. Start from the reanchored bucket 'Reserve Bench' and current reality status 'bookmark candidate only'. Confirm actual implemented capability, hidden reusable modules, extension seams, and whether it strengthens the existing Weak or ambiguous adjacent candidate lane. Focus on: Inspect package/module map; entrypoints; config and schema files; adapters/integrations; persistence model; tests/examples; hidden feature flags; plugin 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 hidden admin tools, reusable services, plugin systems, import/export, analytics, background jobs, and any engine more valuable than the public README suggests.","Treat as unimplemented ScriptoriumAI candidate only. Do not let it redefine the current stack. Integrate only if a later audit proves it fills a real gap in the existing surfaces such as Dashboard, Editor, Corpus Graph, Runboard, AI Kanban, Corpus Search, Patch Review Queue, Visualizations, Whiteboard, Mind Map, PDF Intake, AI Diagram Studio, Video Studio, Research Agent, New Research Topic, Skills Manager, OpenAPI Routing, Manim Sandbox, Settings.","Repurpose here means mining for specific modules, algorithms, UI patterns, ingestion logic, workflow ideas, or export formats rather than assuming a full product transplant.",native/scriptoriumai-ui,native/ScriptoriumAI-Server,abhigyanpatwari/GitNexus,"Return concrete files/modules/adapters worth reusing and a verdict on whether the current reanchored bucket should be kept, upgraded, or downgraded.",Do not treat licensing as a filter. Do not propose replacing native foundations unless source evidence is overwhelming.,nasller/codeglancepro,v6_unified_source_of_truth_pack,"Before recommending direct code use, inspect the target repo row in the v6.1 operational/phase/source-audit boards. Respect copyleft_strategy_v6_1, preferred_boundary_model_v6_1, and open_compliance_if_used_as_is_v6_1. Do not assume reverse engineering is mandatory or that as-is use is always sensible.","If the repo-level strategy says bounded_sidecar_preferred or boundary_first_then_decide_as_is_vs_reimplementation, audit clean interfaces, protocol seams, subprocess/container boundaries, and what would be required to reimplement only the strategically necessary portions.",v6.3_final_source_of_truth
SCR_0045,,,,,,,,,,ScriptoriumAI repo packet,ScriptoriumAI,ScriptoriumAI re-anchored VS Code packets v1,Paidax01/math-curve-loaders,paidax01/math-curve-loaders,Reserve Bench,P3,bookmark candidate only,"Audit Paidax01/math-curve-loaders for ScriptoriumAI. Start from the reanchored bucket 'Reserve Bench' and current reality status 'bookmark candidate only'. Confirm actual implemented capability, hidden reusable modules, extension seams, and whether it strengthens the existing Weak or ambiguous adjacent candidate lane. Focus on: 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.","Treat as unimplemented ScriptoriumAI candidate only. Do not let it redefine the current stack. Integrate only if a later audit proves it fills a real gap in the existing surfaces such as Dashboard, Editor, Corpus Graph, Runboard, AI Kanban, Corpus Search, Patch Review Queue, Visualizations, Whiteboard, Mind Map, PDF Intake, AI Diagram Studio, Video Studio, Research Agent, New Research Topic, Skills Manager, OpenAPI Routing, Manim Sandbox, Settings.","Repurpose here means mining for specific modules, algorithms, UI patterns, ingestion logic, workflow ideas, or export formats rather than assuming a full product transplant.",native/scriptoriumai-ui,native/ScriptoriumAI-Server,abhigyanpatwari/GitNexus,"Return concrete files/modules/adapters worth reusing and a verdict on whether the current reanchored bucket should be kept, upgraded, or downgraded.",Do not treat licensing as a filter. Do not propose replacing native foundations unless source evidence is overwhelming.,paidax01/math-curve-loaders,v6_unified_source_of_truth_pack,"Before recommending direct code use, inspect the target repo row in the v6.1 operational/phase/source-audit boards. Respect copyleft_strategy_v6_1, preferred_boundary_model_v6_1, and open_compliance_if_used_as_is_v6_1. Do not assume reverse engineering is mandatory or that as-is use is always sensible.","If the repo-level strategy says bounded_sidecar_preferred or boundary_first_then_decide_as_is_vs_reimplementation, audit clean interfaces, protocol seams, subprocess/container boundaries, and what would be required to reimplement only the strategically necessary portions.",v6.3_final_source_of_truth
SCR_0046,,,,,,,,,,ScriptoriumAI repo packet,ScriptoriumAI,ScriptoriumAI re-anchored VS Code packets v1,ParthJadhav/ios-marketing-capture,parthjadhav/ios-marketing-capture,Reserve Bench,P3,bookmark candidate only,"Audit ParthJadhav/ios-marketing-capture for ScriptoriumAI. Start from the reanchored bucket 'Reserve Bench' and current reality status 'bookmark candidate only'. Confirm actual implemented capability, hidden reusable modules, extension seams, and whether it strengthens the existing Weak or ambiguous adjacent candidate lane. Focus on: Inspect package/module map; entrypoints; config and schema files; adapters/integrations; persistence model; tests/examples; hidden feature flags; plugin 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 hidden admin tools, reusable services, plugin systems, import/export, analytics, background jobs, and any engine more valuable than the public README suggests.","Treat as unimplemented ScriptoriumAI candidate only. Do not let it redefine the current stack. Integrate only if a later audit proves it fills a real gap in the existing surfaces such as Dashboard, Editor, Corpus Graph, Runboard, AI Kanban, Corpus Search, Patch Review Queue, Visualizations, Whiteboard, Mind Map, PDF Intake, AI Diagram Studio, Video Studio, Research Agent, New Research Topic, Skills Manager, OpenAPI Routing, Manim Sandbox, Settings.","Repurpose here means mining for specific modules, algorithms, UI patterns, ingestion logic, workflow ideas, or export formats rather than assuming a full product transplant.",native/scriptoriumai-ui,native/ScriptoriumAI-Server,abhigyanpatwari/GitNexus,"Return concrete files/modules/adapters worth reusing and a verdict on whether the current reanchored bucket should be kept, upgraded, or downgraded.",Do not treat licensing as a filter. Do not propose replacing native foundations unless source evidence is overwhelming.,parthjadhav/ios-marketing-capture,v6_unified_source_of_truth_pack,"Before recommending direct code use, inspect the target repo row in the v6.1 operational/phase/source-audit boards. Respect copyleft_strategy_v6_1, preferred_boundary_model_v6_1, and open_compliance_if_used_as_is_v6_1. Do not assume reverse engineering is mandatory or that as-is use is always sensible.","If the repo-level strategy says bounded_sidecar_preferred or boundary_first_then_decide_as_is_vs_reimplementation, audit clean interfaces, protocol seams, subprocess/container boundaries, and what would be required to reimplement only the strategically necessary portions.",v6.3_final_source_of_truth
SCR_0047,,,,,,,,,,ScriptoriumAI repo packet,ScriptoriumAI,ScriptoriumAI re-anchored VS Code packets v1,TimeWarpEngineering/timewarp-state,timewarpengineering/timewarp-state,Reserve Bench,P3,bookmark candidate only,"Audit TimeWarpEngineering/timewarp-state for ScriptoriumAI. Start from the reanchored bucket 'Reserve Bench' and current reality status 'bookmark candidate only'. Confirm actual implemented capability, hidden reusable modules, extension seams, and whether it strengthens the existing Weak or ambiguous adjacent candidate lane. Focus on: 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.","Treat as unimplemented ScriptoriumAI candidate only. Do not let it redefine the current stack. Integrate only if a later audit proves it fills a real gap in the existing surfaces such as Dashboard, Editor, Corpus Graph, Runboard, AI Kanban, Corpus Search, Patch Review Queue, Visualizations, Whiteboard, Mind Map, PDF Intake, AI Diagram Studio, Video Studio, Research Agent, New Research Topic, Skills Manager, OpenAPI Routing, Manim Sandbox, Settings.","Repurpose here means mining for specific modules, algorithms, UI patterns, ingestion logic, workflow ideas, or export formats rather than assuming a full product transplant.",native/scriptoriumai-ui,native/ScriptoriumAI-Server,abhigyanpatwari/GitNexus,"Return concrete files/modules/adapters worth reusing and a verdict on whether the current reanchored bucket should be kept, upgraded, or downgraded.",Do not treat licensing as a filter. Do not propose replacing native foundations unless source evidence is overwhelming.,timewarpengineering/timewarp-state,v6_unified_source_of_truth_pack,"Before recommending direct code use, inspect the target repo row in the v6.1 operational/phase/source-audit boards. Respect copyleft_strategy_v6_1, preferred_boundary_model_v6_1, and open_compliance_if_used_as_is_v6_1. Do not assume reverse engineering is mandatory or that as-is use is always sensible.","If the repo-level strategy says bounded_sidecar_preferred or boundary_first_then_decide_as_is_vs_reimplementation, audit clean interfaces, protocol seams, subprocess/container boundaries, and what would be required to reimplement only the strategically necessary portions.",v6.3_final_source_of_truth
SCR_0048,,,,,,,,,,ScriptoriumAI repo packet,ScriptoriumAI,ScriptoriumAI re-anchored VS Code packets v1,VulcanWM/saasheaven,vulcanwm/saasheaven,Reserve Bench,P3,bookmark candidate only,"Audit VulcanWM/saasheaven for ScriptoriumAI. Start from the reanchored bucket 'Reserve Bench' and current reality status 'bookmark candidate only'. Confirm actual implemented capability, hidden reusable modules, extension seams, and whether it strengthens the existing Weak or ambiguous adjacent candidate lane. Focus on: 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.","Treat as unimplemented ScriptoriumAI candidate only. Do not let it redefine the current stack. Integrate only if a later audit proves it fills a real gap in the existing surfaces such as Dashboard, Editor, Corpus Graph, Runboard, AI Kanban, Corpus Search, Patch Review Queue, Visualizations, Whiteboard, Mind Map, PDF Intake, AI Diagram Studio, Video Studio, Research Agent, New Research Topic, Skills Manager, OpenAPI Routing, Manim Sandbox, Settings.","Repurpose here means mining for specific modules, algorithms, UI patterns, ingestion logic, workflow ideas, or export formats rather than assuming a full product transplant.",native/scriptoriumai-ui,native/ScriptoriumAI-Server,abhigyanpatwari/GitNexus,"Return concrete files/modules/adapters worth reusing and a verdict on whether the current reanchored bucket should be kept, upgraded, or downgraded.",Do not treat licensing as a filter. Do not propose replacing native foundations unless source evidence is overwhelming.,vulcanwm/saasheaven,v6_unified_source_of_truth_pack,"Before recommending direct code use, inspect the target repo row in the v6.1 operational/phase/source-audit boards. Respect copyleft_strategy_v6_1, preferred_boundary_model_v6_1, and open_compliance_if_used_as_is_v6_1. Do not assume reverse engineering is mandatory or that as-is use is always sensible.","If the repo-level strategy says bounded_sidecar_preferred or boundary_first_then_decide_as_is_vs_reimplementation, audit clean interfaces, protocol seams, subprocess/container boundaries, and what would be required to reimplement only the strategically necessary portions.",v6.3_final_source_of_truth
SCR_0049,,,,,,,,,,ScriptoriumAI repo packet,ScriptoriumAI,ScriptoriumAI re-anchored VS Code packets v1,YUZU-Hub/appscreen,yuzu-hub/appscreen,Reserve Bench,P3,bookmark candidate only,"Audit YUZU-Hub/appscreen for ScriptoriumAI. Start from the reanchored bucket 'Reserve Bench' and current reality status 'bookmark candidate only'. Confirm actual implemented capability, hidden reusable modules, extension seams, and whether it strengthens the existing Weak or ambiguous adjacent candidate lane. Focus on: Inspect package/module map; entrypoints; config and schema files; adapters/integrations; persistence model; tests/examples; hidden feature flags; plugin 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 hidden admin tools, reusable services, plugin systems, import/export, analytics, background jobs, and any engine more valuable than the public README suggests.","Treat as unimplemented ScriptoriumAI candidate only. Do not let it redefine the current stack. Integrate only if a later audit proves it fills a real gap in the existing surfaces such as Dashboard, Editor, Corpus Graph, Runboard, AI Kanban, Corpus Search, Patch Review Queue, Visualizations, Whiteboard, Mind Map, PDF Intake, AI Diagram Studio, Video Studio, Research Agent, New Research Topic, Skills Manager, OpenAPI Routing, Manim Sandbox, Settings.","Repurpose here means mining for specific modules, algorithms, UI patterns, ingestion logic, workflow ideas, or export formats rather than assuming a full product transplant.",native/scriptoriumai-ui,native/ScriptoriumAI-Server,abhigyanpatwari/GitNexus,"Return concrete files/modules/adapters worth reusing and a verdict on whether the current reanchored bucket should be kept, upgraded, or downgraded.",Do not treat licensing as a filter. Do not propose replacing native foundations unless source evidence is overwhelming.,yuzu-hub/appscreen,v6_unified_source_of_truth_pack,"Before recommending direct code use, inspect the target repo row in the v6.1 operational/phase/source-audit boards. Respect copyleft_strategy_v6_1, preferred_boundary_model_v6_1, and open_compliance_if_used_as_is_v6_1. Do not assume reverse engineering is mandatory or that as-is use is always sensible.","If the repo-level strategy says bounded_sidecar_preferred or boundary_first_then_decide_as_is_vs_reimplementation, audit clean interfaces, protocol seams, subprocess/container boundaries, and what would be required to reimplement only the strategically necessary portions.",v6.3_final_source_of_truth
SCR_0050,,,,,,,,,,ScriptoriumAI repo packet,ScriptoriumAI,ScriptoriumAI re-anchored VS Code packets v1,ZeroLu/awesome-nanobanana-pro,zerolu/awesome-nanobanana-pro,Reserve Bench,P3,bookmark candidate only,"Audit ZeroLu/awesome-nanobanana-pro for ScriptoriumAI. Start from the reanchored bucket 'Reserve Bench' and current reality status 'bookmark candidate only'. Confirm actual implemented capability, hidden reusable modules, extension seams, and whether it strengthens the existing Weak or ambiguous adjacent candidate lane. Focus on: 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.","Treat as unimplemented ScriptoriumAI candidate only. Do not let it redefine the current stack. Integrate only if a later audit proves it fills a real gap in the existing surfaces such as Dashboard, Editor, Corpus Graph, Runboard, AI Kanban, Corpus Search, Patch Review Queue, Visualizations, Whiteboard, Mind Map, PDF Intake, AI Diagram Studio, Video Studio, Research Agent, New Research Topic, Skills Manager, OpenAPI Routing, Manim Sandbox, Settings.","Repurpose here means mining for specific modules, algorithms, UI patterns, ingestion logic, workflow ideas, or export formats rather than assuming a full product transplant.",native/scriptoriumai-ui,native/ScriptoriumAI-Server,abhigyanpatwari/GitNexus,"Return concrete files/modules/adapters worth reusing and a verdict on whether the current reanchored bucket should be kept, upgraded, or downgraded.",Do not treat licensing as a filter. Do not propose replacing native foundations unless source evidence is overwhelming.,zerolu/awesome-nanobanana-pro,v6_unified_source_of_truth_pack,"Before recommending direct code use, inspect the target repo row in the v6.1 operational/phase/source-audit boards. Respect copyleft_strategy_v6_1, preferred_boundary_model_v6_1, and open_compliance_if_used_as_is_v6_1. Do not assume reverse engineering is mandatory or that as-is use is always sensible.","If the repo-level strategy says bounded_sidecar_preferred or boundary_first_then_decide_as_is_vs_reimplementation, audit clean interfaces, protocol seams, subprocess/container boundaries, and what would be required to reimplement only the strategically necessary portions.",v6.3_final_source_of_truth
SCR_0051,,,,,,,,,,ScriptoriumAI repo packet,ScriptoriumAI,ScriptoriumAI re-anchored VS Code packets v1,alorak/csvx,alorak/csvx,Reserve Bench,P3,bookmark candidate only,"Audit alorak/csvx for ScriptoriumAI. Start from the reanchored bucket 'Reserve Bench' and current reality status 'bookmark candidate only'. Confirm actual implemented capability, hidden reusable modules, extension seams, and whether it strengthens the existing Weak or ambiguous adjacent candidate lane. Focus on: Inspect parsers and language adapters; graph schema and storage; incremental indexing/update logic; layout engine; query API; export/import formats; test fixtures for graph correctness.","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.","Treat as unimplemented ScriptoriumAI candidate only. Do not let it redefine the current stack. Integrate only if a later audit proves it fills a real gap in the existing surfaces such as Dashboard, Editor, Corpus Graph, Runboard, AI Kanban, Corpus Search, Patch Review Queue, Visualizations, Whiteboard, Mind Map, PDF Intake, AI Diagram Studio, Video Studio, Research Agent, New Research Topic, Skills Manager, OpenAPI Routing, Manim Sandbox, Settings.","Repurpose here means mining for specific modules, algorithms, UI patterns, ingestion logic, workflow ideas, or export formats rather than assuming a full product transplant.",native/scriptoriumai-ui,native/ScriptoriumAI-Server,sharelatex/sharelatex,"Return concrete files/modules/adapters worth reusing and a verdict on whether the current reanchored bucket should be kept, upgraded, or downgraded.",Do not treat licensing as a filter. Do not propose replacing native foundations unless source evidence is overwhelming.,alorak/csvx,v6_unified_source_of_truth_pack,"Before recommending direct code use, inspect the target repo row in the v6.1 operational/phase/source-audit boards. Respect copyleft_strategy_v6_1, preferred_boundary_model_v6_1, and open_compliance_if_used_as_is_v6_1. Do not assume reverse engineering is mandatory or that as-is use is always sensible.","If the repo-level strategy says bounded_sidecar_preferred or boundary_first_then_decide_as_is_vs_reimplementation, audit clean interfaces, protocol seams, subprocess/container boundaries, and what would be required to reimplement only the strategically necessary portions.",v6.3_final_source_of_truth
SCR_0052,,,,,,,,,,ScriptoriumAI repo packet,ScriptoriumAI,ScriptoriumAI re-anchored VS Code packets v1,amicalhq/refref,amicalhq/refref,Reserve Bench,P3,bookmark candidate only,"Audit amicalhq/refref for ScriptoriumAI. Start from the reanchored bucket 'Reserve Bench' and current reality status 'bookmark candidate only'. Confirm actual implemented capability, hidden reusable modules, extension seams, and whether it strengthens the existing Weak or ambiguous adjacent candidate lane. Focus on: Inspect package/module map; entrypoints; config and schema files; adapters/integrations; persistence model; tests/examples; hidden feature flags; plugin 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 hidden admin tools, reusable services, plugin systems, import/export, analytics, background jobs, and any engine more valuable than the public README suggests.","Treat as unimplemented ScriptoriumAI candidate only. Do not let it redefine the current stack. Integrate only if a later audit proves it fills a real gap in the existing surfaces such as Dashboard, Editor, Corpus Graph, Runboard, AI Kanban, Corpus Search, Patch Review Queue, Visualizations, Whiteboard, Mind Map, PDF Intake, AI Diagram Studio, Video Studio, Research Agent, New Research Topic, Skills Manager, OpenAPI Routing, Manim Sandbox, Settings.","Repurpose here means mining for specific modules, algorithms, UI patterns, ingestion logic, workflow ideas, or export formats rather than assuming a full product transplant.",native/scriptoriumai-ui,native/ScriptoriumAI-Server,abhigyanpatwari/GitNexus,"Return concrete files/modules/adapters worth reusing and a verdict on whether the current reanchored bucket should be kept, upgraded, or downgraded.",Do not treat licensing as a filter. Do not propose replacing native foundations unless source evidence is overwhelming.,amicalhq/refref,v6_unified_source_of_truth_pack,"Before recommending direct code use, inspect the target repo row in the v6.1 operational/phase/source-audit boards. Respect copyleft_strategy_v6_1, preferred_boundary_model_v6_1, and open_compliance_if_used_as_is_v6_1. Do not assume reverse engineering is mandatory or that as-is use is always sensible.","If the repo-level strategy says bounded_sidecar_preferred or boundary_first_then_decide_as_is_vs_reimplementation, audit clean interfaces, protocol seams, subprocess/container boundaries, and what would be required to reimplement only the strategically necessary portions.",v6.3_final_source_of_truth
SCR_0053,,,,,,,,,,ScriptoriumAI repo packet,ScriptoriumAI,ScriptoriumAI re-anchored VS Code packets v1,anthropics/claude-prism,anthropics/claude-prism,Reserve Bench,P3,bookmark candidate only,"Audit anthropics/claude-prism for ScriptoriumAI. Start from the reanchored bucket 'Reserve Bench' and current reality status 'bookmark candidate only'. Confirm actual implemented capability, hidden reusable modules, extension seams, and whether it strengthens the existing Weak or ambiguous adjacent candidate lane. Focus on: Inspect hidden modules, extension seams, data contracts, rendering paths, auth/storage coupling, and export/import boundaries.",,"Treat as unimplemented ScriptoriumAI candidate only. Do not let it redefine the current stack. Integrate only if a later audit proves it fills a real gap in the existing surfaces such as Dashboard, Editor, Corpus Graph, Runboard, AI Kanban, Corpus Search, Patch Review Queue, Visualizations, Whiteboard, Mind Map, PDF Intake, AI Diagram Studio, Video Studio, Research Agent, New Research Topic, Skills Manager, OpenAPI Routing, Manim Sandbox, Settings.","Repurpose here means mining for specific modules, algorithms, UI patterns, ingestion logic, workflow ideas, or export formats rather than assuming a full product transplant.",native/ScriptoriumAI-Server,stanford-oval/storm,abhigyanpatwari/GitNexus,"Return concrete files/modules/adapters worth reusing and a verdict on whether the current reanchored bucket should be kept, upgraded, or downgraded.",Do not treat licensing as a filter. Do not propose replacing native foundations unless source evidence is overwhelming.,anthropics/claude-prism,v6_unified_source_of_truth_pack,"Before recommending direct code use, inspect the target repo row in the v6.1 operational/phase/source-audit boards. Respect copyleft_strategy_v6_1, preferred_boundary_model_v6_1, and open_compliance_if_used_as_is_v6_1. Do not assume reverse engineering is mandatory or that as-is use is always sensible.","If the repo-level strategy says bounded_sidecar_preferred or boundary_first_then_decide_as_is_vs_reimplementation, audit clean interfaces, protocol seams, subprocess/container boundaries, and what would be required to reimplement only the strategically necessary portions.",v6.3_final_source_of_truth
SCR_0054,,,,,,,,,,ScriptoriumAI repo packet,ScriptoriumAI,ScriptoriumAI re-anchored VS Code packets v1,babun/babun,babun/babun,Reserve Bench,P3,bookmark candidate only,"Audit babun/babun for ScriptoriumAI. Start from the reanchored bucket 'Reserve Bench' and current reality status 'bookmark candidate only'. Confirm actual implemented capability, hidden reusable modules, extension seams, and whether it strengthens the existing Weak or ambiguous adjacent candidate lane. Focus on: Inspect parsers and language adapters; graph schema and storage; incremental indexing/update logic; layout engine; query API; export/import formats; test fixtures for graph correctness.","Inspect package manifests, README/docs, src tree, examples, tests, CI workflows, config files, migrations/schemas, and hidden feature flags or experimental modules. Look for hidden admin tools, reusable services, plugin systems, import/export, analytics, background jobs, and any engine more valuable than the public README suggests.","Treat as unimplemented ScriptoriumAI candidate only. Do not let it redefine the current stack. Integrate only if a later audit proves it fills a real gap in the existing surfaces such as Dashboard, Editor, Corpus Graph, Runboard, AI Kanban, Corpus Search, Patch Review Queue, Visualizations, Whiteboard, Mind Map, PDF Intake, AI Diagram Studio, Video Studio, Research Agent, New Research Topic, Skills Manager, OpenAPI Routing, Manim Sandbox, Settings.","Repurpose here means mining for specific modules, algorithms, UI patterns, ingestion logic, workflow ideas, or export formats rather than assuming a full product transplant.",native/scriptoriumai-ui,native/ScriptoriumAI-Server,abhigyanpatwari/GitNexus,"Return concrete files/modules/adapters worth reusing and a verdict on whether the current reanchored bucket should be kept, upgraded, or downgraded.",Do not treat licensing as a filter. Do not propose replacing native foundations unless source evidence is overwhelming.,babun/babun,v6_unified_source_of_truth_pack,"Before recommending direct code use, inspect the target repo row in the v6.1 operational/phase/source-audit boards. Respect copyleft_strategy_v6_1, preferred_boundary_model_v6_1, and open_compliance_if_used_as_is_v6_1. Do not assume reverse engineering is mandatory or that as-is use is always sensible.","If the repo-level strategy says bounded_sidecar_preferred or boundary_first_then_decide_as_is_vs_reimplementation, audit clean interfaces, protocol seams, subprocess/container boundaries, and what would be required to reimplement only the strategically necessary portions.",v6.3_final_source_of_truth
SCR_0055,,,,,,,,,,ScriptoriumAI repo packet,ScriptoriumAI,ScriptoriumAI re-anchored VS Code packets v1,boranfurkan/react-3d-button,boranfurkan/react-3d-button,Reserve Bench,P3,bookmark candidate only,"Audit boranfurkan/react-3d-button for ScriptoriumAI. Start from the reanchored bucket 'Reserve Bench' and current reality status 'bookmark candidate only'. Confirm actual implemented capability, hidden reusable modules, extension seams, and whether it strengthens the existing Weak or ambiguous adjacent candidate lane. Focus on: Inspect parsers and language adapters; graph schema and storage; incremental indexing/update logic; layout engine; query API; export/import formats; test fixtures for graph correctness.","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.","Treat as unimplemented ScriptoriumAI candidate only. Do not let it redefine the current stack. Integrate only if a later audit proves it fills a real gap in the existing surfaces such as Dashboard, Editor, Corpus Graph, Runboard, AI Kanban, Corpus Search, Patch Review Queue, Visualizations, Whiteboard, Mind Map, PDF Intake, AI Diagram Studio, Video Studio, Research Agent, New Research Topic, Skills Manager, OpenAPI Routing, Manim Sandbox, Settings.","Repurpose here means mining for specific modules, algorithms, UI patterns, ingestion logic, workflow ideas, or export formats rather than assuming a full product transplant.",native/scriptoriumai-ui,native/ScriptoriumAI-Server,abhigyanpatwari/GitNexus,"Return concrete files/modules/adapters worth reusing and a verdict on whether the current reanchored bucket should be kept, upgraded, or downgraded.",Do not treat licensing as a filter. Do not propose replacing native foundations unless source evidence is overwhelming.,boranfurkan/react-3d-button,v6_unified_source_of_truth_pack,"Before recommending direct code use, inspect the target repo row in the v6.1 operational/phase/source-audit boards. Respect copyleft_strategy_v6_1, preferred_boundary_model_v6_1, and open_compliance_if_used_as_is_v6_1. Do not assume reverse engineering is mandatory or that as-is use is always sensible.","If the repo-level strategy says bounded_sidecar_preferred or boundary_first_then_decide_as_is_vs_reimplementation, audit clean interfaces, protocol seams, subprocess/container boundaries, and what would be required to reimplement only the strategically necessary portions.",v6.3_final_source_of_truth
SCR_0056,,,,,,,,,,ScriptoriumAI repo packet,ScriptoriumAI,ScriptoriumAI re-anchored VS Code packets v1,btahir/react-kino,btahir/react-kino,Reserve Bench,P3,bookmark candidate only,"Audit btahir/react-kino for ScriptoriumAI. Start from the reanchored bucket 'Reserve Bench' and current reality status 'bookmark candidate only'. Confirm actual implemented capability, hidden reusable modules, extension seams, and whether it strengthens the existing Weak or ambiguous adjacent candidate lane. Focus on: 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.","Treat as unimplemented ScriptoriumAI candidate only. Do not let it redefine the current stack. Integrate only if a later audit proves it fills a real gap in the existing surfaces such as Dashboard, Editor, Corpus Graph, Runboard, AI Kanban, Corpus Search, Patch Review Queue, Visualizations, Whiteboard, Mind Map, PDF Intake, AI Diagram Studio, Video Studio, Research Agent, New Research Topic, Skills Manager, OpenAPI Routing, Manim Sandbox, Settings.","Repurpose here means mining for specific modules, algorithms, UI patterns, ingestion logic, workflow ideas, or export formats rather than assuming a full product transplant.",native/scriptoriumai-ui,native/ScriptoriumAI-Server,abhigyanpatwari/GitNexus,"Return concrete files/modules/adapters worth reusing and a verdict on whether the current reanchored bucket should be kept, upgraded, or downgraded.",Do not treat licensing as a filter. Do not propose replacing native foundations unless source evidence is overwhelming.,btahir/react-kino,v6_unified_source_of_truth_pack,"Before recommending direct code use, inspect the target repo row in the v6.1 operational/phase/source-audit boards. Respect copyleft_strategy_v6_1, preferred_boundary_model_v6_1, and open_compliance_if_used_as_is_v6_1. Do not assume reverse engineering is mandatory or that as-is use is always sensible.","If the repo-level strategy says bounded_sidecar_preferred or boundary_first_then_decide_as_is_vs_reimplementation, audit clean interfaces, protocol seams, subprocess/container boundaries, and what would be required to reimplement only the strategically necessary portions.",v6.3_final_source_of_truth
SCR_0057,,,,,,,,,,ScriptoriumAI repo packet,ScriptoriumAI,ScriptoriumAI re-anchored VS Code packets v1,chaitin/SafeLine,chaitin/safeline,Reserve Bench,P3,bookmark candidate only,"Audit chaitin/SafeLine for ScriptoriumAI. Start from the reanchored bucket 'Reserve Bench' and current reality status 'bookmark candidate only'. Confirm actual implemented capability, hidden reusable modules, extension seams, and whether it strengthens the existing Weak or ambiguous adjacent candidate lane. Focus on: Inspect parsers and language adapters; graph schema and storage; incremental indexing/update logic; layout engine; query API; export/import formats; test fixtures for graph correctness.","Inspect package manifests, README/docs, src tree, examples, tests, CI workflows, config files, migrations/schemas, and hidden feature flags or experimental modules. Look for hidden admin tools, reusable services, plugin systems, import/export, analytics, background jobs, and any engine more valuable than the public README suggests.","Treat as unimplemented ScriptoriumAI candidate only. Do not let it redefine the current stack. Integrate only if a later audit proves it fills a real gap in the existing surfaces such as Dashboard, Editor, Corpus Graph, Runboard, AI Kanban, Corpus Search, Patch Review Queue, Visualizations, Whiteboard, Mind Map, PDF Intake, AI Diagram Studio, Video Studio, Research Agent, New Research Topic, Skills Manager, OpenAPI Routing, Manim Sandbox, Settings.","Repurpose here means mining for specific modules, algorithms, UI patterns, ingestion logic, workflow ideas, or export formats rather than assuming a full product transplant.",native/scriptoriumai-ui,native/ScriptoriumAI-Server,abhigyanpatwari/GitNexus,"Return concrete files/modules/adapters worth reusing and a verdict on whether the current reanchored bucket should be kept, upgraded, or downgraded.",Do not treat licensing as a filter. Do not propose replacing native foundations unless source evidence is overwhelming.,chaitin/safeline,v6_unified_source_of_truth_pack,"Before recommending direct code use, inspect the target repo row in the v6.1 operational/phase/source-audit boards. Respect copyleft_strategy_v6_1, preferred_boundary_model_v6_1, and open_compliance_if_used_as_is_v6_1. Do not assume reverse engineering is mandatory or that as-is use is always sensible.","If the repo-level strategy says bounded_sidecar_preferred or boundary_first_then_decide_as_is_vs_reimplementation, audit clean interfaces, protocol seams, subprocess/container boundaries, and what would be required to reimplement only the strategically necessary portions.",v6.3_final_source_of_truth
SCR_0058,,,,,,,,,,ScriptoriumAI repo packet,ScriptoriumAI,ScriptoriumAI re-anchored VS Code packets v1,codemerx/CodemerxDecompile,codemerx/codemerxdecompile,Reserve Bench,P3,bookmark candidate only,"Audit codemerx/CodemerxDecompile for ScriptoriumAI. Start from the reanchored bucket 'Reserve Bench' and current reality status 'bookmark candidate only'. Confirm actual implemented capability, hidden reusable modules, extension seams, and whether it strengthens the existing Weak or ambiguous adjacent candidate lane. Focus on: Inspect package/module map; entrypoints; config and schema files; adapters/integrations; persistence model; tests/examples; hidden feature flags; plugin 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 hidden admin tools, reusable services, plugin systems, import/export, analytics, background jobs, and any engine more valuable than the public README suggests.","Treat as unimplemented ScriptoriumAI candidate only. Do not let it redefine the current stack. Integrate only if a later audit proves it fills a real gap in the existing surfaces such as Dashboard, Editor, Corpus Graph, Runboard, AI Kanban, Corpus Search, Patch Review Queue, Visualizations, Whiteboard, Mind Map, PDF Intake, AI Diagram Studio, Video Studio, Research Agent, New Research Topic, Skills Manager, OpenAPI Routing, Manim Sandbox, Settings.","Repurpose here means mining for specific modules, algorithms, UI patterns, ingestion logic, workflow ideas, or export formats rather than assuming a full product transplant.",native/scriptoriumai-ui,native/ScriptoriumAI-Server,abhigyanpatwari/GitNexus,"Return concrete files/modules/adapters worth reusing and a verdict on whether the current reanchored bucket should be kept, upgraded, or downgraded.",Do not treat licensing as a filter. Do not propose replacing native foundations unless source evidence is overwhelming.,codemerx/codemerxdecompile,v6_unified_source_of_truth_pack,"Before recommending direct code use, inspect the target repo row in the v6.1 operational/phase/source-audit boards. Respect copyleft_strategy_v6_1, preferred_boundary_model_v6_1, and open_compliance_if_used_as_is_v6_1. Do not assume reverse engineering is mandatory or that as-is use is always sensible.","If the repo-level strategy says bounded_sidecar_preferred or boundary_first_then_decide_as_is_vs_reimplementation, audit clean interfaces, protocol seams, subprocess/container boundaries, and what would be required to reimplement only the strategically necessary portions.",v6.3_final_source_of_truth
SCR_0059,,,,,,,,,,ScriptoriumAI repo packet,ScriptoriumAI,ScriptoriumAI re-anchored VS Code packets v1,coleam00/local-ai-packaged,coleam00/local-ai-packaged,Reserve Bench,P3,bookmark candidate only,"Audit coleam00/local-ai-packaged for ScriptoriumAI. Start from the reanchored bucket 'Reserve Bench' and current reality status 'bookmark candidate only'. Confirm actual implemented capability, hidden reusable modules, extension seams, and whether it strengthens the existing Weak or ambiguous adjacent candidate lane. Focus on: 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.","Treat as unimplemented ScriptoriumAI candidate only. Do not let it redefine the current stack. Integrate only if a later audit proves it fills a real gap in the existing surfaces such as Dashboard, Editor, Corpus Graph, Runboard, AI Kanban, Corpus Search, Patch Review Queue, Visualizations, Whiteboard, Mind Map, PDF Intake, AI Diagram Studio, Video Studio, Research Agent, New Research Topic, Skills Manager, OpenAPI Routing, Manim Sandbox, Settings.","Repurpose here means mining for specific modules, algorithms, UI patterns, ingestion logic, workflow ideas, or export formats rather than assuming a full product transplant.",native/scriptoriumai-ui,native/ScriptoriumAI-Server,abhigyanpatwari/GitNexus,"Return concrete files/modules/adapters worth reusing and a verdict on whether the current reanchored bucket should be kept, upgraded, or downgraded.",Do not treat licensing as a filter. Do not propose replacing native foundations unless source evidence is overwhelming.,coleam00/local-ai-packaged,v6_unified_source_of_truth_pack,"Before recommending direct code use, inspect the target repo row in the v6.1 operational/phase/source-audit boards. Respect copyleft_strategy_v6_1, preferred_boundary_model_v6_1, and open_compliance_if_used_as_is_v6_1. Do not assume reverse engineering is mandatory or that as-is use is always sensible.","If the repo-level strategy says bounded_sidecar_preferred or boundary_first_then_decide_as_is_vs_reimplementation, audit clean interfaces, protocol seams, subprocess/container boundaries, and what would be required to reimplement only the strategically necessary portions.",v6.3_final_source_of_truth
SCR_0060,,,,,,,,,,ScriptoriumAI repo packet,ScriptoriumAI,ScriptoriumAI re-anchored VS Code packets v1,coollabsio/sentinel,coollabsio/sentinel,Reserve Bench,P3,bookmark candidate only,"Audit coollabsio/sentinel for ScriptoriumAI. Start from the reanchored bucket 'Reserve Bench' and current reality status 'bookmark candidate only'. Confirm actual implemented capability, hidden reusable modules, extension seams, and whether it strengthens the existing Weak or ambiguous adjacent candidate lane. Focus on: 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.","Treat as unimplemented ScriptoriumAI candidate only. Do not let it redefine the current stack. Integrate only if a later audit proves it fills a real gap in the existing surfaces such as Dashboard, Editor, Corpus Graph, Runboard, AI Kanban, Corpus Search, Patch Review Queue, Visualizations, Whiteboard, Mind Map, PDF Intake, AI Diagram Studio, Video Studio, Research Agent, New Research Topic, Skills Manager, OpenAPI Routing, Manim Sandbox, Settings.","Repurpose here means mining for specific modules, algorithms, UI patterns, ingestion logic, workflow ideas, or export formats rather than assuming a full product transplant.",native/scriptoriumai-ui,native/ScriptoriumAI-Server,abhigyanpatwari/GitNexus,"Return concrete files/modules/adapters worth reusing and a verdict on whether the current reanchored bucket should be kept, upgraded, or downgraded.",Do not treat licensing as a filter. Do not propose replacing native foundations unless source evidence is overwhelming.,coollabsio/sentinel,v6_unified_source_of_truth_pack,"Before recommending direct code use, inspect the target repo row in the v6.1 operational/phase/source-audit boards. Respect copyleft_strategy_v6_1, preferred_boundary_model_v6_1, and open_compliance_if_used_as_is_v6_1. Do not assume reverse engineering is mandatory or that as-is use is always sensible.","If the repo-level strategy says bounded_sidecar_preferred or boundary_first_then_decide_as_is_vs_reimplementation, audit clean interfaces, protocol seams, subprocess/container boundaries, and what would be required to reimplement only the strategically necessary portions.",v6.3_final_source_of_truth
SCR_0061,,,,,,,,,,ScriptoriumAI repo packet,ScriptoriumAI,ScriptoriumAI re-anchored VS Code packets v1,danish296/codevibes,danish296/codevibes,Reserve Bench,P3,bookmark candidate only,"Audit danish296/codevibes for ScriptoriumAI. Start from the reanchored bucket 'Reserve Bench' and current reality status 'bookmark candidate only'. Confirm actual implemented capability, hidden reusable modules, extension seams, and whether it strengthens the existing Weak or ambiguous adjacent candidate lane. Focus on: Inspect parsers and language adapters; graph schema and storage; incremental indexing/update logic; layout engine; query API; export/import formats; test fixtures for graph correctness.","Inspect package manifests, README/docs, src tree, examples, tests, CI workflows, config files, migrations/schemas, and hidden feature flags or experimental modules. Look for template packs, protocol adapters, scan schedulers, passive-recon modules, fingerprinting, evidence schemas, diff/baseline logic, and plugin hooks for new scanners.","Treat as unimplemented ScriptoriumAI candidate only. Do not let it redefine the current stack. Integrate only if a later audit proves it fills a real gap in the existing surfaces such as Dashboard, Editor, Corpus Graph, Runboard, AI Kanban, Corpus Search, Patch Review Queue, Visualizations, Whiteboard, Mind Map, PDF Intake, AI Diagram Studio, Video Studio, Research Agent, New Research Topic, Skills Manager, OpenAPI Routing, Manim Sandbox, Settings.","Repurpose here means mining for specific modules, algorithms, UI patterns, ingestion logic, workflow ideas, or export formats rather than assuming a full product transplant.",native/scriptoriumai-ui,native/ScriptoriumAI-Server,abhigyanpatwari/GitNexus,"Return concrete files/modules/adapters worth reusing and a verdict on whether the current reanchored bucket should be kept, upgraded, or downgraded.",Do not treat licensing as a filter. Do not propose replacing native foundations unless source evidence is overwhelming.,danish296/codevibes,v6_unified_source_of_truth_pack,"Before recommending direct code use, inspect the target repo row in the v6.1 operational/phase/source-audit boards. Respect copyleft_strategy_v6_1, preferred_boundary_model_v6_1, and open_compliance_if_used_as_is_v6_1. Do not assume reverse engineering is mandatory or that as-is use is always sensible.","If the repo-level strategy says bounded_sidecar_preferred or boundary_first_then_decide_as_is_vs_reimplementation, audit clean interfaces, protocol seams, subprocess/container boundaries, and what would be required to reimplement only the strategically necessary portions.",v6.3_final_source_of_truth
SCR_0062,,,,,,,,,,ScriptoriumAI repo packet,ScriptoriumAI,ScriptoriumAI re-anchored VS Code packets v1,darula-hpp/shimmer-from-structure,darula-hpp/shimmer-from-structure,Reserve Bench,P3,bookmark candidate only,"Audit darula-hpp/shimmer-from-structure for ScriptoriumAI. Start from the reanchored bucket 'Reserve Bench' and current reality status 'bookmark candidate only'. Confirm actual implemented capability, hidden reusable modules, extension seams, and whether it strengthens the existing Weak or ambiguous adjacent candidate lane. Focus on: Inspect parsers and language adapters; graph schema and storage; incremental indexing/update logic; layout engine; query API; export/import formats; test fixtures for graph correctness.","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.","Treat as unimplemented ScriptoriumAI candidate only. Do not let it redefine the current stack. Integrate only if a later audit proves it fills a real gap in the existing surfaces such as Dashboard, Editor, Corpus Graph, Runboard, AI Kanban, Corpus Search, Patch Review Queue, Visualizations, Whiteboard, Mind Map, PDF Intake, AI Diagram Studio, Video Studio, Research Agent, New Research Topic, Skills Manager, OpenAPI Routing, Manim Sandbox, Settings.","Repurpose here means mining for specific modules, algorithms, UI patterns, ingestion logic, workflow ideas, or export formats rather than assuming a full product transplant.",native/scriptoriumai-ui,native/ScriptoriumAI-Server,abhigyanpatwari/GitNexus,"Return concrete files/modules/adapters worth reusing and a verdict on whether the current reanchored bucket should be kept, upgraded, or downgraded.",Do not treat licensing as a filter. Do not propose replacing native foundations unless source evidence is overwhelming.,darula-hpp/shimmer-from-structure,v6_unified_source_of_truth_pack,"Before recommending direct code use, inspect the target repo row in the v6.1 operational/phase/source-audit boards. Respect copyleft_strategy_v6_1, preferred_boundary_model_v6_1, and open_compliance_if_used_as_is_v6_1. Do not assume reverse engineering is mandatory or that as-is use is always sensible.","If the repo-level strategy says bounded_sidecar_preferred or boundary_first_then_decide_as_is_vs_reimplementation, audit clean interfaces, protocol seams, subprocess/container boundaries, and what would be required to reimplement only the strategically necessary portions.",v6.3_final_source_of_truth
SCR_0063,,,,,,,,,,ScriptoriumAI repo packet,ScriptoriumAI,ScriptoriumAI re-anchored VS Code packets v1,dotnet/csharplang,dotnet/csharplang,Reserve Bench,P3,bookmark candidate only,"Audit dotnet/csharplang for ScriptoriumAI. Start from the reanchored bucket 'Reserve Bench' and current reality status 'bookmark candidate only'. Confirm actual implemented capability, hidden reusable modules, extension seams, and whether it strengthens the existing Weak or ambiguous adjacent candidate lane. Focus on: 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 event schemas, ingestion pipelines, queue/job workers, service adapters, deployment/runtime config, RBAC/auth, alerting, and API contract generators.","Treat as unimplemented ScriptoriumAI candidate only. Do not let it redefine the current stack. Integrate only if a later audit proves it fills a real gap in the existing surfaces such as Dashboard, Editor, Corpus Graph, Runboard, AI Kanban, Corpus Search, Patch Review Queue, Visualizations, Whiteboard, Mind Map, PDF Intake, AI Diagram Studio, Video Studio, Research Agent, New Research Topic, Skills Manager, OpenAPI Routing, Manim Sandbox, Settings.","Repurpose here means mining for specific modules, algorithms, UI patterns, ingestion logic, workflow ideas, or export formats rather than assuming a full product transplant.",native/scriptoriumai-ui,native/ScriptoriumAI-Server,abhigyanpatwari/GitNexus,"Return concrete files/modules/adapters worth reusing and a verdict on whether the current reanchored bucket should be kept, upgraded, or downgraded.",Do not treat licensing as a filter. Do not propose replacing native foundations unless source evidence is overwhelming.,dotnet/csharplang,v6_unified_source_of_truth_pack,"Before recommending direct code use, inspect the target repo row in the v6.1 operational/phase/source-audit boards. Respect copyleft_strategy_v6_1, preferred_boundary_model_v6_1, and open_compliance_if_used_as_is_v6_1. Do not assume reverse engineering is mandatory or that as-is use is always sensible.","If the repo-level strategy says bounded_sidecar_preferred or boundary_first_then_decide_as_is_vs_reimplementation, audit clean interfaces, protocol seams, subprocess/container boundaries, and what would be required to reimplement only the strategically necessary portions.",v6.3_final_source_of_truth
SCR_0064,,,,,,,,,,ScriptoriumAI repo packet,ScriptoriumAI,ScriptoriumAI re-anchored VS Code packets v1,einui/einui,einui/einui,Reserve Bench,P3,bookmark candidate only,"Audit einui/einui for ScriptoriumAI. Start from the reanchored bucket 'Reserve Bench' and current reality status 'bookmark candidate only'. Confirm actual implemented capability, hidden reusable modules, extension seams, and whether it strengthens the existing Weak or ambiguous adjacent candidate lane. Focus on: 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.","Treat as unimplemented ScriptoriumAI candidate only. Do not let it redefine the current stack. Integrate only if a later audit proves it fills a real gap in the existing surfaces such as Dashboard, Editor, Corpus Graph, Runboard, AI Kanban, Corpus Search, Patch Review Queue, Visualizations, Whiteboard, Mind Map, PDF Intake, AI Diagram Studio, Video Studio, Research Agent, New Research Topic, Skills Manager, OpenAPI Routing, Manim Sandbox, Settings.","Repurpose here means mining for specific modules, algorithms, UI patterns, ingestion logic, workflow ideas, or export formats rather than assuming a full product transplant.",native/scriptoriumai-ui,native/ScriptoriumAI-Server,abhigyanpatwari/GitNexus,"Return concrete files/modules/adapters worth reusing and a verdict on whether the current reanchored bucket should be kept, upgraded, or downgraded.",Do not treat licensing as a filter. Do not propose replacing native foundations unless source evidence is overwhelming.,einui/einui,v6_unified_source_of_truth_pack,"Before recommending direct code use, inspect the target repo row in the v6.1 operational/phase/source-audit boards. Respect copyleft_strategy_v6_1, preferred_boundary_model_v6_1, and open_compliance_if_used_as_is_v6_1. Do not assume reverse engineering is mandatory or that as-is use is always sensible.","If the repo-level strategy says bounded_sidecar_preferred or boundary_first_then_decide_as_is_vs_reimplementation, audit clean interfaces, protocol seams, subprocess/container boundaries, and what would be required to reimplement only the strategically necessary portions.",v6.3_final_source_of_truth
SCR_0065,,,,,,,,,,ScriptoriumAI repo packet,ScriptoriumAI,ScriptoriumAI re-anchored VS Code packets v1,en0ndev/0e70e5f07296fbfe3dd9628cd19615da,en0ndev/0e70e5f07296fbfe3dd9628cd19615da,Reserve Bench,P3,bookmark candidate only,"Audit en0ndev/0e70e5f07296fbfe3dd9628cd19615da for ScriptoriumAI. Start from the reanchored bucket 'Reserve Bench' and current reality status 'bookmark candidate only'. Confirm actual implemented capability, hidden reusable modules, extension seams, and whether it strengthens the existing Weak or ambiguous adjacent candidate lane. Focus on: 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.","Treat as unimplemented ScriptoriumAI candidate only. Do not let it redefine the current stack. Integrate only if a later audit proves it fills a real gap in the existing surfaces such as Dashboard, Editor, Corpus Graph, Runboard, AI Kanban, Corpus Search, Patch Review Queue, Visualizations, Whiteboard, Mind Map, PDF Intake, AI Diagram Studio, Video Studio, Research Agent, New Research Topic, Skills Manager, OpenAPI Routing, Manim Sandbox, Settings.","Repurpose here means mining for specific modules, algorithms, UI patterns, ingestion logic, workflow ideas, or export formats rather than assuming a full product transplant.",native/scriptoriumai-ui,native/ScriptoriumAI-Server,abhigyanpatwari/GitNexus,"Return concrete files/modules/adapters worth reusing and a verdict on whether the current reanchored bucket should be kept, upgraded, or downgraded.",Do not treat licensing as a filter. Do not propose replacing native foundations unless source evidence is overwhelming.,en0ndev/0e70e5f07296fbfe3dd9628cd19615da,v6_unified_source_of_truth_pack,"Before recommending direct code use, inspect the target repo row in the v6.1 operational/phase/source-audit boards. Respect copyleft_strategy_v6_1, preferred_boundary_model_v6_1, and open_compliance_if_used_as_is_v6_1. Do not assume reverse engineering is mandatory or that as-is use is always sensible.","If the repo-level strategy says bounded_sidecar_preferred or boundary_first_then_decide_as_is_vs_reimplementation, audit clean interfaces, protocol seams, subprocess/container boundaries, and what would be required to reimplement only the strategically necessary portions.",v6.3_final_source_of_truth
SCR_0066,,,,,,,,,,ScriptoriumAI repo packet,ScriptoriumAI,ScriptoriumAI re-anchored VS Code packets v1,fabro/fabro,fabro/fabro,Reserve Bench,P3,bookmark candidate only,"Audit fabro/fabro for ScriptoriumAI. Start from the reanchored bucket 'Reserve Bench' and current reality status 'bookmark candidate only'. Confirm actual implemented capability, hidden reusable modules, extension seams, and whether it strengthens the existing Weak or ambiguous adjacent candidate lane. Focus on: Inspect hidden modules, extension seams, data contracts, rendering paths, auth/storage coupling, and export/import boundaries.",,"Treat as unimplemented ScriptoriumAI candidate only. Do not let it redefine the current stack. Integrate only if a later audit proves it fills a real gap in the existing surfaces such as Dashboard, Editor, Corpus Graph, Runboard, AI Kanban, Corpus Search, Patch Review Queue, Visualizations, Whiteboard, Mind Map, PDF Intake, AI Diagram Studio, Video Studio, Research Agent, New Research Topic, Skills Manager, OpenAPI Routing, Manim Sandbox, Settings.","Repurpose here means mining for specific modules, algorithms, UI patterns, ingestion logic, workflow ideas, or export formats rather than assuming a full product transplant.",native/scriptoriumai-ui,excalidraw/excalidraw,jgraph/drawio,"Return concrete files/modules/adapters worth reusing and a verdict on whether the current reanchored bucket should be kept, upgraded, or downgraded.",Do not treat licensing as a filter. Do not propose replacing native foundations unless source evidence is overwhelming.,fabro/fabro,v6_unified_source_of_truth_pack,"Before recommending direct code use, inspect the target repo row in the v6.1 operational/phase/source-audit boards. Respect copyleft_strategy_v6_1, preferred_boundary_model_v6_1, and open_compliance_if_used_as_is_v6_1. Do not assume reverse engineering is mandatory or that as-is use is always sensible.","If the repo-level strategy says bounded_sidecar_preferred or boundary_first_then_decide_as_is_vs_reimplementation, audit clean interfaces, protocol seams, subprocess/container boundaries, and what would be required to reimplement only the strategically necessary portions.",v6.3_final_source_of_truth
SCR_0067,,,,,,,,,,ScriptoriumAI repo packet,ScriptoriumAI,ScriptoriumAI re-anchored VS Code packets v1,fal-ai/f-lite,fal-ai/f-lite,Reserve Bench,P3,bookmark candidate only,"Audit fal-ai/f-lite for ScriptoriumAI. Start from the reanchored bucket 'Reserve Bench' and current reality status 'bookmark candidate only'. Confirm actual implemented capability, hidden reusable modules, extension seams, and whether it strengthens the existing Weak or ambiguous adjacent candidate lane. Focus on: 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.","Treat as unimplemented ScriptoriumAI candidate only. Do not let it redefine the current stack. Integrate only if a later audit proves it fills a real gap in the existing surfaces such as Dashboard, Editor, Corpus Graph, Runboard, AI Kanban, Corpus Search, Patch Review Queue, Visualizations, Whiteboard, Mind Map, PDF Intake, AI Diagram Studio, Video Studio, Research Agent, New Research Topic, Skills Manager, OpenAPI Routing, Manim Sandbox, Settings.","Repurpose here means mining for specific modules, algorithms, UI patterns, ingestion logic, workflow ideas, or export formats rather than assuming a full product transplant.",native/scriptoriumai-ui,native/ScriptoriumAI-Server,abhigyanpatwari/GitNexus,"Return concrete files/modules/adapters worth reusing and a verdict on whether the current reanchored bucket should be kept, upgraded, or downgraded.",Do not treat licensing as a filter. Do not propose replacing native foundations unless source evidence is overwhelming.,fal-ai/f-lite,v6_unified_source_of_truth_pack,"Before recommending direct code use, inspect the target repo row in the v6.1 operational/phase/source-audit boards. Respect copyleft_strategy_v6_1, preferred_boundary_model_v6_1, and open_compliance_if_used_as_is_v6_1. Do not assume reverse engineering is mandatory or that as-is use is always sensible.","If the repo-level strategy says bounded_sidecar_preferred or boundary_first_then_decide_as_is_vs_reimplementation, audit clean interfaces, protocol seams, subprocess/container boundaries, and what would be required to reimplement only the strategically necessary portions.",v6.3_final_source_of_truth
SCR_0068,,,,,,,,,,ScriptoriumAI repo packet,ScriptoriumAI,ScriptoriumAI re-anchored VS Code packets v1,farzaa/clicky,farzaa/clicky,Reserve Bench,P3,bookmark candidate only,"Audit farzaa/clicky for ScriptoriumAI. Start from the reanchored bucket 'Reserve Bench' and current reality status 'bookmark candidate only'. Confirm actual implemented capability, hidden reusable modules, extension seams, and whether it strengthens the existing Weak or ambiguous adjacent candidate lane. Focus on: Inspect planner/task graph; provider abstraction; tool registry or MCP bridges; memory/state schema; approvals/retries; telemetry/event bus; plugin or skill loading 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 event schemas, ingestion pipelines, queue/job workers, service adapters, deployment/runtime config, RBAC/auth, alerting, and API contract generators.","Treat as unimplemented ScriptoriumAI candidate only. Do not let it redefine the current stack. Integrate only if a later audit proves it fills a real gap in the existing surfaces such as Dashboard, Editor, Corpus Graph, Runboard, AI Kanban, Corpus Search, Patch Review Queue, Visualizations, Whiteboard, Mind Map, PDF Intake, AI Diagram Studio, Video Studio, Research Agent, New Research Topic, Skills Manager, OpenAPI Routing, Manim Sandbox, Settings.","Repurpose here means mining for specific modules, algorithms, UI patterns, ingestion logic, workflow ideas, or export formats rather than assuming a full product transplant.",native/scriptoriumai-ui,native/ScriptoriumAI-Server,abhigyanpatwari/GitNexus,"Return concrete files/modules/adapters worth reusing and a verdict on whether the current reanchored bucket should be kept, upgraded, or downgraded.",Do not treat licensing as a filter. Do not propose replacing native foundations unless source evidence is overwhelming.,farzaa/clicky,v6_unified_source_of_truth_pack,"Before recommending direct code use, inspect the target repo row in the v6.1 operational/phase/source-audit boards. Respect copyleft_strategy_v6_1, preferred_boundary_model_v6_1, and open_compliance_if_used_as_is_v6_1. Do not assume reverse engineering is mandatory or that as-is use is always sensible.","If the repo-level strategy says bounded_sidecar_preferred or boundary_first_then_decide_as_is_vs_reimplementation, audit clean interfaces, protocol seams, subprocess/container boundaries, and what would be required to reimplement only the strategically necessary portions.",v6.3_final_source_of_truth
SCR_0069,,,,,,,,,,ScriptoriumAI repo packet,ScriptoriumAI,ScriptoriumAI re-anchored VS Code packets v1,firebase/genkit,firebase/genkit,Reserve Bench,P3,bookmark candidate only,"Audit firebase/genkit for ScriptoriumAI. Start from the reanchored bucket 'Reserve Bench' and current reality status 'bookmark candidate only'. Confirm actual implemented capability, hidden reusable modules, extension seams, and whether it strengthens the existing Weak or ambiguous adjacent candidate lane. Focus on: 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.","Treat as unimplemented ScriptoriumAI candidate only. Do not let it redefine the current stack. Integrate only if a later audit proves it fills a real gap in the existing surfaces such as Dashboard, Editor, Corpus Graph, Runboard, AI Kanban, Corpus Search, Patch Review Queue, Visualizations, Whiteboard, Mind Map, PDF Intake, AI Diagram Studio, Video Studio, Research Agent, New Research Topic, Skills Manager, OpenAPI Routing, Manim Sandbox, Settings.","Repurpose here means mining for specific modules, algorithms, UI patterns, ingestion logic, workflow ideas, or export formats rather than assuming a full product transplant.",native/scriptoriumai-ui,native/ScriptoriumAI-Server,abhigyanpatwari/GitNexus,"Return concrete files/modules/adapters worth reusing and a verdict on whether the current reanchored bucket should be kept, upgraded, or downgraded.",Do not treat licensing as a filter. Do not propose replacing native foundations unless source evidence is overwhelming.,firebase/genkit,v6_unified_source_of_truth_pack,"Before recommending direct code use, inspect the target repo row in the v6.1 operational/phase/source-audit boards. Respect copyleft_strategy_v6_1, preferred_boundary_model_v6_1, and open_compliance_if_used_as_is_v6_1. Do not assume reverse engineering is mandatory or that as-is use is always sensible.","If the repo-level strategy says bounded_sidecar_preferred or boundary_first_then_decide_as_is_vs_reimplementation, audit clean interfaces, protocol seams, subprocess/container boundaries, and what would be required to reimplement only the strategically necessary portions.",v6.3_final_source_of_truth
SCR_0070,,,,,,,,,,ScriptoriumAI repo packet,ScriptoriumAI,ScriptoriumAI re-anchored VS Code packets v1,getcompanion-ai/feynman,getcompanion-ai/feynman,Reserve Bench,P3,bookmark candidate only,"Audit getcompanion-ai/feynman for ScriptoriumAI. Start from the reanchored bucket 'Reserve Bench' and current reality status 'bookmark candidate only'. Confirm actual implemented capability, hidden reusable modules, extension seams, and whether it strengthens the existing Weak or ambiguous adjacent candidate lane. Focus on: Inspect parsers and language adapters; graph schema and storage; incremental indexing/update logic; layout engine; query API; export/import formats; test fixtures for graph correctness.","Inspect package manifests, README/docs, src tree, examples, tests, CI workflows, config files, migrations/schemas, and hidden feature flags or experimental modules. Look for hidden admin tools, reusable services, plugin systems, import/export, analytics, background jobs, and any engine more valuable than the public README suggests.","Treat as unimplemented ScriptoriumAI candidate only. Do not let it redefine the current stack. Integrate only if a later audit proves it fills a real gap in the existing surfaces such as Dashboard, Editor, Corpus Graph, Runboard, AI Kanban, Corpus Search, Patch Review Queue, Visualizations, Whiteboard, Mind Map, PDF Intake, AI Diagram Studio, Video Studio, Research Agent, New Research Topic, Skills Manager, OpenAPI Routing, Manim Sandbox, Settings.","Repurpose here means mining for specific modules, algorithms, UI patterns, ingestion logic, workflow ideas, or export formats rather than assuming a full product transplant.",native/scriptoriumai-ui,native/ScriptoriumAI-Server,abhigyanpatwari/GitNexus,"Return concrete files/modules/adapters worth reusing and a verdict on whether the current reanchored bucket should be kept, upgraded, or downgraded.",Do not treat licensing as a filter. Do not propose replacing native foundations unless source evidence is overwhelming.,getcompanion-ai/feynman,v6_unified_source_of_truth_pack,"Before recommending direct code use, inspect the target repo row in the v6.1 operational/phase/source-audit boards. Respect copyleft_strategy_v6_1, preferred_boundary_model_v6_1, and open_compliance_if_used_as_is_v6_1. Do not assume reverse engineering is mandatory or that as-is use is always sensible.","If the repo-level strategy says bounded_sidecar_preferred or boundary_first_then_decide_as_is_vs_reimplementation, audit clean interfaces, protocol seams, subprocess/container boundaries, and what would be required to reimplement only the strategically necessary portions.",v6.3_final_source_of_truth
SCR_0071,,,,,,,,,,ScriptoriumAI repo packet,ScriptoriumAI,ScriptoriumAI re-anchored VS Code packets v1,huggingface/transformers,huggingface/transformers,Reserve Bench,P3,bookmark candidate only,"Audit huggingface/transformers for ScriptoriumAI. Start from the reanchored bucket 'Reserve Bench' and current reality status 'bookmark candidate only'. Confirm actual implemented capability, hidden reusable modules, extension seams, and whether it strengthens the existing Weak or ambiguous adjacent candidate lane. Focus on: 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.","Treat as unimplemented ScriptoriumAI candidate only. Do not let it redefine the current stack. Integrate only if a later audit proves it fills a real gap in the existing surfaces such as Dashboard, Editor, Corpus Graph, Runboard, AI Kanban, Corpus Search, Patch Review Queue, Visualizations, Whiteboard, Mind Map, PDF Intake, AI Diagram Studio, Video Studio, Research Agent, New Research Topic, Skills Manager, OpenAPI Routing, Manim Sandbox, Settings.","Repurpose here means mining for specific modules, algorithms, UI patterns, ingestion logic, workflow ideas, or export formats rather than assuming a full product transplant.",native/scriptoriumai-ui,native/ScriptoriumAI-Server,abhigyanpatwari/GitNexus,"Return concrete files/modules/adapters worth reusing and a verdict on whether the current reanchored bucket should be kept, upgraded, or downgraded.",Do not treat licensing as a filter. Do not propose replacing native foundations unless source evidence is overwhelming.,huggingface/transformers,v6_unified_source_of_truth_pack,"Before recommending direct code use, inspect the target repo row in the v6.1 operational/phase/source-audit boards. Respect copyleft_strategy_v6_1, preferred_boundary_model_v6_1, and open_compliance_if_used_as_is_v6_1. Do not assume reverse engineering is mandatory or that as-is use is always sensible.","If the repo-level strategy says bounded_sidecar_preferred or boundary_first_then_decide_as_is_vs_reimplementation, audit clean interfaces, protocol seams, subprocess/container boundaries, and what would be required to reimplement only the strategically necessary portions.",v6.3_final_source_of_truth
SCR_0072,,,,,,,,,,ScriptoriumAI repo packet,ScriptoriumAI,ScriptoriumAI re-anchored VS Code packets v1,icedland/iced,icedland/iced,Reserve Bench,P3,bookmark candidate only,"Audit icedland/iced for ScriptoriumAI. Start from the reanchored bucket 'Reserve Bench' and current reality status 'bookmark candidate only'. Confirm actual implemented capability, hidden reusable modules, extension seams, and whether it strengthens the existing Weak or ambiguous adjacent candidate lane. Focus on: Inspect parsers and language adapters; graph schema and storage; incremental indexing/update logic; layout engine; query API; export/import formats; test fixtures for graph correctness.","Inspect package manifests, README/docs, src tree, examples, tests, CI workflows, config files, migrations/schemas, and hidden feature flags or experimental modules. Look for hidden admin tools, reusable services, plugin systems, import/export, analytics, background jobs, and any engine more valuable than the public README suggests.","Treat as unimplemented ScriptoriumAI candidate only. Do not let it redefine the current stack. Integrate only if a later audit proves it fills a real gap in the existing surfaces such as Dashboard, Editor, Corpus Graph, Runboard, AI Kanban, Corpus Search, Patch Review Queue, Visualizations, Whiteboard, Mind Map, PDF Intake, AI Diagram Studio, Video Studio, Research Agent, New Research Topic, Skills Manager, OpenAPI Routing, Manim Sandbox, Settings.","Repurpose here means mining for specific modules, algorithms, UI patterns, ingestion logic, workflow ideas, or export formats rather than assuming a full product transplant.",native/scriptoriumai-ui,native/ScriptoriumAI-Server,abhigyanpatwari/GitNexus,"Return concrete files/modules/adapters worth reusing and a verdict on whether the current reanchored bucket should be kept, upgraded, or downgraded.",Do not treat licensing as a filter. Do not propose replacing native foundations unless source evidence is overwhelming.,icedland/iced,v6_unified_source_of_truth_pack,"Before recommending direct code use, inspect the target repo row in the v6.1 operational/phase/source-audit boards. Respect copyleft_strategy_v6_1, preferred_boundary_model_v6_1, and open_compliance_if_used_as_is_v6_1. Do not assume reverse engineering is mandatory or that as-is use is always sensible.","If the repo-level strategy says bounded_sidecar_preferred or boundary_first_then_decide_as_is_vs_reimplementation, audit clean interfaces, protocol seams, subprocess/container boundaries, and what would be required to reimplement only the strategically necessary portions.",v6.3_final_source_of_truth
SCR_0073,,,,,,,,,,ScriptoriumAI repo packet,ScriptoriumAI,ScriptoriumAI re-anchored VS Code packets v1,icsharpcode/ILSpy,icsharpcode/ilspy,Reserve Bench,P3,bookmark candidate only,"Audit icsharpcode/ILSpy for ScriptoriumAI. Start from the reanchored bucket 'Reserve Bench' and current reality status 'bookmark candidate only'. Confirm actual implemented capability, hidden reusable modules, extension seams, and whether it strengthens the existing Weak or ambiguous adjacent candidate lane. Focus on: Inspect package/module map; entrypoints; config and schema files; adapters/integrations; persistence model; tests/examples; hidden feature flags; plugin 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 hidden admin tools, reusable services, plugin systems, import/export, analytics, background jobs, and any engine more valuable than the public README suggests.","Treat as unimplemented ScriptoriumAI candidate only. Do not let it redefine the current stack. Integrate only if a later audit proves it fills a real gap in the existing surfaces such as Dashboard, Editor, Corpus Graph, Runboard, AI Kanban, Corpus Search, Patch Review Queue, Visualizations, Whiteboard, Mind Map, PDF Intake, AI Diagram Studio, Video Studio, Research Agent, New Research Topic, Skills Manager, OpenAPI Routing, Manim Sandbox, Settings.","Repurpose here means mining for specific modules, algorithms, UI patterns, ingestion logic, workflow ideas, or export formats rather than assuming a full product transplant.",native/scriptoriumai-ui,native/ScriptoriumAI-Server,abhigyanpatwari/GitNexus,"Return concrete files/modules/adapters worth reusing and a verdict on whether the current reanchored bucket should be kept, upgraded, or downgraded.",Do not treat licensing as a filter. Do not propose replacing native foundations unless source evidence is overwhelming.,icsharpcode/ilspy,v6_unified_source_of_truth_pack,"Before recommending direct code use, inspect the target repo row in the v6.1 operational/phase/source-audit boards. Respect copyleft_strategy_v6_1, preferred_boundary_model_v6_1, and open_compliance_if_used_as_is_v6_1. Do not assume reverse engineering is mandatory or that as-is use is always sensible.","If the repo-level strategy says bounded_sidecar_preferred or boundary_first_then_decide_as_is_vs_reimplementation, audit clean interfaces, protocol seams, subprocess/container boundaries, and what would be required to reimplement only the strategically necessary portions.",v6.3_final_source_of_truth
SCR_0074,,,,,,,,,,ScriptoriumAI repo packet,ScriptoriumAI,ScriptoriumAI re-anchored VS Code packets v1,inbn/component-gallery,inbn/component-gallery,Reserve Bench,P3,bookmark candidate only,"Audit inbn/component-gallery for ScriptoriumAI. Start from the reanchored bucket 'Reserve Bench' and current reality status 'bookmark candidate only'. Confirm actual implemented capability, hidden reusable modules, extension seams, and whether it strengthens the existing Weak or ambiguous adjacent candidate lane. Focus on: 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.","Treat as unimplemented ScriptoriumAI candidate only. Do not let it redefine the current stack. Integrate only if a later audit proves it fills a real gap in the existing surfaces such as Dashboard, Editor, Corpus Graph, Runboard, AI Kanban, Corpus Search, Patch Review Queue, Visualizations, Whiteboard, Mind Map, PDF Intake, AI Diagram Studio, Video Studio, Research Agent, New Research Topic, Skills Manager, OpenAPI Routing, Manim Sandbox, Settings.","Repurpose here means mining for specific modules, algorithms, UI patterns, ingestion logic, workflow ideas, or export formats rather than assuming a full product transplant.",native/scriptoriumai-ui,native/ScriptoriumAI-Server,abhigyanpatwari/GitNexus,"Return concrete files/modules/adapters worth reusing and a verdict on whether the current reanchored bucket should be kept, upgraded, or downgraded.",Do not treat licensing as a filter. Do not propose replacing native foundations unless source evidence is overwhelming.,inbn/component-gallery,v6_unified_source_of_truth_pack,"Before recommending direct code use, inspect the target repo row in the v6.1 operational/phase/source-audit boards. Respect copyleft_strategy_v6_1, preferred_boundary_model_v6_1, and open_compliance_if_used_as_is_v6_1. Do not assume reverse engineering is mandatory or that as-is use is always sensible.","If the repo-level strategy says bounded_sidecar_preferred or boundary_first_then_decide_as_is_vs_reimplementation, audit clean interfaces, protocol seams, subprocess/container boundaries, and what would be required to reimplement only the strategically necessary portions.",v6.3_final_source_of_truth
SCR_0075,,,,,,,,,,ScriptoriumAI repo packet,ScriptoriumAI,ScriptoriumAI re-anchored VS Code packets v1,isocpp/CppCoreGuidelines,isocpp/cppcoreguidelines,Reserve Bench,P3,bookmark candidate only,"Audit isocpp/CppCoreGuidelines for ScriptoriumAI. Start from the reanchored bucket 'Reserve Bench' and current reality status 'bookmark candidate only'. Confirm actual implemented capability, hidden reusable modules, extension seams, and whether it strengthens the existing Weak or ambiguous adjacent candidate lane. Focus on: 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.","Treat as unimplemented ScriptoriumAI candidate only. Do not let it redefine the current stack. Integrate only if a later audit proves it fills a real gap in the existing surfaces such as Dashboard, Editor, Corpus Graph, Runboard, AI Kanban, Corpus Search, Patch Review Queue, Visualizations, Whiteboard, Mind Map, PDF Intake, AI Diagram Studio, Video Studio, Research Agent, New Research Topic, Skills Manager, OpenAPI Routing, Manim Sandbox, Settings.","Repurpose here means mining for specific modules, algorithms, UI patterns, ingestion logic, workflow ideas, or export formats rather than assuming a full product transplant.",native/scriptoriumai-ui,native/ScriptoriumAI-Server,abhigyanpatwari/GitNexus,"Return concrete files/modules/adapters worth reusing and a verdict on whether the current reanchored bucket should be kept, upgraded, or downgraded.",Do not treat licensing as a filter. Do not propose replacing native foundations unless source evidence is overwhelming.,isocpp/cppcoreguidelines,v6_unified_source_of_truth_pack,"Before recommending direct code use, inspect the target repo row in the v6.1 operational/phase/source-audit boards. Respect copyleft_strategy_v6_1, preferred_boundary_model_v6_1, and open_compliance_if_used_as_is_v6_1. Do not assume reverse engineering is mandatory or that as-is use is always sensible.","If the repo-level strategy says bounded_sidecar_preferred or boundary_first_then_decide_as_is_vs_reimplementation, audit clean interfaces, protocol seams, subprocess/container boundaries, and what would be required to reimplement only the strategically necessary portions.",v6.3_final_source_of_truth
SCR_0076,,,,,,,,,,ScriptoriumAI repo packet,ScriptoriumAI,ScriptoriumAI re-anchored VS Code packets v1,jlevy/the-art-of-command-line,jlevy/the-art-of-command-line,Reserve Bench,P3,bookmark candidate only,"Audit jlevy/the-art-of-command-line for ScriptoriumAI. Start from the reanchored bucket 'Reserve Bench' and current reality status 'bookmark candidate only'. Confirm actual implemented capability, hidden reusable modules, extension seams, and whether it strengthens the existing Weak or ambiguous adjacent candidate lane. Focus on: Inspect parsers and language adapters; graph schema and storage; incremental indexing/update logic; layout engine; query API; export/import formats; test fixtures for graph correctness.","Inspect package manifests, README/docs, src tree, examples, tests, CI workflows, config files, migrations/schemas, and hidden feature flags or experimental modules. Look for hidden admin tools, reusable services, plugin systems, import/export, analytics, background jobs, and any engine more valuable than the public README suggests.","Treat as unimplemented ScriptoriumAI candidate only. Do not let it redefine the current stack. Integrate only if a later audit proves it fills a real gap in the existing surfaces such as Dashboard, Editor, Corpus Graph, Runboard, AI Kanban, Corpus Search, Patch Review Queue, Visualizations, Whiteboard, Mind Map, PDF Intake, AI Diagram Studio, Video Studio, Research Agent, New Research Topic, Skills Manager, OpenAPI Routing, Manim Sandbox, Settings.","Repurpose here means mining for specific modules, algorithms, UI patterns, ingestion logic, workflow ideas, or export formats rather than assuming a full product transplant.",native/scriptoriumai-ui,native/ScriptoriumAI-Server,abhigyanpatwari/GitNexus,"Return concrete files/modules/adapters worth reusing and a verdict on whether the current reanchored bucket should be kept, upgraded, or downgraded.",Do not treat licensing as a filter. Do not propose replacing native foundations unless source evidence is overwhelming.,jlevy/the-art-of-command-line,v6_unified_source_of_truth_pack,"Before recommending direct code use, inspect the target repo row in the v6.1 operational/phase/source-audit boards. Respect copyleft_strategy_v6_1, preferred_boundary_model_v6_1, and open_compliance_if_used_as_is_v6_1. Do not assume reverse engineering is mandatory or that as-is use is always sensible.","If the repo-level strategy says bounded_sidecar_preferred or boundary_first_then_decide_as_is_vs_reimplementation, audit clean interfaces, protocol seams, subprocess/container boundaries, and what would be required to reimplement only the strategically necessary portions.",v6.3_final_source_of_truth
SCR_0077,,,,,,,,,,ScriptoriumAI repo packet,ScriptoriumAI,ScriptoriumAI re-anchored VS Code packets v1,kilimchoi/engineering-blogs,kilimchoi/engineering-blogs,Reserve Bench,P3,bookmark candidate only,"Audit kilimchoi/engineering-blogs for ScriptoriumAI. Start from the reanchored bucket 'Reserve Bench' and current reality status 'bookmark candidate only'. Confirm actual implemented capability, hidden reusable modules, extension seams, and whether it strengthens the existing Weak or ambiguous adjacent candidate lane. Focus on: Inspect package/module map; entrypoints; config and schema files; adapters/integrations; persistence model; tests/examples; hidden feature flags; plugin 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 hidden admin tools, reusable services, plugin systems, import/export, analytics, background jobs, and any engine more valuable than the public README suggests.","Treat as unimplemented ScriptoriumAI candidate only. Do not let it redefine the current stack. Integrate only if a later audit proves it fills a real gap in the existing surfaces such as Dashboard, Editor, Corpus Graph, Runboard, AI Kanban, Corpus Search, Patch Review Queue, Visualizations, Whiteboard, Mind Map, PDF Intake, AI Diagram Studio, Video Studio, Research Agent, New Research Topic, Skills Manager, OpenAPI Routing, Manim Sandbox, Settings.","Repurpose here means mining for specific modules, algorithms, UI patterns, ingestion logic, workflow ideas, or export formats rather than assuming a full product transplant.",native/scriptoriumai-ui,native/ScriptoriumAI-Server,abhigyanpatwari/GitNexus,"Return concrete files/modules/adapters worth reusing and a verdict on whether the current reanchored bucket should be kept, upgraded, or downgraded.",Do not treat licensing as a filter. Do not propose replacing native foundations unless source evidence is overwhelming.,kilimchoi/engineering-blogs,v6_unified_source_of_truth_pack,"Before recommending direct code use, inspect the target repo row in the v6.1 operational/phase/source-audit boards. Respect copyleft_strategy_v6_1, preferred_boundary_model_v6_1, and open_compliance_if_used_as_is_v6_1. Do not assume reverse engineering is mandatory or that as-is use is always sensible.","If the repo-level strategy says bounded_sidecar_preferred or boundary_first_then_decide_as_is_vs_reimplementation, audit clean interfaces, protocol seams, subprocess/container boundaries, and what would be required to reimplement only the strategically necessary portions.",v6.3_final_source_of_truth
SCR_0078,,,,,,,,,,ScriptoriumAI repo packet,ScriptoriumAI,ScriptoriumAI re-anchored VS Code packets v1,kolibril13/mobject-gallery,kolibril13/mobject-gallery,Reserve Bench,P3,bookmark candidate only,"Audit kolibril13/mobject-gallery for ScriptoriumAI. Start from the reanchored bucket 'Reserve Bench' and current reality status 'bookmark candidate only'. Confirm actual implemented capability, hidden reusable modules, extension seams, and whether it strengthens the existing Weak or ambiguous adjacent candidate lane. Focus on: Inspect hidden modules, extension seams, data contracts, rendering paths, auth/storage coupling, and export/import boundaries.",,"Treat as unimplemented ScriptoriumAI candidate only. Do not let it redefine the current stack. Integrate only if a later audit proves it fills a real gap in the existing surfaces such as Dashboard, Editor, Corpus Graph, Runboard, AI Kanban, Corpus Search, Patch Review Queue, Visualizations, Whiteboard, Mind Map, PDF Intake, AI Diagram Studio, Video Studio, Research Agent, New Research Topic, Skills Manager, OpenAPI Routing, Manim Sandbox, Settings.","Repurpose here means mining for specific modules, algorithms, UI patterns, ingestion logic, workflow ideas, or export formats rather than assuming a full product transplant.",manimcommunity/manim,remotion-dev/remotion,native/ScriptoriumAI-Visualizer,"Return concrete files/modules/adapters worth reusing and a verdict on whether the current reanchored bucket should be kept, upgraded, or downgraded.",Do not treat licensing as a filter. Do not propose replacing native foundations unless source evidence is overwhelming.,kolibril13/mobject-gallery,v6_unified_source_of_truth_pack,"Before recommending direct code use, inspect the target repo row in the v6.1 operational/phase/source-audit boards. Respect copyleft_strategy_v6_1, preferred_boundary_model_v6_1, and open_compliance_if_used_as_is_v6_1. Do not assume reverse engineering is mandatory or that as-is use is always sensible.","If the repo-level strategy says bounded_sidecar_preferred or boundary_first_then_decide_as_is_vs_reimplementation, audit clean interfaces, protocol seams, subprocess/container boundaries, and what would be required to reimplement only the strategically necessary portions.",v6.3_final_source_of_truth
SCR_0079,,,,,,,,,,ScriptoriumAI repo packet,ScriptoriumAI,ScriptoriumAI re-anchored VS Code packets v1,liquid-glass-react/liquid-glass-react,liquid-glass-react/liquid-glass-react,Reserve Bench,P3,bookmark candidate only,"Audit liquid-glass-react/liquid-glass-react for ScriptoriumAI. Start from the reanchored bucket 'Reserve Bench' and current reality status 'bookmark candidate only'. Confirm actual implemented capability, hidden reusable modules, extension seams, and whether it strengthens the existing Weak or ambiguous adjacent candidate lane. Focus on: Inspect hidden modules, extension seams, data contracts, rendering paths, auth/storage coupling, and export/import boundaries.",,"Treat as unimplemented ScriptoriumAI candidate only. Do not let it redefine the current stack. Integrate only if a later audit proves it fills a real gap in the existing surfaces such as Dashboard, Editor, Corpus Graph, Runboard, AI Kanban, Corpus Search, Patch Review Queue, Visualizations, Whiteboard, Mind Map, PDF Intake, AI Diagram Studio, Video Studio, Research Agent, New Research Topic, Skills Manager, OpenAPI Routing, Manim Sandbox, Settings.","Repurpose here means mining for specific modules, algorithms, UI patterns, ingestion logic, workflow ideas, or export formats rather than assuming a full product transplant.",native/scriptoriumai-ui,excalidraw/excalidraw,jgraph/drawio,"Return concrete files/modules/adapters worth reusing and a verdict on whether the current reanchored bucket should be kept, upgraded, or downgraded.",Do not treat licensing as a filter. Do not propose replacing native foundations unless source evidence is overwhelming.,liquid-glass-react/liquid-glass-react,v6_unified_source_of_truth_pack,"Before recommending direct code use, inspect the target repo row in the v6.1 operational/phase/source-audit boards. Respect copyleft_strategy_v6_1, preferred_boundary_model_v6_1, and open_compliance_if_used_as_is_v6_1. Do not assume reverse engineering is mandatory or that as-is use is always sensible.","If the repo-level strategy says bounded_sidecar_preferred or boundary_first_then_decide_as_is_vs_reimplementation, audit clean interfaces, protocol seams, subprocess/container boundaries, and what would be required to reimplement only the strategically necessary portions.",v6.3_final_source_of_truth
SCR_0080,,,,,,,,,,ScriptoriumAI repo packet,ScriptoriumAI,ScriptoriumAI re-anchored VS Code packets v1,localstack/localstack,localstack/localstack,Reserve Bench,P3,bookmark candidate only,"Audit localstack/localstack for ScriptoriumAI. Start from the reanchored bucket 'Reserve Bench' and current reality status 'bookmark candidate only'. Confirm actual implemented capability, hidden reusable modules, extension seams, and whether it strengthens the existing Weak or ambiguous adjacent candidate lane. Focus on: Inspect parsers and language adapters; graph schema and storage; incremental indexing/update logic; layout engine; query API; export/import formats; test fixtures for graph correctness.","Inspect package manifests, README/docs, src tree, examples, tests, CI workflows, config files, migrations/schemas, and hidden feature flags or experimental modules. Look for event schemas, ingestion pipelines, queue/job workers, service adapters, deployment/runtime config, RBAC/auth, alerting, and API contract generators.","Treat as unimplemented ScriptoriumAI candidate only. Do not let it redefine the current stack. Integrate only if a later audit proves it fills a real gap in the existing surfaces such as Dashboard, Editor, Corpus Graph, Runboard, AI Kanban, Corpus Search, Patch Review Queue, Visualizations, Whiteboard, Mind Map, PDF Intake, AI Diagram Studio, Video Studio, Research Agent, New Research Topic, Skills Manager, OpenAPI Routing, Manim Sandbox, Settings.","Repurpose here means mining for specific modules, algorithms, UI patterns, ingestion logic, workflow ideas, or export formats rather than assuming a full product transplant.",native/scriptoriumai-ui,native/ScriptoriumAI-Server,abhigyanpatwari/GitNexus,"Return concrete files/modules/adapters worth reusing and a verdict on whether the current reanchored bucket should be kept, upgraded, or downgraded.",Do not treat licensing as a filter. Do not propose replacing native foundations unless source evidence is overwhelming.,localstack/localstack,v6_unified_source_of_truth_pack,"Before recommending direct code use, inspect the target repo row in the v6.1 operational/phase/source-audit boards. Respect copyleft_strategy_v6_1, preferred_boundary_model_v6_1, and open_compliance_if_used_as_is_v6_1. Do not assume reverse engineering is mandatory or that as-is use is always sensible.","If the repo-level strategy says bounded_sidecar_preferred or boundary_first_then_decide_as_is_vs_reimplementation, audit clean interfaces, protocol seams, subprocess/container boundaries, and what would be required to reimplement only the strategically necessary portions.",v6.3_final_source_of_truth
SCR_0081,,,,,,,,,,ScriptoriumAI repo packet,ScriptoriumAI,ScriptoriumAI re-anchored VS Code packets v1,maxgfr/csv-ai-analyzer,maxgfr/csv-ai-analyzer,Reserve Bench,P3,bookmark candidate only,"Audit maxgfr/csv-ai-analyzer for ScriptoriumAI. Start from the reanchored bucket 'Reserve Bench' and current reality status 'bookmark candidate only'. Confirm actual implemented capability, hidden reusable modules, extension seams, and whether it strengthens the existing Weak or ambiguous adjacent candidate lane. Focus on: Inspect parsers and language adapters; graph schema and storage; incremental indexing/update logic; layout engine; query API; export/import formats; test fixtures for graph correctness.","Inspect package manifests, README/docs, src tree, examples, tests, CI workflows, config files, migrations/schemas, and hidden feature flags or experimental modules. Look for hidden admin tools, reusable services, plugin systems, import/export, analytics, background jobs, and any engine more valuable than the public README suggests.","Treat as unimplemented ScriptoriumAI candidate only. Do not let it redefine the current stack. Integrate only if a later audit proves it fills a real gap in the existing surfaces such as Dashboard, Editor, Corpus Graph, Runboard, AI Kanban, Corpus Search, Patch Review Queue, Visualizations, Whiteboard, Mind Map, PDF Intake, AI Diagram Studio, Video Studio, Research Agent, New Research Topic, Skills Manager, OpenAPI Routing, Manim Sandbox, Settings.","Repurpose here means mining for specific modules, algorithms, UI patterns, ingestion logic, workflow ideas, or export formats rather than assuming a full product transplant.",native/scriptoriumai-ui,native/ScriptoriumAI-Server,abhigyanpatwari/GitNexus,"Return concrete files/modules/adapters worth reusing and a verdict on whether the current reanchored bucket should be kept, upgraded, or downgraded.",Do not treat licensing as a filter. Do not propose replacing native foundations unless source evidence is overwhelming.,maxgfr/csv-ai-analyzer,v6_unified_source_of_truth_pack,"Before recommending direct code use, inspect the target repo row in the v6.1 operational/phase/source-audit boards. Respect copyleft_strategy_v6_1, preferred_boundary_model_v6_1, and open_compliance_if_used_as_is_v6_1. Do not assume reverse engineering is mandatory or that as-is use is always sensible.","If the repo-level strategy says bounded_sidecar_preferred or boundary_first_then_decide_as_is_vs_reimplementation, audit clean interfaces, protocol seams, subprocess/container boundaries, and what would be required to reimplement only the strategically necessary portions.",v6.3_final_source_of_truth
SCR_0082,,,,,,,,,,ScriptoriumAI repo packet,ScriptoriumAI,ScriptoriumAI re-anchored VS Code packets v1,microsoft/CsWin32,microsoft/cswin32,Reserve Bench,P3,bookmark candidate only,"Audit microsoft/CsWin32 for ScriptoriumAI. Start from the reanchored bucket 'Reserve Bench' and current reality status 'bookmark candidate only'. Confirm actual implemented capability, hidden reusable modules, extension seams, and whether it strengthens the existing Weak or ambiguous adjacent candidate lane. Focus on: Inspect package/module map; entrypoints; config and schema files; adapters/integrations; persistence model; tests/examples; hidden feature flags; plugin 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 hidden admin tools, reusable services, plugin systems, import/export, analytics, background jobs, and any engine more valuable than the public README suggests.","Treat as unimplemented ScriptoriumAI candidate only. Do not let it redefine the current stack. Integrate only if a later audit proves it fills a real gap in the existing surfaces such as Dashboard, Editor, Corpus Graph, Runboard, AI Kanban, Corpus Search, Patch Review Queue, Visualizations, Whiteboard, Mind Map, PDF Intake, AI Diagram Studio, Video Studio, Research Agent, New Research Topic, Skills Manager, OpenAPI Routing, Manim Sandbox, Settings.","Repurpose here means mining for specific modules, algorithms, UI patterns, ingestion logic, workflow ideas, or export formats rather than assuming a full product transplant.",native/scriptoriumai-ui,native/ScriptoriumAI-Server,abhigyanpatwari/GitNexus,"Return concrete files/modules/adapters worth reusing and a verdict on whether the current reanchored bucket should be kept, upgraded, or downgraded.",Do not treat licensing as a filter. Do not propose replacing native foundations unless source evidence is overwhelming.,microsoft/cswin32,v6_unified_source_of_truth_pack,"Before recommending direct code use, inspect the target repo row in the v6.1 operational/phase/source-audit boards. Respect copyleft_strategy_v6_1, preferred_boundary_model_v6_1, and open_compliance_if_used_as_is_v6_1. Do not assume reverse engineering is mandatory or that as-is use is always sensible.","If the repo-level strategy says bounded_sidecar_preferred or boundary_first_then_decide_as_is_vs_reimplementation, audit clean interfaces, protocol seams, subprocess/container boundaries, and what would be required to reimplement only the strategically necessary portions.",v6.3_final_source_of_truth
SCR_0083,,,,,,,,,,ScriptoriumAI repo packet,ScriptoriumAI,ScriptoriumAI re-anchored VS Code packets v1,microsoft/playwright,microsoft/playwright,Reserve Bench,P3,bookmark candidate only,"Audit microsoft/playwright for ScriptoriumAI. Start from the reanchored bucket 'Reserve Bench' and current reality status 'bookmark candidate only'. Confirm actual implemented capability, hidden reusable modules, extension seams, and whether it strengthens the existing Weak or ambiguous adjacent candidate lane. Focus on: 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 event schemas, ingestion pipelines, queue/job workers, service adapters, deployment/runtime config, RBAC/auth, alerting, and API contract generators.","Treat as unimplemented ScriptoriumAI candidate only. Do not let it redefine the current stack. Integrate only if a later audit proves it fills a real gap in the existing surfaces such as Dashboard, Editor, Corpus Graph, Runboard, AI Kanban, Corpus Search, Patch Review Queue, Visualizations, Whiteboard, Mind Map, PDF Intake, AI Diagram Studio, Video Studio, Research Agent, New Research Topic, Skills Manager, OpenAPI Routing, Manim Sandbox, Settings.","Repurpose here means mining for specific modules, algorithms, UI patterns, ingestion logic, workflow ideas, or export formats rather than assuming a full product transplant.",native/scriptoriumai-ui,native/ScriptoriumAI-Server,abhigyanpatwari/GitNexus,"Return concrete files/modules/adapters worth reusing and a verdict on whether the current reanchored bucket should be kept, upgraded, or downgraded.",Do not treat licensing as a filter. Do not propose replacing native foundations unless source evidence is overwhelming.,microsoft/playwright,v6_unified_source_of_truth_pack,"Before recommending direct code use, inspect the target repo row in the v6.1 operational/phase/source-audit boards. Respect copyleft_strategy_v6_1, preferred_boundary_model_v6_1, and open_compliance_if_used_as_is_v6_1. Do not assume reverse engineering is mandatory or that as-is use is always sensible.","If the repo-level strategy says bounded_sidecar_preferred or boundary_first_then_decide_as_is_vs_reimplementation, audit clean interfaces, protocol seams, subprocess/container boundaries, and what would be required to reimplement only the strategically necessary portions.",v6.3_final_source_of_truth
SCR_0084,,,,,,,,,,ScriptoriumAI repo packet,ScriptoriumAI,ScriptoriumAI re-anchored VS Code packets v1,midudev/jscamp,midudev/jscamp,Reserve Bench,P3,bookmark candidate only,"Audit midudev/jscamp for ScriptoriumAI. Start from the reanchored bucket 'Reserve Bench' and current reality status 'bookmark candidate only'. Confirm actual implemented capability, hidden reusable modules, extension seams, and whether it strengthens the existing Weak or ambiguous adjacent candidate lane. Focus on: Inspect package/module map; entrypoints; config and schema files; adapters/integrations; persistence model; tests/examples; hidden feature flags; plugin 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 hidden admin tools, reusable services, plugin systems, import/export, analytics, background jobs, and any engine more valuable than the public README suggests.","Treat as unimplemented ScriptoriumAI candidate only. Do not let it redefine the current stack. Integrate only if a later audit proves it fills a real gap in the existing surfaces such as Dashboard, Editor, Corpus Graph, Runboard, AI Kanban, Corpus Search, Patch Review Queue, Visualizations, Whiteboard, Mind Map, PDF Intake, AI Diagram Studio, Video Studio, Research Agent, New Research Topic, Skills Manager, OpenAPI Routing, Manim Sandbox, Settings.","Repurpose here means mining for specific modules, algorithms, UI patterns, ingestion logic, workflow ideas, or export formats rather than assuming a full product transplant.",native/scriptoriumai-ui,native/ScriptoriumAI-Server,abhigyanpatwari/GitNexus,"Return concrete files/modules/adapters worth reusing and a verdict on whether the current reanchored bucket should be kept, upgraded, or downgraded.",Do not treat licensing as a filter. Do not propose replacing native foundations unless source evidence is overwhelming.,midudev/jscamp,v6_unified_source_of_truth_pack,"Before recommending direct code use, inspect the target repo row in the v6.1 operational/phase/source-audit boards. Respect copyleft_strategy_v6_1, preferred_boundary_model_v6_1, and open_compliance_if_used_as_is_v6_1. Do not assume reverse engineering is mandatory or that as-is use is always sensible.","If the repo-level strategy says bounded_sidecar_preferred or boundary_first_then_decide_as_is_vs_reimplementation, audit clean interfaces, protocol seams, subprocess/container boundaries, and what would be required to reimplement only the strategically necessary portions.",v6.3_final_source_of_truth
SCR_0085,,,,,,,,,,ScriptoriumAI repo packet,ScriptoriumAI,ScriptoriumAI re-anchored VS Code packets v1,minimaxir/big-list-of-naughty-strings,minimaxir/big-list-of-naughty-strings,Reserve Bench,P3,bookmark candidate only,"Audit minimaxir/big-list-of-naughty-strings for ScriptoriumAI. Start from the reanchored bucket 'Reserve Bench' and current reality status 'bookmark candidate only'. Confirm actual implemented capability, hidden reusable modules, extension seams, and whether it strengthens the existing Weak or ambiguous adjacent candidate lane. Focus on: Inspect package/module map; entrypoints; config and schema files; adapters/integrations; persistence model; tests/examples; hidden feature flags; plugin 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 hidden admin tools, reusable services, plugin systems, import/export, analytics, background jobs, and any engine more valuable than the public README suggests.","Treat as unimplemented ScriptoriumAI candidate only. Do not let it redefine the current stack. Integrate only if a later audit proves it fills a real gap in the existing surfaces such as Dashboard, Editor, Corpus Graph, Runboard, AI Kanban, Corpus Search, Patch Review Queue, Visualizations, Whiteboard, Mind Map, PDF Intake, AI Diagram Studio, Video Studio, Research Agent, New Research Topic, Skills Manager, OpenAPI Routing, Manim Sandbox, Settings.","Repurpose here means mining for specific modules, algorithms, UI patterns, ingestion logic, workflow ideas, or export formats rather than assuming a full product transplant.",native/scriptoriumai-ui,native/ScriptoriumAI-Server,abhigyanpatwari/GitNexus,"Return concrete files/modules/adapters worth reusing and a verdict on whether the current reanchored bucket should be kept, upgraded, or downgraded.",Do not treat licensing as a filter. Do not propose replacing native foundations unless source evidence is overwhelming.,minimaxir/big-list-of-naughty-strings,v6_unified_source_of_truth_pack,"Before recommending direct code use, inspect the target repo row in the v6.1 operational/phase/source-audit boards. Respect copyleft_strategy_v6_1, preferred_boundary_model_v6_1, and open_compliance_if_used_as_is_v6_1. Do not assume reverse engineering is mandatory or that as-is use is always sensible.","If the repo-level strategy says bounded_sidecar_preferred or boundary_first_then_decide_as_is_vs_reimplementation, audit clean interfaces, protocol seams, subprocess/container boundaries, and what would be required to reimplement only the strategically necessary portions.",v6.3_final_source_of_truth
SCR_0086,,,,,,,,,,ScriptoriumAI repo packet,ScriptoriumAI,ScriptoriumAI re-anchored VS Code packets v1,nari-labs/dia2,nari-labs/dia2,Reserve Bench,P3,bookmark candidate only,"Audit nari-labs/dia2 for ScriptoriumAI. Start from the reanchored bucket 'Reserve Bench' and current reality status 'bookmark candidate only'. Confirm actual implemented capability, hidden reusable modules, extension seams, and whether it strengthens the existing Weak or ambiguous adjacent candidate lane. Focus on: 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.","Treat as unimplemented ScriptoriumAI candidate only. Do not let it redefine the current stack. Integrate only if a later audit proves it fills a real gap in the existing surfaces such as Dashboard, Editor, Corpus Graph, Runboard, AI Kanban, Corpus Search, Patch Review Queue, Visualizations, Whiteboard, Mind Map, PDF Intake, AI Diagram Studio, Video Studio, Research Agent, New Research Topic, Skills Manager, OpenAPI Routing, Manim Sandbox, Settings.","Repurpose here means mining for specific modules, algorithms, UI patterns, ingestion logic, workflow ideas, or export formats rather than assuming a full product transplant.",native/scriptoriumai-ui,native/ScriptoriumAI-Server,abhigyanpatwari/GitNexus,"Return concrete files/modules/adapters worth reusing and a verdict on whether the current reanchored bucket should be kept, upgraded, or downgraded.",Do not treat licensing as a filter. Do not propose replacing native foundations unless source evidence is overwhelming.,nari-labs/dia2,v6_unified_source_of_truth_pack,"Before recommending direct code use, inspect the target repo row in the v6.1 operational/phase/source-audit boards. Respect copyleft_strategy_v6_1, preferred_boundary_model_v6_1, and open_compliance_if_used_as_is_v6_1. Do not assume reverse engineering is mandatory or that as-is use is always sensible.","If the repo-level strategy says bounded_sidecar_preferred or boundary_first_then_decide_as_is_vs_reimplementation, audit clean interfaces, protocol seams, subprocess/container boundaries, and what would be required to reimplement only the strategically necessary portions.",v6.3_final_source_of_truth
SCR_0087,,,,,,,,,,ScriptoriumAI repo packet,ScriptoriumAI,ScriptoriumAI re-anchored VS Code packets v1,neuphonic/neutts-air,neuphonic/neutts-air,Reserve Bench,P3,bookmark candidate only,"Audit neuphonic/neutts-air for ScriptoriumAI. Start from the reanchored bucket 'Reserve Bench' and current reality status 'bookmark candidate only'. Confirm actual implemented capability, hidden reusable modules, extension seams, and whether it strengthens the existing Weak or ambiguous adjacent candidate lane. Focus on: Inspect streaming pipeline; VAD/segmentation; device abstraction; latency handling; multilingual or translation chain; local/offline fallback; API wrappers.","Inspect package manifests, README/docs, src tree, examples, tests, CI workflows, config files, migrations/schemas, and hidden feature flags or experimental modules. Look for streaming, VAD, wakeword, buffering, diarization, device handling, latency compensation, and command grammar or transcript post-processing.","Treat as unimplemented ScriptoriumAI candidate only. Do not let it redefine the current stack. Integrate only if a later audit proves it fills a real gap in the existing surfaces such as Dashboard, Editor, Corpus Graph, Runboard, AI Kanban, Corpus Search, Patch Review Queue, Visualizations, Whiteboard, Mind Map, PDF Intake, AI Diagram Studio, Video Studio, Research Agent, New Research Topic, Skills Manager, OpenAPI Routing, Manim Sandbox, Settings.","Repurpose here means mining for specific modules, algorithms, UI patterns, ingestion logic, workflow ideas, or export formats rather than assuming a full product transplant.",native/scriptoriumai-ui,native/ScriptoriumAI-Server,abhigyanpatwari/GitNexus,"Return concrete files/modules/adapters worth reusing and a verdict on whether the current reanchored bucket should be kept, upgraded, or downgraded.",Do not treat licensing as a filter. Do not propose replacing native foundations unless source evidence is overwhelming.,neuphonic/neutts-air,v6_unified_source_of_truth_pack,"Before recommending direct code use, inspect the target repo row in the v6.1 operational/phase/source-audit boards. Respect copyleft_strategy_v6_1, preferred_boundary_model_v6_1, and open_compliance_if_used_as_is_v6_1. Do not assume reverse engineering is mandatory or that as-is use is always sensible.","If the repo-level strategy says bounded_sidecar_preferred or boundary_first_then_decide_as_is_vs_reimplementation, audit clean interfaces, protocol seams, subprocess/container boundaries, and what would be required to reimplement only the strategically necessary portions.",v6.3_final_source_of_truth
SCR_0088,,,,,,,,,,ScriptoriumAI repo packet,ScriptoriumAI,ScriptoriumAI re-anchored VS Code packets v1,nordtheme/dircolors,nordtheme/dircolors,Reserve Bench,P3,bookmark candidate only,"Audit nordtheme/dircolors for ScriptoriumAI. Start from the reanchored bucket 'Reserve Bench' and current reality status 'bookmark candidate only'. Confirm actual implemented capability, hidden reusable modules, extension seams, and whether it strengthens the existing Weak or ambiguous adjacent candidate lane. Focus on: 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.","Treat as unimplemented ScriptoriumAI candidate only. Do not let it redefine the current stack. Integrate only if a later audit proves it fills a real gap in the existing surfaces such as Dashboard, Editor, Corpus Graph, Runboard, AI Kanban, Corpus Search, Patch Review Queue, Visualizations, Whiteboard, Mind Map, PDF Intake, AI Diagram Studio, Video Studio, Research Agent, New Research Topic, Skills Manager, OpenAPI Routing, Manim Sandbox, Settings.","Repurpose here means mining for specific modules, algorithms, UI patterns, ingestion logic, workflow ideas, or export formats rather than assuming a full product transplant.",native/scriptoriumai-ui,native/ScriptoriumAI-Server,abhigyanpatwari/GitNexus,"Return concrete files/modules/adapters worth reusing and a verdict on whether the current reanchored bucket should be kept, upgraded, or downgraded.",Do not treat licensing as a filter. Do not propose replacing native foundations unless source evidence is overwhelming.,nordtheme/dircolors,v6_unified_source_of_truth_pack,"Before recommending direct code use, inspect the target repo row in the v6.1 operational/phase/source-audit boards. Respect copyleft_strategy_v6_1, preferred_boundary_model_v6_1, and open_compliance_if_used_as_is_v6_1. Do not assume reverse engineering is mandatory or that as-is use is always sensible.","If the repo-level strategy says bounded_sidecar_preferred or boundary_first_then_decide_as_is_vs_reimplementation, audit clean interfaces, protocol seams, subprocess/container boundaries, and what would be required to reimplement only the strategically necessary portions.",v6.3_final_source_of_truth
SCR_0089,,,,,,,,,,ScriptoriumAI repo packet,ScriptoriumAI,ScriptoriumAI re-anchored VS Code packets v1,ossu/computer-science,ossu/computer-science,Reserve Bench,P3,bookmark candidate only,"Audit ossu/computer-science for ScriptoriumAI. Start from the reanchored bucket 'Reserve Bench' and current reality status 'bookmark candidate only'. Confirm actual implemented capability, hidden reusable modules, extension seams, and whether it strengthens the existing Weak or ambiguous adjacent candidate lane. Focus on: Inspect package/module map; entrypoints; config and schema files; adapters/integrations; persistence model; tests/examples; hidden feature flags; plugin 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 hidden admin tools, reusable services, plugin systems, import/export, analytics, background jobs, and any engine more valuable than the public README suggests.","Treat as unimplemented ScriptoriumAI candidate only. Do not let it redefine the current stack. Integrate only if a later audit proves it fills a real gap in the existing surfaces such as Dashboard, Editor, Corpus Graph, Runboard, AI Kanban, Corpus Search, Patch Review Queue, Visualizations, Whiteboard, Mind Map, PDF Intake, AI Diagram Studio, Video Studio, Research Agent, New Research Topic, Skills Manager, OpenAPI Routing, Manim Sandbox, Settings.","Repurpose here means mining for specific modules, algorithms, UI patterns, ingestion logic, workflow ideas, or export formats rather than assuming a full product transplant.",native/scriptoriumai-ui,native/ScriptoriumAI-Server,abhigyanpatwari/GitNexus,"Return concrete files/modules/adapters worth reusing and a verdict on whether the current reanchored bucket should be kept, upgraded, or downgraded.",Do not treat licensing as a filter. Do not propose replacing native foundations unless source evidence is overwhelming.,ossu/computer-science,v6_unified_source_of_truth_pack,"Before recommending direct code use, inspect the target repo row in the v6.1 operational/phase/source-audit boards. Respect copyleft_strategy_v6_1, preferred_boundary_model_v6_1, and open_compliance_if_used_as_is_v6_1. Do not assume reverse engineering is mandatory or that as-is use is always sensible.","If the repo-level strategy says bounded_sidecar_preferred or boundary_first_then_decide_as_is_vs_reimplementation, audit clean interfaces, protocol seams, subprocess/container boundaries, and what would be required to reimplement only the strategically necessary portions.",v6.3_final_source_of_truth
SCR_0090,,,,,,,,,,ScriptoriumAI repo packet,ScriptoriumAI,ScriptoriumAI re-anchored VS Code packets v1,pbakaus/radiant,pbakaus/radiant,Reserve Bench,P3,bookmark candidate only,"Audit pbakaus/radiant for ScriptoriumAI. Start from the reanchored bucket 'Reserve Bench' and current reality status 'bookmark candidate only'. Confirm actual implemented capability, hidden reusable modules, extension seams, and whether it strengthens the existing Weak or ambiguous adjacent candidate lane. Focus on: Inspect parsers and language adapters; graph schema and storage; incremental indexing/update logic; layout engine; query API; export/import formats; test fixtures for graph correctness.","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.","Treat as unimplemented ScriptoriumAI candidate only. Do not let it redefine the current stack. Integrate only if a later audit proves it fills a real gap in the existing surfaces such as Dashboard, Editor, Corpus Graph, Runboard, AI Kanban, Corpus Search, Patch Review Queue, Visualizations, Whiteboard, Mind Map, PDF Intake, AI Diagram Studio, Video Studio, Research Agent, New Research Topic, Skills Manager, OpenAPI Routing, Manim Sandbox, Settings.","Repurpose here means mining for specific modules, algorithms, UI patterns, ingestion logic, workflow ideas, or export formats rather than assuming a full product transplant.",native/scriptoriumai-ui,native/ScriptoriumAI-Server,abhigyanpatwari/GitNexus,"Return concrete files/modules/adapters worth reusing and a verdict on whether the current reanchored bucket should be kept, upgraded, or downgraded.",Do not treat licensing as a filter. Do not propose replacing native foundations unless source evidence is overwhelming.,pbakaus/radiant,v6_unified_source_of_truth_pack,"Before recommending direct code use, inspect the target repo row in the v6.1 operational/phase/source-audit boards. Respect copyleft_strategy_v6_1, preferred_boundary_model_v6_1, and open_compliance_if_used_as_is_v6_1. Do not assume reverse engineering is mandatory or that as-is use is always sensible.","If the repo-level strategy says bounded_sidecar_preferred or boundary_first_then_decide_as_is_vs_reimplementation, audit clean interfaces, protocol seams, subprocess/container boundaries, and what would be required to reimplement only the strategically necessary portions.",v6.3_final_source_of_truth
SCR_0091,,,,,,,,,,ScriptoriumAI repo packet,ScriptoriumAI,ScriptoriumAI re-anchored VS Code packets v1,plausible/analytics,plausible/analytics,Reserve Bench,P3,bookmark candidate only,"Audit plausible/analytics for ScriptoriumAI. Start from the reanchored bucket 'Reserve Bench' and current reality status 'bookmark candidate only'. Confirm actual implemented capability, hidden reusable modules, extension seams, and whether it strengthens the existing Weak or ambiguous adjacent candidate lane. Focus on: Inspect parsers and language adapters; graph schema and storage; incremental indexing/update logic; layout engine; query API; export/import formats; test fixtures for graph correctness.","Inspect package manifests, README/docs, src tree, examples, tests, CI workflows, config files, migrations/schemas, and hidden feature flags or experimental modules. Look for event schemas, ingestion pipelines, queue/job workers, service adapters, deployment/runtime config, RBAC/auth, alerting, and API contract generators.","Treat as unimplemented ScriptoriumAI candidate only. Do not let it redefine the current stack. Integrate only if a later audit proves it fills a real gap in the existing surfaces such as Dashboard, Editor, Corpus Graph, Runboard, AI Kanban, Corpus Search, Patch Review Queue, Visualizations, Whiteboard, Mind Map, PDF Intake, AI Diagram Studio, Video Studio, Research Agent, New Research Topic, Skills Manager, OpenAPI Routing, Manim Sandbox, Settings.","Repurpose here means mining for specific modules, algorithms, UI patterns, ingestion logic, workflow ideas, or export formats rather than assuming a full product transplant.",native/scriptoriumai-ui,native/ScriptoriumAI-Server,abhigyanpatwari/GitNexus,"Return concrete files/modules/adapters worth reusing and a verdict on whether the current reanchored bucket should be kept, upgraded, or downgraded.",Do not treat licensing as a filter. Do not propose replacing native foundations unless source evidence is overwhelming.,plausible/analytics,v6_unified_source_of_truth_pack,"Before recommending direct code use, inspect the target repo row in the v6.1 operational/phase/source-audit boards. Respect copyleft_strategy_v6_1, preferred_boundary_model_v6_1, and open_compliance_if_used_as_is_v6_1. Do not assume reverse engineering is mandatory or that as-is use is always sensible.","If the repo-level strategy says bounded_sidecar_preferred or boundary_first_then_decide_as_is_vs_reimplementation, audit clean interfaces, protocol seams, subprocess/container boundaries, and what would be required to reimplement only the strategically necessary portions.",v6.3_final_source_of_truth
SCR_0092,,,,,,,,,,ScriptoriumAI repo packet,ScriptoriumAI,ScriptoriumAI re-anchored VS Code packets v1,ripienaar/free-for-dev,ripienaar/free-for-dev,Reserve Bench,P3,bookmark candidate only,"Audit ripienaar/free-for-dev for ScriptoriumAI. Start from the reanchored bucket 'Reserve Bench' and current reality status 'bookmark candidate only'. Confirm actual implemented capability, hidden reusable modules, extension seams, and whether it strengthens the existing Weak or ambiguous adjacent candidate lane. Focus on: 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 event schemas, ingestion pipelines, queue/job workers, service adapters, deployment/runtime config, RBAC/auth, alerting, and API contract generators.","Treat as unimplemented ScriptoriumAI candidate only. Do not let it redefine the current stack. Integrate only if a later audit proves it fills a real gap in the existing surfaces such as Dashboard, Editor, Corpus Graph, Runboard, AI Kanban, Corpus Search, Patch Review Queue, Visualizations, Whiteboard, Mind Map, PDF Intake, AI Diagram Studio, Video Studio, Research Agent, New Research Topic, Skills Manager, OpenAPI Routing, Manim Sandbox, Settings.","Repurpose here means mining for specific modules, algorithms, UI patterns, ingestion logic, workflow ideas, or export formats rather than assuming a full product transplant.",native/scriptoriumai-ui,native/ScriptoriumAI-Server,abhigyanpatwari/GitNexus,"Return concrete files/modules/adapters worth reusing and a verdict on whether the current reanchored bucket should be kept, upgraded, or downgraded.",Do not treat licensing as a filter. Do not propose replacing native foundations unless source evidence is overwhelming.,ripienaar/free-for-dev,v6_unified_source_of_truth_pack,"Before recommending direct code use, inspect the target repo row in the v6.1 operational/phase/source-audit boards. Respect copyleft_strategy_v6_1, preferred_boundary_model_v6_1, and open_compliance_if_used_as_is_v6_1. Do not assume reverse engineering is mandatory or that as-is use is always sensible.","If the repo-level strategy says bounded_sidecar_preferred or boundary_first_then_decide_as_is_vs_reimplementation, audit clean interfaces, protocol seams, subprocess/container boundaries, and what would be required to reimplement only the strategically necessary portions.",v6.3_final_source_of_truth
SCR_0093,,,,,,,,,,ScriptoriumAI repo packet,ScriptoriumAI,ScriptoriumAI re-anchored VS Code packets v1,robrich/git-explorer,robrich/git-explorer,Reserve Bench,P3,bookmark candidate only,"Audit robrich/git-explorer for ScriptoriumAI. Start from the reanchored bucket 'Reserve Bench' and current reality status 'bookmark candidate only'. Confirm actual implemented capability, hidden reusable modules, extension seams, and whether it strengthens the existing Weak or ambiguous adjacent candidate lane. Focus on: Inspect package/module map; entrypoints; config and schema files; adapters/integrations; persistence model; tests/examples; hidden feature flags; plugin 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 hidden admin tools, reusable services, plugin systems, import/export, analytics, background jobs, and any engine more valuable than the public README suggests.","Treat as unimplemented ScriptoriumAI candidate only. Do not let it redefine the current stack. Integrate only if a later audit proves it fills a real gap in the existing surfaces such as Dashboard, Editor, Corpus Graph, Runboard, AI Kanban, Corpus Search, Patch Review Queue, Visualizations, Whiteboard, Mind Map, PDF Intake, AI Diagram Studio, Video Studio, Research Agent, New Research Topic, Skills Manager, OpenAPI Routing, Manim Sandbox, Settings.","Repurpose here means mining for specific modules, algorithms, UI patterns, ingestion logic, workflow ideas, or export formats rather than assuming a full product transplant.",native/scriptoriumai-ui,native/ScriptoriumAI-Server,abhigyanpatwari/GitNexus,"Return concrete files/modules/adapters worth reusing and a verdict on whether the current reanchored bucket should be kept, upgraded, or downgraded.",Do not treat licensing as a filter. Do not propose replacing native foundations unless source evidence is overwhelming.,robrich/git-explorer,v6_unified_source_of_truth_pack,"Before recommending direct code use, inspect the target repo row in the v6.1 operational/phase/source-audit boards. Respect copyleft_strategy_v6_1, preferred_boundary_model_v6_1, and open_compliance_if_used_as_is_v6_1. Do not assume reverse engineering is mandatory or that as-is use is always sensible.","If the repo-level strategy says bounded_sidecar_preferred or boundary_first_then_decide_as_is_vs_reimplementation, audit clean interfaces, protocol seams, subprocess/container boundaries, and what would be required to reimplement only the strategically necessary portions.",v6.3_final_source_of_truth
SCR_0094,,,,,,,,,,ScriptoriumAI repo packet,ScriptoriumAI,ScriptoriumAI re-anchored VS Code packets v1,ryo-manba/data-anim,ryo-manba/data-anim,Reserve Bench,P3,bookmark candidate only,"Audit ryo-manba/data-anim for ScriptoriumAI. Start from the reanchored bucket 'Reserve Bench' and current reality status 'bookmark candidate only'. Confirm actual implemented capability, hidden reusable modules, extension seams, and whether it strengthens the existing Weak or ambiguous adjacent candidate lane. Focus on: 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.","Treat as unimplemented ScriptoriumAI candidate only. Do not let it redefine the current stack. Integrate only if a later audit proves it fills a real gap in the existing surfaces such as Dashboard, Editor, Corpus Graph, Runboard, AI Kanban, Corpus Search, Patch Review Queue, Visualizations, Whiteboard, Mind Map, PDF Intake, AI Diagram Studio, Video Studio, Research Agent, New Research Topic, Skills Manager, OpenAPI Routing, Manim Sandbox, Settings.","Repurpose here means mining for specific modules, algorithms, UI patterns, ingestion logic, workflow ideas, or export formats rather than assuming a full product transplant.",native/scriptoriumai-ui,native/ScriptoriumAI-Server,abhigyanpatwari/GitNexus,"Return concrete files/modules/adapters worth reusing and a verdict on whether the current reanchored bucket should be kept, upgraded, or downgraded.",Do not treat licensing as a filter. Do not propose replacing native foundations unless source evidence is overwhelming.,ryo-manba/data-anim,v6_unified_source_of_truth_pack,"Before recommending direct code use, inspect the target repo row in the v6.1 operational/phase/source-audit boards. Respect copyleft_strategy_v6_1, preferred_boundary_model_v6_1, and open_compliance_if_used_as_is_v6_1. Do not assume reverse engineering is mandatory or that as-is use is always sensible.","If the repo-level strategy says bounded_sidecar_preferred or boundary_first_then_decide_as_is_vs_reimplementation, audit clean interfaces, protocol seams, subprocess/container boundaries, and what would be required to reimplement only the strategically necessary portions.",v6.3_final_source_of_truth
SCR_0095,,,,,,,,,,ScriptoriumAI repo packet,ScriptoriumAI,ScriptoriumAI re-anchored VS Code packets v1,sdmg15/Best-websites-a-programmer-should-visit,sdmg15/best-websites-a-programmer-should-visit,Reserve Bench,P3,bookmark candidate only,"Audit sdmg15/Best-websites-a-programmer-should-visit for ScriptoriumAI. Start from the reanchored bucket 'Reserve Bench' and current reality status 'bookmark candidate only'. Confirm actual implemented capability, hidden reusable modules, extension seams, and whether it strengthens the existing Weak or ambiguous adjacent candidate lane. Focus on: Inspect package/module map; entrypoints; config and schema files; adapters/integrations; persistence model; tests/examples; hidden feature flags; plugin 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 hidden admin tools, reusable services, plugin systems, import/export, analytics, background jobs, and any engine more valuable than the public README suggests.","Treat as unimplemented ScriptoriumAI candidate only. Do not let it redefine the current stack. Integrate only if a later audit proves it fills a real gap in the existing surfaces such as Dashboard, Editor, Corpus Graph, Runboard, AI Kanban, Corpus Search, Patch Review Queue, Visualizations, Whiteboard, Mind Map, PDF Intake, AI Diagram Studio, Video Studio, Research Agent, New Research Topic, Skills Manager, OpenAPI Routing, Manim Sandbox, Settings.","Repurpose here means mining for specific modules, algorithms, UI patterns, ingestion logic, workflow ideas, or export formats rather than assuming a full product transplant.",native/scriptoriumai-ui,native/ScriptoriumAI-Server,abhigyanpatwari/GitNexus,"Return concrete files/modules/adapters worth reusing and a verdict on whether the current reanchored bucket should be kept, upgraded, or downgraded.",Do not treat licensing as a filter. Do not propose replacing native foundations unless source evidence is overwhelming.,sdmg15/best-websites-a-programmer-should-visit,v6_unified_source_of_truth_pack,"Before recommending direct code use, inspect the target repo row in the v6.1 operational/phase/source-audit boards. Respect copyleft_strategy_v6_1, preferred_boundary_model_v6_1, and open_compliance_if_used_as_is_v6_1. Do not assume reverse engineering is mandatory or that as-is use is always sensible.","If the repo-level strategy says bounded_sidecar_preferred or boundary_first_then_decide_as_is_vs_reimplementation, audit clean interfaces, protocol seams, subprocess/container boundaries, and what would be required to reimplement only the strategically necessary portions.",v6.3_final_source_of_truth
SCR_0096,,,,,,,,,,ScriptoriumAI repo packet,ScriptoriumAI,ScriptoriumAI re-anchored VS Code packets v1,siddharthvaddem/openscreen,siddharthvaddem/openscreen,Reserve Bench,P3,bookmark candidate only,"Audit siddharthvaddem/openscreen for ScriptoriumAI. Start from the reanchored bucket 'Reserve Bench' and current reality status 'bookmark candidate only'. Confirm actual implemented capability, hidden reusable modules, extension seams, and whether it strengthens the existing Weak or ambiguous adjacent candidate lane. Focus on: Inspect parsers and language adapters; graph schema and storage; incremental indexing/update logic; layout engine; query API; export/import formats; test fixtures for graph correctness.","Inspect package manifests, README/docs, src tree, examples, tests, CI workflows, config files, migrations/schemas, and hidden feature flags or experimental modules. Look for hidden admin tools, reusable services, plugin systems, import/export, analytics, background jobs, and any engine more valuable than the public README suggests.","Treat as unimplemented ScriptoriumAI candidate only. Do not let it redefine the current stack. Integrate only if a later audit proves it fills a real gap in the existing surfaces such as Dashboard, Editor, Corpus Graph, Runboard, AI Kanban, Corpus Search, Patch Review Queue, Visualizations, Whiteboard, Mind Map, PDF Intake, AI Diagram Studio, Video Studio, Research Agent, New Research Topic, Skills Manager, OpenAPI Routing, Manim Sandbox, Settings.","Repurpose here means mining for specific modules, algorithms, UI patterns, ingestion logic, workflow ideas, or export formats rather than assuming a full product transplant.",native/scriptoriumai-ui,native/ScriptoriumAI-Server,abhigyanpatwari/GitNexus,"Return concrete files/modules/adapters worth reusing and a verdict on whether the current reanchored bucket should be kept, upgraded, or downgraded.",Do not treat licensing as a filter. Do not propose replacing native foundations unless source evidence is overwhelming.,siddharthvaddem/openscreen,v6_unified_source_of_truth_pack,"Before recommending direct code use, inspect the target repo row in the v6.1 operational/phase/source-audit boards. Respect copyleft_strategy_v6_1, preferred_boundary_model_v6_1, and open_compliance_if_used_as_is_v6_1. Do not assume reverse engineering is mandatory or that as-is use is always sensible.","If the repo-level strategy says bounded_sidecar_preferred or boundary_first_then_decide_as_is_vs_reimplementation, audit clean interfaces, protocol seams, subprocess/container boundaries, and what would be required to reimplement only the strategically necessary portions.",v6.3_final_source_of_truth
SCR_0097,,,,,,,,,,ScriptoriumAI repo packet,ScriptoriumAI,ScriptoriumAI re-anchored VS Code packets v1,stepfun-ai/Step-Audio-EditX,stepfun-ai/step-audio-editx,Reserve Bench,P3,bookmark candidate only,"Audit stepfun-ai/Step-Audio-EditX for ScriptoriumAI. Start from the reanchored bucket 'Reserve Bench' and current reality status 'bookmark candidate only'. Confirm actual implemented capability, hidden reusable modules, extension seams, and whether it strengthens the existing Weak or ambiguous adjacent candidate lane. Focus on: 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.","Treat as unimplemented ScriptoriumAI candidate only. Do not let it redefine the current stack. Integrate only if a later audit proves it fills a real gap in the existing surfaces such as Dashboard, Editor, Corpus Graph, Runboard, AI Kanban, Corpus Search, Patch Review Queue, Visualizations, Whiteboard, Mind Map, PDF Intake, AI Diagram Studio, Video Studio, Research Agent, New Research Topic, Skills Manager, OpenAPI Routing, Manim Sandbox, Settings.","Repurpose here means mining for specific modules, algorithms, UI patterns, ingestion logic, workflow ideas, or export formats rather than assuming a full product transplant.",native/scriptoriumai-ui,native/ScriptoriumAI-Server,abhigyanpatwari/GitNexus,"Return concrete files/modules/adapters worth reusing and a verdict on whether the current reanchored bucket should be kept, upgraded, or downgraded.",Do not treat licensing as a filter. Do not propose replacing native foundations unless source evidence is overwhelming.,stepfun-ai/step-audio-editx,v6_unified_source_of_truth_pack,"Before recommending direct code use, inspect the target repo row in the v6.1 operational/phase/source-audit boards. Respect copyleft_strategy_v6_1, preferred_boundary_model_v6_1, and open_compliance_if_used_as_is_v6_1. Do not assume reverse engineering is mandatory or that as-is use is always sensible.","If the repo-level strategy says bounded_sidecar_preferred or boundary_first_then_decide_as_is_vs_reimplementation, audit clean interfaces, protocol seams, subprocess/container boundaries, and what would be required to reimplement only the strategically necessary portions.",v6.3_final_source_of_truth
SCR_0098,,,,,,,,,,ScriptoriumAI repo packet,ScriptoriumAI,ScriptoriumAI re-anchored VS Code packets v1,tikzit/tikzit,tikzit/tikzit,Reserve Bench,P3,bookmark candidate only,"Audit tikzit/tikzit for ScriptoriumAI. Start from the reanchored bucket 'Reserve Bench' and current reality status 'bookmark candidate only'. Confirm actual implemented capability, hidden reusable modules, extension seams, and whether it strengthens the existing Weak or ambiguous adjacent candidate lane. Focus on: Inspect hidden modules, extension seams, data contracts, rendering paths, auth/storage coupling, and export/import boundaries.",,"Treat as unimplemented ScriptoriumAI candidate only. Do not let it redefine the current stack. Integrate only if a later audit proves it fills a real gap in the existing surfaces such as Dashboard, Editor, Corpus Graph, Runboard, AI Kanban, Corpus Search, Patch Review Queue, Visualizations, Whiteboard, Mind Map, PDF Intake, AI Diagram Studio, Video Studio, Research Agent, New Research Topic, Skills Manager, OpenAPI Routing, Manim Sandbox, Settings.","Repurpose here means mining for specific modules, algorithms, UI patterns, ingestion logic, workflow ideas, or export formats rather than assuming a full product transplant.",manimcommunity/manim,remotion-dev/remotion,native/ScriptoriumAI-Visualizer,"Return concrete files/modules/adapters worth reusing and a verdict on whether the current reanchored bucket should be kept, upgraded, or downgraded.",Do not treat licensing as a filter. Do not propose replacing native foundations unless source evidence is overwhelming.,tikzit/tikzit,v6_unified_source_of_truth_pack,"Before recommending direct code use, inspect the target repo row in the v6.1 operational/phase/source-audit boards. Respect copyleft_strategy_v6_1, preferred_boundary_model_v6_1, and open_compliance_if_used_as_is_v6_1. Do not assume reverse engineering is mandatory or that as-is use is always sensible.","If the repo-level strategy says bounded_sidecar_preferred or boundary_first_then_decide_as_is_vs_reimplementation, audit clean interfaces, protocol seams, subprocess/container boundaries, and what would be required to reimplement only the strategically necessary portions.",v6.3_final_source_of_truth
SCR_0099,,,,,,,,,,ScriptoriumAI repo packet,ScriptoriumAI,ScriptoriumAI re-anchored VS Code packets v1,transcode-open/apt-cyg,transcode-open/apt-cyg,Reserve Bench,P3,bookmark candidate only,"Audit transcode-open/apt-cyg for ScriptoriumAI. Start from the reanchored bucket 'Reserve Bench' and current reality status 'bookmark candidate only'. Confirm actual implemented capability, hidden reusable modules, extension seams, and whether it strengthens the existing Weak or ambiguous adjacent candidate lane. Focus on: Inspect package/module map; entrypoints; config and schema files; adapters/integrations; persistence model; tests/examples; hidden feature flags; plugin 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 hidden admin tools, reusable services, plugin systems, import/export, analytics, background jobs, and any engine more valuable than the public README suggests.","Treat as unimplemented ScriptoriumAI candidate only. Do not let it redefine the current stack. Integrate only if a later audit proves it fills a real gap in the existing surfaces such as Dashboard, Editor, Corpus Graph, Runboard, AI Kanban, Corpus Search, Patch Review Queue, Visualizations, Whiteboard, Mind Map, PDF Intake, AI Diagram Studio, Video Studio, Research Agent, New Research Topic, Skills Manager, OpenAPI Routing, Manim Sandbox, Settings.","Repurpose here means mining for specific modules, algorithms, UI patterns, ingestion logic, workflow ideas, or export formats rather than assuming a full product transplant.",native/scriptoriumai-ui,native/ScriptoriumAI-Server,abhigyanpatwari/GitNexus,"Return concrete files/modules/adapters worth reusing and a verdict on whether the current reanchored bucket should be kept, upgraded, or downgraded.",Do not treat licensing as a filter. Do not propose replacing native foundations unless source evidence is overwhelming.,transcode-open/apt-cyg,v6_unified_source_of_truth_pack,"Before recommending direct code use, inspect the target repo row in the v6.1 operational/phase/source-audit boards. Respect copyleft_strategy_v6_1, preferred_boundary_model_v6_1, and open_compliance_if_used_as_is_v6_1. Do not assume reverse engineering is mandatory or that as-is use is always sensible.","If the repo-level strategy says bounded_sidecar_preferred or boundary_first_then_decide_as_is_vs_reimplementation, audit clean interfaces, protocol seams, subprocess/container boundaries, and what would be required to reimplement only the strategically necessary portions.",v6.3_final_source_of_truth
SCR_0100,,,,,,,,,,ScriptoriumAI repo packet,ScriptoriumAI,ScriptoriumAI re-anchored VS Code packets v1,trycua/launchpad,trycua/launchpad,Reserve Bench,P3,bookmark candidate only,"Audit trycua/launchpad for ScriptoriumAI. Start from the reanchored bucket 'Reserve Bench' and current reality status 'bookmark candidate only'. Confirm actual implemented capability, hidden reusable modules, extension seams, and whether it strengthens the existing Weak or ambiguous adjacent candidate lane. Focus on: Inspect package/module map; entrypoints; config and schema files; adapters/integrations; persistence model; tests/examples; hidden feature flags; plugin 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 hidden admin tools, reusable services, plugin systems, import/export, analytics, background jobs, and any engine more valuable than the public README suggests.","Treat as unimplemented ScriptoriumAI candidate only. Do not let it redefine the current stack. Integrate only if a later audit proves it fills a real gap in the existing surfaces such as Dashboard, Editor, Corpus Graph, Runboard, AI Kanban, Corpus Search, Patch Review Queue, Visualizations, Whiteboard, Mind Map, PDF Intake, AI Diagram Studio, Video Studio, Research Agent, New Research Topic, Skills Manager, OpenAPI Routing, Manim Sandbox, Settings.","Repurpose here means mining for specific modules, algorithms, UI patterns, ingestion logic, workflow ideas, or export formats rather than assuming a full product transplant.",native/scriptoriumai-ui,native/ScriptoriumAI-Server,abhigyanpatwari/GitNexus,"Return concrete files/modules/adapters worth reusing and a verdict on whether the current reanchored bucket should be kept, upgraded, or downgraded.",Do not treat licensing as a filter. Do not propose replacing native foundations unless source evidence is overwhelming.,trycua/launchpad,v6_unified_source_of_truth_pack,"Before recommending direct code use, inspect the target repo row in the v6.1 operational/phase/source-audit boards. Respect copyleft_strategy_v6_1, preferred_boundary_model_v6_1, and open_compliance_if_used_as_is_v6_1. Do not assume reverse engineering is mandatory or that as-is use is always sensible.","If the repo-level strategy says bounded_sidecar_preferred or boundary_first_then_decide_as_is_vs_reimplementation, audit clean interfaces, protocol seams, subprocess/container boundaries, and what would be required to reimplement only the strategically necessary portions.",v6.3_final_source_of_truth
SCR_0101,,,,,,,,,,ScriptoriumAI repo packet,ScriptoriumAI,ScriptoriumAI re-anchored VS Code packets v1,valinet/ExplorerPatcher,valinet/explorerpatcher,Reserve Bench,P3,bookmark candidate only,"Audit valinet/ExplorerPatcher for ScriptoriumAI. Start from the reanchored bucket 'Reserve Bench' and current reality status 'bookmark candidate only'. Confirm actual implemented capability, hidden reusable modules, extension seams, and whether it strengthens the existing Weak or ambiguous adjacent candidate lane. Focus on: Inspect package/module map; entrypoints; config and schema files; adapters/integrations; persistence model; tests/examples; hidden feature flags; plugin 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 hidden admin tools, reusable services, plugin systems, import/export, analytics, background jobs, and any engine more valuable than the public README suggests.","Treat as unimplemented ScriptoriumAI candidate only. Do not let it redefine the current stack. Integrate only if a later audit proves it fills a real gap in the existing surfaces such as Dashboard, Editor, Corpus Graph, Runboard, AI Kanban, Corpus Search, Patch Review Queue, Visualizations, Whiteboard, Mind Map, PDF Intake, AI Diagram Studio, Video Studio, Research Agent, New Research Topic, Skills Manager, OpenAPI Routing, Manim Sandbox, Settings.","Repurpose here means mining for specific modules, algorithms, UI patterns, ingestion logic, workflow ideas, or export formats rather than assuming a full product transplant.",native/scriptoriumai-ui,native/ScriptoriumAI-Server,abhigyanpatwari/GitNexus,"Return concrete files/modules/adapters worth reusing and a verdict on whether the current reanchored bucket should be kept, upgraded, or downgraded.",Do not treat licensing as a filter. Do not propose replacing native foundations unless source evidence is overwhelming.,valinet/explorerpatcher,v6_unified_source_of_truth_pack,"Before recommending direct code use, inspect the target repo row in the v6.1 operational/phase/source-audit boards. Respect copyleft_strategy_v6_1, preferred_boundary_model_v6_1, and open_compliance_if_used_as_is_v6_1. Do not assume reverse engineering is mandatory or that as-is use is always sensible.","If the repo-level strategy says bounded_sidecar_preferred or boundary_first_then_decide_as_is_vs_reimplementation, audit clean interfaces, protocol seams, subprocess/container boundaries, and what would be required to reimplement only the strategically necessary portions.",v6.3_final_source_of_truth
SCR_0102,,,,,,,,,,ScriptoriumAI repo packet,ScriptoriumAI,ScriptoriumAI re-anchored VS Code packets v1,woltapp/blurhash,woltapp/blurhash,Reserve Bench,P3,bookmark candidate only,"Audit woltapp/blurhash for ScriptoriumAI. Start from the reanchored bucket 'Reserve Bench' and current reality status 'bookmark candidate only'. Confirm actual implemented capability, hidden reusable modules, extension seams, and whether it strengthens the existing Weak or ambiguous adjacent candidate lane. Focus on: 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.","Treat as unimplemented ScriptoriumAI candidate only. Do not let it redefine the current stack. Integrate only if a later audit proves it fills a real gap in the existing surfaces such as Dashboard, Editor, Corpus Graph, Runboard, AI Kanban, Corpus Search, Patch Review Queue, Visualizations, Whiteboard, Mind Map, PDF Intake, AI Diagram Studio, Video Studio, Research Agent, New Research Topic, Skills Manager, OpenAPI Routing, Manim Sandbox, Settings.","Repurpose here means mining for specific modules, algorithms, UI patterns, ingestion logic, workflow ideas, or export formats rather than assuming a full product transplant.",native/scriptoriumai-ui,native/ScriptoriumAI-Server,abhigyanpatwari/GitNexus,"Return concrete files/modules/adapters worth reusing and a verdict on whether the current reanchored bucket should be kept, upgraded, or downgraded.",Do not treat licensing as a filter. Do not propose replacing native foundations unless source evidence is overwhelming.,woltapp/blurhash,v6_unified_source_of_truth_pack,"Before recommending direct code use, inspect the target repo row in the v6.1 operational/phase/source-audit boards. Respect copyleft_strategy_v6_1, preferred_boundary_model_v6_1, and open_compliance_if_used_as_is_v6_1. Do not assume reverse engineering is mandatory or that as-is use is always sensible.","If the repo-level strategy says bounded_sidecar_preferred or boundary_first_then_decide_as_is_vs_reimplementation, audit clean interfaces, protocol seams, subprocess/container boundaries, and what would be required to reimplement only the strategically necessary portions.",v6.3_final_source_of_truth
SCR_0103,,,,,,,,,,ScriptoriumAI repo packet,ScriptoriumAI,ScriptoriumAI re-anchored VS Code packets v1,x1xhlol/system-prompts-and-models-of-ai-tools,x1xhlol/system-prompts-and-models-of-ai-tools,Reserve Bench,P3,bookmark candidate only,"Audit x1xhlol/system-prompts-and-models-of-ai-tools for ScriptoriumAI. Start from the reanchored bucket 'Reserve Bench' and current reality status 'bookmark candidate only'. Confirm actual implemented capability, hidden reusable modules, extension seams, and whether it strengthens the existing Weak or ambiguous adjacent candidate lane. Focus on: Inspect package/module map; entrypoints; config and schema files; adapters/integrations; persistence model; tests/examples; hidden feature flags; plugin 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 hidden admin tools, reusable services, plugin systems, import/export, analytics, background jobs, and any engine more valuable than the public README suggests.","Treat as unimplemented ScriptoriumAI candidate only. Do not let it redefine the current stack. Integrate only if a later audit proves it fills a real gap in the existing surfaces such as Dashboard, Editor, Corpus Graph, Runboard, AI Kanban, Corpus Search, Patch Review Queue, Visualizations, Whiteboard, Mind Map, PDF Intake, AI Diagram Studio, Video Studio, Research Agent, New Research Topic, Skills Manager, OpenAPI Routing, Manim Sandbox, Settings.","Repurpose here means mining for specific modules, algorithms, UI patterns, ingestion logic, workflow ideas, or export formats rather than assuming a full product transplant.",native/scriptoriumai-ui,native/ScriptoriumAI-Server,abhigyanpatwari/GitNexus,"Return concrete files/modules/adapters worth reusing and a verdict on whether the current reanchored bucket should be kept, upgraded, or downgraded.",Do not treat licensing as a filter. Do not propose replacing native foundations unless source evidence is overwhelming.,x1xhlol/system-prompts-and-models-of-ai-tools,v6_unified_source_of_truth_pack,"Before recommending direct code use, inspect the target repo row in the v6.1 operational/phase/source-audit boards. Respect copyleft_strategy_v6_1, preferred_boundary_model_v6_1, and open_compliance_if_used_as_is_v6_1. Do not assume reverse engineering is mandatory or that as-is use is always sensible.","If the repo-level strategy says bounded_sidecar_preferred or boundary_first_then_decide_as_is_vs_reimplementation, audit clean interfaces, protocol seams, subprocess/container boundaries, and what would be required to reimplement only the strategically necessary portions.",v6.3_final_source_of_truth
SCR_0104,,,,,,,,,,ScriptoriumAI repo packet,ScriptoriumAI,ScriptoriumAI re-anchored VS Code packets v1,xiongsiheng/DeepVerify,xiongsiheng/deepverify,Reserve Bench,P3,bookmark candidate only,"Audit xiongsiheng/DeepVerify for ScriptoriumAI. Start from the reanchored bucket 'Reserve Bench' and current reality status 'bookmark candidate only'. Confirm actual implemented capability, hidden reusable modules, extension seams, and whether it strengthens the existing Weak or ambiguous adjacent candidate lane. Focus on: Inspect package/module map; entrypoints; config and schema files; adapters/integrations; persistence model; tests/examples; hidden feature flags; plugin 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 hidden admin tools, reusable services, plugin systems, import/export, analytics, background jobs, and any engine more valuable than the public README suggests.","Treat as unimplemented ScriptoriumAI candidate only. Do not let it redefine the current stack. Integrate only if a later audit proves it fills a real gap in the existing surfaces such as Dashboard, Editor, Corpus Graph, Runboard, AI Kanban, Corpus Search, Patch Review Queue, Visualizations, Whiteboard, Mind Map, PDF Intake, AI Diagram Studio, Video Studio, Research Agent, New Research Topic, Skills Manager, OpenAPI Routing, Manim Sandbox, Settings.","Repurpose here means mining for specific modules, algorithms, UI patterns, ingestion logic, workflow ideas, or export formats rather than assuming a full product transplant.",native/scriptoriumai-ui,native/ScriptoriumAI-Server,abhigyanpatwari/GitNexus,"Return concrete files/modules/adapters worth reusing and a verdict on whether the current reanchored bucket should be kept, upgraded, or downgraded.",Do not treat licensing as a filter. Do not propose replacing native foundations unless source evidence is overwhelming.,xiongsiheng/deepverify,v6_unified_source_of_truth_pack,"Before recommending direct code use, inspect the target repo row in the v6.1 operational/phase/source-audit boards. Respect copyleft_strategy_v6_1, preferred_boundary_model_v6_1, and open_compliance_if_used_as_is_v6_1. Do not assume reverse engineering is mandatory or that as-is use is always sensible.","If the repo-level strategy says bounded_sidecar_preferred or boundary_first_then_decide_as_is_vs_reimplementation, audit clean interfaces, protocol seams, subprocess/container boundaries, and what would be required to reimplement only the strategically necessary portions.",v6.3_final_source_of_truth
SCR_0105,,,,,,,,,,ScriptoriumAI repo packet,ScriptoriumAI,ScriptoriumAI re-anchored VS Code packets v1,xoofx/SuperluminalPerf,xoofx/superluminalperf,Reserve Bench,P3,bookmark candidate only,"Audit xoofx/SuperluminalPerf for ScriptoriumAI. Start from the reanchored bucket 'Reserve Bench' and current reality status 'bookmark candidate only'. Confirm actual implemented capability, hidden reusable modules, extension seams, and whether it strengthens the existing Weak or ambiguous adjacent candidate lane. Focus on: 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 event schemas, ingestion pipelines, queue/job workers, service adapters, deployment/runtime config, RBAC/auth, alerting, and API contract generators.","Treat as unimplemented ScriptoriumAI candidate only. Do not let it redefine the current stack. Integrate only if a later audit proves it fills a real gap in the existing surfaces such as Dashboard, Editor, Corpus Graph, Runboard, AI Kanban, Corpus Search, Patch Review Queue, Visualizations, Whiteboard, Mind Map, PDF Intake, AI Diagram Studio, Video Studio, Research Agent, New Research Topic, Skills Manager, OpenAPI Routing, Manim Sandbox, Settings.","Repurpose here means mining for specific modules, algorithms, UI patterns, ingestion logic, workflow ideas, or export formats rather than assuming a full product transplant.",native/scriptoriumai-ui,native/ScriptoriumAI-Server,abhigyanpatwari/GitNexus,"Return concrete files/modules/adapters worth reusing and a verdict on whether the current reanchored bucket should be kept, upgraded, or downgraded.",Do not treat licensing as a filter. Do not propose replacing native foundations unless source evidence is overwhelming.,xoofx/superluminalperf,v6_unified_source_of_truth_pack,"Before recommending direct code use, inspect the target repo row in the v6.1 operational/phase/source-audit boards. Respect copyleft_strategy_v6_1, preferred_boundary_model_v6_1, and open_compliance_if_used_as_is_v6_1. Do not assume reverse engineering is mandatory or that as-is use is always sensible.","If the repo-level strategy says bounded_sidecar_preferred or boundary_first_then_decide_as_is_vs_reimplementation, audit clean interfaces, protocol seams, subprocess/container boundaries, and what would be required to reimplement only the strategically necessary portions.",v6.3_final_source_of_truth
SCR_0106,,,,,,,,,,ScriptoriumAI repo packet,ScriptoriumAI,ScriptoriumAI re-anchored VS Code packets v1,xyjoey/PRISM,xyjoey/prism,Reserve Bench,P3,bookmark candidate only,"Audit xyjoey/PRISM for ScriptoriumAI. Start from the reanchored bucket 'Reserve Bench' and current reality status 'bookmark candidate only'. Confirm actual implemented capability, hidden reusable modules, extension seams, and whether it strengthens the existing Weak or ambiguous adjacent candidate lane. Focus on: 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.","Treat as unimplemented ScriptoriumAI candidate only. Do not let it redefine the current stack. Integrate only if a later audit proves it fills a real gap in the existing surfaces such as Dashboard, Editor, Corpus Graph, Runboard, AI Kanban, Corpus Search, Patch Review Queue, Visualizations, Whiteboard, Mind Map, PDF Intake, AI Diagram Studio, Video Studio, Research Agent, New Research Topic, Skills Manager, OpenAPI Routing, Manim Sandbox, Settings.","Repurpose here means mining for specific modules, algorithms, UI patterns, ingestion logic, workflow ideas, or export formats rather than assuming a full product transplant.",native/scriptoriumai-ui,native/ScriptoriumAI-Server,abhigyanpatwari/GitNexus,"Return concrete files/modules/adapters worth reusing and a verdict on whether the current reanchored bucket should be kept, upgraded, or downgraded.",Do not treat licensing as a filter. Do not propose replacing native foundations unless source evidence is overwhelming.,xyjoey/prism,v6_unified_source_of_truth_pack,"Before recommending direct code use, inspect the target repo row in the v6.1 operational/phase/source-audit boards. Respect copyleft_strategy_v6_1, preferred_boundary_model_v6_1, and open_compliance_if_used_as_is_v6_1. Do not assume reverse engineering is mandatory or that as-is use is always sensible.","If the repo-level strategy says bounded_sidecar_preferred or boundary_first_then_decide_as_is_vs_reimplementation, audit clean interfaces, protocol seams, subprocess/container boundaries, and what would be required to reimplement only the strategically necessary portions.",v6.3_final_source_of_truth
SCR_0107,,,,,,,,,,ScriptoriumAI repo packet,ScriptoriumAI,ScriptoriumAI re-anchored VS Code packets v1,you-dont-need/You-Dont-Need,you-dont-need/you-dont-need,Reserve Bench,P3,bookmark candidate only,"Audit you-dont-need/You-Dont-Need for ScriptoriumAI. Start from the reanchored bucket 'Reserve Bench' and current reality status 'bookmark candidate only'. Confirm actual implemented capability, hidden reusable modules, extension seams, and whether it strengthens the existing Weak or ambiguous adjacent candidate lane. Focus on: 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.","Treat as unimplemented ScriptoriumAI candidate only. Do not let it redefine the current stack. Integrate only if a later audit proves it fills a real gap in the existing surfaces such as Dashboard, Editor, Corpus Graph, Runboard, AI Kanban, Corpus Search, Patch Review Queue, Visualizations, Whiteboard, Mind Map, PDF Intake, AI Diagram Studio, Video Studio, Research Agent, New Research Topic, Skills Manager, OpenAPI Routing, Manim Sandbox, Settings.","Repurpose here means mining for specific modules, algorithms, UI patterns, ingestion logic, workflow ideas, or export formats rather than assuming a full product transplant.",native/scriptoriumai-ui,native/ScriptoriumAI-Server,abhigyanpatwari/GitNexus,"Return concrete files/modules/adapters worth reusing and a verdict on whether the current reanchored bucket should be kept, upgraded, or downgraded.",Do not treat licensing as a filter. Do not propose replacing native foundations unless source evidence is overwhelming.,you-dont-need/you-dont-need,v6_unified_source_of_truth_pack,"Before recommending direct code use, inspect the target repo row in the v6.1 operational/phase/source-audit boards. Respect copyleft_strategy_v6_1, preferred_boundary_model_v6_1, and open_compliance_if_used_as_is_v6_1. Do not assume reverse engineering is mandatory or that as-is use is always sensible.","If the repo-level strategy says bounded_sidecar_preferred or boundary_first_then_decide_as_is_vs_reimplementation, audit clean interfaces, protocol seams, subprocess/container boundaries, and what would be required to reimplement only the strategically necessary portions.",v6.3_final_source_of_truth
SCR_0108,,,,,,,,,,ScriptoriumAI repo packet,ScriptoriumAI,ScriptoriumAI re-anchored VS Code packets v1,you-dont-need/You-Dont-Need-GUI,you-dont-need/you-dont-need-gui,Reserve Bench,P3,bookmark candidate only,"Audit you-dont-need/You-Dont-Need-GUI for ScriptoriumAI. Start from the reanchored bucket 'Reserve Bench' and current reality status 'bookmark candidate only'. Confirm actual implemented capability, hidden reusable modules, extension seams, and whether it strengthens the existing Weak or ambiguous adjacent candidate lane. Focus on: 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 reusable canvas/editor components, design tokens, state models, keyboard shortcuts, drag/drop, accessibility, virtualization, and polished interaction patterns.","Treat as unimplemented ScriptoriumAI candidate only. Do not let it redefine the current stack. Integrate only if a later audit proves it fills a real gap in the existing surfaces such as Dashboard, Editor, Corpus Graph, Runboard, AI Kanban, Corpus Search, Patch Review Queue, Visualizations, Whiteboard, Mind Map, PDF Intake, AI Diagram Studio, Video Studio, Research Agent, New Research Topic, Skills Manager, OpenAPI Routing, Manim Sandbox, Settings.","Repurpose here means mining for specific modules, algorithms, UI patterns, ingestion logic, workflow ideas, or export formats rather than assuming a full product transplant.",native/scriptoriumai-ui,native/ScriptoriumAI-Server,abhigyanpatwari/GitNexus,"Return concrete files/modules/adapters worth reusing and a verdict on whether the current reanchored bucket should be kept, upgraded, or downgraded.",Do not treat licensing as a filter. Do not propose replacing native foundations unless source evidence is overwhelming.,you-dont-need/you-dont-need-gui,v6_unified_source_of_truth_pack,"Before recommending direct code use, inspect the target repo row in the v6.1 operational/phase/source-audit boards. Respect copyleft_strategy_v6_1, preferred_boundary_model_v6_1, and open_compliance_if_used_as_is_v6_1. Do not assume reverse engineering is mandatory or that as-is use is always sensible.","If the repo-level strategy says bounded_sidecar_preferred or boundary_first_then_decide_as_is_vs_reimplementation, audit clean interfaces, protocol seams, subprocess/container boundaries, and what would be required to reimplement only the strategically necessary portions.",v6.3_final_source_of_truth
SCR_0109,,,,,,,,,,ScriptoriumAI repo packet,ScriptoriumAI,ScriptoriumAI re-anchored VS Code packets v1,zavden/chanim,zavden/chanim,Reserve Bench,P3,bookmark candidate only,"Audit zavden/chanim for ScriptoriumAI. Start from the reanchored bucket 'Reserve Bench' and current reality status 'bookmark candidate only'. Confirm actual implemented capability, hidden reusable modules, extension seams, and whether it strengthens the existing Weak or ambiguous adjacent candidate lane. Focus on: Inspect hidden modules, extension seams, data contracts, rendering paths, auth/storage coupling, and export/import boundaries.",,"Treat as unimplemented ScriptoriumAI candidate only. Do not let it redefine the current stack. Integrate only if a later audit proves it fills a real gap in the existing surfaces such as Dashboard, Editor, Corpus Graph, Runboard, AI Kanban, Corpus Search, Patch Review Queue, Visualizations, Whiteboard, Mind Map, PDF Intake, AI Diagram Studio, Video Studio, Research Agent, New Research Topic, Skills Manager, OpenAPI Routing, Manim Sandbox, Settings.","Repurpose here means mining for specific modules, algorithms, UI patterns, ingestion logic, workflow ideas, or export formats rather than assuming a full product transplant.",manimcommunity/manim,remotion-dev/remotion,native/ScriptoriumAI-Visualizer,"Return concrete files/modules/adapters worth reusing and a verdict on whether the current reanchored bucket should be kept, upgraded, or downgraded.",Do not treat licensing as a filter. Do not propose replacing native foundations unless source evidence is overwhelming.,zavden/chanim,v6_unified_source_of_truth_pack,"Before recommending direct code use, inspect the target repo row in the v6.1 operational/phase/source-audit boards. Respect copyleft_strategy_v6_1, preferred_boundary_model_v6_1, and open_compliance_if_used_as_is_v6_1. Do not assume reverse engineering is mandatory or that as-is use is always sensible.","If the repo-level strategy says bounded_sidecar_preferred or boundary_first_then_decide_as_is_vs_reimplementation, audit clean interfaces, protocol seams, subprocess/container boundaries, and what would be required to reimplement only the strategically necessary portions.",v6.3_final_source_of_truth
SCR_0110,,,,,,,,,,ScriptoriumAI repo packet,ScriptoriumAI,ScriptoriumAI re-anchored VS Code packets v1,zeabur/zeabur,zeabur/zeabur,Reserve Bench,P3,bookmark candidate only,"Audit zeabur/zeabur for ScriptoriumAI. Start from the reanchored bucket 'Reserve Bench' and current reality status 'bookmark candidate only'. Confirm actual implemented capability, hidden reusable modules, extension seams, and whether it strengthens the existing Weak or ambiguous adjacent candidate lane. Focus on: Inspect parsers and language adapters; graph schema and storage; incremental indexing/update logic; layout engine; query API; export/import formats; test fixtures for graph correctness.","Inspect package manifests, README/docs, src tree, examples, tests, CI workflows, config files, migrations/schemas, and hidden feature flags or experimental modules. Look for event schemas, ingestion pipelines, queue/job workers, service adapters, deployment/runtime config, RBAC/auth, alerting, and API contract generators.","Treat as unimplemented ScriptoriumAI candidate only. Do not let it redefine the current stack. Integrate only if a later audit proves it fills a real gap in the existing surfaces such as Dashboard, Editor, Corpus Graph, Runboard, AI Kanban, Corpus Search, Patch Review Queue, Visualizations, Whiteboard, Mind Map, PDF Intake, AI Diagram Studio, Video Studio, Research Agent, New Research Topic, Skills Manager, OpenAPI Routing, Manim Sandbox, Settings.","Repurpose here means mining for specific modules, algorithms, UI patterns, ingestion logic, workflow ideas, or export formats rather than assuming a full product transplant.",native/scriptoriumai-ui,native/ScriptoriumAI-Server,abhigyanpatwari/GitNexus,"Return concrete files/modules/adapters worth reusing and a verdict on whether the current reanchored bucket should be kept, upgraded, or downgraded.",Do not treat licensing as a filter. Do not propose replacing native foundations unless source evidence is overwhelming.,zeabur/zeabur,v6_unified_source_of_truth_pack,"Before recommending direct code use, inspect the target repo row in the v6.1 operational/phase/source-audit boards. Respect copyleft_strategy_v6_1, preferred_boundary_model_v6_1, and open_compliance_if_used_as_is_v6_1. Do not assume reverse engineering is mandatory or that as-is use is always sensible.","If the repo-level strategy says bounded_sidecar_preferred or boundary_first_then_decide_as_is_vs_reimplementation, audit clean interfaces, protocol seams, subprocess/container boundaries, and what would be required to reimplement only the strategically necessary portions.",v6.3_final_source_of_truth
SCR_0111,,,,,,,,,,ScriptoriumAI repo packet,ScriptoriumAI,ScriptoriumAI re-anchored VS Code packets v1,0x77dev/pdf-sign,0x77dev/pdf-sign,Candidate Bench,P3,bookmark candidate only,"Audit 0x77dev/pdf-sign for ScriptoriumAI. Start from the reanchored bucket 'Candidate Bench' and current reality status 'bookmark candidate only'. Confirm actual implemented capability, hidden reusable modules, extension seams, and whether it strengthens the existing Unimplemented but relevant candidate lane. Focus on: 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.","Treat as unimplemented ScriptoriumAI candidate only. Do not let it redefine the current stack. Integrate only if a later audit proves it fills a real gap in the existing surfaces such as Dashboard, Editor, Corpus Graph, Runboard, AI Kanban, Corpus Search, Patch Review Queue, Visualizations, Whiteboard, Mind Map, PDF Intake, AI Diagram Studio, Video Studio, Research Agent, New Research Topic, Skills Manager, OpenAPI Routing, Manim Sandbox, Settings.","Repurpose here means mining for specific modules, algorithms, UI patterns, ingestion logic, workflow ideas, or export formats rather than assuming a full product transplant.",pdfmd/pdfmd,lukas-blecher/latex-ocr,mli55/pdfdelta,"Return concrete files/modules/adapters worth reusing and a verdict on whether the current reanchored bucket should be kept, upgraded, or downgraded.",Do not treat licensing as a filter. Do not propose replacing native foundations unless source evidence is overwhelming.,0x77dev/pdf-sign,v6_unified_source_of_truth_pack,"Before recommending direct code use, inspect the target repo row in the v6.1 operational/phase/source-audit boards. Respect copyleft_strategy_v6_1, preferred_boundary_model_v6_1, and open_compliance_if_used_as_is_v6_1. Do not assume reverse engineering is mandatory or that as-is use is always sensible.","If the repo-level strategy says bounded_sidecar_preferred or boundary_first_then_decide_as_is_vs_reimplementation, audit clean interfaces, protocol seams, subprocess/container boundaries, and what would be required to reimplement only the strategically necessary portions.",v6.3_final_source_of_truth
SCR_0112,,,,,,,,,,ScriptoriumAI repo packet,ScriptoriumAI,ScriptoriumAI re-anchored VS Code packets v1,0xsline/StoryGen-Atelier,0xsline/storygen-atelier,Candidate Bench,P3,bookmark candidate only,"Audit 0xsline/StoryGen-Atelier for ScriptoriumAI. Start from the reanchored bucket 'Candidate Bench' and current reality status 'bookmark candidate only'. Confirm actual implemented capability, hidden reusable modules, extension seams, and whether it strengthens the existing Unimplemented but relevant candidate lane. Focus on: 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 reusable canvas/editor components, design tokens, state models, keyboard shortcuts, drag/drop, accessibility, virtualization, and polished interaction patterns.","Treat as unimplemented ScriptoriumAI candidate only. Do not let it redefine the current stack. Integrate only if a later audit proves it fills a real gap in the existing surfaces such as Dashboard, Editor, Corpus Graph, Runboard, AI Kanban, Corpus Search, Patch Review Queue, Visualizations, Whiteboard, Mind Map, PDF Intake, AI Diagram Studio, Video Studio, Research Agent, New Research Topic, Skills Manager, OpenAPI Routing, Manim Sandbox, Settings.","Repurpose here means mining for specific modules, algorithms, UI patterns, ingestion logic, workflow ideas, or export formats rather than assuming a full product transplant.",manimcommunity/manim,remotion-dev/remotion,native/ScriptoriumAI-Visualizer,"Return concrete files/modules/adapters worth reusing and a verdict on whether the current reanchored bucket should be kept, upgraded, or downgraded.",Do not treat licensing as a filter. Do not propose replacing native foundations unless source evidence is overwhelming.,0xsline/storygen-atelier,v6_unified_source_of_truth_pack,"Before recommending direct code use, inspect the target repo row in the v6.1 operational/phase/source-audit boards. Respect copyleft_strategy_v6_1, preferred_boundary_model_v6_1, and open_compliance_if_used_as_is_v6_1. Do not assume reverse engineering is mandatory or that as-is use is always sensible.","If the repo-level strategy says bounded_sidecar_preferred or boundary_first_then_decide_as_is_vs_reimplementation, audit clean interfaces, protocol seams, subprocess/container boundaries, and what would be required to reimplement only the strategically necessary portions.",v6.3_final_source_of_truth
SCR_0113,,,,,,,,,,ScriptoriumAI repo packet,ScriptoriumAI,ScriptoriumAI re-anchored VS Code packets v1,1jehuang/mermaid-rs-renderer,1jehuang/mermaid-rs-renderer,Candidate Bench,P3,bookmark candidate only,"Audit 1jehuang/mermaid-rs-renderer for ScriptoriumAI. Start from the reanchored bucket 'Candidate Bench' and current reality status 'bookmark candidate only'. Confirm actual implemented capability, hidden reusable modules, extension seams, and whether it strengthens the existing Unimplemented but relevant candidate lane. Focus on: Inspect document/block schema; sync/persistence model; permissions and sharing; citation/external-source pipeline; import/export adapters; plugin/extension points; editor rendering model.","Inspect package manifests, README/docs, src tree, examples, tests, CI workflows, config files, migrations/schemas, and hidden feature flags or experimental modules. Look for document/block schema, sync/conflict logic, citation handling, editor plugins, export/render pipeline, prompt chains, report assembly, and collaborative presence code.","Treat as unimplemented ScriptoriumAI candidate only. Do not let it redefine the current stack. Integrate only if a later audit proves it fills a real gap in the existing surfaces such as Dashboard, Editor, Corpus Graph, Runboard, AI Kanban, Corpus Search, Patch Review Queue, Visualizations, Whiteboard, Mind Map, PDF Intake, AI Diagram Studio, Video Studio, Research Agent, New Research Topic, Skills Manager, OpenAPI Routing, Manim Sandbox, Settings.","Repurpose here means mining for specific modules, algorithms, UI patterns, ingestion logic, workflow ideas, or export formats rather than assuming a full product transplant.",native/scriptoriumai-ui,native/ScriptoriumAI-Server,abhigyanpatwari/GitNexus,"Return concrete files/modules/adapters worth reusing and a verdict on whether the current reanchored bucket should be kept, upgraded, or downgraded.",Do not treat licensing as a filter. Do not propose replacing native foundations unless source evidence is overwhelming.,1jehuang/mermaid-rs-renderer,v6_unified_source_of_truth_pack,"Before recommending direct code use, inspect the target repo row in the v6.1 operational/phase/source-audit boards. Respect copyleft_strategy_v6_1, preferred_boundary_model_v6_1, and open_compliance_if_used_as_is_v6_1. Do not assume reverse engineering is mandatory or that as-is use is always sensible.","If the repo-level strategy says bounded_sidecar_preferred or boundary_first_then_decide_as_is_vs_reimplementation, audit clean interfaces, protocol seams, subprocess/container boundaries, and what would be required to reimplement only the strategically necessary portions.",v6.3_final_source_of_truth
SCR_0114,,,,,,,,,,ScriptoriumAI repo packet,ScriptoriumAI,ScriptoriumAI re-anchored VS Code packets v1,666ghj/BettaFish,666ghj/bettafish,Candidate Bench,P3,bookmark candidate only,"Audit 666ghj/BettaFish for ScriptoriumAI. Start from the reanchored bucket 'Candidate Bench' and current reality status 'bookmark candidate only'. Confirm actual implemented capability, hidden reusable modules, extension seams, and whether it strengthens the existing Unimplemented but relevant candidate lane. Focus on: Inspect planner/task graph; provider abstraction; tool registry or MCP bridges; memory/state schema; approvals/retries; telemetry/event bus; plugin or skill loading 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 planner loops, tool registries, MCP servers/clients, prompt/skill folders, memory stores, approval gates, background-job orchestration, and undocumented provider adapters.","Treat as unimplemented ScriptoriumAI candidate only. Do not let it redefine the current stack. Integrate only if a later audit proves it fills a real gap in the existing surfaces such as Dashboard, Editor, Corpus Graph, Runboard, AI Kanban, Corpus Search, Patch Review Queue, Visualizations, Whiteboard, Mind Map, PDF Intake, AI Diagram Studio, Video Studio, Research Agent, New Research Topic, Skills Manager, OpenAPI Routing, Manim Sandbox, Settings.","Repurpose here means mining for specific modules, algorithms, UI patterns, ingestion logic, workflow ideas, or export formats rather than assuming a full product transplant.",native/ScriptoriumAI-Server,stanford-oval/storm,abhigyanpatwari/GitNexus,"Return concrete files/modules/adapters worth reusing and a verdict on whether the current reanchored bucket should be kept, upgraded, or downgraded.",Do not treat licensing as a filter. Do not propose replacing native foundations unless source evidence is overwhelming.,666ghj/bettafish,v6_unified_source_of_truth_pack,"Before recommending direct code use, inspect the target repo row in the v6.1 operational/phase/source-audit boards. Respect copyleft_strategy_v6_1, preferred_boundary_model_v6_1, and open_compliance_if_used_as_is_v6_1. Do not assume reverse engineering is mandatory or that as-is use is always sensible.","If the repo-level strategy says bounded_sidecar_preferred or boundary_first_then_decide_as_is_vs_reimplementation, audit clean interfaces, protocol seams, subprocess/container boundaries, and what would be required to reimplement only the strategically necessary portions.",v6.3_final_source_of_truth
SCR_0115,,,,,,,,,,ScriptoriumAI repo packet,ScriptoriumAI,ScriptoriumAI re-anchored VS Code packets v1,AMDResearch/DRAM-Refresh-Research,amdresearch/dram-refresh-research,Candidate Bench,P3,bookmark candidate only,"Audit AMDResearch/DRAM-Refresh-Research for ScriptoriumAI. Start from the reanchored bucket 'Candidate Bench' and current reality status 'bookmark candidate only'. Confirm actual implemented capability, hidden reusable modules, extension seams, and whether it strengthens the existing Unimplemented but relevant candidate lane. Focus on: Inspect document/block schema; sync/persistence model; permissions and sharing; citation/external-source pipeline; import/export adapters; plugin/extension points; editor rendering model.","Inspect package manifests, README/docs, src tree, examples, tests, CI workflows, config files, migrations/schemas, and hidden feature flags or experimental modules. Look for document/block schema, sync/conflict logic, citation handling, editor plugins, export/render pipeline, prompt chains, report assembly, and collaborative presence code.","Treat as unimplemented ScriptoriumAI candidate only. Do not let it redefine the current stack. Integrate only if a later audit proves it fills a real gap in the existing surfaces such as Dashboard, Editor, Corpus Graph, Runboard, AI Kanban, Corpus Search, Patch Review Queue, Visualizations, Whiteboard, Mind Map, PDF Intake, AI Diagram Studio, Video Studio, Research Agent, New Research Topic, Skills Manager, OpenAPI Routing, Manim Sandbox, Settings.","Repurpose here means mining for specific modules, algorithms, UI patterns, ingestion logic, workflow ideas, or export formats rather than assuming a full product transplant.",native/ScriptoriumAI-Server,stanford-oval/storm,abhigyanpatwari/GitNexus,"Return concrete files/modules/adapters worth reusing and a verdict on whether the current reanchored bucket should be kept, upgraded, or downgraded.",Do not treat licensing as a filter. Do not propose replacing native foundations unless source evidence is overwhelming.,amdresearch/dram-refresh-research,v6_unified_source_of_truth_pack,"Before recommending direct code use, inspect the target repo row in the v6.1 operational/phase/source-audit boards. Respect copyleft_strategy_v6_1, preferred_boundary_model_v6_1, and open_compliance_if_used_as_is_v6_1. Do not assume reverse engineering is mandatory or that as-is use is always sensible.","If the repo-level strategy says bounded_sidecar_preferred or boundary_first_then_decide_as_is_vs_reimplementation, audit clean interfaces, protocol seams, subprocess/container boundaries, and what would be required to reimplement only the strategically necessary portions.",v6.3_final_source_of_truth
SCR_0116,,,,,,,,,,ScriptoriumAI repo packet,ScriptoriumAI,ScriptoriumAI re-anchored VS Code packets v1,BloopAI/vibe-kanban,bloopai/vibe-kanban,Candidate Bench,P3,bookmark candidate only,"Audit BloopAI/vibe-kanban for ScriptoriumAI. Start from the reanchored bucket 'Candidate Bench' and current reality status 'bookmark candidate only'. Confirm actual implemented capability, hidden reusable modules, extension seams, and whether it strengthens the existing Unimplemented but relevant candidate lane. Focus on: Inspect planner/task graph; provider abstraction; tool registry or MCP bridges; memory/state schema; approvals/retries; telemetry/event bus; plugin or skill loading 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 planner loops, tool registries, MCP servers/clients, prompt/skill folders, memory stores, approval gates, background-job orchestration, and undocumented provider adapters.","Treat as unimplemented ScriptoriumAI candidate only. Do not let it redefine the current stack. Integrate only if a later audit proves it fills a real gap in the existing surfaces such as Dashboard, Editor, Corpus Graph, Runboard, AI Kanban, Corpus Search, Patch Review Queue, Visualizations, Whiteboard, Mind Map, PDF Intake, AI Diagram Studio, Video Studio, Research Agent, New Research Topic, Skills Manager, OpenAPI Routing, Manim Sandbox, Settings.","Repurpose here means mining for specific modules, algorithms, UI patterns, ingestion logic, workflow ideas, or export formats rather than assuming a full product transplant.",native/ScriptoriumAI-Server,stanford-oval/storm,abhigyanpatwari/GitNexus,"Return concrete files/modules/adapters worth reusing and a verdict on whether the current reanchored bucket should be kept, upgraded, or downgraded.",Do not treat licensing as a filter. Do not propose replacing native foundations unless source evidence is overwhelming.,bloopai/vibe-kanban,v6_unified_source_of_truth_pack,"Before recommending direct code use, inspect the target repo row in the v6.1 operational/phase/source-audit boards. Respect copyleft_strategy_v6_1, preferred_boundary_model_v6_1, and open_compliance_if_used_as_is_v6_1. Do not assume reverse engineering is mandatory or that as-is use is always sensible.","If the repo-level strategy says bounded_sidecar_preferred or boundary_first_then_decide_as_is_vs_reimplementation, audit clean interfaces, protocol seams, subprocess/container boundaries, and what would be required to reimplement only the strategically necessary portions.",v6.3_final_source_of_truth
SCR_0117,,,,,,,,,,ScriptoriumAI repo packet,ScriptoriumAI,ScriptoriumAI re-anchored VS Code packets v1,DangJin/pdf2video,dangjin/pdf2video,Candidate Bench,P3,bookmark candidate only,"Audit DangJin/pdf2video for ScriptoriumAI. Start from the reanchored bucket 'Candidate Bench' and current reality status 'bookmark candidate only'. Confirm actual implemented capability, hidden reusable modules, extension seams, and whether it strengthens the existing Unimplemented but relevant candidate lane. Focus on: Inspect document/block schema; sync/persistence model; permissions and sharing; citation/external-source pipeline; import/export adapters; plugin/extension points; editor rendering model.","Inspect package manifests, README/docs, src tree, examples, tests, CI workflows, config files, migrations/schemas, and hidden feature flags or experimental modules. Look for document/block schema, sync/conflict logic, citation handling, editor plugins, export/render pipeline, prompt chains, report assembly, and collaborative presence code.","Treat as unimplemented ScriptoriumAI candidate only. Do not let it redefine the current stack. Integrate only if a later audit proves it fills a real gap in the existing surfaces such as Dashboard, Editor, Corpus Graph, Runboard, AI Kanban, Corpus Search, Patch Review Queue, Visualizations, Whiteboard, Mind Map, PDF Intake, AI Diagram Studio, Video Studio, Research Agent, New Research Topic, Skills Manager, OpenAPI Routing, Manim Sandbox, Settings.","Repurpose here means mining for specific modules, algorithms, UI patterns, ingestion logic, workflow ideas, or export formats rather than assuming a full product transplant.",pdfmd/pdfmd,lukas-blecher/latex-ocr,mli55/pdfdelta,"Return concrete files/modules/adapters worth reusing and a verdict on whether the current reanchored bucket should be kept, upgraded, or downgraded.",Do not treat licensing as a filter. Do not propose replacing native foundations unless source evidence is overwhelming.,dangjin/pdf2video,v6_unified_source_of_truth_pack,"Before recommending direct code use, inspect the target repo row in the v6.1 operational/phase/source-audit boards. Respect copyleft_strategy_v6_1, preferred_boundary_model_v6_1, and open_compliance_if_used_as_is_v6_1. Do not assume reverse engineering is mandatory or that as-is use is always sensible.","If the repo-level strategy says bounded_sidecar_preferred or boundary_first_then_decide_as_is_vs_reimplementation, audit clean interfaces, protocol seams, subprocess/container boundaries, and what would be required to reimplement only the strategically necessary portions.",v6.3_final_source_of_truth
SCR_0118,,,,,,,,,,ScriptoriumAI repo packet,ScriptoriumAI,ScriptoriumAI re-anchored VS Code packets v1,DataExpert-io/data-engineer-handbook,dataexpert-io/data-engineer-handbook,Candidate Bench,P3,bookmark candidate only,"Audit DataExpert-io/data-engineer-handbook for ScriptoriumAI. Start from the reanchored bucket 'Candidate Bench' and current reality status 'bookmark candidate only'. Confirm actual implemented capability, hidden reusable modules, extension seams, and whether it strengthens the existing Unimplemented but relevant candidate lane. Focus on: Inspect package/module map; entrypoints; config and schema files; adapters/integrations; persistence model; tests/examples; hidden feature flags; plugin 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 hidden admin tools, reusable services, plugin systems, import/export, analytics, background jobs, and any engine more valuable than the public README suggests.","Treat as unimplemented ScriptoriumAI candidate only. Do not let it redefine the current stack. Integrate only if a later audit proves it fills a real gap in the existing surfaces such as Dashboard, Editor, Corpus Graph, Runboard, AI Kanban, Corpus Search, Patch Review Queue, Visualizations, Whiteboard, Mind Map, PDF Intake, AI Diagram Studio, Video Studio, Research Agent, New Research Topic, Skills Manager, OpenAPI Routing, Manim Sandbox, Settings.","Repurpose here means mining for specific modules, algorithms, UI patterns, ingestion logic, workflow ideas, or export formats rather than assuming a full product transplant.",native/scriptoriumai-ui,native/ScriptoriumAI-Server,abhigyanpatwari/GitNexus,"Return concrete files/modules/adapters worth reusing and a verdict on whether the current reanchored bucket should be kept, upgraded, or downgraded.",Do not treat licensing as a filter. Do not propose replacing native foundations unless source evidence is overwhelming.,dataexpert-io/data-engineer-handbook,v6_unified_source_of_truth_pack,"Before recommending direct code use, inspect the target repo row in the v6.1 operational/phase/source-audit boards. Respect copyleft_strategy_v6_1, preferred_boundary_model_v6_1, and open_compliance_if_used_as_is_v6_1. Do not assume reverse engineering is mandatory or that as-is use is always sensible.","If the repo-level strategy says bounded_sidecar_preferred or boundary_first_then_decide_as_is_vs_reimplementation, audit clean interfaces, protocol seams, subprocess/container boundaries, and what would be required to reimplement only the strategically necessary portions.",v6.3_final_source_of_truth
SCR_0119,,,,,,,,,,ScriptoriumAI repo packet,ScriptoriumAI,ScriptoriumAI re-anchored VS Code packets v1,Doriandarko/o1-engineer,doriandarko/o1-engineer,Candidate Bench,P3,bookmark candidate only,"Audit Doriandarko/o1-engineer for ScriptoriumAI. Start from the reanchored bucket 'Candidate Bench' and current reality status 'bookmark candidate only'. Confirm actual implemented capability, hidden reusable modules, extension seams, and whether it strengthens the existing Unimplemented but relevant candidate lane. Focus on: Inspect planner/task graph; provider abstraction; tool registry or MCP bridges; memory/state schema; approvals/retries; telemetry/event bus; plugin or skill loading 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 planner loops, tool registries, MCP servers/clients, prompt/skill folders, memory stores, approval gates, background-job orchestration, and undocumented provider adapters.","Treat as unimplemented ScriptoriumAI candidate only. Do not let it redefine the current stack. Integrate only if a later audit proves it fills a real gap in the existing surfaces such as Dashboard, Editor, Corpus Graph, Runboard, AI Kanban, Corpus Search, Patch Review Queue, Visualizations, Whiteboard, Mind Map, PDF Intake, AI Diagram Studio, Video Studio, Research Agent, New Research Topic, Skills Manager, OpenAPI Routing, Manim Sandbox, Settings.","Repurpose here means mining for specific modules, algorithms, UI patterns, ingestion logic, workflow ideas, or export formats rather than assuming a full product transplant.",native/scriptoriumai-ui,native/ScriptoriumAI-Server,abhigyanpatwari/GitNexus,"Return concrete files/modules/adapters worth reusing and a verdict on whether the current reanchored bucket should be kept, upgraded, or downgraded.",Do not treat licensing as a filter. Do not propose replacing native foundations unless source evidence is overwhelming.,doriandarko/o1-engineer,v6_unified_source_of_truth_pack,"Before recommending direct code use, inspect the target repo row in the v6.1 operational/phase/source-audit boards. Respect copyleft_strategy_v6_1, preferred_boundary_model_v6_1, and open_compliance_if_used_as_is_v6_1. Do not assume reverse engineering is mandatory or that as-is use is always sensible.","If the repo-level strategy says bounded_sidecar_preferred or boundary_first_then_decide_as_is_vs_reimplementation, audit clean interfaces, protocol seams, subprocess/container boundaries, and what would be required to reimplement only the strategically necessary portions.",v6.3_final_source_of_truth
SCR_0120,,,,,,,,,,ScriptoriumAI repo packet,ScriptoriumAI,ScriptoriumAI re-anchored VS Code packets v1,DrewThomasson/ebook2audiobook,drewthomasson/ebook2audiobook,Candidate Bench,P3,bookmark candidate only,"Audit DrewThomasson/ebook2audiobook for ScriptoriumAI. Start from the reanchored bucket 'Candidate Bench' and current reality status 'bookmark candidate only'. Confirm actual implemented capability, hidden reusable modules, extension seams, and whether it strengthens the existing Unimplemented but relevant candidate lane. Focus on: Inspect streaming pipeline; VAD/segmentation; device abstraction; latency handling; multilingual or translation chain; local/offline fallback; API wrappers.","Inspect package manifests, README/docs, src tree, examples, tests, CI workflows, config files, migrations/schemas, and hidden feature flags or experimental modules. Look for streaming, VAD, wakeword, buffering, diarization, device handling, latency compensation, and command grammar or transcript post-processing.","Treat as unimplemented ScriptoriumAI candidate only. Do not let it redefine the current stack. Integrate only if a later audit proves it fills a real gap in the existing surfaces such as Dashboard, Editor, Corpus Graph, Runboard, AI Kanban, Corpus Search, Patch Review Queue, Visualizations, Whiteboard, Mind Map, PDF Intake, AI Diagram Studio, Video Studio, Research Agent, New Research Topic, Skills Manager, OpenAPI Routing, Manim Sandbox, Settings.","Repurpose here means mining for specific modules, algorithms, UI patterns, ingestion logic, workflow ideas, or export formats rather than assuming a full product transplant.",native/scriptoriumai-ui,native/ScriptoriumAI-Server,abhigyanpatwari/GitNexus,"Return concrete files/modules/adapters worth reusing and a verdict on whether the current reanchored bucket should be kept, upgraded, or downgraded.",Do not treat licensing as a filter. Do not propose replacing native foundations unless source evidence is overwhelming.,drewthomasson/ebook2audiobook,v6_unified_source_of_truth_pack,"Before recommending direct code use, inspect the target repo row in the v6.1 operational/phase/source-audit boards. Respect copyleft_strategy_v6_1, preferred_boundary_model_v6_1, and open_compliance_if_used_as_is_v6_1. Do not assume reverse engineering is mandatory or that as-is use is always sensible.","If the repo-level strategy says bounded_sidecar_preferred or boundary_first_then_decide_as_is_vs_reimplementation, audit clean interfaces, protocol seams, subprocess/container boundaries, and what would be required to reimplement only the strategically necessary portions.",v6.3_final_source_of_truth
SCR_0121,,,,,,,,,,ScriptoriumAI repo packet,ScriptoriumAI,ScriptoriumAI re-anchored VS Code packets v1,EbookFoundation/free-programming-books,ebookfoundation/free-programming-books,Candidate Bench,P3,bookmark candidate only,"Audit EbookFoundation/free-programming-books for ScriptoriumAI. Start from the reanchored bucket 'Candidate Bench' and current reality status 'bookmark candidate only'. Confirm actual implemented capability, hidden reusable modules, extension seams, and whether it strengthens the existing Unimplemented but relevant candidate lane. Focus on: Inspect package/module map; entrypoints; config and schema files; adapters/integrations; persistence model; tests/examples; hidden feature flags; plugin 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 hidden admin tools, reusable services, plugin systems, import/export, analytics, background jobs, and any engine more valuable than the public README suggests.","Treat as unimplemented ScriptoriumAI candidate only. Do not let it redefine the current stack. Integrate only if a later audit proves it fills a real gap in the existing surfaces such as Dashboard, Editor, Corpus Graph, Runboard, AI Kanban, Corpus Search, Patch Review Queue, Visualizations, Whiteboard, Mind Map, PDF Intake, AI Diagram Studio, Video Studio, Research Agent, New Research Topic, Skills Manager, OpenAPI Routing, Manim Sandbox, Settings.","Repurpose here means mining for specific modules, algorithms, UI patterns, ingestion logic, workflow ideas, or export formats rather than assuming a full product transplant.",native/scriptoriumai-ui,native/ScriptoriumAI-Server,abhigyanpatwari/GitNexus,"Return concrete files/modules/adapters worth reusing and a verdict on whether the current reanchored bucket should be kept, upgraded, or downgraded.",Do not treat licensing as a filter. Do not propose replacing native foundations unless source evidence is overwhelming.,ebookfoundation/free-programming-books,v6_unified_source_of_truth_pack,"Before recommending direct code use, inspect the target repo row in the v6.1 operational/phase/source-audit boards. Respect copyleft_strategy_v6_1, preferred_boundary_model_v6_1, and open_compliance_if_used_as_is_v6_1. Do not assume reverse engineering is mandatory or that as-is use is always sensible.","If the repo-level strategy says bounded_sidecar_preferred or boundary_first_then_decide_as_is_vs_reimplementation, audit clean interfaces, protocol seams, subprocess/container boundaries, and what would be required to reimplement only the strategically necessary portions.",v6.3_final_source_of_truth
SCR_0122,,,,,,,,,,ScriptoriumAI repo packet,ScriptoriumAI,ScriptoriumAI re-anchored VS Code packets v1,Errichto/youtube,errichto/youtube,Candidate Bench,P3,bookmark candidate only,"Audit Errichto/youtube for ScriptoriumAI. Start from the reanchored bucket 'Candidate Bench' and current reality status 'bookmark candidate only'. Confirm actual implemented capability, hidden reusable modules, extension seams, and whether it strengthens the existing Unimplemented but relevant candidate lane. Focus on: Inspect package/module map; entrypoints; config and schema files; adapters/integrations; persistence model; tests/examples; hidden feature flags; plugin 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 hidden admin tools, reusable services, plugin systems, import/export, analytics, background jobs, and any engine more valuable than the public README suggests.","Treat as unimplemented ScriptoriumAI candidate only. Do not let it redefine the current stack. Integrate only if a later audit proves it fills a real gap in the existing surfaces such as Dashboard, Editor, Corpus Graph, Runboard, AI Kanban, Corpus Search, Patch Review Queue, Visualizations, Whiteboard, Mind Map, PDF Intake, AI Diagram Studio, Video Studio, Research Agent, New Research Topic, Skills Manager, OpenAPI Routing, Manim Sandbox, Settings.","Repurpose here means mining for specific modules, algorithms, UI patterns, ingestion logic, workflow ideas, or export formats rather than assuming a full product transplant.",manimcommunity/manim,remotion-dev/remotion,native/ScriptoriumAI-Visualizer,"Return concrete files/modules/adapters worth reusing and a verdict on whether the current reanchored bucket should be kept, upgraded, or downgraded.",Do not treat licensing as a filter. Do not propose replacing native foundations unless source evidence is overwhelming.,errichto/youtube,v6_unified_source_of_truth_pack,"Before recommending direct code use, inspect the target repo row in the v6.1 operational/phase/source-audit boards. Respect copyleft_strategy_v6_1, preferred_boundary_model_v6_1, and open_compliance_if_used_as_is_v6_1. Do not assume reverse engineering is mandatory or that as-is use is always sensible.","If the repo-level strategy says bounded_sidecar_preferred or boundary_first_then_decide_as_is_vs_reimplementation, audit clean interfaces, protocol seams, subprocess/container boundaries, and what would be required to reimplement only the strategically necessary portions.",v6.3_final_source_of_truth
SCR_0123,,,,,,,,,,ScriptoriumAI repo packet,ScriptoriumAI,ScriptoriumAI re-anchored VS Code packets v1,EverMind-AI/EverMemOS,evermind-ai/evermemos,Candidate Bench,P3,bookmark candidate only,"Audit EverMind-AI/EverMemOS for ScriptoriumAI. Start from the reanchored bucket 'Candidate Bench' and current reality status 'bookmark candidate only'. Confirm actual implemented capability, hidden reusable modules, extension seams, and whether it strengthens the existing Unimplemented but relevant candidate lane. Focus on: Inspect planner/task graph; provider abstraction; tool registry or MCP bridges; memory/state schema; approvals/retries; telemetry/event bus; plugin or skill loading 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 planner loops, tool registries, MCP servers/clients, prompt/skill folders, memory stores, approval gates, background-job orchestration, and undocumented provider adapters.","Treat as unimplemented ScriptoriumAI candidate only. Do not let it redefine the current stack. Integrate only if a later audit proves it fills a real gap in the existing surfaces such as Dashboard, Editor, Corpus Graph, Runboard, AI Kanban, Corpus Search, Patch Review Queue, Visualizations, Whiteboard, Mind Map, PDF Intake, AI Diagram Studio, Video Studio, Research Agent, New Research Topic, Skills Manager, OpenAPI Routing, Manim Sandbox, Settings.","Repurpose here means mining for specific modules, algorithms, UI patterns, ingestion logic, workflow ideas, or export formats rather than assuming a full product transplant.",native/ScriptoriumAI-Server,stanford-oval/storm,abhigyanpatwari/GitNexus,"Return concrete files/modules/adapters worth reusing and a verdict on whether the current reanchored bucket should be kept, upgraded, or downgraded.",Do not treat licensing as a filter. Do not propose replacing native foundations unless source evidence is overwhelming.,evermind-ai/evermemos,v6_unified_source_of_truth_pack,"Before recommending direct code use, inspect the target repo row in the v6.1 operational/phase/source-audit boards. Respect copyleft_strategy_v6_1, preferred_boundary_model_v6_1, and open_compliance_if_used_as_is_v6_1. Do not assume reverse engineering is mandatory or that as-is use is always sensible.","If the repo-level strategy says bounded_sidecar_preferred or boundary_first_then_decide_as_is_vs_reimplementation, audit clean interfaces, protocol seams, subprocess/container boundaries, and what would be required to reimplement only the strategically necessary portions.",v6.3_final_source_of_truth
SCR_0124,,,,,,,,,,ScriptoriumAI repo packet,ScriptoriumAI,ScriptoriumAI re-anchored VS Code packets v1,FareedKhan-dev/complex-RAG-guide,fareedkhan-dev/complex-rag-guide,Candidate Bench,P3,bookmark candidate only,"Audit FareedKhan-dev/complex-RAG-guide for ScriptoriumAI. Start from the reanchored bucket 'Candidate Bench' and current reality status 'bookmark candidate only'. Confirm actual implemented capability, hidden reusable modules, extension seams, and whether it strengthens the existing Unimplemented but relevant candidate lane. Focus on: 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.","Treat as unimplemented ScriptoriumAI candidate only. Do not let it redefine the current stack. Integrate only if a later audit proves it fills a real gap in the existing surfaces such as Dashboard, Editor, Corpus Graph, Runboard, AI Kanban, Corpus Search, Patch Review Queue, Visualizations, Whiteboard, Mind Map, PDF Intake, AI Diagram Studio, Video Studio, Research Agent, New Research Topic, Skills Manager, OpenAPI Routing, Manim Sandbox, Settings.","Repurpose here means mining for specific modules, algorithms, UI patterns, ingestion logic, workflow ideas, or export formats rather than assuming a full product transplant.",native/scriptoriumai-ui,native/ScriptoriumAI-Server,abhigyanpatwari/GitNexus,"Return concrete files/modules/adapters worth reusing and a verdict on whether the current reanchored bucket should be kept, upgraded, or downgraded.",Do not treat licensing as a filter. Do not propose replacing native foundations unless source evidence is overwhelming.,fareedkhan-dev/complex-rag-guide,v6_unified_source_of_truth_pack,"Before recommending direct code use, inspect the target repo row in the v6.1 operational/phase/source-audit boards. Respect copyleft_strategy_v6_1, preferred_boundary_model_v6_1, and open_compliance_if_used_as_is_v6_1. Do not assume reverse engineering is mandatory or that as-is use is always sensible.","If the repo-level strategy says bounded_sidecar_preferred or boundary_first_then_decide_as_is_vs_reimplementation, audit clean interfaces, protocol seams, subprocess/container boundaries, and what would be required to reimplement only the strategically necessary portions.",v6.3_final_source_of_truth
SCR_0125,,,,,,,,,,ScriptoriumAI repo packet,ScriptoriumAI,ScriptoriumAI re-anchored VS Code packets v1,GokuMohandas/Made-With-ML,gokumohandas/made-with-ml,Candidate Bench,P3,bookmark candidate only,"Audit GokuMohandas/Made-With-ML for ScriptoriumAI. Start from the reanchored bucket 'Candidate Bench' and current reality status 'bookmark candidate only'. Confirm actual implemented capability, hidden reusable modules, extension seams, and whether it strengthens the existing Unimplemented but relevant candidate lane. Focus on: Inspect planner/task graph; provider abstraction; tool registry or MCP bridges; memory/state schema; approvals/retries; telemetry/event bus; plugin or skill loading 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 planner loops, tool registries, MCP servers/clients, prompt/skill folders, memory stores, approval gates, background-job orchestration, and undocumented provider adapters.","Treat as unimplemented ScriptoriumAI candidate only. Do not let it redefine the current stack. Integrate only if a later audit proves it fills a real gap in the existing surfaces such as Dashboard, Editor, Corpus Graph, Runboard, AI Kanban, Corpus Search, Patch Review Queue, Visualizations, Whiteboard, Mind Map, PDF Intake, AI Diagram Studio, Video Studio, Research Agent, New Research Topic, Skills Manager, OpenAPI Routing, Manim Sandbox, Settings.","Repurpose here means mining for specific modules, algorithms, UI patterns, ingestion logic, workflow ideas, or export formats rather than assuming a full product transplant.",native/scriptoriumai-ui,native/ScriptoriumAI-Server,abhigyanpatwari/GitNexus,"Return concrete files/modules/adapters worth reusing and a verdict on whether the current reanchored bucket should be kept, upgraded, or downgraded.",Do not treat licensing as a filter. Do not propose replacing native foundations unless source evidence is overwhelming.,gokumohandas/made-with-ml,v6_unified_source_of_truth_pack,"Before recommending direct code use, inspect the target repo row in the v6.1 operational/phase/source-audit boards. Respect copyleft_strategy_v6_1, preferred_boundary_model_v6_1, and open_compliance_if_used_as_is_v6_1. Do not assume reverse engineering is mandatory or that as-is use is always sensible.","If the repo-level strategy says bounded_sidecar_preferred or boundary_first_then_decide_as_is_vs_reimplementation, audit clean interfaces, protocol seams, subprocess/container boundaries, and what would be required to reimplement only the strategically necessary portions.",v6.3_final_source_of_truth
SCR_0126,,,,,,,,,,ScriptoriumAI repo packet,ScriptoriumAI,ScriptoriumAI re-anchored VS Code packets v1,HKUDS/Paper2Slides,hkuds/paper2slides,Candidate Bench,P3,bookmark candidate only,"Audit HKUDS/Paper2Slides for ScriptoriumAI. Start from the reanchored bucket 'Candidate Bench' and current reality status 'bookmark candidate only'. Confirm actual implemented capability, hidden reusable modules, extension seams, and whether it strengthens the existing Unimplemented but relevant candidate lane. Focus on: Inspect document/block schema; sync/persistence model; permissions and sharing; citation/external-source pipeline; import/export adapters; plugin/extension points; editor rendering model.","Inspect package manifests, README/docs, src tree, examples, tests, CI workflows, config files, migrations/schemas, and hidden feature flags or experimental modules. Look for document/block schema, sync/conflict logic, citation handling, editor plugins, export/render pipeline, prompt chains, report assembly, and collaborative presence code.","Treat as unimplemented ScriptoriumAI candidate only. Do not let it redefine the current stack. Integrate only if a later audit proves it fills a real gap in the existing surfaces such as Dashboard, Editor, Corpus Graph, Runboard, AI Kanban, Corpus Search, Patch Review Queue, Visualizations, Whiteboard, Mind Map, PDF Intake, AI Diagram Studio, Video Studio, Research Agent, New Research Topic, Skills Manager, OpenAPI Routing, Manim Sandbox, Settings.","Repurpose here means mining for specific modules, algorithms, UI patterns, ingestion logic, workflow ideas, or export formats rather than assuming a full product transplant.",native/scriptoriumai-ui,native/ScriptoriumAI-Server,abhigyanpatwari/GitNexus,"Return concrete files/modules/adapters worth reusing and a verdict on whether the current reanchored bucket should be kept, upgraded, or downgraded.",Do not treat licensing as a filter. Do not propose replacing native foundations unless source evidence is overwhelming.,hkuds/paper2slides,v6_unified_source_of_truth_pack,"Before recommending direct code use, inspect the target repo row in the v6.1 operational/phase/source-audit boards. Respect copyleft_strategy_v6_1, preferred_boundary_model_v6_1, and open_compliance_if_used_as_is_v6_1. Do not assume reverse engineering is mandatory or that as-is use is always sensible.","If the repo-level strategy says bounded_sidecar_preferred or boundary_first_then_decide_as_is_vs_reimplementation, audit clean interfaces, protocol seams, subprocess/container boundaries, and what would be required to reimplement only the strategically necessary portions.",v6.3_final_source_of_truth
SCR_0127,,,,,,,,,,ScriptoriumAI repo packet,ScriptoriumAI,ScriptoriumAI re-anchored VS Code packets v1,JarodMica/audiobook_maker,jarodmica/audiobook_maker,Candidate Bench,P3,bookmark candidate only,"Audit JarodMica/audiobook_maker for ScriptoriumAI. Start from the reanchored bucket 'Candidate Bench' and current reality status 'bookmark candidate only'. Confirm actual implemented capability, hidden reusable modules, extension seams, and whether it strengthens the existing Unimplemented but relevant candidate lane. Focus on: Inspect streaming pipeline; VAD/segmentation; device abstraction; latency handling; multilingual or translation chain; local/offline fallback; API wrappers.","Inspect package manifests, README/docs, src tree, examples, tests, CI workflows, config files, migrations/schemas, and hidden feature flags or experimental modules. Look for streaming, VAD, wakeword, buffering, diarization, device handling, latency compensation, and command grammar or transcript post-processing.","Treat as unimplemented ScriptoriumAI candidate only. Do not let it redefine the current stack. Integrate only if a later audit proves it fills a real gap in the existing surfaces such as Dashboard, Editor, Corpus Graph, Runboard, AI Kanban, Corpus Search, Patch Review Queue, Visualizations, Whiteboard, Mind Map, PDF Intake, AI Diagram Studio, Video Studio, Research Agent, New Research Topic, Skills Manager, OpenAPI Routing, Manim Sandbox, Settings.","Repurpose here means mining for specific modules, algorithms, UI patterns, ingestion logic, workflow ideas, or export formats rather than assuming a full product transplant.",native/scriptoriumai-ui,native/ScriptoriumAI-Server,abhigyanpatwari/GitNexus,"Return concrete files/modules/adapters worth reusing and a verdict on whether the current reanchored bucket should be kept, upgraded, or downgraded.",Do not treat licensing as a filter. Do not propose replacing native foundations unless source evidence is overwhelming.,jarodmica/audiobook_maker,v6_unified_source_of_truth_pack,"Before recommending direct code use, inspect the target repo row in the v6.1 operational/phase/source-audit boards. Respect copyleft_strategy_v6_1, preferred_boundary_model_v6_1, and open_compliance_if_used_as_is_v6_1. Do not assume reverse engineering is mandatory or that as-is use is always sensible.","If the repo-level strategy says bounded_sidecar_preferred or boundary_first_then_decide_as_is_vs_reimplementation, audit clean interfaces, protocol seams, subprocess/container boundaries, and what would be required to reimplement only the strategically necessary portions.",v6.3_final_source_of_truth
SCR_0128,,,,,,,,,,ScriptoriumAI repo packet,ScriptoriumAI,ScriptoriumAI re-anchored VS Code packets v1,JetBrains/resharper-fsharp,jetbrains/resharper-fsharp,Candidate Bench,P3,bookmark candidate only,"Audit JetBrains/resharper-fsharp for ScriptoriumAI. Start from the reanchored bucket 'Candidate Bench' and current reality status 'bookmark candidate only'. Confirm actual implemented capability, hidden reusable modules, extension seams, and whether it strengthens the existing Unimplemented but relevant candidate lane. Focus on: Inspect document/block schema; sync/persistence model; permissions and sharing; citation/external-source pipeline; import/export adapters; plugin/extension points; editor rendering model.","Inspect package manifests, README/docs, src tree, examples, tests, CI workflows, config files, migrations/schemas, and hidden feature flags or experimental modules. Look for document/block schema, sync/conflict logic, citation handling, editor plugins, export/render pipeline, prompt chains, report assembly, and collaborative presence code.","Treat as unimplemented ScriptoriumAI candidate only. Do not let it redefine the current stack. Integrate only if a later audit proves it fills a real gap in the existing surfaces such as Dashboard, Editor, Corpus Graph, Runboard, AI Kanban, Corpus Search, Patch Review Queue, Visualizations, Whiteboard, Mind Map, PDF Intake, AI Diagram Studio, Video Studio, Research Agent, New Research Topic, Skills Manager, OpenAPI Routing, Manim Sandbox, Settings.","Repurpose here means mining for specific modules, algorithms, UI patterns, ingestion logic, workflow ideas, or export formats rather than assuming a full product transplant.",native/scriptoriumai-ui,native/ScriptoriumAI-Server,abhigyanpatwari/GitNexus,"Return concrete files/modules/adapters worth reusing and a verdict on whether the current reanchored bucket should be kept, upgraded, or downgraded.",Do not treat licensing as a filter. Do not propose replacing native foundations unless source evidence is overwhelming.,jetbrains/resharper-fsharp,v6_unified_source_of_truth_pack,"Before recommending direct code use, inspect the target repo row in the v6.1 operational/phase/source-audit boards. Respect copyleft_strategy_v6_1, preferred_boundary_model_v6_1, and open_compliance_if_used_as_is_v6_1. Do not assume reverse engineering is mandatory or that as-is use is always sensible.","If the repo-level strategy says bounded_sidecar_preferred or boundary_first_then_decide_as_is_vs_reimplementation, audit clean interfaces, protocol seams, subprocess/container boundaries, and what would be required to reimplement only the strategically necessary portions.",v6.3_final_source_of_truth
SCR_0129,,,,,,,,,,ScriptoriumAI repo packet,ScriptoriumAI,ScriptoriumAI re-anchored VS Code packets v1,Jpisnice/shadcn-ui-mcp-server,jpisnice/shadcn-ui-mcp-server,Candidate Bench,P3,bookmark candidate only,"Audit Jpisnice/shadcn-ui-mcp-server for ScriptoriumAI. Start from the reanchored bucket 'Candidate Bench' and current reality status 'bookmark candidate only'. Confirm actual implemented capability, hidden reusable modules, extension seams, and whether it strengthens the existing Unimplemented but relevant candidate lane. Focus on: Inspect planner/task graph; provider abstraction; tool registry or MCP bridges; memory/state schema; approvals/retries; telemetry/event bus; plugin or skill loading 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 planner loops, tool registries, MCP servers/clients, prompt/skill folders, memory stores, approval gates, background-job orchestration, and undocumented provider adapters.","Treat as unimplemented ScriptoriumAI candidate only. Do not let it redefine the current stack. Integrate only if a later audit proves it fills a real gap in the existing surfaces such as Dashboard, Editor, Corpus Graph, Runboard, AI Kanban, Corpus Search, Patch Review Queue, Visualizations, Whiteboard, Mind Map, PDF Intake, AI Diagram Studio, Video Studio, Research Agent, New Research Topic, Skills Manager, OpenAPI Routing, Manim Sandbox, Settings.","Repurpose here means mining for specific modules, algorithms, UI patterns, ingestion logic, workflow ideas, or export formats rather than assuming a full product transplant.",native/scriptoriumai-ui,native/ScriptoriumAI-Server,abhigyanpatwari/GitNexus,"Return concrete files/modules/adapters worth reusing and a verdict on whether the current reanchored bucket should be kept, upgraded, or downgraded.",Do not treat licensing as a filter. Do not propose replacing native foundations unless source evidence is overwhelming.,jpisnice/shadcn-ui-mcp-server,v6_unified_source_of_truth_pack,"Before recommending direct code use, inspect the target repo row in the v6.1 operational/phase/source-audit boards. Respect copyleft_strategy_v6_1, preferred_boundary_model_v6_1, and open_compliance_if_used_as_is_v6_1. Do not assume reverse engineering is mandatory or that as-is use is always sensible.","If the repo-level strategy says bounded_sidecar_preferred or boundary_first_then_decide_as_is_vs_reimplementation, audit clean interfaces, protocol seams, subprocess/container boundaries, and what would be required to reimplement only the strategically necessary portions.",v6.3_final_source_of_truth
SCR_0130,,,,,,,,,,ScriptoriumAI repo packet,ScriptoriumAI,ScriptoriumAI re-anchored VS Code packets v1,KeaBase/kea-research,keabase/kea-research,Candidate Bench,P3,bookmark candidate only,"Audit KeaBase/kea-research for ScriptoriumAI. Start from the reanchored bucket 'Candidate Bench' and current reality status 'bookmark candidate only'. Confirm actual implemented capability, hidden reusable modules, extension seams, and whether it strengthens the existing Unimplemented but relevant candidate lane. Focus on: 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.","Treat as unimplemented ScriptoriumAI candidate only. Do not let it redefine the current stack. Integrate only if a later audit proves it fills a real gap in the existing surfaces such as Dashboard, Editor, Corpus Graph, Runboard, AI Kanban, Corpus Search, Patch Review Queue, Visualizations, Whiteboard, Mind Map, PDF Intake, AI Diagram Studio, Video Studio, Research Agent, New Research Topic, Skills Manager, OpenAPI Routing, Manim Sandbox, Settings.","Repurpose here means mining for specific modules, algorithms, UI patterns, ingestion logic, workflow ideas, or export formats rather than assuming a full product transplant.",native/ScriptoriumAI-Server,stanford-oval/storm,abhigyanpatwari/GitNexus,"Return concrete files/modules/adapters worth reusing and a verdict on whether the current reanchored bucket should be kept, upgraded, or downgraded.",Do not treat licensing as a filter. Do not propose replacing native foundations unless source evidence is overwhelming.,keabase/kea-research,v6_unified_source_of_truth_pack,"Before recommending direct code use, inspect the target repo row in the v6.1 operational/phase/source-audit boards. Respect copyleft_strategy_v6_1, preferred_boundary_model_v6_1, and open_compliance_if_used_as_is_v6_1. Do not assume reverse engineering is mandatory or that as-is use is always sensible.","If the repo-level strategy says bounded_sidecar_preferred or boundary_first_then_decide_as_is_vs_reimplementation, audit clean interfaces, protocol seams, subprocess/container boundaries, and what would be required to reimplement only the strategically necessary portions.",v6.3_final_source_of_truth
SCR_0131,,,,,,,,,,ScriptoriumAI repo packet,ScriptoriumAI,ScriptoriumAI re-anchored VS Code packets v1,Kevin-thu/StoryMem,kevin-thu/storymem,Candidate Bench,P3,bookmark candidate only,"Audit Kevin-thu/StoryMem for ScriptoriumAI. Start from the reanchored bucket 'Candidate Bench' and current reality status 'bookmark candidate only'. Confirm actual implemented capability, hidden reusable modules, extension seams, and whether it strengthens the existing Unimplemented but relevant candidate lane. Focus on: Inspect planner/task graph; provider abstraction; tool registry or MCP bridges; memory/state schema; approvals/retries; telemetry/event bus; plugin or skill loading 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 planner loops, tool registries, MCP servers/clients, prompt/skill folders, memory stores, approval gates, background-job orchestration, and undocumented provider adapters.","Treat as unimplemented ScriptoriumAI candidate only. Do not let it redefine the current stack. Integrate only if a later audit proves it fills a real gap in the existing surfaces such as Dashboard, Editor, Corpus Graph, Runboard, AI Kanban, Corpus Search, Patch Review Queue, Visualizations, Whiteboard, Mind Map, PDF Intake, AI Diagram Studio, Video Studio, Research Agent, New Research Topic, Skills Manager, OpenAPI Routing, Manim Sandbox, Settings.","Repurpose here means mining for specific modules, algorithms, UI patterns, ingestion logic, workflow ideas, or export formats rather than assuming a full product transplant.",native/ScriptoriumAI-Server,stanford-oval/storm,abhigyanpatwari/GitNexus,"Return concrete files/modules/adapters worth reusing and a verdict on whether the current reanchored bucket should be kept, upgraded, or downgraded.",Do not treat licensing as a filter. Do not propose replacing native foundations unless source evidence is overwhelming.,kevin-thu/storymem,v6_unified_source_of_truth_pack,"Before recommending direct code use, inspect the target repo row in the v6.1 operational/phase/source-audit boards. Respect copyleft_strategy_v6_1, preferred_boundary_model_v6_1, and open_compliance_if_used_as_is_v6_1. Do not assume reverse engineering is mandatory or that as-is use is always sensible.","If the repo-level strategy says bounded_sidecar_preferred or boundary_first_then_decide_as_is_vs_reimplementation, audit clean interfaces, protocol seams, subprocess/container boundaries, and what would be required to reimplement only the strategically necessary portions.",v6.3_final_source_of_truth
SCR_0132,,,,,,,,,,ScriptoriumAI repo packet,ScriptoriumAI,ScriptoriumAI re-anchored VS Code packets v1,LLmHub-dev/open-computer-use,llmhub-dev/open-computer-use,Candidate Bench,P3,bookmark candidate only,"Audit LLmHub-dev/open-computer-use for ScriptoriumAI. Start from the reanchored bucket 'Candidate Bench' and current reality status 'bookmark candidate only'. Confirm actual implemented capability, hidden reusable modules, extension seams, and whether it strengthens the existing Unimplemented but relevant candidate lane. Focus on: Inspect planner/task graph; provider abstraction; tool registry or MCP bridges; memory/state schema; approvals/retries; telemetry/event bus; plugin or skill loading 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 planner loops, tool registries, MCP servers/clients, prompt/skill folders, memory stores, approval gates, background-job orchestration, and undocumented provider adapters.","Treat as unimplemented ScriptoriumAI candidate only. Do not let it redefine the current stack. Integrate only if a later audit proves it fills a real gap in the existing surfaces such as Dashboard, Editor, Corpus Graph, Runboard, AI Kanban, Corpus Search, Patch Review Queue, Visualizations, Whiteboard, Mind Map, PDF Intake, AI Diagram Studio, Video Studio, Research Agent, New Research Topic, Skills Manager, OpenAPI Routing, Manim Sandbox, Settings.","Repurpose here means mining for specific modules, algorithms, UI patterns, ingestion logic, workflow ideas, or export formats rather than assuming a full product transplant.",native/ScriptoriumAI-Server,stanford-oval/storm,abhigyanpatwari/GitNexus,"Return concrete files/modules/adapters worth reusing and a verdict on whether the current reanchored bucket should be kept, upgraded, or downgraded.",Do not treat licensing as a filter. Do not propose replacing native foundations unless source evidence is overwhelming.,llmhub-dev/open-computer-use,v6_unified_source_of_truth_pack,"Before recommending direct code use, inspect the target repo row in the v6.1 operational/phase/source-audit boards. Respect copyleft_strategy_v6_1, preferred_boundary_model_v6_1, and open_compliance_if_used_as_is_v6_1. Do not assume reverse engineering is mandatory or that as-is use is always sensible.","If the repo-level strategy says bounded_sidecar_preferred or boundary_first_then_decide_as_is_vs_reimplementation, audit clean interfaces, protocol seams, subprocess/container boundaries, and what would be required to reimplement only the strategically necessary portions.",v6.3_final_source_of_truth
SCR_0133,,,,,,,,,,ScriptoriumAI repo packet,ScriptoriumAI,ScriptoriumAI re-anchored VS Code packets v1,MemoriLabs/Memori,memorilabs/memori,Candidate Bench,P3,bookmark candidate only,"Audit MemoriLabs/Memori for ScriptoriumAI. Start from the reanchored bucket 'Candidate Bench' and current reality status 'bookmark candidate only'. Confirm actual implemented capability, hidden reusable modules, extension seams, and whether it strengthens the existing Unimplemented but relevant candidate lane. Focus on: Inspect planner/task graph; provider abstraction; tool registry or MCP bridges; memory/state schema; approvals/retries; telemetry/event bus; plugin or skill loading 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 planner loops, tool registries, MCP servers/clients, prompt/skill folders, memory stores, approval gates, background-job orchestration, and undocumented provider adapters.","Treat as unimplemented ScriptoriumAI candidate only. Do not let it redefine the current stack. Integrate only if a later audit proves it fills a real gap in the existing surfaces such as Dashboard, Editor, Corpus Graph, Runboard, AI Kanban, Corpus Search, Patch Review Queue, Visualizations, Whiteboard, Mind Map, PDF Intake, AI Diagram Studio, Video Studio, Research Agent, New Research Topic, Skills Manager, OpenAPI Routing, Manim Sandbox, Settings.","Repurpose here means mining for specific modules, algorithms, UI patterns, ingestion logic, workflow ideas, or export formats rather than assuming a full product transplant.",native/ScriptoriumAI-Server,stanford-oval/storm,abhigyanpatwari/GitNexus,"Return concrete files/modules/adapters worth reusing and a verdict on whether the current reanchored bucket should be kept, upgraded, or downgraded.",Do not treat licensing as a filter. Do not propose replacing native foundations unless source evidence is overwhelming.,memorilabs/memori,v6_unified_source_of_truth_pack,"Before recommending direct code use, inspect the target repo row in the v6.1 operational/phase/source-audit boards. Respect copyleft_strategy_v6_1, preferred_boundary_model_v6_1, and open_compliance_if_used_as_is_v6_1. Do not assume reverse engineering is mandatory or that as-is use is always sensible.","If the repo-level strategy says bounded_sidecar_preferred or boundary_first_then_decide_as_is_vs_reimplementation, audit clean interfaces, protocol seams, subprocess/container boundaries, and what would be required to reimplement only the strategically necessary portions.",v6.3_final_source_of_truth
SCR_0134,,,,,,,,,,ScriptoriumAI repo packet,ScriptoriumAI,ScriptoriumAI re-anchored VS Code packets v1,NeoVertex1/nuggets,neovertex1/nuggets,Candidate Bench,P3,bookmark candidate only,"Audit NeoVertex1/nuggets for ScriptoriumAI. Start from the reanchored bucket 'Candidate Bench' and current reality status 'bookmark candidate only'. Confirm actual implemented capability, hidden reusable modules, extension seams, and whether it strengthens the existing Unimplemented but relevant candidate lane. Focus on: Inspect planner/task graph; provider abstraction; tool registry or MCP bridges; memory/state schema; approvals/retries; telemetry/event bus; plugin or skill loading 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 planner loops, tool registries, MCP servers/clients, prompt/skill folders, memory stores, approval gates, background-job orchestration, and undocumented provider adapters.","Treat as unimplemented ScriptoriumAI candidate only. Do not let it redefine the current stack. Integrate only if a later audit proves it fills a real gap in the existing surfaces such as Dashboard, Editor, Corpus Graph, Runboard, AI Kanban, Corpus Search, Patch Review Queue, Visualizations, Whiteboard, Mind Map, PDF Intake, AI Diagram Studio, Video Studio, Research Agent, New Research Topic, Skills Manager, OpenAPI Routing, Manim Sandbox, Settings.","Repurpose here means mining for specific modules, algorithms, UI patterns, ingestion logic, workflow ideas, or export formats rather than assuming a full product transplant.",native/ScriptoriumAI-Server,stanford-oval/storm,abhigyanpatwari/GitNexus,"Return concrete files/modules/adapters worth reusing and a verdict on whether the current reanchored bucket should be kept, upgraded, or downgraded.",Do not treat licensing as a filter. Do not propose replacing native foundations unless source evidence is overwhelming.,neovertex1/nuggets,v6_unified_source_of_truth_pack,"Before recommending direct code use, inspect the target repo row in the v6.1 operational/phase/source-audit boards. Respect copyleft_strategy_v6_1, preferred_boundary_model_v6_1, and open_compliance_if_used_as_is_v6_1. Do not assume reverse engineering is mandatory or that as-is use is always sensible.","If the repo-level strategy says bounded_sidecar_preferred or boundary_first_then_decide_as_is_vs_reimplementation, audit clean interfaces, protocol seams, subprocess/container boundaries, and what would be required to reimplement only the strategically necessary portions.",v6.3_final_source_of_truth
SCR_0135,,,,,,,,,,ScriptoriumAI repo packet,ScriptoriumAI,ScriptoriumAI re-anchored VS Code packets v1,NirDiamant/RAG_Techniques,nirdiamant/rag_techniques,Candidate Bench,P3,bookmark candidate only,"Audit NirDiamant/RAG_Techniques for ScriptoriumAI. Start from the reanchored bucket 'Candidate Bench' and current reality status 'bookmark candidate only'. Confirm actual implemented capability, hidden reusable modules, extension seams, and whether it strengthens the existing Unimplemented but relevant candidate lane. Focus on: Inspect package/module map; entrypoints; config and schema files; adapters/integrations; persistence model; tests/examples; hidden feature flags; plugin 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 hidden admin tools, reusable services, plugin systems, import/export, analytics, background jobs, and any engine more valuable than the public README suggests.","Treat as unimplemented ScriptoriumAI candidate only. Do not let it redefine the current stack. Integrate only if a later audit proves it fills a real gap in the existing surfaces such as Dashboard, Editor, Corpus Graph, Runboard, AI Kanban, Corpus Search, Patch Review Queue, Visualizations, Whiteboard, Mind Map, PDF Intake, AI Diagram Studio, Video Studio, Research Agent, New Research Topic, Skills Manager, OpenAPI Routing, Manim Sandbox, Settings.","Repurpose here means mining for specific modules, algorithms, UI patterns, ingestion logic, workflow ideas, or export formats rather than assuming a full product transplant.",native/scriptoriumai-ui,native/ScriptoriumAI-Server,abhigyanpatwari/GitNexus,"Return concrete files/modules/adapters worth reusing and a verdict on whether the current reanchored bucket should be kept, upgraded, or downgraded.",Do not treat licensing as a filter. Do not propose replacing native foundations unless source evidence is overwhelming.,nirdiamant/rag_techniques,v6_unified_source_of_truth_pack,"Before recommending direct code use, inspect the target repo row in the v6.1 operational/phase/source-audit boards. Respect copyleft_strategy_v6_1, preferred_boundary_model_v6_1, and open_compliance_if_used_as_is_v6_1. Do not assume reverse engineering is mandatory or that as-is use is always sensible.","If the repo-level strategy says bounded_sidecar_preferred or boundary_first_then_decide_as_is_vs_reimplementation, audit clean interfaces, protocol seams, subprocess/container boundaries, and what would be required to reimplement only the strategically necessary portions.",v6.3_final_source_of_truth
SCR_0136,,,,,,,,,,ScriptoriumAI repo packet,ScriptoriumAI,ScriptoriumAI re-anchored VS Code packets v1,NirDiamant/agents-towards-production,nirdiamant/agents-towards-production,Candidate Bench,P3,bookmark candidate only,"Audit NirDiamant/agents-towards-production for ScriptoriumAI. Start from the reanchored bucket 'Candidate Bench' and current reality status 'bookmark candidate only'. Confirm actual implemented capability, hidden reusable modules, extension seams, and whether it strengthens the existing Unimplemented but relevant candidate lane. Focus on: Inspect planner/task graph; provider abstraction; tool registry or MCP bridges; memory/state schema; approvals/retries; telemetry/event bus; plugin or skill loading 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 planner loops, tool registries, MCP servers/clients, prompt/skill folders, memory stores, approval gates, background-job orchestration, and undocumented provider adapters.","Treat as unimplemented ScriptoriumAI candidate only. Do not let it redefine the current stack. Integrate only if a later audit proves it fills a real gap in the existing surfaces such as Dashboard, Editor, Corpus Graph, Runboard, AI Kanban, Corpus Search, Patch Review Queue, Visualizations, Whiteboard, Mind Map, PDF Intake, AI Diagram Studio, Video Studio, Research Agent, New Research Topic, Skills Manager, OpenAPI Routing, Manim Sandbox, Settings.","Repurpose here means mining for specific modules, algorithms, UI patterns, ingestion logic, workflow ideas, or export formats rather than assuming a full product transplant.",native/ScriptoriumAI-Server,stanford-oval/storm,abhigyanpatwari/GitNexus,"Return concrete files/modules/adapters worth reusing and a verdict on whether the current reanchored bucket should be kept, upgraded, or downgraded.",Do not treat licensing as a filter. Do not propose replacing native foundations unless source evidence is overwhelming.,nirdiamant/agents-towards-production,v6_unified_source_of_truth_pack,"Before recommending direct code use, inspect the target repo row in the v6.1 operational/phase/source-audit boards. Respect copyleft_strategy_v6_1, preferred_boundary_model_v6_1, and open_compliance_if_used_as_is_v6_1. Do not assume reverse engineering is mandatory or that as-is use is always sensible.","If the repo-level strategy says bounded_sidecar_preferred or boundary_first_then_decide_as_is_vs_reimplementation, audit clean interfaces, protocol seams, subprocess/container boundaries, and what would be required to reimplement only the strategically necessary portions.",v6.3_final_source_of_truth
SCR_0137,,,,,,,,,,ScriptoriumAI repo packet,ScriptoriumAI,ScriptoriumAI re-anchored VS Code packets v1,OpenMOSS/MOVA,openmoss/mova,Candidate Bench,P3,bookmark candidate only,"Audit OpenMOSS/MOVA for ScriptoriumAI. Start from the reanchored bucket 'Candidate Bench' and current reality status 'bookmark candidate only'. Confirm actual implemented capability, hidden reusable modules, extension seams, and whether it strengthens the existing Unimplemented but relevant candidate lane. Focus on: Inspect streaming pipeline; VAD/segmentation; device abstraction; latency handling; multilingual or translation chain; local/offline fallback; API wrappers.","Inspect package manifests, README/docs, src tree, examples, tests, CI workflows, config files, migrations/schemas, and hidden feature flags or experimental modules. Look for streaming, VAD, wakeword, buffering, diarization, device handling, latency compensation, and command grammar or transcript post-processing.","Treat as unimplemented ScriptoriumAI candidate only. Do not let it redefine the current stack. Integrate only if a later audit proves it fills a real gap in the existing surfaces such as Dashboard, Editor, Corpus Graph, Runboard, AI Kanban, Corpus Search, Patch Review Queue, Visualizations, Whiteboard, Mind Map, PDF Intake, AI Diagram Studio, Video Studio, Research Agent, New Research Topic, Skills Manager, OpenAPI Routing, Manim Sandbox, Settings.","Repurpose here means mining for specific modules, algorithms, UI patterns, ingestion logic, workflow ideas, or export formats rather than assuming a full product transplant.",manimcommunity/manim,remotion-dev/remotion,native/ScriptoriumAI-Visualizer,"Return concrete files/modules/adapters worth reusing and a verdict on whether the current reanchored bucket should be kept, upgraded, or downgraded.",Do not treat licensing as a filter. Do not propose replacing native foundations unless source evidence is overwhelming.,openmoss/mova,v6_unified_source_of_truth_pack,"Before recommending direct code use, inspect the target repo row in the v6.1 operational/phase/source-audit boards. Respect copyleft_strategy_v6_1, preferred_boundary_model_v6_1, and open_compliance_if_used_as_is_v6_1. Do not assume reverse engineering is mandatory or that as-is use is always sensible.","If the repo-level strategy says bounded_sidecar_preferred or boundary_first_then_decide_as_is_vs_reimplementation, audit clean interfaces, protocol seams, subprocess/container boundaries, and what would be required to reimplement only the strategically necessary portions.",v6.3_final_source_of_truth
SCR_0138,,,,,,,,,,ScriptoriumAI repo packet,ScriptoriumAI,ScriptoriumAI re-anchored VS Code packets v1,PDFCraftTool/pdfcraft,pdfcrafttool/pdfcraft,Candidate Bench,P3,bookmark candidate only,"Audit PDFCraftTool/pdfcraft for ScriptoriumAI. Start from the reanchored bucket 'Candidate Bench' and current reality status 'bookmark candidate only'. Confirm actual implemented capability, hidden reusable modules, extension seams, and whether it strengthens the existing Unimplemented but relevant candidate lane. Focus on: Inspect document/block schema; sync/persistence model; permissions and sharing; citation/external-source pipeline; import/export adapters; plugin/extension points; editor rendering model.","Inspect package manifests, README/docs, src tree, examples, tests, CI workflows, config files, migrations/schemas, and hidden feature flags or experimental modules. Look for document/block schema, sync/conflict logic, citation handling, editor plugins, export/render pipeline, prompt chains, report assembly, and collaborative presence code.","Treat as unimplemented ScriptoriumAI candidate only. Do not let it redefine the current stack. Integrate only if a later audit proves it fills a real gap in the existing surfaces such as Dashboard, Editor, Corpus Graph, Runboard, AI Kanban, Corpus Search, Patch Review Queue, Visualizations, Whiteboard, Mind Map, PDF Intake, AI Diagram Studio, Video Studio, Research Agent, New Research Topic, Skills Manager, OpenAPI Routing, Manim Sandbox, Settings.","Repurpose here means mining for specific modules, algorithms, UI patterns, ingestion logic, workflow ideas, or export formats rather than assuming a full product transplant.",pdfmd/pdfmd,lukas-blecher/latex-ocr,mli55/pdfdelta,"Return concrete files/modules/adapters worth reusing and a verdict on whether the current reanchored bucket should be kept, upgraded, or downgraded.",Do not treat licensing as a filter. Do not propose replacing native foundations unless source evidence is overwhelming.,pdfcrafttool/pdfcraft,v6_unified_source_of_truth_pack,"Before recommending direct code use, inspect the target repo row in the v6.1 operational/phase/source-audit boards. Respect copyleft_strategy_v6_1, preferred_boundary_model_v6_1, and open_compliance_if_used_as_is_v6_1. Do not assume reverse engineering is mandatory or that as-is use is always sensible.","If the repo-level strategy says bounded_sidecar_preferred or boundary_first_then_decide_as_is_vs_reimplementation, audit clean interfaces, protocol seams, subprocess/container boundaries, and what would be required to reimplement only the strategically necessary portions.",v6.3_final_source_of_truth
SCR_0139,,,,,,,,,,ScriptoriumAI repo packet,ScriptoriumAI,ScriptoriumAI re-anchored VS Code packets v1,PDFMathTranslate/PDFMathTranslate,pdfmathtranslate/pdfmathtranslate,Candidate Bench,P3,bookmark candidate only,"Audit PDFMathTranslate/PDFMathTranslate for ScriptoriumAI. Start from the reanchored bucket 'Candidate Bench' and current reality status 'bookmark candidate only'. Confirm actual implemented capability, hidden reusable modules, extension seams, and whether it strengthens the existing Unimplemented but relevant candidate lane. Focus on: 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.","Treat as unimplemented ScriptoriumAI candidate only. Do not let it redefine the current stack. Integrate only if a later audit proves it fills a real gap in the existing surfaces such as Dashboard, Editor, Corpus Graph, Runboard, AI Kanban, Corpus Search, Patch Review Queue, Visualizations, Whiteboard, Mind Map, PDF Intake, AI Diagram Studio, Video Studio, Research Agent, New Research Topic, Skills Manager, OpenAPI Routing, Manim Sandbox, Settings.","Repurpose here means mining for specific modules, algorithms, UI patterns, ingestion logic, workflow ideas, or export formats rather than assuming a full product transplant.",pdfmd/pdfmd,lukas-blecher/latex-ocr,mli55/pdfdelta,"Return concrete files/modules/adapters worth reusing and a verdict on whether the current reanchored bucket should be kept, upgraded, or downgraded.",Do not treat licensing as a filter. Do not propose replacing native foundations unless source evidence is overwhelming.,pdfmathtranslate/pdfmathtranslate,v6_unified_source_of_truth_pack,"Before recommending direct code use, inspect the target repo row in the v6.1 operational/phase/source-audit boards. Respect copyleft_strategy_v6_1, preferred_boundary_model_v6_1, and open_compliance_if_used_as_is_v6_1. Do not assume reverse engineering is mandatory or that as-is use is always sensible.","If the repo-level strategy says bounded_sidecar_preferred or boundary_first_then_decide_as_is_vs_reimplementation, audit clean interfaces, protocol seams, subprocess/container boundaries, and what would be required to reimplement only the strategically necessary portions.",v6.3_final_source_of_truth
SCR_0140,,,,,,,,,,ScriptoriumAI repo packet,ScriptoriumAI,ScriptoriumAI re-anchored VS Code packets v1,PaddlePaddle/PaddleOCR,paddlepaddle/paddleocr,Candidate Bench,P3,bookmark candidate only,"Audit PaddlePaddle/PaddleOCR for ScriptoriumAI. Start from the reanchored bucket 'Candidate Bench' and current reality status 'bookmark candidate only'. Confirm actual implemented capability, hidden reusable modules, extension seams, and whether it strengthens the existing Unimplemented but relevant candidate lane. Focus on: 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.","Treat as unimplemented ScriptoriumAI candidate only. Do not let it redefine the current stack. Integrate only if a later audit proves it fills a real gap in the existing surfaces such as Dashboard, Editor, Corpus Graph, Runboard, AI Kanban, Corpus Search, Patch Review Queue, Visualizations, Whiteboard, Mind Map, PDF Intake, AI Diagram Studio, Video Studio, Research Agent, New Research Topic, Skills Manager, OpenAPI Routing, Manim Sandbox, Settings.","Repurpose here means mining for specific modules, algorithms, UI patterns, ingestion logic, workflow ideas, or export formats rather than assuming a full product transplant.",pdfmd/pdfmd,lukas-blecher/latex-ocr,mli55/pdfdelta,"Return concrete files/modules/adapters worth reusing and a verdict on whether the current reanchored bucket should be kept, upgraded, or downgraded.",Do not treat licensing as a filter. Do not propose replacing native foundations unless source evidence is overwhelming.,paddlepaddle/paddleocr,v6_unified_source_of_truth_pack,"Before recommending direct code use, inspect the target repo row in the v6.1 operational/phase/source-audit boards. Respect copyleft_strategy_v6_1, preferred_boundary_model_v6_1, and open_compliance_if_used_as_is_v6_1. Do not assume reverse engineering is mandatory or that as-is use is always sensible.","If the repo-level strategy says bounded_sidecar_preferred or boundary_first_then_decide_as_is_vs_reimplementation, audit clean interfaces, protocol seams, subprocess/container boundaries, and what would be required to reimplement only the strategically necessary portions.",v6.3_final_source_of_truth
SCR_0141,,,,,,,,,,ScriptoriumAI repo packet,ScriptoriumAI,ScriptoriumAI re-anchored VS Code packets v1,Prismer-AI/Prismer,prismer-ai/prismer,Candidate Bench,P3,bookmark candidate only,"Audit Prismer-AI/Prismer for ScriptoriumAI. Start from the reanchored bucket 'Candidate Bench' and current reality status 'bookmark candidate only'. Confirm actual implemented capability, hidden reusable modules, extension seams, and whether it strengthens the existing Unimplemented but relevant candidate lane. Focus on: Inspect document/block schema; sync/persistence model; permissions and sharing; citation/external-source pipeline; import/export adapters; plugin/extension points; editor rendering model.","Inspect package manifests, README/docs, src tree, examples, tests, CI workflows, config files, migrations/schemas, and hidden feature flags or experimental modules. Look for document/block schema, sync/conflict logic, citation handling, editor plugins, export/render pipeline, prompt chains, report assembly, and collaborative presence code.","Treat as unimplemented ScriptoriumAI candidate only. Do not let it redefine the current stack. Integrate only if a later audit proves it fills a real gap in the existing surfaces such as Dashboard, Editor, Corpus Graph, Runboard, AI Kanban, Corpus Search, Patch Review Queue, Visualizations, Whiteboard, Mind Map, PDF Intake, AI Diagram Studio, Video Studio, Research Agent, New Research Topic, Skills Manager, OpenAPI Routing, Manim Sandbox, Settings.","Repurpose here means mining for specific modules, algorithms, UI patterns, ingestion logic, workflow ideas, or export formats rather than assuming a full product transplant.",native/ScriptoriumAI-Server,stanford-oval/storm,abhigyanpatwari/GitNexus,"Return concrete files/modules/adapters worth reusing and a verdict on whether the current reanchored bucket should be kept, upgraded, or downgraded.",Do not treat licensing as a filter. Do not propose replacing native foundations unless source evidence is overwhelming.,prismer-ai/prismer,v6_unified_source_of_truth_pack,"Before recommending direct code use, inspect the target repo row in the v6.1 operational/phase/source-audit boards. Respect copyleft_strategy_v6_1, preferred_boundary_model_v6_1, and open_compliance_if_used_as_is_v6_1. Do not assume reverse engineering is mandatory or that as-is use is always sensible.","If the repo-level strategy says bounded_sidecar_preferred or boundary_first_then_decide_as_is_vs_reimplementation, audit clean interfaces, protocol seams, subprocess/container boundaries, and what would be required to reimplement only the strategically necessary portions.",v6.3_final_source_of_truth
SCR_0142,,,,,,,,,,ScriptoriumAI repo packet,ScriptoriumAI,ScriptoriumAI re-anchored VS Code packets v1,ResearAI/AutoFigure-Edit,researai/autofigure-edit,Candidate Bench,P3,bookmark candidate only,"Audit ResearAI/AutoFigure-Edit for ScriptoriumAI. Start from the reanchored bucket 'Candidate Bench' and current reality status 'bookmark candidate only'. Confirm actual implemented capability, hidden reusable modules, extension seams, and whether it strengthens the existing Unimplemented but relevant candidate lane. Focus on: Inspect planner/task graph; provider abstraction; tool registry or MCP bridges; memory/state schema; approvals/retries; telemetry/event bus; plugin or skill loading 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 document/block schema, sync/conflict logic, citation handling, editor plugins, export/render pipeline, prompt chains, report assembly, and collaborative presence code.","Treat as unimplemented ScriptoriumAI candidate only. Do not let it redefine the current stack. Integrate only if a later audit proves it fills a real gap in the existing surfaces such as Dashboard, Editor, Corpus Graph, Runboard, AI Kanban, Corpus Search, Patch Review Queue, Visualizations, Whiteboard, Mind Map, PDF Intake, AI Diagram Studio, Video Studio, Research Agent, New Research Topic, Skills Manager, OpenAPI Routing, Manim Sandbox, Settings.","Repurpose here means mining for specific modules, algorithms, UI patterns, ingestion logic, workflow ideas, or export formats rather than assuming a full product transplant.",pdfmd/pdfmd,lukas-blecher/latex-ocr,mli55/pdfdelta,"Return concrete files/modules/adapters worth reusing and a verdict on whether the current reanchored bucket should be kept, upgraded, or downgraded.",Do not treat licensing as a filter. Do not propose replacing native foundations unless source evidence is overwhelming.,researai/autofigure-edit,v6_unified_source_of_truth_pack,"Before recommending direct code use, inspect the target repo row in the v6.1 operational/phase/source-audit boards. Respect copyleft_strategy_v6_1, preferred_boundary_model_v6_1, and open_compliance_if_used_as_is_v6_1. Do not assume reverse engineering is mandatory or that as-is use is always sensible.","If the repo-level strategy says bounded_sidecar_preferred or boundary_first_then_decide_as_is_vs_reimplementation, audit clean interfaces, protocol seams, subprocess/container boundaries, and what would be required to reimplement only the strategically necessary portions.",v6.3_final_source_of_truth
SCR_0143,,,,,,,,,,ScriptoriumAI repo packet,ScriptoriumAI,ScriptoriumAI re-anchored VS Code packets v1,RocketChat/Rocket.Chat,rocketchat/rocket.chat,Candidate Bench,P3,not in implemented architecture snapshot,"Audit RocketChat/Rocket.Chat for ScriptoriumAI. Start from the reanchored bucket 'Candidate Bench' and current reality status 'not in implemented architecture snapshot'. Confirm actual implemented capability, hidden reusable modules, extension seams, and whether it strengthens the existing Potential collaboration/comms donor lane. Focus on: 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 realtime protocols, presence, room/thread models, moderation/RBAC, attachments/embeds, notifications, and offline conflict handling.","Treat as unimplemented ScriptoriumAI candidate only. Do not let it redefine the current stack. Integrate only if a later audit proves it fills a real gap in the existing surfaces such as Dashboard, Editor, Corpus Graph, Runboard, AI Kanban, Corpus Search, Patch Review Queue, Visualizations, Whiteboard, Mind Map, PDF Intake, AI Diagram Studio, Video Studio, Research Agent, New Research Topic, Skills Manager, OpenAPI Routing, Manim Sandbox, Settings.","Repurpose here means mining for specific modules, algorithms, UI patterns, ingestion logic, workflow ideas, or export formats rather than assuming a full product transplant.",native/scriptoriumai-ui,native/ScriptoriumAI-Server,abhigyanpatwari/GitNexus,"Return concrete files/modules/adapters worth reusing and a verdict on whether the current reanchored bucket should be kept, upgraded, or downgraded.",Do not treat licensing as a filter. Do not propose replacing native foundations unless source evidence is overwhelming.,rocketchat/rocket.chat,v6_unified_source_of_truth_pack,"Before recommending direct code use, inspect the target repo row in the v6.1 operational/phase/source-audit boards. Respect copyleft_strategy_v6_1, preferred_boundary_model_v6_1, and open_compliance_if_used_as_is_v6_1. Do not assume reverse engineering is mandatory or that as-is use is always sensible.","If the repo-level strategy says bounded_sidecar_preferred or boundary_first_then_decide_as_is_vs_reimplementation, audit clean interfaces, protocol seams, subprocess/container boundaries, and what would be required to reimplement only the strategically necessary portions.",v6.3_final_source_of_truth
SCR_0144,,,,,,,,,,ScriptoriumAI repo packet,ScriptoriumAI,ScriptoriumAI re-anchored VS Code packets v1,RuizeLyu/paper-dl,ruizelyu/paper-dl,Candidate Bench,P3,bookmark candidate only,"Audit RuizeLyu/paper-dl for ScriptoriumAI. Start from the reanchored bucket 'Candidate Bench' and current reality status 'bookmark candidate only'. Confirm actual implemented capability, hidden reusable modules, extension seams, and whether it strengthens the existing Unimplemented but relevant candidate lane. Focus on: Inspect document/block schema; sync/persistence model; permissions and sharing; citation/external-source pipeline; import/export adapters; plugin/extension points; editor rendering model.","Inspect package manifests, README/docs, src tree, examples, tests, CI workflows, config files, migrations/schemas, and hidden feature flags or experimental modules. Look for document/block schema, sync/conflict logic, citation handling, editor plugins, export/render pipeline, prompt chains, report assembly, and collaborative presence code.","Treat as unimplemented ScriptoriumAI candidate only. Do not let it redefine the current stack. Integrate only if a later audit proves it fills a real gap in the existing surfaces such as Dashboard, Editor, Corpus Graph, Runboard, AI Kanban, Corpus Search, Patch Review Queue, Visualizations, Whiteboard, Mind Map, PDF Intake, AI Diagram Studio, Video Studio, Research Agent, New Research Topic, Skills Manager, OpenAPI Routing, Manim Sandbox, Settings.","Repurpose here means mining for specific modules, algorithms, UI patterns, ingestion logic, workflow ideas, or export formats rather than assuming a full product transplant.",pdfmd/pdfmd,lukas-blecher/latex-ocr,mli55/pdfdelta,"Return concrete files/modules/adapters worth reusing and a verdict on whether the current reanchored bucket should be kept, upgraded, or downgraded.",Do not treat licensing as a filter. Do not propose replacing native foundations unless source evidence is overwhelming.,ruizelyu/paper-dl,v6_unified_source_of_truth_pack,"Before recommending direct code use, inspect the target repo row in the v6.1 operational/phase/source-audit boards. Respect copyleft_strategy_v6_1, preferred_boundary_model_v6_1, and open_compliance_if_used_as_is_v6_1. Do not assume reverse engineering is mandatory or that as-is use is always sensible.","If the repo-level strategy says bounded_sidecar_preferred or boundary_first_then_decide_as_is_vs_reimplementation, audit clean interfaces, protocol seams, subprocess/container boundaries, and what would be required to reimplement only the strategically necessary portions.",v6.3_final_source_of_truth
SCR_0145,,,,,,,,,,ScriptoriumAI repo packet,ScriptoriumAI,ScriptoriumAI re-anchored VS Code packets v1,Snapchat/Valdi,snapchat/valdi,Candidate Bench,P3,bookmark candidate only,"Audit Snapchat/Valdi for ScriptoriumAI. Start from the reanchored bucket 'Candidate Bench' and current reality status 'bookmark candidate only'. Confirm actual implemented capability, hidden reusable modules, extension seams, and whether it strengthens the existing Unimplemented but relevant candidate lane. Focus on: 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 realtime protocols, presence, room/thread models, moderation/RBAC, attachments/embeds, notifications, and offline conflict handling.","Treat as unimplemented ScriptoriumAI candidate only. Do not let it redefine the current stack. Integrate only if a later audit proves it fills a real gap in the existing surfaces such as Dashboard, Editor, Corpus Graph, Runboard, AI Kanban, Corpus Search, Patch Review Queue, Visualizations, Whiteboard, Mind Map, PDF Intake, AI Diagram Studio, Video Studio, Research Agent, New Research Topic, Skills Manager, OpenAPI Routing, Manim Sandbox, Settings.","Repurpose here means mining for specific modules, algorithms, UI patterns, ingestion logic, workflow ideas, or export formats rather than assuming a full product transplant.",native/scriptoriumai-ui,native/ScriptoriumAI-Server,abhigyanpatwari/GitNexus,"Return concrete files/modules/adapters worth reusing and a verdict on whether the current reanchored bucket should be kept, upgraded, or downgraded.",Do not treat licensing as a filter. Do not propose replacing native foundations unless source evidence is overwhelming.,snapchat/valdi,v6_unified_source_of_truth_pack,"Before recommending direct code use, inspect the target repo row in the v6.1 operational/phase/source-audit boards. Respect copyleft_strategy_v6_1, preferred_boundary_model_v6_1, and open_compliance_if_used_as_is_v6_1. Do not assume reverse engineering is mandatory or that as-is use is always sensible.","If the repo-level strategy says bounded_sidecar_preferred or boundary_first_then_decide_as_is_vs_reimplementation, audit clean interfaces, protocol seams, subprocess/container boundaries, and what would be required to reimplement only the strategically necessary portions.",v6.3_final_source_of_truth
SCR_0146,,,,,,,,,,ScriptoriumAI repo packet,ScriptoriumAI,ScriptoriumAI re-anchored VS Code packets v1,SylvianAI/sv-excel-agent,sylvianai/sv-excel-agent,Candidate Bench,P3,bookmark candidate only,"Audit SylvianAI/sv-excel-agent for ScriptoriumAI. Start from the reanchored bucket 'Candidate Bench' and current reality status 'bookmark candidate only'. Confirm actual implemented capability, hidden reusable modules, extension seams, and whether it strengthens the existing Unimplemented but relevant candidate lane. Focus on: Inspect planner/task graph; provider abstraction; tool registry or MCP bridges; memory/state schema; approvals/retries; telemetry/event bus; plugin or skill loading 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 planner loops, tool registries, MCP servers/clients, prompt/skill folders, memory stores, approval gates, background-job orchestration, and undocumented provider adapters.","Treat as unimplemented ScriptoriumAI candidate only. Do not let it redefine the current stack. Integrate only if a later audit proves it fills a real gap in the existing surfaces such as Dashboard, Editor, Corpus Graph, Runboard, AI Kanban, Corpus Search, Patch Review Queue, Visualizations, Whiteboard, Mind Map, PDF Intake, AI Diagram Studio, Video Studio, Research Agent, New Research Topic, Skills Manager, OpenAPI Routing, Manim Sandbox, Settings.","Repurpose here means mining for specific modules, algorithms, UI patterns, ingestion logic, workflow ideas, or export formats rather than assuming a full product transplant.",native/ScriptoriumAI-Server,stanford-oval/storm,abhigyanpatwari/GitNexus,"Return concrete files/modules/adapters worth reusing and a verdict on whether the current reanchored bucket should be kept, upgraded, or downgraded.",Do not treat licensing as a filter. Do not propose replacing native foundations unless source evidence is overwhelming.,sylvianai/sv-excel-agent,v6_unified_source_of_truth_pack,"Before recommending direct code use, inspect the target repo row in the v6.1 operational/phase/source-audit boards. Respect copyleft_strategy_v6_1, preferred_boundary_model_v6_1, and open_compliance_if_used_as_is_v6_1. Do not assume reverse engineering is mandatory or that as-is use is always sensible.","If the repo-level strategy says bounded_sidecar_preferred or boundary_first_then_decide_as_is_vs_reimplementation, audit clean interfaces, protocol seams, subprocess/container boundaries, and what would be required to reimplement only the strategically necessary portions.",v6.3_final_source_of_truth
SCR_0147,,,,,,,,,,ScriptoriumAI repo packet,ScriptoriumAI,ScriptoriumAI re-anchored VS Code packets v1,TapXWorld/ChinaTextbook,tapxworld/chinatextbook,Candidate Bench,P3,bookmark candidate only,"Audit TapXWorld/ChinaTextbook for ScriptoriumAI. Start from the reanchored bucket 'Candidate Bench' and current reality status 'bookmark candidate only'. Confirm actual implemented capability, hidden reusable modules, extension seams, and whether it strengthens the existing Unimplemented but relevant candidate lane. Focus on: Inspect document/block schema; sync/persistence model; permissions and sharing; citation/external-source pipeline; import/export adapters; plugin/extension points; editor rendering model.","Inspect package manifests, README/docs, src tree, examples, tests, CI workflows, config files, migrations/schemas, and hidden feature flags or experimental modules. Look for document/block schema, sync/conflict logic, citation handling, editor plugins, export/render pipeline, prompt chains, report assembly, and collaborative presence code.","Treat as unimplemented ScriptoriumAI candidate only. Do not let it redefine the current stack. Integrate only if a later audit proves it fills a real gap in the existing surfaces such as Dashboard, Editor, Corpus Graph, Runboard, AI Kanban, Corpus Search, Patch Review Queue, Visualizations, Whiteboard, Mind Map, PDF Intake, AI Diagram Studio, Video Studio, Research Agent, New Research Topic, Skills Manager, OpenAPI Routing, Manim Sandbox, Settings.","Repurpose here means mining for specific modules, algorithms, UI patterns, ingestion logic, workflow ideas, or export formats rather than assuming a full product transplant.",pdfmd/pdfmd,lukas-blecher/latex-ocr,mli55/pdfdelta,"Return concrete files/modules/adapters worth reusing and a verdict on whether the current reanchored bucket should be kept, upgraded, or downgraded.",Do not treat licensing as a filter. Do not propose replacing native foundations unless source evidence is overwhelming.,tapxworld/chinatextbook,v6_unified_source_of_truth_pack,"Before recommending direct code use, inspect the target repo row in the v6.1 operational/phase/source-audit boards. Respect copyleft_strategy_v6_1, preferred_boundary_model_v6_1, and open_compliance_if_used_as_is_v6_1. Do not assume reverse engineering is mandatory or that as-is use is always sensible.","If the repo-level strategy says bounded_sidecar_preferred or boundary_first_then_decide_as_is_vs_reimplementation, audit clean interfaces, protocol seams, subprocess/container boundaries, and what would be required to reimplement only the strategically necessary portions.",v6.3_final_source_of_truth
SCR_0148,,,,,,,,,,ScriptoriumAI repo packet,ScriptoriumAI,ScriptoriumAI re-anchored VS Code packets v1,Tencent/WeKnora,tencent/weknora,Candidate Bench,P3,bookmark candidate only,"Audit Tencent/WeKnora for ScriptoriumAI. Start from the reanchored bucket 'Candidate Bench' and current reality status 'bookmark candidate only'. Confirm actual implemented capability, hidden reusable modules, extension seams, and whether it strengthens the existing Unimplemented but relevant candidate lane. Focus on: Inspect planner/task graph; provider abstraction; tool registry or MCP bridges; memory/state schema; approvals/retries; telemetry/event bus; plugin or skill loading 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 planner loops, tool registries, MCP servers/clients, prompt/skill folders, memory stores, approval gates, background-job orchestration, and undocumented provider adapters.","Treat as unimplemented ScriptoriumAI candidate only. Do not let it redefine the current stack. Integrate only if a later audit proves it fills a real gap in the existing surfaces such as Dashboard, Editor, Corpus Graph, Runboard, AI Kanban, Corpus Search, Patch Review Queue, Visualizations, Whiteboard, Mind Map, PDF Intake, AI Diagram Studio, Video Studio, Research Agent, New Research Topic, Skills Manager, OpenAPI Routing, Manim Sandbox, Settings.","Repurpose here means mining for specific modules, algorithms, UI patterns, ingestion logic, workflow ideas, or export formats rather than assuming a full product transplant.",native/scriptoriumai-ui,native/ScriptoriumAI-Server,abhigyanpatwari/GitNexus,"Return concrete files/modules/adapters worth reusing and a verdict on whether the current reanchored bucket should be kept, upgraded, or downgraded.",Do not treat licensing as a filter. Do not propose replacing native foundations unless source evidence is overwhelming.,tencent/weknora,v6_unified_source_of_truth_pack,"Before recommending direct code use, inspect the target repo row in the v6.1 operational/phase/source-audit boards. Respect copyleft_strategy_v6_1, preferred_boundary_model_v6_1, and open_compliance_if_used_as_is_v6_1. Do not assume reverse engineering is mandatory or that as-is use is always sensible.","If the repo-level strategy says bounded_sidecar_preferred or boundary_first_then_decide_as_is_vs_reimplementation, audit clean interfaces, protocol seams, subprocess/container boundaries, and what would be required to reimplement only the strategically necessary portions.",v6.3_final_source_of_truth
SCR_0149,,,,,,,,,,ScriptoriumAI repo packet,ScriptoriumAI,ScriptoriumAI re-anchored VS Code packets v1,VideoZero/skills,videozero/skills,Candidate Bench,P3,bookmark candidate only,"Audit VideoZero/skills for ScriptoriumAI. Start from the reanchored bucket 'Candidate Bench' and current reality status 'bookmark candidate only'. Confirm actual implemented capability, hidden reusable modules, extension seams, and whether it strengthens the existing Unimplemented but relevant candidate lane. Focus on: 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.","Treat as unimplemented ScriptoriumAI candidate only. Do not let it redefine the current stack. Integrate only if a later audit proves it fills a real gap in the existing surfaces such as Dashboard, Editor, Corpus Graph, Runboard, AI Kanban, Corpus Search, Patch Review Queue, Visualizations, Whiteboard, Mind Map, PDF Intake, AI Diagram Studio, Video Studio, Research Agent, New Research Topic, Skills Manager, OpenAPI Routing, Manim Sandbox, Settings.","Repurpose here means mining for specific modules, algorithms, UI patterns, ingestion logic, workflow ideas, or export formats rather than assuming a full product transplant.",native/ScriptoriumAI-Server,stanford-oval/storm,abhigyanpatwari/GitNexus,"Return concrete files/modules/adapters worth reusing and a verdict on whether the current reanchored bucket should be kept, upgraded, or downgraded.",Do not treat licensing as a filter. Do not propose replacing native foundations unless source evidence is overwhelming.,videozero/skills,v6_unified_source_of_truth_pack,"Before recommending direct code use, inspect the target repo row in the v6.1 operational/phase/source-audit boards. Respect copyleft_strategy_v6_1, preferred_boundary_model_v6_1, and open_compliance_if_used_as_is_v6_1. Do not assume reverse engineering is mandatory or that as-is use is always sensible.","If the repo-level strategy says bounded_sidecar_preferred or boundary_first_then_decide_as_is_vs_reimplementation, audit clean interfaces, protocol seams, subprocess/container boundaries, and what would be required to reimplement only the strategically necessary portions.",v6.3_final_source_of_truth
SCR_0150,,,,,,,,,,ScriptoriumAI repo packet,ScriptoriumAI,ScriptoriumAI re-anchored VS Code packets v1,YouMind-OpenLab/awesome-nano-banana-pro-prompts,youmind-openlab/awesome-nano-banana-pro-prompts,Candidate Bench,P3,bookmark candidate only,"Audit YouMind-OpenLab/awesome-nano-banana-pro-prompts for ScriptoriumAI. Start from the reanchored bucket 'Candidate Bench' and current reality status 'bookmark candidate only'. Confirm actual implemented capability, hidden reusable modules, extension seams, and whether it strengthens the existing Unimplemented but relevant candidate lane. Focus on: 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.","Treat as unimplemented ScriptoriumAI candidate only. Do not let it redefine the current stack. Integrate only if a later audit proves it fills a real gap in the existing surfaces such as Dashboard, Editor, Corpus Graph, Runboard, AI Kanban, Corpus Search, Patch Review Queue, Visualizations, Whiteboard, Mind Map, PDF Intake, AI Diagram Studio, Video Studio, Research Agent, New Research Topic, Skills Manager, OpenAPI Routing, Manim Sandbox, Settings.","Repurpose here means mining for specific modules, algorithms, UI patterns, ingestion logic, workflow ideas, or export formats rather than assuming a full product transplant.",native/scriptoriumai-ui,native/ScriptoriumAI-Server,abhigyanpatwari/GitNexus,"Return concrete files/modules/adapters worth reusing and a verdict on whether the current reanchored bucket should be kept, upgraded, or downgraded.",Do not treat licensing as a filter. Do not propose replacing native foundations unless source evidence is overwhelming.,youmind-openlab/awesome-nano-banana-pro-prompts,v6_unified_source_of_truth_pack,"Before recommending direct code use, inspect the target repo row in the v6.1 operational/phase/source-audit boards. Respect copyleft_strategy_v6_1, preferred_boundary_model_v6_1, and open_compliance_if_used_as_is_v6_1. Do not assume reverse engineering is mandatory or that as-is use is always sensible.","If the repo-level strategy says bounded_sidecar_preferred or boundary_first_then_decide_as_is_vs_reimplementation, audit clean interfaces, protocol seams, subprocess/container boundaries, and what would be required to reimplement only the strategically necessary portions.",v6.3_final_source_of_truth
SCR_0151,,,,,,,,,,ScriptoriumAI repo packet,ScriptoriumAI,ScriptoriumAI re-anchored VS Code packets v1,YuhangChen1/Paper2All,yuhangchen1/paper2all,Candidate Bench,P3,bookmark candidate only,"Audit YuhangChen1/Paper2All for ScriptoriumAI. Start from the reanchored bucket 'Candidate Bench' and current reality status 'bookmark candidate only'. Confirm actual implemented capability, hidden reusable modules, extension seams, and whether it strengthens the existing Unimplemented but relevant candidate lane. Focus on: Inspect document/block schema; sync/persistence model; permissions and sharing; citation/external-source pipeline; import/export adapters; plugin/extension points; editor rendering model.","Inspect package manifests, README/docs, src tree, examples, tests, CI workflows, config files, migrations/schemas, and hidden feature flags or experimental modules. Look for document/block schema, sync/conflict logic, citation handling, editor plugins, export/render pipeline, prompt chains, report assembly, and collaborative presence code.","Treat as unimplemented ScriptoriumAI candidate only. Do not let it redefine the current stack. Integrate only if a later audit proves it fills a real gap in the existing surfaces such as Dashboard, Editor, Corpus Graph, Runboard, AI Kanban, Corpus Search, Patch Review Queue, Visualizations, Whiteboard, Mind Map, PDF Intake, AI Diagram Studio, Video Studio, Research Agent, New Research Topic, Skills Manager, OpenAPI Routing, Manim Sandbox, Settings.","Repurpose here means mining for specific modules, algorithms, UI patterns, ingestion logic, workflow ideas, or export formats rather than assuming a full product transplant.",pdfmd/pdfmd,lukas-blecher/latex-ocr,mli55/pdfdelta,"Return concrete files/modules/adapters worth reusing and a verdict on whether the current reanchored bucket should be kept, upgraded, or downgraded.",Do not treat licensing as a filter. Do not propose replacing native foundations unless source evidence is overwhelming.,yuhangchen1/paper2all,v6_unified_source_of_truth_pack,"Before recommending direct code use, inspect the target repo row in the v6.1 operational/phase/source-audit boards. Respect copyleft_strategy_v6_1, preferred_boundary_model_v6_1, and open_compliance_if_used_as_is_v6_1. Do not assume reverse engineering is mandatory or that as-is use is always sensible.","If the repo-level strategy says bounded_sidecar_preferred or boundary_first_then_decide_as_is_vs_reimplementation, audit clean interfaces, protocol seams, subprocess/container boundaries, and what would be required to reimplement only the strategically necessary portions.",v6.3_final_source_of_truth
SCR_0152,,,,,,,,,,ScriptoriumAI repo packet,ScriptoriumAI,ScriptoriumAI re-anchored VS Code packets v1,ZimengXiong/ExcaliDash,zimengxiong/excalidash,Candidate Bench,P3,bookmark candidate only,"Audit ZimengXiong/ExcaliDash for ScriptoriumAI. Start from the reanchored bucket 'Candidate Bench' and current reality status 'bookmark candidate only'. Confirm actual implemented capability, hidden reusable modules, extension seams, and whether it strengthens the existing Unimplemented but relevant candidate lane. Focus on: 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.","Treat as unimplemented ScriptoriumAI candidate only. Do not let it redefine the current stack. Integrate only if a later audit proves it fills a real gap in the existing surfaces such as Dashboard, Editor, Corpus Graph, Runboard, AI Kanban, Corpus Search, Patch Review Queue, Visualizations, Whiteboard, Mind Map, PDF Intake, AI Diagram Studio, Video Studio, Research Agent, New Research Topic, Skills Manager, OpenAPI Routing, Manim Sandbox, Settings.","Repurpose here means mining for specific modules, algorithms, UI patterns, ingestion logic, workflow ideas, or export formats rather than assuming a full product transplant.",native/scriptoriumai-ui,excalidraw/excalidraw,jgraph/drawio,"Return concrete files/modules/adapters worth reusing and a verdict on whether the current reanchored bucket should be kept, upgraded, or downgraded.",Do not treat licensing as a filter. Do not propose replacing native foundations unless source evidence is overwhelming.,zimengxiong/excalidash,v6_unified_source_of_truth_pack,"Before recommending direct code use, inspect the target repo row in the v6.1 operational/phase/source-audit boards. Respect copyleft_strategy_v6_1, preferred_boundary_model_v6_1, and open_compliance_if_used_as_is_v6_1. Do not assume reverse engineering is mandatory or that as-is use is always sensible.","If the repo-level strategy says bounded_sidecar_preferred or boundary_first_then_decide_as_is_vs_reimplementation, audit clean interfaces, protocol seams, subprocess/container boundaries, and what would be required to reimplement only the strategically necessary portions.",v6.3_final_source_of_truth
SCR_0153,,,,,,,,,,ScriptoriumAI repo packet,ScriptoriumAI,ScriptoriumAI re-anchored VS Code packets v1,aaditya-prog/manimdsa,aaditya-prog/manimdsa,Candidate Bench,P3,bookmark candidate only,"Audit aaditya-prog/manimdsa for ScriptoriumAI. Start from the reanchored bucket 'Candidate Bench' and current reality status 'bookmark candidate only'. Confirm actual implemented capability, hidden reusable modules, extension seams, and whether it strengthens the existing Unimplemented but relevant candidate lane. Focus on: Inspect hidden modules, extension seams, data contracts, rendering paths, auth/storage coupling, and export/import boundaries.",,"Treat as unimplemented ScriptoriumAI candidate only. Do not let it redefine the current stack. Integrate only if a later audit proves it fills a real gap in the existing surfaces such as Dashboard, Editor, Corpus Graph, Runboard, AI Kanban, Corpus Search, Patch Review Queue, Visualizations, Whiteboard, Mind Map, PDF Intake, AI Diagram Studio, Video Studio, Research Agent, New Research Topic, Skills Manager, OpenAPI Routing, Manim Sandbox, Settings.","Repurpose here means mining for specific modules, algorithms, UI patterns, ingestion logic, workflow ideas, or export formats rather than assuming a full product transplant.",manimcommunity/manim,remotion-dev/remotion,native/ScriptoriumAI-Visualizer,"Return concrete files/modules/adapters worth reusing and a verdict on whether the current reanchored bucket should be kept, upgraded, or downgraded.",Do not treat licensing as a filter. Do not propose replacing native foundations unless source evidence is overwhelming.,aaditya-prog/manimdsa,v6_unified_source_of_truth_pack,"Before recommending direct code use, inspect the target repo row in the v6.1 operational/phase/source-audit boards. Respect copyleft_strategy_v6_1, preferred_boundary_model_v6_1, and open_compliance_if_used_as_is_v6_1. Do not assume reverse engineering is mandatory or that as-is use is always sensible.","If the repo-level strategy says bounded_sidecar_preferred or boundary_first_then_decide_as_is_vs_reimplementation, audit clean interfaces, protocol seams, subprocess/container boundaries, and what would be required to reimplement only the strategically necessary portions.",v6.3_final_source_of_truth
SCR_0154,,,,,,,,,,ScriptoriumAI repo packet,ScriptoriumAI,ScriptoriumAI re-anchored VS Code packets v1,adithya-s-k/manim_skill,adithya-s-k/manim_skill,Candidate Bench,P3,bookmark candidate only,"Audit adithya-s-k/manim_skill for ScriptoriumAI. Start from the reanchored bucket 'Candidate Bench' and current reality status 'bookmark candidate only'. Confirm actual implemented capability, hidden reusable modules, extension seams, and whether it strengthens the existing Unimplemented but relevant candidate lane. Focus on: Inspect planner/task graph; provider abstraction; tool registry or MCP bridges; memory/state schema; approvals/retries; telemetry/event bus; plugin or skill loading 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 planner loops, tool registries, MCP servers/clients, prompt/skill folders, memory stores, approval gates, background-job orchestration, and undocumented provider adapters.","Treat as unimplemented ScriptoriumAI candidate only. Do not let it redefine the current stack. Integrate only if a later audit proves it fills a real gap in the existing surfaces such as Dashboard, Editor, Corpus Graph, Runboard, AI Kanban, Corpus Search, Patch Review Queue, Visualizations, Whiteboard, Mind Map, PDF Intake, AI Diagram Studio, Video Studio, Research Agent, New Research Topic, Skills Manager, OpenAPI Routing, Manim Sandbox, Settings.","Repurpose here means mining for specific modules, algorithms, UI patterns, ingestion logic, workflow ideas, or export formats rather than assuming a full product transplant.",native/ScriptoriumAI-Server,stanford-oval/storm,abhigyanpatwari/GitNexus,"Return concrete files/modules/adapters worth reusing and a verdict on whether the current reanchored bucket should be kept, upgraded, or downgraded.",Do not treat licensing as a filter. Do not propose replacing native foundations unless source evidence is overwhelming.,adithya-s-k/manim_skill,v6_unified_source_of_truth_pack,"Before recommending direct code use, inspect the target repo row in the v6.1 operational/phase/source-audit boards. Respect copyleft_strategy_v6_1, preferred_boundary_model_v6_1, and open_compliance_if_used_as_is_v6_1. Do not assume reverse engineering is mandatory or that as-is use is always sensible.","If the repo-level strategy says bounded_sidecar_preferred or boundary_first_then_decide_as_is_vs_reimplementation, audit clean interfaces, protocol seams, subprocess/container boundaries, and what would be required to reimplement only the strategically necessary portions.",v6.3_final_source_of_truth
SCR_0155,,,,,,,,,,ScriptoriumAI repo packet,ScriptoriumAI,ScriptoriumAI re-anchored VS Code packets v1,adubovskoy/dimandocs,adubovskoy/dimandocs,Candidate Bench,P3,bookmark candidate only,"Audit adubovskoy/dimandocs for ScriptoriumAI. Start from the reanchored bucket 'Candidate Bench' and current reality status 'bookmark candidate only'. Confirm actual implemented capability, hidden reusable modules, extension seams, and whether it strengthens the existing Unimplemented but relevant candidate lane. Focus on: Inspect document/block schema; sync/persistence model; permissions and sharing; citation/external-source pipeline; import/export adapters; plugin/extension points; editor rendering model.","Inspect package manifests, README/docs, src tree, examples, tests, CI workflows, config files, migrations/schemas, and hidden feature flags or experimental modules. Look for document/block schema, sync/conflict logic, citation handling, editor plugins, export/render pipeline, prompt chains, report assembly, and collaborative presence code.","Treat as unimplemented ScriptoriumAI candidate only. Do not let it redefine the current stack. Integrate only if a later audit proves it fills a real gap in the existing surfaces such as Dashboard, Editor, Corpus Graph, Runboard, AI Kanban, Corpus Search, Patch Review Queue, Visualizations, Whiteboard, Mind Map, PDF Intake, AI Diagram Studio, Video Studio, Research Agent, New Research Topic, Skills Manager, OpenAPI Routing, Manim Sandbox, Settings.","Repurpose here means mining for specific modules, algorithms, UI patterns, ingestion logic, workflow ideas, or export formats rather than assuming a full product transplant.",native/scriptoriumai-ui,native/ScriptoriumAI-Server,abhigyanpatwari/GitNexus,"Return concrete files/modules/adapters worth reusing and a verdict on whether the current reanchored bucket should be kept, upgraded, or downgraded.",Do not treat licensing as a filter. Do not propose replacing native foundations unless source evidence is overwhelming.,adubovskoy/dimandocs,v6_unified_source_of_truth_pack,"Before recommending direct code use, inspect the target repo row in the v6.1 operational/phase/source-audit boards. Respect copyleft_strategy_v6_1, preferred_boundary_model_v6_1, and open_compliance_if_used_as_is_v6_1. Do not assume reverse engineering is mandatory or that as-is use is always sensible.","If the repo-level strategy says bounded_sidecar_preferred or boundary_first_then_decide_as_is_vs_reimplementation, audit clean interfaces, protocol seams, subprocess/container boundaries, and what would be required to reimplement only the strategically necessary portions.",v6.3_final_source_of_truth
SCR_0156,,,,,,,,,,ScriptoriumAI repo packet,ScriptoriumAI,ScriptoriumAI re-anchored VS Code packets v1,agentscope-ai/ReMe,agentscope-ai/reme,Candidate Bench,P3,bookmark candidate only,"Audit agentscope-ai/ReMe for ScriptoriumAI. Start from the reanchored bucket 'Candidate Bench' and current reality status 'bookmark candidate only'. Confirm actual implemented capability, hidden reusable modules, extension seams, and whether it strengthens the existing Unimplemented but relevant candidate lane. Focus on: Inspect planner/task graph; provider abstraction; tool registry or MCP bridges; memory/state schema; approvals/retries; telemetry/event bus; plugin or skill loading 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 planner loops, tool registries, MCP servers/clients, prompt/skill folders, memory stores, approval gates, background-job orchestration, and undocumented provider adapters.","Treat as unimplemented ScriptoriumAI candidate only. Do not let it redefine the current stack. Integrate only if a later audit proves it fills a real gap in the existing surfaces such as Dashboard, Editor, Corpus Graph, Runboard, AI Kanban, Corpus Search, Patch Review Queue, Visualizations, Whiteboard, Mind Map, PDF Intake, AI Diagram Studio, Video Studio, Research Agent, New Research Topic, Skills Manager, OpenAPI Routing, Manim Sandbox, Settings.","Repurpose here means mining for specific modules, algorithms, UI patterns, ingestion logic, workflow ideas, or export formats rather than assuming a full product transplant.",native/ScriptoriumAI-Server,stanford-oval/storm,abhigyanpatwari/GitNexus,"Return concrete files/modules/adapters worth reusing and a verdict on whether the current reanchored bucket should be kept, upgraded, or downgraded.",Do not treat licensing as a filter. Do not propose replacing native foundations unless source evidence is overwhelming.,agentscope-ai/reme,v6_unified_source_of_truth_pack,"Before recommending direct code use, inspect the target repo row in the v6.1 operational/phase/source-audit boards. Respect copyleft_strategy_v6_1, preferred_boundary_model_v6_1, and open_compliance_if_used_as_is_v6_1. Do not assume reverse engineering is mandatory or that as-is use is always sensible.","If the repo-level strategy says bounded_sidecar_preferred or boundary_first_then_decide_as_is_vs_reimplementation, audit clean interfaces, protocol seams, subprocess/container boundaries, and what would be required to reimplement only the strategically necessary portions.",v6.3_final_source_of_truth
SCR_0157,,,,,,,,,,ScriptoriumAI repo packet,ScriptoriumAI,ScriptoriumAI re-anchored VS Code packets v1,ali-vilab/VACE,ali-vilab/vace,Candidate Bench,P3,bookmark candidate only,"Audit ali-vilab/VACE for ScriptoriumAI. Start from the reanchored bucket 'Candidate Bench' and current reality status 'bookmark candidate only'. Confirm actual implemented capability, hidden reusable modules, extension seams, and whether it strengthens the existing Unimplemented but relevant candidate lane. Focus on: 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.","Treat as unimplemented ScriptoriumAI candidate only. Do not let it redefine the current stack. Integrate only if a later audit proves it fills a real gap in the existing surfaces such as Dashboard, Editor, Corpus Graph, Runboard, AI Kanban, Corpus Search, Patch Review Queue, Visualizations, Whiteboard, Mind Map, PDF Intake, AI Diagram Studio, Video Studio, Research Agent, New Research Topic, Skills Manager, OpenAPI Routing, Manim Sandbox, Settings.","Repurpose here means mining for specific modules, algorithms, UI patterns, ingestion logic, workflow ideas, or export formats rather than assuming a full product transplant.",manimcommunity/manim,remotion-dev/remotion,native/ScriptoriumAI-Visualizer,"Return concrete files/modules/adapters worth reusing and a verdict on whether the current reanchored bucket should be kept, upgraded, or downgraded.",Do not treat licensing as a filter. Do not propose replacing native foundations unless source evidence is overwhelming.,ali-vilab/vace,v6_unified_source_of_truth_pack,"Before recommending direct code use, inspect the target repo row in the v6.1 operational/phase/source-audit boards. Respect copyleft_strategy_v6_1, preferred_boundary_model_v6_1, and open_compliance_if_used_as_is_v6_1. Do not assume reverse engineering is mandatory or that as-is use is always sensible.","If the repo-level strategy says bounded_sidecar_preferred or boundary_first_then_decide_as_is_vs_reimplementation, audit clean interfaces, protocol seams, subprocess/container boundaries, and what would be required to reimplement only the strategically necessary portions.",v6.3_final_source_of_truth
SCR_0158,,,,,,,,,,ScriptoriumAI repo packet,ScriptoriumAI,ScriptoriumAI re-anchored VS Code packets v1,alibaba/hiclaw,alibaba/hiclaw,Candidate Bench,P3,bookmark candidate only,"Audit alibaba/hiclaw for ScriptoriumAI. Start from the reanchored bucket 'Candidate Bench' and current reality status 'bookmark candidate only'. Confirm actual implemented capability, hidden reusable modules, extension seams, and whether it strengthens the existing Unimplemented but relevant candidate lane. Focus on: 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.","Treat as unimplemented ScriptoriumAI candidate only. Do not let it redefine the current stack. Integrate only if a later audit proves it fills a real gap in the existing surfaces such as Dashboard, Editor, Corpus Graph, Runboard, AI Kanban, Corpus Search, Patch Review Queue, Visualizations, Whiteboard, Mind Map, PDF Intake, AI Diagram Studio, Video Studio, Research Agent, New Research Topic, Skills Manager, OpenAPI Routing, Manim Sandbox, Settings.","Repurpose here means mining for specific modules, algorithms, UI patterns, ingestion logic, workflow ideas, or export formats rather than assuming a full product transplant.",native/ScriptoriumAI-Server,stanford-oval/storm,abhigyanpatwari/GitNexus,"Return concrete files/modules/adapters worth reusing and a verdict on whether the current reanchored bucket should be kept, upgraded, or downgraded.",Do not treat licensing as a filter. Do not propose replacing native foundations unless source evidence is overwhelming.,alibaba/hiclaw,v6_unified_source_of_truth_pack,"Before recommending direct code use, inspect the target repo row in the v6.1 operational/phase/source-audit boards. Respect copyleft_strategy_v6_1, preferred_boundary_model_v6_1, and open_compliance_if_used_as_is_v6_1. Do not assume reverse engineering is mandatory or that as-is use is always sensible.","If the repo-level strategy says bounded_sidecar_preferred or boundary_first_then_decide_as_is_vs_reimplementation, audit clean interfaces, protocol seams, subprocess/container boundaries, and what would be required to reimplement only the strategically necessary portions.",v6.3_final_source_of_truth
SCR_0159,,,,,,,,,,ScriptoriumAI repo packet,ScriptoriumAI,ScriptoriumAI re-anchored VS Code packets v1,anthropics/claude-skills,anthropics/claude-skills,Candidate Bench,P3,bookmark candidate only,"Audit anthropics/claude-skills for ScriptoriumAI. Start from the reanchored bucket 'Candidate Bench' and current reality status 'bookmark candidate only'. Confirm actual implemented capability, hidden reusable modules, extension seams, and whether it strengthens the existing Unimplemented but relevant candidate lane. Focus on: Inspect hidden modules, extension seams, data contracts, rendering paths, auth/storage coupling, and export/import boundaries.",,"Treat as unimplemented ScriptoriumAI candidate only. Do not let it redefine the current stack. Integrate only if a later audit proves it fills a real gap in the existing surfaces such as Dashboard, Editor, Corpus Graph, Runboard, AI Kanban, Corpus Search, Patch Review Queue, Visualizations, Whiteboard, Mind Map, PDF Intake, AI Diagram Studio, Video Studio, Research Agent, New Research Topic, Skills Manager, OpenAPI Routing, Manim Sandbox, Settings.","Repurpose here means mining for specific modules, algorithms, UI patterns, ingestion logic, workflow ideas, or export formats rather than assuming a full product transplant.",native/ScriptoriumAI-Server,stanford-oval/storm,abhigyanpatwari/GitNexus,"Return concrete files/modules/adapters worth reusing and a verdict on whether the current reanchored bucket should be kept, upgraded, or downgraded.",Do not treat licensing as a filter. Do not propose replacing native foundations unless source evidence is overwhelming.,anthropics/claude-skills,v6_unified_source_of_truth_pack,"Before recommending direct code use, inspect the target repo row in the v6.1 operational/phase/source-audit boards. Respect copyleft_strategy_v6_1, preferred_boundary_model_v6_1, and open_compliance_if_used_as_is_v6_1. Do not assume reverse engineering is mandatory or that as-is use is always sensible.","If the repo-level strategy says bounded_sidecar_preferred or boundary_first_then_decide_as_is_vs_reimplementation, audit clean interfaces, protocol seams, subprocess/container boundaries, and what would be required to reimplement only the strategically necessary portions.",v6.3_final_source_of_truth
SCR_0160,,,,,,,,,,ScriptoriumAI repo packet,ScriptoriumAI,ScriptoriumAI re-anchored VS Code packets v1,automazeio/ccpm,automazeio/ccpm,Candidate Bench,P3,bookmark candidate only,"Audit automazeio/ccpm for ScriptoriumAI. Start from the reanchored bucket 'Candidate Bench' and current reality status 'bookmark candidate only'. Confirm actual implemented capability, hidden reusable modules, extension seams, and whether it strengthens the existing Unimplemented but relevant candidate lane. Focus on: Inspect planner/task graph; provider abstraction; tool registry or MCP bridges; memory/state schema; approvals/retries; telemetry/event bus; plugin or skill loading 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 planner loops, tool registries, MCP servers/clients, prompt/skill folders, memory stores, approval gates, background-job orchestration, and undocumented provider adapters.","Treat as unimplemented ScriptoriumAI candidate only. Do not let it redefine the current stack. Integrate only if a later audit proves it fills a real gap in the existing surfaces such as Dashboard, Editor, Corpus Graph, Runboard, AI Kanban, Corpus Search, Patch Review Queue, Visualizations, Whiteboard, Mind Map, PDF Intake, AI Diagram Studio, Video Studio, Research Agent, New Research Topic, Skills Manager, OpenAPI Routing, Manim Sandbox, Settings.","Repurpose here means mining for specific modules, algorithms, UI patterns, ingestion logic, workflow ideas, or export formats rather than assuming a full product transplant.",native/ScriptoriumAI-Server,stanford-oval/storm,abhigyanpatwari/GitNexus,"Return concrete files/modules/adapters worth reusing and a verdict on whether the current reanchored bucket should be kept, upgraded, or downgraded.",Do not treat licensing as a filter. Do not propose replacing native foundations unless source evidence is overwhelming.,automazeio/ccpm,v6_unified_source_of_truth_pack,"Before recommending direct code use, inspect the target repo row in the v6.1 operational/phase/source-audit boards. Respect copyleft_strategy_v6_1, preferred_boundary_model_v6_1, and open_compliance_if_used_as_is_v6_1. Do not assume reverse engineering is mandatory or that as-is use is always sensible.","If the repo-level strategy says bounded_sidecar_preferred or boundary_first_then_decide_as_is_vs_reimplementation, audit clean interfaces, protocol seams, subprocess/container boundaries, and what would be required to reimplement only the strategically necessary portions.",v6.3_final_source_of_truth
SCR_0161,,,,,,,,,,ScriptoriumAI repo packet,ScriptoriumAI,ScriptoriumAI re-anchored VS Code packets v1,avinash201199/founders-kit,avinash201199/founders-kit,Candidate Bench,P3,bookmark candidate only,"Audit avinash201199/founders-kit for ScriptoriumAI. Start from the reanchored bucket 'Candidate Bench' and current reality status 'bookmark candidate only'. Confirm actual implemented capability, hidden reusable modules, extension seams, and whether it strengthens the existing Unimplemented but relevant candidate lane. Focus on: 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.","Treat as unimplemented ScriptoriumAI candidate only. Do not let it redefine the current stack. Integrate only if a later audit proves it fills a real gap in the existing surfaces such as Dashboard, Editor, Corpus Graph, Runboard, AI Kanban, Corpus Search, Patch Review Queue, Visualizations, Whiteboard, Mind Map, PDF Intake, AI Diagram Studio, Video Studio, Research Agent, New Research Topic, Skills Manager, OpenAPI Routing, Manim Sandbox, Settings.","Repurpose here means mining for specific modules, algorithms, UI patterns, ingestion logic, workflow ideas, or export formats rather than assuming a full product transplant.",native/scriptoriumai-ui,native/ScriptoriumAI-Server,abhigyanpatwari/GitNexus,"Return concrete files/modules/adapters worth reusing and a verdict on whether the current reanchored bucket should be kept, upgraded, or downgraded.",Do not treat licensing as a filter. Do not propose replacing native foundations unless source evidence is overwhelming.,avinash201199/founders-kit,v6_unified_source_of_truth_pack,"Before recommending direct code use, inspect the target repo row in the v6.1 operational/phase/source-audit boards. Respect copyleft_strategy_v6_1, preferred_boundary_model_v6_1, and open_compliance_if_used_as_is_v6_1. Do not assume reverse engineering is mandatory or that as-is use is always sensible.","If the repo-level strategy says bounded_sidecar_preferred or boundary_first_then_decide_as_is_vs_reimplementation, audit clean interfaces, protocol seams, subprocess/container boundaries, and what would be required to reimplement only the strategically necessary portions.",v6.3_final_source_of_truth
SCR_0162,,,,,,,,,,ScriptoriumAI repo packet,ScriptoriumAI,ScriptoriumAI re-anchored VS Code packets v1,bcurts/agentchattr,bcurts/agentchattr,Candidate Bench,P3,bookmark candidate only,"Audit bcurts/agentchattr for ScriptoriumAI. Start from the reanchored bucket 'Candidate Bench' and current reality status 'bookmark candidate only'. Confirm actual implemented capability, hidden reusable modules, extension seams, and whether it strengthens the existing Unimplemented but relevant candidate lane. Focus on: Inspect planner/task graph; provider abstraction; tool registry or MCP bridges; memory/state schema; approvals/retries; telemetry/event bus; plugin or skill loading 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 planner loops, tool registries, MCP servers/clients, prompt/skill folders, memory stores, approval gates, background-job orchestration, and undocumented provider adapters.","Treat as unimplemented ScriptoriumAI candidate only. Do not let it redefine the current stack. Integrate only if a later audit proves it fills a real gap in the existing surfaces such as Dashboard, Editor, Corpus Graph, Runboard, AI Kanban, Corpus Search, Patch Review Queue, Visualizations, Whiteboard, Mind Map, PDF Intake, AI Diagram Studio, Video Studio, Research Agent, New Research Topic, Skills Manager, OpenAPI Routing, Manim Sandbox, Settings.","Repurpose here means mining for specific modules, algorithms, UI patterns, ingestion logic, workflow ideas, or export formats rather than assuming a full product transplant.",native/ScriptoriumAI-Server,stanford-oval/storm,abhigyanpatwari/GitNexus,"Return concrete files/modules/adapters worth reusing and a verdict on whether the current reanchored bucket should be kept, upgraded, or downgraded.",Do not treat licensing as a filter. Do not propose replacing native foundations unless source evidence is overwhelming.,bcurts/agentchattr,v6_unified_source_of_truth_pack,"Before recommending direct code use, inspect the target repo row in the v6.1 operational/phase/source-audit boards. Respect copyleft_strategy_v6_1, preferred_boundary_model_v6_1, and open_compliance_if_used_as_is_v6_1. Do not assume reverse engineering is mandatory or that as-is use is always sensible.","If the repo-level strategy says bounded_sidecar_preferred or boundary_first_then_decide_as_is_vs_reimplementation, audit clean interfaces, protocol seams, subprocess/container boundaries, and what would be required to reimplement only the strategically necessary portions.",v6.3_final_source_of_truth
SCR_0163,,,,,,,,,,ScriptoriumAI repo packet,ScriptoriumAI,ScriptoriumAI re-anchored VS Code packets v1,better-auth/better-icons,better-auth/better-icons,Candidate Bench,P3,bookmark candidate only,"Audit better-auth/better-icons for ScriptoriumAI. Start from the reanchored bucket 'Candidate Bench' and current reality status 'bookmark candidate only'. Confirm actual implemented capability, hidden reusable modules, extension seams, and whether it strengthens the existing Unimplemented but relevant candidate lane. Focus on: Inspect planner/task graph; provider abstraction; tool registry or MCP bridges; memory/state schema; approvals/retries; telemetry/event bus; plugin or skill loading 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 planner loops, tool registries, MCP servers/clients, prompt/skill folders, memory stores, approval gates, background-job orchestration, and undocumented provider adapters.","Treat as unimplemented ScriptoriumAI candidate only. Do not let it redefine the current stack. Integrate only if a later audit proves it fills a real gap in the existing surfaces such as Dashboard, Editor, Corpus Graph, Runboard, AI Kanban, Corpus Search, Patch Review Queue, Visualizations, Whiteboard, Mind Map, PDF Intake, AI Diagram Studio, Video Studio, Research Agent, New Research Topic, Skills Manager, OpenAPI Routing, Manim Sandbox, Settings.","Repurpose here means mining for specific modules, algorithms, UI patterns, ingestion logic, workflow ideas, or export formats rather than assuming a full product transplant.",native/scriptoriumai-ui,native/ScriptoriumAI-Server,sharelatex/sharelatex,"Return concrete files/modules/adapters worth reusing and a verdict on whether the current reanchored bucket should be kept, upgraded, or downgraded.",Do not treat licensing as a filter. Do not propose replacing native foundations unless source evidence is overwhelming.,better-auth/better-icons,v6_unified_source_of_truth_pack,"Before recommending direct code use, inspect the target repo row in the v6.1 operational/phase/source-audit boards. Respect copyleft_strategy_v6_1, preferred_boundary_model_v6_1, and open_compliance_if_used_as_is_v6_1. Do not assume reverse engineering is mandatory or that as-is use is always sensible.","If the repo-level strategy says bounded_sidecar_preferred or boundary_first_then_decide_as_is_vs_reimplementation, audit clean interfaces, protocol seams, subprocess/container boundaries, and what would be required to reimplement only the strategically necessary portions.",v6.3_final_source_of_truth
SCR_0164,,,,,,,,,,ScriptoriumAI repo packet,ScriptoriumAI,ScriptoriumAI re-anchored VS Code packets v1,bhosley/manim-meshes,bhosley/manim-meshes,Candidate Bench,P3,bookmark candidate only,"Audit bhosley/manim-meshes for ScriptoriumAI. Start from the reanchored bucket 'Candidate Bench' and current reality status 'bookmark candidate only'. Confirm actual implemented capability, hidden reusable modules, extension seams, and whether it strengthens the existing Unimplemented but relevant candidate lane. Focus on: Inspect hidden modules, extension seams, data contracts, rendering paths, auth/storage coupling, and export/import boundaries.",,"Treat as unimplemented ScriptoriumAI candidate only. Do not let it redefine the current stack. Integrate only if a later audit proves it fills a real gap in the existing surfaces such as Dashboard, Editor, Corpus Graph, Runboard, AI Kanban, Corpus Search, Patch Review Queue, Visualizations, Whiteboard, Mind Map, PDF Intake, AI Diagram Studio, Video Studio, Research Agent, New Research Topic, Skills Manager, OpenAPI Routing, Manim Sandbox, Settings.","Repurpose here means mining for specific modules, algorithms, UI patterns, ingestion logic, workflow ideas, or export formats rather than assuming a full product transplant.",manimcommunity/manim,remotion-dev/remotion,native/ScriptoriumAI-Visualizer,"Return concrete files/modules/adapters worth reusing and a verdict on whether the current reanchored bucket should be kept, upgraded, or downgraded.",Do not treat licensing as a filter. Do not propose replacing native foundations unless source evidence is overwhelming.,bhosley/manim-meshes,v6_unified_source_of_truth_pack,"Before recommending direct code use, inspect the target repo row in the v6.1 operational/phase/source-audit boards. Respect copyleft_strategy_v6_1, preferred_boundary_model_v6_1, and open_compliance_if_used_as_is_v6_1. Do not assume reverse engineering is mandatory or that as-is use is always sensible.","If the repo-level strategy says bounded_sidecar_preferred or boundary_first_then_decide_as_is_vs_reimplementation, audit clean interfaces, protocol seams, subprocess/container boundaries, and what would be required to reimplement only the strategically necessary portions.",v6.3_final_source_of_truth
SCR_0165,,,,,,,,,,ScriptoriumAI repo packet,ScriptoriumAI,ScriptoriumAI re-anchored VS Code packets v1,brightdata/brightdata-mcp,brightdata/brightdata-mcp,Candidate Bench,P3,bookmark candidate only,"Audit brightdata/brightdata-mcp for ScriptoriumAI. Start from the reanchored bucket 'Candidate Bench' and current reality status 'bookmark candidate only'. Confirm actual implemented capability, hidden reusable modules, extension seams, and whether it strengthens the existing Unimplemented but relevant candidate lane. Focus on: Inspect planner/task graph; provider abstraction; tool registry or MCP bridges; memory/state schema; approvals/retries; telemetry/event bus; plugin or skill loading 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 planner loops, tool registries, MCP servers/clients, prompt/skill folders, memory stores, approval gates, background-job orchestration, and undocumented provider adapters.","Treat as unimplemented ScriptoriumAI candidate only. Do not let it redefine the current stack. Integrate only if a later audit proves it fills a real gap in the existing surfaces such as Dashboard, Editor, Corpus Graph, Runboard, AI Kanban, Corpus Search, Patch Review Queue, Visualizations, Whiteboard, Mind Map, PDF Intake, AI Diagram Studio, Video Studio, Research Agent, New Research Topic, Skills Manager, OpenAPI Routing, Manim Sandbox, Settings.","Repurpose here means mining for specific modules, algorithms, UI patterns, ingestion logic, workflow ideas, or export formats rather than assuming a full product transplant.",native/scriptoriumai-ui,native/ScriptoriumAI-Server,abhigyanpatwari/GitNexus,"Return concrete files/modules/adapters worth reusing and a verdict on whether the current reanchored bucket should be kept, upgraded, or downgraded.",Do not treat licensing as a filter. Do not propose replacing native foundations unless source evidence is overwhelming.,brightdata/brightdata-mcp,v6_unified_source_of_truth_pack,"Before recommending direct code use, inspect the target repo row in the v6.1 operational/phase/source-audit boards. Respect copyleft_strategy_v6_1, preferred_boundary_model_v6_1, and open_compliance_if_used_as_is_v6_1. Do not assume reverse engineering is mandatory or that as-is use is always sensible.","If the repo-level strategy says bounded_sidecar_preferred or boundary_first_then_decide_as_is_vs_reimplementation, audit clean interfaces, protocol seams, subprocess/container boundaries, and what would be required to reimplement only the strategically necessary portions.",v6.3_final_source_of_truth
SCR_0166,,,,,,,,,,ScriptoriumAI repo packet,ScriptoriumAI,ScriptoriumAI re-anchored VS Code packets v1,bytebot-ai/bytebot,bytebot-ai/bytebot,Candidate Bench,P3,bookmark candidate only,"Audit bytebot-ai/bytebot for ScriptoriumAI. Start from the reanchored bucket 'Candidate Bench' and current reality status 'bookmark candidate only'. Confirm actual implemented capability, hidden reusable modules, extension seams, and whether it strengthens the existing Unimplemented but relevant candidate lane. Focus on: Inspect planner/task graph; provider abstraction; tool registry or MCP bridges; memory/state schema; approvals/retries; telemetry/event bus; plugin or skill loading 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 planner loops, tool registries, MCP servers/clients, prompt/skill folders, memory stores, approval gates, background-job orchestration, and undocumented provider adapters.","Treat as unimplemented ScriptoriumAI candidate only. Do not let it redefine the current stack. Integrate only if a later audit proves it fills a real gap in the existing surfaces such as Dashboard, Editor, Corpus Graph, Runboard, AI Kanban, Corpus Search, Patch Review Queue, Visualizations, Whiteboard, Mind Map, PDF Intake, AI Diagram Studio, Video Studio, Research Agent, New Research Topic, Skills Manager, OpenAPI Routing, Manim Sandbox, Settings.","Repurpose here means mining for specific modules, algorithms, UI patterns, ingestion logic, workflow ideas, or export formats rather than assuming a full product transplant.",native/ScriptoriumAI-Server,stanford-oval/storm,abhigyanpatwari/GitNexus,"Return concrete files/modules/adapters worth reusing and a verdict on whether the current reanchored bucket should be kept, upgraded, or downgraded.",Do not treat licensing as a filter. Do not propose replacing native foundations unless source evidence is overwhelming.,bytebot-ai/bytebot,v6_unified_source_of_truth_pack,"Before recommending direct code use, inspect the target repo row in the v6.1 operational/phase/source-audit boards. Respect copyleft_strategy_v6_1, preferred_boundary_model_v6_1, and open_compliance_if_used_as_is_v6_1. Do not assume reverse engineering is mandatory or that as-is use is always sensible.","If the repo-level strategy says bounded_sidecar_preferred or boundary_first_then_decide_as_is_vs_reimplementation, audit clean interfaces, protocol seams, subprocess/container boundaries, and what would be required to reimplement only the strategically necessary portions.",v6.3_final_source_of_truth
SCR_0167,,,,,,,,,,ScriptoriumAI repo packet,ScriptoriumAI,ScriptoriumAI re-anchored VS Code packets v1,calesthio/OpenMontage,calesthio/openmontage,Candidate Bench,P3,bookmark candidate only,"Audit calesthio/OpenMontage for ScriptoriumAI. Start from the reanchored bucket 'Candidate Bench' and current reality status 'bookmark candidate only'. Confirm actual implemented capability, hidden reusable modules, extension seams, and whether it strengthens the existing Unimplemented but relevant candidate lane. Focus on: Inspect planner/task graph; provider abstraction; tool registry or MCP bridges; memory/state schema; approvals/retries; telemetry/event bus; plugin or skill loading 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 planner loops, tool registries, MCP servers/clients, prompt/skill folders, memory stores, approval gates, background-job orchestration, and undocumented provider adapters.","Treat as unimplemented ScriptoriumAI candidate only. Do not let it redefine the current stack. Integrate only if a later audit proves it fills a real gap in the existing surfaces such as Dashboard, Editor, Corpus Graph, Runboard, AI Kanban, Corpus Search, Patch Review Queue, Visualizations, Whiteboard, Mind Map, PDF Intake, AI Diagram Studio, Video Studio, Research Agent, New Research Topic, Skills Manager, OpenAPI Routing, Manim Sandbox, Settings.","Repurpose here means mining for specific modules, algorithms, UI patterns, ingestion logic, workflow ideas, or export formats rather than assuming a full product transplant.",native/ScriptoriumAI-Server,stanford-oval/storm,abhigyanpatwari/GitNexus,"Return concrete files/modules/adapters worth reusing and a verdict on whether the current reanchored bucket should be kept, upgraded, or downgraded.",Do not treat licensing as a filter. Do not propose replacing native foundations unless source evidence is overwhelming.,calesthio/openmontage,v6_unified_source_of_truth_pack,"Before recommending direct code use, inspect the target repo row in the v6.1 operational/phase/source-audit boards. Respect copyleft_strategy_v6_1, preferred_boundary_model_v6_1, and open_compliance_if_used_as_is_v6_1. Do not assume reverse engineering is mandatory or that as-is use is always sensible.","If the repo-level strategy says bounded_sidecar_preferred or boundary_first_then_decide_as_is_vs_reimplementation, audit clean interfaces, protocol seams, subprocess/container boundaries, and what would be required to reimplement only the strategically necessary portions.",v6.3_final_source_of_truth
SCR_0168,,,,,,,,,,ScriptoriumAI repo packet,ScriptoriumAI,ScriptoriumAI re-anchored VS Code packets v1,chiphuyen/aie-book,chiphuyen/aie-book,Candidate Bench,P3,bookmark candidate only,"Audit chiphuyen/aie-book for ScriptoriumAI. Start from the reanchored bucket 'Candidate Bench' and current reality status 'bookmark candidate only'. Confirm actual implemented capability, hidden reusable modules, extension seams, and whether it strengthens the existing Unimplemented but relevant candidate lane. Focus on: Inspect package/module map; entrypoints; config and schema files; adapters/integrations; persistence model; tests/examples; hidden feature flags; plugin 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 hidden admin tools, reusable services, plugin systems, import/export, analytics, background jobs, and any engine more valuable than the public README suggests.","Treat as unimplemented ScriptoriumAI candidate only. Do not let it redefine the current stack. Integrate only if a later audit proves it fills a real gap in the existing surfaces such as Dashboard, Editor, Corpus Graph, Runboard, AI Kanban, Corpus Search, Patch Review Queue, Visualizations, Whiteboard, Mind Map, PDF Intake, AI Diagram Studio, Video Studio, Research Agent, New Research Topic, Skills Manager, OpenAPI Routing, Manim Sandbox, Settings.","Repurpose here means mining for specific modules, algorithms, UI patterns, ingestion logic, workflow ideas, or export formats rather than assuming a full product transplant.",native/scriptoriumai-ui,native/ScriptoriumAI-Server,abhigyanpatwari/GitNexus,"Return concrete files/modules/adapters worth reusing and a verdict on whether the current reanchored bucket should be kept, upgraded, or downgraded.",Do not treat licensing as a filter. Do not propose replacing native foundations unless source evidence is overwhelming.,chiphuyen/aie-book,v6_unified_source_of_truth_pack,"Before recommending direct code use, inspect the target repo row in the v6.1 operational/phase/source-audit boards. Respect copyleft_strategy_v6_1, preferred_boundary_model_v6_1, and open_compliance_if_used_as_is_v6_1. Do not assume reverse engineering is mandatory or that as-is use is always sensible.","If the repo-level strategy says bounded_sidecar_preferred or boundary_first_then_decide_as_is_vs_reimplementation, audit clean interfaces, protocol seams, subprocess/container boundaries, and what would be required to reimplement only the strategically necessary portions.",v6.3_final_source_of_truth
SCR_0169,,,,,,,,,,ScriptoriumAI repo packet,ScriptoriumAI,ScriptoriumAI re-anchored VS Code packets v1,code2video/code2video,code2video/code2video,Candidate Bench,P3,bookmark candidate only,"Audit code2video/code2video for ScriptoriumAI. Start from the reanchored bucket 'Candidate Bench' and current reality status 'bookmark candidate only'. Confirm actual implemented capability, hidden reusable modules, extension seams, and whether it strengthens the existing Unimplemented but relevant candidate lane. Focus on: Inspect hidden modules, extension seams, data contracts, rendering paths, auth/storage coupling, and export/import boundaries.",,"Treat as unimplemented ScriptoriumAI candidate only. Do not let it redefine the current stack. Integrate only if a later audit proves it fills a real gap in the existing surfaces such as Dashboard, Editor, Corpus Graph, Runboard, AI Kanban, Corpus Search, Patch Review Queue, Visualizations, Whiteboard, Mind Map, PDF Intake, AI Diagram Studio, Video Studio, Research Agent, New Research Topic, Skills Manager, OpenAPI Routing, Manim Sandbox, Settings.","Repurpose here means mining for specific modules, algorithms, UI patterns, ingestion logic, workflow ideas, or export formats rather than assuming a full product transplant.",manimcommunity/manim,remotion-dev/remotion,native/ScriptoriumAI-Visualizer,"Return concrete files/modules/adapters worth reusing and a verdict on whether the current reanchored bucket should be kept, upgraded, or downgraded.",Do not treat licensing as a filter. Do not propose replacing native foundations unless source evidence is overwhelming.,code2video/code2video,v6_unified_source_of_truth_pack,"Before recommending direct code use, inspect the target repo row in the v6.1 operational/phase/source-audit boards. Respect copyleft_strategy_v6_1, preferred_boundary_model_v6_1, and open_compliance_if_used_as_is_v6_1. Do not assume reverse engineering is mandatory or that as-is use is always sensible.","If the repo-level strategy says bounded_sidecar_preferred or boundary_first_then_decide_as_is_vs_reimplementation, audit clean interfaces, protocol seams, subprocess/container boundaries, and what would be required to reimplement only the strategically necessary portions.",v6.3_final_source_of_truth
SCR_0170,,,,,,,,,,ScriptoriumAI repo packet,ScriptoriumAI,ScriptoriumAI re-anchored VS Code packets v1,coleam00/ottomator-agents,coleam00/ottomator-agents,Candidate Bench,P3,bookmark candidate only,"Audit coleam00/ottomator-agents for ScriptoriumAI. Start from the reanchored bucket 'Candidate Bench' and current reality status 'bookmark candidate only'. Confirm actual implemented capability, hidden reusable modules, extension seams, and whether it strengthens the existing Unimplemented but relevant candidate lane. Focus on: Inspect planner/task graph; provider abstraction; tool registry or MCP bridges; memory/state schema; approvals/retries; telemetry/event bus; plugin or skill loading 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 planner loops, tool registries, MCP servers/clients, prompt/skill folders, memory stores, approval gates, background-job orchestration, and undocumented provider adapters.","Treat as unimplemented ScriptoriumAI candidate only. Do not let it redefine the current stack. Integrate only if a later audit proves it fills a real gap in the existing surfaces such as Dashboard, Editor, Corpus Graph, Runboard, AI Kanban, Corpus Search, Patch Review Queue, Visualizations, Whiteboard, Mind Map, PDF Intake, AI Diagram Studio, Video Studio, Research Agent, New Research Topic, Skills Manager, OpenAPI Routing, Manim Sandbox, Settings.","Repurpose here means mining for specific modules, algorithms, UI patterns, ingestion logic, workflow ideas, or export formats rather than assuming a full product transplant.",native/ScriptoriumAI-Server,stanford-oval/storm,abhigyanpatwari/GitNexus,"Return concrete files/modules/adapters worth reusing and a verdict on whether the current reanchored bucket should be kept, upgraded, or downgraded.",Do not treat licensing as a filter. Do not propose replacing native foundations unless source evidence is overwhelming.,coleam00/ottomator-agents,v6_unified_source_of_truth_pack,"Before recommending direct code use, inspect the target repo row in the v6.1 operational/phase/source-audit boards. Respect copyleft_strategy_v6_1, preferred_boundary_model_v6_1, and open_compliance_if_used_as_is_v6_1. Do not assume reverse engineering is mandatory or that as-is use is always sensible.","If the repo-level strategy says bounded_sidecar_preferred or boundary_first_then_decide_as_is_vs_reimplementation, audit clean interfaces, protocol seams, subprocess/container boundaries, and what would be required to reimplement only the strategically necessary portions.",v6.3_final_source_of_truth
SCR_0171,,,,,,,,,,ScriptoriumAI repo packet,ScriptoriumAI,ScriptoriumAI re-anchored VS Code packets v1,connor-mccloskey/manim-automata,connor-mccloskey/manim-automata,Candidate Bench,P3,bookmark candidate only,"Audit connor-mccloskey/manim-automata for ScriptoriumAI. Start from the reanchored bucket 'Candidate Bench' and current reality status 'bookmark candidate only'. Confirm actual implemented capability, hidden reusable modules, extension seams, and whether it strengthens the existing Unimplemented but relevant candidate lane. Focus on: Inspect hidden modules, extension seams, data contracts, rendering paths, auth/storage coupling, and export/import boundaries.",,"Treat as unimplemented ScriptoriumAI candidate only. Do not let it redefine the current stack. Integrate only if a later audit proves it fills a real gap in the existing surfaces such as Dashboard, Editor, Corpus Graph, Runboard, AI Kanban, Corpus Search, Patch Review Queue, Visualizations, Whiteboard, Mind Map, PDF Intake, AI Diagram Studio, Video Studio, Research Agent, New Research Topic, Skills Manager, OpenAPI Routing, Manim Sandbox, Settings.","Repurpose here means mining for specific modules, algorithms, UI patterns, ingestion logic, workflow ideas, or export formats rather than assuming a full product transplant.",manimcommunity/manim,remotion-dev/remotion,native/ScriptoriumAI-Visualizer,"Return concrete files/modules/adapters worth reusing and a verdict on whether the current reanchored bucket should be kept, upgraded, or downgraded.",Do not treat licensing as a filter. Do not propose replacing native foundations unless source evidence is overwhelming.,connor-mccloskey/manim-automata,v6_unified_source_of_truth_pack,"Before recommending direct code use, inspect the target repo row in the v6.1 operational/phase/source-audit boards. Respect copyleft_strategy_v6_1, preferred_boundary_model_v6_1, and open_compliance_if_used_as_is_v6_1. Do not assume reverse engineering is mandatory or that as-is use is always sensible.","If the repo-level strategy says bounded_sidecar_preferred or boundary_first_then_decide_as_is_vs_reimplementation, audit clean interfaces, protocol seams, subprocess/container boundaries, and what would be required to reimplement only the strategically necessary portions.",v6.3_final_source_of_truth
SCR_0172,,,,,,,,,,ScriptoriumAI repo packet,ScriptoriumAI,ScriptoriumAI re-anchored VS Code packets v1,crshdn/mission-control,crshdn/mission-control,Candidate Bench,P3,bookmark candidate only,"Audit crshdn/mission-control for ScriptoriumAI. Start from the reanchored bucket 'Candidate Bench' and current reality status 'bookmark candidate only'. Confirm actual implemented capability, hidden reusable modules, extension seams, and whether it strengthens the existing Unimplemented but relevant candidate lane. Focus on: Inspect planner/task graph; provider abstraction; tool registry or MCP bridges; memory/state schema; approvals/retries; telemetry/event bus; plugin or skill loading 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 planner loops, tool registries, MCP servers/clients, prompt/skill folders, memory stores, approval gates, background-job orchestration, and undocumented provider adapters.","Treat as unimplemented ScriptoriumAI candidate only. Do not let it redefine the current stack. Integrate only if a later audit proves it fills a real gap in the existing surfaces such as Dashboard, Editor, Corpus Graph, Runboard, AI Kanban, Corpus Search, Patch Review Queue, Visualizations, Whiteboard, Mind Map, PDF Intake, AI Diagram Studio, Video Studio, Research Agent, New Research Topic, Skills Manager, OpenAPI Routing, Manim Sandbox, Settings.","Repurpose here means mining for specific modules, algorithms, UI patterns, ingestion logic, workflow ideas, or export formats rather than assuming a full product transplant.",native/ScriptoriumAI-Server,stanford-oval/storm,abhigyanpatwari/GitNexus,"Return concrete files/modules/adapters worth reusing and a verdict on whether the current reanchored bucket should be kept, upgraded, or downgraded.",Do not treat licensing as a filter. Do not propose replacing native foundations unless source evidence is overwhelming.,crshdn/mission-control,v6_unified_source_of_truth_pack,"Before recommending direct code use, inspect the target repo row in the v6.1 operational/phase/source-audit boards. Respect copyleft_strategy_v6_1, preferred_boundary_model_v6_1, and open_compliance_if_used_as_is_v6_1. Do not assume reverse engineering is mandatory or that as-is use is always sensible.","If the repo-level strategy says bounded_sidecar_preferred or boundary_first_then_decide_as_is_vs_reimplementation, audit clean interfaces, protocol seams, subprocess/container boundaries, and what would be required to reimplement only the strategically necessary portions.",v6.3_final_source_of_truth
SCR_0173,,,,,,,,,,ScriptoriumAI repo packet,ScriptoriumAI,ScriptoriumAI re-anchored VS Code packets v1,dabit3/agent-handoff,dabit3/agent-handoff,Candidate Bench,P3,bookmark candidate only,"Audit dabit3/agent-handoff for ScriptoriumAI. Start from the reanchored bucket 'Candidate Bench' and current reality status 'bookmark candidate only'. Confirm actual implemented capability, hidden reusable modules, extension seams, and whether it strengthens the existing Unimplemented but relevant candidate lane. Focus on: Inspect planner/task graph; provider abstraction; tool registry or MCP bridges; memory/state schema; approvals/retries; telemetry/event bus; plugin or skill loading 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 planner loops, tool registries, MCP servers/clients, prompt/skill folders, memory stores, approval gates, background-job orchestration, and undocumented provider adapters.","Treat as unimplemented ScriptoriumAI candidate only. Do not let it redefine the current stack. Integrate only if a later audit proves it fills a real gap in the existing surfaces such as Dashboard, Editor, Corpus Graph, Runboard, AI Kanban, Corpus Search, Patch Review Queue, Visualizations, Whiteboard, Mind Map, PDF Intake, AI Diagram Studio, Video Studio, Research Agent, New Research Topic, Skills Manager, OpenAPI Routing, Manim Sandbox, Settings.","Repurpose here means mining for specific modules, algorithms, UI patterns, ingestion logic, workflow ideas, or export formats rather than assuming a full product transplant.",native/ScriptoriumAI-Server,stanford-oval/storm,abhigyanpatwari/GitNexus,"Return concrete files/modules/adapters worth reusing and a verdict on whether the current reanchored bucket should be kept, upgraded, or downgraded.",Do not treat licensing as a filter. Do not propose replacing native foundations unless source evidence is overwhelming.,dabit3/agent-handoff,v6_unified_source_of_truth_pack,"Before recommending direct code use, inspect the target repo row in the v6.1 operational/phase/source-audit boards. Respect copyleft_strategy_v6_1, preferred_boundary_model_v6_1, and open_compliance_if_used_as_is_v6_1. Do not assume reverse engineering is mandatory or that as-is use is always sensible.","If the repo-level strategy says bounded_sidecar_preferred or boundary_first_then_decide_as_is_vs_reimplementation, audit clean interfaces, protocol seams, subprocess/container boundaries, and what would be required to reimplement only the strategically necessary portions.",v6.3_final_source_of_truth
SCR_0174,,,,,,,,,,ScriptoriumAI repo packet,ScriptoriumAI,ScriptoriumAI re-anchored VS Code packets v1,dabit3/agent-replay,dabit3/agent-replay,Candidate Bench,P3,bookmark candidate only,"Audit dabit3/agent-replay for ScriptoriumAI. Start from the reanchored bucket 'Candidate Bench' and current reality status 'bookmark candidate only'. Confirm actual implemented capability, hidden reusable modules, extension seams, and whether it strengthens the existing Unimplemented but relevant candidate lane. Focus on: 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 planner loops, tool registries, MCP servers/clients, prompt/skill folders, memory stores, approval gates, background-job orchestration, and undocumented provider adapters.","Treat as unimplemented ScriptoriumAI candidate only. Do not let it redefine the current stack. Integrate only if a later audit proves it fills a real gap in the existing surfaces such as Dashboard, Editor, Corpus Graph, Runboard, AI Kanban, Corpus Search, Patch Review Queue, Visualizations, Whiteboard, Mind Map, PDF Intake, AI Diagram Studio, Video Studio, Research Agent, New Research Topic, Skills Manager, OpenAPI Routing, Manim Sandbox, Settings.","Repurpose here means mining for specific modules, algorithms, UI patterns, ingestion logic, workflow ideas, or export formats rather than assuming a full product transplant.",native/ScriptoriumAI-Server,stanford-oval/storm,abhigyanpatwari/GitNexus,"Return concrete files/modules/adapters worth reusing and a verdict on whether the current reanchored bucket should be kept, upgraded, or downgraded.",Do not treat licensing as a filter. Do not propose replacing native foundations unless source evidence is overwhelming.,dabit3/agent-replay,v6_unified_source_of_truth_pack,"Before recommending direct code use, inspect the target repo row in the v6.1 operational/phase/source-audit boards. Respect copyleft_strategy_v6_1, preferred_boundary_model_v6_1, and open_compliance_if_used_as_is_v6_1. Do not assume reverse engineering is mandatory or that as-is use is always sensible.","If the repo-level strategy says bounded_sidecar_preferred or boundary_first_then_decide_as_is_vs_reimplementation, audit clean interfaces, protocol seams, subprocess/container boundaries, and what would be required to reimplement only the strategically necessary portions.",v6.3_final_source_of_truth
SCR_0175,,,,,,,,,,ScriptoriumAI repo packet,ScriptoriumAI,ScriptoriumAI re-anchored VS Code packets v1,dair-ai/Prompt-Engineering-Guide,dair-ai/prompt-engineering-guide,Candidate Bench,P3,bookmark candidate only,"Audit dair-ai/Prompt-Engineering-Guide for ScriptoriumAI. Start from the reanchored bucket 'Candidate Bench' and current reality status 'bookmark candidate only'. Confirm actual implemented capability, hidden reusable modules, extension seams, and whether it strengthens the existing Unimplemented but relevant candidate lane. Focus on: Inspect planner/task graph; provider abstraction; tool registry or MCP bridges; memory/state schema; approvals/retries; telemetry/event bus; plugin or skill loading 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 planner loops, tool registries, MCP servers/clients, prompt/skill folders, memory stores, approval gates, background-job orchestration, and undocumented provider adapters.","Treat as unimplemented ScriptoriumAI candidate only. Do not let it redefine the current stack. Integrate only if a later audit proves it fills a real gap in the existing surfaces such as Dashboard, Editor, Corpus Graph, Runboard, AI Kanban, Corpus Search, Patch Review Queue, Visualizations, Whiteboard, Mind Map, PDF Intake, AI Diagram Studio, Video Studio, Research Agent, New Research Topic, Skills Manager, OpenAPI Routing, Manim Sandbox, Settings.","Repurpose here means mining for specific modules, algorithms, UI patterns, ingestion logic, workflow ideas, or export formats rather than assuming a full product transplant.",native/ScriptoriumAI-Server,stanford-oval/storm,abhigyanpatwari/GitNexus,"Return concrete files/modules/adapters worth reusing and a verdict on whether the current reanchored bucket should be kept, upgraded, or downgraded.",Do not treat licensing as a filter. Do not propose replacing native foundations unless source evidence is overwhelming.,dair-ai/prompt-engineering-guide,v6_unified_source_of_truth_pack,"Before recommending direct code use, inspect the target repo row in the v6.1 operational/phase/source-audit boards. Respect copyleft_strategy_v6_1, preferred_boundary_model_v6_1, and open_compliance_if_used_as_is_v6_1. Do not assume reverse engineering is mandatory or that as-is use is always sensible.","If the repo-level strategy says bounded_sidecar_preferred or boundary_first_then_decide_as_is_vs_reimplementation, audit clean interfaces, protocol seams, subprocess/container boundaries, and what would be required to reimplement only the strategically necessary portions.",v6.3_final_source_of_truth
SCR_0176,,,,,,,,,,ScriptoriumAI repo packet,ScriptoriumAI,ScriptoriumAI re-anchored VS Code packets v1,datawhalechina/happy-llm,datawhalechina/happy-llm,Candidate Bench,P3,bookmark candidate only,"Audit datawhalechina/happy-llm for ScriptoriumAI. Start from the reanchored bucket 'Candidate Bench' and current reality status 'bookmark candidate only'. Confirm actual implemented capability, hidden reusable modules, extension seams, and whether it strengthens the existing Unimplemented but relevant candidate lane. Focus on: Inspect planner/task graph; provider abstraction; tool registry or MCP bridges; memory/state schema; approvals/retries; telemetry/event bus; plugin or skill loading 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 planner loops, tool registries, MCP servers/clients, prompt/skill folders, memory stores, approval gates, background-job orchestration, and undocumented provider adapters.","Treat as unimplemented ScriptoriumAI candidate only. Do not let it redefine the current stack. Integrate only if a later audit proves it fills a real gap in the existing surfaces such as Dashboard, Editor, Corpus Graph, Runboard, AI Kanban, Corpus Search, Patch Review Queue, Visualizations, Whiteboard, Mind Map, PDF Intake, AI Diagram Studio, Video Studio, Research Agent, New Research Topic, Skills Manager, OpenAPI Routing, Manim Sandbox, Settings.","Repurpose here means mining for specific modules, algorithms, UI patterns, ingestion logic, workflow ideas, or export formats rather than assuming a full product transplant.",native/scriptoriumai-ui,native/ScriptoriumAI-Server,abhigyanpatwari/GitNexus,"Return concrete files/modules/adapters worth reusing and a verdict on whether the current reanchored bucket should be kept, upgraded, or downgraded.",Do not treat licensing as a filter. Do not propose replacing native foundations unless source evidence is overwhelming.,datawhalechina/happy-llm,v6_unified_source_of_truth_pack,"Before recommending direct code use, inspect the target repo row in the v6.1 operational/phase/source-audit boards. Respect copyleft_strategy_v6_1, preferred_boundary_model_v6_1, and open_compliance_if_used_as_is_v6_1. Do not assume reverse engineering is mandatory or that as-is use is always sensible.","If the repo-level strategy says bounded_sidecar_preferred or boundary_first_then_decide_as_is_vs_reimplementation, audit clean interfaces, protocol seams, subprocess/container boundaries, and what would be required to reimplement only the strategically necessary portions.",v6.3_final_source_of_truth
SCR_0177,,,,,,,,,,ScriptoriumAI repo packet,ScriptoriumAI,ScriptoriumAI re-anchored VS Code packets v1,dotnet/templating,dotnet/templating,Candidate Bench,P3,bookmark candidate only,"Audit dotnet/templating for ScriptoriumAI. Start from the reanchored bucket 'Candidate Bench' and current reality status 'bookmark candidate only'. Confirm actual implemented capability, hidden reusable modules, extension seams, and whether it strengthens the existing Unimplemented but relevant candidate lane. Focus on: Inspect document/block schema; sync/persistence model; permissions and sharing; citation/external-source pipeline; import/export adapters; plugin/extension points; editor rendering model.","Inspect package manifests, README/docs, src tree, examples, tests, CI workflows, config files, migrations/schemas, and hidden feature flags or experimental modules. Look for document/block schema, sync/conflict logic, citation handling, editor plugins, export/render pipeline, prompt chains, report assembly, and collaborative presence code.","Treat as unimplemented ScriptoriumAI candidate only. Do not let it redefine the current stack. Integrate only if a later audit proves it fills a real gap in the existing surfaces such as Dashboard, Editor, Corpus Graph, Runboard, AI Kanban, Corpus Search, Patch Review Queue, Visualizations, Whiteboard, Mind Map, PDF Intake, AI Diagram Studio, Video Studio, Research Agent, New Research Topic, Skills Manager, OpenAPI Routing, Manim Sandbox, Settings.","Repurpose here means mining for specific modules, algorithms, UI patterns, ingestion logic, workflow ideas, or export formats rather than assuming a full product transplant.",native/scriptoriumai-ui,native/ScriptoriumAI-Server,abhigyanpatwari/GitNexus,"Return concrete files/modules/adapters worth reusing and a verdict on whether the current reanchored bucket should be kept, upgraded, or downgraded.",Do not treat licensing as a filter. Do not propose replacing native foundations unless source evidence is overwhelming.,dotnet/templating,v6_unified_source_of_truth_pack,"Before recommending direct code use, inspect the target repo row in the v6.1 operational/phase/source-audit boards. Respect copyleft_strategy_v6_1, preferred_boundary_model_v6_1, and open_compliance_if_used_as_is_v6_1. Do not assume reverse engineering is mandatory or that as-is use is always sensible.","If the repo-level strategy says bounded_sidecar_preferred or boundary_first_then_decide_as_is_vs_reimplementation, audit clean interfaces, protocol seams, subprocess/container boundaries, and what would be required to reimplement only the strategically necessary portions.",v6.3_final_source_of_truth
SCR_0178,,,,,,,,,,ScriptoriumAI repo packet,ScriptoriumAI,ScriptoriumAI re-anchored VS Code packets v1,enter-tainer/manim-typst,enter-tainer/manim-typst,Candidate Bench,P3,bookmark candidate only,"Audit enter-tainer/manim-typst for ScriptoriumAI. Start from the reanchored bucket 'Candidate Bench' and current reality status 'bookmark candidate only'. Confirm actual implemented capability, hidden reusable modules, extension seams, and whether it strengthens the existing Unimplemented but relevant candidate lane. Focus on: Inspect hidden modules, extension seams, data contracts, rendering paths, auth/storage coupling, and export/import boundaries.",,"Treat as unimplemented ScriptoriumAI candidate only. Do not let it redefine the current stack. Integrate only if a later audit proves it fills a real gap in the existing surfaces such as Dashboard, Editor, Corpus Graph, Runboard, AI Kanban, Corpus Search, Patch Review Queue, Visualizations, Whiteboard, Mind Map, PDF Intake, AI Diagram Studio, Video Studio, Research Agent, New Research Topic, Skills Manager, OpenAPI Routing, Manim Sandbox, Settings.","Repurpose here means mining for specific modules, algorithms, UI patterns, ingestion logic, workflow ideas, or export formats rather than assuming a full product transplant.",manimcommunity/manim,remotion-dev/remotion,native/ScriptoriumAI-Visualizer,"Return concrete files/modules/adapters worth reusing and a verdict on whether the current reanchored bucket should be kept, upgraded, or downgraded.",Do not treat licensing as a filter. Do not propose replacing native foundations unless source evidence is overwhelming.,enter-tainer/manim-typst,v6_unified_source_of_truth_pack,"Before recommending direct code use, inspect the target repo row in the v6.1 operational/phase/source-audit boards. Respect copyleft_strategy_v6_1, preferred_boundary_model_v6_1, and open_compliance_if_used_as_is_v6_1. Do not assume reverse engineering is mandatory or that as-is use is always sensible.","If the repo-level strategy says bounded_sidecar_preferred or boundary_first_then_decide_as_is_vs_reimplementation, audit clean interfaces, protocol seams, subprocess/container boundaries, and what would be required to reimplement only the strategically necessary portions.",v6.3_final_source_of_truth
SCR_0179,,,,,,,,,,ScriptoriumAI repo packet,ScriptoriumAI,ScriptoriumAI re-anchored VS Code packets v1,eriklindernoren/ML-From-Scratch,eriklindernoren/ml-from-scratch,Candidate Bench,P3,bookmark candidate only,"Audit eriklindernoren/ML-From-Scratch for ScriptoriumAI. Start from the reanchored bucket 'Candidate Bench' and current reality status 'bookmark candidate only'. Confirm actual implemented capability, hidden reusable modules, extension seams, and whether it strengthens the existing Unimplemented but relevant candidate lane. Focus on: 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 planner loops, tool registries, MCP servers/clients, prompt/skill folders, memory stores, approval gates, background-job orchestration, and undocumented provider adapters.","Treat as unimplemented ScriptoriumAI candidate only. Do not let it redefine the current stack. Integrate only if a later audit proves it fills a real gap in the existing surfaces such as Dashboard, Editor, Corpus Graph, Runboard, AI Kanban, Corpus Search, Patch Review Queue, Visualizations, Whiteboard, Mind Map, PDF Intake, AI Diagram Studio, Video Studio, Research Agent, New Research Topic, Skills Manager, OpenAPI Routing, Manim Sandbox, Settings.","Repurpose here means mining for specific modules, algorithms, UI patterns, ingestion logic, workflow ideas, or export formats rather than assuming a full product transplant.",native/scriptoriumai-ui,native/ScriptoriumAI-Server,abhigyanpatwari/GitNexus,"Return concrete files/modules/adapters worth reusing and a verdict on whether the current reanchored bucket should be kept, upgraded, or downgraded.",Do not treat licensing as a filter. Do not propose replacing native foundations unless source evidence is overwhelming.,eriklindernoren/ml-from-scratch,v6_unified_source_of_truth_pack,"Before recommending direct code use, inspect the target repo row in the v6.1 operational/phase/source-audit boards. Respect copyleft_strategy_v6_1, preferred_boundary_model_v6_1, and open_compliance_if_used_as_is_v6_1. Do not assume reverse engineering is mandatory or that as-is use is always sensible.","If the repo-level strategy says bounded_sidecar_preferred or boundary_first_then_decide_as_is_vs_reimplementation, audit clean interfaces, protocol seams, subprocess/container boundaries, and what would be required to reimplement only the strategically necessary portions.",v6.3_final_source_of_truth
SCR_0180,,,,,,,,,,ScriptoriumAI repo packet,ScriptoriumAI,ScriptoriumAI re-anchored VS Code packets v1,excalidraw/excalidraw-mcp,excalidraw/excalidraw-mcp,Candidate Bench,P3,bookmark candidate only,"Audit excalidraw/excalidraw-mcp for ScriptoriumAI. Start from the reanchored bucket 'Candidate Bench' and current reality status 'bookmark candidate only'. Confirm actual implemented capability, hidden reusable modules, extension seams, and whether it strengthens the existing Unimplemented but relevant candidate lane. Focus on: Inspect planner/task graph; provider abstraction; tool registry or MCP bridges; memory/state schema; approvals/retries; telemetry/event bus; plugin or skill loading 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 planner loops, tool registries, MCP servers/clients, prompt/skill folders, memory stores, approval gates, background-job orchestration, and undocumented provider adapters.","Treat as unimplemented ScriptoriumAI candidate only. Do not let it redefine the current stack. Integrate only if a later audit proves it fills a real gap in the existing surfaces such as Dashboard, Editor, Corpus Graph, Runboard, AI Kanban, Corpus Search, Patch Review Queue, Visualizations, Whiteboard, Mind Map, PDF Intake, AI Diagram Studio, Video Studio, Research Agent, New Research Topic, Skills Manager, OpenAPI Routing, Manim Sandbox, Settings.","Repurpose here means mining for specific modules, algorithms, UI patterns, ingestion logic, workflow ideas, or export formats rather than assuming a full product transplant.",native/scriptoriumai-ui,excalidraw/excalidraw,jgraph/drawio,"Return concrete files/modules/adapters worth reusing and a verdict on whether the current reanchored bucket should be kept, upgraded, or downgraded.",Do not treat licensing as a filter. Do not propose replacing native foundations unless source evidence is overwhelming.,excalidraw/excalidraw-mcp,v6_unified_source_of_truth_pack,"Before recommending direct code use, inspect the target repo row in the v6.1 operational/phase/source-audit boards. Respect copyleft_strategy_v6_1, preferred_boundary_model_v6_1, and open_compliance_if_used_as_is_v6_1. Do not assume reverse engineering is mandatory or that as-is use is always sensible.","If the repo-level strategy says bounded_sidecar_preferred or boundary_first_then_decide_as_is_vs_reimplementation, audit clean interfaces, protocol seams, subprocess/container boundaries, and what would be required to reimplement only the strategically necessary portions.",v6.3_final_source_of_truth
SCR_0181,,,,,,,,,,ScriptoriumAI repo packet,ScriptoriumAI,ScriptoriumAI re-anchored VS Code packets v1,facebook/zstd,facebook/zstd,Candidate Bench,P3,bookmark candidate only,"Audit facebook/zstd for ScriptoriumAI. Start from the reanchored bucket 'Candidate Bench' and current reality status 'bookmark candidate only'. Confirm actual implemented capability, hidden reusable modules, extension seams, and whether it strengthens the existing Unimplemented but relevant candidate lane. Focus on: Inspect parsers and language adapters; graph schema and storage; incremental indexing/update logic; layout engine; query API; export/import formats; test fixtures for graph correctness.","Inspect package manifests, README/docs, src tree, examples, tests, CI workflows, config files, migrations/schemas, and hidden feature flags or experimental modules. Look for hidden admin tools, reusable services, plugin systems, import/export, analytics, background jobs, and any engine more valuable than the public README suggests.","Treat as unimplemented ScriptoriumAI candidate only. Do not let it redefine the current stack. Integrate only if a later audit proves it fills a real gap in the existing surfaces such as Dashboard, Editor, Corpus Graph, Runboard, AI Kanban, Corpus Search, Patch Review Queue, Visualizations, Whiteboard, Mind Map, PDF Intake, AI Diagram Studio, Video Studio, Research Agent, New Research Topic, Skills Manager, OpenAPI Routing, Manim Sandbox, Settings.","Repurpose here means mining for specific modules, algorithms, UI patterns, ingestion logic, workflow ideas, or export formats rather than assuming a full product transplant.",native/scriptoriumai-ui,native/ScriptoriumAI-Server,abhigyanpatwari/GitNexus,"Return concrete files/modules/adapters worth reusing and a verdict on whether the current reanchored bucket should be kept, upgraded, or downgraded.",Do not treat licensing as a filter. Do not propose replacing native foundations unless source evidence is overwhelming.,facebook/zstd,v6_unified_source_of_truth_pack,"Before recommending direct code use, inspect the target repo row in the v6.1 operational/phase/source-audit boards. Respect copyleft_strategy_v6_1, preferred_boundary_model_v6_1, and open_compliance_if_used_as_is_v6_1. Do not assume reverse engineering is mandatory or that as-is use is always sensible.","If the repo-level strategy says bounded_sidecar_preferred or boundary_first_then_decide_as_is_vs_reimplementation, audit clean interfaces, protocol seams, subprocess/container boundaries, and what would be required to reimplement only the strategically necessary portions.",v6.3_final_source_of_truth
SCR_0182,,,,,,,,,,ScriptoriumAI repo packet,ScriptoriumAI,ScriptoriumAI re-anchored VS Code packets v1,filibusterer/manim-quantumcircuit,filibusterer/manim-quantumcircuit,Candidate Bench,P3,bookmark candidate only,"Audit filibusterer/manim-quantumcircuit for ScriptoriumAI. Start from the reanchored bucket 'Candidate Bench' and current reality status 'bookmark candidate only'. Confirm actual implemented capability, hidden reusable modules, extension seams, and whether it strengthens the existing Unimplemented but relevant candidate lane. Focus on: Inspect hidden modules, extension seams, data contracts, rendering paths, auth/storage coupling, and export/import boundaries.",,"Treat as unimplemented ScriptoriumAI candidate only. Do not let it redefine the current stack. Integrate only if a later audit proves it fills a real gap in the existing surfaces such as Dashboard, Editor, Corpus Graph, Runboard, AI Kanban, Corpus Search, Patch Review Queue, Visualizations, Whiteboard, Mind Map, PDF Intake, AI Diagram Studio, Video Studio, Research Agent, New Research Topic, Skills Manager, OpenAPI Routing, Manim Sandbox, Settings.","Repurpose here means mining for specific modules, algorithms, UI patterns, ingestion logic, workflow ideas, or export formats rather than assuming a full product transplant.",manimcommunity/manim,remotion-dev/remotion,native/ScriptoriumAI-Visualizer,"Return concrete files/modules/adapters worth reusing and a verdict on whether the current reanchored bucket should be kept, upgraded, or downgraded.",Do not treat licensing as a filter. Do not propose replacing native foundations unless source evidence is overwhelming.,filibusterer/manim-quantumcircuit,v6_unified_source_of_truth_pack,"Before recommending direct code use, inspect the target repo row in the v6.1 operational/phase/source-audit boards. Respect copyleft_strategy_v6_1, preferred_boundary_model_v6_1, and open_compliance_if_used_as_is_v6_1. Do not assume reverse engineering is mandatory or that as-is use is always sensible.","If the repo-level strategy says bounded_sidecar_preferred or boundary_first_then_decide_as_is_vs_reimplementation, audit clean interfaces, protocol seams, subprocess/container boundaries, and what would be required to reimplement only the strategically necessary portions.",v6.3_final_source_of_truth
SCR_0183,,,,,,,,,,ScriptoriumAI repo packet,ScriptoriumAI,ScriptoriumAI re-anchored VS Code packets v1,flodlol/PDF-Slides-to-Handouts-Converter,flodlol/pdf-slides-to-handouts-converter,Candidate Bench,P3,bookmark candidate only,"Audit flodlol/PDF-Slides-to-Handouts-Converter for ScriptoriumAI. Start from the reanchored bucket 'Candidate Bench' and current reality status 'bookmark candidate only'. Confirm actual implemented capability, hidden reusable modules, extension seams, and whether it strengthens the existing Unimplemented but relevant candidate lane. Focus on: Inspect document/block schema; sync/persistence model; permissions and sharing; citation/external-source pipeline; import/export adapters; plugin/extension points; editor rendering model.","Inspect package manifests, README/docs, src tree, examples, tests, CI workflows, config files, migrations/schemas, and hidden feature flags or experimental modules. Look for document/block schema, sync/conflict logic, citation handling, editor plugins, export/render pipeline, prompt chains, report assembly, and collaborative presence code.","Treat as unimplemented ScriptoriumAI candidate only. Do not let it redefine the current stack. Integrate only if a later audit proves it fills a real gap in the existing surfaces such as Dashboard, Editor, Corpus Graph, Runboard, AI Kanban, Corpus Search, Patch Review Queue, Visualizations, Whiteboard, Mind Map, PDF Intake, AI Diagram Studio, Video Studio, Research Agent, New Research Topic, Skills Manager, OpenAPI Routing, Manim Sandbox, Settings.","Repurpose here means mining for specific modules, algorithms, UI patterns, ingestion logic, workflow ideas, or export formats rather than assuming a full product transplant.",pdfmd/pdfmd,lukas-blecher/latex-ocr,mli55/pdfdelta,"Return concrete files/modules/adapters worth reusing and a verdict on whether the current reanchored bucket should be kept, upgraded, or downgraded.",Do not treat licensing as a filter. Do not propose replacing native foundations unless source evidence is overwhelming.,flodlol/pdf-slides-to-handouts-converter,v6_unified_source_of_truth_pack,"Before recommending direct code use, inspect the target repo row in the v6.1 operational/phase/source-audit boards. Respect copyleft_strategy_v6_1, preferred_boundary_model_v6_1, and open_compliance_if_used_as_is_v6_1. Do not assume reverse engineering is mandatory or that as-is use is always sensible.","If the repo-level strategy says bounded_sidecar_preferred or boundary_first_then_decide_as_is_vs_reimplementation, audit clean interfaces, protocol seams, subprocess/container boundaries, and what would be required to reimplement only the strategically necessary portions.",v6.3_final_source_of_truth
SCR_0184,,,,,,,,,,ScriptoriumAI repo packet,ScriptoriumAI,ScriptoriumAI re-anchored VS Code packets v1,furkan/dockerlings,furkan/dockerlings,Candidate Bench,P3,bookmark candidate only,"Audit furkan/dockerlings for ScriptoriumAI. Start from the reanchored bucket 'Candidate Bench' and current reality status 'bookmark candidate only'. Confirm actual implemented capability, hidden reusable modules, extension seams, and whether it strengthens the existing Unimplemented but relevant candidate lane. Focus on: 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 event schemas, ingestion pipelines, queue/job workers, service adapters, deployment/runtime config, RBAC/auth, alerting, and API contract generators.","Treat as unimplemented ScriptoriumAI candidate only. Do not let it redefine the current stack. Integrate only if a later audit proves it fills a real gap in the existing surfaces such as Dashboard, Editor, Corpus Graph, Runboard, AI Kanban, Corpus Search, Patch Review Queue, Visualizations, Whiteboard, Mind Map, PDF Intake, AI Diagram Studio, Video Studio, Research Agent, New Research Topic, Skills Manager, OpenAPI Routing, Manim Sandbox, Settings.","Repurpose here means mining for specific modules, algorithms, UI patterns, ingestion logic, workflow ideas, or export formats rather than assuming a full product transplant.",native/scriptoriumai-ui,native/ScriptoriumAI-Server,abhigyanpatwari/GitNexus,"Return concrete files/modules/adapters worth reusing and a verdict on whether the current reanchored bucket should be kept, upgraded, or downgraded.",Do not treat licensing as a filter. Do not propose replacing native foundations unless source evidence is overwhelming.,furkan/dockerlings,v6_unified_source_of_truth_pack,"Before recommending direct code use, inspect the target repo row in the v6.1 operational/phase/source-audit boards. Respect copyleft_strategy_v6_1, preferred_boundary_model_v6_1, and open_compliance_if_used_as_is_v6_1. Do not assume reverse engineering is mandatory or that as-is use is always sensible.","If the repo-level strategy says bounded_sidecar_preferred or boundary_first_then_decide_as_is_vs_reimplementation, audit clean interfaces, protocol seams, subprocess/container boundaries, and what would be required to reimplement only the strategically necessary portions.",v6.3_final_source_of_truth
SCR_0185,,,,,,,,,,ScriptoriumAI repo packet,ScriptoriumAI,ScriptoriumAI re-anchored VS Code packets v1,greensock/gsap-skills,greensock/gsap-skills,Candidate Bench,P3,bookmark candidate only,"Audit greensock/gsap-skills for ScriptoriumAI. Start from the reanchored bucket 'Candidate Bench' and current reality status 'bookmark candidate only'. Confirm actual implemented capability, hidden reusable modules, extension seams, and whether it strengthens the existing Unimplemented but relevant candidate lane. Focus on: Inspect planner/task graph; provider abstraction; tool registry or MCP bridges; memory/state schema; approvals/retries; telemetry/event bus; plugin or skill loading 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 planner loops, tool registries, MCP servers/clients, prompt/skill folders, memory stores, approval gates, background-job orchestration, and undocumented provider adapters.","Treat as unimplemented ScriptoriumAI candidate only. Do not let it redefine the current stack. Integrate only if a later audit proves it fills a real gap in the existing surfaces such as Dashboard, Editor, Corpus Graph, Runboard, AI Kanban, Corpus Search, Patch Review Queue, Visualizations, Whiteboard, Mind Map, PDF Intake, AI Diagram Studio, Video Studio, Research Agent, New Research Topic, Skills Manager, OpenAPI Routing, Manim Sandbox, Settings.","Repurpose here means mining for specific modules, algorithms, UI patterns, ingestion logic, workflow ideas, or export formats rather than assuming a full product transplant.",native/ScriptoriumAI-Server,stanford-oval/storm,abhigyanpatwari/GitNexus,"Return concrete files/modules/adapters worth reusing and a verdict on whether the current reanchored bucket should be kept, upgraded, or downgraded.",Do not treat licensing as a filter. Do not propose replacing native foundations unless source evidence is overwhelming.,greensock/gsap-skills,v6_unified_source_of_truth_pack,"Before recommending direct code use, inspect the target repo row in the v6.1 operational/phase/source-audit boards. Respect copyleft_strategy_v6_1, preferred_boundary_model_v6_1, and open_compliance_if_used_as_is_v6_1. Do not assume reverse engineering is mandatory or that as-is use is always sensible.","If the repo-level strategy says bounded_sidecar_preferred or boundary_first_then_decide_as_is_vs_reimplementation, audit clean interfaces, protocol seams, subprocess/container boundaries, and what would be required to reimplement only the strategically necessary portions.",v6.3_final_source_of_truth
SCR_0186,,,,,,,,,,ScriptoriumAI repo packet,ScriptoriumAI,ScriptoriumAI re-anchored VS Code packets v1,helblazer811/manimml,helblazer811/manimml,Candidate Bench,P3,bookmark candidate only,"Audit helblazer811/manimml for ScriptoriumAI. Start from the reanchored bucket 'Candidate Bench' and current reality status 'bookmark candidate only'. Confirm actual implemented capability, hidden reusable modules, extension seams, and whether it strengthens the existing Unimplemented but relevant candidate lane. Focus on: Inspect hidden modules, extension seams, data contracts, rendering paths, auth/storage coupling, and export/import boundaries.",,"Treat as unimplemented ScriptoriumAI candidate only. Do not let it redefine the current stack. Integrate only if a later audit proves it fills a real gap in the existing surfaces such as Dashboard, Editor, Corpus Graph, Runboard, AI Kanban, Corpus Search, Patch Review Queue, Visualizations, Whiteboard, Mind Map, PDF Intake, AI Diagram Studio, Video Studio, Research Agent, New Research Topic, Skills Manager, OpenAPI Routing, Manim Sandbox, Settings.","Repurpose here means mining for specific modules, algorithms, UI patterns, ingestion logic, workflow ideas, or export formats rather than assuming a full product transplant.",manimcommunity/manim,remotion-dev/remotion,native/ScriptoriumAI-Visualizer,"Return concrete files/modules/adapters worth reusing and a verdict on whether the current reanchored bucket should be kept, upgraded, or downgraded.",Do not treat licensing as a filter. Do not propose replacing native foundations unless source evidence is overwhelming.,helblazer811/manimml,v6_unified_source_of_truth_pack,"Before recommending direct code use, inspect the target repo row in the v6.1 operational/phase/source-audit boards. Respect copyleft_strategy_v6_1, preferred_boundary_model_v6_1, and open_compliance_if_used_as_is_v6_1. Do not assume reverse engineering is mandatory or that as-is use is always sensible.","If the repo-level strategy says bounded_sidecar_preferred or boundary_first_then_decide_as_is_vs_reimplementation, audit clean interfaces, protocol seams, subprocess/container boundaries, and what would be required to reimplement only the strategically necessary portions.",v6.3_final_source_of_truth
SCR_0187,,,,,,,,,,ScriptoriumAI repo packet,ScriptoriumAI,ScriptoriumAI re-anchored VS Code packets v1,hkuds/ai-researcher,hkuds/ai-researcher,Candidate Bench,P3,not in implemented architecture snapshot,"Audit hkuds/ai-researcher for ScriptoriumAI. Start from the reanchored bucket 'Candidate Bench' and current reality status 'not in implemented architecture snapshot'. Confirm actual implemented capability, hidden reusable modules, extension seams, and whether it strengthens the existing Research-generation candidate lane. Focus on: Inspect planner/task graph; provider abstraction; tool registry or MCP bridges; memory/state schema; approvals/retries; telemetry/event bus; plugin or skill loading 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 planner loops, tool registries, MCP servers/clients, prompt/skill folders, memory stores, approval gates, background-job orchestration, and undocumented provider adapters.","Treat as unimplemented ScriptoriumAI candidate only. Do not let it redefine the current stack. Integrate only if a later audit proves it fills a real gap in the existing surfaces such as Dashboard, Editor, Corpus Graph, Runboard, AI Kanban, Corpus Search, Patch Review Queue, Visualizations, Whiteboard, Mind Map, PDF Intake, AI Diagram Studio, Video Studio, Research Agent, New Research Topic, Skills Manager, OpenAPI Routing, Manim Sandbox, Settings.","Repurpose here means mining for specific modules, algorithms, UI patterns, ingestion logic, workflow ideas, or export formats rather than assuming a full product transplant.",native/ScriptoriumAI-Server,stanford-oval/storm,abhigyanpatwari/GitNexus,"Return concrete files/modules/adapters worth reusing and a verdict on whether the current reanchored bucket should be kept, upgraded, or downgraded.",Do not treat licensing as a filter. Do not propose replacing native foundations unless source evidence is overwhelming.,hkuds/ai-researcher,v6_unified_source_of_truth_pack,"Before recommending direct code use, inspect the target repo row in the v6.1 operational/phase/source-audit boards. Respect copyleft_strategy_v6_1, preferred_boundary_model_v6_1, and open_compliance_if_used_as_is_v6_1. Do not assume reverse engineering is mandatory or that as-is use is always sensible.","If the repo-level strategy says bounded_sidecar_preferred or boundary_first_then_decide_as_is_vs_reimplementation, audit clean interfaces, protocol seams, subprocess/container boundaries, and what would be required to reimplement only the strategically necessary portions.",v6.3_final_source_of_truth
SCR_0188,,,,,,,,,,ScriptoriumAI repo packet,ScriptoriumAI,ScriptoriumAI re-anchored VS Code packets v1,isaac-dabkowski/manim-sequence-diagram,isaac-dabkowski/manim-sequence-diagram,Candidate Bench,P3,bookmark candidate only,"Audit isaac-dabkowski/manim-sequence-diagram for ScriptoriumAI. Start from the reanchored bucket 'Candidate Bench' and current reality status 'bookmark candidate only'. Confirm actual implemented capability, hidden reusable modules, extension seams, and whether it strengthens the existing Unimplemented but relevant candidate lane. Focus on: Inspect hidden modules, extension seams, data contracts, rendering paths, auth/storage coupling, and export/import boundaries.",,"Treat as unimplemented ScriptoriumAI candidate only. Do not let it redefine the current stack. Integrate only if a later audit proves it fills a real gap in the existing surfaces such as Dashboard, Editor, Corpus Graph, Runboard, AI Kanban, Corpus Search, Patch Review Queue, Visualizations, Whiteboard, Mind Map, PDF Intake, AI Diagram Studio, Video Studio, Research Agent, New Research Topic, Skills Manager, OpenAPI Routing, Manim Sandbox, Settings.","Repurpose here means mining for specific modules, algorithms, UI patterns, ingestion logic, workflow ideas, or export formats rather than assuming a full product transplant.",manimcommunity/manim,remotion-dev/remotion,native/ScriptoriumAI-Visualizer,"Return concrete files/modules/adapters worth reusing and a verdict on whether the current reanchored bucket should be kept, upgraded, or downgraded.",Do not treat licensing as a filter. Do not propose replacing native foundations unless source evidence is overwhelming.,isaac-dabkowski/manim-sequence-diagram,v6_unified_source_of_truth_pack,"Before recommending direct code use, inspect the target repo row in the v6.1 operational/phase/source-audit boards. Respect copyleft_strategy_v6_1, preferred_boundary_model_v6_1, and open_compliance_if_used_as_is_v6_1. Do not assume reverse engineering is mandatory or that as-is use is always sensible.","If the repo-level strategy says bounded_sidecar_preferred or boundary_first_then_decide_as_is_vs_reimplementation, audit clean interfaces, protocol seams, subprocess/container boundaries, and what would be required to reimplement only the strategically necessary portions.",v6.3_final_source_of_truth
SCR_0189,,,,,,,,,,ScriptoriumAI repo packet,ScriptoriumAI,ScriptoriumAI re-anchored VS Code packets v1,isaacabraham/get-programming-fsharp,isaacabraham/get-programming-fsharp,Candidate Bench,P3,bookmark candidate only,"Audit isaacabraham/get-programming-fsharp for ScriptoriumAI. Start from the reanchored bucket 'Candidate Bench' and current reality status 'bookmark candidate only'. Confirm actual implemented capability, hidden reusable modules, extension seams, and whether it strengthens the existing Unimplemented but relevant candidate lane. Focus on: Inspect package/module map; entrypoints; config and schema files; adapters/integrations; persistence model; tests/examples; hidden feature flags; plugin 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 hidden admin tools, reusable services, plugin systems, import/export, analytics, background jobs, and any engine more valuable than the public README suggests.","Treat as unimplemented ScriptoriumAI candidate only. Do not let it redefine the current stack. Integrate only if a later audit proves it fills a real gap in the existing surfaces such as Dashboard, Editor, Corpus Graph, Runboard, AI Kanban, Corpus Search, Patch Review Queue, Visualizations, Whiteboard, Mind Map, PDF Intake, AI Diagram Studio, Video Studio, Research Agent, New Research Topic, Skills Manager, OpenAPI Routing, Manim Sandbox, Settings.","Repurpose here means mining for specific modules, algorithms, UI patterns, ingestion logic, workflow ideas, or export formats rather than assuming a full product transplant.",native/scriptoriumai-ui,native/ScriptoriumAI-Server,abhigyanpatwari/GitNexus,"Return concrete files/modules/adapters worth reusing and a verdict on whether the current reanchored bucket should be kept, upgraded, or downgraded.",Do not treat licensing as a filter. Do not propose replacing native foundations unless source evidence is overwhelming.,isaacabraham/get-programming-fsharp,v6_unified_source_of_truth_pack,"Before recommending direct code use, inspect the target repo row in the v6.1 operational/phase/source-audit boards. Respect copyleft_strategy_v6_1, preferred_boundary_model_v6_1, and open_compliance_if_used_as_is_v6_1. Do not assume reverse engineering is mandatory or that as-is use is always sensible.","If the repo-level strategy says bounded_sidecar_preferred or boundary_first_then_decide_as_is_vs_reimplementation, audit clean interfaces, protocol seams, subprocess/container boundaries, and what would be required to reimplement only the strategically necessary portions.",v6.3_final_source_of_truth
SCR_0190,,,,,,,,,,ScriptoriumAI repo packet,ScriptoriumAI,ScriptoriumAI re-anchored VS Code packets v1,jeertmans/manim-slides,jeertmans/manim-slides,Candidate Bench,P3,bookmark candidate only,"Audit jeertmans/manim-slides for ScriptoriumAI. Start from the reanchored bucket 'Candidate Bench' and current reality status 'bookmark candidate only'. Confirm actual implemented capability, hidden reusable modules, extension seams, and whether it strengthens the existing Unimplemented but relevant candidate lane. Focus on: Inspect hidden modules, extension seams, data contracts, rendering paths, auth/storage coupling, and export/import boundaries.",,"Treat as unimplemented ScriptoriumAI candidate only. Do not let it redefine the current stack. Integrate only if a later audit proves it fills a real gap in the existing surfaces such as Dashboard, Editor, Corpus Graph, Runboard, AI Kanban, Corpus Search, Patch Review Queue, Visualizations, Whiteboard, Mind Map, PDF Intake, AI Diagram Studio, Video Studio, Research Agent, New Research Topic, Skills Manager, OpenAPI Routing, Manim Sandbox, Settings.","Repurpose here means mining for specific modules, algorithms, UI patterns, ingestion logic, workflow ideas, or export formats rather than assuming a full product transplant.",manimcommunity/manim,remotion-dev/remotion,native/ScriptoriumAI-Visualizer,"Return concrete files/modules/adapters worth reusing and a verdict on whether the current reanchored bucket should be kept, upgraded, or downgraded.",Do not treat licensing as a filter. Do not propose replacing native foundations unless source evidence is overwhelming.,jeertmans/manim-slides,v6_unified_source_of_truth_pack,"Before recommending direct code use, inspect the target repo row in the v6.1 operational/phase/source-audit boards. Respect copyleft_strategy_v6_1, preferred_boundary_model_v6_1, and open_compliance_if_used_as_is_v6_1. Do not assume reverse engineering is mandatory or that as-is use is always sensible.","If the repo-level strategy says bounded_sidecar_preferred or boundary_first_then_decide_as_is_vs_reimplementation, audit clean interfaces, protocol seams, subprocess/container boundaries, and what would be required to reimplement only the strategically necessary portions.",v6.3_final_source_of_truth
SCR_0191,,,,,,,,,,ScriptoriumAI repo packet,ScriptoriumAI,ScriptoriumAI re-anchored VS Code packets v1,jsakamoto/BlazingStory,jsakamoto/blazingstory,Candidate Bench,P3,bookmark candidate only,"Audit jsakamoto/BlazingStory for ScriptoriumAI. Start from the reanchored bucket 'Candidate Bench' and current reality status 'bookmark candidate only'. Confirm actual implemented capability, hidden reusable modules, extension seams, and whether it strengthens the existing Unimplemented but relevant candidate lane. Focus on: 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.","Treat as unimplemented ScriptoriumAI candidate only. Do not let it redefine the current stack. Integrate only if a later audit proves it fills a real gap in the existing surfaces such as Dashboard, Editor, Corpus Graph, Runboard, AI Kanban, Corpus Search, Patch Review Queue, Visualizations, Whiteboard, Mind Map, PDF Intake, AI Diagram Studio, Video Studio, Research Agent, New Research Topic, Skills Manager, OpenAPI Routing, Manim Sandbox, Settings.","Repurpose here means mining for specific modules, algorithms, UI patterns, ingestion logic, workflow ideas, or export formats rather than assuming a full product transplant.",native/scriptoriumai-ui,native/ScriptoriumAI-Server,abhigyanpatwari/GitNexus,"Return concrete files/modules/adapters worth reusing and a verdict on whether the current reanchored bucket should be kept, upgraded, or downgraded.",Do not treat licensing as a filter. Do not propose replacing native foundations unless source evidence is overwhelming.,jsakamoto/blazingstory,v6_unified_source_of_truth_pack,"Before recommending direct code use, inspect the target repo row in the v6.1 operational/phase/source-audit boards. Respect copyleft_strategy_v6_1, preferred_boundary_model_v6_1, and open_compliance_if_used_as_is_v6_1. Do not assume reverse engineering is mandatory or that as-is use is always sensible.","If the repo-level strategy says bounded_sidecar_preferred or boundary_first_then_decide_as_is_vs_reimplementation, audit clean interfaces, protocol seams, subprocess/container boundaries, and what would be required to reimplement only the strategically necessary portions.",v6.3_final_source_of_truth
SCR_0192,,,,,,,,,,ScriptoriumAI repo packet,ScriptoriumAI,ScriptoriumAI re-anchored VS Code packets v1,juanjosalvador/manim-pptx,juanjosalvador/manim-pptx,Candidate Bench,P3,bookmark candidate only,"Audit juanjosalvador/manim-pptx for ScriptoriumAI. Start from the reanchored bucket 'Candidate Bench' and current reality status 'bookmark candidate only'. Confirm actual implemented capability, hidden reusable modules, extension seams, and whether it strengthens the existing Unimplemented but relevant candidate lane. Focus on: Inspect hidden modules, extension seams, data contracts, rendering paths, auth/storage coupling, and export/import boundaries.",,"Treat as unimplemented ScriptoriumAI candidate only. Do not let it redefine the current stack. Integrate only if a later audit proves it fills a real gap in the existing surfaces such as Dashboard, Editor, Corpus Graph, Runboard, AI Kanban, Corpus Search, Patch Review Queue, Visualizations, Whiteboard, Mind Map, PDF Intake, AI Diagram Studio, Video Studio, Research Agent, New Research Topic, Skills Manager, OpenAPI Routing, Manim Sandbox, Settings.","Repurpose here means mining for specific modules, algorithms, UI patterns, ingestion logic, workflow ideas, or export formats rather than assuming a full product transplant.",manimcommunity/manim,remotion-dev/remotion,native/ScriptoriumAI-Visualizer,"Return concrete files/modules/adapters worth reusing and a verdict on whether the current reanchored bucket should be kept, upgraded, or downgraded.",Do not treat licensing as a filter. Do not propose replacing native foundations unless source evidence is overwhelming.,juanjosalvador/manim-pptx,v6_unified_source_of_truth_pack,"Before recommending direct code use, inspect the target repo row in the v6.1 operational/phase/source-audit boards. Respect copyleft_strategy_v6_1, preferred_boundary_model_v6_1, and open_compliance_if_used_as_is_v6_1. Do not assume reverse engineering is mandatory or that as-is use is always sensible.","If the repo-level strategy says bounded_sidecar_preferred or boundary_first_then_decide_as_is_vs_reimplementation, audit clean interfaces, protocol seams, subprocess/container boundaries, and what would be required to reimplement only the strategically necessary portions.",v6.3_final_source_of_truth
SCR_0193,,,,,,,,,,ScriptoriumAI repo packet,ScriptoriumAI,ScriptoriumAI re-anchored VS Code packets v1,karpathy/autoresearch,karpathy/autoresearch,Candidate Bench,P3,bookmark candidate only,"Audit karpathy/autoresearch for ScriptoriumAI. Start from the reanchored bucket 'Candidate Bench' and current reality status 'bookmark candidate only'. Confirm actual implemented capability, hidden reusable modules, extension seams, and whether it strengthens the existing Unimplemented but relevant candidate lane. Focus on: Inspect planner/task graph; provider abstraction; tool registry or MCP bridges; memory/state schema; approvals/retries; telemetry/event bus; plugin or skill loading 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 planner loops, tool registries, MCP servers/clients, prompt/skill folders, memory stores, approval gates, background-job orchestration, and undocumented provider adapters.","Treat as unimplemented ScriptoriumAI candidate only. Do not let it redefine the current stack. Integrate only if a later audit proves it fills a real gap in the existing surfaces such as Dashboard, Editor, Corpus Graph, Runboard, AI Kanban, Corpus Search, Patch Review Queue, Visualizations, Whiteboard, Mind Map, PDF Intake, AI Diagram Studio, Video Studio, Research Agent, New Research Topic, Skills Manager, OpenAPI Routing, Manim Sandbox, Settings.","Repurpose here means mining for specific modules, algorithms, UI patterns, ingestion logic, workflow ideas, or export formats rather than assuming a full product transplant.",native/ScriptoriumAI-Server,stanford-oval/storm,abhigyanpatwari/GitNexus,"Return concrete files/modules/adapters worth reusing and a verdict on whether the current reanchored bucket should be kept, upgraded, or downgraded.",Do not treat licensing as a filter. Do not propose replacing native foundations unless source evidence is overwhelming.,karpathy/autoresearch,v6_unified_source_of_truth_pack,"Before recommending direct code use, inspect the target repo row in the v6.1 operational/phase/source-audit boards. Respect copyleft_strategy_v6_1, preferred_boundary_model_v6_1, and open_compliance_if_used_as_is_v6_1. Do not assume reverse engineering is mandatory or that as-is use is always sensible.","If the repo-level strategy says bounded_sidecar_preferred or boundary_first_then_decide_as_is_vs_reimplementation, audit clean interfaces, protocol seams, subprocess/container boundaries, and what would be required to reimplement only the strategically necessary portions.",v6.3_final_source_of_truth
SCR_0194,,,,,,,,,,ScriptoriumAI repo packet,ScriptoriumAI,ScriptoriumAI re-anchored VS Code packets v1,karpathy/reader3,karpathy/reader3,Candidate Bench,P3,bookmark candidate only,"Audit karpathy/reader3 for ScriptoriumAI. Start from the reanchored bucket 'Candidate Bench' and current reality status 'bookmark candidate only'. Confirm actual implemented capability, hidden reusable modules, extension seams, and whether it strengthens the existing Unimplemented but relevant candidate lane. Focus on: Inspect planner/task graph; provider abstraction; tool registry or MCP bridges; memory/state schema; approvals/retries; telemetry/event bus; plugin or skill loading 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 planner loops, tool registries, MCP servers/clients, prompt/skill folders, memory stores, approval gates, background-job orchestration, and undocumented provider adapters.","Treat as unimplemented ScriptoriumAI candidate only. Do not let it redefine the current stack. Integrate only if a later audit proves it fills a real gap in the existing surfaces such as Dashboard, Editor, Corpus Graph, Runboard, AI Kanban, Corpus Search, Patch Review Queue, Visualizations, Whiteboard, Mind Map, PDF Intake, AI Diagram Studio, Video Studio, Research Agent, New Research Topic, Skills Manager, OpenAPI Routing, Manim Sandbox, Settings.","Repurpose here means mining for specific modules, algorithms, UI patterns, ingestion logic, workflow ideas, or export formats rather than assuming a full product transplant.",native/scriptoriumai-ui,native/ScriptoriumAI-Server,abhigyanpatwari/GitNexus,"Return concrete files/modules/adapters worth reusing and a verdict on whether the current reanchored bucket should be kept, upgraded, or downgraded.",Do not treat licensing as a filter. Do not propose replacing native foundations unless source evidence is overwhelming.,karpathy/reader3,v6_unified_source_of_truth_pack,"Before recommending direct code use, inspect the target repo row in the v6.1 operational/phase/source-audit boards. Respect copyleft_strategy_v6_1, preferred_boundary_model_v6_1, and open_compliance_if_used_as_is_v6_1. Do not assume reverse engineering is mandatory or that as-is use is always sensible.","If the repo-level strategy says bounded_sidecar_preferred or boundary_first_then_decide_as_is_vs_reimplementation, audit clean interfaces, protocol seams, subprocess/container boundaries, and what would be required to reimplement only the strategically necessary portions.",v6.3_final_source_of_truth
SCR_0195,,,,,,,,,,ScriptoriumAI repo packet,ScriptoriumAI,ScriptoriumAI re-anchored VS Code packets v1,kreuzberg-dev/kreuzberg,kreuzberg-dev/kreuzberg,Candidate Bench,P3,bookmark candidate only,"Audit kreuzberg-dev/kreuzberg for ScriptoriumAI. Start from the reanchored bucket 'Candidate Bench' and current reality status 'bookmark candidate only'. Confirm actual implemented capability, hidden reusable modules, extension seams, and whether it strengthens the existing Unimplemented but relevant candidate lane. Focus on: 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.","Treat as unimplemented ScriptoriumAI candidate only. Do not let it redefine the current stack. Integrate only if a later audit proves it fills a real gap in the existing surfaces such as Dashboard, Editor, Corpus Graph, Runboard, AI Kanban, Corpus Search, Patch Review Queue, Visualizations, Whiteboard, Mind Map, PDF Intake, AI Diagram Studio, Video Studio, Research Agent, New Research Topic, Skills Manager, OpenAPI Routing, Manim Sandbox, Settings.","Repurpose here means mining for specific modules, algorithms, UI patterns, ingestion logic, workflow ideas, or export formats rather than assuming a full product transplant.",pdfmd/pdfmd,lukas-blecher/latex-ocr,mli55/pdfdelta,"Return concrete files/modules/adapters worth reusing and a verdict on whether the current reanchored bucket should be kept, upgraded, or downgraded.",Do not treat licensing as a filter. Do not propose replacing native foundations unless source evidence is overwhelming.,kreuzberg-dev/kreuzberg,v6_unified_source_of_truth_pack,"Before recommending direct code use, inspect the target repo row in the v6.1 operational/phase/source-audit boards. Respect copyleft_strategy_v6_1, preferred_boundary_model_v6_1, and open_compliance_if_used_as_is_v6_1. Do not assume reverse engineering is mandatory or that as-is use is always sensible.","If the repo-level strategy says bounded_sidecar_preferred or boundary_first_then_decide_as_is_vs_reimplementation, audit clean interfaces, protocol seams, subprocess/container boundaries, and what would be required to reimplement only the strategically necessary portions.",v6.3_final_source_of_truth
SCR_0196,,,,,,,,,,ScriptoriumAI repo packet,ScriptoriumAI,ScriptoriumAI re-anchored VS Code packets v1,labarba/sciwrite,labarba/sciwrite,Candidate Bench,P3,bookmark candidate only,"Audit labarba/sciwrite for ScriptoriumAI. Start from the reanchored bucket 'Candidate Bench' and current reality status 'bookmark candidate only'. Confirm actual implemented capability, hidden reusable modules, extension seams, and whether it strengthens the existing Unimplemented but relevant candidate lane. Focus on: Inspect planner/task graph; provider abstraction; tool registry or MCP bridges; memory/state schema; approvals/retries; telemetry/event bus; plugin or skill loading 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 planner loops, tool registries, MCP servers/clients, prompt/skill folders, memory stores, approval gates, background-job orchestration, and undocumented provider adapters.","Treat as unimplemented ScriptoriumAI candidate only. Do not let it redefine the current stack. Integrate only if a later audit proves it fills a real gap in the existing surfaces such as Dashboard, Editor, Corpus Graph, Runboard, AI Kanban, Corpus Search, Patch Review Queue, Visualizations, Whiteboard, Mind Map, PDF Intake, AI Diagram Studio, Video Studio, Research Agent, New Research Topic, Skills Manager, OpenAPI Routing, Manim Sandbox, Settings.","Repurpose here means mining for specific modules, algorithms, UI patterns, ingestion logic, workflow ideas, or export formats rather than assuming a full product transplant.",native/ScriptoriumAI-Server,stanford-oval/storm,abhigyanpatwari/GitNexus,"Return concrete files/modules/adapters worth reusing and a verdict on whether the current reanchored bucket should be kept, upgraded, or downgraded.",Do not treat licensing as a filter. Do not propose replacing native foundations unless source evidence is overwhelming.,labarba/sciwrite,v6_unified_source_of_truth_pack,"Before recommending direct code use, inspect the target repo row in the v6.1 operational/phase/source-audit boards. Respect copyleft_strategy_v6_1, preferred_boundary_model_v6_1, and open_compliance_if_used_as_is_v6_1. Do not assume reverse engineering is mandatory or that as-is use is always sensible.","If the repo-level strategy says bounded_sidecar_preferred or boundary_first_then_decide_as_is_vs_reimplementation, audit clean interfaces, protocol seams, subprocess/container boundaries, and what would be required to reimplement only the strategically necessary portions.",v6.3_final_source_of_truth
SCR_0197,,,,,,,,,,ScriptoriumAI repo packet,ScriptoriumAI,ScriptoriumAI re-anchored VS Code packets v1,leleogere/manim-algorithm,leleogere/manim-algorithm,Candidate Bench,P3,bookmark candidate only,"Audit leleogere/manim-algorithm for ScriptoriumAI. Start from the reanchored bucket 'Candidate Bench' and current reality status 'bookmark candidate only'. Confirm actual implemented capability, hidden reusable modules, extension seams, and whether it strengthens the existing Unimplemented but relevant candidate lane. Focus on: Inspect hidden modules, extension seams, data contracts, rendering paths, auth/storage coupling, and export/import boundaries.",,"Treat as unimplemented ScriptoriumAI candidate only. Do not let it redefine the current stack. Integrate only if a later audit proves it fills a real gap in the existing surfaces such as Dashboard, Editor, Corpus Graph, Runboard, AI Kanban, Corpus Search, Patch Review Queue, Visualizations, Whiteboard, Mind Map, PDF Intake, AI Diagram Studio, Video Studio, Research Agent, New Research Topic, Skills Manager, OpenAPI Routing, Manim Sandbox, Settings.","Repurpose here means mining for specific modules, algorithms, UI patterns, ingestion logic, workflow ideas, or export formats rather than assuming a full product transplant.",manimcommunity/manim,remotion-dev/remotion,native/ScriptoriumAI-Visualizer,"Return concrete files/modules/adapters worth reusing and a verdict on whether the current reanchored bucket should be kept, upgraded, or downgraded.",Do not treat licensing as a filter. Do not propose replacing native foundations unless source evidence is overwhelming.,leleogere/manim-algorithm,v6_unified_source_of_truth_pack,"Before recommending direct code use, inspect the target repo row in the v6.1 operational/phase/source-audit boards. Respect copyleft_strategy_v6_1, preferred_boundary_model_v6_1, and open_compliance_if_used_as_is_v6_1. Do not assume reverse engineering is mandatory or that as-is use is always sensible.","If the repo-level strategy says bounded_sidecar_preferred or boundary_first_then_decide_as_is_vs_reimplementation, audit clean interfaces, protocol seams, subprocess/container boundaries, and what would be required to reimplement only the strategically necessary portions.",v6.3_final_source_of_truth
SCR_0198,,,,,,,,,,ScriptoriumAI repo packet,ScriptoriumAI,ScriptoriumAI re-anchored VS Code packets v1,libpdf-js/core,libpdf-js/core,Candidate Bench,P3,bookmark candidate only,"Audit libpdf-js/core for ScriptoriumAI. Start from the reanchored bucket 'Candidate Bench' and current reality status 'bookmark candidate only'. Confirm actual implemented capability, hidden reusable modules, extension seams, and whether it strengthens the existing Unimplemented but relevant candidate lane. Focus on: Inspect document/block schema; sync/persistence model; permissions and sharing; citation/external-source pipeline; import/export adapters; plugin/extension points; editor rendering model.","Inspect package manifests, README/docs, src tree, examples, tests, CI workflows, config files, migrations/schemas, and hidden feature flags or experimental modules. Look for event schemas, ingestion pipelines, queue/job workers, service adapters, deployment/runtime config, RBAC/auth, alerting, and API contract generators.","Treat as unimplemented ScriptoriumAI candidate only. Do not let it redefine the current stack. Integrate only if a later audit proves it fills a real gap in the existing surfaces such as Dashboard, Editor, Corpus Graph, Runboard, AI Kanban, Corpus Search, Patch Review Queue, Visualizations, Whiteboard, Mind Map, PDF Intake, AI Diagram Studio, Video Studio, Research Agent, New Research Topic, Skills Manager, OpenAPI Routing, Manim Sandbox, Settings.","Repurpose here means mining for specific modules, algorithms, UI patterns, ingestion logic, workflow ideas, or export formats rather than assuming a full product transplant.",pdfmd/pdfmd,lukas-blecher/latex-ocr,mli55/pdfdelta,"Return concrete files/modules/adapters worth reusing and a verdict on whether the current reanchored bucket should be kept, upgraded, or downgraded.",Do not treat licensing as a filter. Do not propose replacing native foundations unless source evidence is overwhelming.,libpdf-js/core,v6_unified_source_of_truth_pack,"Before recommending direct code use, inspect the target repo row in the v6.1 operational/phase/source-audit boards. Respect copyleft_strategy_v6_1, preferred_boundary_model_v6_1, and open_compliance_if_used_as_is_v6_1. Do not assume reverse engineering is mandatory or that as-is use is always sensible.","If the repo-level strategy says bounded_sidecar_preferred or boundary_first_then_decide_as_is_vs_reimplementation, audit clean interfaces, protocol seams, subprocess/container boundaries, and what would be required to reimplement only the strategically necessary portions.",v6.3_final_source_of_truth
SCR_0199,,,,,,,,,,ScriptoriumAI repo packet,ScriptoriumAI,ScriptoriumAI re-anchored VS Code packets v1,liujuntao123/smart-excalidraw-next,liujuntao123/smart-excalidraw-next,Candidate Bench,P3,bookmark candidate only,"Audit liujuntao123/smart-excalidraw-next for ScriptoriumAI. Start from the reanchored bucket 'Candidate Bench' and current reality status 'bookmark candidate only'. Confirm actual implemented capability, hidden reusable modules, extension seams, and whether it strengthens the existing Unimplemented but relevant candidate lane. Focus on: Inspect document/block schema; sync/persistence model; permissions and sharing; citation/external-source pipeline; import/export adapters; plugin/extension points; editor rendering model.","Inspect package manifests, README/docs, src tree, examples, tests, CI workflows, config files, migrations/schemas, and hidden feature flags or experimental modules. Look for document/block schema, sync/conflict logic, citation handling, editor plugins, export/render pipeline, prompt chains, report assembly, and collaborative presence code.","Treat as unimplemented ScriptoriumAI candidate only. Do not let it redefine the current stack. Integrate only if a later audit proves it fills a real gap in the existing surfaces such as Dashboard, Editor, Corpus Graph, Runboard, AI Kanban, Corpus Search, Patch Review Queue, Visualizations, Whiteboard, Mind Map, PDF Intake, AI Diagram Studio, Video Studio, Research Agent, New Research Topic, Skills Manager, OpenAPI Routing, Manim Sandbox, Settings.","Repurpose here means mining for specific modules, algorithms, UI patterns, ingestion logic, workflow ideas, or export formats rather than assuming a full product transplant.",native/scriptoriumai-ui,excalidraw/excalidraw,jgraph/drawio,"Return concrete files/modules/adapters worth reusing and a verdict on whether the current reanchored bucket should be kept, upgraded, or downgraded.",Do not treat licensing as a filter. Do not propose replacing native foundations unless source evidence is overwhelming.,liujuntao123/smart-excalidraw-next,v6_unified_source_of_truth_pack,"Before recommending direct code use, inspect the target repo row in the v6.1 operational/phase/source-audit boards. Respect copyleft_strategy_v6_1, preferred_boundary_model_v6_1, and open_compliance_if_used_as_is_v6_1. Do not assume reverse engineering is mandatory or that as-is use is always sensible.","If the repo-level strategy says bounded_sidecar_preferred or boundary_first_then_decide_as_is_vs_reimplementation, audit clean interfaces, protocol seams, subprocess/container boundaries, and what would be required to reimplement only the strategically necessary portions.",v6.3_final_source_of_truth
SCR_0200,,,,,,,,,,ScriptoriumAI repo packet,ScriptoriumAI,ScriptoriumAI re-anchored VS Code packets v1,ltjed/freephdlabor,ltjed/freephdlabor,Candidate Bench,P3,bookmark candidate only,"Audit ltjed/freephdlabor for ScriptoriumAI. Start from the reanchored bucket 'Candidate Bench' and current reality status 'bookmark candidate only'. Confirm actual implemented capability, hidden reusable modules, extension seams, and whether it strengthens the existing Unimplemented but relevant candidate lane. Focus on: Inspect planner/task graph; provider abstraction; tool registry or MCP bridges; memory/state schema; approvals/retries; telemetry/event bus; plugin or skill loading 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 planner loops, tool registries, MCP servers/clients, prompt/skill folders, memory stores, approval gates, background-job orchestration, and undocumented provider adapters.","Treat as unimplemented ScriptoriumAI candidate only. Do not let it redefine the current stack. Integrate only if a later audit proves it fills a real gap in the existing surfaces such as Dashboard, Editor, Corpus Graph, Runboard, AI Kanban, Corpus Search, Patch Review Queue, Visualizations, Whiteboard, Mind Map, PDF Intake, AI Diagram Studio, Video Studio, Research Agent, New Research Topic, Skills Manager, OpenAPI Routing, Manim Sandbox, Settings.","Repurpose here means mining for specific modules, algorithms, UI patterns, ingestion logic, workflow ideas, or export formats rather than assuming a full product transplant.",native/ScriptoriumAI-Server,stanford-oval/storm,abhigyanpatwari/GitNexus,"Return concrete files/modules/adapters worth reusing and a verdict on whether the current reanchored bucket should be kept, upgraded, or downgraded.",Do not treat licensing as a filter. Do not propose replacing native foundations unless source evidence is overwhelming.,ltjed/freephdlabor,v6_unified_source_of_truth_pack,"Before recommending direct code use, inspect the target repo row in the v6.1 operational/phase/source-audit boards. Respect copyleft_strategy_v6_1, preferred_boundary_model_v6_1, and open_compliance_if_used_as_is_v6_1. Do not assume reverse engineering is mandatory or that as-is use is always sensible.","If the repo-level strategy says bounded_sidecar_preferred or boundary_first_then_decide_as_is_vs_reimplementation, audit clean interfaces, protocol seams, subprocess/container boundaries, and what would be required to reimplement only the strategically necessary portions.",v6.3_final_source_of_truth
SCR_0201,,,,,,,,,,ScriptoriumAI repo packet,ScriptoriumAI,ScriptoriumAI re-anchored VS Code packets v1,manim-resources/manim_cad_drawing_utils,manim-resources/manim_cad_drawing_utils,Candidate Bench,P3,bookmark candidate only,"Audit manim-resources/manim_cad_drawing_utils for ScriptoriumAI. Start from the reanchored bucket 'Candidate Bench' and current reality status 'bookmark candidate only'. Confirm actual implemented capability, hidden reusable modules, extension seams, and whether it strengthens the existing Unimplemented but relevant candidate lane. Focus on: Inspect hidden modules, extension seams, data contracts, rendering paths, auth/storage coupling, and export/import boundaries.",,"Treat as unimplemented ScriptoriumAI candidate only. Do not let it redefine the current stack. Integrate only if a later audit proves it fills a real gap in the existing surfaces such as Dashboard, Editor, Corpus Graph, Runboard, AI Kanban, Corpus Search, Patch Review Queue, Visualizations, Whiteboard, Mind Map, PDF Intake, AI Diagram Studio, Video Studio, Research Agent, New Research Topic, Skills Manager, OpenAPI Routing, Manim Sandbox, Settings.","Repurpose here means mining for specific modules, algorithms, UI patterns, ingestion logic, workflow ideas, or export formats rather than assuming a full product transplant.",manimcommunity/manim,remotion-dev/remotion,native/ScriptoriumAI-Visualizer,"Return concrete files/modules/adapters worth reusing and a verdict on whether the current reanchored bucket should be kept, upgraded, or downgraded.",Do not treat licensing as a filter. Do not propose replacing native foundations unless source evidence is overwhelming.,manim-resources/manim_cad_drawing_utils,v6_unified_source_of_truth_pack,"Before recommending direct code use, inspect the target repo row in the v6.1 operational/phase/source-audit boards. Respect copyleft_strategy_v6_1, preferred_boundary_model_v6_1, and open_compliance_if_used_as_is_v6_1. Do not assume reverse engineering is mandatory or that as-is use is always sensible.","If the repo-level strategy says bounded_sidecar_preferred or boundary_first_then_decide_as_is_vs_reimplementation, audit clean interfaces, protocol seams, subprocess/container boundaries, and what would be required to reimplement only the strategically necessary portions.",v6.3_final_source_of_truth
SCR_0202,,,,,,,,,,ScriptoriumAI repo packet,ScriptoriumAI,ScriptoriumAI re-anchored VS Code packets v1,math-ai-org/mathcode,math-ai-org/mathcode,Candidate Bench,P3,bookmark candidate only,"Audit math-ai-org/mathcode for ScriptoriumAI. Start from the reanchored bucket 'Candidate Bench' and current reality status 'bookmark candidate only'. Confirm actual implemented capability, hidden reusable modules, extension seams, and whether it strengthens the existing Unimplemented but relevant candidate lane. Focus on: Inspect planner/task graph; provider abstraction; tool registry or MCP bridges; memory/state schema; approvals/retries; telemetry/event bus; plugin or skill loading 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 planner loops, tool registries, MCP servers/clients, prompt/skill folders, memory stores, approval gates, background-job orchestration, and undocumented provider adapters.","Treat as unimplemented ScriptoriumAI candidate only. Do not let it redefine the current stack. Integrate only if a later audit proves it fills a real gap in the existing surfaces such as Dashboard, Editor, Corpus Graph, Runboard, AI Kanban, Corpus Search, Patch Review Queue, Visualizations, Whiteboard, Mind Map, PDF Intake, AI Diagram Studio, Video Studio, Research Agent, New Research Topic, Skills Manager, OpenAPI Routing, Manim Sandbox, Settings.","Repurpose here means mining for specific modules, algorithms, UI patterns, ingestion logic, workflow ideas, or export formats rather than assuming a full product transplant.",native/ScriptoriumAI-Server,stanford-oval/storm,abhigyanpatwari/GitNexus,"Return concrete files/modules/adapters worth reusing and a verdict on whether the current reanchored bucket should be kept, upgraded, or downgraded.",Do not treat licensing as a filter. Do not propose replacing native foundations unless source evidence is overwhelming.,math-ai-org/mathcode,v6_unified_source_of_truth_pack,"Before recommending direct code use, inspect the target repo row in the v6.1 operational/phase/source-audit boards. Respect copyleft_strategy_v6_1, preferred_boundary_model_v6_1, and open_compliance_if_used_as_is_v6_1. Do not assume reverse engineering is mandatory or that as-is use is always sensible.","If the repo-level strategy says bounded_sidecar_preferred or boundary_first_then_decide_as_is_vs_reimplementation, audit clean interfaces, protocol seams, subprocess/container boundaries, and what would be required to reimplement only the strategically necessary portions.",v6.3_final_source_of_truth
SCR_0203,,,,,,,,,,ScriptoriumAI repo packet,ScriptoriumAI,ScriptoriumAI re-anchored VS Code packets v1,matheart/manim-astronomy,matheart/manim-astronomy,Candidate Bench,P3,bookmark candidate only,"Audit matheart/manim-astronomy for ScriptoriumAI. Start from the reanchored bucket 'Candidate Bench' and current reality status 'bookmark candidate only'. Confirm actual implemented capability, hidden reusable modules, extension seams, and whether it strengthens the existing Unimplemented but relevant candidate lane. Focus on: Inspect hidden modules, extension seams, data contracts, rendering paths, auth/storage coupling, and export/import boundaries.",,"Treat as unimplemented ScriptoriumAI candidate only. Do not let it redefine the current stack. Integrate only if a later audit proves it fills a real gap in the existing surfaces such as Dashboard, Editor, Corpus Graph, Runboard, AI Kanban, Corpus Search, Patch Review Queue, Visualizations, Whiteboard, Mind Map, PDF Intake, AI Diagram Studio, Video Studio, Research Agent, New Research Topic, Skills Manager, OpenAPI Routing, Manim Sandbox, Settings.","Repurpose here means mining for specific modules, algorithms, UI patterns, ingestion logic, workflow ideas, or export formats rather than assuming a full product transplant.",manimcommunity/manim,remotion-dev/remotion,native/ScriptoriumAI-Visualizer,"Return concrete files/modules/adapters worth reusing and a verdict on whether the current reanchored bucket should be kept, upgraded, or downgraded.",Do not treat licensing as a filter. Do not propose replacing native foundations unless source evidence is overwhelming.,matheart/manim-astronomy,v6_unified_source_of_truth_pack,"Before recommending direct code use, inspect the target repo row in the v6.1 operational/phase/source-audit boards. Respect copyleft_strategy_v6_1, preferred_boundary_model_v6_1, and open_compliance_if_used_as_is_v6_1. Do not assume reverse engineering is mandatory or that as-is use is always sensible.","If the repo-level strategy says bounded_sidecar_preferred or boundary_first_then_decide_as_is_vs_reimplementation, audit clean interfaces, protocol seams, subprocess/container boundaries, and what would be required to reimplement only the strategically necessary portions.",v6.3_final_source_of_truth
SCR_0204,,,,,,,,,,ScriptoriumAI repo packet,ScriptoriumAI,ScriptoriumAI re-anchored VS Code packets v1,matheart/manim-physics,matheart/manim-physics,Candidate Bench,P3,bookmark candidate only,"Audit matheart/manim-physics for ScriptoriumAI. Start from the reanchored bucket 'Candidate Bench' and current reality status 'bookmark candidate only'. Confirm actual implemented capability, hidden reusable modules, extension seams, and whether it strengthens the existing Unimplemented but relevant candidate lane. Focus on: Inspect hidden modules, extension seams, data contracts, rendering paths, auth/storage coupling, and export/import boundaries.",,"Treat as unimplemented ScriptoriumAI candidate only. Do not let it redefine the current stack. Integrate only if a later audit proves it fills a real gap in the existing surfaces such as Dashboard, Editor, Corpus Graph, Runboard, AI Kanban, Corpus Search, Patch Review Queue, Visualizations, Whiteboard, Mind Map, PDF Intake, AI Diagram Studio, Video Studio, Research Agent, New Research Topic, Skills Manager, OpenAPI Routing, Manim Sandbox, Settings.","Repurpose here means mining for specific modules, algorithms, UI patterns, ingestion logic, workflow ideas, or export formats rather than assuming a full product transplant.",manimcommunity/manim,remotion-dev/remotion,native/ScriptoriumAI-Visualizer,"Return concrete files/modules/adapters worth reusing and a verdict on whether the current reanchored bucket should be kept, upgraded, or downgraded.",Do not treat licensing as a filter. Do not propose replacing native foundations unless source evidence is overwhelming.,matheart/manim-physics,v6_unified_source_of_truth_pack,"Before recommending direct code use, inspect the target repo row in the v6.1 operational/phase/source-audit boards. Respect copyleft_strategy_v6_1, preferred_boundary_model_v6_1, and open_compliance_if_used_as_is_v6_1. Do not assume reverse engineering is mandatory or that as-is use is always sensible.","If the repo-level strategy says bounded_sidecar_preferred or boundary_first_then_decide_as_is_vs_reimplementation, audit clean interfaces, protocol seams, subprocess/container boundaries, and what would be required to reimplement only the strategically necessary portions.",v6.3_final_source_of_truth
SCR_0205,,,,,,,,,,ScriptoriumAI repo packet,ScriptoriumAI,ScriptoriumAI re-anchored VS Code packets v1,microsoft/RD-Agent,microsoft/rd-agent,Candidate Bench,P3,bookmark candidate only,"Audit microsoft/RD-Agent for ScriptoriumAI. Start from the reanchored bucket 'Candidate Bench' and current reality status 'bookmark candidate only'. Confirm actual implemented capability, hidden reusable modules, extension seams, and whether it strengthens the existing Unimplemented but relevant candidate lane. Focus on: Inspect planner/task graph; provider abstraction; tool registry or MCP bridges; memory/state schema; approvals/retries; telemetry/event bus; plugin or skill loading 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 planner loops, tool registries, MCP servers/clients, prompt/skill folders, memory stores, approval gates, background-job orchestration, and undocumented provider adapters.","Treat as unimplemented ScriptoriumAI candidate only. Do not let it redefine the current stack. Integrate only if a later audit proves it fills a real gap in the existing surfaces such as Dashboard, Editor, Corpus Graph, Runboard, AI Kanban, Corpus Search, Patch Review Queue, Visualizations, Whiteboard, Mind Map, PDF Intake, AI Diagram Studio, Video Studio, Research Agent, New Research Topic, Skills Manager, OpenAPI Routing, Manim Sandbox, Settings.","Repurpose here means mining for specific modules, algorithms, UI patterns, ingestion logic, workflow ideas, or export formats rather than assuming a full product transplant.",native/ScriptoriumAI-Server,stanford-oval/storm,abhigyanpatwari/GitNexus,"Return concrete files/modules/adapters worth reusing and a verdict on whether the current reanchored bucket should be kept, upgraded, or downgraded.",Do not treat licensing as a filter. Do not propose replacing native foundations unless source evidence is overwhelming.,microsoft/rd-agent,v6_unified_source_of_truth_pack,"Before recommending direct code use, inspect the target repo row in the v6.1 operational/phase/source-audit boards. Respect copyleft_strategy_v6_1, preferred_boundary_model_v6_1, and open_compliance_if_used_as_is_v6_1. Do not assume reverse engineering is mandatory or that as-is use is always sensible.","If the repo-level strategy says bounded_sidecar_preferred or boundary_first_then_decide_as_is_vs_reimplementation, audit clean interfaces, protocol seams, subprocess/container boundaries, and what would be required to reimplement only the strategically necessary portions.",v6.3_final_source_of_truth
SCR_0206,,,,,,,,,,ScriptoriumAI repo packet,ScriptoriumAI,ScriptoriumAI re-anchored VS Code packets v1,mkueh/manim-graphviz,mkueh/manim-graphviz,Candidate Bench,P3,bookmark candidate only,"Audit mkueh/manim-graphviz for ScriptoriumAI. Start from the reanchored bucket 'Candidate Bench' and current reality status 'bookmark candidate only'. Confirm actual implemented capability, hidden reusable modules, extension seams, and whether it strengthens the existing Unimplemented but relevant candidate lane. Focus on: Inspect hidden modules, extension seams, data contracts, rendering paths, auth/storage coupling, and export/import boundaries.",,"Treat as unimplemented ScriptoriumAI candidate only. Do not let it redefine the current stack. Integrate only if a later audit proves it fills a real gap in the existing surfaces such as Dashboard, Editor, Corpus Graph, Runboard, AI Kanban, Corpus Search, Patch Review Queue, Visualizations, Whiteboard, Mind Map, PDF Intake, AI Diagram Studio, Video Studio, Research Agent, New Research Topic, Skills Manager, OpenAPI Routing, Manim Sandbox, Settings.","Repurpose here means mining for specific modules, algorithms, UI patterns, ingestion logic, workflow ideas, or export formats rather than assuming a full product transplant.",manimcommunity/manim,remotion-dev/remotion,native/ScriptoriumAI-Visualizer,"Return concrete files/modules/adapters worth reusing and a verdict on whether the current reanchored bucket should be kept, upgraded, or downgraded.",Do not treat licensing as a filter. Do not propose replacing native foundations unless source evidence is overwhelming.,mkueh/manim-graphviz,v6_unified_source_of_truth_pack,"Before recommending direct code use, inspect the target repo row in the v6.1 operational/phase/source-audit boards. Respect copyleft_strategy_v6_1, preferred_boundary_model_v6_1, and open_compliance_if_used_as_is_v6_1. Do not assume reverse engineering is mandatory or that as-is use is always sensible.","If the repo-level strategy says bounded_sidecar_preferred or boundary_first_then_decide_as_is_vs_reimplementation, audit clean interfaces, protocol seams, subprocess/container boundaries, and what would be required to reimplement only the strategically necessary portions.",v6.3_final_source_of_truth
SCR_0207,,,,,,,,,,ScriptoriumAI repo packet,ScriptoriumAI,ScriptoriumAI re-anchored VS Code packets v1,moltbot/moltbot,moltbot/moltbot,Candidate Bench,P3,bookmark candidate only,"Audit moltbot/moltbot for ScriptoriumAI. Start from the reanchored bucket 'Candidate Bench' and current reality status 'bookmark candidate only'. Confirm actual implemented capability, hidden reusable modules, extension seams, and whether it strengthens the existing Unimplemented but relevant candidate lane. Focus on: Inspect planner/task graph; provider abstraction; tool registry or MCP bridges; memory/state schema; approvals/retries; telemetry/event bus; plugin or skill loading 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 planner loops, tool registries, MCP servers/clients, prompt/skill folders, memory stores, approval gates, background-job orchestration, and undocumented provider adapters.","Treat as unimplemented ScriptoriumAI candidate only. Do not let it redefine the current stack. Integrate only if a later audit proves it fills a real gap in the existing surfaces such as Dashboard, Editor, Corpus Graph, Runboard, AI Kanban, Corpus Search, Patch Review Queue, Visualizations, Whiteboard, Mind Map, PDF Intake, AI Diagram Studio, Video Studio, Research Agent, New Research Topic, Skills Manager, OpenAPI Routing, Manim Sandbox, Settings.","Repurpose here means mining for specific modules, algorithms, UI patterns, ingestion logic, workflow ideas, or export formats rather than assuming a full product transplant.",native/scriptoriumai-ui,native/ScriptoriumAI-Server,abhigyanpatwari/GitNexus,"Return concrete files/modules/adapters worth reusing and a verdict on whether the current reanchored bucket should be kept, upgraded, or downgraded.",Do not treat licensing as a filter. Do not propose replacing native foundations unless source evidence is overwhelming.,moltbot/moltbot,v6_unified_source_of_truth_pack,"Before recommending direct code use, inspect the target repo row in the v6.1 operational/phase/source-audit boards. Respect copyleft_strategy_v6_1, preferred_boundary_model_v6_1, and open_compliance_if_used_as_is_v6_1. Do not assume reverse engineering is mandatory or that as-is use is always sensible.","If the repo-level strategy says bounded_sidecar_preferred or boundary_first_then_decide_as_is_vs_reimplementation, audit clean interfaces, protocol seams, subprocess/container boundaries, and what would be required to reimplement only the strategically necessary portions.",v6.3_final_source_of_truth
SCR_0208,,,,,,,,,,ScriptoriumAI repo packet,ScriptoriumAI,ScriptoriumAI re-anchored VS Code packets v1,mr-fuzzypenguin/manim-circuit,mr-fuzzypenguin/manim-circuit,Candidate Bench,P3,bookmark candidate only,"Audit mr-fuzzypenguin/manim-circuit for ScriptoriumAI. Start from the reanchored bucket 'Candidate Bench' and current reality status 'bookmark candidate only'. Confirm actual implemented capability, hidden reusable modules, extension seams, and whether it strengthens the existing Unimplemented but relevant candidate lane. Focus on: Inspect hidden modules, extension seams, data contracts, rendering paths, auth/storage coupling, and export/import boundaries.",,"Treat as unimplemented ScriptoriumAI candidate only. Do not let it redefine the current stack. Integrate only if a later audit proves it fills a real gap in the existing surfaces such as Dashboard, Editor, Corpus Graph, Runboard, AI Kanban, Corpus Search, Patch Review Queue, Visualizations, Whiteboard, Mind Map, PDF Intake, AI Diagram Studio, Video Studio, Research Agent, New Research Topic, Skills Manager, OpenAPI Routing, Manim Sandbox, Settings.","Repurpose here means mining for specific modules, algorithms, UI patterns, ingestion logic, workflow ideas, or export formats rather than assuming a full product transplant.",manimcommunity/manim,remotion-dev/remotion,native/ScriptoriumAI-Visualizer,"Return concrete files/modules/adapters worth reusing and a verdict on whether the current reanchored bucket should be kept, upgraded, or downgraded.",Do not treat licensing as a filter. Do not propose replacing native foundations unless source evidence is overwhelming.,mr-fuzzypenguin/manim-circuit,v6_unified_source_of_truth_pack,"Before recommending direct code use, inspect the target repo row in the v6.1 operational/phase/source-audit boards. Respect copyleft_strategy_v6_1, preferred_boundary_model_v6_1, and open_compliance_if_used_as_is_v6_1. Do not assume reverse engineering is mandatory or that as-is use is always sensible.","If the repo-level strategy says bounded_sidecar_preferred or boundary_first_then_decide_as_is_vs_reimplementation, audit clean interfaces, protocol seams, subprocess/container boundaries, and what would be required to reimplement only the strategically necessary portions.",v6.3_final_source_of_truth
SCR_0209,,,,,,,,,,ScriptoriumAI repo packet,ScriptoriumAI,ScriptoriumAI re-anchored VS Code packets v1,mshumer/autonomous-researcher,mshumer/autonomous-researcher,Candidate Bench,P3,bookmark candidate only,"Audit mshumer/autonomous-researcher for ScriptoriumAI. Start from the reanchored bucket 'Candidate Bench' and current reality status 'bookmark candidate only'. Confirm actual implemented capability, hidden reusable modules, extension seams, and whether it strengthens the existing Unimplemented but relevant candidate lane. Focus on: Inspect planner/task graph; provider abstraction; tool registry or MCP bridges; memory/state schema; approvals/retries; telemetry/event bus; plugin or skill loading 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 planner loops, tool registries, MCP servers/clients, prompt/skill folders, memory stores, approval gates, background-job orchestration, and undocumented provider adapters.","Treat as unimplemented ScriptoriumAI candidate only. Do not let it redefine the current stack. Integrate only if a later audit proves it fills a real gap in the existing surfaces such as Dashboard, Editor, Corpus Graph, Runboard, AI Kanban, Corpus Search, Patch Review Queue, Visualizations, Whiteboard, Mind Map, PDF Intake, AI Diagram Studio, Video Studio, Research Agent, New Research Topic, Skills Manager, OpenAPI Routing, Manim Sandbox, Settings.","Repurpose here means mining for specific modules, algorithms, UI patterns, ingestion logic, workflow ideas, or export formats rather than assuming a full product transplant.",native/ScriptoriumAI-Server,stanford-oval/storm,abhigyanpatwari/GitNexus,"Return concrete files/modules/adapters worth reusing and a verdict on whether the current reanchored bucket should be kept, upgraded, or downgraded.",Do not treat licensing as a filter. Do not propose replacing native foundations unless source evidence is overwhelming.,mshumer/autonomous-researcher,v6_unified_source_of_truth_pack,"Before recommending direct code use, inspect the target repo row in the v6.1 operational/phase/source-audit boards. Respect copyleft_strategy_v6_1, preferred_boundary_model_v6_1, and open_compliance_if_used_as_is_v6_1. Do not assume reverse engineering is mandatory or that as-is use is always sensible.","If the repo-level strategy says bounded_sidecar_preferred or boundary_first_then_decide_as_is_vs_reimplementation, audit clean interfaces, protocol seams, subprocess/container boundaries, and what would be required to reimplement only the strategically necessary portions.",v6.3_final_source_of_truth
SCR_0210,,,,,,,,,,ScriptoriumAI repo packet,ScriptoriumAI,ScriptoriumAI re-anchored VS Code packets v1,naveen521kk/manim-data-structures,naveen521kk/manim-data-structures,Candidate Bench,P3,bookmark candidate only,"Audit naveen521kk/manim-data-structures for ScriptoriumAI. Start from the reanchored bucket 'Candidate Bench' and current reality status 'bookmark candidate only'. Confirm actual implemented capability, hidden reusable modules, extension seams, and whether it strengthens the existing Unimplemented but relevant candidate lane. Focus on: Inspect hidden modules, extension seams, data contracts, rendering paths, auth/storage coupling, and export/import boundaries.",,"Treat as unimplemented ScriptoriumAI candidate only. Do not let it redefine the current stack. Integrate only if a later audit proves it fills a real gap in the existing surfaces such as Dashboard, Editor, Corpus Graph, Runboard, AI Kanban, Corpus Search, Patch Review Queue, Visualizations, Whiteboard, Mind Map, PDF Intake, AI Diagram Studio, Video Studio, Research Agent, New Research Topic, Skills Manager, OpenAPI Routing, Manim Sandbox, Settings.","Repurpose here means mining for specific modules, algorithms, UI patterns, ingestion logic, workflow ideas, or export formats rather than assuming a full product transplant.",manimcommunity/manim,remotion-dev/remotion,native/ScriptoriumAI-Visualizer,"Return concrete files/modules/adapters worth reusing and a verdict on whether the current reanchored bucket should be kept, upgraded, or downgraded.",Do not treat licensing as a filter. Do not propose replacing native foundations unless source evidence is overwhelming.,naveen521kk/manim-data-structures,v6_unified_source_of_truth_pack,"Before recommending direct code use, inspect the target repo row in the v6.1 operational/phase/source-audit boards. Respect copyleft_strategy_v6_1, preferred_boundary_model_v6_1, and open_compliance_if_used_as_is_v6_1. Do not assume reverse engineering is mandatory or that as-is use is always sensible.","If the repo-level strategy says bounded_sidecar_preferred or boundary_first_then_decide_as_is_vs_reimplementation, audit clean interfaces, protocol seams, subprocess/container boundaries, and what would be required to reimplement only the strategically necessary portions.",v6.3_final_source_of_truth
SCR_0211,,,,,,,,,,ScriptoriumAI repo packet,ScriptoriumAI,ScriptoriumAI re-anchored VS Code packets v1,naveen521kk/manim-fonts,naveen521kk/manim-fonts,Candidate Bench,P3,bookmark candidate only,"Audit naveen521kk/manim-fonts for ScriptoriumAI. Start from the reanchored bucket 'Candidate Bench' and current reality status 'bookmark candidate only'. Confirm actual implemented capability, hidden reusable modules, extension seams, and whether it strengthens the existing Unimplemented but relevant candidate lane. Focus on: Inspect hidden modules, extension seams, data contracts, rendering paths, auth/storage coupling, and export/import boundaries.",,"Treat as unimplemented ScriptoriumAI candidate only. Do not let it redefine the current stack. Integrate only if a later audit proves it fills a real gap in the existing surfaces such as Dashboard, Editor, Corpus Graph, Runboard, AI Kanban, Corpus Search, Patch Review Queue, Visualizations, Whiteboard, Mind Map, PDF Intake, AI Diagram Studio, Video Studio, Research Agent, New Research Topic, Skills Manager, OpenAPI Routing, Manim Sandbox, Settings.","Repurpose here means mining for specific modules, algorithms, UI patterns, ingestion logic, workflow ideas, or export formats rather than assuming a full product transplant.",manimcommunity/manim,remotion-dev/remotion,native/ScriptoriumAI-Visualizer,"Return concrete files/modules/adapters worth reusing and a verdict on whether the current reanchored bucket should be kept, upgraded, or downgraded.",Do not treat licensing as a filter. Do not propose replacing native foundations unless source evidence is overwhelming.,naveen521kk/manim-fonts,v6_unified_source_of_truth_pack,"Before recommending direct code use, inspect the target repo row in the v6.1 operational/phase/source-audit boards. Respect copyleft_strategy_v6_1, preferred_boundary_model_v6_1, and open_compliance_if_used_as_is_v6_1. Do not assume reverse engineering is mandatory or that as-is use is always sensible.","If the repo-level strategy says bounded_sidecar_preferred or boundary_first_then_decide_as_is_vs_reimplementation, audit clean interfaces, protocol seams, subprocess/container boundaries, and what would be required to reimplement only the strategically necessary portions.",v6.3_final_source_of_truth
SCR_0212,,,,,,,,,,ScriptoriumAI repo packet,ScriptoriumAI,ScriptoriumAI re-anchored VS Code packets v1,nikitamahoviya/manim-code,nikitamahoviya/manim-code,Candidate Bench,P3,bookmark candidate only,"Audit nikitamahoviya/manim-code for ScriptoriumAI. Start from the reanchored bucket 'Candidate Bench' and current reality status 'bookmark candidate only'. Confirm actual implemented capability, hidden reusable modules, extension seams, and whether it strengthens the existing Unimplemented but relevant candidate lane. Focus on: Inspect hidden modules, extension seams, data contracts, rendering paths, auth/storage coupling, and export/import boundaries.",,"Treat as unimplemented ScriptoriumAI candidate only. Do not let it redefine the current stack. Integrate only if a later audit proves it fills a real gap in the existing surfaces such as Dashboard, Editor, Corpus Graph, Runboard, AI Kanban, Corpus Search, Patch Review Queue, Visualizations, Whiteboard, Mind Map, PDF Intake, AI Diagram Studio, Video Studio, Research Agent, New Research Topic, Skills Manager, OpenAPI Routing, Manim Sandbox, Settings.","Repurpose here means mining for specific modules, algorithms, UI patterns, ingestion logic, workflow ideas, or export formats rather than assuming a full product transplant.",manimcommunity/manim,remotion-dev/remotion,native/ScriptoriumAI-Visualizer,"Return concrete files/modules/adapters worth reusing and a verdict on whether the current reanchored bucket should be kept, upgraded, or downgraded.",Do not treat licensing as a filter. Do not propose replacing native foundations unless source evidence is overwhelming.,nikitamahoviya/manim-code,v6_unified_source_of_truth_pack,"Before recommending direct code use, inspect the target repo row in the v6.1 operational/phase/source-audit boards. Respect copyleft_strategy_v6_1, preferred_boundary_model_v6_1, and open_compliance_if_used_as_is_v6_1. Do not assume reverse engineering is mandatory or that as-is use is always sensible.","If the repo-level strategy says bounded_sidecar_preferred or boundary_first_then_decide_as_is_vs_reimplementation, audit clean interfaces, protocol seams, subprocess/container boundaries, and what would be required to reimplement only the strategically necessary portions.",v6.3_final_source_of_truth
SCR_0213,,,,,,,,,,ScriptoriumAI repo packet,ScriptoriumAI,ScriptoriumAI re-anchored VS Code packets v1,ocrbase-hq/ocrbase,ocrbase-hq/ocrbase,Candidate Bench,P3,bookmark candidate only,"Audit ocrbase-hq/ocrbase for ScriptoriumAI. Start from the reanchored bucket 'Candidate Bench' and current reality status 'bookmark candidate only'. Confirm actual implemented capability, hidden reusable modules, extension seams, and whether it strengthens the existing Unimplemented but relevant candidate lane. Focus on: Inspect parsers and language adapters; graph schema and storage; incremental indexing/update logic; layout engine; query API; export/import formats; test fixtures for graph correctness.","Inspect package manifests, README/docs, src tree, examples, tests, CI workflows, config files, migrations/schemas, and hidden feature flags or experimental modules. Look for event schemas, ingestion pipelines, queue/job workers, service adapters, deployment/runtime config, RBAC/auth, alerting, and API contract generators.","Treat as unimplemented ScriptoriumAI candidate only. Do not let it redefine the current stack. Integrate only if a later audit proves it fills a real gap in the existing surfaces such as Dashboard, Editor, Corpus Graph, Runboard, AI Kanban, Corpus Search, Patch Review Queue, Visualizations, Whiteboard, Mind Map, PDF Intake, AI Diagram Studio, Video Studio, Research Agent, New Research Topic, Skills Manager, OpenAPI Routing, Manim Sandbox, Settings.","Repurpose here means mining for specific modules, algorithms, UI patterns, ingestion logic, workflow ideas, or export formats rather than assuming a full product transplant.",pdfmd/pdfmd,lukas-blecher/latex-ocr,mli55/pdfdelta,"Return concrete files/modules/adapters worth reusing and a verdict on whether the current reanchored bucket should be kept, upgraded, or downgraded.",Do not treat licensing as a filter. Do not propose replacing native foundations unless source evidence is overwhelming.,ocrbase-hq/ocrbase,v6_unified_source_of_truth_pack,"Before recommending direct code use, inspect the target repo row in the v6.1 operational/phase/source-audit boards. Respect copyleft_strategy_v6_1, preferred_boundary_model_v6_1, and open_compliance_if_used_as_is_v6_1. Do not assume reverse engineering is mandatory or that as-is use is always sensible.","If the repo-level strategy says bounded_sidecar_preferred or boundary_first_then_decide_as_is_vs_reimplementation, audit clean interfaces, protocol seams, subprocess/container boundaries, and what would be required to reimplement only the strategically necessary portions.",v6.3_final_source_of_truth
SCR_0214,,,,,,,,,,ScriptoriumAI repo packet,ScriptoriumAI,ScriptoriumAI re-anchored VS Code packets v1,onyx-dot-app/onyx,onyx-dot-app/onyx,Candidate Bench,P3,bookmark candidate only,"Audit onyx-dot-app/onyx for ScriptoriumAI. Start from the reanchored bucket 'Candidate Bench' and current reality status 'bookmark candidate only'. Confirm actual implemented capability, hidden reusable modules, extension seams, and whether it strengthens the existing Unimplemented but relevant candidate lane. Focus on: 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 planner loops, tool registries, MCP servers/clients, prompt/skill folders, memory stores, approval gates, background-job orchestration, and undocumented provider adapters.","Treat as unimplemented ScriptoriumAI candidate only. Do not let it redefine the current stack. Integrate only if a later audit proves it fills a real gap in the existing surfaces such as Dashboard, Editor, Corpus Graph, Runboard, AI Kanban, Corpus Search, Patch Review Queue, Visualizations, Whiteboard, Mind Map, PDF Intake, AI Diagram Studio, Video Studio, Research Agent, New Research Topic, Skills Manager, OpenAPI Routing, Manim Sandbox, Settings.","Repurpose here means mining for specific modules, algorithms, UI patterns, ingestion logic, workflow ideas, or export formats rather than assuming a full product transplant.",native/scriptoriumai-ui,native/ScriptoriumAI-Server,abhigyanpatwari/GitNexus,"Return concrete files/modules/adapters worth reusing and a verdict on whether the current reanchored bucket should be kept, upgraded, or downgraded.",Do not treat licensing as a filter. Do not propose replacing native foundations unless source evidence is overwhelming.,onyx-dot-app/onyx,v6_unified_source_of_truth_pack,"Before recommending direct code use, inspect the target repo row in the v6.1 operational/phase/source-audit boards. Respect copyleft_strategy_v6_1, preferred_boundary_model_v6_1, and open_compliance_if_used_as_is_v6_1. Do not assume reverse engineering is mandatory or that as-is use is always sensible.","If the repo-level strategy says bounded_sidecar_preferred or boundary_first_then_decide_as_is_vs_reimplementation, audit clean interfaces, protocol seams, subprocess/container boundaries, and what would be required to reimplement only the strategically necessary portions.",v6.3_final_source_of_truth
SCR_0215,,,,,,,,,,ScriptoriumAI repo packet,ScriptoriumAI,ScriptoriumAI re-anchored VS Code packets v1,openai/openai-agents-python,openai/openai-agents-python,Candidate Bench,P3,bookmark candidate only,"Audit openai/openai-agents-python for ScriptoriumAI. Start from the reanchored bucket 'Candidate Bench' and current reality status 'bookmark candidate only'. Confirm actual implemented capability, hidden reusable modules, extension seams, and whether it strengthens the existing Unimplemented but relevant candidate lane. Focus on: Inspect planner/task graph; provider abstraction; tool registry or MCP bridges; memory/state schema; approvals/retries; telemetry/event bus; plugin or skill loading 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 planner loops, tool registries, MCP servers/clients, prompt/skill folders, memory stores, approval gates, background-job orchestration, and undocumented provider adapters.","Treat as unimplemented ScriptoriumAI candidate only. Do not let it redefine the current stack. Integrate only if a later audit proves it fills a real gap in the existing surfaces such as Dashboard, Editor, Corpus Graph, Runboard, AI Kanban, Corpus Search, Patch Review Queue, Visualizations, Whiteboard, Mind Map, PDF Intake, AI Diagram Studio, Video Studio, Research Agent, New Research Topic, Skills Manager, OpenAPI Routing, Manim Sandbox, Settings.","Repurpose here means mining for specific modules, algorithms, UI patterns, ingestion logic, workflow ideas, or export formats rather than assuming a full product transplant.",native/ScriptoriumAI-Server,stanford-oval/storm,abhigyanpatwari/GitNexus,"Return concrete files/modules/adapters worth reusing and a verdict on whether the current reanchored bucket should be kept, upgraded, or downgraded.",Do not treat licensing as a filter. Do not propose replacing native foundations unless source evidence is overwhelming.,openai/openai-agents-python,v6_unified_source_of_truth_pack,"Before recommending direct code use, inspect the target repo row in the v6.1 operational/phase/source-audit boards. Respect copyleft_strategy_v6_1, preferred_boundary_model_v6_1, and open_compliance_if_used_as_is_v6_1. Do not assume reverse engineering is mandatory or that as-is use is always sensible.","If the repo-level strategy says bounded_sidecar_preferred or boundary_first_then_decide_as_is_vs_reimplementation, audit clean interfaces, protocol seams, subprocess/container boundaries, and what would be required to reimplement only the strategically necessary portions.",v6.3_final_source_of_truth
SCR_0216,,,,,,,,,,ScriptoriumAI repo packet,ScriptoriumAI,ScriptoriumAI re-anchored VS Code packets v1,openai/symphony,openai/symphony,Candidate Bench,P3,bookmark candidate only,"Audit openai/symphony for ScriptoriumAI. Start from the reanchored bucket 'Candidate Bench' and current reality status 'bookmark candidate only'. Confirm actual implemented capability, hidden reusable modules, extension seams, and whether it strengthens the existing Unimplemented but relevant candidate lane. Focus on: Inspect planner/task graph; provider abstraction; tool registry or MCP bridges; memory/state schema; approvals/retries; telemetry/event bus; plugin or skill loading 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 planner loops, tool registries, MCP servers/clients, prompt/skill folders, memory stores, approval gates, background-job orchestration, and undocumented provider adapters.","Treat as unimplemented ScriptoriumAI candidate only. Do not let it redefine the current stack. Integrate only if a later audit proves it fills a real gap in the existing surfaces such as Dashboard, Editor, Corpus Graph, Runboard, AI Kanban, Corpus Search, Patch Review Queue, Visualizations, Whiteboard, Mind Map, PDF Intake, AI Diagram Studio, Video Studio, Research Agent, New Research Topic, Skills Manager, OpenAPI Routing, Manim Sandbox, Settings.","Repurpose here means mining for specific modules, algorithms, UI patterns, ingestion logic, workflow ideas, or export formats rather than assuming a full product transplant.",native/ScriptoriumAI-Server,stanford-oval/storm,abhigyanpatwari/GitNexus,"Return concrete files/modules/adapters worth reusing and a verdict on whether the current reanchored bucket should be kept, upgraded, or downgraded.",Do not treat licensing as a filter. Do not propose replacing native foundations unless source evidence is overwhelming.,openai/symphony,v6_unified_source_of_truth_pack,"Before recommending direct code use, inspect the target repo row in the v6.1 operational/phase/source-audit boards. Respect copyleft_strategy_v6_1, preferred_boundary_model_v6_1, and open_compliance_if_used_as_is_v6_1. Do not assume reverse engineering is mandatory or that as-is use is always sensible.","If the repo-level strategy says bounded_sidecar_preferred or boundary_first_then_decide_as_is_vs_reimplementation, audit clean interfaces, protocol seams, subprocess/container boundaries, and what would be required to reimplement only the strategically necessary portions.",v6.3_final_source_of_truth
SCR_0217,,,,,,,,,,ScriptoriumAI repo packet,ScriptoriumAI,ScriptoriumAI re-anchored VS Code packets v1,opendataloader-project/opendataloader-pdf,opendataloader-project/opendataloader-pdf,Candidate Bench,P3,bookmark candidate only,"Audit opendataloader-project/opendataloader-pdf for ScriptoriumAI. Start from the reanchored bucket 'Candidate Bench' and current reality status 'bookmark candidate only'. Confirm actual implemented capability, hidden reusable modules, extension seams, and whether it strengthens the existing Unimplemented but relevant candidate lane. Focus on: Inspect document/block schema; sync/persistence model; permissions and sharing; citation/external-source pipeline; import/export adapters; plugin/extension points; editor rendering model.","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.","Treat as unimplemented ScriptoriumAI candidate only. Do not let it redefine the current stack. Integrate only if a later audit proves it fills a real gap in the existing surfaces such as Dashboard, Editor, Corpus Graph, Runboard, AI Kanban, Corpus Search, Patch Review Queue, Visualizations, Whiteboard, Mind Map, PDF Intake, AI Diagram Studio, Video Studio, Research Agent, New Research Topic, Skills Manager, OpenAPI Routing, Manim Sandbox, Settings.","Repurpose here means mining for specific modules, algorithms, UI patterns, ingestion logic, workflow ideas, or export formats rather than assuming a full product transplant.",pdfmd/pdfmd,lukas-blecher/latex-ocr,mli55/pdfdelta,"Return concrete files/modules/adapters worth reusing and a verdict on whether the current reanchored bucket should be kept, upgraded, or downgraded.",Do not treat licensing as a filter. Do not propose replacing native foundations unless source evidence is overwhelming.,opendataloader-project/opendataloader-pdf,v6_unified_source_of_truth_pack,"Before recommending direct code use, inspect the target repo row in the v6.1 operational/phase/source-audit boards. Respect copyleft_strategy_v6_1, preferred_boundary_model_v6_1, and open_compliance_if_used_as_is_v6_1. Do not assume reverse engineering is mandatory or that as-is use is always sensible.","If the repo-level strategy says bounded_sidecar_preferred or boundary_first_then_decide_as_is_vs_reimplementation, audit clean interfaces, protocol seams, subprocess/container boundaries, and what would be required to reimplement only the strategically necessary portions.",v6.3_final_source_of_truth
SCR_0218,,,,,,,,,,ScriptoriumAI repo packet,ScriptoriumAI,ScriptoriumAI re-anchored VS Code packets v1,overegneered/manim-eng,overegneered/manim-eng,Candidate Bench,P3,bookmark candidate only,"Audit overegneered/manim-eng for ScriptoriumAI. Start from the reanchored bucket 'Candidate Bench' and current reality status 'bookmark candidate only'. Confirm actual implemented capability, hidden reusable modules, extension seams, and whether it strengthens the existing Unimplemented but relevant candidate lane. Focus on: Inspect hidden modules, extension seams, data contracts, rendering paths, auth/storage coupling, and export/import boundaries.",,"Treat as unimplemented ScriptoriumAI candidate only. Do not let it redefine the current stack. Integrate only if a later audit proves it fills a real gap in the existing surfaces such as Dashboard, Editor, Corpus Graph, Runboard, AI Kanban, Corpus Search, Patch Review Queue, Visualizations, Whiteboard, Mind Map, PDF Intake, AI Diagram Studio, Video Studio, Research Agent, New Research Topic, Skills Manager, OpenAPI Routing, Manim Sandbox, Settings.","Repurpose here means mining for specific modules, algorithms, UI patterns, ingestion logic, workflow ideas, or export formats rather than assuming a full product transplant.",manimcommunity/manim,remotion-dev/remotion,native/ScriptoriumAI-Visualizer,"Return concrete files/modules/adapters worth reusing and a verdict on whether the current reanchored bucket should be kept, upgraded, or downgraded.",Do not treat licensing as a filter. Do not propose replacing native foundations unless source evidence is overwhelming.,overegneered/manim-eng,v6_unified_source_of_truth_pack,"Before recommending direct code use, inspect the target repo row in the v6.1 operational/phase/source-audit boards. Respect copyleft_strategy_v6_1, preferred_boundary_model_v6_1, and open_compliance_if_used_as_is_v6_1. Do not assume reverse engineering is mandatory or that as-is use is always sensible.","If the repo-level strategy says bounded_sidecar_preferred or boundary_first_then_decide_as_is_vs_reimplementation, audit clean interfaces, protocol seams, subprocess/container boundaries, and what would be required to reimplement only the strategically necessary portions.",v6.3_final_source_of_truth
SCR_0219,,,,,,,,,,ScriptoriumAI repo packet,ScriptoriumAI,ScriptoriumAI re-anchored VS Code packets v1,paper2video/paper2video,paper2video/paper2video,Candidate Bench,P3,bookmark candidate only,"Audit paper2video/paper2video for ScriptoriumAI. Start from the reanchored bucket 'Candidate Bench' and current reality status 'bookmark candidate only'. Confirm actual implemented capability, hidden reusable modules, extension seams, and whether it strengthens the existing Unimplemented but relevant candidate lane. Focus on: Inspect hidden modules, extension seams, data contracts, rendering paths, auth/storage coupling, and export/import boundaries.",,"Treat as unimplemented ScriptoriumAI candidate only. Do not let it redefine the current stack. Integrate only if a later audit proves it fills a real gap in the existing surfaces such as Dashboard, Editor, Corpus Graph, Runboard, AI Kanban, Corpus Search, Patch Review Queue, Visualizations, Whiteboard, Mind Map, PDF Intake, AI Diagram Studio, Video Studio, Research Agent, New Research Topic, Skills Manager, OpenAPI Routing, Manim Sandbox, Settings.","Repurpose here means mining for specific modules, algorithms, UI patterns, ingestion logic, workflow ideas, or export formats rather than assuming a full product transplant.",manimcommunity/manim,remotion-dev/remotion,native/ScriptoriumAI-Visualizer,"Return concrete files/modules/adapters worth reusing and a verdict on whether the current reanchored bucket should be kept, upgraded, or downgraded.",Do not treat licensing as a filter. Do not propose replacing native foundations unless source evidence is overwhelming.,paper2video/paper2video,v6_unified_source_of_truth_pack,"Before recommending direct code use, inspect the target repo row in the v6.1 operational/phase/source-audit boards. Respect copyleft_strategy_v6_1, preferred_boundary_model_v6_1, and open_compliance_if_used_as_is_v6_1. Do not assume reverse engineering is mandatory or that as-is use is always sensible.","If the repo-level strategy says bounded_sidecar_preferred or boundary_first_then_decide_as_is_vs_reimplementation, audit clean interfaces, protocol seams, subprocess/container boundaries, and what would be required to reimplement only the strategically necessary portions.",v6.3_final_source_of_truth
SCR_0220,,,,,,,,,,ScriptoriumAI repo packet,ScriptoriumAI,ScriptoriumAI re-anchored VS Code packets v1,papers-we-love/papers-we-love,papers-we-love/papers-we-love,Candidate Bench,P3,bookmark candidate only,"Audit papers-we-love/papers-we-love for ScriptoriumAI. Start from the reanchored bucket 'Candidate Bench' and current reality status 'bookmark candidate only'. Confirm actual implemented capability, hidden reusable modules, extension seams, and whether it strengthens the existing Unimplemented but relevant candidate lane. Focus on: Inspect document/block schema; sync/persistence model; permissions and sharing; citation/external-source pipeline; import/export adapters; plugin/extension points; editor rendering model.","Inspect package manifests, README/docs, src tree, examples, tests, CI workflows, config files, migrations/schemas, and hidden feature flags or experimental modules. Look for document/block schema, sync/conflict logic, citation handling, editor plugins, export/render pipeline, prompt chains, report assembly, and collaborative presence code.","Treat as unimplemented ScriptoriumAI candidate only. Do not let it redefine the current stack. Integrate only if a later audit proves it fills a real gap in the existing surfaces such as Dashboard, Editor, Corpus Graph, Runboard, AI Kanban, Corpus Search, Patch Review Queue, Visualizations, Whiteboard, Mind Map, PDF Intake, AI Diagram Studio, Video Studio, Research Agent, New Research Topic, Skills Manager, OpenAPI Routing, Manim Sandbox, Settings.","Repurpose here means mining for specific modules, algorithms, UI patterns, ingestion logic, workflow ideas, or export formats rather than assuming a full product transplant.",native/scriptoriumai-ui,native/ScriptoriumAI-Server,abhigyanpatwari/GitNexus,"Return concrete files/modules/adapters worth reusing and a verdict on whether the current reanchored bucket should be kept, upgraded, or downgraded.",Do not treat licensing as a filter. Do not propose replacing native foundations unless source evidence is overwhelming.,papers-we-love/papers-we-love,v6_unified_source_of_truth_pack,"Before recommending direct code use, inspect the target repo row in the v6.1 operational/phase/source-audit boards. Respect copyleft_strategy_v6_1, preferred_boundary_model_v6_1, and open_compliance_if_used_as_is_v6_1. Do not assume reverse engineering is mandatory or that as-is use is always sensible.","If the repo-level strategy says bounded_sidecar_preferred or boundary_first_then_decide_as_is_vs_reimplementation, audit clean interfaces, protocol seams, subprocess/container boundaries, and what would be required to reimplement only the strategically necessary portions.",v6.3_final_source_of_truth
SCR_0221,,,,,,,,,,ScriptoriumAI repo packet,ScriptoriumAI,ScriptoriumAI re-anchored VS Code packets v1,prime126/manim-fontawesome,prime126/manim-fontawesome,Candidate Bench,P3,bookmark candidate only,"Audit prime126/manim-fontawesome for ScriptoriumAI. Start from the reanchored bucket 'Candidate Bench' and current reality status 'bookmark candidate only'. Confirm actual implemented capability, hidden reusable modules, extension seams, and whether it strengthens the existing Unimplemented but relevant candidate lane. Focus on: Inspect hidden modules, extension seams, data contracts, rendering paths, auth/storage coupling, and export/import boundaries.",,"Treat as unimplemented ScriptoriumAI candidate only. Do not let it redefine the current stack. Integrate only if a later audit proves it fills a real gap in the existing surfaces such as Dashboard, Editor, Corpus Graph, Runboard, AI Kanban, Corpus Search, Patch Review Queue, Visualizations, Whiteboard, Mind Map, PDF Intake, AI Diagram Studio, Video Studio, Research Agent, New Research Topic, Skills Manager, OpenAPI Routing, Manim Sandbox, Settings.","Repurpose here means mining for specific modules, algorithms, UI patterns, ingestion logic, workflow ideas, or export formats rather than assuming a full product transplant.",manimcommunity/manim,remotion-dev/remotion,native/ScriptoriumAI-Visualizer,"Return concrete files/modules/adapters worth reusing and a verdict on whether the current reanchored bucket should be kept, upgraded, or downgraded.",Do not treat licensing as a filter. Do not propose replacing native foundations unless source evidence is overwhelming.,prime126/manim-fontawesome,v6_unified_source_of_truth_pack,"Before recommending direct code use, inspect the target repo row in the v6.1 operational/phase/source-audit boards. Respect copyleft_strategy_v6_1, preferred_boundary_model_v6_1, and open_compliance_if_used_as_is_v6_1. Do not assume reverse engineering is mandatory or that as-is use is always sensible.","If the repo-level strategy says bounded_sidecar_preferred or boundary_first_then_decide_as_is_vs_reimplementation, audit clean interfaces, protocol seams, subprocess/container boundaries, and what would be required to reimplement only the strategically necessary portions.",v6.3_final_source_of_truth
SCR_0222,,,,,,,,,,ScriptoriumAI repo packet,ScriptoriumAI,ScriptoriumAI re-anchored VS Code packets v1,rasbt/LLMs-from-scratch,rasbt/llms-from-scratch,Candidate Bench,P3,bookmark candidate only,"Audit rasbt/LLMs-from-scratch for ScriptoriumAI. Start from the reanchored bucket 'Candidate Bench' and current reality status 'bookmark candidate only'. Confirm actual implemented capability, hidden reusable modules, extension seams, and whether it strengthens the existing Unimplemented but relevant candidate lane. Focus on: 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 planner loops, tool registries, MCP servers/clients, prompt/skill folders, memory stores, approval gates, background-job orchestration, and undocumented provider adapters.","Treat as unimplemented ScriptoriumAI candidate only. Do not let it redefine the current stack. Integrate only if a later audit proves it fills a real gap in the existing surfaces such as Dashboard, Editor, Corpus Graph, Runboard, AI Kanban, Corpus Search, Patch Review Queue, Visualizations, Whiteboard, Mind Map, PDF Intake, AI Diagram Studio, Video Studio, Research Agent, New Research Topic, Skills Manager, OpenAPI Routing, Manim Sandbox, Settings.","Repurpose here means mining for specific modules, algorithms, UI patterns, ingestion logic, workflow ideas, or export formats rather than assuming a full product transplant.",native/scriptoriumai-ui,native/ScriptoriumAI-Server,abhigyanpatwari/GitNexus,"Return concrete files/modules/adapters worth reusing and a verdict on whether the current reanchored bucket should be kept, upgraded, or downgraded.",Do not treat licensing as a filter. Do not propose replacing native foundations unless source evidence is overwhelming.,rasbt/llms-from-scratch,v6_unified_source_of_truth_pack,"Before recommending direct code use, inspect the target repo row in the v6.1 operational/phase/source-audit boards. Respect copyleft_strategy_v6_1, preferred_boundary_model_v6_1, and open_compliance_if_used_as_is_v6_1. Do not assume reverse engineering is mandatory or that as-is use is always sensible.","If the repo-level strategy says bounded_sidecar_preferred or boundary_first_then_decide_as_is_vs_reimplementation, audit clean interfaces, protocol seams, subprocess/container boundaries, and what would be required to reimplement only the strategically necessary portions.",v6.3_final_source_of_truth
SCR_0223,,,,,,,,,,ScriptoriumAI repo packet,ScriptoriumAI,ScriptoriumAI re-anchored VS Code packets v1,rasmusrendal/manim-revealjs,rasmusrendal/manim-revealjs,Candidate Bench,P3,bookmark candidate only,"Audit rasmusrendal/manim-revealjs for ScriptoriumAI. Start from the reanchored bucket 'Candidate Bench' and current reality status 'bookmark candidate only'. Confirm actual implemented capability, hidden reusable modules, extension seams, and whether it strengthens the existing Unimplemented but relevant candidate lane. Focus on: Inspect hidden modules, extension seams, data contracts, rendering paths, auth/storage coupling, and export/import boundaries.",,"Treat as unimplemented ScriptoriumAI candidate only. Do not let it redefine the current stack. Integrate only if a later audit proves it fills a real gap in the existing surfaces such as Dashboard, Editor, Corpus Graph, Runboard, AI Kanban, Corpus Search, Patch Review Queue, Visualizations, Whiteboard, Mind Map, PDF Intake, AI Diagram Studio, Video Studio, Research Agent, New Research Topic, Skills Manager, OpenAPI Routing, Manim Sandbox, Settings.","Repurpose here means mining for specific modules, algorithms, UI patterns, ingestion logic, workflow ideas, or export formats rather than assuming a full product transplant.",manimcommunity/manim,remotion-dev/remotion,native/ScriptoriumAI-Visualizer,"Return concrete files/modules/adapters worth reusing and a verdict on whether the current reanchored bucket should be kept, upgraded, or downgraded.",Do not treat licensing as a filter. Do not propose replacing native foundations unless source evidence is overwhelming.,rasmusrendal/manim-revealjs,v6_unified_source_of_truth_pack,"Before recommending direct code use, inspect the target repo row in the v6.1 operational/phase/source-audit boards. Respect copyleft_strategy_v6_1, preferred_boundary_model_v6_1, and open_compliance_if_used_as_is_v6_1. Do not assume reverse engineering is mandatory or that as-is use is always sensible.","If the repo-level strategy says bounded_sidecar_preferred or boundary_first_then_decide_as_is_vs_reimplementation, audit clean interfaces, protocol seams, subprocess/container boundaries, and what would be required to reimplement only the strategically necessary portions.",v6.3_final_source_of_truth
SCR_0224,,,,,,,,,,ScriptoriumAI repo packet,ScriptoriumAI,ScriptoriumAI re-anchored VS Code packets v1,rasmusrendal/manimgl-shaders,rasmusrendal/manimgl-shaders,Candidate Bench,P3,bookmark candidate only,"Audit rasmusrendal/manimgl-shaders for ScriptoriumAI. Start from the reanchored bucket 'Candidate Bench' and current reality status 'bookmark candidate only'. Confirm actual implemented capability, hidden reusable modules, extension seams, and whether it strengthens the existing Unimplemented but relevant candidate lane. Focus on: Inspect hidden modules, extension seams, data contracts, rendering paths, auth/storage coupling, and export/import boundaries.",,"Treat as unimplemented ScriptoriumAI candidate only. Do not let it redefine the current stack. Integrate only if a later audit proves it fills a real gap in the existing surfaces such as Dashboard, Editor, Corpus Graph, Runboard, AI Kanban, Corpus Search, Patch Review Queue, Visualizations, Whiteboard, Mind Map, PDF Intake, AI Diagram Studio, Video Studio, Research Agent, New Research Topic, Skills Manager, OpenAPI Routing, Manim Sandbox, Settings.","Repurpose here means mining for specific modules, algorithms, UI patterns, ingestion logic, workflow ideas, or export formats rather than assuming a full product transplant.",manimcommunity/manim,remotion-dev/remotion,native/ScriptoriumAI-Visualizer,"Return concrete files/modules/adapters worth reusing and a verdict on whether the current reanchored bucket should be kept, upgraded, or downgraded.",Do not treat licensing as a filter. Do not propose replacing native foundations unless source evidence is overwhelming.,rasmusrendal/manimgl-shaders,v6_unified_source_of_truth_pack,"Before recommending direct code use, inspect the target repo row in the v6.1 operational/phase/source-audit boards. Respect copyleft_strategy_v6_1, preferred_boundary_model_v6_1, and open_compliance_if_used_as_is_v6_1. Do not assume reverse engineering is mandatory or that as-is use is always sensible.","If the repo-level strategy says bounded_sidecar_preferred or boundary_first_then_decide_as_is_vs_reimplementation, audit clean interfaces, protocol seams, subprocess/container boundaries, and what would be required to reimplement only the strategically necessary portions.",v6.3_final_source_of_truth
SCR_0225,,,,,,,,,,ScriptoriumAI repo packet,ScriptoriumAI,ScriptoriumAI re-anchored VS Code packets v1,rdgao/manim_plotly,rdgao/manim_plotly,Candidate Bench,P3,bookmark candidate only,"Audit rdgao/manim_plotly for ScriptoriumAI. Start from the reanchored bucket 'Candidate Bench' and current reality status 'bookmark candidate only'. Confirm actual implemented capability, hidden reusable modules, extension seams, and whether it strengthens the existing Unimplemented but relevant candidate lane. Focus on: Inspect hidden modules, extension seams, data contracts, rendering paths, auth/storage coupling, and export/import boundaries.",,"Treat as unimplemented ScriptoriumAI candidate only. Do not let it redefine the current stack. Integrate only if a later audit proves it fills a real gap in the existing surfaces such as Dashboard, Editor, Corpus Graph, Runboard, AI Kanban, Corpus Search, Patch Review Queue, Visualizations, Whiteboard, Mind Map, PDF Intake, AI Diagram Studio, Video Studio, Research Agent, New Research Topic, Skills Manager, OpenAPI Routing, Manim Sandbox, Settings.","Repurpose here means mining for specific modules, algorithms, UI patterns, ingestion logic, workflow ideas, or export formats rather than assuming a full product transplant.",manimcommunity/manim,remotion-dev/remotion,native/ScriptoriumAI-Visualizer,"Return concrete files/modules/adapters worth reusing and a verdict on whether the current reanchored bucket should be kept, upgraded, or downgraded.",Do not treat licensing as a filter. Do not propose replacing native foundations unless source evidence is overwhelming.,rdgao/manim_plotly,v6_unified_source_of_truth_pack,"Before recommending direct code use, inspect the target repo row in the v6.1 operational/phase/source-audit boards. Respect copyleft_strategy_v6_1, preferred_boundary_model_v6_1, and open_compliance_if_used_as_is_v6_1. Do not assume reverse engineering is mandatory or that as-is use is always sensible.","If the repo-level strategy says bounded_sidecar_preferred or boundary_first_then_decide_as_is_vs_reimplementation, audit clean interfaces, protocol seams, subprocess/container boundaries, and what would be required to reimplement only the strategically necessary portions.",v6.3_final_source_of_truth
SCR_0226,,,,,,,,,,ScriptoriumAI repo packet,ScriptoriumAI,ScriptoriumAI re-anchored VS Code packets v1,resemble-ai/chatterbox,resemble-ai/chatterbox,Candidate Bench,P3,bookmark candidate only,"Audit resemble-ai/chatterbox for ScriptoriumAI. Start from the reanchored bucket 'Candidate Bench' and current reality status 'bookmark candidate only'. Confirm actual implemented capability, hidden reusable modules, extension seams, and whether it strengthens the existing Unimplemented but relevant candidate lane. Focus on: 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 calibration routines, detection heuristics/models, color/state normalization, replay serialization, solver bridges, camera abstraction layers, and debug visualizations.","Treat as unimplemented ScriptoriumAI candidate only. Do not let it redefine the current stack. Integrate only if a later audit proves it fills a real gap in the existing surfaces such as Dashboard, Editor, Corpus Graph, Runboard, AI Kanban, Corpus Search, Patch Review Queue, Visualizations, Whiteboard, Mind Map, PDF Intake, AI Diagram Studio, Video Studio, Research Agent, New Research Topic, Skills Manager, OpenAPI Routing, Manim Sandbox, Settings.","Repurpose here means mining for specific modules, algorithms, UI patterns, ingestion logic, workflow ideas, or export formats rather than assuming a full product transplant.",native/scriptoriumai-ui,native/ScriptoriumAI-Server,abhigyanpatwari/GitNexus,"Return concrete files/modules/adapters worth reusing and a verdict on whether the current reanchored bucket should be kept, upgraded, or downgraded.",Do not treat licensing as a filter. Do not propose replacing native foundations unless source evidence is overwhelming.,resemble-ai/chatterbox,v6_unified_source_of_truth_pack,"Before recommending direct code use, inspect the target repo row in the v6.1 operational/phase/source-audit boards. Respect copyleft_strategy_v6_1, preferred_boundary_model_v6_1, and open_compliance_if_used_as_is_v6_1. Do not assume reverse engineering is mandatory or that as-is use is always sensible.","If the repo-level strategy says bounded_sidecar_preferred or boundary_first_then_decide_as_is_vs_reimplementation, audit clean interfaces, protocol seams, subprocess/container boundaries, and what would be required to reimplement only the strategically necessary portions.",v6.3_final_source_of_truth
SCR_0227,,,,,,,,,,ScriptoriumAI repo packet,ScriptoriumAI,ScriptoriumAI re-anchored VS Code packets v1,rokpiy/auto-commenter,rokpiy/auto-commenter,Candidate Bench,P3,bookmark candidate only,"Audit rokpiy/auto-commenter for ScriptoriumAI. Start from the reanchored bucket 'Candidate Bench' and current reality status 'bookmark candidate only'. Confirm actual implemented capability, hidden reusable modules, extension seams, and whether it strengthens the existing Unimplemented but relevant candidate lane. Focus on: Inspect planner/task graph; provider abstraction; tool registry or MCP bridges; memory/state schema; approvals/retries; telemetry/event bus; plugin or skill loading 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 hidden admin tools, reusable services, plugin systems, import/export, analytics, background jobs, and any engine more valuable than the public README suggests.","Treat as unimplemented ScriptoriumAI candidate only. Do not let it redefine the current stack. Integrate only if a later audit proves it fills a real gap in the existing surfaces such as Dashboard, Editor, Corpus Graph, Runboard, AI Kanban, Corpus Search, Patch Review Queue, Visualizations, Whiteboard, Mind Map, PDF Intake, AI Diagram Studio, Video Studio, Research Agent, New Research Topic, Skills Manager, OpenAPI Routing, Manim Sandbox, Settings.","Repurpose here means mining for specific modules, algorithms, UI patterns, ingestion logic, workflow ideas, or export formats rather than assuming a full product transplant.",native/scriptoriumai-ui,native/ScriptoriumAI-Server,sharelatex/sharelatex,"Return concrete files/modules/adapters worth reusing and a verdict on whether the current reanchored bucket should be kept, upgraded, or downgraded.",Do not treat licensing as a filter. Do not propose replacing native foundations unless source evidence is overwhelming.,rokpiy/auto-commenter,v6_unified_source_of_truth_pack,"Before recommending direct code use, inspect the target repo row in the v6.1 operational/phase/source-audit boards. Respect copyleft_strategy_v6_1, preferred_boundary_model_v6_1, and open_compliance_if_used_as_is_v6_1. Do not assume reverse engineering is mandatory or that as-is use is always sensible.","If the repo-level strategy says bounded_sidecar_preferred or boundary_first_then_decide_as_is_vs_reimplementation, audit clean interfaces, protocol seams, subprocess/container boundaries, and what would be required to reimplement only the strategically necessary portions.",v6.3_final_source_of_truth
SCR_0228,,,,,,,,,,ScriptoriumAI repo packet,ScriptoriumAI,ScriptoriumAI re-anchored VS Code packets v1,ruc-datalab/DeepAnalyze,ruc-datalab/deepanalyze,Candidate Bench,P3,bookmark candidate only,"Audit ruc-datalab/DeepAnalyze for ScriptoriumAI. Start from the reanchored bucket 'Candidate Bench' and current reality status 'bookmark candidate only'. Confirm actual implemented capability, hidden reusable modules, extension seams, and whether it strengthens the existing Unimplemented but relevant candidate lane. Focus on: Inspect planner/task graph; provider abstraction; tool registry or MCP bridges; memory/state schema; approvals/retries; telemetry/event bus; plugin or skill loading 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 planner loops, tool registries, MCP servers/clients, prompt/skill folders, memory stores, approval gates, background-job orchestration, and undocumented provider adapters.","Treat as unimplemented ScriptoriumAI candidate only. Do not let it redefine the current stack. Integrate only if a later audit proves it fills a real gap in the existing surfaces such as Dashboard, Editor, Corpus Graph, Runboard, AI Kanban, Corpus Search, Patch Review Queue, Visualizations, Whiteboard, Mind Map, PDF Intake, AI Diagram Studio, Video Studio, Research Agent, New Research Topic, Skills Manager, OpenAPI Routing, Manim Sandbox, Settings.","Repurpose here means mining for specific modules, algorithms, UI patterns, ingestion logic, workflow ideas, or export formats rather than assuming a full product transplant.",native/ScriptoriumAI-Server,stanford-oval/storm,abhigyanpatwari/GitNexus,"Return concrete files/modules/adapters worth reusing and a verdict on whether the current reanchored bucket should be kept, upgraded, or downgraded.",Do not treat licensing as a filter. Do not propose replacing native foundations unless source evidence is overwhelming.,ruc-datalab/deepanalyze,v6_unified_source_of_truth_pack,"Before recommending direct code use, inspect the target repo row in the v6.1 operational/phase/source-audit boards. Respect copyleft_strategy_v6_1, preferred_boundary_model_v6_1, and open_compliance_if_used_as_is_v6_1. Do not assume reverse engineering is mandatory or that as-is use is always sensible.","If the repo-level strategy says bounded_sidecar_preferred or boundary_first_then_decide_as_is_vs_reimplementation, audit clean interfaces, protocol seams, subprocess/container boundaries, and what would be required to reimplement only the strategically necessary portions.",v6.3_final_source_of_truth
SCR_0229,,,,,,,,,,ScriptoriumAI repo packet,ScriptoriumAI,ScriptoriumAI re-anchored VS Code packets v1,saber-nyan/manim-markdown,saber-nyan/manim-markdown,Candidate Bench,P3,bookmark candidate only,"Audit saber-nyan/manim-markdown for ScriptoriumAI. Start from the reanchored bucket 'Candidate Bench' and current reality status 'bookmark candidate only'. Confirm actual implemented capability, hidden reusable modules, extension seams, and whether it strengthens the existing Unimplemented but relevant candidate lane. Focus on: Inspect hidden modules, extension seams, data contracts, rendering paths, auth/storage coupling, and export/import boundaries.",,"Treat as unimplemented ScriptoriumAI candidate only. Do not let it redefine the current stack. Integrate only if a later audit proves it fills a real gap in the existing surfaces such as Dashboard, Editor, Corpus Graph, Runboard, AI Kanban, Corpus Search, Patch Review Queue, Visualizations, Whiteboard, Mind Map, PDF Intake, AI Diagram Studio, Video Studio, Research Agent, New Research Topic, Skills Manager, OpenAPI Routing, Manim Sandbox, Settings.","Repurpose here means mining for specific modules, algorithms, UI patterns, ingestion logic, workflow ideas, or export formats rather than assuming a full product transplant.",manimcommunity/manim,remotion-dev/remotion,native/ScriptoriumAI-Visualizer,"Return concrete files/modules/adapters worth reusing and a verdict on whether the current reanchored bucket should be kept, upgraded, or downgraded.",Do not treat licensing as a filter. Do not propose replacing native foundations unless source evidence is overwhelming.,saber-nyan/manim-markdown,v6_unified_source_of_truth_pack,"Before recommending direct code use, inspect the target repo row in the v6.1 operational/phase/source-audit boards. Respect copyleft_strategy_v6_1, preferred_boundary_model_v6_1, and open_compliance_if_used_as_is_v6_1. Do not assume reverse engineering is mandatory or that as-is use is always sensible.","If the repo-level strategy says bounded_sidecar_preferred or boundary_first_then_decide_as_is_vs_reimplementation, audit clean interfaces, protocol seams, subprocess/container boundaries, and what would be required to reimplement only the strategically necessary portions.",v6.3_final_source_of_truth
SCR_0230,,,,,,,,,,ScriptoriumAI repo packet,ScriptoriumAI,ScriptoriumAI re-anchored VS Code packets v1,sakanaai/ai-scientist,sakanaai/ai-scientist,Candidate Bench,P3,not in implemented architecture snapshot,"Audit sakanaai/ai-scientist for ScriptoriumAI. Start from the reanchored bucket 'Candidate Bench' and current reality status 'not in implemented architecture snapshot'. Confirm actual implemented capability, hidden reusable modules, extension seams, and whether it strengthens the existing Research-generation candidate lane. Focus on: Inspect planner/task graph; provider abstraction; tool registry or MCP bridges; memory/state schema; approvals/retries; telemetry/event bus; plugin or skill loading 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 document/block schema, sync/conflict logic, citation handling, editor plugins, export/render pipeline, prompt chains, report assembly, and collaborative presence code.","Treat as unimplemented ScriptoriumAI candidate only. Do not let it redefine the current stack. Integrate only if a later audit proves it fills a real gap in the existing surfaces such as Dashboard, Editor, Corpus Graph, Runboard, AI Kanban, Corpus Search, Patch Review Queue, Visualizations, Whiteboard, Mind Map, PDF Intake, AI Diagram Studio, Video Studio, Research Agent, New Research Topic, Skills Manager, OpenAPI Routing, Manim Sandbox, Settings.","Repurpose here means mining for specific modules, algorithms, UI patterns, ingestion logic, workflow ideas, or export formats rather than assuming a full product transplant.",native/scriptoriumai-ui,native/ScriptoriumAI-Server,abhigyanpatwari/GitNexus,"Return concrete files/modules/adapters worth reusing and a verdict on whether the current reanchored bucket should be kept, upgraded, or downgraded.",Do not treat licensing as a filter. Do not propose replacing native foundations unless source evidence is overwhelming.,sakanaai/ai-scientist,v6_unified_source_of_truth_pack,"Before recommending direct code use, inspect the target repo row in the v6.1 operational/phase/source-audit boards. Respect copyleft_strategy_v6_1, preferred_boundary_model_v6_1, and open_compliance_if_used_as_is_v6_1. Do not assume reverse engineering is mandatory or that as-is use is always sensible.","If the repo-level strategy says bounded_sidecar_preferred or boundary_first_then_decide_as_is_vs_reimplementation, audit clean interfaces, protocol seams, subprocess/container boundaries, and what would be required to reimplement only the strategically necessary portions.",v6.3_final_source_of_truth
SCR_0231,,,,,,,,,,ScriptoriumAI repo packet,ScriptoriumAI,ScriptoriumAI re-anchored VS Code packets v1,sharbelxyz/nova-youtube-agent,sharbelxyz/nova-youtube-agent,Candidate Bench,P3,bookmark candidate only,"Audit sharbelxyz/nova-youtube-agent for ScriptoriumAI. Start from the reanchored bucket 'Candidate Bench' and current reality status 'bookmark candidate only'. Confirm actual implemented capability, hidden reusable modules, extension seams, and whether it strengthens the existing Unimplemented but relevant candidate lane. Focus on: Inspect planner/task graph; provider abstraction; tool registry or MCP bridges; memory/state schema; approvals/retries; telemetry/event bus; plugin or skill loading 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 planner loops, tool registries, MCP servers/clients, prompt/skill folders, memory stores, approval gates, background-job orchestration, and undocumented provider adapters.","Treat as unimplemented ScriptoriumAI candidate only. Do not let it redefine the current stack. Integrate only if a later audit proves it fills a real gap in the existing surfaces such as Dashboard, Editor, Corpus Graph, Runboard, AI Kanban, Corpus Search, Patch Review Queue, Visualizations, Whiteboard, Mind Map, PDF Intake, AI Diagram Studio, Video Studio, Research Agent, New Research Topic, Skills Manager, OpenAPI Routing, Manim Sandbox, Settings.","Repurpose here means mining for specific modules, algorithms, UI patterns, ingestion logic, workflow ideas, or export formats rather than assuming a full product transplant.",native/ScriptoriumAI-Server,stanford-oval/storm,abhigyanpatwari/GitNexus,"Return concrete files/modules/adapters worth reusing and a verdict on whether the current reanchored bucket should be kept, upgraded, or downgraded.",Do not treat licensing as a filter. Do not propose replacing native foundations unless source evidence is overwhelming.,sharbelxyz/nova-youtube-agent,v6_unified_source_of_truth_pack,"Before recommending direct code use, inspect the target repo row in the v6.1 operational/phase/source-audit boards. Respect copyleft_strategy_v6_1, preferred_boundary_model_v6_1, and open_compliance_if_used_as_is_v6_1. Do not assume reverse engineering is mandatory or that as-is use is always sensible.","If the repo-level strategy says bounded_sidecar_preferred or boundary_first_then_decide_as_is_vs_reimplementation, audit clean interfaces, protocol seams, subprocess/container boundaries, and what would be required to reimplement only the strategically necessary portions.",v6.3_final_source_of_truth
SCR_0232,,,,,,,,,,ScriptoriumAI repo packet,ScriptoriumAI,ScriptoriumAI re-anchored VS Code packets v1,slidevjs/slidev,slidevjs/slidev,Candidate Bench,P3,bookmark candidate only,"Audit slidevjs/slidev for ScriptoriumAI. Start from the reanchored bucket 'Candidate Bench' and current reality status 'bookmark candidate only'. Confirm actual implemented capability, hidden reusable modules, extension seams, and whether it strengthens the existing Unimplemented but relevant candidate lane. Focus on: Inspect document/block schema; sync/persistence model; permissions and sharing; citation/external-source pipeline; import/export adapters; plugin/extension points; editor rendering model.","Inspect package manifests, README/docs, src tree, examples, tests, CI workflows, config files, migrations/schemas, and hidden feature flags or experimental modules. Look for document/block schema, sync/conflict logic, citation handling, editor plugins, export/render pipeline, prompt chains, report assembly, and collaborative presence code.","Treat as unimplemented ScriptoriumAI candidate only. Do not let it redefine the current stack. Integrate only if a later audit proves it fills a real gap in the existing surfaces such as Dashboard, Editor, Corpus Graph, Runboard, AI Kanban, Corpus Search, Patch Review Queue, Visualizations, Whiteboard, Mind Map, PDF Intake, AI Diagram Studio, Video Studio, Research Agent, New Research Topic, Skills Manager, OpenAPI Routing, Manim Sandbox, Settings.","Repurpose here means mining for specific modules, algorithms, UI patterns, ingestion logic, workflow ideas, or export formats rather than assuming a full product transplant.",pdfmd/pdfmd,lukas-blecher/latex-ocr,mli55/pdfdelta,"Return concrete files/modules/adapters worth reusing and a verdict on whether the current reanchored bucket should be kept, upgraded, or downgraded.",Do not treat licensing as a filter. Do not propose replacing native foundations unless source evidence is overwhelming.,slidevjs/slidev,v6_unified_source_of_truth_pack,"Before recommending direct code use, inspect the target repo row in the v6.1 operational/phase/source-audit boards. Respect copyleft_strategy_v6_1, preferred_boundary_model_v6_1, and open_compliance_if_used_as_is_v6_1. Do not assume reverse engineering is mandatory or that as-is use is always sensible.","If the repo-level strategy says bounded_sidecar_preferred or boundary_first_then_decide_as_is_vs_reimplementation, audit clean interfaces, protocol seams, subprocess/container boundaries, and what would be required to reimplement only the strategically necessary portions.",v6.3_final_source_of_truth
SCR_0233,,,,,,,,,,ScriptoriumAI repo packet,ScriptoriumAI,ScriptoriumAI re-anchored VS Code packets v1,supertokens/supertokens-auth-react,supertokens/supertokens-auth-react,Candidate Bench,P3,bookmark candidate only,"Audit supertokens/supertokens-auth-react for ScriptoriumAI. Start from the reanchored bucket 'Candidate Bench' and current reality status 'bookmark candidate only'. Confirm actual implemented capability, hidden reusable modules, extension seams, and whether it strengthens the existing Unimplemented but relevant candidate lane. Focus on: Inspect scan engine; rule/template packs; protocol handlers; result schema normalization; auth/session handling; enrichment/correlation pipeline; evidence/report exporters; distributed runner support.","Inspect package manifests, README/docs, src tree, examples, tests, CI workflows, config files, migrations/schemas, and hidden feature flags or experimental modules. Look for template packs, protocol adapters, scan schedulers, passive-recon modules, fingerprinting, evidence schemas, diff/baseline logic, and plugin hooks for new scanners.","Treat as unimplemented ScriptoriumAI candidate only. Do not let it redefine the current stack. Integrate only if a later audit proves it fills a real gap in the existing surfaces such as Dashboard, Editor, Corpus Graph, Runboard, AI Kanban, Corpus Search, Patch Review Queue, Visualizations, Whiteboard, Mind Map, PDF Intake, AI Diagram Studio, Video Studio, Research Agent, New Research Topic, Skills Manager, OpenAPI Routing, Manim Sandbox, Settings.","Repurpose here means mining for specific modules, algorithms, UI patterns, ingestion logic, workflow ideas, or export formats rather than assuming a full product transplant.",native/scriptoriumai-ui,native/ScriptoriumAI-Server,sharelatex/sharelatex,"Return concrete files/modules/adapters worth reusing and a verdict on whether the current reanchored bucket should be kept, upgraded, or downgraded.",Do not treat licensing as a filter. Do not propose replacing native foundations unless source evidence is overwhelming.,supertokens/supertokens-auth-react,v6_unified_source_of_truth_pack,"Before recommending direct code use, inspect the target repo row in the v6.1 operational/phase/source-audit boards. Respect copyleft_strategy_v6_1, preferred_boundary_model_v6_1, and open_compliance_if_used_as_is_v6_1. Do not assume reverse engineering is mandatory or that as-is use is always sensible.","If the repo-level strategy says bounded_sidecar_preferred or boundary_first_then_decide_as_is_vs_reimplementation, audit clean interfaces, protocol seams, subprocess/container boundaries, and what would be required to reimplement only the strategically necessary portions.",v6.3_final_source_of_truth
SCR_0234,,,,,,,,,,ScriptoriumAI repo packet,ScriptoriumAI,ScriptoriumAI re-anchored VS Code packets v1,tencentmusic/supersonic,tencentmusic/supersonic,Candidate Bench,P3,bookmark candidate only,"Audit tencentmusic/supersonic for ScriptoriumAI. Start from the reanchored bucket 'Candidate Bench' and current reality status 'bookmark candidate only'. Confirm actual implemented capability, hidden reusable modules, extension seams, and whether it strengthens the existing Unimplemented but relevant candidate lane. Focus on: 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 calibration routines, detection heuristics/models, color/state normalization, replay serialization, solver bridges, camera abstraction layers, and debug visualizations.","Treat as unimplemented ScriptoriumAI candidate only. Do not let it redefine the current stack. Integrate only if a later audit proves it fills a real gap in the existing surfaces such as Dashboard, Editor, Corpus Graph, Runboard, AI Kanban, Corpus Search, Patch Review Queue, Visualizations, Whiteboard, Mind Map, PDF Intake, AI Diagram Studio, Video Studio, Research Agent, New Research Topic, Skills Manager, OpenAPI Routing, Manim Sandbox, Settings.","Repurpose here means mining for specific modules, algorithms, UI patterns, ingestion logic, workflow ideas, or export formats rather than assuming a full product transplant.",native/scriptoriumai-ui,native/ScriptoriumAI-Server,abhigyanpatwari/GitNexus,"Return concrete files/modules/adapters worth reusing and a verdict on whether the current reanchored bucket should be kept, upgraded, or downgraded.",Do not treat licensing as a filter. Do not propose replacing native foundations unless source evidence is overwhelming.,tencentmusic/supersonic,v6_unified_source_of_truth_pack,"Before recommending direct code use, inspect the target repo row in the v6.1 operational/phase/source-audit boards. Respect copyleft_strategy_v6_1, preferred_boundary_model_v6_1, and open_compliance_if_used_as_is_v6_1. Do not assume reverse engineering is mandatory or that as-is use is always sensible.","If the repo-level strategy says bounded_sidecar_preferred or boundary_first_then_decide_as_is_vs_reimplementation, audit clean interfaces, protocol seams, subprocess/container boundaries, and what would be required to reimplement only the strategically necessary portions.",v6.3_final_source_of_truth
SCR_0235,,,,,,,,,,ScriptoriumAI repo packet,ScriptoriumAI,ScriptoriumAI re-anchored VS Code packets v1,timescale/pg-aiguide,timescale/pg-aiguide,Candidate Bench,P3,bookmark candidate only,"Audit timescale/pg-aiguide for ScriptoriumAI. Start from the reanchored bucket 'Candidate Bench' and current reality status 'bookmark candidate only'. Confirm actual implemented capability, hidden reusable modules, extension seams, and whether it strengthens the existing Unimplemented but relevant candidate lane. Focus on: Inspect planner/task graph; provider abstraction; tool registry or MCP bridges; memory/state schema; approvals/retries; telemetry/event bus; plugin or skill loading 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 planner loops, tool registries, MCP servers/clients, prompt/skill folders, memory stores, approval gates, background-job orchestration, and undocumented provider adapters.","Treat as unimplemented ScriptoriumAI candidate only. Do not let it redefine the current stack. Integrate only if a later audit proves it fills a real gap in the existing surfaces such as Dashboard, Editor, Corpus Graph, Runboard, AI Kanban, Corpus Search, Patch Review Queue, Visualizations, Whiteboard, Mind Map, PDF Intake, AI Diagram Studio, Video Studio, Research Agent, New Research Topic, Skills Manager, OpenAPI Routing, Manim Sandbox, Settings.","Repurpose here means mining for specific modules, algorithms, UI patterns, ingestion logic, workflow ideas, or export formats rather than assuming a full product transplant.",native/ScriptoriumAI-Server,stanford-oval/storm,abhigyanpatwari/GitNexus,"Return concrete files/modules/adapters worth reusing and a verdict on whether the current reanchored bucket should be kept, upgraded, or downgraded.",Do not treat licensing as a filter. Do not propose replacing native foundations unless source evidence is overwhelming.,timescale/pg-aiguide,v6_unified_source_of_truth_pack,"Before recommending direct code use, inspect the target repo row in the v6.1 operational/phase/source-audit boards. Respect copyleft_strategy_v6_1, preferred_boundary_model_v6_1, and open_compliance_if_used_as_is_v6_1. Do not assume reverse engineering is mandatory or that as-is use is always sensible.","If the repo-level strategy says bounded_sidecar_preferred or boundary_first_then_decide_as_is_vs_reimplementation, audit clean interfaces, protocol seams, subprocess/container boundaries, and what would be required to reimplement only the strategically necessary portions.",v6.3_final_source_of_truth
SCR_0236,,,,,,,,,,ScriptoriumAI repo packet,ScriptoriumAI,ScriptoriumAI re-anchored VS Code packets v1,trimstray/the-book-of-secret-knowledge,trimstray/the-book-of-secret-knowledge,Candidate Bench,P3,bookmark candidate only,"Audit trimstray/the-book-of-secret-knowledge for ScriptoriumAI. Start from the reanchored bucket 'Candidate Bench' and current reality status 'bookmark candidate only'. Confirm actual implemented capability, hidden reusable modules, extension seams, and whether it strengthens the existing Unimplemented but relevant candidate lane. Focus on: 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.","Treat as unimplemented ScriptoriumAI candidate only. Do not let it redefine the current stack. Integrate only if a later audit proves it fills a real gap in the existing surfaces such as Dashboard, Editor, Corpus Graph, Runboard, AI Kanban, Corpus Search, Patch Review Queue, Visualizations, Whiteboard, Mind Map, PDF Intake, AI Diagram Studio, Video Studio, Research Agent, New Research Topic, Skills Manager, OpenAPI Routing, Manim Sandbox, Settings.","Repurpose here means mining for specific modules, algorithms, UI patterns, ingestion logic, workflow ideas, or export formats rather than assuming a full product transplant.",native/scriptoriumai-ui,native/ScriptoriumAI-Server,abhigyanpatwari/GitNexus,"Return concrete files/modules/adapters worth reusing and a verdict on whether the current reanchored bucket should be kept, upgraded, or downgraded.",Do not treat licensing as a filter. Do not propose replacing native foundations unless source evidence is overwhelming.,trimstray/the-book-of-secret-knowledge,v6_unified_source_of_truth_pack,"Before recommending direct code use, inspect the target repo row in the v6.1 operational/phase/source-audit boards. Respect copyleft_strategy_v6_1, preferred_boundary_model_v6_1, and open_compliance_if_used_as_is_v6_1. Do not assume reverse engineering is mandatory or that as-is use is always sensible.","If the repo-level strategy says bounded_sidecar_preferred or boundary_first_then_decide_as_is_vs_reimplementation, audit clean interfaces, protocol seams, subprocess/container boundaries, and what would be required to reimplement only the strategically necessary portions.",v6.3_final_source_of_truth
SCR_0237,,,,,,,,,,ScriptoriumAI repo packet,ScriptoriumAI,ScriptoriumAI re-anchored VS Code packets v1,unmoldequimica/manim-chemistry,unmoldequimica/manim-chemistry,Candidate Bench,P3,bookmark candidate only,"Audit unmoldequimica/manim-chemistry for ScriptoriumAI. Start from the reanchored bucket 'Candidate Bench' and current reality status 'bookmark candidate only'. Confirm actual implemented capability, hidden reusable modules, extension seams, and whether it strengthens the existing Unimplemented but relevant candidate lane. Focus on: Inspect hidden modules, extension seams, data contracts, rendering paths, auth/storage coupling, and export/import boundaries.",,"Treat as unimplemented ScriptoriumAI candidate only. Do not let it redefine the current stack. Integrate only if a later audit proves it fills a real gap in the existing surfaces such as Dashboard, Editor, Corpus Graph, Runboard, AI Kanban, Corpus Search, Patch Review Queue, Visualizations, Whiteboard, Mind Map, PDF Intake, AI Diagram Studio, Video Studio, Research Agent, New Research Topic, Skills Manager, OpenAPI Routing, Manim Sandbox, Settings.","Repurpose here means mining for specific modules, algorithms, UI patterns, ingestion logic, workflow ideas, or export formats rather than assuming a full product transplant.",manimcommunity/manim,remotion-dev/remotion,native/ScriptoriumAI-Visualizer,"Return concrete files/modules/adapters worth reusing and a verdict on whether the current reanchored bucket should be kept, upgraded, or downgraded.",Do not treat licensing as a filter. Do not propose replacing native foundations unless source evidence is overwhelming.,unmoldequimica/manim-chemistry,v6_unified_source_of_truth_pack,"Before recommending direct code use, inspect the target repo row in the v6.1 operational/phase/source-audit boards. Respect copyleft_strategy_v6_1, preferred_boundary_model_v6_1, and open_compliance_if_used_as_is_v6_1. Do not assume reverse engineering is mandatory or that as-is use is always sensible.","If the repo-level strategy says bounded_sidecar_preferred or boundary_first_then_decide_as_is_vs_reimplementation, audit clean interfaces, protocol seams, subprocess/container boundaries, and what would be required to reimplement only the strategically necessary portions.",v6.3_final_source_of_truth
SCR_0238,,,,,,,,,,ScriptoriumAI repo packet,ScriptoriumAI,ScriptoriumAI re-anchored VS Code packets v1,verticaltension/CompleteRubiksCube,verticaltension/completerubikscube,Candidate Bench,P3,bookmark candidate only,"Audit verticaltension/CompleteRubiksCube for ScriptoriumAI. Start from the reanchored bucket 'Candidate Bench' and current reality status 'bookmark candidate only'. Confirm actual implemented capability, hidden reusable modules, extension seams, and whether it strengthens the existing Unimplemented but relevant candidate lane. Focus on: 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.","Treat as unimplemented ScriptoriumAI candidate only. Do not let it redefine the current stack. Integrate only if a later audit proves it fills a real gap in the existing surfaces such as Dashboard, Editor, Corpus Graph, Runboard, AI Kanban, Corpus Search, Patch Review Queue, Visualizations, Whiteboard, Mind Map, PDF Intake, AI Diagram Studio, Video Studio, Research Agent, New Research Topic, Skills Manager, OpenAPI Routing, Manim Sandbox, Settings.","Repurpose here means mining for specific modules, algorithms, UI patterns, ingestion logic, workflow ideas, or export formats rather than assuming a full product transplant.",native/scriptoriumai-ui,native/ScriptoriumAI-Server,abhigyanpatwari/GitNexus,"Return concrete files/modules/adapters worth reusing and a verdict on whether the current reanchored bucket should be kept, upgraded, or downgraded.",Do not treat licensing as a filter. Do not propose replacing native foundations unless source evidence is overwhelming.,verticaltension/completerubikscube,v6_unified_source_of_truth_pack,"Before recommending direct code use, inspect the target repo row in the v6.1 operational/phase/source-audit boards. Respect copyleft_strategy_v6_1, preferred_boundary_model_v6_1, and open_compliance_if_used_as_is_v6_1. Do not assume reverse engineering is mandatory or that as-is use is always sensible.","If the repo-level strategy says bounded_sidecar_preferred or boundary_first_then_decide_as_is_vs_reimplementation, audit clean interfaces, protocol seams, subprocess/container boundaries, and what would be required to reimplement only the strategically necessary portions.",v6.3_final_source_of_truth
SCR_0239,,,,,,,,,,ScriptoriumAI repo packet,ScriptoriumAI,ScriptoriumAI re-anchored VS Code packets v1,outline/outline,outline/outline,Comparator / Legacy,P2,not in implemented architecture snapshot,"Audit outline/outline for ScriptoriumAI. Start from the reanchored bucket 'Comparator / Legacy' and current reality status 'not in implemented architecture snapshot'. Confirm actual implemented capability, hidden reusable modules, extension seams, and whether it strengthens the existing Alternative knowledge base / docs substrate comparator lane. Focus on: 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.","Treat as unimplemented ScriptoriumAI candidate only. Do not let it redefine the current stack. Integrate only if a later audit proves it fills a real gap in the existing surfaces such as Dashboard, Editor, Corpus Graph, Runboard, AI Kanban, Corpus Search, Patch Review Queue, Visualizations, Whiteboard, Mind Map, PDF Intake, AI Diagram Studio, Video Studio, Research Agent, New Research Topic, Skills Manager, OpenAPI Routing, Manim Sandbox, Settings.","Repurpose here means mining for specific modules, algorithms, UI patterns, ingestion logic, workflow ideas, or export formats rather than assuming a full product transplant.",native/scriptoriumai-ui,native/ScriptoriumAI-Server,abhigyanpatwari/GitNexus,"Return concrete files/modules/adapters worth reusing and a verdict on whether the current reanchored bucket should be kept, upgraded, or downgraded.",Do not treat licensing as a filter. Do not propose replacing native foundations unless source evidence is overwhelming.,outline/outline,v6_unified_source_of_truth_pack,"Before recommending direct code use, inspect the target repo row in the v6.1 operational/phase/source-audit boards. Respect copyleft_strategy_v6_1, preferred_boundary_model_v6_1, and open_compliance_if_used_as_is_v6_1. Do not assume reverse engineering is mandatory or that as-is use is always sensible.","If the repo-level strategy says bounded_sidecar_preferred or boundary_first_then_decide_as_is_vs_reimplementation, audit clean interfaces, protocol seams, subprocess/container boundaries, and what would be required to reimplement only the strategically necessary portions.",v6.3_final_source_of_truth
SCR_0240,,,,,,,,,,ScriptoriumAI repo packet,ScriptoriumAI,ScriptoriumAI re-anchored VS Code packets v1,paper2all/paper2all,paper2all/paper2all,Deferred / Monitor Only,P2,**Deferred** — feasibility re-reviewed 2026-03-28. No root SPDX license file upstream; heavy runtime profile. Awaiting upstream licence clarity.,"Audit paper2all/paper2all for ScriptoriumAI. Start from the reanchored bucket 'Deferred / Monitor Only' and current reality status '**Deferred** — feasibility re-reviewed 2026-03-28. No root SPDX license file upstream; heavy runtime profile. Awaiting upstream licence clarity.'. Confirm actual implemented capability, hidden reusable modules, extension seams, and whether it strengthens the existing Paper ingestion candidate pending clarity lane. Focus on: Inspect hidden modules, extension seams, data contracts, rendering paths, auth/storage coupling, and export/import boundaries.", ; Future: PDF Intake advanced pipeline,"Ground this repo in the actual ScriptoriumAI architecture rather than treating it as speculative. Preserve the current integration boundary (see architecture snapshot) and audit for hidden reusable modules, extension points, and coupling risks. Existing powers: Future: PDF Intake advanced pipeline.","Repurpose means extracting hidden internals, adapters, schemas, UI patterns, or subservices that strengthen the existing implemented surfaces without destabilizing the current product shell.",native/ScriptoriumAI-Server,stanford-oval/storm,abhigyanpatwari/GitNexus,"Return concrete files/modules/adapters worth reusing and a verdict on whether the current reanchored bucket should be kept, upgraded, or downgraded.",Do not treat licensing as a filter. Do not propose replacing native foundations unless source evidence is overwhelming.,paper2all/paper2all,v6_unified_source_of_truth_pack,"Before recommending direct code use, inspect the target repo row in the v6.1 operational/phase/source-audit boards. Respect copyleft_strategy_v6_1, preferred_boundary_model_v6_1, and open_compliance_if_used_as_is_v6_1. Do not assume reverse engineering is mandatory or that as-is use is always sensible.","If the repo-level strategy says bounded_sidecar_preferred or boundary_first_then_decide_as_is_vs_reimplementation, audit clean interfaces, protocol seams, subprocess/container boundaries, and what would be required to reimplement only the strategically necessary portions.",v6.3_final_source_of_truth
SCR_0241,,,,,,,,,,ScriptoriumAI repo packet,ScriptoriumAI,ScriptoriumAI re-anchored VS Code packets v1,paperbanana/paperbanana,paperbanana/paperbanana,Deferred / Monitor Only,P2,**Deferred** — feasibility re-reviewed 2026-03-28. No root SPDX license file upstream; heavy runtime profile. Awaiting upstream licence clarity.,"Audit paperbanana/paperbanana for ScriptoriumAI. Start from the reanchored bucket 'Deferred / Monitor Only' and current reality status '**Deferred** — feasibility re-reviewed 2026-03-28. No root SPDX license file upstream; heavy runtime profile. Awaiting upstream licence clarity.'. Confirm actual implemented capability, hidden reusable modules, extension seams, and whether it strengthens the existing Paper ingestion candidate pending clarity lane. Focus on: Inspect hidden modules, extension seams, data contracts, rendering paths, auth/storage coupling, and export/import boundaries.", ; Future: PDF Intake advanced pipeline,"Ground this repo in the actual ScriptoriumAI architecture rather than treating it as speculative. Preserve the current integration boundary (see architecture snapshot) and audit for hidden reusable modules, extension points, and coupling risks. Existing powers: Future: PDF Intake advanced pipeline.","Repurpose means extracting hidden internals, adapters, schemas, UI patterns, or subservices that strengthen the existing implemented surfaces without destabilizing the current product shell.",native/ScriptoriumAI-Server,stanford-oval/storm,abhigyanpatwari/GitNexus,"Return concrete files/modules/adapters worth reusing and a verdict on whether the current reanchored bucket should be kept, upgraded, or downgraded.",Do not treat licensing as a filter. Do not propose replacing native foundations unless source evidence is overwhelming.,paperbanana/paperbanana,v6_unified_source_of_truth_pack,"Before recommending direct code use, inspect the target repo row in the v6.1 operational/phase/source-audit boards. Respect copyleft_strategy_v6_1, preferred_boundary_model_v6_1, and open_compliance_if_used_as_is_v6_1. Do not assume reverse engineering is mandatory or that as-is use is always sensible.","If the repo-level strategy says bounded_sidecar_preferred or boundary_first_then_decide_as_is_vs_reimplementation, audit clean interfaces, protocol seams, subprocess/container boundaries, and what would be required to reimplement only the strategically necessary portions.",v6.3_final_source_of_truth
SCR_0242,,,,,,,,,,ScriptoriumAI repo packet,ScriptoriumAI,ScriptoriumAI re-anchored VS Code packets v1,supermemoryai/supermemory,supermemoryai/supermemory,Deferred / Monitor Only,P2,"Smriti: **integrated** (see §3.11). ReMe: integrated (offline queue, session export). Supermemory: **monitor only** — future adapter candidate","Audit supermemoryai/supermemory for ScriptoriumAI. Start from the reanchored bucket 'Deferred / Monitor Only' and current reality status 'Smriti: **integrated** (see §3.11). ReMe: integrated (offline queue, session export). Supermemory: **monitor only** — future adapter candidate'. Confirm actual implemented capability, hidden reusable modules, extension seams, and whether it strengthens the existing Future long-memory candidate lane. Focus on: Inspect hidden modules, extension seams, data contracts, rendering paths, auth/storage coupling, and export/import boundaries."," ; Breathe-memory domain all 8 modules, AI Memory panel","Ground this repo in the actual ScriptoriumAI architecture rather than treating it as speculative. Preserve the current integration boundary (see architecture snapshot) and audit for hidden reusable modules, extension points, and coupling risks. Existing powers: Breathe-memory domain all 8 modules, AI Memory panel.","Repurpose means extracting hidden internals, adapters, schemas, UI patterns, or subservices that strengthen the existing implemented surfaces without destabilizing the current product shell.",native/ScriptoriumAI-Server,stanford-oval/storm,abhigyanpatwari/GitNexus,"Return concrete files/modules/adapters worth reusing and a verdict on whether the current reanchored bucket should be kept, upgraded, or downgraded.",Do not treat licensing as a filter. Do not propose replacing native foundations unless source evidence is overwhelming.,supermemoryai/supermemory,v6_unified_source_of_truth_pack,"Before recommending direct code use, inspect the target repo row in the v6.1 operational/phase/source-audit boards. Respect copyleft_strategy_v6_1, preferred_boundary_model_v6_1, and open_compliance_if_used_as_is_v6_1. Do not assume reverse engineering is mandatory or that as-is use is always sensible.","If the repo-level strategy says bounded_sidecar_preferred or boundary_first_then_decide_as_is_vs_reimplementation, audit clean interfaces, protocol seams, subprocess/container boundaries, and what would be required to reimplement only the strategically necessary portions.",v6.3_final_source_of_truth
SCR_0243,,,,,,,,,,ScriptoriumAI repo packet,ScriptoriumAI,ScriptoriumAI re-anchored VS Code packets v1,zotero/zotero,zotero/zotero,Deferred / Monitor Only,P2,Integration boundary active (event logging); deep adapter deferred,"Audit zotero/zotero for ScriptoriumAI. Start from the reanchored bucket 'Deferred / Monitor Only' and current reality status 'Integration boundary active (event logging); deep adapter deferred'. Confirm actual implemented capability, hidden reusable modules, extension seams, and whether it strengthens the existing Citation/reference adapter candidate lane. Focus on: Inspect hidden modules, extension seams, data contracts, rendering paths, auth/storage coupling, and export/import boundaries.","Integration boundary memory event type zotero; bibtex-autocomplete.js pulls from corpus DOI/ArXiv/URL chain ; Citation intelligence — BibTeX auto-completion, citation graph memory","Ground this repo in the actual ScriptoriumAI architecture rather than treating it as speculative. Preserve the current integration boundary (Integration boundary memory event type zotero; bibtex-autocomplete.js pulls from corpus DOI/ArXiv/URL chain) and audit for hidden reusable modules, extension points, and coupling risks. Existing powers: Citation intelligence — BibTeX auto-completion, citation graph memory.","Repurpose means extracting hidden internals, adapters, schemas, UI patterns, or subservices that strengthen the existing implemented surfaces without destabilizing the current product shell.",pdfmd/pdfmd,lukas-blecher/latex-ocr,mli55/pdfdelta,"Return concrete files/modules/adapters worth reusing and a verdict on whether the current reanchored bucket should be kept, upgraded, or downgraded.",Do not treat licensing as a filter. Do not propose replacing native foundations unless source evidence is overwhelming.,zotero/zotero,v6_unified_source_of_truth_pack,"Before recommending direct code use, inspect the target repo row in the v6.1 operational/phase/source-audit boards. Respect copyleft_strategy_v6_1, preferred_boundary_model_v6_1, and open_compliance_if_used_as_is_v6_1. Do not assume reverse engineering is mandatory or that as-is use is always sensible.","If the repo-level strategy says bounded_sidecar_preferred or boundary_first_then_decide_as_is_vs_reimplementation, audit clean interfaces, protocol seams, subprocess/container boundaries, and what would be required to reimplement only the strategically necessary portions.",v6.3_final_source_of_truth
SCR_0244,,,,,,,,,,ScriptoriumAI repo packet,ScriptoriumAI,ScriptoriumAI re-anchored VS Code packets v1,hkuds/openspace,hkuds/openspace,Deferred / Monitor Only,P3,**Monitor only** — not a runtime dependency,"Audit hkuds/openspace for ScriptoriumAI. Start from the reanchored bucket 'Deferred / Monitor Only' and current reality status '**Monitor only** — not a runtime dependency'. Confirm actual implemented capability, hidden reusable modules, extension seams, and whether it strengthens the existing Collaborative human-agent orchestration reference lane. Focus on: Inspect hidden modules, extension seams, data contracts, rendering paths, auth/storage coupling, and export/import boundaries.", ; Conceptual input to Research Agent swarm design,"Ground this repo in the actual ScriptoriumAI architecture rather than treating it as speculative. Preserve the current integration boundary (see architecture snapshot) and audit for hidden reusable modules, extension points, and coupling risks. Existing powers: Conceptual input to Research Agent swarm design.","Repurpose means extracting hidden internals, adapters, schemas, UI patterns, or subservices that strengthen the existing implemented surfaces without destabilizing the current product shell.",native/ScriptoriumAI-Server,stanford-oval/storm,abhigyanpatwari/GitNexus,"Return concrete files/modules/adapters worth reusing and a verdict on whether the current reanchored bucket should be kept, upgraded, or downgraded.",Do not treat licensing as a filter. Do not propose replacing native foundations unless source evidence is overwhelming.,hkuds/openspace,v6_unified_source_of_truth_pack,"Before recommending direct code use, inspect the target repo row in the v6.1 operational/phase/source-audit boards. Respect copyleft_strategy_v6_1, preferred_boundary_model_v6_1, and open_compliance_if_used_as_is_v6_1. Do not assume reverse engineering is mandatory or that as-is use is always sensible.","If the repo-level strategy says bounded_sidecar_preferred or boundary_first_then_decide_as_is_vs_reimplementation, audit clean interfaces, protocol seams, subprocess/container boundaries, and what would be required to reimplement only the strategically necessary portions.",v6.3_final_source_of_truth
SCR_0245,,,,,,,,,,ScriptoriumAI repo packet,ScriptoriumAI,ScriptoriumAI re-anchored VS Code packets v1,Anduin2017/HowToCook,anduin2017/howtocook,Exclude Current Horizon,P3,bookmark candidate only,"Audit Anduin2017/HowToCook for ScriptoriumAI. Start from the reanchored bucket 'Exclude Current Horizon' and current reality status 'bookmark candidate only'. Confirm actual implemented capability, hidden reusable modules, extension seams, and whether it strengthens the existing Off-axis candidate for current ScriptoriumAI baseline lane. Focus on: 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.","Treat as unimplemented ScriptoriumAI candidate only. Do not let it redefine the current stack. Integrate only if a later audit proves it fills a real gap in the existing surfaces such as Dashboard, Editor, Corpus Graph, Runboard, AI Kanban, Corpus Search, Patch Review Queue, Visualizations, Whiteboard, Mind Map, PDF Intake, AI Diagram Studio, Video Studio, Research Agent, New Research Topic, Skills Manager, OpenAPI Routing, Manim Sandbox, Settings.","Repurpose here means mining for specific modules, algorithms, UI patterns, ingestion logic, workflow ideas, or export formats rather than assuming a full product transplant.",native/scriptoriumai-ui,native/ScriptoriumAI-Server,abhigyanpatwari/GitNexus,"Return concrete files/modules/adapters worth reusing and a verdict on whether the current reanchored bucket should be kept, upgraded, or downgraded.",Do not treat licensing as a filter. Do not propose replacing native foundations unless source evidence is overwhelming.,anduin2017/howtocook,v6_unified_source_of_truth_pack,"Before recommending direct code use, inspect the target repo row in the v6.1 operational/phase/source-audit boards. Respect copyleft_strategy_v6_1, preferred_boundary_model_v6_1, and open_compliance_if_used_as_is_v6_1. Do not assume reverse engineering is mandatory or that as-is use is always sensible.","If the repo-level strategy says bounded_sidecar_preferred or boundary_first_then_decide_as_is_vs_reimplementation, audit clean interfaces, protocol seams, subprocess/container boundaries, and what would be required to reimplement only the strategically necessary portions.",v6.3_final_source_of_truth
SCR_0246,,,,,,,,,,ScriptoriumAI repo packet,ScriptoriumAI,ScriptoriumAI re-anchored VS Code packets v1,AvaloniaCommunity/Material.Avalonia,avaloniacommunity/material.avalonia,Exclude Current Horizon,P3,bookmark candidate only,"Audit AvaloniaCommunity/Material.Avalonia for ScriptoriumAI. Start from the reanchored bucket 'Exclude Current Horizon' and current reality status 'bookmark candidate only'. Confirm actual implemented capability, hidden reusable modules, extension seams, and whether it strengthens the existing Off-axis candidate for current ScriptoriumAI baseline lane. Focus on: 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.","Treat as unimplemented ScriptoriumAI candidate only. Do not let it redefine the current stack. Integrate only if a later audit proves it fills a real gap in the existing surfaces such as Dashboard, Editor, Corpus Graph, Runboard, AI Kanban, Corpus Search, Patch Review Queue, Visualizations, Whiteboard, Mind Map, PDF Intake, AI Diagram Studio, Video Studio, Research Agent, New Research Topic, Skills Manager, OpenAPI Routing, Manim Sandbox, Settings.","Repurpose here means mining for specific modules, algorithms, UI patterns, ingestion logic, workflow ideas, or export formats rather than assuming a full product transplant.",native/scriptoriumai-ui,native/ScriptoriumAI-Server,abhigyanpatwari/GitNexus,"Return concrete files/modules/adapters worth reusing and a verdict on whether the current reanchored bucket should be kept, upgraded, or downgraded.",Do not treat licensing as a filter. Do not propose replacing native foundations unless source evidence is overwhelming.,avaloniacommunity/material.avalonia,v6_unified_source_of_truth_pack,"Before recommending direct code use, inspect the target repo row in the v6.1 operational/phase/source-audit boards. Respect copyleft_strategy_v6_1, preferred_boundary_model_v6_1, and open_compliance_if_used_as_is_v6_1. Do not assume reverse engineering is mandatory or that as-is use is always sensible.","If the repo-level strategy says bounded_sidecar_preferred or boundary_first_then_decide_as_is_vs_reimplementation, audit clean interfaces, protocol seams, subprocess/container boundaries, and what would be required to reimplement only the strategically necessary portions.",v6.3_final_source_of_truth
SCR_0247,,,,,,,,,,ScriptoriumAI repo packet,ScriptoriumAI,ScriptoriumAI re-anchored VS Code packets v1,AvaloniaUI/Avalonia,avaloniaui/avalonia,Exclude Current Horizon,P3,bookmark candidate only,"Audit AvaloniaUI/Avalonia for ScriptoriumAI. Start from the reanchored bucket 'Exclude Current Horizon' and current reality status 'bookmark candidate only'. Confirm actual implemented capability, hidden reusable modules, extension seams, and whether it strengthens the existing Off-axis candidate for current ScriptoriumAI baseline lane. Focus on: 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 reusable canvas/editor components, design tokens, state models, keyboard shortcuts, drag/drop, accessibility, virtualization, and polished interaction patterns.","Treat as unimplemented ScriptoriumAI candidate only. Do not let it redefine the current stack. Integrate only if a later audit proves it fills a real gap in the existing surfaces such as Dashboard, Editor, Corpus Graph, Runboard, AI Kanban, Corpus Search, Patch Review Queue, Visualizations, Whiteboard, Mind Map, PDF Intake, AI Diagram Studio, Video Studio, Research Agent, New Research Topic, Skills Manager, OpenAPI Routing, Manim Sandbox, Settings.","Repurpose here means mining for specific modules, algorithms, UI patterns, ingestion logic, workflow ideas, or export formats rather than assuming a full product transplant.",native/scriptoriumai-ui,native/ScriptoriumAI-Server,abhigyanpatwari/GitNexus,"Return concrete files/modules/adapters worth reusing and a verdict on whether the current reanchored bucket should be kept, upgraded, or downgraded.",Do not treat licensing as a filter. Do not propose replacing native foundations unless source evidence is overwhelming.,avaloniaui/avalonia,v6_unified_source_of_truth_pack,"Before recommending direct code use, inspect the target repo row in the v6.1 operational/phase/source-audit boards. Respect copyleft_strategy_v6_1, preferred_boundary_model_v6_1, and open_compliance_if_used_as_is_v6_1. Do not assume reverse engineering is mandatory or that as-is use is always sensible.","If the repo-level strategy says bounded_sidecar_preferred or boundary_first_then_decide_as_is_vs_reimplementation, audit clean interfaces, protocol seams, subprocess/container boundaries, and what would be required to reimplement only the strategically necessary portions.",v6.3_final_source_of_truth
SCR_0248,,,,,,,,,,ScriptoriumAI repo packet,ScriptoriumAI,ScriptoriumAI re-anchored VS Code packets v1,AvaloniaUI/Avalonia.Labs,avaloniaui/avalonia.labs,Exclude Current Horizon,P3,bookmark candidate only,"Audit AvaloniaUI/Avalonia.Labs for ScriptoriumAI. Start from the reanchored bucket 'Exclude Current Horizon' and current reality status 'bookmark candidate only'. Confirm actual implemented capability, hidden reusable modules, extension seams, and whether it strengthens the existing Off-axis candidate for current ScriptoriumAI baseline lane. Focus on: 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.","Treat as unimplemented ScriptoriumAI candidate only. Do not let it redefine the current stack. Integrate only if a later audit proves it fills a real gap in the existing surfaces such as Dashboard, Editor, Corpus Graph, Runboard, AI Kanban, Corpus Search, Patch Review Queue, Visualizations, Whiteboard, Mind Map, PDF Intake, AI Diagram Studio, Video Studio, Research Agent, New Research Topic, Skills Manager, OpenAPI Routing, Manim Sandbox, Settings.","Repurpose here means mining for specific modules, algorithms, UI patterns, ingestion logic, workflow ideas, or export formats rather than assuming a full product transplant.",native/scriptoriumai-ui,native/ScriptoriumAI-Server,abhigyanpatwari/GitNexus,"Return concrete files/modules/adapters worth reusing and a verdict on whether the current reanchored bucket should be kept, upgraded, or downgraded.",Do not treat licensing as a filter. Do not propose replacing native foundations unless source evidence is overwhelming.,avaloniaui/avalonia.labs,v6_unified_source_of_truth_pack,"Before recommending direct code use, inspect the target repo row in the v6.1 operational/phase/source-audit boards. Respect copyleft_strategy_v6_1, preferred_boundary_model_v6_1, and open_compliance_if_used_as_is_v6_1. Do not assume reverse engineering is mandatory or that as-is use is always sensible.","If the repo-level strategy says bounded_sidecar_preferred or boundary_first_then_decide_as_is_vs_reimplementation, audit clean interfaces, protocol seams, subprocess/container boundaries, and what would be required to reimplement only the strategically necessary portions.",v6.3_final_source_of_truth
SCR_0249,,,,,,,,,,ScriptoriumAI repo packet,ScriptoriumAI,ScriptoriumAI re-anchored VS Code packets v1,AvaloniaUI/Avalonia.Xaml.Behaviors,avaloniaui/avalonia.xaml.behaviors,Exclude Current Horizon,P3,bookmark candidate only,"Audit AvaloniaUI/Avalonia.Xaml.Behaviors for ScriptoriumAI. Start from the reanchored bucket 'Exclude Current Horizon' and current reality status 'bookmark candidate only'. Confirm actual implemented capability, hidden reusable modules, extension seams, and whether it strengthens the existing Off-axis candidate for current ScriptoriumAI baseline lane. Focus on: Inspect parsers and language adapters; graph schema and storage; incremental indexing/update logic; layout engine; query API; export/import formats; test fixtures for graph correctness.","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.","Treat as unimplemented ScriptoriumAI candidate only. Do not let it redefine the current stack. Integrate only if a later audit proves it fills a real gap in the existing surfaces such as Dashboard, Editor, Corpus Graph, Runboard, AI Kanban, Corpus Search, Patch Review Queue, Visualizations, Whiteboard, Mind Map, PDF Intake, AI Diagram Studio, Video Studio, Research Agent, New Research Topic, Skills Manager, OpenAPI Routing, Manim Sandbox, Settings.","Repurpose here means mining for specific modules, algorithms, UI patterns, ingestion logic, workflow ideas, or export formats rather than assuming a full product transplant.",native/scriptoriumai-ui,native/ScriptoriumAI-Server,abhigyanpatwari/GitNexus,"Return concrete files/modules/adapters worth reusing and a verdict on whether the current reanchored bucket should be kept, upgraded, or downgraded.",Do not treat licensing as a filter. Do not propose replacing native foundations unless source evidence is overwhelming.,avaloniaui/avalonia.xaml.behaviors,v6_unified_source_of_truth_pack,"Before recommending direct code use, inspect the target repo row in the v6.1 operational/phase/source-audit boards. Respect copyleft_strategy_v6_1, preferred_boundary_model_v6_1, and open_compliance_if_used_as_is_v6_1. Do not assume reverse engineering is mandatory or that as-is use is always sensible.","If the repo-level strategy says bounded_sidecar_preferred or boundary_first_then_decide_as_is_vs_reimplementation, audit clean interfaces, protocol seams, subprocess/container boundaries, and what would be required to reimplement only the strategically necessary portions.",v6.3_final_source_of_truth
SCR_0250,,,,,,,,,,ScriptoriumAI repo packet,ScriptoriumAI,ScriptoriumAI re-anchored VS Code packets v1,AvaloniaUI/AvaloniaMauiHybrid,avaloniaui/avaloniamauihybrid,Exclude Current Horizon,P3,bookmark candidate only,"Audit AvaloniaUI/AvaloniaMauiHybrid for ScriptoriumAI. Start from the reanchored bucket 'Exclude Current Horizon' and current reality status 'bookmark candidate only'. Confirm actual implemented capability, hidden reusable modules, extension seams, and whether it strengthens the existing Off-axis candidate for current ScriptoriumAI baseline lane. Focus on: 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.","Treat as unimplemented ScriptoriumAI candidate only. Do not let it redefine the current stack. Integrate only if a later audit proves it fills a real gap in the existing surfaces such as Dashboard, Editor, Corpus Graph, Runboard, AI Kanban, Corpus Search, Patch Review Queue, Visualizations, Whiteboard, Mind Map, PDF Intake, AI Diagram Studio, Video Studio, Research Agent, New Research Topic, Skills Manager, OpenAPI Routing, Manim Sandbox, Settings.","Repurpose here means mining for specific modules, algorithms, UI patterns, ingestion logic, workflow ideas, or export formats rather than assuming a full product transplant.",native/scriptoriumai-ui,native/ScriptoriumAI-Server,abhigyanpatwari/GitNexus,"Return concrete files/modules/adapters worth reusing and a verdict on whether the current reanchored bucket should be kept, upgraded, or downgraded.",Do not treat licensing as a filter. Do not propose replacing native foundations unless source evidence is overwhelming.,avaloniaui/avaloniamauihybrid,v6_unified_source_of_truth_pack,"Before recommending direct code use, inspect the target repo row in the v6.1 operational/phase/source-audit boards. Respect copyleft_strategy_v6_1, preferred_boundary_model_v6_1, and open_compliance_if_used_as_is_v6_1. Do not assume reverse engineering is mandatory or that as-is use is always sensible.","If the repo-level strategy says bounded_sidecar_preferred or boundary_first_then_decide_as_is_vs_reimplementation, audit clean interfaces, protocol seams, subprocess/container boundaries, and what would be required to reimplement only the strategically necessary portions.",v6.3_final_source_of_truth
SCR_0251,,,,,,,,,,ScriptoriumAI repo packet,ScriptoriumAI,ScriptoriumAI re-anchored VS Code packets v1,ByteByteGoHq/system-design-101,bytebytegohq/system-design-101,Exclude Current Horizon,P3,bookmark candidate only,"Audit ByteByteGoHq/system-design-101 for ScriptoriumAI. Start from the reanchored bucket 'Exclude Current Horizon' and current reality status 'bookmark candidate only'. Confirm actual implemented capability, hidden reusable modules, extension seams, and whether it strengthens the existing Off-axis candidate for current ScriptoriumAI baseline lane. Focus on: 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.","Treat as unimplemented ScriptoriumAI candidate only. Do not let it redefine the current stack. Integrate only if a later audit proves it fills a real gap in the existing surfaces such as Dashboard, Editor, Corpus Graph, Runboard, AI Kanban, Corpus Search, Patch Review Queue, Visualizations, Whiteboard, Mind Map, PDF Intake, AI Diagram Studio, Video Studio, Research Agent, New Research Topic, Skills Manager, OpenAPI Routing, Manim Sandbox, Settings.","Repurpose here means mining for specific modules, algorithms, UI patterns, ingestion logic, workflow ideas, or export formats rather than assuming a full product transplant.",native/scriptoriumai-ui,native/ScriptoriumAI-Server,abhigyanpatwari/GitNexus,"Return concrete files/modules/adapters worth reusing and a verdict on whether the current reanchored bucket should be kept, upgraded, or downgraded.",Do not treat licensing as a filter. Do not propose replacing native foundations unless source evidence is overwhelming.,bytebytegohq/system-design-101,v6_unified_source_of_truth_pack,"Before recommending direct code use, inspect the target repo row in the v6.1 operational/phase/source-audit boards. Respect copyleft_strategy_v6_1, preferred_boundary_model_v6_1, and open_compliance_if_used_as_is_v6_1. Do not assume reverse engineering is mandatory or that as-is use is always sensible.","If the repo-level strategy says bounded_sidecar_preferred or boundary_first_then_decide_as_is_vs_reimplementation, audit clean interfaces, protocol seams, subprocess/container boundaries, and what would be required to reimplement only the strategically necessary portions.",v6.3_final_source_of_truth
SCR_0252,,,,,,,,,,ScriptoriumAI repo packet,ScriptoriumAI,ScriptoriumAI re-anchored VS Code packets v1,CoderGamester/mcp-unity,codergamester/mcp-unity,Exclude Current Horizon,P3,bookmark candidate only,"Audit CoderGamester/mcp-unity for ScriptoriumAI. Start from the reanchored bucket 'Exclude Current Horizon' and current reality status 'bookmark candidate only'. Confirm actual implemented capability, hidden reusable modules, extension seams, and whether it strengthens the existing Off-axis candidate for current ScriptoriumAI baseline lane. Focus on: Inspect planner/task graph; provider abstraction; tool registry or MCP bridges; memory/state schema; approvals/retries; telemetry/event bus; plugin or skill loading 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 planner loops, tool registries, MCP servers/clients, prompt/skill folders, memory stores, approval gates, background-job orchestration, and undocumented provider adapters.","Treat as unimplemented ScriptoriumAI candidate only. Do not let it redefine the current stack. Integrate only if a later audit proves it fills a real gap in the existing surfaces such as Dashboard, Editor, Corpus Graph, Runboard, AI Kanban, Corpus Search, Patch Review Queue, Visualizations, Whiteboard, Mind Map, PDF Intake, AI Diagram Studio, Video Studio, Research Agent, New Research Topic, Skills Manager, OpenAPI Routing, Manim Sandbox, Settings.","Repurpose here means mining for specific modules, algorithms, UI patterns, ingestion logic, workflow ideas, or export formats rather than assuming a full product transplant.",native/scriptoriumai-ui,native/ScriptoriumAI-Server,sharelatex/sharelatex,"Return concrete files/modules/adapters worth reusing and a verdict on whether the current reanchored bucket should be kept, upgraded, or downgraded.",Do not treat licensing as a filter. Do not propose replacing native foundations unless source evidence is overwhelming.,codergamester/mcp-unity,v6_unified_source_of_truth_pack,"Before recommending direct code use, inspect the target repo row in the v6.1 operational/phase/source-audit boards. Respect copyleft_strategy_v6_1, preferred_boundary_model_v6_1, and open_compliance_if_used_as_is_v6_1. Do not assume reverse engineering is mandatory or that as-is use is always sensible.","If the repo-level strategy says bounded_sidecar_preferred or boundary_first_then_decide_as_is_vs_reimplementation, audit clean interfaces, protocol seams, subprocess/container boundaries, and what would be required to reimplement only the strategically necessary portions.",v6.3_final_source_of_truth
SCR_0253,,,,,,,,,,ScriptoriumAI repo packet,ScriptoriumAI,ScriptoriumAI re-anchored VS Code packets v1,CoplayDev/unity-mcp,coplaydev/unity-mcp,Exclude Current Horizon,P3,bookmark candidate only,"Audit CoplayDev/unity-mcp for ScriptoriumAI. Start from the reanchored bucket 'Exclude Current Horizon' and current reality status 'bookmark candidate only'. Confirm actual implemented capability, hidden reusable modules, extension seams, and whether it strengthens the existing Off-axis candidate for current ScriptoriumAI baseline lane. Focus on: Inspect planner/task graph; provider abstraction; tool registry or MCP bridges; memory/state schema; approvals/retries; telemetry/event bus; plugin or skill loading 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 planner loops, tool registries, MCP servers/clients, prompt/skill folders, memory stores, approval gates, background-job orchestration, and undocumented provider adapters.","Treat as unimplemented ScriptoriumAI candidate only. Do not let it redefine the current stack. Integrate only if a later audit proves it fills a real gap in the existing surfaces such as Dashboard, Editor, Corpus Graph, Runboard, AI Kanban, Corpus Search, Patch Review Queue, Visualizations, Whiteboard, Mind Map, PDF Intake, AI Diagram Studio, Video Studio, Research Agent, New Research Topic, Skills Manager, OpenAPI Routing, Manim Sandbox, Settings.","Repurpose here means mining for specific modules, algorithms, UI patterns, ingestion logic, workflow ideas, or export formats rather than assuming a full product transplant.",native/scriptoriumai-ui,native/ScriptoriumAI-Server,sharelatex/sharelatex,"Return concrete files/modules/adapters worth reusing and a verdict on whether the current reanchored bucket should be kept, upgraded, or downgraded.",Do not treat licensing as a filter. Do not propose replacing native foundations unless source evidence is overwhelming.,coplaydev/unity-mcp,v6_unified_source_of_truth_pack,"Before recommending direct code use, inspect the target repo row in the v6.1 operational/phase/source-audit boards. Respect copyleft_strategy_v6_1, preferred_boundary_model_v6_1, and open_compliance_if_used_as_is_v6_1. Do not assume reverse engineering is mandatory or that as-is use is always sensible.","If the repo-level strategy says bounded_sidecar_preferred or boundary_first_then_decide_as_is_vs_reimplementation, audit clean interfaces, protocol seams, subprocess/container boundaries, and what would be required to reimplement only the strategically necessary portions.",v6.3_final_source_of_truth
SCR_0254,,,,,,,,,,ScriptoriumAI repo packet,ScriptoriumAI,ScriptoriumAI re-anchored VS Code packets v1,NotHarshhaa/DevOps-Interview-Questions,notharshhaa/devops-interview-questions,Exclude Current Horizon,P3,bookmark candidate only,"Audit NotHarshhaa/DevOps-Interview-Questions for ScriptoriumAI. Start from the reanchored bucket 'Exclude Current Horizon' and current reality status 'bookmark candidate only'. Confirm actual implemented capability, hidden reusable modules, extension seams, and whether it strengthens the existing Off-axis candidate for current ScriptoriumAI baseline lane. Focus on: 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.","Treat as unimplemented ScriptoriumAI candidate only. Do not let it redefine the current stack. Integrate only if a later audit proves it fills a real gap in the existing surfaces such as Dashboard, Editor, Corpus Graph, Runboard, AI Kanban, Corpus Search, Patch Review Queue, Visualizations, Whiteboard, Mind Map, PDF Intake, AI Diagram Studio, Video Studio, Research Agent, New Research Topic, Skills Manager, OpenAPI Routing, Manim Sandbox, Settings.","Repurpose here means mining for specific modules, algorithms, UI patterns, ingestion logic, workflow ideas, or export formats rather than assuming a full product transplant.",native/scriptoriumai-ui,native/ScriptoriumAI-Server,abhigyanpatwari/GitNexus,"Return concrete files/modules/adapters worth reusing and a verdict on whether the current reanchored bucket should be kept, upgraded, or downgraded.",Do not treat licensing as a filter. Do not propose replacing native foundations unless source evidence is overwhelming.,notharshhaa/devops-interview-questions,v6_unified_source_of_truth_pack,"Before recommending direct code use, inspect the target repo row in the v6.1 operational/phase/source-audit boards. Respect copyleft_strategy_v6_1, preferred_boundary_model_v6_1, and open_compliance_if_used_as_is_v6_1. Do not assume reverse engineering is mandatory or that as-is use is always sensible.","If the repo-level strategy says bounded_sidecar_preferred or boundary_first_then_decide_as_is_vs_reimplementation, audit clean interfaces, protocol seams, subprocess/container boundaries, and what would be required to reimplement only the strategically necessary portions.",v6.3_final_source_of_truth
SCR_0255,,,,,,,,,,ScriptoriumAI repo packet,ScriptoriumAI,ScriptoriumAI re-anchored VS Code packets v1,STARasGAMES/193b7a5a3b98c7731ac7c36b63d6ef8e,starasgames/193b7a5a3b98c7731ac7c36b63d6ef8e,Exclude Current Horizon,P3,bookmark candidate only,"Audit STARasGAMES/193b7a5a3b98c7731ac7c36b63d6ef8e for ScriptoriumAI. Start from the reanchored bucket 'Exclude Current Horizon' and current reality status 'bookmark candidate only'. Confirm actual implemented capability, hidden reusable modules, extension seams, and whether it strengthens the existing Off-axis candidate for current ScriptoriumAI baseline lane. Focus on: Inspect planner/task graph; provider abstraction; tool registry or MCP bridges; memory/state schema; approvals/retries; telemetry/event bus; plugin or skill loading 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 planner loops, tool registries, MCP servers/clients, prompt/skill folders, memory stores, approval gates, background-job orchestration, and undocumented provider adapters.","Treat as unimplemented ScriptoriumAI candidate only. Do not let it redefine the current stack. Integrate only if a later audit proves it fills a real gap in the existing surfaces such as Dashboard, Editor, Corpus Graph, Runboard, AI Kanban, Corpus Search, Patch Review Queue, Visualizations, Whiteboard, Mind Map, PDF Intake, AI Diagram Studio, Video Studio, Research Agent, New Research Topic, Skills Manager, OpenAPI Routing, Manim Sandbox, Settings.","Repurpose here means mining for specific modules, algorithms, UI patterns, ingestion logic, workflow ideas, or export formats rather than assuming a full product transplant.",native/scriptoriumai-ui,native/ScriptoriumAI-Server,abhigyanpatwari/GitNexus,"Return concrete files/modules/adapters worth reusing and a verdict on whether the current reanchored bucket should be kept, upgraded, or downgraded.",Do not treat licensing as a filter. Do not propose replacing native foundations unless source evidence is overwhelming.,starasgames/193b7a5a3b98c7731ac7c36b63d6ef8e,v6_unified_source_of_truth_pack,"Before recommending direct code use, inspect the target repo row in the v6.1 operational/phase/source-audit boards. Respect copyleft_strategy_v6_1, preferred_boundary_model_v6_1, and open_compliance_if_used_as_is_v6_1. Do not assume reverse engineering is mandatory or that as-is use is always sensible.","If the repo-level strategy says bounded_sidecar_preferred or boundary_first_then_decide_as_is_vs_reimplementation, audit clean interfaces, protocol seams, subprocess/container boundaries, and what would be required to reimplement only the strategically necessary portions.",v6.3_final_source_of_truth
SCR_0256,,,,,,,,,,ScriptoriumAI repo packet,ScriptoriumAI,ScriptoriumAI re-anchored VS Code packets v1,Unity-Technologies/EntityComponentSystemSamples,unity-technologies/entitycomponentsystemsamples,Exclude Current Horizon,P3,bookmark candidate only,"Audit Unity-Technologies/EntityComponentSystemSamples for ScriptoriumAI. Start from the reanchored bucket 'Exclude Current Horizon' and current reality status 'bookmark candidate only'. Confirm actual implemented capability, hidden reusable modules, extension seams, and whether it strengthens the existing Off-axis candidate for current ScriptoriumAI baseline lane. Focus on: 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.","Treat as unimplemented ScriptoriumAI candidate only. Do not let it redefine the current stack. Integrate only if a later audit proves it fills a real gap in the existing surfaces such as Dashboard, Editor, Corpus Graph, Runboard, AI Kanban, Corpus Search, Patch Review Queue, Visualizations, Whiteboard, Mind Map, PDF Intake, AI Diagram Studio, Video Studio, Research Agent, New Research Topic, Skills Manager, OpenAPI Routing, Manim Sandbox, Settings.","Repurpose here means mining for specific modules, algorithms, UI patterns, ingestion logic, workflow ideas, or export formats rather than assuming a full product transplant.",native/scriptoriumai-ui,native/ScriptoriumAI-Server,abhigyanpatwari/GitNexus,"Return concrete files/modules/adapters worth reusing and a verdict on whether the current reanchored bucket should be kept, upgraded, or downgraded.",Do not treat licensing as a filter. Do not propose replacing native foundations unless source evidence is overwhelming.,unity-technologies/entitycomponentsystemsamples,v6_unified_source_of_truth_pack,"Before recommending direct code use, inspect the target repo row in the v6.1 operational/phase/source-audit boards. Respect copyleft_strategy_v6_1, preferred_boundary_model_v6_1, and open_compliance_if_used_as_is_v6_1. Do not assume reverse engineering is mandatory or that as-is use is always sensible.","If the repo-level strategy says bounded_sidecar_preferred or boundary_first_then_decide_as_is_vs_reimplementation, audit clean interfaces, protocol seams, subprocess/container boundaries, and what would be required to reimplement only the strategically necessary portions.",v6.3_final_source_of_truth
SCR_0257,,,,,,,,,,ScriptoriumAI repo packet,ScriptoriumAI,ScriptoriumAI re-anchored VS Code packets v1,UnityTechnologies/open-project-1,unitytechnologies/open-project-1,Exclude Current Horizon,P3,bookmark candidate only,"Audit UnityTechnologies/open-project-1 for ScriptoriumAI. Start from the reanchored bucket 'Exclude Current Horizon' and current reality status 'bookmark candidate only'. Confirm actual implemented capability, hidden reusable modules, extension seams, and whether it strengthens the existing Off-axis candidate for current ScriptoriumAI baseline lane. Focus on: Inspect package/module map; entrypoints; config and schema files; adapters/integrations; persistence model; tests/examples; hidden feature flags; plugin 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 hidden admin tools, reusable services, plugin systems, import/export, analytics, background jobs, and any engine more valuable than the public README suggests.","Treat as unimplemented ScriptoriumAI candidate only. Do not let it redefine the current stack. Integrate only if a later audit proves it fills a real gap in the existing surfaces such as Dashboard, Editor, Corpus Graph, Runboard, AI Kanban, Corpus Search, Patch Review Queue, Visualizations, Whiteboard, Mind Map, PDF Intake, AI Diagram Studio, Video Studio, Research Agent, New Research Topic, Skills Manager, OpenAPI Routing, Manim Sandbox, Settings.","Repurpose here means mining for specific modules, algorithms, UI patterns, ingestion logic, workflow ideas, or export formats rather than assuming a full product transplant.",native/scriptoriumai-ui,native/ScriptoriumAI-Server,abhigyanpatwari/GitNexus,"Return concrete files/modules/adapters worth reusing and a verdict on whether the current reanchored bucket should be kept, upgraded, or downgraded.",Do not treat licensing as a filter. Do not propose replacing native foundations unless source evidence is overwhelming.,unitytechnologies/open-project-1,v6_unified_source_of_truth_pack,"Before recommending direct code use, inspect the target repo row in the v6.1 operational/phase/source-audit boards. Respect copyleft_strategy_v6_1, preferred_boundary_model_v6_1, and open_compliance_if_used_as_is_v6_1. Do not assume reverse engineering is mandatory or that as-is use is always sensible.","If the repo-level strategy says bounded_sidecar_preferred or boundary_first_then_decide_as_is_vs_reimplementation, audit clean interfaces, protocol seams, subprocess/container boundaries, and what would be required to reimplement only the strategically necessary portions.",v6.3_final_source_of_truth
SCR_0258,,,,,,,,,,ScriptoriumAI repo packet,ScriptoriumAI,ScriptoriumAI re-anchored VS Code packets v1,baba-s/awesome-unity-open-source-on-github,baba-s/awesome-unity-open-source-on-github,Exclude Current Horizon,P3,bookmark candidate only,"Audit baba-s/awesome-unity-open-source-on-github for ScriptoriumAI. Start from the reanchored bucket 'Exclude Current Horizon' and current reality status 'bookmark candidate only'. Confirm actual implemented capability, hidden reusable modules, extension seams, and whether it strengthens the existing Off-axis candidate for current ScriptoriumAI baseline lane. Focus on: 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.","Treat as unimplemented ScriptoriumAI candidate only. Do not let it redefine the current stack. Integrate only if a later audit proves it fills a real gap in the existing surfaces such as Dashboard, Editor, Corpus Graph, Runboard, AI Kanban, Corpus Search, Patch Review Queue, Visualizations, Whiteboard, Mind Map, PDF Intake, AI Diagram Studio, Video Studio, Research Agent, New Research Topic, Skills Manager, OpenAPI Routing, Manim Sandbox, Settings.","Repurpose here means mining for specific modules, algorithms, UI patterns, ingestion logic, workflow ideas, or export formats rather than assuming a full product transplant.",native/scriptoriumai-ui,native/ScriptoriumAI-Server,abhigyanpatwari/GitNexus,"Return concrete files/modules/adapters worth reusing and a verdict on whether the current reanchored bucket should be kept, upgraded, or downgraded.",Do not treat licensing as a filter. Do not propose replacing native foundations unless source evidence is overwhelming.,baba-s/awesome-unity-open-source-on-github,v6_unified_source_of_truth_pack,"Before recommending direct code use, inspect the target repo row in the v6.1 operational/phase/source-audit boards. Respect copyleft_strategy_v6_1, preferred_boundary_model_v6_1, and open_compliance_if_used_as_is_v6_1. Do not assume reverse engineering is mandatory or that as-is use is always sensible.","If the repo-level strategy says bounded_sidecar_preferred or boundary_first_then_decide_as_is_vs_reimplementation, audit clean interfaces, protocol seams, subprocess/container boundaries, and what would be required to reimplement only the strategically necessary portions.",v6.3_final_source_of_truth
SCR_0259,,,,,,,,,,ScriptoriumAI repo packet,ScriptoriumAI,ScriptoriumAI re-anchored VS Code packets v1,beto-rodriguez/Manuela,beto-rodriguez/manuela,Exclude Current Horizon,P3,bookmark candidate only,"Audit beto-rodriguez/Manuela for ScriptoriumAI. Start from the reanchored bucket 'Exclude Current Horizon' and current reality status 'bookmark candidate only'. Confirm actual implemented capability, hidden reusable modules, extension seams, and whether it strengthens the existing Off-axis candidate for current ScriptoriumAI baseline lane. Focus on: 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.","Treat as unimplemented ScriptoriumAI candidate only. Do not let it redefine the current stack. Integrate only if a later audit proves it fills a real gap in the existing surfaces such as Dashboard, Editor, Corpus Graph, Runboard, AI Kanban, Corpus Search, Patch Review Queue, Visualizations, Whiteboard, Mind Map, PDF Intake, AI Diagram Studio, Video Studio, Research Agent, New Research Topic, Skills Manager, OpenAPI Routing, Manim Sandbox, Settings.","Repurpose here means mining for specific modules, algorithms, UI patterns, ingestion logic, workflow ideas, or export formats rather than assuming a full product transplant.",native/scriptoriumai-ui,native/ScriptoriumAI-Server,abhigyanpatwari/GitNexus,"Return concrete files/modules/adapters worth reusing and a verdict on whether the current reanchored bucket should be kept, upgraded, or downgraded.",Do not treat licensing as a filter. Do not propose replacing native foundations unless source evidence is overwhelming.,beto-rodriguez/manuela,v6_unified_source_of_truth_pack,"Before recommending direct code use, inspect the target repo row in the v6.1 operational/phase/source-audit boards. Respect copyleft_strategy_v6_1, preferred_boundary_model_v6_1, and open_compliance_if_used_as_is_v6_1. Do not assume reverse engineering is mandatory or that as-is use is always sensible.","If the repo-level strategy says bounded_sidecar_preferred or boundary_first_then_decide_as_is_vs_reimplementation, audit clean interfaces, protocol seams, subprocess/container boundaries, and what would be required to reimplement only the strategically necessary portions.",v6.3_final_source_of_truth
SCR_0260,,,,,,,,,,ScriptoriumAI repo packet,ScriptoriumAI,ScriptoriumAI re-anchored VS Code packets v1,bregman-arie/devops-exercises,bregman-arie/devops-exercises,Exclude Current Horizon,P3,bookmark candidate only,"Audit bregman-arie/devops-exercises for ScriptoriumAI. Start from the reanchored bucket 'Exclude Current Horizon' and current reality status 'bookmark candidate only'. Confirm actual implemented capability, hidden reusable modules, extension seams, and whether it strengthens the existing Off-axis candidate for current ScriptoriumAI baseline lane. Focus on: Inspect parsers and language adapters; graph schema and storage; incremental indexing/update logic; layout engine; query API; export/import formats; test fixtures for graph correctness.","Inspect package manifests, README/docs, src tree, examples, tests, CI workflows, config files, migrations/schemas, and hidden feature flags or experimental modules. Look for event schemas, ingestion pipelines, queue/job workers, service adapters, deployment/runtime config, RBAC/auth, alerting, and API contract generators.","Treat as unimplemented ScriptoriumAI candidate only. Do not let it redefine the current stack. Integrate only if a later audit proves it fills a real gap in the existing surfaces such as Dashboard, Editor, Corpus Graph, Runboard, AI Kanban, Corpus Search, Patch Review Queue, Visualizations, Whiteboard, Mind Map, PDF Intake, AI Diagram Studio, Video Studio, Research Agent, New Research Topic, Skills Manager, OpenAPI Routing, Manim Sandbox, Settings.","Repurpose here means mining for specific modules, algorithms, UI patterns, ingestion logic, workflow ideas, or export formats rather than assuming a full product transplant.",native/scriptoriumai-ui,native/ScriptoriumAI-Server,abhigyanpatwari/GitNexus,"Return concrete files/modules/adapters worth reusing and a verdict on whether the current reanchored bucket should be kept, upgraded, or downgraded.",Do not treat licensing as a filter. Do not propose replacing native foundations unless source evidence is overwhelming.,bregman-arie/devops-exercises,v6_unified_source_of_truth_pack,"Before recommending direct code use, inspect the target repo row in the v6.1 operational/phase/source-audit boards. Respect copyleft_strategy_v6_1, preferred_boundary_model_v6_1, and open_compliance_if_used_as_is_v6_1. Do not assume reverse engineering is mandatory or that as-is use is always sensible.","If the repo-level strategy says bounded_sidecar_preferred or boundary_first_then_decide_as_is_vs_reimplementation, audit clean interfaces, protocol seams, subprocess/container boundaries, and what would be required to reimplement only the strategically necessary portions.",v6.3_final_source_of_truth
SCR_0261,,,,,,,,,,ScriptoriumAI repo packet,ScriptoriumAI,ScriptoriumAI re-anchored VS Code packets v1,cloudcommunity/Free-Certifications,cloudcommunity/free-certifications,Exclude Current Horizon,P3,bookmark candidate only,"Audit cloudcommunity/Free-Certifications for ScriptoriumAI. Start from the reanchored bucket 'Exclude Current Horizon' and current reality status 'bookmark candidate only'. Confirm actual implemented capability, hidden reusable modules, extension seams, and whether it strengthens the existing Off-axis candidate for current ScriptoriumAI baseline lane. Focus on: 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 event schemas, ingestion pipelines, queue/job workers, service adapters, deployment/runtime config, RBAC/auth, alerting, and API contract generators.","Treat as unimplemented ScriptoriumAI candidate only. Do not let it redefine the current stack. Integrate only if a later audit proves it fills a real gap in the existing surfaces such as Dashboard, Editor, Corpus Graph, Runboard, AI Kanban, Corpus Search, Patch Review Queue, Visualizations, Whiteboard, Mind Map, PDF Intake, AI Diagram Studio, Video Studio, Research Agent, New Research Topic, Skills Manager, OpenAPI Routing, Manim Sandbox, Settings.","Repurpose here means mining for specific modules, algorithms, UI patterns, ingestion logic, workflow ideas, or export formats rather than assuming a full product transplant.",native/scriptoriumai-ui,native/ScriptoriumAI-Server,abhigyanpatwari/GitNexus,"Return concrete files/modules/adapters worth reusing and a verdict on whether the current reanchored bucket should be kept, upgraded, or downgraded.",Do not treat licensing as a filter. Do not propose replacing native foundations unless source evidence is overwhelming.,cloudcommunity/free-certifications,v6_unified_source_of_truth_pack,"Before recommending direct code use, inspect the target repo row in the v6.1 operational/phase/source-audit boards. Respect copyleft_strategy_v6_1, preferred_boundary_model_v6_1, and open_compliance_if_used_as_is_v6_1. Do not assume reverse engineering is mandatory or that as-is use is always sensible.","If the repo-level strategy says bounded_sidecar_preferred or boundary_first_then_decide_as_is_vs_reimplementation, audit clean interfaces, protocol seams, subprocess/container boundaries, and what would be required to reimplement only the strategically necessary portions.",v6.3_final_source_of_truth
SCR_0262,,,,,,,,,,ScriptoriumAI repo packet,ScriptoriumAI,ScriptoriumAI re-anchored VS Code packets v1,de4dot/de4dot,de4dot/de4dot,Exclude Current Horizon,P3,bookmark candidate only,"Audit de4dot/de4dot for ScriptoriumAI. Start from the reanchored bucket 'Exclude Current Horizon' and current reality status 'bookmark candidate only'. Confirm actual implemented capability, hidden reusable modules, extension seams, and whether it strengthens the existing Off-axis candidate for current ScriptoriumAI baseline lane. Focus on: 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.","Treat as unimplemented ScriptoriumAI candidate only. Do not let it redefine the current stack. Integrate only if a later audit proves it fills a real gap in the existing surfaces such as Dashboard, Editor, Corpus Graph, Runboard, AI Kanban, Corpus Search, Patch Review Queue, Visualizations, Whiteboard, Mind Map, PDF Intake, AI Diagram Studio, Video Studio, Research Agent, New Research Topic, Skills Manager, OpenAPI Routing, Manim Sandbox, Settings.","Repurpose here means mining for specific modules, algorithms, UI patterns, ingestion logic, workflow ideas, or export formats rather than assuming a full product transplant.",native/scriptoriumai-ui,native/ScriptoriumAI-Server,abhigyanpatwari/GitNexus,"Return concrete files/modules/adapters worth reusing and a verdict on whether the current reanchored bucket should be kept, upgraded, or downgraded.",Do not treat licensing as a filter. Do not propose replacing native foundations unless source evidence is overwhelming.,de4dot/de4dot,v6_unified_source_of_truth_pack,"Before recommending direct code use, inspect the target repo row in the v6.1 operational/phase/source-audit boards. Respect copyleft_strategy_v6_1, preferred_boundary_model_v6_1, and open_compliance_if_used_as_is_v6_1. Do not assume reverse engineering is mandatory or that as-is use is always sensible.","If the repo-level strategy says bounded_sidecar_preferred or boundary_first_then_decide_as_is_vs_reimplementation, audit clean interfaces, protocol seams, subprocess/container boundaries, and what would be required to reimplement only the strategically necessary portions.",v6.3_final_source_of_truth
SCR_0263,,,,,,,,,,ScriptoriumAI repo packet,ScriptoriumAI,ScriptoriumAI re-anchored VS Code packets v1,dnSpy/dnSpy,dnspy/dnspy,Exclude Current Horizon,P3,bookmark candidate only,"Audit dnSpy/dnSpy for ScriptoriumAI. Start from the reanchored bucket 'Exclude Current Horizon' and current reality status 'bookmark candidate only'. Confirm actual implemented capability, hidden reusable modules, extension seams, and whether it strengthens the existing Off-axis candidate for current ScriptoriumAI baseline lane. Focus on: 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.","Treat as unimplemented ScriptoriumAI candidate only. Do not let it redefine the current stack. Integrate only if a later audit proves it fills a real gap in the existing surfaces such as Dashboard, Editor, Corpus Graph, Runboard, AI Kanban, Corpus Search, Patch Review Queue, Visualizations, Whiteboard, Mind Map, PDF Intake, AI Diagram Studio, Video Studio, Research Agent, New Research Topic, Skills Manager, OpenAPI Routing, Manim Sandbox, Settings.","Repurpose here means mining for specific modules, algorithms, UI patterns, ingestion logic, workflow ideas, or export formats rather than assuming a full product transplant.",native/scriptoriumai-ui,native/ScriptoriumAI-Server,sharelatex/sharelatex,"Return concrete files/modules/adapters worth reusing and a verdict on whether the current reanchored bucket should be kept, upgraded, or downgraded.",Do not treat licensing as a filter. Do not propose replacing native foundations unless source evidence is overwhelming.,dnspy/dnspy,v6_unified_source_of_truth_pack,"Before recommending direct code use, inspect the target repo row in the v6.1 operational/phase/source-audit boards. Respect copyleft_strategy_v6_1, preferred_boundary_model_v6_1, and open_compliance_if_used_as_is_v6_1. Do not assume reverse engineering is mandatory or that as-is use is always sensible.","If the repo-level strategy says bounded_sidecar_preferred or boundary_first_then_decide_as_is_vs_reimplementation, audit clean interfaces, protocol seams, subprocess/container boundaries, and what would be required to reimplement only the strategically necessary portions.",v6.3_final_source_of_truth
SCR_0264,,,,,,,,,,ScriptoriumAI repo packet,ScriptoriumAI,ScriptoriumAI re-anchored VS Code packets v1,dnSpyEx/dnSpy,dnspyex/dnspy,Exclude Current Horizon,P3,bookmark candidate only,"Audit dnSpyEx/dnSpy for ScriptoriumAI. Start from the reanchored bucket 'Exclude Current Horizon' and current reality status 'bookmark candidate only'. Confirm actual implemented capability, hidden reusable modules, extension seams, and whether it strengthens the existing Off-axis candidate for current ScriptoriumAI baseline lane. Focus on: Inspect package/module map; entrypoints; config and schema files; adapters/integrations; persistence model; tests/examples; hidden feature flags; plugin 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 hidden admin tools, reusable services, plugin systems, import/export, analytics, background jobs, and any engine more valuable than the public README suggests.","Treat as unimplemented ScriptoriumAI candidate only. Do not let it redefine the current stack. Integrate only if a later audit proves it fills a real gap in the existing surfaces such as Dashboard, Editor, Corpus Graph, Runboard, AI Kanban, Corpus Search, Patch Review Queue, Visualizations, Whiteboard, Mind Map, PDF Intake, AI Diagram Studio, Video Studio, Research Agent, New Research Topic, Skills Manager, OpenAPI Routing, Manim Sandbox, Settings.","Repurpose here means mining for specific modules, algorithms, UI patterns, ingestion logic, workflow ideas, or export formats rather than assuming a full product transplant.",native/scriptoriumai-ui,native/ScriptoriumAI-Server,abhigyanpatwari/GitNexus,"Return concrete files/modules/adapters worth reusing and a verdict on whether the current reanchored bucket should be kept, upgraded, or downgraded.",Do not treat licensing as a filter. Do not propose replacing native foundations unless source evidence is overwhelming.,dnspyex/dnspy,v6_unified_source_of_truth_pack,"Before recommending direct code use, inspect the target repo row in the v6.1 operational/phase/source-audit boards. Respect copyleft_strategy_v6_1, preferred_boundary_model_v6_1, and open_compliance_if_used_as_is_v6_1. Do not assume reverse engineering is mandatory or that as-is use is always sensible.","If the repo-level strategy says bounded_sidecar_preferred or boundary_first_then_decide_as_is_vs_reimplementation, audit clean interfaces, protocol seams, subprocess/container boundaries, and what would be required to reimplement only the strategically necessary portions.",v6.3_final_source_of_truth
SCR_0265,,,,,,,,,,ScriptoriumAI repo packet,ScriptoriumAI,ScriptoriumAI re-anchored VS Code packets v1,donnemartin/system-design-primer,donnemartin/system-design-primer,Exclude Current Horizon,P3,bookmark candidate only,"Audit donnemartin/system-design-primer for ScriptoriumAI. Start from the reanchored bucket 'Exclude Current Horizon' and current reality status 'bookmark candidate only'. Confirm actual implemented capability, hidden reusable modules, extension seams, and whether it strengthens the existing Off-axis candidate for current ScriptoriumAI baseline lane. Focus on: 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.","Treat as unimplemented ScriptoriumAI candidate only. Do not let it redefine the current stack. Integrate only if a later audit proves it fills a real gap in the existing surfaces such as Dashboard, Editor, Corpus Graph, Runboard, AI Kanban, Corpus Search, Patch Review Queue, Visualizations, Whiteboard, Mind Map, PDF Intake, AI Diagram Studio, Video Studio, Research Agent, New Research Topic, Skills Manager, OpenAPI Routing, Manim Sandbox, Settings.","Repurpose here means mining for specific modules, algorithms, UI patterns, ingestion logic, workflow ideas, or export formats rather than assuming a full product transplant.",native/scriptoriumai-ui,native/ScriptoriumAI-Server,abhigyanpatwari/GitNexus,"Return concrete files/modules/adapters worth reusing and a verdict on whether the current reanchored bucket should be kept, upgraded, or downgraded.",Do not treat licensing as a filter. Do not propose replacing native foundations unless source evidence is overwhelming.,donnemartin/system-design-primer,v6_unified_source_of_truth_pack,"Before recommending direct code use, inspect the target repo row in the v6.1 operational/phase/source-audit boards. Respect copyleft_strategy_v6_1, preferred_boundary_model_v6_1, and open_compliance_if_used_as_is_v6_1. Do not assume reverse engineering is mandatory or that as-is use is always sensible.","If the repo-level strategy says bounded_sidecar_preferred or boundary_first_then_decide_as_is_vs_reimplementation, audit clean interfaces, protocol seams, subprocess/container boundaries, and what would be required to reimplement only the strategically necessary portions.",v6.3_final_source_of_truth
SCR_0266,,,,,,,,,,ScriptoriumAI repo packet,ScriptoriumAI,ScriptoriumAI re-anchored VS Code packets v1,fillmember/unity-bridge,fillmember/unity-bridge,Exclude Current Horizon,P3,bookmark candidate only,"Audit fillmember/unity-bridge for ScriptoriumAI. Start from the reanchored bucket 'Exclude Current Horizon' and current reality status 'bookmark candidate only'. Confirm actual implemented capability, hidden reusable modules, extension seams, and whether it strengthens the existing Off-axis candidate for current ScriptoriumAI baseline lane. Focus on: Inspect planner/task graph; provider abstraction; tool registry or MCP bridges; memory/state schema; approvals/retries; telemetry/event bus; plugin or skill loading 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 planner loops, tool registries, MCP servers/clients, prompt/skill folders, memory stores, approval gates, background-job orchestration, and undocumented provider adapters.","Treat as unimplemented ScriptoriumAI candidate only. Do not let it redefine the current stack. Integrate only if a later audit proves it fills a real gap in the existing surfaces such as Dashboard, Editor, Corpus Graph, Runboard, AI Kanban, Corpus Search, Patch Review Queue, Visualizations, Whiteboard, Mind Map, PDF Intake, AI Diagram Studio, Video Studio, Research Agent, New Research Topic, Skills Manager, OpenAPI Routing, Manim Sandbox, Settings.","Repurpose here means mining for specific modules, algorithms, UI patterns, ingestion logic, workflow ideas, or export formats rather than assuming a full product transplant.",native/scriptoriumai-ui,native/ScriptoriumAI-Server,abhigyanpatwari/GitNexus,"Return concrete files/modules/adapters worth reusing and a verdict on whether the current reanchored bucket should be kept, upgraded, or downgraded.",Do not treat licensing as a filter. Do not propose replacing native foundations unless source evidence is overwhelming.,fillmember/unity-bridge,v6_unified_source_of_truth_pack,"Before recommending direct code use, inspect the target repo row in the v6.1 operational/phase/source-audit boards. Respect copyleft_strategy_v6_1, preferred_boundary_model_v6_1, and open_compliance_if_used_as_is_v6_1. Do not assume reverse engineering is mandatory or that as-is use is always sensible.","If the repo-level strategy says bounded_sidecar_preferred or boundary_first_then_decide_as_is_vs_reimplementation, audit clean interfaces, protocol seams, subprocess/container boundaries, and what would be required to reimplement only the strategically necessary portions.",v6.3_final_source_of_truth
SCR_0267,,,,,,,,,,ScriptoriumAI repo packet,ScriptoriumAI,ScriptoriumAI re-anchored VS Code packets v1,jsuarezruiz/awesome-dotnet-maui,jsuarezruiz/awesome-dotnet-maui,Exclude Current Horizon,P3,bookmark candidate only,"Audit jsuarezruiz/awesome-dotnet-maui for ScriptoriumAI. Start from the reanchored bucket 'Exclude Current Horizon' and current reality status 'bookmark candidate only'. Confirm actual implemented capability, hidden reusable modules, extension seams, and whether it strengthens the existing Off-axis candidate for current ScriptoriumAI baseline lane. Focus on: 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.","Treat as unimplemented ScriptoriumAI candidate only. Do not let it redefine the current stack. Integrate only if a later audit proves it fills a real gap in the existing surfaces such as Dashboard, Editor, Corpus Graph, Runboard, AI Kanban, Corpus Search, Patch Review Queue, Visualizations, Whiteboard, Mind Map, PDF Intake, AI Diagram Studio, Video Studio, Research Agent, New Research Topic, Skills Manager, OpenAPI Routing, Manim Sandbox, Settings.","Repurpose here means mining for specific modules, algorithms, UI patterns, ingestion logic, workflow ideas, or export formats rather than assuming a full product transplant.",native/scriptoriumai-ui,native/ScriptoriumAI-Server,abhigyanpatwari/GitNexus,"Return concrete files/modules/adapters worth reusing and a verdict on whether the current reanchored bucket should be kept, upgraded, or downgraded.",Do not treat licensing as a filter. Do not propose replacing native foundations unless source evidence is overwhelming.,jsuarezruiz/awesome-dotnet-maui,v6_unified_source_of_truth_pack,"Before recommending direct code use, inspect the target repo row in the v6.1 operational/phase/source-audit boards. Respect copyleft_strategy_v6_1, preferred_boundary_model_v6_1, and open_compliance_if_used_as_is_v6_1. Do not assume reverse engineering is mandatory or that as-is use is always sensible.","If the repo-level strategy says bounded_sidecar_preferred or boundary_first_then_decide_as_is_vs_reimplementation, audit clean interfaces, protocol seams, subprocess/container boundaries, and what would be required to reimplement only the strategically necessary portions.",v6.3_final_source_of_truth
SCR_0268,,,,,,,,,,ScriptoriumAI repo packet,ScriptoriumAI,ScriptoriumAI re-anchored VS Code packets v1,jwasham/coding-interview-university,jwasham/coding-interview-university,Exclude Current Horizon,P3,bookmark candidate only,"Audit jwasham/coding-interview-university for ScriptoriumAI. Start from the reanchored bucket 'Exclude Current Horizon' and current reality status 'bookmark candidate only'. Confirm actual implemented capability, hidden reusable modules, extension seams, and whether it strengthens the existing Off-axis candidate for current ScriptoriumAI baseline lane. Focus on: Inspect package/module map; entrypoints; config and schema files; adapters/integrations; persistence model; tests/examples; hidden feature flags; plugin 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 hidden admin tools, reusable services, plugin systems, import/export, analytics, background jobs, and any engine more valuable than the public README suggests.","Treat as unimplemented ScriptoriumAI candidate only. Do not let it redefine the current stack. Integrate only if a later audit proves it fills a real gap in the existing surfaces such as Dashboard, Editor, Corpus Graph, Runboard, AI Kanban, Corpus Search, Patch Review Queue, Visualizations, Whiteboard, Mind Map, PDF Intake, AI Diagram Studio, Video Studio, Research Agent, New Research Topic, Skills Manager, OpenAPI Routing, Manim Sandbox, Settings.","Repurpose here means mining for specific modules, algorithms, UI patterns, ingestion logic, workflow ideas, or export formats rather than assuming a full product transplant.",native/scriptoriumai-ui,native/ScriptoriumAI-Server,abhigyanpatwari/GitNexus,"Return concrete files/modules/adapters worth reusing and a verdict on whether the current reanchored bucket should be kept, upgraded, or downgraded.",Do not treat licensing as a filter. Do not propose replacing native foundations unless source evidence is overwhelming.,jwasham/coding-interview-university,v6_unified_source_of_truth_pack,"Before recommending direct code use, inspect the target repo row in the v6.1 operational/phase/source-audit boards. Respect copyleft_strategy_v6_1, preferred_boundary_model_v6_1, and open_compliance_if_used_as_is_v6_1. Do not assume reverse engineering is mandatory or that as-is use is always sensible.","If the repo-level strategy says bounded_sidecar_preferred or boundary_first_then_decide_as_is_vs_reimplementation, audit clean interfaces, protocol seams, subprocess/container boundaries, and what would be required to reimplement only the strategically necessary portions.",v6.3_final_source_of_truth
SCR_0269,,,,,,,,,,ScriptoriumAI repo packet,ScriptoriumAI,ScriptoriumAI re-anchored VS Code packets v1,manimcommunity/jupyter_manim,manimcommunity/jupyter_manim,Exclude Current Horizon,P3,bookmark candidate only,"Audit manimcommunity/jupyter_manim for ScriptoriumAI. Start from the reanchored bucket 'Exclude Current Horizon' and current reality status 'bookmark candidate only'. Confirm actual implemented capability, hidden reusable modules, extension seams, and whether it strengthens the existing Off-axis candidate for current ScriptoriumAI baseline lane. Focus on: Inspect hidden modules, extension seams, data contracts, rendering paths, auth/storage coupling, and export/import boundaries.",,"Treat as unimplemented ScriptoriumAI candidate only. Do not let it redefine the current stack. Integrate only if a later audit proves it fills a real gap in the existing surfaces such as Dashboard, Editor, Corpus Graph, Runboard, AI Kanban, Corpus Search, Patch Review Queue, Visualizations, Whiteboard, Mind Map, PDF Intake, AI Diagram Studio, Video Studio, Research Agent, New Research Topic, Skills Manager, OpenAPI Routing, Manim Sandbox, Settings.","Repurpose here means mining for specific modules, algorithms, UI patterns, ingestion logic, workflow ideas, or export formats rather than assuming a full product transplant.",manimcommunity/manim,remotion-dev/remotion,native/ScriptoriumAI-Visualizer,"Return concrete files/modules/adapters worth reusing and a verdict on whether the current reanchored bucket should be kept, upgraded, or downgraded.",Do not treat licensing as a filter. Do not propose replacing native foundations unless source evidence is overwhelming.,manimcommunity/jupyter_manim,v6_unified_source_of_truth_pack,"Before recommending direct code use, inspect the target repo row in the v6.1 operational/phase/source-audit boards. Respect copyleft_strategy_v6_1, preferred_boundary_model_v6_1, and open_compliance_if_used_as_is_v6_1. Do not assume reverse engineering is mandatory or that as-is use is always sensible.","If the repo-level strategy says bounded_sidecar_preferred or boundary_first_then_decide_as_is_vs_reimplementation, audit clean interfaces, protocol seams, subprocess/container boundaries, and what would be required to reimplement only the strategically necessary portions.",v6.3_final_source_of_truth
SCR_0270,,,,,,,,,,ScriptoriumAI repo packet,ScriptoriumAI,ScriptoriumAI re-anchored VS Code packets v1,manimcommunity/manim-studio,manimcommunity/manim-studio,Exclude Current Horizon,P3,bookmark candidate only,"Audit manimcommunity/manim-studio for ScriptoriumAI. Start from the reanchored bucket 'Exclude Current Horizon' and current reality status 'bookmark candidate only'. Confirm actual implemented capability, hidden reusable modules, extension seams, and whether it strengthens the existing Off-axis candidate for current ScriptoriumAI baseline lane. Focus on: Inspect hidden modules, extension seams, data contracts, rendering paths, auth/storage coupling, and export/import boundaries.",,"Treat as unimplemented ScriptoriumAI candidate only. Do not let it redefine the current stack. Integrate only if a later audit proves it fills a real gap in the existing surfaces such as Dashboard, Editor, Corpus Graph, Runboard, AI Kanban, Corpus Search, Patch Review Queue, Visualizations, Whiteboard, Mind Map, PDF Intake, AI Diagram Studio, Video Studio, Research Agent, New Research Topic, Skills Manager, OpenAPI Routing, Manim Sandbox, Settings.","Repurpose here means mining for specific modules, algorithms, UI patterns, ingestion logic, workflow ideas, or export formats rather than assuming a full product transplant.",manimcommunity/manim,remotion-dev/remotion,native/ScriptoriumAI-Visualizer,"Return concrete files/modules/adapters worth reusing and a verdict on whether the current reanchored bucket should be kept, upgraded, or downgraded.",Do not treat licensing as a filter. Do not propose replacing native foundations unless source evidence is overwhelming.,manimcommunity/manim-studio,v6_unified_source_of_truth_pack,"Before recommending direct code use, inspect the target repo row in the v6.1 operational/phase/source-audit boards. Respect copyleft_strategy_v6_1, preferred_boundary_model_v6_1, and open_compliance_if_used_as_is_v6_1. Do not assume reverse engineering is mandatory or that as-is use is always sensible.","If the repo-level strategy says bounded_sidecar_preferred or boundary_first_then_decide_as_is_vs_reimplementation, audit clean interfaces, protocol seams, subprocess/container boundaries, and what would be required to reimplement only the strategically necessary portions.",v6.3_final_source_of_truth
SCR_0271,,,,,,,,,,ScriptoriumAI repo packet,ScriptoriumAI,ScriptoriumAI re-anchored VS Code packets v1,manimcommunity/manim-voiceover,manimcommunity/manim-voiceover,Exclude Current Horizon,P3,bookmark candidate only,"Audit manimcommunity/manim-voiceover for ScriptoriumAI. Start from the reanchored bucket 'Exclude Current Horizon' and current reality status 'bookmark candidate only'. Confirm actual implemented capability, hidden reusable modules, extension seams, and whether it strengthens the existing Off-axis candidate for current ScriptoriumAI baseline lane. Focus on: Inspect hidden modules, extension seams, data contracts, rendering paths, auth/storage coupling, and export/import boundaries.",,"Treat as unimplemented ScriptoriumAI candidate only. Do not let it redefine the current stack. Integrate only if a later audit proves it fills a real gap in the existing surfaces such as Dashboard, Editor, Corpus Graph, Runboard, AI Kanban, Corpus Search, Patch Review Queue, Visualizations, Whiteboard, Mind Map, PDF Intake, AI Diagram Studio, Video Studio, Research Agent, New Research Topic, Skills Manager, OpenAPI Routing, Manim Sandbox, Settings.","Repurpose here means mining for specific modules, algorithms, UI patterns, ingestion logic, workflow ideas, or export formats rather than assuming a full product transplant.",manimcommunity/manim,remotion-dev/remotion,native/ScriptoriumAI-Visualizer,"Return concrete files/modules/adapters worth reusing and a verdict on whether the current reanchored bucket should be kept, upgraded, or downgraded.",Do not treat licensing as a filter. Do not propose replacing native foundations unless source evidence is overwhelming.,manimcommunity/manim-voiceover,v6_unified_source_of_truth_pack,"Before recommending direct code use, inspect the target repo row in the v6.1 operational/phase/source-audit boards. Respect copyleft_strategy_v6_1, preferred_boundary_model_v6_1, and open_compliance_if_used_as_is_v6_1. Do not assume reverse engineering is mandatory or that as-is use is always sensible.","If the repo-level strategy says bounded_sidecar_preferred or boundary_first_then_decide_as_is_vs_reimplementation, audit clean interfaces, protocol seams, subprocess/container boundaries, and what would be required to reimplement only the strategically necessary portions.",v6.3_final_source_of_truth
SCR_0272,,,,,,,,,,ScriptoriumAI repo packet,ScriptoriumAI,ScriptoriumAI re-anchored VS Code packets v1,manimcommunity/manim-web,manimcommunity/manim-web,Exclude Current Horizon,P3,bookmark candidate only,"Audit manimcommunity/manim-web for ScriptoriumAI. Start from the reanchored bucket 'Exclude Current Horizon' and current reality status 'bookmark candidate only'. Confirm actual implemented capability, hidden reusable modules, extension seams, and whether it strengthens the existing Off-axis candidate for current ScriptoriumAI baseline lane. Focus on: Inspect hidden modules, extension seams, data contracts, rendering paths, auth/storage coupling, and export/import boundaries.",,"Treat as unimplemented ScriptoriumAI candidate only. Do not let it redefine the current stack. Integrate only if a later audit proves it fills a real gap in the existing surfaces such as Dashboard, Editor, Corpus Graph, Runboard, AI Kanban, Corpus Search, Patch Review Queue, Visualizations, Whiteboard, Mind Map, PDF Intake, AI Diagram Studio, Video Studio, Research Agent, New Research Topic, Skills Manager, OpenAPI Routing, Manim Sandbox, Settings.","Repurpose here means mining for specific modules, algorithms, UI patterns, ingestion logic, workflow ideas, or export formats rather than assuming a full product transplant.",manimcommunity/manim,remotion-dev/remotion,native/ScriptoriumAI-Visualizer,"Return concrete files/modules/adapters worth reusing and a verdict on whether the current reanchored bucket should be kept, upgraded, or downgraded.",Do not treat licensing as a filter. Do not propose replacing native foundations unless source evidence is overwhelming.,manimcommunity/manim-web,v6_unified_source_of_truth_pack,"Before recommending direct code use, inspect the target repo row in the v6.1 operational/phase/source-audit boards. Respect copyleft_strategy_v6_1, preferred_boundary_model_v6_1, and open_compliance_if_used_as_is_v6_1. Do not assume reverse engineering is mandatory or that as-is use is always sensible.","If the repo-level strategy says bounded_sidecar_preferred or boundary_first_then_decide_as_is_vs_reimplementation, audit clean interfaces, protocol seams, subprocess/container boundaries, and what would be required to reimplement only the strategically necessary portions.",v6.3_final_source_of_truth
SCR_0273,,,,,,,,,,ScriptoriumAI repo packet,ScriptoriumAI,ScriptoriumAI re-anchored VS Code packets v1,manimcommunity/manim_editor,manimcommunity/manim_editor,Exclude Current Horizon,P3,bookmark candidate only,"Audit manimcommunity/manim_editor for ScriptoriumAI. Start from the reanchored bucket 'Exclude Current Horizon' and current reality status 'bookmark candidate only'. Confirm actual implemented capability, hidden reusable modules, extension seams, and whether it strengthens the existing Off-axis candidate for current ScriptoriumAI baseline lane. Focus on: Inspect hidden modules, extension seams, data contracts, rendering paths, auth/storage coupling, and export/import boundaries.",,"Treat as unimplemented ScriptoriumAI candidate only. Do not let it redefine the current stack. Integrate only if a later audit proves it fills a real gap in the existing surfaces such as Dashboard, Editor, Corpus Graph, Runboard, AI Kanban, Corpus Search, Patch Review Queue, Visualizations, Whiteboard, Mind Map, PDF Intake, AI Diagram Studio, Video Studio, Research Agent, New Research Topic, Skills Manager, OpenAPI Routing, Manim Sandbox, Settings.","Repurpose here means mining for specific modules, algorithms, UI patterns, ingestion logic, workflow ideas, or export formats rather than assuming a full product transplant.",native/scriptoriumai-ui,native/ScriptoriumAI-Server,sharelatex/sharelatex,"Return concrete files/modules/adapters worth reusing and a verdict on whether the current reanchored bucket should be kept, upgraded, or downgraded.",Do not treat licensing as a filter. Do not propose replacing native foundations unless source evidence is overwhelming.,manimcommunity/manim_editor,v6_unified_source_of_truth_pack,"Before recommending direct code use, inspect the target repo row in the v6.1 operational/phase/source-audit boards. Respect copyleft_strategy_v6_1, preferred_boundary_model_v6_1, and open_compliance_if_used_as_is_v6_1. Do not assume reverse engineering is mandatory or that as-is use is always sensible.","If the repo-level strategy says bounded_sidecar_preferred or boundary_first_then_decide_as_is_vs_reimplementation, audit clean interfaces, protocol seams, subprocess/container boundaries, and what would be required to reimplement only the strategically necessary portions.",v6.3_final_source_of_truth
SCR_0274,,,,,,,,,,ScriptoriumAI repo packet,ScriptoriumAI,ScriptoriumAI re-anchored VS Code packets v1,manimcommunity/manimpango,manimcommunity/manimpango,Exclude Current Horizon,P3,bookmark candidate only,"Audit manimcommunity/manimpango for ScriptoriumAI. Start from the reanchored bucket 'Exclude Current Horizon' and current reality status 'bookmark candidate only'. Confirm actual implemented capability, hidden reusable modules, extension seams, and whether it strengthens the existing Off-axis candidate for current ScriptoriumAI baseline lane. Focus on: Inspect hidden modules, extension seams, data contracts, rendering paths, auth/storage coupling, and export/import boundaries.",,"Treat as unimplemented ScriptoriumAI candidate only. Do not let it redefine the current stack. Integrate only if a later audit proves it fills a real gap in the existing surfaces such as Dashboard, Editor, Corpus Graph, Runboard, AI Kanban, Corpus Search, Patch Review Queue, Visualizations, Whiteboard, Mind Map, PDF Intake, AI Diagram Studio, Video Studio, Research Agent, New Research Topic, Skills Manager, OpenAPI Routing, Manim Sandbox, Settings.","Repurpose here means mining for specific modules, algorithms, UI patterns, ingestion logic, workflow ideas, or export formats rather than assuming a full product transplant.",manimcommunity/manim,remotion-dev/remotion,native/ScriptoriumAI-Visualizer,"Return concrete files/modules/adapters worth reusing and a verdict on whether the current reanchored bucket should be kept, upgraded, or downgraded.",Do not treat licensing as a filter. Do not propose replacing native foundations unless source evidence is overwhelming.,manimcommunity/manimpango,v6_unified_source_of_truth_pack,"Before recommending direct code use, inspect the target repo row in the v6.1 operational/phase/source-audit boards. Respect copyleft_strategy_v6_1, preferred_boundary_model_v6_1, and open_compliance_if_used_as_is_v6_1. Do not assume reverse engineering is mandatory or that as-is use is always sensible.","If the repo-level strategy says bounded_sidecar_preferred or boundary_first_then_decide_as_is_vs_reimplementation, audit clean interfaces, protocol seams, subprocess/container boundaries, and what would be required to reimplement only the strategically necessary portions.",v6.3_final_source_of_truth
SCR_0275,,,,,,,,,,ScriptoriumAI repo packet,ScriptoriumAI,ScriptoriumAI re-anchored VS Code packets v1,mintty/mintty,mintty/mintty,Exclude Current Horizon,P3,bookmark candidate only,"Audit mintty/mintty for ScriptoriumAI. Start from the reanchored bucket 'Exclude Current Horizon' and current reality status 'bookmark candidate only'. Confirm actual implemented capability, hidden reusable modules, extension seams, and whether it strengthens the existing Off-axis candidate for current ScriptoriumAI baseline lane. Focus on: Inspect document/block schema; sync/persistence model; permissions and sharing; citation/external-source pipeline; import/export adapters; plugin/extension points; editor rendering model.","Inspect package manifests, README/docs, src tree, examples, tests, CI workflows, config files, migrations/schemas, and hidden feature flags or experimental modules. Look for document/block schema, sync/conflict logic, citation handling, editor plugins, export/render pipeline, prompt chains, report assembly, and collaborative presence code.","Treat as unimplemented ScriptoriumAI candidate only. Do not let it redefine the current stack. Integrate only if a later audit proves it fills a real gap in the existing surfaces such as Dashboard, Editor, Corpus Graph, Runboard, AI Kanban, Corpus Search, Patch Review Queue, Visualizations, Whiteboard, Mind Map, PDF Intake, AI Diagram Studio, Video Studio, Research Agent, New Research Topic, Skills Manager, OpenAPI Routing, Manim Sandbox, Settings.","Repurpose here means mining for specific modules, algorithms, UI patterns, ingestion logic, workflow ideas, or export formats rather than assuming a full product transplant.",native/scriptoriumai-ui,native/ScriptoriumAI-Server,abhigyanpatwari/GitNexus,"Return concrete files/modules/adapters worth reusing and a verdict on whether the current reanchored bucket should be kept, upgraded, or downgraded.",Do not treat licensing as a filter. Do not propose replacing native foundations unless source evidence is overwhelming.,mintty/mintty,v6_unified_source_of_truth_pack,"Before recommending direct code use, inspect the target repo row in the v6.1 operational/phase/source-audit boards. Respect copyleft_strategy_v6_1, preferred_boundary_model_v6_1, and open_compliance_if_used_as_is_v6_1. Do not assume reverse engineering is mandatory or that as-is use is always sensible.","If the repo-level strategy says bounded_sidecar_preferred or boundary_first_then_decide_as_is_vs_reimplementation, audit clean interfaces, protocol seams, subprocess/container boundaries, and what would be required to reimplement only the strategically necessary portions.",v6.3_final_source_of_truth
SCR_0276,,,,,,,,,,ScriptoriumAI repo packet,ScriptoriumAI,ScriptoriumAI re-anchored VS Code packets v1,ohmyzsh/ohmyzsh,ohmyzsh/ohmyzsh,Exclude Current Horizon,P3,bookmark candidate only,"Audit ohmyzsh/ohmyzsh for ScriptoriumAI. Start from the reanchored bucket 'Exclude Current Horizon' and current reality status 'bookmark candidate only'. Confirm actual implemented capability, hidden reusable modules, extension seams, and whether it strengthens the existing Off-axis candidate for current ScriptoriumAI baseline lane. Focus on: Inspect document/block schema; sync/persistence model; permissions and sharing; citation/external-source pipeline; import/export adapters; plugin/extension points; editor rendering model.","Inspect package manifests, README/docs, src tree, examples, tests, CI workflows, config files, migrations/schemas, and hidden feature flags or experimental modules. Look for document/block schema, sync/conflict logic, citation handling, editor plugins, export/render pipeline, prompt chains, report assembly, and collaborative presence code.","Treat as unimplemented ScriptoriumAI candidate only. Do not let it redefine the current stack. Integrate only if a later audit proves it fills a real gap in the existing surfaces such as Dashboard, Editor, Corpus Graph, Runboard, AI Kanban, Corpus Search, Patch Review Queue, Visualizations, Whiteboard, Mind Map, PDF Intake, AI Diagram Studio, Video Studio, Research Agent, New Research Topic, Skills Manager, OpenAPI Routing, Manim Sandbox, Settings.","Repurpose here means mining for specific modules, algorithms, UI patterns, ingestion logic, workflow ideas, or export formats rather than assuming a full product transplant.",native/scriptoriumai-ui,native/ScriptoriumAI-Server,abhigyanpatwari/GitNexus,"Return concrete files/modules/adapters worth reusing and a verdict on whether the current reanchored bucket should be kept, upgraded, or downgraded.",Do not treat licensing as a filter. Do not propose replacing native foundations unless source evidence is overwhelming.,ohmyzsh/ohmyzsh,v6_unified_source_of_truth_pack,"Before recommending direct code use, inspect the target repo row in the v6.1 operational/phase/source-audit boards. Respect copyleft_strategy_v6_1, preferred_boundary_model_v6_1, and open_compliance_if_used_as_is_v6_1. Do not assume reverse engineering is mandatory or that as-is use is always sensible.","If the repo-level strategy says bounded_sidecar_preferred or boundary_first_then_decide_as_is_vs_reimplementation, audit clean interfaces, protocol seams, subprocess/container boundaries, and what would be required to reimplement only the strategically necessary portions.",v6.3_final_source_of_truth
SCR_0277,,,,,,,,,,ScriptoriumAI repo packet,ScriptoriumAI,ScriptoriumAI re-anchored VS Code packets v1,paperless-ngx/paperless-ngx,paperless-ngx/paperless-ngx,Exclude Current Horizon,P3,bookmark candidate only,"Audit paperless-ngx/paperless-ngx for ScriptoriumAI. Start from the reanchored bucket 'Exclude Current Horizon' and current reality status 'bookmark candidate only'. Confirm actual implemented capability, hidden reusable modules, extension seams, and whether it strengthens the existing Off-axis candidate for current ScriptoriumAI baseline lane. Focus on: Inspect document/block schema; sync/persistence model; permissions and sharing; citation/external-source pipeline; import/export adapters; plugin/extension points; editor rendering model.","Inspect package manifests, README/docs, src tree, examples, tests, CI workflows, config files, migrations/schemas, and hidden feature flags or experimental modules. Look for document/block schema, sync/conflict logic, citation handling, editor plugins, export/render pipeline, prompt chains, report assembly, and collaborative presence code.","Treat as unimplemented ScriptoriumAI candidate only. Do not let it redefine the current stack. Integrate only if a later audit proves it fills a real gap in the existing surfaces such as Dashboard, Editor, Corpus Graph, Runboard, AI Kanban, Corpus Search, Patch Review Queue, Visualizations, Whiteboard, Mind Map, PDF Intake, AI Diagram Studio, Video Studio, Research Agent, New Research Topic, Skills Manager, OpenAPI Routing, Manim Sandbox, Settings.","Repurpose here means mining for specific modules, algorithms, UI patterns, ingestion logic, workflow ideas, or export formats rather than assuming a full product transplant.",pdfmd/pdfmd,lukas-blecher/latex-ocr,mli55/pdfdelta,"Return concrete files/modules/adapters worth reusing and a verdict on whether the current reanchored bucket should be kept, upgraded, or downgraded.",Do not treat licensing as a filter. Do not propose replacing native foundations unless source evidence is overwhelming.,paperless-ngx/paperless-ngx,v6_unified_source_of_truth_pack,"Before recommending direct code use, inspect the target repo row in the v6.1 operational/phase/source-audit boards. Respect copyleft_strategy_v6_1, preferred_boundary_model_v6_1, and open_compliance_if_used_as_is_v6_1. Do not assume reverse engineering is mandatory or that as-is use is always sensible.","If the repo-level strategy says bounded_sidecar_preferred or boundary_first_then_decide_as_is_vs_reimplementation, audit clean interfaces, protocol seams, subprocess/container boundaries, and what would be required to reimplement only the strategically necessary portions.",v6.3_final_source_of_truth
SCR_0278,,,,,,,,,,ScriptoriumAI repo packet,ScriptoriumAI,ScriptoriumAI re-anchored VS Code packets v1,sickn33/antigravity-awesome-skills,sickn33/antigravity-awesome-skills,Exclude Current Horizon,P3,bookmark candidate only,"Audit sickn33/antigravity-awesome-skills for ScriptoriumAI. Start from the reanchored bucket 'Exclude Current Horizon' and current reality status 'bookmark candidate only'. Confirm actual implemented capability, hidden reusable modules, extension seams, and whether it strengthens the existing Off-axis candidate for current ScriptoriumAI baseline lane. Focus on: 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.","Treat as unimplemented ScriptoriumAI candidate only. Do not let it redefine the current stack. Integrate only if a later audit proves it fills a real gap in the existing surfaces such as Dashboard, Editor, Corpus Graph, Runboard, AI Kanban, Corpus Search, Patch Review Queue, Visualizations, Whiteboard, Mind Map, PDF Intake, AI Diagram Studio, Video Studio, Research Agent, New Research Topic, Skills Manager, OpenAPI Routing, Manim Sandbox, Settings.","Repurpose here means mining for specific modules, algorithms, UI patterns, ingestion logic, workflow ideas, or export formats rather than assuming a full product transplant.",native/ScriptoriumAI-Server,stanford-oval/storm,abhigyanpatwari/GitNexus,"Return concrete files/modules/adapters worth reusing and a verdict on whether the current reanchored bucket should be kept, upgraded, or downgraded.",Do not treat licensing as a filter. Do not propose replacing native foundations unless source evidence is overwhelming.,sickn33/antigravity-awesome-skills,v6_unified_source_of_truth_pack,"Before recommending direct code use, inspect the target repo row in the v6.1 operational/phase/source-audit boards. Respect copyleft_strategy_v6_1, preferred_boundary_model_v6_1, and open_compliance_if_used_as_is_v6_1. Do not assume reverse engineering is mandatory or that as-is use is always sensible.","If the repo-level strategy says bounded_sidecar_preferred or boundary_first_then_decide_as_is_vs_reimplementation, audit clean interfaces, protocol seams, subprocess/container boundaries, and what would be required to reimplement only the strategically necessary portions.",v6.3_final_source_of_truth
SCR_0279,,,,,,,,,,ScriptoriumAI repo packet,ScriptoriumAI,ScriptoriumAI re-anchored VS Code packets v1,src-d/blog,src-d/blog,Exclude Current Horizon,P3,bookmark candidate only,"Audit src-d/blog for ScriptoriumAI. Start from the reanchored bucket 'Exclude Current Horizon' and current reality status 'bookmark candidate only'. Confirm actual implemented capability, hidden reusable modules, extension seams, and whether it strengthens the existing Off-axis candidate for current ScriptoriumAI baseline lane. Focus on: Inspect parsers and language adapters; graph schema and storage; incremental indexing/update logic; layout engine; query API; export/import formats; test fixtures for graph correctness.","Inspect package manifests, README/docs, src tree, examples, tests, CI workflows, config files, migrations/schemas, and hidden feature flags or experimental modules. Look for hidden admin tools, reusable services, plugin systems, import/export, analytics, background jobs, and any engine more valuable than the public README suggests.","Treat as unimplemented ScriptoriumAI candidate only. Do not let it redefine the current stack. Integrate only if a later audit proves it fills a real gap in the existing surfaces such as Dashboard, Editor, Corpus Graph, Runboard, AI Kanban, Corpus Search, Patch Review Queue, Visualizations, Whiteboard, Mind Map, PDF Intake, AI Diagram Studio, Video Studio, Research Agent, New Research Topic, Skills Manager, OpenAPI Routing, Manim Sandbox, Settings.","Repurpose here means mining for specific modules, algorithms, UI patterns, ingestion logic, workflow ideas, or export formats rather than assuming a full product transplant.",native/scriptoriumai-ui,native/ScriptoriumAI-Server,abhigyanpatwari/GitNexus,"Return concrete files/modules/adapters worth reusing and a verdict on whether the current reanchored bucket should be kept, upgraded, or downgraded.",Do not treat licensing as a filter. Do not propose replacing native foundations unless source evidence is overwhelming.,src-d/blog,v6_unified_source_of_truth_pack,"Before recommending direct code use, inspect the target repo row in the v6.1 operational/phase/source-audit boards. Respect copyleft_strategy_v6_1, preferred_boundary_model_v6_1, and open_compliance_if_used_as_is_v6_1. Do not assume reverse engineering is mandatory or that as-is use is always sensible.","If the repo-level strategy says bounded_sidecar_preferred or boundary_first_then_decide_as_is_vs_reimplementation, audit clean interfaces, protocol seams, subprocess/container boundaries, and what would be required to reimplement only the strategically necessary portions.",v6.3_final_source_of_truth
SCR_0280,,,,,,,,,,ScriptoriumAI repo packet,ScriptoriumAI,ScriptoriumAI re-anchored VS Code packets v1,supabase-community/copycat,supabase-community/copycat,Exclude Current Horizon,P3,bookmark candidate only,"Audit supabase-community/copycat for ScriptoriumAI. Start from the reanchored bucket 'Exclude Current Horizon' and current reality status 'bookmark candidate only'. Confirm actual implemented capability, hidden reusable modules, extension seams, and whether it strengthens the existing Off-axis candidate for current ScriptoriumAI baseline lane. Focus on: Inspect package/module map; entrypoints; config and schema files; adapters/integrations; persistence model; tests/examples; hidden feature flags; plugin 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 hidden admin tools, reusable services, plugin systems, import/export, analytics, background jobs, and any engine more valuable than the public README suggests.","Treat as unimplemented ScriptoriumAI candidate only. Do not let it redefine the current stack. Integrate only if a later audit proves it fills a real gap in the existing surfaces such as Dashboard, Editor, Corpus Graph, Runboard, AI Kanban, Corpus Search, Patch Review Queue, Visualizations, Whiteboard, Mind Map, PDF Intake, AI Diagram Studio, Video Studio, Research Agent, New Research Topic, Skills Manager, OpenAPI Routing, Manim Sandbox, Settings.","Repurpose here means mining for specific modules, algorithms, UI patterns, ingestion logic, workflow ideas, or export formats rather than assuming a full product transplant.",native/scriptoriumai-ui,native/ScriptoriumAI-Server,abhigyanpatwari/GitNexus,"Return concrete files/modules/adapters worth reusing and a verdict on whether the current reanchored bucket should be kept, upgraded, or downgraded.",Do not treat licensing as a filter. Do not propose replacing native foundations unless source evidence is overwhelming.,supabase-community/copycat,v6_unified_source_of_truth_pack,"Before recommending direct code use, inspect the target repo row in the v6.1 operational/phase/source-audit boards. Respect copyleft_strategy_v6_1, preferred_boundary_model_v6_1, and open_compliance_if_used_as_is_v6_1. Do not assume reverse engineering is mandatory or that as-is use is always sensible.","If the repo-level strategy says bounded_sidecar_preferred or boundary_first_then_decide_as_is_vs_reimplementation, audit clean interfaces, protocol seams, subprocess/container boundaries, and what would be required to reimplement only the strategically necessary portions.",v6.3_final_source_of_truth
SCR_0281,,,,,,,,,,ScriptoriumAI repo packet,ScriptoriumAI,ScriptoriumAI re-anchored VS Code packets v1,unity-atoms/unity-atoms,unity-atoms/unity-atoms,Exclude Current Horizon,P3,bookmark candidate only,"Audit unity-atoms/unity-atoms for ScriptoriumAI. Start from the reanchored bucket 'Exclude Current Horizon' and current reality status 'bookmark candidate only'. Confirm actual implemented capability, hidden reusable modules, extension seams, and whether it strengthens the existing Off-axis candidate for current ScriptoriumAI baseline lane. Focus on: 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.","Treat as unimplemented ScriptoriumAI candidate only. Do not let it redefine the current stack. Integrate only if a later audit proves it fills a real gap in the existing surfaces such as Dashboard, Editor, Corpus Graph, Runboard, AI Kanban, Corpus Search, Patch Review Queue, Visualizations, Whiteboard, Mind Map, PDF Intake, AI Diagram Studio, Video Studio, Research Agent, New Research Topic, Skills Manager, OpenAPI Routing, Manim Sandbox, Settings.","Repurpose here means mining for specific modules, algorithms, UI patterns, ingestion logic, workflow ideas, or export formats rather than assuming a full product transplant.",native/scriptoriumai-ui,native/ScriptoriumAI-Server,abhigyanpatwari/GitNexus,"Return concrete files/modules/adapters worth reusing and a verdict on whether the current reanchored bucket should be kept, upgraded, or downgraded.",Do not treat licensing as a filter. Do not propose replacing native foundations unless source evidence is overwhelming.,unity-atoms/unity-atoms,v6_unified_source_of_truth_pack,"Before recommending direct code use, inspect the target repo row in the v6.1 operational/phase/source-audit boards. Respect copyleft_strategy_v6_1, preferred_boundary_model_v6_1, and open_compliance_if_used_as_is_v6_1. Do not assume reverse engineering is mandatory or that as-is use is always sensible.","If the repo-level strategy says bounded_sidecar_preferred or boundary_first_then_decide_as_is_vs_reimplementation, audit clean interfaces, protocol seams, subprocess/container boundaries, and what would be required to reimplement only the strategically necessary portions.",v6.3_final_source_of_truth
SCR_0282,,,,,,,,,,ScriptoriumAI repo packet,ScriptoriumAI,ScriptoriumAI re-anchored VS Code packets v1,xceedsoftware/Xceed-Toolkit-for-.NET-MAUI,xceedsoftware/xceed-toolkit-for-.net-maui,Exclude Current Horizon,P3,bookmark candidate only,"Audit xceedsoftware/Xceed-Toolkit-for-.NET-MAUI for ScriptoriumAI. Start from the reanchored bucket 'Exclude Current Horizon' and current reality status 'bookmark candidate only'. Confirm actual implemented capability, hidden reusable modules, extension seams, and whether it strengthens the existing Off-axis candidate for current ScriptoriumAI baseline lane. Focus on: 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.","Treat as unimplemented ScriptoriumAI candidate only. Do not let it redefine the current stack. Integrate only if a later audit proves it fills a real gap in the existing surfaces such as Dashboard, Editor, Corpus Graph, Runboard, AI Kanban, Corpus Search, Patch Review Queue, Visualizations, Whiteboard, Mind Map, PDF Intake, AI Diagram Studio, Video Studio, Research Agent, New Research Topic, Skills Manager, OpenAPI Routing, Manim Sandbox, Settings.","Repurpose here means mining for specific modules, algorithms, UI patterns, ingestion logic, workflow ideas, or export formats rather than assuming a full product transplant.",native/scriptoriumai-ui,native/ScriptoriumAI-Server,abhigyanpatwari/GitNexus,"Return concrete files/modules/adapters worth reusing and a verdict on whether the current reanchored bucket should be kept, upgraded, or downgraded.",Do not treat licensing as a filter. Do not propose replacing native foundations unless source evidence is overwhelming.,xceedsoftware/xceed-toolkit-for-.net-maui,v6_unified_source_of_truth_pack,"Before recommending direct code use, inspect the target repo row in the v6.1 operational/phase/source-audit boards. Respect copyleft_strategy_v6_1, preferred_boundary_model_v6_1, and open_compliance_if_used_as_is_v6_1. Do not assume reverse engineering is mandatory or that as-is use is always sensible.","If the repo-level strategy says bounded_sidecar_preferred or boundary_first_then_decide_as_is_vs_reimplementation, audit clean interfaces, protocol seams, subprocess/container boundaries, and what would be required to reimplement only the strategically necessary portions.",v6.3_final_source_of_truth
SCR_0283,,,,,,,,,,ScriptoriumAI repo packet,ScriptoriumAI,ScriptoriumAI re-anchored VS Code packets v1,native/ScriptoriumAi-Orchestrator,native/scriptoriumai-orchestrator,Merge Bench,P1,scaffold additive,"Audit native/ScriptoriumAi-Orchestrator for ScriptoriumAI. Start from the reanchored bucket 'Merge Bench' and current reality status 'scaffold additive'. Confirm actual implemented capability, hidden reusable modules, extension seams, and whether it strengthens the existing Additive orchestration sidecar lane. Focus on: Which internal boundaries are stable? Which adapters are already abstracted? Which local modules are overloaded and should be split?","Inspect internal service boundaries, adapters, route-level dependencies, state stores, auth guards, compile coordination, tests, and extension seams.",Treat this as a non-external native anchor. External repo decisions should now be made around this anchor rather than replacing it.,Native anchor; repurpose logic does not apply except by splitting submodules into reusable internal services.,,,,"Return concrete files/modules/adapters worth reusing and a verdict on whether the current reanchored bucket should be kept, upgraded, or downgraded.",Do not treat licensing as a filter. Do not propose replacing native foundations unless source evidence is overwhelming.,native/scriptoriumai-orchestrator,v6_unified_source_of_truth_pack,"Before recommending direct code use, inspect the target repo row in the v6.1 operational/phase/source-audit boards. Respect copyleft_strategy_v6_1, preferred_boundary_model_v6_1, and open_compliance_if_used_as_is_v6_1. Do not assume reverse engineering is mandatory or that as-is use is always sensible.","If the repo-level strategy says bounded_sidecar_preferred or boundary_first_then_decide_as_is_vs_reimplementation, audit clean interfaces, protocol seams, subprocess/container boundaries, and what would be required to reimplement only the strategically necessary portions.",v6.3_final_source_of_truth
V6-P0-VS-PLATFORM,VectorShell Platform / Orchestration / Observability Core,docker + kubernetes + core platform donors,docker/cli ; docker/compose ; kubernetes/client-go ; kubernetes/api ; kubernetes/apimachinery,Decide which platform repos become true VectorShell live-infrastructure donors rather than mere references.,"CLI/API clients, metrics/resource models, topology/event schemas, controller/operator patterns, machine-readable outputs.",Which repos provide the strongest bridge into the hyperspace world model? Which are core runtime donors vs merely docs/examples?,"Per-repo donor decision, output contracts, bridge integration notes, promotion/demotion triggers.","Prefer repos with direct machine-readable outputs, stable APIs, strong topology models, and clear bridgeability.","Audit the following v6 packet: VectorShell Platform / Orchestration / Observability Core. Inspect the listed repos in source and extract real capability, reusable subsystems, upgrade triggers, downgrade triggers, and exact integration paths.",family_packet,VectorShell weightless hyperspace + runtime/observability overlays.,v6_unified_source_of_truth_pack,,,,P0,supplemental_v6_packet,"Use v6 as the source of truth. Decide which platform repos become true VectorShell live-infrastructure donors rather than mere references. Focus on: CLI/API clients, metrics/resource models, topology/event schemas, controller/operator patterns, machine-readable outputs.. Answer: Which repos provide the strongest bridge into the hyperspace world model? Which are core runtime donors vs merely docs/examples?.","CLI/API clients, metrics/resource models, topology/event schemas, controller/operator patterns, machine-readable outputs.",VectorShell weightless hyperspace + runtime/observability overlays.,Repurpose according to v6 project design language and family role.,,,,"Per-repo donor decision, output contracts, bridge integration notes, promotion/demotion triggers.",,,,"Before recommending direct code use, inspect the target repo row in the v6.1 operational/phase/source-audit boards. Respect copyleft_strategy_v6_1, preferred_boundary_model_v6_1, and open_compliance_if_used_as_is_v6_1. Do not assume reverse engineering is mandatory or that as-is use is always sensible.","If the repo-level strategy says bounded_sidecar_preferred or boundary_first_then_decide_as_is_vs_reimplementation, audit clean interfaces, protocol seams, subprocess/container boundaries, and what would be required to reimplement only the strategically necessary portions.",v6.3_final_source_of_truth
V6-P0-VS-SECURITY,VectorShell Security Overlay Core,projectdiscovery + Semgrep + ZAP + core security feeds,projectdiscovery/nuclei ; projectdiscovery/httpx ; projectdiscovery/subfinder ; semgrep/semgrep ; zaproxy/zaproxy,Identify the strongest core security feeds for VectorShell attack-path and recon overlays.,"Scanner outputs, template/rule systems, API/CLI emitters, graph or risk models, replay-friendly data.","Which repos are strategic overlay feeders, which are secondary utilities, and which should remain comparator-only?","Overlay integration notes, output normalization plan, source-audit reclassification decision.",Prefer repos with clear machine outputs and reusable parser-friendly structures.,"Audit the following v6 packet: VectorShell Security Overlay Core. Inspect the listed repos in source and extract real capability, reusable subsystems, upgrade triggers, downgrade triggers, and exact integration paths.",family_packet,VectorShell red-team hyperspace and Kali-aware agent orchestration.,v6_unified_source_of_truth_pack,,,,P0,supplemental_v6_packet,"Use v6 as the source of truth. Identify the strongest core security feeds for VectorShell attack-path and recon overlays. Focus on: Scanner outputs, template/rule systems, API/CLI emitters, graph or risk models, replay-friendly data.. Answer: Which repos are strategic overlay feeders, which are secondary utilities, and which should remain comparator-only?.","Scanner outputs, template/rule systems, API/CLI emitters, graph or risk models, replay-friendly data.",VectorShell red-team hyperspace and Kali-aware agent orchestration.,Repurpose according to v6 project design language and family role.,,,,"Overlay integration notes, output normalization plan, source-audit reclassification decision.",,,,"Before recommending direct code use, inspect the target repo row in the v6.1 operational/phase/source-audit boards. Respect copyleft_strategy_v6_1, preferred_boundary_model_v6_1, and open_compliance_if_used_as_is_v6_1. Do not assume reverse engineering is mandatory or that as-is use is always sensible.","If the repo-level strategy says bounded_sidecar_preferred or boundary_first_then_decide_as_is_vs_reimplementation, audit clean interfaces, protocol seams, subprocess/container boundaries, and what would be required to reimplement only the strategically necessary portions.",v6.3_final_source_of_truth
V6-P0-AGENT-PROTOCOL,Agent / Protocol Control Plane Core,MCP + LangChain core families,modelcontextprotocol/specification ; modelcontextprotocol/modelcontextprotocol ; modelcontextprotocol/servers ; langchain-ai/langchain ; langchain-ai/langgraph ; langchain-ai/open-swe,"Determine the control-plane foundations that matter across VectorShell, ScriptoriumAI, and agentic workflows.","Protocol schemas, SDK abstractions, server templates, graph/runtime loops, tool adapters, registry shapes.","Which repos are foundations, which are donor benches, and which are connector sprawl best kept in reserve?","Control-plane architecture notes, protocol adoption guidance, upgrade/downgrade rationale.",Prefer reusable protocol/runtime cores over peripheral connectors.,"Audit the following v6 packet: Agent / Protocol Control Plane Core. Inspect the listed repos in source and extract real capability, reusable subsystems, upgrade triggers, downgrade triggers, and exact integration paths.",family_packet,Multi-project agent/protocol/coding-system horizon.,v6_unified_source_of_truth_pack,,,,P0,supplemental_v6_packet,"Use v6 as the source of truth. Determine the control-plane foundations that matter across VectorShell, ScriptoriumAI, and agentic workflows. Focus on: Protocol schemas, SDK abstractions, server templates, graph/runtime loops, tool adapters, registry shapes.. Answer: Which repos are foundations, which are donor benches, and which are connector sprawl best kept in reserve?.","Protocol schemas, SDK abstractions, server templates, graph/runtime loops, tool adapters, registry shapes.",Multi-project agent/protocol/coding-system horizon.,Repurpose according to v6 project design language and family role.,,,,"Control-plane architecture notes, protocol adoption guidance, upgrade/downgrade rationale.",,,,"Before recommending direct code use, inspect the target repo row in the v6.1 operational/phase/source-audit boards. Respect copyleft_strategy_v6_1, preferred_boundary_model_v6_1, and open_compliance_if_used_as_is_v6_1. Do not assume reverse engineering is mandatory or that as-is use is always sensible.","If the repo-level strategy says bounded_sidecar_preferred or boundary_first_then_decide_as_is_vs_reimplementation, audit clean interfaces, protocol seams, subprocess/container boundaries, and what would be required to reimplement only the strategically necessary portions.",v6.3_final_source_of_truth
V6-P0-HT-CORE,HyperTwist Supplemental Core,cubing + HactarCE core puzzle stack,cubing/cubing.js ; cubing/alg.js ; cubing/twisty.js ; HactarCE/hyperspeedcube,"Audit the extended HyperTwist core around logic, renderer, and puzzle-surface infrastructure.","State representations, algorithm parsers, scramblers, geometry cores, renderer abstractions, engine bindings.",Which new cubing/HactarCE repos materially deepen HyperTwist vs merely surround the existing core?,"Promotion notes, renderer/binding extraction notes, integration and merger decisions.",Prefer deep logic/renderer artifacts over peripheral branding or docs repos.,"Audit the following v6 packet: HyperTwist Supplemental Core. Inspect the listed repos in source and extract real capability, reusable subsystems, upgrade triggers, downgrade triggers, and exact integration paths.",family_packet,HyperTwist physical + virtual hypercube training stack.,v6_unified_source_of_truth_pack,,,,P0,supplemental_v6_packet,"Use v6 as the source of truth. Audit the extended HyperTwist core around logic, renderer, and puzzle-surface infrastructure. Focus on: State representations, algorithm parsers, scramblers, geometry cores, renderer abstractions, engine bindings.. Answer: Which new cubing/HactarCE repos materially deepen HyperTwist vs merely surround the existing core?.","State representations, algorithm parsers, scramblers, geometry cores, renderer abstractions, engine bindings.",HyperTwist physical + virtual hypercube training stack.,Repurpose according to v6 project design language and family role.,,,,"Promotion notes, renderer/binding extraction notes, integration and merger decisions.",,,,"Before recommending direct code use, inspect the target repo row in the v6.1 operational/phase/source-audit boards. Respect copyleft_strategy_v6_1, preferred_boundary_model_v6_1, and open_compliance_if_used_as_is_v6_1. Do not assume reverse engineering is mandatory or that as-is use is always sensible.","If the repo-level strategy says bounded_sidecar_preferred or boundary_first_then_decide_as_is_vs_reimplementation, audit clean interfaces, protocol seams, subprocess/container boundaries, and what would be required to reimplement only the strategically necessary portions.",v6.3_final_source_of_truth
V6-P0-SA-CORE,ScriptoriumAI Supplemental Core,Overleaf and realized workspace-adjacent additions,overleaf/overleaf ; overleaf/toolkit ; BerriAI/litellm ; remotion-dev/remotion,Audit supplemental repos that most directly touch the realized ScriptoriumAI runtime.,"Editor/collab boundaries, compile/toolkit adapters, routing/proxy layers, render/export pipelines.",What truly extends the realized stack without destabilizing it? What is already superseded by implementation?,"Runtime extension notes, boundary-safe integration path, demotion notes for weak duplicates.",Prefer repos that clearly align with the implemented ScriptoriumAI architecture snapshot.,"Audit the following v6 packet: ScriptoriumAI Supplemental Core. Inspect the listed repos in source and extract real capability, reusable subsystems, upgrade triggers, downgrade triggers, and exact integration paths.",family_packet,ScriptoriumAI reality-anchored workspace stack.,v6_unified_source_of_truth_pack,,,,P0,supplemental_v6_packet,"Use v6 as the source of truth. Audit supplemental repos that most directly touch the realized ScriptoriumAI runtime. Focus on: Editor/collab boundaries, compile/toolkit adapters, routing/proxy layers, render/export pipelines.. Answer: What truly extends the realized stack without destabilizing it? What is already superseded by implementation?.","Editor/collab boundaries, compile/toolkit adapters, routing/proxy layers, render/export pipelines.",ScriptoriumAI reality-anchored workspace stack.,Repurpose according to v6 project design language and family role.,,,,"Runtime extension notes, boundary-safe integration path, demotion notes for weak duplicates.",,,,"Before recommending direct code use, inspect the target repo row in the v6.1 operational/phase/source-audit boards. Respect copyleft_strategy_v6_1, preferred_boundary_model_v6_1, and open_compliance_if_used_as_is_v6_1. Do not assume reverse engineering is mandatory or that as-is use is always sensible.","If the repo-level strategy says bounded_sidecar_preferred or boundary_first_then_decide_as_is_vs_reimplementation, audit clean interfaces, protocol seams, subprocess/container boundaries, and what would be required to reimplement only the strategically necessary portions.",v6.3_final_source_of_truth
V6-P1-VS-KALI,VectorShell Kali Tooling Sweep,Kali packaging and tool-ingestion family,kalilinux/packages/amass ; kalilinux/packages/bloodhound ; kalilinux/packages/burpsuite ; kalilinux/packages/caldera ; kalilinux/packages/certipy-ad,Identify which Kali package repos matter as true VectorShell tool-ingestion candidates versus packaging noise.,"Packaging deltas, patches, wrappers, launch scripts, service glue, output normalization helpers.","Which Kali package repos point to valuable upstream integrations, and which package repos are operationally irrelevant?","Package-vs-upstream decision notes, wrapper extraction notes, promotion/demotion decisions.","Prefer repos that add meaningful wrappers, patches, or integration glue over plain distro metadata.","Audit the following v6 packet: VectorShell Kali Tooling Sweep. Inspect the listed repos in source and extract real capability, reusable subsystems, upgrade triggers, downgrade triggers, and exact integration paths.",family_packet,VectorShell agents in Kali Linux and subprocess/MCP tool access.,v6_unified_source_of_truth_pack,,,,P1,supplemental_v6_packet,"Use v6 as the source of truth. Identify which Kali package repos matter as true VectorShell tool-ingestion candidates versus packaging noise. Focus on: Packaging deltas, patches, wrappers, launch scripts, service glue, output normalization helpers.. Answer: Which Kali package repos point to valuable upstream integrations, and which package repos are operationally irrelevant?.","Packaging deltas, patches, wrappers, launch scripts, service glue, output normalization helpers.",VectorShell agents in Kali Linux and subprocess/MCP tool access.,Repurpose according to v6 project design language and family role.,,,,"Package-vs-upstream decision notes, wrapper extraction notes, promotion/demotion decisions.",,,,"Before recommending direct code use, inspect the target repo row in the v6.1 operational/phase/source-audit boards. Respect copyleft_strategy_v6_1, preferred_boundary_model_v6_1, and open_compliance_if_used_as_is_v6_1. Do not assume reverse engineering is mandatory or that as-is use is always sensible.","If the repo-level strategy says bounded_sidecar_preferred or boundary_first_then_decide_as_is_vs_reimplementation, audit clean interfaces, protocol seams, subprocess/container boundaries, and what would be required to reimplement only the strategically necessary portions.",v6.3_final_source_of_truth
V6-P1-SA-WORKSPACE,ScriptoriumAI Workspace Candidate Sweep,Consider II + workspace/editor comparisons,docmost/docmost ; papra-hq/papra ; badlogic/jot ; KurtGokhan/tegaki,Determine which ScriptoriumAI Consider II repos are meaningful donors for the realized workspace and media/document surfaces.,"Editor/document model, inline comment/threading, handwriting/animation, ingest/export, embed boundaries.",Which candidates add genuine workspace value and which duplicate the realized stack without enough upside?,"Donor/reject decision, exact integration or comparator note, source-audit rationale.",Prefer unique subsystem value over generic workspace similarity.,"Audit the following v6 packet: ScriptoriumAI Workspace Candidate Sweep. Inspect the listed repos in source and extract real capability, reusable subsystems, upgrade triggers, downgrade triggers, and exact integration paths.",family_packet,ScriptoriumAI Consider II intake.,v6_unified_source_of_truth_pack,,,,P1,supplemental_v6_packet,"Use v6 as the source of truth. Determine which ScriptoriumAI Consider II repos are meaningful donors for the realized workspace and media/document surfaces. Focus on: Editor/document model, inline comment/threading, handwriting/animation, ingest/export, embed boundaries.. Answer: Which candidates add genuine workspace value and which duplicate the realized stack without enough upside?.","Editor/document model, inline comment/threading, handwriting/animation, ingest/export, embed boundaries.",ScriptoriumAI Consider II intake.,Repurpose according to v6 project design language and family role.,,,,"Donor/reject decision, exact integration or comparator note, source-audit rationale.",,,,"Before recommending direct code use, inspect the target repo row in the v6.1 operational/phase/source-audit boards. Respect copyleft_strategy_v6_1, preferred_boundary_model_v6_1, and open_compliance_if_used_as_is_v6_1. Do not assume reverse engineering is mandatory or that as-is use is always sensible.","If the repo-level strategy says bounded_sidecar_preferred or boundary_first_then_decide_as_is_vs_reimplementation, audit clean interfaces, protocol seams, subprocess/container boundaries, and what would be required to reimplement only the strategically necessary portions.",v6.3_final_source_of_truth
V6-P1-AGENT-EXT,Agent Runtime Extension Sweep,Open WebUI / browser-use / ollama / skills,open-webui/open-webui ; browser-use/browser-use ; ollama/ollama,Assess which runtime and UI/control-plane extensions should be retained for multi-project agent layers.,"Browser control, local model runtime, UI/session ergonomics, tool execution loops, extension points.",What strengthens the control plane across projects and what stays peripheral?,"Runtime extension decision, cross-project transfer notes, source-audit outputs.",Prefer clear reusable control surfaces and execution loops.,"Audit the following v6 packet: Agent Runtime Extension Sweep. Inspect the listed repos in source and extract real capability, reusable subsystems, upgrade triggers, downgrade triggers, and exact integration paths.",family_packet,Multi-project agent runtime extensions.,v6_unified_source_of_truth_pack,,,,P1,supplemental_v6_packet,"Use v6 as the source of truth. Assess which runtime and UI/control-plane extensions should be retained for multi-project agent layers. Focus on: Browser control, local model runtime, UI/session ergonomics, tool execution loops, extension points.. Answer: What strengthens the control plane across projects and what stays peripheral?.","Browser control, local model runtime, UI/session ergonomics, tool execution loops, extension points.",Multi-project agent runtime extensions.,Repurpose according to v6 project design language and family role.,,,,"Runtime extension decision, cross-project transfer notes, source-audit outputs.",,,,"Before recommending direct code use, inspect the target repo row in the v6.1 operational/phase/source-audit boards. Respect copyleft_strategy_v6_1, preferred_boundary_model_v6_1, and open_compliance_if_used_as_is_v6_1. Do not assume reverse engineering is mandatory or that as-is use is always sensible.","If the repo-level strategy says bounded_sidecar_preferred or boundary_first_then_decide_as_is_vs_reimplementation, audit clean interfaces, protocol seams, subprocess/container boundaries, and what would be required to reimplement only the strategically necessary portions.",v6.3_final_source_of_truth
SRE-STRATUM1,Supplemental RE Layer — Stratum 1 Analyst Surfaces,VectorShell supplemental RE layer,NationalSecurityAgency/ghidra | WerWolv/ImHex | rizinorg/cutter | x64dbg/x64dbg | skylot/jadx | dnSpy/dnSpy | dnSpy/ILSpy,"Confirm sidecar viability, native-donor viability, exportability, plugin surface, and license for the packet repos.",Implemented capabilities; automation hooks; plugin/extensibility model; export/import; session files; license.,"Should these stay external, become donors for native panes, or be relegated to comparator status?","Per-repo audit notes with integration, repurpose, merger, and rank impacts.",Prefer source-backed findings over README claims.,Use v6.2 supplemental RE layer guidance. Distinguish Kali package availability from upstream architectural value.,supplemental_re_layer,VectorShell,v6.2 unified portfolio,NationalSecurityAgency/ghidra | WerWolv/ImHex | rizinorg/cutter | x64dbg/x64dbg | skylot/jadx | dnSpy/dnSpy | dnSpy/ILSpy,sre-stratum1,not_scriptorium_primary,P1/P2,"supplemental intake, not yet source-audited","Audit the packet repos as part of the VectorShell supplemental RE layer. Extract actual capabilities, plugin systems, outputs, sidecar viability, native donor viability, and concrete upgrade/downgrade triggers.",automation hooks | plugin model | export/import | session files | headless mode | license confirmation,bounded sidecar / CLI worker / launchable specialist surface / native donor,"sidecar first, native donor later if warranted",,,,"Clear decision on sidecar viability, donor viability, and whether the packet changes the RE layer ranking.",Do not merge advanced RE tools into the everyday navigator core without strong reason.,sre-stratum1,v6.2 unified portfolio,use v6.1 strategy as starting hypothesis,Prefer bounded sidecar or native-donor classification over premature deep embedding.,v6.3_final_source_of_truth
SRE-STRATUM2,Supplemental RE Layer — Stratum 2 Automation Engines,VectorShell supplemental RE layer,rizinorg/rizin | radareorg/radare2 | ReFirmLabs/binwalk | angr/angr | avast/retdec | frida/frida,"Confirm sidecar viability, native-donor viability, exportability, plugin surface, and license for the packet repos.",Implemented capabilities; automation hooks; plugin/extensibility model; export/import; session files; license.,"Should these stay external, become donors for native panes, or be relegated to comparator status?","Per-repo audit notes with integration, repurpose, merger, and rank impacts.",Prefer source-backed findings over README claims.,Use v6.2 supplemental RE layer guidance. Distinguish Kali package availability from upstream architectural value.,supplemental_re_layer,VectorShell,v6.2 unified portfolio,rizinorg/rizin | radareorg/radare2 | ReFirmLabs/binwalk | angr/angr | avast/retdec | frida/frida,sre-stratum2,not_scriptorium_primary,P1/P2,"supplemental intake, not yet source-audited","Audit the packet repos as part of the VectorShell supplemental RE layer. Extract actual capabilities, plugin systems, outputs, sidecar viability, native donor viability, and concrete upgrade/downgrade triggers.",automation hooks | plugin model | export/import | session files | headless mode | license confirmation,bounded sidecar / CLI worker / launchable specialist surface / native donor,"sidecar first, native donor later if warranted",,,,"Clear decision on sidecar viability, donor viability, and whether the packet changes the RE layer ranking.",Do not merge advanced RE tools into the everyday navigator core without strong reason.,sre-stratum2,v6.2 unified portfolio,use v6.1 strategy as starting hypothesis,Prefer bounded sidecar or native-donor classification over premature deep embedding.,v6.3_final_source_of_truth
SRE-STRATUM3,Supplemental RE Layer — Stratum 3 Primitive Libraries,VectorShell supplemental RE layer,capstone-engine/capstone | keystone-engine/keystone | unicorn-engine/unicorn | lief-project/LIEF,"Confirm sidecar viability, native-donor viability, exportability, plugin surface, and license for the packet repos.",Implemented capabilities; automation hooks; plugin/extensibility model; export/import; session files; license.,"Should these stay external, become donors for native panes, or be relegated to comparator status?","Per-repo audit notes with integration, repurpose, merger, and rank impacts.",Prefer source-backed findings over README claims.,Use v6.2 supplemental RE layer guidance. Distinguish Kali package availability from upstream architectural value.,supplemental_re_layer,VectorShell,v6.2 unified portfolio,capstone-engine/capstone | keystone-engine/keystone | unicorn-engine/unicorn | lief-project/LIEF,sre-stratum3,not_scriptorium_primary,P1/P2,"supplemental intake, not yet source-audited","Audit the packet repos as part of the VectorShell supplemental RE layer. Extract actual capabilities, plugin systems, outputs, sidecar viability, native donor viability, and concrete upgrade/downgrade triggers.",automation hooks | plugin model | export/import | session files | headless mode | license confirmation,bounded sidecar / CLI worker / launchable specialist surface / native donor,"sidecar first, native donor later if warranted",,,,"Clear decision on sidecar viability, donor viability, and whether the packet changes the RE layer ranking.",Do not merge advanced RE tools into the everyday navigator core without strong reason.,sre-stratum3,v6.2 unified portfolio,use v6.1 strategy as starting hypothesis,Prefer bounded sidecar or native-donor classification over premature deep embedding.,v6.3_final_source_of_truth
SRE-DOTNET,Supplemental RE Layer — Managed Code / .NET Family,VectorShell supplemental RE layer,dnSpy/dnSpy | dnSpy/ILSpy | dnSpy/Mono.Debugger.Soft | dnSpy/NRefactory | dnSpy/ICSharpCode.TreeView,"Confirm sidecar viability, native-donor viability, exportability, plugin surface, and license for the packet repos.",Implemented capabilities; automation hooks; plugin/extensibility model; export/import; session files; license.,"Should these stay external, become donors for native panes, or be relegated to comparator status?","Per-repo audit notes with integration, repurpose, merger, and rank impacts.",Prefer source-backed findings over README claims.,Use v6.2 supplemental RE layer guidance. Distinguish Kali package availability from upstream architectural value.,supplemental_re_layer,VectorShell,v6.2 unified portfolio,dnSpy/dnSpy | dnSpy/ILSpy | dnSpy/Mono.Debugger.Soft | dnSpy/NRefactory | dnSpy/ICSharpCode.TreeView,sre-dotnet,not_scriptorium_primary,P1/P2,"supplemental intake, not yet source-audited","Audit the packet repos as part of the VectorShell supplemental RE layer. Extract actual capabilities, plugin systems, outputs, sidecar viability, native donor viability, and concrete upgrade/downgrade triggers.",automation hooks | plugin model | export/import | session files | headless mode | license confirmation,bounded sidecar / CLI worker / launchable specialist surface / native donor,"sidecar first, native donor later if warranted",,,,"Clear decision on sidecar viability, donor viability, and whether the packet changes the RE layer ranking.",Do not merge advanced RE tools into the everyday navigator core without strong reason.,sre-dotnet,v6.2 unified portfolio,use v6.1 strategy as starting hypothesis,Prefer bounded sidecar or native-donor classification over premature deep embedding.,v6.3_final_source_of_truth
SRE-KALI-BRIDGE,Supplemental RE Layer — Kali Packaging Bridge,VectorShell supplemental RE layer,kalilinux/packages/ghidra | kalilinux/packages/imhex | kalilinux/packages/rizin | kalilinux/packages/binwalk3 | kalilinux/packages/gef,"Confirm sidecar viability, native-donor viability, exportability, plugin surface, and license for the packet repos.",Implemented capabilities; automation hooks; plugin/extensibility model; export/import; session files; license.,"Should these stay external, become donors for native panes, or be relegated to comparator status?","Per-repo audit notes with integration, repurpose, merger, and rank impacts.",Prefer source-backed findings over README claims.,Use v6.2 supplemental RE layer guidance. Distinguish Kali package availability from upstream architectural value.,supplemental_re_layer,VectorShell,v6.2 unified portfolio,kalilinux/packages/ghidra | kalilinux/packages/imhex | kalilinux/packages/rizin | kalilinux/packages/binwalk3 | kalilinux/packages/gef,sre-kali-bridge,not_scriptorium_primary,P1/P2,"supplemental intake, not yet source-audited","Audit the packet repos as part of the VectorShell supplemental RE layer. Extract actual capabilities, plugin systems, outputs, sidecar viability, native donor viability, and concrete upgrade/downgrade triggers.",automation hooks | plugin model | export/import | session files | headless mode | license confirmation,bounded sidecar / CLI worker / launchable specialist surface / native donor,"sidecar first, native donor later if warranted",,,,"Clear decision on sidecar viability, donor viability, and whether the packet changes the RE layer ranking.",Do not merge advanced RE tools into the everyday navigator core without strong reason.,sre-kali-bridge,v6.2 unified portfolio,use v6.1 strategy as starting hypothesis,Prefer bounded sidecar or native-donor classification over premature deep embedding.,v6.3_final_source_of_truth
