May be we need to have a folder or thread structure (i.e. basically a survo tree) to keep Survo's organized like how web pages are organized on web server.

We should also be able to make copies and rename them across different folders to avoid re-writing or to make slight modification to existing survo without breaking dependent functionality. At times we don't need to rename a Survo instead we need to reference another Survo from a common folder like calling a common survo from a specific survo.

You concept about these survo forms is great but when people want to express complex cases, it will become wieldy and too hard to maintin like how writing a c++ project old style was improved in visual studio to have project workspace and later on they added project group to keep all related dependent files together. I believe we should have atleast 2 levels like this and an ability to refer to common folders in level 1.

May be you need to raise this concern immediately to your architect or Irv, as I foresee it as an big issue in near future.