Public form-filling: This use case is the casting questionnaire for the LARP; or, only slightly different, the Rolls Ethereal. Allow members of the public to fill in a predefined form of a specific type, which then becomes queryable in the LARP. For the casting questionnaire case, I want to be able to predefine the expected entries with their email addresses, and automatically send email to everyone in that list with passwords (maybe embedded in the one-shot URLs) taking them to their own entries. For the Rolls, I want anyone to be able to create password-protected entries, but require some sort of admin approval before making those pages available to public queries (so that wikispam is useless for this case).
Story Management System: As soon as possible, the system should be used to develop and manage itself.
Bug Tracking System: Same as the above -- this is a system where eating its own dogfood makes lots of sense.
Cookbook: An example that's a great fit, and less meta. A cookbook is just right: a collection of pages that are partly data fields, and partly open text. Note that this introduces an interesting new requirement: for each ingredient, we really want the "ingredient" and "quantity" to be separate conceptually, so that we can query on ingredients. That implies that a property potentially needs to be a parameterizable data structure unto itself, not just a string or link. Fun!
Back to Querki Design Notes.