From baed74e25c19a869db8d231cc149a7f975657380 Mon Sep 17 00:00:00 2001
From: Nils Lehnen <30603423+iderex@users.noreply.github.com>
Date: Mon, 31 Aug 2026 12:14:46 +0200
Subject: [PATCH] Write in the first person where a role word described me
 [#220]

Three tracked files described me from outside instead of saying "I". The text
this project carries is written in the first person, so a word that reports on
me from outside is a defect in the voice rather than a wording preference. The
word is `maintainer`, and it stands here only inside backticks and indented
blocks so that the sentences of this message are themselves in the voice they
are about.

Before, at cfa174a:

    git grep -icl maintainer -- . | wc -l
    3

`decisions/0004` said commits would land in the organisation profile tree from
a source its own holder was not reading. That tree is Flowfin/.github, and its
roster record in the operations tree names one writer:

    git -C G:/Github/operations show origin/main:store/repo/.github.md | sed -n '7,8p'
    Owner: Flowfin
    Writers: iderex

So the sentence was about me and now says so.

`decisions/0006` and `decisions/0008` both handed entry 3 of issue #7 to
somebody named in the third person. That call is mine, and both records now
say so.

Each of the three is a correction that does not change the answer, which
`decisions/README.md` admits as an ordinary edit on a landed record:

    Corrections that do not change the answer are ordinary edits: a broken
    link, a misspelled identifier, a command that has to change because the
    thing it queries moved.

None of the three moves what a reader would decide after reading the record,
so none of them needs a new number and none of them supersedes anything.

After:

    git grep -il maintainer -- . ; echo "exit=$?"
    exit=1

    go run . ci
    7 of 7 legs ran. None was skipped.
---
 decisions/0004-one-table-two-places.md                  | 2 +-
 decisions/0006-what-answers-at-the-catalogue-address.md | 6 +++---
 decisions/0008-the-url-shape.md                         | 6 +++---
 3 files changed, 7 insertions(+), 7 deletions(-)

diff --git a/decisions/0004-one-table-two-places.md b/decisions/0004-one-table-two-places.md
index 40ec30f..a08e757 100644
--- a/decisions/0004-one-table-two-places.md
+++ b/decisions/0004-one-table-two-places.md
@@ -61,7 +61,7 @@ remove, and it is the same failure record 0007 refuses for the design tokens.
 
 Have this build write the profile table directly. The cost is a credential that
 reaches another repository, held by a job here, plus commits landing in that
-tree from a source its own maintainer is not reading.
+tree from a source I am not reading when I edit it by hand.
 
 ## When this is worth revisiting
 
diff --git a/decisions/0006-what-answers-at-the-catalogue-address.md b/decisions/0006-what-answers-at-the-catalogue-address.md
index 0afe747..7661fb3 100644
--- a/decisions/0006-what-answers-at-the-catalogue-address.md
+++ b/decisions/0006-what-answers-at-the-catalogue-address.md
@@ -75,9 +75,9 @@ invisible.
 
 ## What this record does not decide
 
-Whether the domain moves at all is the maintainer's call, as entry 3 of issue #7.
-Nothing here decides it, and what this record states has to hold on whichever
-answer comes back.
+Whether the domain moves at all is my call, as entry 3 of issue #7. Nothing
+here decides it, and what this record states has to hold on whichever answer
+comes back.
 
 ## When this is worth revisiting
 
diff --git a/decisions/0008-the-url-shape.md b/decisions/0008-the-url-shape.md
index b9432d6..7367481 100644
--- a/decisions/0008-the-url-shape.md
+++ b/decisions/0008-the-url-shape.md
@@ -96,9 +96,9 @@ which is the kind this project cannot see and cannot repair.
 
 ## What this record does not decide
 
-Where the addresses are served from is entry 3 of issue #7 and is the maintainer's
-call. The catalogue address is held by record 0006 and is fixed by a commitment
-rather than by this scheme.
+Where the addresses are served from is entry 3 of issue #7 and is my call. The
+catalogue address is held by record 0006 and is fixed by a commitment rather
+than by this scheme.
 
 The scheme above is written for a site published in one language. Entry 2 of issue
 #7 has an option that publishes two, and on that answer every address here gains a