if the architect changes his mind - he has to clean up the mess the change created.
Of course nobody is allowed to check in code that breaks tests.
-Only completed features with their tests as one commit are acceptable. This means:
-at this point we use short lived feature branches, that pick the the code from a
-use case prototype and bring it into the program.
- * documentation (user, programmer, comments)
+Only completed features with their tests are acceptable and will be inserted as
+one commit. This means: at this point we use short lived feature branches,
+that pick the the code from a use case prototype and bring it into the program.
+Try bring the programm with the merge into a state, where it could be shipped today.
+This not only means that the code is documented, commented and has test coverage.
+Also configs and other auxiliary data like icons should be included.
+If there is an config dialog or config files - all switches for the new function
+are there and do work. make sure you only rely on included libs or modules that
+are listed in the installer. Please mention also in the comments which prototypes
+were the basis of this feature.