Product workflow 2026.09.27
How to Group Issues in a DramaFork Playable Preview: Which Step Should Story, Interaction, and Assets Each Go Back To for Fixes? When issues appear in a playable preview, don't rush to change nodes. Use a one-sentence symptom record to clearly write down "who saw what at what moment," then determine whether it belongs to story, interaction, or assets. Story issues go back to planning or script, interaction issues go back to interaction nodes, and asset issues go back to storyboard, style, character assets, or video; after changes, only recheck the affected downstream steps, and do not treat a preview that runs successfully as passing release testing.