Conduit is organized around two clear modes: Core for the dependable script-to-production workflow, and Labs for advanced tools that can evolve without disrupting daily work.
Core is the everyday Conduit surface. It is where the writing, scene planning, production context, and local project workflow stay stable enough to use on an actual production.
Labs is where Conduit can test advanced planning, inspection, technical handoff, and automation ideas without making the core workflow feel unstable or overbuilt.
Core is the everyday Conduit surface. It is where the writing, scene planning, production context, and local project workflow stay stable enough to use on an actual production.
Core keeps the draft, scenes, summaries, tags, and revision context close together so the script does not become detached from the rest of the project.
Scene-level planning gives the production a practical place to track readiness, intent, notes, and what needs attention next.
The goal is a calm operating surface for breakdowns, deliverables, reminders, exports, and production state without forcing users into scattered tools.
Core is designed around local project ownership, desktop reliability, and account-based permissions that keep installer access separate from paid app permissions.
Labs is where Conduit can test advanced planning, inspection, technical handoff, and automation ideas without making the core workflow feel unstable or overbuilt.
Labs gives advanced surfaces a place to live while Core remains focused on the dependable writing and production spine.
Labs can support inspection, validation, and technical follow-through when a production needs them, without becoming required for basic project planning.
Labs is the right place for higher-depth analysis, generated assistance, scene diagnostics, and planning experiments that should prove themselves before becoming core behavior.
Separating Labs from Core makes it easier to expand Conduit ambitiously while keeping the main product understandable, reliable, and production-safe.
Conduit is strongest when one filmmaker or a small team needs the writing surface, the scene board, and the production plan to stay aligned instead of being passed across disconnected tools.
Conduit starts with screenplay structure, scene intent, revisions, and planning context instead of splitting writing away from the rest of the job.
Keep summaries, tags, shot readiness, and linked work visible at the scene level so the next decision is obvious instead of hidden in notes.
Breakdown, revisions, deliverables, and production status live in the same system so the screenplay remains the source of truth.
Bridge workflows are there for inspection, validation, and technical follow-through, not as a requirement for basic writing or planning.