Editing Legislative governance proposals (section)

===Example for dev bounty===
Suppose a DAO wishes to offer a bounty for improving the UI, say to make the skin more attractive. The basic process would be to make a proposal to the DAO that they should pay a certain amount <math>$b</math>, which could be claimed by anyone who satisfies the stipulations of the proposal. If the proposal is eventually accepted by the DAO according to the following legislative process, then the proposal would become an active smart contract which selects a developer for the job following DGF [[DAO Governance Framework#DGF workflow|work flow]]. The process for funding the proposal is also detailed below.
====Legislative process for adopting a bounty proposal====
The governance process is as follows:
#A proposal is submitted.
#If accepted the proposal becomes a promise.
#Future work posts donate their REP to fill all promises.
#When a promise is filled it becomes a fulfilled promise.
In greater detail: A ''proposal'' is a post submitted to the Validation Pool for gREP owners to consider. If the proposal is accepted by the DAO through a [[Validation Pool]], then it becomes a ''promise''. A promise typically has 0 value at initiation and will only gain REP value after subsequent references give it power. A proposal references other posts, donating and/or leaching, which entail a suggestion for redistribution of REP. In other words, a proposal has a set of references and number called its full potential. The ''full potential'' is the value it proposes to eventually receive by future work posts. The full potential and the references determine the actual value of REP redistribution of a proposal.

That is, a promise is a validated proposal in the Forum which has a set of references and a specified full potential, which is filled by references from future WSCs.
====Funding the bounty====
Typically a promise starts with 0 value, then subsequent work posts donate REP value ([[Legislative governance#Governance tax|governance tax]]) to it until it reaches value equal to its full potential. Then the promise becomes a ''fulfilled promise''. Before a promise is fulfilled, it is an ''unfulfilled promise''.

The WSC has the functionality of referencing unfulfilled promises. The worker UI scans the Forum for new promises and parses the difference between the sets of fulfilled and unfulfilled promises. If there are no outstanding unfilled promises, then the UI automatically donates its [[Legislative governance#Governance tax|governance tax]] to the incinerator. The other worker UIs verify that each new WSC submitted has added the required references before validating.
====DGF work flow for claiming the bounty====
For a worker to do the work and claim the example bounty, the worker follows basic DGF [[DAO Governance Framework#DGF workflow|work flow]].
#Workers willing to participate encumber REP in the bounty availability smart contract (ASC).
#Bounty Work smart contract (bWSC) selects the worker(s) from the ASCs.
#Worker finishes the work off chain, then has the bWSC submit the proof as a post to the Forum, which opens a Validation Pool.
#Validation Pool mints new REP and opens the voting for validation. VP distributes the fee and new REP.
There are several alternatives for funding the bounty and paying the worker, as discussed in [[Reputation tokenomics#Applications|REP tokenomics applications]].