A verbatim archive is written by a command that fetches it - #6
Merged
Conversation
"Verbatim" is a claim about bytes, and a hand transcription cannot make it true. Either a command reads the source and writes the file, so the bytes are the source-s bytes, or the file is not an archive and is not labelled one. Citing where the original lives is always available and always honest. Derivation, from a sibling tree that archived eight reviewer verdicts by hand under the label "Archived verbatim". Diffed against the source afterwards: four were abridged, one was a different round-s verdict entire, and one contained a sentence the reviewer never wrote - an attestation of independent verification lifted from another round with the identifiers substituted. That last one is fabricated evidence, and the text names it as such rather than as a transcription error. The others moved real text to the wrong place; that one created a verification claim nobody made, inside the file offered as proof of what was said. Same principle as the rule above it, applied to a copied artefact rather than a measured one, and the same family as a mutation reported as applied but never applied. An archive reported as verbatim but never fetched is indistinguishable from evidence, which is what makes it the worst member of that family. Closes SCR-258. Signed-off-by: Ayla Croft <aylacroft@proton.me>
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
1 participant
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.
CONVENTIONS.mdonly, 22 insertions, no code. Closes SCR-258."Verbatim" is a claim about bytes, and a hand transcription cannot make it true. Either a command reads the source and writes the file — so the bytes are the source's bytes — or the file is not an archive and is not labelled one.
Derivation, from a sibling tree that archived eight reviewer verdicts by hand under the label "Archived verbatim". Diffed against the source afterwards: four abridged, one a different round's verdict entire, and one containing a sentence the reviewer never wrote — an attestation of independent verification lifted from another round with the identifiers substituted.
That last is fabricated evidence, and the text names it as such rather than as a transcription error. The others moved real text to the wrong place; that one created a verification claim nobody made, inside the file offered as proof of what was said. All four unreliable files were deleted rather than repaired.
Same principle as the rule it sits under — every "verified" names its command and its exit code — applied to a copied artefact rather than a measured one. And the same family as a mutation reported as applied but never applied: an archive reported as verbatim but never fetched is indistinguishable from evidence, which is what makes it the worst member of that family.
Gate green: format, compile, test, credo, reuse, licence files.