. e Manual edits

Author: isidore

.windsurf/ArloCommitNotation.process.md

@@ -5,10 +5,9 @@ Arlo Commit Notation is a system for prefixing commit messages with a short code
 ## Commit Message Structure
 
 ```
-[hash] [prefix] [commit message]
+[prefix] [commit message]
 ```
 
-- **hash**: The git commit hash.
 - **prefix**: A short code, typically two characters (sometimes more), that encodes information about the commit.
 - **commit message**: Description of the change.
 
@@ -20,39 +19,39 @@ The prefix generally follows this pattern:
 [symbol][space][letter(s)]
 ```
 
-- **symbol**: One of `.`, `-`, `!`, `@`, `***`, `v`, or none.
+- **symbol**: One of `.`, `-`, `!`, `@`, `***`.
 - **letter(s)**: One or more letters, usually a single uppercase or lowercase letter, sometimes two (`dt`).
 
 ### Observed Prefixes and Likely Meanings
 
 | Prefix    | Meaning (Inferred)                    |
 |-----------|---------------------------------------|
-| `. e`     | Enhancement, engineering, or edit (not shipped to user, e.g., scripts, infra) |
+| `. e`     | Environment / Changes that are only used by the developer to use the system (not shipped to user, e.g., scripts, infra) |
 | `. d`     | Documentation (not shipped to user)   |
 | `. t`     | Test (not shipped to user)            |
-| `. r`     | Refactor (not shipped to user, or tooling-safe refactor) |
+| `. r`     | Refactor (tooling-safe refactor) |
 | `. C`     | Release/Changelog                     |
-| `- r`     | Refactor (possibly higher risk)        |
-| `- F`     | Feature (possibly higher risk)         |
-| `! r`     | Risky refactor                        |
-| `! F`     | Risky feature                         |
-| `@ r`     | Refactor (special context)            |
-| `@ F`     | Feature (special context)             |
-| `***`     | Major/experimental/unknown            |
-| `v`       | Version bump/release                  |
-| `a`       | Automated/formatting                  |
-| `. dt`    | Documentation for DynamicTest         |
+| `- r`     | Refactor (unit tested)        |
+| `- F`     | Feature (unit tested)         |
+| `! r`     | Risky refactor (but single change)                        |
+| `! F`     | Risky feature (but single change)                         |
+| `@ r`     | Refactor (really risky)            |
+| `@ F`     | Feature (really risky)             |
+| `***`     | Work in progress (these are intermediate commits in a chain of the thought. The project is usually in a broken state at this point)            |
+
+| `. a`       | Automated/formatting                  |
+| `. dt`    | Documentation with Sample Code in a Unit Test        |
 | (none)    | Merge, bump, or update (auto/merge)   |
 
-> **Note:** The exact meaning of each prefix may depend on team conventions. The above are inferred from commit messages and may need confirmation.
+## Inconsistencies
+Some of the commits in this repository are not going to adhere to our format. Those are mistakes. Don't base your rules on them.
 
 ## Guidelines for Use
 
 - Always use a prefix unless the commit is a merge, bump, or automated update.
 - Choose the symbol and letter(s) that best match the intent and risk of the commit.
 - Use uppercase letters for features, releases, or high-impact changes.
 - Use special symbols (`-`, `!`, `@`, `***`) to indicate increased risk, automation, or special cases.
-- For version bumps, use `v` followed by the version number.
 
 ## Next Steps