Since v3 is implicitly 32-bits how say we - lose the .32bit & .64bit and just have spur32 & spur64? - lose vm; it's also implicit given the plugins directory So then we'd have src/ ckformat.c examplePlugins.ext examplePlugins.int lowcode.cog.spur32 lowcode.stack.spur32 lowcode.cog.spur64 lowcode.stack.spur64 newspeak.cog.spur32 newspeak.stack.spur32 newspeak.cog.spur64 newspeak.stack.spur64 plugins cog.spur32 cog.v3 sista.spur32 stack.spur32 stack.v3 cog.spur64 sista.spur64 stack.spur64
And to my mind the object memory architecture is primary (since it determines image compatibility), so I would go for ckformat.c examplePlugins.ext examplePlugins.int plugins spur32.cog spur32.cog.lowcode spur32.cog.newspeak spur32.sista spur32.stack spur32.stack.lowcode spur32.stack.newspeak spur64.cog spur64.cog.lowcode spur64.cog.newspeak spur64.sista spur64.stack spur64.stack.lowcode spur64.stack.newspeak v3.cog v3.stack
That makes *much* more sense to me.