From 4665007c1e651c7bd6db1105d179b658364cb86c Mon Sep 17 00:00:00 2001
From: Thomas Walker Lynch <eknp9n@reasoningtechnology.com>
Date: Mon, 9 Mar 2026 08:05:36 +0000
Subject: [PATCH] doc tweaks

---
 ...ntions.html => File_directory_naming.html} | 40 ++++++++++++++-----
 developer/document/RT_code_format.html        |  8 ++--
 2 files changed, 34 insertions(+), 14 deletions(-)
 rename developer/document/{File and directory naming conventions.html => File_directory_naming.html} (57%)

diff --git a/developer/document/File and directory naming conventions.html b/developer/document/File_directory_naming.html
similarity index 57%
rename from developer/document/File and directory naming conventions.html
rename to developer/document/File_directory_naming.html
index afa4ad3..6de0ede 100644
--- a/developer/document/File and directory naming conventions.html	
+++ b/developer/document/File_directory_naming.html
@@ -17,15 +17,41 @@
         title="File and directory naming conventions">
       </RT-title>
 
-      <h1>Case</h1>
+      <h1>Program file system objects</h1>
+
       <p>
-        Directory and file names follow the exact same casing rules as the identifiers they represent. Because standard file systems support the hyphen (<RT-code>-</RT-code>), file and directory names use <RT-code>snake-kebab_case</RT-code> for functions and scripts, and <RT-code>PascalCase</RT-code> for types and modules. The hyphen serves as the primary word separator, while the underscore (<RT-code>_</RT-code>) is reserved for structural or namespace boundaries. (Currently many file names use primarily `_`, but we will transition to this more uniform approach.)
+        Harmony files and directories are considered to be program file systems objects.
       </p>
 
-      <h1>Directory properties</h1>
+      <h2>Files</h2>
       <p>
-        A directory name is taken as a <RT-term>property</RT-term> for a set of files. Consequently, directory names are rarely plural. For example, suppose we have a number of test files in a directory. The directory would be named <RT-code>test</RT-code>, as each file in the directory has the property of being a test.
+        Files that hold a single class, have he same base name as that class. If a file holds multiple classes, but there is a class of primary importance and auxiliary classes, the file carries the name of the primary class.
       </p>
+
+      <p>
+        If a file represents a module or name space, follow the same naming conventions specified for classes and name spaces in the <RT-code>RT_code_format.html</RT-code> document.
+      </p>
+
+      <p>
+        Other program files follow the same naming conventions specified in the <RT-code>RT_code_format.html</RT-code> document for an identifier of the
+        contained or related language.
+      </p>
+
+      <h2>Hyphens and spaces</h2>
+
+      <p>In a C language culture, file names use underscores between words. In a Lisp language culture use snake-kebab_case. Spaces are generally not used in program file names.
+      </p>
+
+
+      <h1>Program Directories</h1>
+      <p>
+        A directory that is a package, follows the convention for name spaces.
+      </p>
+
+      <p>
+        A directory that is used to give the contained files a property is an identifier.
+      </p>
+      
       <p>
         What is a reasonable primary property for a set of files? Perhaps:
       </p>
@@ -36,7 +62,7 @@
         <li>The generic category of program said files are for. We prefer the names <RT-code>authored</RT-code> and <RT-code>made</RT-code>. <RT-code>authored</RT-code> files are those written by humans or AI, while <RT-code>made</RT-code> files are products of tools.</li>
       </ul>
 
-      <h1>Dot extensions as properties</h1>
+      <h1>Property indicators on files</h1>
       <p>
         We add a second property to a file using dot extensions to the file's name. We can extend the dot suffix model by using multiple dot suffixes. File name extensions are used to signal to the build tools how the file is to be processed:
       </p>
@@ -46,10 +72,6 @@
         <li><RT-code>.mod.c</RT-code> : Kernel module sources.</li>
       </ul>
 
-      <h2>C source file structure</h2>
-      <p>
-        The RT C coding environment does not use separate source and header files. Each module has an <strong>Interface</strong> section and an <strong>Implementation</strong> section in the same file. A preprocessor macro (e.g., <RT-code>FACE</RT-code>) is used to gate off the implementation if the source code is to be used as a header. 
-      </p>
     </RT-article>
   </body>
 </html>
diff --git a/developer/document/RT_code_format.html b/developer/document/RT_code_format.html
index d9085a2..e01c98d 100644
--- a/developer/document/RT_code_format.html
+++ b/developer/document/RT_code_format.html
@@ -109,12 +109,10 @@
         }
       </RT-code>
 
-      <p>This rule is not applied to function calls in Lisp.</p>
-
-      <h2>Short stuff rule</h2>
-      <p>If a statement can fit on a single line and is short, keep it on a single line without braces.</p>
+      <p>This rule is not applied to function calls in Lisp. For example, the outer parentheses forming a function call receive no padding, even when they contain nested data lists:</p>
+      
       <RT-code>
-        if(x == 0) return;
+        (cat 'a 'b '( 2 (4 5)))
       </RT-code>
 
       <h1>Indentation</h1>
-- 
2.20.1