I need to stress that this was only a list of perceived needs for the system. Anything can go in there at any level and may well be rejected or postponed as a requirement for any particulal version of the "product". It's just to help think about that it should do.
I'll write some more about how this should be turned into a proper list of features and possibly use cases - and why it 's a good idea to do so later on.
Ugh, I'm turning this into a clone of my day job except on a more interesting product
But I think some planning of what the requirements actually are is probably even more important in a project likt this that a commercial project as it's considerably more easy to lose sight of your goals in a project like this and get sidetracked on something that seems interesting while fogretting the things that are needed to make a sucessfull "product"