Held record · the gray record, contested

A held record — contested

What is contested

Held as contested. The archive holds this passage and this attestation and does not assert the name they are filed under. The archive's test for a vernacular name asks whether the asserted name stands beside the verb that would be naming it — English puts a name against its naming construction, as in “Boston was called Shawmut” and, inverted, “it was ordered that Trimountain be called Boston”. In the passage quoted from Francis S. Drake, The Town of Roxbury: Its Memorable Persons and Places the words “the Neck” and a naming verb both appear and do not stand together, so the test cannot show that this passage gives “the Neck” as a name of Boston Neck. WHAT IS WRONG HERE IS THE TEST, NOT THE EVIDENCE, AND THE ARCHIVE SAYS SO PLAINLY. Read the passage: it is a genuine naming construction. It names Boston Neck as the Neck and a reader can see that it does. It fails only because the archive's test requires the name within twenty-five characters before its verb, and here the name stands further off than that. The window is that narrow for a reason — a wider one re-admits “a town-meeting was called, June 9”, where nothing is being named at all — so it is not widened for the sake of one record that a human eye happens to like. Publishing on an eyeball where the mechanism cannot see is the drift this standard exists to prevent, and an archive that overrides its own instrument case by case has no instrument. THIS RECORD AWAITS A WIDER WINDOW: it is resolved when the archive measures a better rule against its whole corpus and this passage passes it, which is a later act of curation and not a defect in the source. Meanwhile the disposition is neither of the two the archive had. Publishing would assert a place-name the evidence does not settle, which is a fabrication carrying a citation. Withdrawing would throw away real evidence for being untidy, which is the one thing an archive of the gray record must not do. So it is kept, marked contested, printed here whole with its passage and its attestation, and excluded from the archive's composed answers, from the corpus its retrieval surface draws on, and from every structured assertion it emits — so that no machine can quote it as settled while it is unsettled.

A held record is not a withdrawal. Nothing here says the archive found the evidence wanting. It says the archive has not settled what the evidence carries, and will not assert a name on it until something does. The record is excluded from the archive’s composed answers and from the corpus its retrieval surface draws on, and its structured data carries no assertion at all — so no machine reading this page can quote the name as settled. It resolves at the address it has always had, keeps its identifier and its provenance, and will be published or withdrawn on evidence the day a cleaner source names the place unambiguously.

The record, as the archive holds it

The reading in dispute, which the archive does not assert and prints here so it can be weighed against the passage below:

The archive holds the passage and the attestation. It does not hold that the passage carries this name, and does not say so anywhere a machine can read.

Subject

Boston Neck

Predicate

vernacular_name

Attested by

Francis S. Drake, The Town of Roxbury: Its Memorable Persons and Places

Attestor kind

scholar

Attested since, as stated

1905

Attestation strength

attested — a count of independent attestations, never a truth value

Variant note

The isthmus, as Bostonians said it.

Evidence

Identity

Identifier

urn:lemay:boston:claim:boston-neck-vernacular-name-the-neck-the-town-of-roxbury-its-memo

Canonical URL

https://boston.fyi/claim/boston-neck-vernacular-name-the-neck-the-town-of-roxbury-its-memo

As JSON

https://boston.fyi/claim/boston-neck-vernacular-name-the-neck-the-town-of-roxbury-its-memo.json

Version

3 · last changed 13 September 2026

Status

HELD — CONTESTED. Held as contested. The archive holds this passage and this attestation and does not assert the name they are filed under. The archive's test for a vernacular name asks whether the asserted name stands beside the verb that would be naming it — English puts a name against its naming construction, as in “Boston was called Shawmut” and, inverted, “it was ordered that Trimountain be called Boston”. In the passage quoted from Francis S. Drake, The Town of Roxbury: Its Memorable Persons and Places the words “the Neck” and a naming verb both appear and do not stand together, so the test cannot show that this passage gives “the Neck” as a name of Boston Neck. WHAT IS WRONG HERE IS THE TEST, NOT THE EVIDENCE, AND THE ARCHIVE SAYS SO PLAINLY. Read the passage: it is a genuine naming construction. It names Boston Neck as the Neck and a reader can see that it does. It fails only because the archive's test requires the name within twenty-five characters before its verb, and here the name stands further off than that. The window is that narrow for a reason — a wider one re-admits “a town-meeting was called, June 9”, where nothing is being named at all — so it is not widened for the sake of one record that a human eye happens to like. Publishing on an eyeball where the mechanism cannot see is the drift this standard exists to prevent, and an archive that overrides its own instrument case by case has no instrument. THIS RECORD AWAITS A WIDER WINDOW: it is resolved when the archive measures a better rule against its whole corpus and this passage passes it, which is a later act of curation and not a defect in the source. Meanwhile the disposition is neither of the two the archive had. Publishing would assert a place-name the evidence does not settle, which is a fabrication carrying a citation. Withdrawing would throw away real evidence for being untidy, which is the one thing an archive of the gray record must not do. So it is kept, marked contested, printed here whole with its passage and its attestation, and excluded from the archive's composed answers, from the corpus its retrieval surface draws on, and from every structured assertion it emits — so that no machine can quote it as settled while it is unsettled.