Read the answers that landed rather than the questions they replaced - #217
Merged
Conversation
Every entry of the plan's question issue was answered on 2026-08-24 and eight decision records landed for the eight answers. Two documents went on describing entries of it as open, and one of them refused a hand-over the recorded answer permits. docs/promotion.md told a reader that who may place a contributor's work under another board's terms carries no answer, so a hand-over of somebody else's work still cannot be completed. Record 0020 answers exactly that, is on the default branch, and says of itself that the answer reaches this checklist and the section gains a fifth item. The item is added, naming the consent, when it is asked for and when it is not, and where it is written. The failure the repair prevents is a hand-over refused by a document rather than by a rule. The item is added with what does not stand behind it. Nothing in this repository refuses a promotion section that names no consent, because the check holds the section to the four things record 0005 names and adding a fifth is a record-format change under record 0013. Record 0020 states that residual and this document now carries it too, because an item read as enforced is worse than an item read as owed. docs/supply-chain.md rested three triage rows on the same entries. The Contributors row called who may contribute an open question, which record 0024 answers; the Packaging and Signed-Releases rows rested on whether this board publishes artefacts at all, which record 0021 answers, and the Packaging row named a permanent minus one as the correct outcome on a branch that can no longer be taken. No re-score was run, so nothing here claims a score moved and both rows say to re-read them against a scored run once a release exists. The new links are written the way docs/operator-guide.md and docs/privacy.md write theirs, relative to docs/. The two existing links in docs/promotion.md are written relative to the repository root and do not resolve from a file inside docs/. That is a defect and it is not repaired here, because it is a different topic from the one this change is about; it is written into the issue instead. This does not finish #216. One site is left: a decision record states the entry is open, and record 0000 says a landed record takes only one edit, the line naming what superseded it. What repairs a landed record carrying a claim that has stopped reproducing is a rule nobody has taken, and guessing it here would be worse than leaving the three words in place. Refs #216 Signed-off-by: Nils Lehnen <30603423+iderex@users.noreply.github.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Refs #216
What was wrong
Every entry of the plan's question issue was answered on 2026-08-24, eight
decision records landed for the eight answers, and two documents went on
describing entries of it as open.
docs/promotion.mdwas the one that cost something. It told a reader:Record
0020answers exactly that question, is on the default branch, and saysof itself that the answer reaches this checklist and that the section gains a
fifth thing. It had not:
So the document refused a hand-over that the recorded decision permits.
What the change does
The checklist gains the consent item: what it is, when it is asked for, when it
is not, and that it is written as a
Consent:line in the promotion section.It is added together with what does not stand behind it. Nothing in this
repository refuses a promotion section that names no consent, because the check
holds the section to the four things record
0005names and adding a fifth is arecord-format change under record
0013. Record0020states that residual andthe checklist now carries it too, because an item a reader takes for enforced is
worse than one they can see is owed.
docs/supply-chain.mdrested three triage rows on the same entries. TheContributorsrow called who may contribute an open question, which record0024answers. ThePackagingandSigned-Releasesrows rested on whether thisboard publishes artefacts at all, which record
0021answers, andPackagingnamed a permanent
-1as the correct outcome on a branch that can no longer betaken.
No re-score was run. Nothing here claims a score moved, and both rows now say to
re-read them against a scored run once a release exists.
What this does not finish
#216. One site is left and it is a question rather than an edit:
docs/decisions/0012-the-supported-platforms.mdstates the entryis open, andrecord
0000says a landed record takes exactly one edit, the line naming whatsuperseded it. What repairs a landed record carrying a claim that has stopped
reproducing is a rule nobody here has taken, and taking it inside this change
would be worse than leaving three words in place. The issue carries it.
Two sites named in that issue are deliberately untouched because neither is
wrong:
0001and0005say an entry is not decided in the record carrying thesentence, which is a statement about that record's own scope and is still true.
A defect found on the way and not repaired here
The two existing links in
docs/promotion.mdare written relative to therepository root and do not resolve from a file inside
docs/:docs/operator-guide.mdanddocs/privacy.mdwrite theirs relative todocs/,and the two links added here follow them. Repairing the other two is a different
topic from this change and it is written into the issue rather than done here.
The means
Markdown prose in two documents that already exist, because what is wrong is what
those documents say. Nothing here adds a language, a runtime or a dependency.
Whether a document describes an answered question as open is a judgement about
meaning that no reading of this tree makes, so no check is owed for it and none
is added.
The gate, run at this head
Every one silent or green;
gofmt -lprinted nothing, which is its passingresult. All thirteen packages returned
ok, and the runner's own verb:Reading
There is no second reader for this change tonight. The evidence above stands in
place of one rather than replacing it.