build out readme

[chukinas]

include goals

• experiment with Event Sourcing
• experiment with machine learning - teach it to play a game against me
• refresh my LiveView skills
• Integrate the Tantor library i wrote for my volleyball app (right now and for the immediate future I'm doing strictly in-memory messaging)

overview of app's event sourcing

• currently, no view model state is stored at all. ALL of a game's "state" is stored in game.events. The commands that produced those events are stored in game.commands.
• For each command, pass it into each handler (e.g. Auction). At least one handler will respond back with one or more events. (before even doing that, each handler needs to build its internal state back up from scratch using all the current events).
• These events are then stored in a list. That's the current state.
• There's one more step though before handling or listening for the next command. We pass all the events so far to each handler. They have the opportunity to respond back with "reaction" events. You might think that

[chukinas]

It's a passion project. It's been a while since I built something for fun and "exercise". I love board games and I love thinking about how they would would be implemented. I don't know mobile development, so I'm choosing to do this in the browser.

I'll be using GitHub copilot to help me. I'm already impressed

State charts, event sourcing, live view, elixir, UI DESIGN. There is no specific timeline, but generally I place to do the data model and game loop first (all in-memory with a possible future of persisting using MessageDB.

Then I think I'll build a rather dumb AI. That'll involve