What is the value of your work? Is it just the value of your time? Most jobs, including gig-work, exchange money for your time and your copyright.

By selling yourself as timeslices, you also lose a great deal of control. What if the task takes twice as long? Or half as long? Or if there's an entirely novel way to do it that isn't in the jobsheet but you're stopped from pursuing it? Or worse, you can pursue it but because you're 'on-the-clock' ownership of that idea now belongs to someone else?

By selling yourself in timeslices you don't necessarily get the freedom to spot and do what you know is necessary.

So many Do-ers would prefer not to sell their time and copyright for a one-off fee. The most talented want to build software and generate an income stream from how successful it is.

But the majority of the job market in software construction doesn't allow that.

You also don't get to self-select jobs that you can make a real impact with. Those jobs that you can do better than most, maybe even better than everyone, but which come up rarely and when they do, because you're skilled, it takes you less time and so you get paid less.

Dreamcatcher works by giving a framework for maximising your own output, reducing barriers to entry, encouraging re-use and recombination of code and by aligning the incentives of all involved.

A good job should be rewarded for the output, not the effort. Wouldn't it be helpful then to get more returns from doing something you're more highly skilled at than others, spend less time doing it, and get paid for what it's worth.

Dreamcatcher focuses on this concept; it matches Ideas (a piece of work that others have identified as being useful), with those best placed to contribute to building those Ideas into Products.

It focuses on outputs - finished, useful work - not time. If you can solve a problem in an hour that takes another Do-er 6 days, then the same level of rewards are due.

It registers those outputs at a micro-level - down to a single commit - and then records your ownership of that output as an NFT. That NFT is your asset; you may choose to sell the royalty stream from that asset up front if you need the money, split the cost based on your day rate and share the rewards, or turn up without permission, solve the problem and keep the ownership.

Perhaps those assets can generate a revenue stream over years or decades - for as long as they're still proving useful. If you solve a particularly useful problem, that revenue stream could be generational.

We call this Ambient Attribution.

Dreamcatcher is built on the concept of Ambient Attribution.

Ambient Attribution ensures everyone involved knows that they will get their fair share of any and all rewards coming from the completion of a task. Those tasks can be big or small. It can involve a Buyer suggesting a feature, an innovator proposing a completely new product, a Funder taking an early position on a great new idea - it's the impact of each contribution that dictates the Algorithmic Cap Table.

That Algorithmic Cap Table is guaranteed in code, and ensures that all incentives, throughout the whole project team, are pointing in the same direction.

Ambient Attribution ensures transparency; with transparency, a Funder can be sure that the funds put forward is being spent on what matters.

One of the other great barriers to making a decent living as an independent Do-er is maximising the utility of your work.

In general, there are very few unique problems out there to be solved. More usually a solution to a problem can be re-used wherever that problem is felt.

Dreamcatcher encourages this reuse by providing an off-the-shelf licensing and legal framework that allows others to use your work without further interaction, while ensuring through Ambient Attribution that you get paid for that re-use.

This also works both ways. Duplication in software development is inefficient. If a Product only needs 10% new code to be written, why re-write the other 90%? Someone else has already done that. Under the same licensing scheme Dreamcatcher allows you to make use of the work of others on new Projects, and ensures that, just as with your own work, they get their fair share should the revenue come.

So Dreamcatcher is a great deal for Do-ers. But what about the Buyers and Funders? If this is a zero-sum game then they won't turn up.

Code is not the only way to contribute. A Buyer who identifies a problem in their company that they want solved by software is contributing by clearly identifying that problem. That's a contribution which should be recognised.

Funders willing to back work undertaken to solve a problem are likewise contributing. That again is a contribution that should be recognised.

All of these contributions are considered through Ambient Attribution, secured through the Dreamcatcher License and arbitrated by independent QAs arbiters.

Moreover, the reality is that we all, at different times, take on these different hats. They're not mutually exclusive and neither they should be. A Do-er who includes a library in their code is a Buyer; a Buyer who offers an escrowed pool of money for something they need is a Funder; a Funder who improves and promotes a good Idea is a Do-er. There are many ways that the lines between these three are grey.

But by making the rules the same for all, everyone's incentives align, reducing the cost and improving the competitiveness of all who contribute.

Under Dreamcatcher, you share in the benefits through cooperation.