UTC :: --:--:-- RUST :: stable :: 1.96.0 CLIENT :: browser :: detecting PYPI :: status :: operational CLIENT :: AWS/REGION :: us-east-2 LINUX :: stable_kernel :: 7.0.10 CLOUDFLARE :: pages :: degraded_performance NODE :: lts :: 24.16.0 CLIENT :: os :: detecting CRATES.IO :: crates :: 275k+ GITHUB :: actions :: operational CLIENT :: ip :: masked PYTHON :: stable :: 3.14.x UTC :: --:--:-- RUST :: stable :: 1.96.0 CLIENT :: browser :: detecting PYPI :: status :: operational CLIENT :: AWS/REGION :: us-east-2 LINUX :: stable_kernel :: 7.0.10 CLOUDFLARE :: pages :: degraded_performance NODE :: lts :: 24.16.0 CLIENT :: os :: detecting CRATES.IO :: crates :: 275k+ GITHUB :: actions :: operational CLIENT :: ip :: masked PYTHON :: stable :: 3.14.x

docs::rolethread :: For Developers

~/docs/rolethread/docs/help/28_rolethread_studio_vision.md

RoleThread Studio Vision

RoleThread Lite Docs

./view_on_github

repo: Lattice-Foundry/RoleThread-Lite
path: docs/help/28_rolethread_studio_vision.md
ver: 1.4.45
commit: 3fbdfa7320
synced: May 29, 2026, 03:35 AM UTC

RoleThread Lite and RoleThread Studio are separate product surfaces for related engineering problems.

Lite is the focused dataset tool. Studio is reserved for orchestration-heavy workflows that should not expand Lite's runtime or UI scope.

What Lite Is

RoleThread Lite should stay:

lightweight
deterministic
privacy-focused
creator-oriented
maintainable
stable

Lite owns the practical dataset engineering surface:

creating and editing entries
validating structure
repairing safe format issues
organizing tags, characters, and system prompts
reviewing dataset quality
merging, splitting, joining, and exporting datasets
protecting work with backups and portable metadata

Lite should remain complete without becoming an orchestration platform.

What Studio Is Intended To Become

RoleThread Studio is the planned surface for larger RoleThread workflows.

Studio is where more ambitious systems may belong, including:

large-scale orchestration
advanced roleplay/runtime workflows
multi-agent systems
advanced automation
inference management
power-user tooling
experimental AI-assisted workflows
native desktop workflows later, if they make sense

This is an architectural boundary, not a public roadmap.

The Product Split

The split is operational:

Lite owns deterministic dataset creation, inspection, mutation, validation, backup, and export workflows.
Studio can own orchestration, automation, runtime, and inference-management workflows that require more state or heavier process control.

Why The Separation Exists

The separation prevents broad runtime experiments from weakening Lite's simpler mutation, validation, and recovery model.

Current Status

RoleThread Studio is conceptual. This page documents product boundaries, not committed features, dates, or packaging decisions.

For V1, RoleThread Lite remains the active product surface for dataset crafting, validation, repair, organization, and export.

Lite vs Studio Boundaries
V1 Scope and Intentional Boundaries
What RoleThread Lite Does