Thank you Rod. I'll take your suggestion. I get what you're saying about coming back together and will consider that, but honestly there are degrees of "rightness" with this topic, so will try to keep it intuitive while allowing for multiple paths to a successful "session"--some being more ideal than others. Though I do confess my analyst brain is probably trumping my design brain on this one.
I've designed quite a few branching scenario courses over the years. Some of them were very complex and involved hundreds of custom user variables to track the data. But only rarely did I need to go outside Captivate's default interactivity tools and use JavaScript to pull off the project. Mostly those were courses that were somewhat more like games.
The important thing is to not jump too quickly to the technical side of the solution. Get the instructional design worked out first, then worry about what level of technological complexity you really need to achieve it.