SRC-2026-077

J. B. Rietstap — Armorial Général Vol. 2 (Gouda 1884), the Rens- alphabetical neighbourhood read at the page (leaves 564–566 = printed pages 550–552): NO entry under Rensburg / van Rensburg / Rensburgh / Rendsburg / Rensberg. The run goes Rens (Dordrecht) · Rens (Malines) · Rensen (van) · Rensing · Rensonnet · Rensselaer (van) · then the Rent- names; the position where Rensburg would stand is on printed page 552 and is empty. ABSENT-AT-THE-PAGE, page-verified, control passing in the same run (Lombard → leaf 106). ONE VECTOR ONLY — deliberately not promoted as a negative claim: §6b requires a second vector differing in kind, and none is reachable on the shelf today (Pama 1972 measured 403-restricted at I18)

Tier
T2-primary (canonical armorial at primary-source citation depth; page images preserved and READ by eye — a page-verified ABSENCE, the tier carried inside the finding per §6b rule 3)
Received
2026-08-25
Carrier
R1 — Consulted through the record's armorial-lane instrument (`60_research/sources/_armorial.py`), capability control passing in the same run (Lombard → 5 hits, all at the pinned leaf 106). Seven searches across both volumes (Rensburg · Rensburgh · Rendsburg · Rensberg at v2; Rensburg · Rendsburg · Rensberg at v1 — full-text reaches compound filings regardless of filing letter); neighbourhood located by bracketing searches (Renesse → leaves 564–565); three leaves pulled and read
Families
vanrensburg
Gap it serves
QUEUED_INSIGHT_ATLAS §11.13 van Rensburg (founded as a pointer at this engagement); the armory build-out I19; resolves the LEAD recorded at §11.10's wave-35 ruling ('Rietstap returned zero for Rensburg — a lead, not a finding, until the page image of the neighbourhood has been read')
In the store
3 page image(s) · 0 original(s)

Chain of custody

  1. origin: J. B. Rietstap, Armorial Général, 2nd ed. Vol. 2 (L–Z), Gouda 1884; public domain by age. Internet Archive item `armorialgnra02rietuoft` — the same copy the record's Lombard and Théron engagements read (SRC-2026-018 / 020 / 066)
  2. method: Search by instrument at seven term/volume pairs, bracketing searches to locate the neighbourhood, then three page images pulled and read by eye. THE ROUTE IS PART OF THE CUSTODY: the IIIF image service was down (500/504 on every item including the proven control pull), so the images came through the BookReader endpoint on the item's own d1 node (ia601604.us.archive.org) — the lane's two-route pull built at I18, the route printed at pull time
  3. intermediary: Three JPEG page images preserved at file-register with sha256: riet2-rens-leaf-0564.jpg (page 550, Renard→Renesse) eef630398d3ca583…; riet2-rens-leaf-0565.jpg (page 551, Renesse→Renner) 509a4a310e35dc8b…; riet2-rens-leaf-0566.jpg (page 552, Renner→Rentz, the Rens- run) 77af89965dd73552…

The engagement record for this source (what was read, by whom, what it settled and what it left open) is kept in the record's repository as SRC-2026-077/source.md; this page carries what the register states about the source. All sources.