#+OPTIONS: toc:2 num:nil
* Purpose
-The Harmony skeleton is **Prescriptive**; it defines the authoritative rules for file organization based on fundamental properties (invariants). This system is designed to formalize concepts, eliminate ambiguity, and serve as a central working point for the team.
+The Harmony skeleton is cloned as a starting point for git based project development. Harmony is designed to serve as a central working point for a team.
-* 1. Core Prescriptive Invariants
+* 1. Some nomenclature.
** The Foundational Principle: Create vs. Make
-The project's philosophy is rooted in this semantic distinction, which governs all directory naming:
-- **CREATE:** The act of originating intent. This power belongs only to **God, Artists, and SQL programs.** To avoid confusion we make use of the synonym **authored**.
-- **MAKE:** The act of assembling materials into a product. This is performed by **Factories (Build Tools)**.
+- Something **Created** came from God, Artists, or, apparently SQL interpreters. We will include developers in with Artists.;-) Created written material is **Authored**.
+- Something **Made** is the result of assembling materials into a product. This is done by **Factories** and **Build Tools**.
-The directory structure enforces this semantic separation.
-
-** Provenance: Authored vs. Made
-- **Authored** (The Artist): Trees holding human-written intent (CREATE). Tools must treat as *read-only*.
-- **Made** (The Factory): Trees holding machine-generated content (MAKE).
+With created things it is a mystery as to how it happened. With made things we can typically point at a factory.
** Property Schema (The Semantic Path)
Directory names are properties bestowed upon their contents. The path is a descriptive sentence: