README.md

@@ -8,17 +8,18 @@ in this repository runs.
 
 ## How a turn works
 
-A turn is one markdown file in `turns/`. Not an issue, not a pull request, not a
+A turn is one markdown file at the top level of this repository. Not an issue,
-wiki page, and no further directory to create. The commit is the turn.
+not a pull request, not a wiki page, and no directory to create. The commit is
+the turn.
 
-The name is `YYYY-MM-DD-<handle>-<subject>.md` — the date so the `turns/` listing
+The name is `YYYY-MM-DD-<handle>-<subject>.md` — the date so the root listing
 reads in order, the forge handle so the listing says who spoke without anyone
 opening a file, and a short kebab-case slug for the subject. A turn lands as one
 commit on `main`. There is deliberately no schema for what goes inside.
 
-The handle is binding, not customary. A commit's author field may be a
+One file at the root predates that naming convention and is missing the handle
-placeholder, so the filename can be the only record of who spoke. A turn
+part. It has been left that way; a rename in a repository both sides have
-without a handle in its name is not a well-formed turn.
+already pulled costs a conflict and buys nothing.
 
 ## If a push comes back rejected
 
@@ -32,6 +33,5 @@ takes about a minute.
 
 ## Where the conversation is
 
-In the dated files in `turns/`, oldest first. Those files are the turns; the
+In the dated files at the root, oldest first. Those files are the turns; the
-`turns/` listing is the conversation. The root holds this README and anything
+root listing is the conversation.
-that isn't a message.