Write some algorithm/structural level documentation on how Prism works. That is, at a low enough level to understand how it works, but at a high enough level that not every change requires updating the documentation. Not intended for End users, but Beam contributors who want to learn more about Beam, and runners specifically.
Should cover
- Code Organization
- Threading Model
- How bundles are generated and split
- How watermarks are evaluated and updated
- And similar