Acknowledge terms of service or similar legal disclaimer for a task?

I preface this suggestion/idea with the disclaimer that I am not a lawyer.

Having said that, the idea is to (optionally) enable a feature that functions as some type of legal disclaimer or terms of service that the worker/evaluator/manager would agree to when signing on for a given task. After all, we may be talking about money transmission (even if through a decentralized medium) as well as a decision making process as to whether the work meet the assigned criteria with their task deliverable. There seems like a lot of shades of grey here, and it might be good to bake in some legal protections that people could tailor relative to their given environment. After all, there is only a limited amount of legal precedent in this domain. I can think of a few ways to implement something like this in Colony, but would like to hear any initial reaction/concerns before delving deeper. Cheers!

I think this is sort of thing is particularly important in systems that are more open, but still useful even in relatively closed systems that can have their own standards for interaction.
Integration with blockchain could be the most rigorous and general solution.

1 Like

I tend to think that this is something that each colony will need to define for themselves. Generally, Colony tries to be agnostic to the use-case, so each Colony will need to define the criteria by which it judges contributions to be satisfactory.

Totally agree that each colony should define this for themselves. I suppose something like this could be baked into setTaskBrief, where the specificationHash is a PDF file that includes the relevant legalese. I suppose I was thinking about what the legal context for a multi-sig of something like setTaskWorkerRole would be.

1 Like

Oops. I was confusing Colony with another platform when I wrote my last post.

It’s certainly the freedom and responsibility of each colony designer/community/member to write contracts. But I’m with Fugue in the aspect that good contracts are both essential colony success and may difficult to get right, particularly where stakes are high.

I’m new to colony and unclear if anything can be done on the platform side to help with contract design. May be a job for a legal specialist, but hiring one might be a financial weight for new developers and experimenters.

1 Like

Hey @Fugue. I am in agreement. High-quality task specification will be critical to users ability to assess their capacity to undertake a task, complete it to the manager’s satisfaction and as a basis upon which fair evaluation can take place. I don’t know if it’s its own cognitive bias (or just a subset of another) but people’s ability to transmit exactly what they have in mind to another person is, in my experience, nearly always overestimated. There are interesting questions around what efforts a worker should make to clarify any ambiguities in a task spec, but I share the thrust of your opinion; that achieving a meeting of minds can be hard.

As @auryn says, and as you seem to agree, given the combinatorily explosive range of possible interactions - the subjects about which clarity could be needed would be impossible to taxonomise top-down - getting this right is best attempted at the colony level.

Interested to hear your further thoughts on this. Can you say more?

In the past I’d considered ‘best practice’ guides around eg task specs, dispute resolution, evidential and procedural standards etc but one quickly gets into importing chunks of contract law wholesale.

1 Like

I suppose if I was to greatly over-simplify what made me start this thread, it would be simple CYA. If I create a task within a colony and the worker disputes the findings for whatever reason (to include them being a bad actor), what exactly can I point to (beyond the taskBrief itself) that covers me/the colony from frivolous litigation? To give an example:

Here are Colony’s terms and service and they have on their site before you link with Metamask to the dApp " By using our App, you agree to our [Terms and Conditions of Use]". What would be/could be the equivalent of that within the context of a colony, and what (from a UX perspective) would be the easiest way to enable this feature for an admin when creating a task? My initial thought was basically having it as a parameter for a multisig function that would be then signed by the worker, but I suppose you could just include it as part of the specificationHash itself.

await colonyClient.setTaskBrief.startOperation({

We’d really need someone with more of a legal background to weigh in on what exactly has legal precedent for a user’s acknowledgement of terms and services. Plenty of legal history with data forensics, but decentralized blockchains opens up a number of ambiguous scenarios and even more unforeseen situations we’ll discover as the space develops further.

I think we can safely just assume that no contract can be perfect in its protection of all parties, and that arbitration can generally make up for cracks in contracts. Arbitration is something that can be designed by colony architects and (IIRC) is basically provided for in the Colony system. (I’ve been away for a while.) If a colony has problems with contract disagreements, the colony can decide on an expanded arbitration scheme of some sort. (Like appeals to a larger arbitration board or expert arbitration service.

1 Like