We look to restrict ourselves to simple flat name spaces. This is in part because Livecode (and wiki) force us to do that, and in part becaue the mental model is rich enough and simple enough for most humans to grok. We are looking after all to democratise the process (and power) of software development.
As a result across all projects in the environment: 1. All stacks must have unique names. 1. Handlers in libraries have unique names 1. Projects and Modules must have unique names
This makes creating new elements tricky as we must check against potnetially thousands of files that we are using a unique name. We use a naming convention and tooling to help us with this. So public handlers are prefixed with the root of the library, and projects are organised within a single global project on github (or your desktop).
# Short Names Rule
When we combine this flat name space with each Home Stack having a local stackfiles property, we are able to find associated tool and libnrary filenames for almost any stack - by simply refering to it by name and using standardised functions that rely of the naming conventions.
For instance we can list all behaviors used by a module, or all libraries used by a project.