Index: trunk/doc/design/10_forge.html
===================================================================
--- trunk/doc/design/10_forge.html	(revision 8155)
+++ trunk/doc/design/10_forge.html	(revision 8156)
@@ -84,7 +84,7 @@
 <ul>
 	<li> <b>str == str</b> is 1 if the two strings match (case sensitive), 0 otherwise; the result is an integer
 	<li> <b>str != str</b> is 0 if the two strings match (case sensitive), 1 otherwise; the result is an integer
-<ul>
+</ul>
 
 
 <p>{des10:12} The following binary operators are defined for integers, with
@@ -112,9 +112,25 @@
 <p>{des10:14} Parenthesis affects the precedence the usual way.
 
 
-<h2 id="des10.2">> 10.2. Stances for conditinal forge </h2>
+<h2 id="des10.2"> 10.2. Stances for conditinal forge </h2>
+<p>{des10:15} One of the factors that can be used in conditional forge is
+<i>project stance</i>, which is a collection of project build options: when
+the same project can be used to produce differently configured boards/circuits,
+stance values determine which option is currently displayed or exported.
 
-TODO
+<p>{des10:16} Each stance has a name and an arbitrary textual value. Optionally
+the implementation may provide a list of possible values. All values are
+invented by the user.
 
+<p>{des10:17} The implementation is free to define stance names but the
+following three must be supported:
+<p><table border=1 cellspacing=0>
+<tr><th colspan=3 bgcolor="#aaaaaa"> standard stances
+<tr><th> name      <th> usage provisions 
+<tr><td> model     <td> for the simplest cases, this single stance selects which one of the build configurations is used (e.g. which model or variant of the board is made)
+<tr><td> sub_major <td> major subtype; if there's a build option that is orthogonal to the model, this stance should be used
+<tr><td> sub_minor <td> minor subtype; if there's a build option that is orthogonal to both the model and the sub_major stances, this stance should be used
+</table>
 
 
+