/Docs/S/OurLegal/Sec/StyleSheet_v0.md
  Source views: Source JSON(ish) on GitHub (VSCode)   Doc views: Document (&k=5.r00t): Visual Print Technical: OpenParameters Xray
Section Organization
It would greatly help our review if sections are organized along patterns that we are used to. If you can't find a form agreement from a library to serve as a model, please try to conform to the following to the extent practical:
  1. The first section should be a "Focus" section. It will include a subsection of "Variables" and the sections that define the basic deal. It should be possible for a person to understand the basic elements of the transaction after reading only the "Focus" section.
  2. The "Variables" subsection defines items such as prices, dates, descriptions, special provisions. These are handled like defined terms. E.g., define ' "{_Price_Per_Unit}" means 8 Euros.' And in the document use ' A discount of {_Discount_Rate} will be applied to the {_Price_Per_Unit} for purchases of more than ... '
  3. After the "Focus" section, the other sections can be organized as "Relationship", "Miscellaneous" and "Interpretation." This is not mandatory, but allows us to find things rapidly. For many documents, "Relationship" is the largest of these sections. It includes issues such as IP, Confidentiality, Representations, continuing Covenants, Disputes, etc. "Miscellaneous" is most about the agreement itself. "Interpretation" has two subsections: "Definitions" and "Construction." Definitions has been discussed above. These definitions are intended to be anodyne, background, deepening. They are not intended to contain surprises. If a term is used in a surprising way, it is more appropriate to put it in the "Variables" section. The general principle of "increasing banality" applies.