Overlay hygiene in this onion house listing

An edition plate is already an overlay

The catalog, the captures, and the three dated strings are documentary layers. They can be wrong. They can be incomplete. They can be copied. A prior PGP-signed document from a key you trusted before this visit is a different class of object. If it disagrees, keep the signature.

Search rank is another overlay. So is a helper. So is a screenshot on a forum. Stacking overlays does not become a signature. It becomes a smear. See gutter and run weather.

This host names itself as an overlay in the notices beside onion rows. That sentence is load-bearing. Skipping it is how a listing becomes a fake trust anchor. See each market child under editions.

A layer sits on top of a key without being the key. This clearnet site, a search snippet, a capture, and a cited string are all layers. Stacking them does not become a signature. It becomes a smear. See gutter.

If a prior PGP-signed document disagrees with anything here, keep the signature. Rank, chrome, and a padlock do not outrank that document. This host can be wrong. That is why it calls itself a layer.

A print run delivered over HTTPS is still a layer

Transport security is worth having. It is also easy to misunderstand. This onion house uses HTTPS so the research paper is harder to tamper with in transit. It does not inherit the authenticity of any onion name it cites. Mixing those facts is the mix-up this sheet exists to stop.

A lookalike can also use HTTPS. A padlock on a clone is still a padlock on a clone. Compare strings to a signed source, not to a certificate on a white page. See registration.

Client provenance is packing under the overlay, not a property of the overlay. See tympan. Habitat differences stay on the door child.

Transport security is worth having and easy to misunderstand. HTTPS makes this paper harder to tamper with in transit. A lookalike can also use HTTPS. Compare strings to a signed source, not to a certificate on a white page. See registration.

Impression notes on overlays that must lose

When evidence classes conflict, the signed note wins, then the dated hedge, then the capture as HTML, then the snippet as weather. Conversion copy that reverses that order is marking itself. See proof and forme.

Harm context is not an overlay on a product. It is public-health language that belongs on the job. It still does not authenticate a name. See harm notes.

Return to colophon if you needed who typesets the layer. Stay here if you needed the padlock named as transport, not as a seal on a paste.

When evidence classes conflict, the signed note wins, then the dated hedge, then the capture as HTML, then the snippet as weather. Conversion copy that reverses that order is marking itself. Harm context still does not authenticate a name. See proof.

Questions this sheet files in the chase

Does HTTPS on an edition plate sign the onion strings?

No. It protects delivery of this archive page. Cited v3 names remain unverified overlays until a prior signed note says otherwise.

Is this host a print run that should be treated as a trust anchor?

No. It is a clearnet layer. Rank, chrome, and a padlock do not authenticate a hidden-service key.

What do impression notes do when overlays disagree?

Keep the signed source. Then the dated hedge. Then the capture as HTML. Snippets come last. Conversion copy that reverses the order is a mark against the page.