Cycle Five Reflection 

• We’ve added comment threads to collective applications to Fiscal Hosts. Collective admins and Fiscal Host admins can now communicate directly via these comment threads (instead of having to do so through email, support or Slack channels) and the conversation and any agreements reached is clearly documented and archived. Fiscal Hosts will see this in their “Application” Dashboard tool. Collective admins will find this in their Fiscal Host settings.
  

  

• We’ve also upgraded the comment threads behavior within dashboard (this applies to both expenses and now applications). We’ve made it easier to engage with the comment thread by showing newest comments first and collapsing longer comments so that the thread requires less scrolling. This has helped to mature comment threads themselves so that we can see them being used more broadly across the platform.

• We’ve enhanced the “freeze” (and “unfreeze”) collectives feature by providing an ability to also pause (and then resume) recurring contributions.

•  It is now possible to “edit added funds.” We needed to achieve this without compromising ledger immutability (in order for the ledger to be a trusted source-of-record transactions cannot be changed or deleted). We opted to rely on a “soft-delete” feature in the ledger which allows for transactions to be marked as deleted. They continue to be stored in the ledger but do not effect balances. Editing funds therefore causes the existing transactions to be marked as deleted and creates new ones to replace them. We have flagged follow work needed to make this more visible when working directly with the ledger.

• In our continuing effort to enhance and improve legibility and reliability of the ledger we now accurately represent in it rare cases in which partial payment processor fees are refunded. 

• Improving the goals infrastructure. 
• Enhancing the new designs for collective profiles in order to better tell the story of collectives that have multiple projects and events through which they are either raising funds or earmarking them for spending. 
• Establishing the overall URL structure for public pages. There are numerous needs and constraints for this to work well. This has arisen from the MVP profiles we built during Cycle 4. We are now looking at formulating a clear strategy we can implement while maintaining backwards compatibility with the existing URL structures.