Discuss adding another layer called app to the ops repo

Right now the ops repo is geared towards a single application. By adding a new optional layer (application) and passing in the application and environment we can have multiple applications in a single Ops repo

An application is made of infrastructure and code to be deployed to that infrastructure.

Instead of `ENV/TOOL` use `APP/ENV/TOOL`
- This lets each app have its own configurations.
- Even with a repository for each application, this may still be beneficial. There may be a reason to split the front end and back end into a separate grouping.

This could be accomplished by using multiple repositories

No files, tests, or entry points are named. Start by reviewing the existing ENV/TOOL layout and how application and environment values are passed through the ops repository. The issue proposes an optional APP layer but does not define an agreed implementation or completion condition.

Written by the indexing model from the issue text.