There is a broad category of tools which could benefit from having some
definition of a "project", a list of all UI stacks, libraries, externals, etc.
that comprise a given product or system.

The types of tools that could use this information include installer makers,
version control systems, code analyzers, and even marketing support. If there
were a common definition of a "project", such tools could be used
interchangeably.

This raises a variety of questions:

1. Should a "project" be defined as a property of the mainstack for an app, or
should it be a separate file?

2. What info should be included in the definition for a "project"?

3. Is this actually useful, or could there be some other way of dealing with
multi-file deployments that may be quite different?

I'm very interested in your feedback.