The document I have been reviewing seems like a good start on a
spec for what we were hoping for.
The rules are there but they don't seem to be self-enforcing.
The art of game theory is to engineer the right outcome by constructing the incentives in such a way that people do the right thing naturally in their own self interest without requiring an outside party to have to enforce the rules. Enforcement by an outside force always leads to conflict and hard feelings - what we are hoping to avoid.
A simple example: The Quality Assurance function (missing from the current process) might be set up such that the QA person gets a share of the developer's share proportional to the number of bugs found. This incentivizes the developer not to have bugs when the product is submitted to QA. And the buyer knows that the product is probably bug free if a properly incentivized QA person couldn't collect a big payout. But the process still has to reward the QA person for trying, lest they be discouraged by receiving perfect code too often. The best QA person might be a competitor who has plenty of motivation for finding fault. If your competitor can't find a fault, you've got a really great product.
Game theory logic like this is largely missing from the product so far. I like the fact that the document hasn't become bloated, but it seems to put the burden on the customer to determine if all the rules have been followed or not.
If we are to maximize the number of bounties available to the community, we can't be refereeing all the internal steps of the process.
For example: "Submissions with bugs may be penalized and may result in complete disqualification." How does the customer know that there are no bugs and are we expecting the customer to do the penalizing instead of the natural processes built into the system? If we have to do that ourselves, we won't have enough time available to sponsor many bounties!
In short - the current document does not define a process that is scalable to the number of bounties we hope to offer.
Innovations are needed here. How does this document put in place a system that delivers a quality product that an already overloaded customer can buy with confidence?