Update 'One Pager: Managed Groups ( A Roadmap towards Hybrid Groups)'

One-Pager%3A-Managed-Groups-%28-A-Roadmap-towards-Hybrid-Groups%29.md

@@ -21,6 +21,13 @@ In its most basic form this could just be a bot that sent a new group invite to
 * additional data recorded in the group invite and in the group database entry that associates a bot with the permissions to update certain attributes (like the key)
 
 
+### Questions intended to be answered by this phase:
+
+* What strategies should we preset to group managers for maintaining group security (e.g. reset period limits)
+* How should we deal with members that are mostly offline and who may not have received the most recent keys (e.g. allow them to fetch past keys from the bot? Only allow them to fetch the most recent key?)
+* How can we best integrate the flow between key management and offline storage (e.g. if a key rotation happens prior to a profile fetching the most recent messages from a server how can we structure the flow in cwtch to ensure they don't have to refetch every message again once they learn of a new key).
+
+
 ## Goal 2: Integrated Group Management
 
 Once Goal 1 has been tested we should have a fairly good idea of the UX necessary to bring an integrated experience to group management. This would involve bringing the bot inside of Cwtch and allowing access to its management functions from within the UI. This UI likely needs: