Export synthesized top-module and import in another project

Thank you again @sstrell. I am not sure which project I would designate as the developer project. At first glance, it seems like I would want the final project (defining the final top-module, peripherals, etc) to be the developer project with the root_partition. But then the fact that the 'consumer' project takes the root_partition and fills in 1 or more holes does not fit my model. Maybe you could help me determine what project(s) should be the developer and consumer?

I have projects A, B, and C. I want to export the entire B and C designs (their top-modules) as netlists. Again, B and C will never have any knowledge of A. A will instantiate the B and C modules and import their netlists. As I mentioned in a previous post, project A might ultimately be a submodule of another larger design.

In Quartus Standard, the process is essentially: Compile projects B and C to netlists and create stubs. Instantiate B and C in project A and import the netlists and stubs. Compile project A.

This process can repeat recursively if A is a submodule of a larger design or if B and C have submodules.

Should the 'developer' project be the final project that results in a bitstream, or is that a 'consumer' project?