Antonio Piaggio's 1753 unrolling machine bridges to the vault's 'founding practitioner is not an inventor' MOC as an analytical contrast — same diagnostic question, inverted answer

herculaneumantonio-piaggiokarl-richard-lepsiusattribution-and-origin-mythsfounding-practitionervault-bridgecross-time-bridgebridge-investigationanalytical-contrasthistory-of-technology

A vault_bridge probe on the Piaggio hook returned bridge_candidate: true against moc-a-founding-practitioner-is-not-an-inventor, the Lepsius/squeeze-method cluster, as an unlinked pair. Both clusters pose the identical diagnostic question of a credited "founder": was this figure the technique's inventor, or an adopter of something already established elsewhere? The MOC's argument is that Lepsius was Egyptology's founding large-scale user of the epigraphic squeeze, not its inventor — he learned a method already roughly 150 years old in Mediterranean epigraphy on a four-year tour of European collections before applying it at expedition scale (claim-squeeze-technique-predates-lepsius-learned-not-invented).

Piaggio answers the same question the opposite way. No older workable unrolling method existed anywhere for him to adopt — only what CISPE calls "various unprofitable and destructive attempts" at the carbonized Herculaneum scrolls — though the invention's scope is narrower than this note first stated: the machine was the first durably workable method, itself still "rather destructive" per the claim-note's own Wikipedia quote, not a non-destructive one. Where the Lepsius cluster's record (including the founder's own 1842 memorandum calling the squeeze method "still almost unknown") disproves the invention reading, the record on Piaggio supports it within that corrected scope: the machine is credited to him alone, with nothing workable older to learn from — invented, not adopted.

The bridge is therefore real at the level of the shared diagnostic question — both are "credited founder: inventor or adopter?" cases — and a genuine counter-case at the level of the answer. This is the sharper, more useful outcome of the two a vault_bridge hit can produce: not an extension of the vault's standing myth-correction pattern, but a documented instance of the same test failing to find a myth, because in this case there wasn't one.