@SAXEMBERG Thanks for raising these points, let’s address each one clearly:

• Fellowship overlap with Ref. 373

Ref. 373 (Dec 2023) funded the Fellowship MVP: activity feed, listing views, induction and referendum pages, member profiles, and core infra like pallet indexing, search, and hosting.
This proposal does not re-bill those. The scope here is the next layer: task & salary management workflows, collective analytics dashboards, BI alerts (deadlines, promotions/demotions), enhanced member profiles with salary/vote history, and IPFS documentation with Apillon. In short, 373 delivered the base product; this funds integration and transparency extensions.

• Overlap with Ref. 1463 (“Social Contract”)

Fair point on the title. We kept “Social Contract” for continuity, since the original annual scope was split into two milestones after community feedback. To avoid confusion, we’ll rename this proposal more explicitly around “Fellowship & Transparency.” None of the maintenance costs or subscriptions covered under 1463 are being re-billed here.

• Global Analytics Page

We’ve logged caching improvements and responsiveness fixes (overflow, minimised screen issues) as part of the ongoing revamp. These are tracked separately and will be improved in the next rollout by  11 September 2025. Thanks for pointing out the UX details.

• Bounties Page (child bounties showing 0)

The bounty revamp is mid-migration, and several planned features, including the curator view haven’t gone live yet. That’s why some fields like child bounties look erroneous today. These fixes are already in progress and were billed under previous scope, not here. You’ll see the completed bounty dashboards shipped as part of the revamp release this month, not from this proposal’s budget.

Please let us know if you have any other concerns. We will keep you and the community posted on all product updates including those here, as they go live in the coming few days.

Looking forward to your support!

@bkchr We fully recognise the great work Subsquare has done for Fellowship. Our goal isn’t to duplicate but to extend, giving Polkassembly’s existing users a seamless way to access Fellowship flows without switching platforms. In the first phase we prioritised core stability, wallets, and UX, which meant Fellowship wasn’t included then. Now, with that foundation in place, our users are asking for integrated Fellowship features. What we’re building is a different UI on top of the same underlying calls, designed as a continuation of governance workflows already happening on Polkassembly. We see this as complementary rather than competitive, and an important step to ensure ecosystem choice.