This issue is for follow-on discussion of the CG-04-27 presentation which was itself a follow-up proposal based on discussion in the duplicate import issue (#1402).

A high-level summary of the presentation is:

• Discussion in Disallow duplicate imports? #1402 suggests that module linking be factored out into a layer above core wasm (resolving Disallow duplicate imports? #1402 with "no").
• Interface types would be much simpler as an (optional, if desired) feature proposal extending this new layered spec
• Considering future evolution and the wide variety of possible linking features and host implications, we must carefully consider the scope of this new layered spec.
• A set of relevant use cases and requirements were presented, proposing that the scope we want is a lightweight component model, with implications for what kinds of linking would be supported.

Separately, the presentation suggests next steps, but I think perhaps first we should discuss the general question of "is this the right general direction"? Of course, even if the CG thinks "yes" to the general direction, the precise list of use cases and requirements is open for further iteration (ideally in a new repo, so we can open a bunch of independent issues).