Skip to content

Sixteen seams where the page said one thing in prose and another in a list, a cell or a link - #37

Merged
wshallwshall merged 1 commit into
mainfrom
claude/asvs-assessment-intro-b1f745
Aug 11, 2026
Merged

Sixteen seams where the page said one thing in prose and another in a list, a cell or a link#37
wshallwshall merged 1 commit into
mainfrom
claude/asvs-assessment-intro-b1f745

Conversation

@wshallwshall

Copy link
Copy Markdown
Owner

The rest of the coherence review, after the five defects that made an implementer build the wrong artifact landed in 5e2ef34 (#33). Thirty edits. No argument on the page is reversed.

What was wrong, by class:

  • Duplication. Four passages told twice, three near-verbatim across the Part 1 boundary — including the page's only first-person narration, and a cost argument whose two copies had already drifted apart in wording.
  • Reference. "This repository" named three different trees. Two of the paths it points at do not exist here, and an agent can act on that by searching its own tree for them.
  • Navigation. The pre-flight reading list named two sections and summarised three items, the third delivered by neither. Part 2's manifest accounted for three of the six forcing functions it delivers. The paste command said "begin at step 1" where the agent's slice supplies two different step ones.
  • Unproved claims. Three absolutes the page's own checklist requires be proved or weakened, two competing claims of page-level primacy, and one passage saying no body assesses you against ASVS while another describes the organizations that do.
  • Vocabulary. "Verified" carried two senses producing different numbers from one instruction. A requirement ID was called a control ID — in the section arguing a requirement is not a mechanism. "Cell", the page's most-used term at 125 occurrences, was never defined.
  • The three residues from Five rules disagreed with the page that states them, and one of them could never fire #33 are closed: the rule field's domain, the line field's advisory read, and review row 5 checking all three parts of an absence claim.

How this was produced. Six batched drafters, an adversarial checker on each, then a reconciler doing what no batch could — cross-batch collision detection and ratchet arithmetic. Six edits were amended before landing: two edits to the same paragraph were merged, one coined a fifth name for the decision procedure, one removed a job name at one end of the page while another reintroduced the same ambiguity 1,400 lines earlier, and one wrote a fresh unproven completeness claim into the page whose failure table ranks that defect first. None of those was visible from inside a single batch.

What was deliberately not done. verified_at is not renamed — the name is published and entered the checklist two commits ago, so the correction is made at the definition site instead. The Part 1 / Part 2 label mismatch stays, because dropping that vocabulary costs a second file: HOUSE-STYLE.md pins that section as the only marker that Part 1 ends. Four further items are recorded and left open rather than half-closed.

Measured. Long sentences 219 → 217 against a baseline of 219, inside the slack band, so the baseline does not move. Fat cells 30 → 30, at baseline with zero slack. Words 61,422 → 61,484. Zero doubled blank lines, zero non-ASCII bytes, every internal anchor still resolving. 146 tests green, Word copy rebuilt with pandoc 3.10.

🤖 Generated with Claude Code

… list, a cell or a link

The rest of the coherence review, after the five defects that made an implementer build the wrong
artifact landed in 5e2ef34. Thirty edits, no argument on the page reversed.

WHAT WAS WRONG, by class rather than by edit.

DUPLICATION. Four passages were told twice, three of them near-verbatim across the Part 1 boundary.
The condensed-wording anecdote opened two sections with the same sentence and was the page's only
first-person narration. The per-cell cost argument ran twice with two sentences byte-identical, and
the copies had already drifted apart in wording. The See also block repeated the body's descriptive
sentence rather than only its link.

REFERENCE. "This repository" named three different trees. Two of the paths it points at do not exist
here -- no bin/, no scripts/coord/ -- and every one of those links resolves to a different published
site, while the agent-addressed half uses the same phrase to mean the tree under assessment. An agent
can act on that mistake by searching its own tree.

NAVIGATION. The pre-flight reading list named two sections and summarised three items, the third
delivered by neither, and ordered the reader into the half the page tells them to skip without saying
so. Part 2's manifest accounted for three of the six forcing functions it delivers, so a reader
concluded scope, domain and corpus-pinning were settled earlier. The paste-ready command said "begin
at step 1" where the agent's own slice supplies two different step ones.

UNPROVED CLAIMS. Three absolutes the page's own checklist requires be proved or weakened: every
forcing function called a record-keeping claim when two are not, a machine check said to report
exactly which cells changed where the page's own failure table says otherwise, and one hard
obligation where the page names another. Two sentences claimed page-level primacy against the BLUF's.
One passage said no body assesses you against ASVS while another describes the certifying
organizations that do.

VOCABULARY. The word "verified" carried the standard's name for `pass` and, in the next subsection,
the axis that cuts across every verdict -- two readings producing different numbers from one
instruction. A requirement ID was called a control ID in the section arguing that a requirement is
not a mechanism. The CI job carried two names inside one checklist. "Cell" is the page's most-used
term, 125 occurrences, and was never defined.

THE THREE RESIDUES from 5e2ef34 are closed. The `rule` field's domain is stated, so a `needs-review`
cell has something to record. The `line` field is described as never locating the token rather than
as inert, which is what the verifier's advisory read actually needs. Review row 5 checks all three
parts of an absence claim.

WHAT CHANGED. Thirty edits, each at the single wrong site rather than at the sites that were right.
Six were amended before landing because they collided across batches: two edits to the same paragraph
were merged, one fix coined a fifth name for the decision procedure, one removed a job name at one end
of the page while another added the same ambiguity at the other, and one wrote a fresh unproven
completeness claim into the page whose failure table ranks that defect first.

WHAT WAS DELIBERATELY NOT DONE. `verified_at` is not renamed. The name is published, entered the
pre-scoring checklist two commits ago, and the correction is made at the definition site instead --
this repository has recorded the same call for the same reason before. The Part 1 / Part 2 label
mismatch is left: dropping that vocabulary costs a second file, since HOUSE-STYLE.md pins that
section as the only marker that Part 1 ends. Standardising `grade` to `verdict` across thirteen sites
is left, since "grade" is also the page's verb. Four further items are recorded and left open: the
drift-check result still has no named owner, the definition of "cell" lands after forty prior uses,
three bare repo-relative paths survive in See also, and a `needs-review` cell's rule name is admitted
by the field's domain but never supplied.

MEASURED. Long sentences 219 -> 217 against a baseline of 219, inside the slack band, so the baseline
does not move. Fat cells 30 -> 30, at baseline. Words 61,422 -> 61,484. Zero doubled blank lines,
zero non-ASCII bytes, every internal anchor still resolving. 146 tests green, Word copy rebuilt with
pandoc 3.10.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
@wshallwshall
wshallwshall merged commit 9271c4c into main Aug 11, 2026
3 checks passed
@wshallwshall
wshallwshall deleted the claude/asvs-assessment-intro-b1f745 branch August 11, 2026 13:01
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant