builder-research/Week-4/Task-3.md

Proposal Name

Guided Flow Step Block (Atomic Scene Orchestrator)

Problem

Weeks 2 and 3 repeatedly showed that users can build scene states, but struggle to reliably wire one trigger to update camera, visibility, and transforms together. The workaround (prebuilt states + visibility toggles) is reliable, but it does not scale cleanly and lacks smooth transitions.

User Story

A product marketer or solution engineer wants to build a 3-step 3D walkthrough where each step updates framing and object emphasis in one click. They need predictable sequencing, reset, and polished transitions without custom code.

Proposed Builder Experience

• Author creates Step 1, Step 2, Step 3 in a single Guided Flow panel.
• Each step has bundled targets:
  • Camera state
  • Object visibility state
  • Object transform targets
  • Optional transition duration and easing
• User binds one button (or radio option) to Go To Step N.
• Runtime applies all updates atomically and shows success/failure feedback per target.
• User can preview forward, backward, jump, and reset behavior before publishing.

Proposed Primitive / Block / Pattern

Introduce a reusable Guided Flow Step Block with:

• Data model
  • Steps array where each step includes camera, visibility, transforms, and transition metadata.
• Execution model
  • Single transactional apply for all targets in a step.
  • Deterministic last-write-wins behavior for rapid repeated interactions.
• Authoring model
  • Timeline-like step list with reorder and duplicate.
  • Built-in reset/default step.
  • Optional guardrails for invalid target bindings.
• Debug model
  • Per-step execution log showing applied targets and any failures.

Why This Matters

• It directly solves the most repeated pain in Task 2 and Task 3 from Weeks 2 and 3.
• It upgrades Thob from workaround-based storytelling to first-class guided scene orchestration.
• It leverages current strengths already proven in Week 3: deterministic discrete state switching and strong hierarchy behavior.

Complexity Guess

• Quick Win
  • Step schema MVP with visibility-only bundles and reset support.
• Medium
  • Full bundle support for camera + visibility + transforms with transition controls and validation.
• Deep
  • Robust orchestration runtime with rollback strategy, conflict resolution, and advanced sequencing constraints.

Optional Tiny Demo

A tiny proof-of-concept can reuse the Week 3 reliable pattern:

• Build three authored states in one scene.
• Bind Step 1/2/3 controls through one Guided Flow block instead of manual multi-target bindings.
• Add transition duration to camera and transform updates.

What this would show:

• Same reliability as the Week 3 workaround for step order (1 to 2 to 3, 3 to 2 to 1, 1 to 3, repeated toggles).
• Better authoring clarity and lower setup friction.
• Immediate storytelling quality improvement with smooth transitions.