Colony frames itself as infrastructure for organizations that operate in software rather than through paperwork and management hierarchy. The docs still present the protocol as a full organizational operating system, even though the current homepage emphasizes payments and treasury workflows.
The protocol surface is broader than DAO payroll. Colony’s own docs describe ownership and permissions, reputation, dispute resolution, work management, delegation, financial management, rewards, and payments as part of one design.
Tasks are first-class objects with structured roles. A task has a brief, deliverable, payouts, due date, domain, and optional skill tags, and its lifecycle includes creation, modification, rating, and finalization.
The role split matters: Manager, Evaluator, and Worker are distinct protocol roles, and many task modifications require multiple signatures. That makes labor coordination and work acceptance part of the governance design rather than simple messaging metadata.
Domains and skills are separate abstractions. Domains organize work and pots inside a colony; skills are global across the network. Reputation from completed work flows upward through parent domains and parent skills.
Reputation is non-transferable and computed from onchain events, but Colony intentionally keeps the heavy computation offchain. Miners stake CLNY, compute global reputation state offchain, and submit a reputationRootHash onchain, where conflicting submissions can be challenged.
The docs describe reputation mining as closer to a proof-of-stake consensus process than to a simple dashboard calculation. The key object is the root hash of a Patricia-tree-structured reputation state derived from logged reputation events.
The Meta Colony is an important retained control surface. It maintains the shared skill hierarchy and has special powers over network improvement and upgrades, while access to some upgrade paths depends on Meta Colony reputation.
Specific source signals worth retaining
The Colony Network overview page is the best concise source for the protocol’s intended scope and for the special role of the Meta Colony.
Tasks and Payments is the best source for role structure, task lifecycle, commit-reveal ratings, and the reputation consequences of satisfactory versus unsatisfactory work.
Reputation Mining is the best source for why reputation is offchain, how CLNY stake and root-hash submissions work, and why the system resembles a consensus protocol.
Domains and Skills is the best source for Colony’s organizational decomposition: local domains and funding pots versus global skills and peer-group-based dispute scope.
The repo is mainly useful for confirming that the smart-contract implementation remains a substantial maintained surface and for exposing implementation choices like EtherRouter-based upgradability.
Why this entry belongs in the corpus
It gives the corpus a strong historical and mechanism-rich baseline for reputation-mediated work coordination.
It helps compare later labor and governance tools by keeping separate layers visible: task workflow, budget containers, reputation, dispute scope, and network governance.
The durable insight is that Colony makes the organization itself programmable. Influence comes from tracked work history and organizational placement, not just token balances or chat-platform admin roles.