Dework primary sources — 2026-05-10

Classification takeaway

Dework is most usefully classified as hosted work-admission and contributor-routing infrastructure for crypto organizations. Its main mechanism is not just project tracking; it is the combination of task-permission modes, role gating, global discovery, application routing, milestone/grants workflows, and a beta reputation-staking market tied to contributor revenue share.

Primary sources reviewed

1. Official site — https://dework.xyz/

   • Used to confirm the official product framing around web3-native project management, token payments, credentialing, and bounties.
   • Helpful as a concise statement that Dework wants to be more than a private kanban board.

2. Docs home / “What is Dework?” — https://dework.gitbook.io/

   • Used to confirm the platform’s broader positioning around engaging internal and external contributors, paying for work, and boosting reputation.
   • Also useful for seeing the breadth of documented surfaces: roles, payments, task templates, grants workflows, and integrations.

3. Task Types & Assignee Gating — https://dework.gitbook.io/product-docs/fundamentals/task-types-and-assignee-gating

   • Used to verify the main task-admission modes: assign someone, open to application, multiple submissions, and direct claiming.
   • Important because these permission choices are the clearest practical control surface for who can access work and how work gets evaluated.

4. Roles Center — https://dework.gitbook.io/product-docs/fundamentals/roles-center

   • Used to confirm how organizations feature roles, attach descriptions and compensation, sync/fetch Discord-linked roles, and surface roles on a global board.
   • Helpful for understanding Dework as contributor-discovery and admission infrastructure rather than only internal project management.

5. Managing Grants — https://dework.gitbook.io/product-docs/workflows/operations/managing-grants

   • Used to verify that Dework positions itself as grants-operations infrastructure: sourcing applicants, routing to external forms, collecting RFP ideas, tracking milestones, and exposing community transparency.
   • Important for comparison against grant operating systems and bounty boards.

6. Reputation Staking — https://dework.gitbook.io/product-docs/guides-for-contributors/reputation-staking

   • Used to verify the beta revenue-sharing reputation market: stakers back a contributor with Reputation Credits and receive a share of that contributor’s Dework earnings based on a configurable split.
   • This was the key source for treating Dework as more than workflow software.

Why it stays in the active corpus

• It adds a distinct control-plane layer for crypto work: contributor admission, role-gated discovery, external-application routing, and milestone-based grants operations.
• It creates a useful comparison point for TalentLayer, Talent Protocol, Coordinape, and grants operating systems because it sits between contributor discovery and final payout.
• The durable insight is that practical labor-market power often sits upstream of settlement: in permissions, role sync, external-form routing, global board placement, review workflows, and reputation-financialization design.