Specification: Organization for work that uses building-motif but is not part of the core functionality

[TShapinsky]

Proposed Ideas:

• put in extensions
• make external repos
• put in apps

I think the unifying concerns are:

1. If the buildingMOTIF api changes we want to make sure we keep our ancillary projects up to date.
2. Putting things in different repos can lead to things falling through the cracks.
3. Don't want to unnecessary clutter.
4. Don't want testing in main repo to get any more complicated
5. Adding additional dependencies could lead to issues resolving in the future.

Some Ideas:

• It might be possible to set up actions which trigger testing on other repos when a merge is made to main. This could just help alert us when things do break without needing to clutter our main repo.
• Everything from additional work which would make core buildingmotif api better should be integrated into the main repo.