If you start a new stage, change the value of the iteration property. So after you have created the document in the facade stage and you start to add additional information, set the stage to filled, until you decide you have aggregated enough. Then switch to focused to start the pruning process. If you are satisfied, tag the document as finished. If it is discussed by the team and accepted, move it to released. As soon as it is ready for delivery to third parties, tag it as production. Once you decide the information is no longer valid in near future, signal this state by entering the deprecated state. If it is no longer valid, the document finally arrived in the end state removed. | Caution Box |
|---|
Please notice that the first three states define a stage within the process the document is in, while the other states actually define a state the document has already achieved. |
The first four stages are based on | Cite |
|---|
| template | $[Name] (${Authors}) |
|---|
| document | PDAC:Kulak2000 |
|---|
|
. The authors defines those stages to iteratively develop use cases. But we think those stages also help to create documents of any type. | 
