I / we still haven't resolved how to do this long term but we do know there is a piece of logic missing. And we intuit where it should live in the system. I've modeled this (from our whiteboard) on our architecture board. I didn't repeat the work done on logging (which is part of this.) In my mind, the next step is to figure out as a team how the Customer Service service might work (eventually) and how to iterate towards it. The logging work gets us close to egress-ish. So is probably sufficient for awhile. Just don't want to hardcode logic in the wrong place ;)

Has been shared for review with Stephan, Stephanie, Ryan and Haroon. This is likely "done" once they've added / noted. And another story "publish for X audience" is needed.

@Protsack.stephan Ready for review - in the Three Einstein Problem frame.

Two additions to the board
Easy (MVP) option
Harder - to discuss - option

Trying to convey sufficient context without discussing Everything was super tricky. Thank you, truly, @Pchelolo for helping to bring context into view.

Do we put them into one or different containers?

• Decided to put them in multiple containers. Please, future devs, don't hate us. There are reasons :)

Thank you for this feedback. Some of it mirrors feedback from the initial review, so will show up in Revision 1 (after the holiday). I will ping when that's ready.
Some notes:

Fairly sure you're a professor already :)