From 8e038d4d0dd1ddf650c3789bb70116a2eb9aded81713d83c1ffc61afef534688 Mon Sep 17 00:00:00 2001 From: Jansen Smith Date: Tue, 22 Sep 2026 00:48:33 -0400 Subject: [PATCH] jansen: give the 08-25 reply its handle and make the convention binding (proposal, for review) --- README.md | 6 +++--- ...t.md => 2026-08-25-dkp-reply-to-the-crosswalk-report.md} | 0 2 files changed, 3 insertions(+), 3 deletions(-) rename turns/{2026-08-25-reply-to-the-crosswalk-report.md => 2026-08-25-dkp-reply-to-the-crosswalk-report.md} (100%) diff --git a/README.md b/README.md index 3ab9c88..48d0bca 100644 --- a/README.md +++ b/README.md @@ -16,9 +16,9 @@ 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. -One file in `turns/` predates that naming convention and is missing the handle -part. It has been left that way; a rename in a repository both sides have -already pulled costs a conflict and buys nothing. +The handle is binding, not customary. A commit's author field may be a +placeholder, so the filename can be the only record of who spoke. A turn +without a handle in its name is not a well-formed turn. ## If a push comes back rejected diff --git a/turns/2026-08-25-reply-to-the-crosswalk-report.md b/turns/2026-08-25-dkp-reply-to-the-crosswalk-report.md similarity index 100% rename from turns/2026-08-25-reply-to-the-crosswalk-report.md rename to turns/2026-08-25-dkp-reply-to-the-crosswalk-report.md