The tree says I where it described a role from outside

[iderex]

Closes #162.

The issue names five tracked files carrying the role word the order of 30 August
removes, and asks that what is left after the repair be only text this project
did not write, each such file named with the reason it stays. Nothing is left,
so the list of files that stay is empty, and the section below says why that is
an answer rather than an omission.

What the head carried

Nine sites in the five files the issue names, read at origin/main
8cc74e25c9e915efe4ce23313ce90b1ee28d826c:

$ git grep -in 'maintainer' origin/main -- . | sed 's/^origin.main://'
CODE_OF_CONDUCT.md:90:private to the maintainers.
SECURITY.md:12:enabled and it goes to the maintainers only.
decisions/licensing.md:12:**The code is AGPL-3.0-or-later.** The licence was taken by the maintainer on
decisions/licensing.md:20:settled by the maintainer on 2026-08-24, who read the `-only` answer as a slip
decisions/licensing.md:25:Decided by the maintainer on 2026-08-11, with the reason: a design system other
decisions/licensing.md:30:the maintainer on 2026-08-24, because the boundary does not run between files and
decisions/licensing.md:158:that is an answer rather than an omission. The maintainer decided it on
decisions/site-language.md:9:The published pages are in English. Decided by the maintainer on 2026-08-09 in
internal/lang/lang.go:35:// English, decided by the maintainer on 2026-08-09 in entry 3 of #1 and recorded

Seven of the nine attribute a decision this account took. Each becomes first
person and keeps its date and its entry reference, because the date is what the
sentence is for and only the voice was wrong.

The two that are not attributions, and the reading behind them

CODE_OF_CONDUCT.md:90 and SECURITY.md:12 name who receives a private report,
and both said it in the plural. Who receives one is a fact about this repository
rather than a matter of phrasing, so it is read rather than recalled:

$ gh api repos/Flowfin/hub/collaborators --jq '.[] | .login + " " + .role_name'
iderex admin
$ gh api orgs/Flowfin/members --jq '.[].login'
iderex

Both sentences now say the report reaches me and nobody else. That is narrower
than the plural it replaces and it is backed by the reading above; the
restriction each sentence states is the same one it stated before, and neither
admission in either file is softened.

What stays, and why the list is empty

The issue's exception is for text this project did not write. This tree holds
two such texts and neither carries the word:

• The Contributor Covenant body of CODE_OF_CONDUCT.md, version 2.1 adopted
  verbatim, says community leaders throughout and never the word. The one site
  in that file is in ## A note on the reporting route, appended below the
  attribution block, which is this project's own sentence about its own
  reporting route.
• LICENSE and LICENSES/ carry it nowhere, which is why neither appears in
  the reading above.

So no file is named here as one where it stays, because there is none. At the
head of this branch:

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

Means

The tree's own prose and one Go line comment, unchanged from what each of the
five files is already written in. The change rewords existing sentences, so
every one of the three rules is carried exactly as it was before by the same
means, and introducing a format or a tool for a rewording would add a thing to
this tree for a change that removes one.

Nothing executable moves

The only Go file touched is a line comment above lang.Tag, whose value stays
"en". The gate is green on this branch and covered every leg:

$ go run . gate
gate examined 14 of 14 legs.
  build                            passed
  test                             passed
  format                           passed
  editorconfig                     passed
  tests-reach-nothing              passed
  no-hardcoded-names               passed
  site-fetches-nothing-outside     passed
  site-links-resolve               passed
  coverage                         passed
  site-declares-its-language       passed
  install-address-is-answered      passed
  colour-stands-off-every-surface  passed
  page-matches-the-token-file      passed
  pr-hygiene                       passed

No guard is added and none is deleted, so there is no deletion to watch go red:
this change adds no refusable property, and no leg of this gate has the role
word as its subject. What refuses the word is the write path in front of GitHub
rather than anything in this tree, which is why the issue exists at all and why
the tree is the half the write path never reached.

No second reader

Nobody but me has read this change. That is stated rather than left to be
assumed, and the readings above stand in place of a second pair of eyes: the
before and after greps are the whole subject, and both are one command each.