Verify this page

Ledger entry for the Autoposter landing page

Autoposter's argument is that a claim is worth what its evidence is worth. That applies to this site before it applies to anyone else's, so the hash in the corner of the landing page is a real digest of the copy you are reading — not a decorative string.

sha2568c482cad468d96eb25fea960ebf287c827e193a30e7389f525aa3656d5a3919e
short8c48…919e
covers/ (landing page rendered copy)
approverIng. Florian Zeba LL.B.
entitySOFTWERK GmbH
methodsha256 of visible text, hash stamps excluded
status● signed

Reproduce it yourself

The digest covers the landing page's rendered copy — every visible text node, whitespace collapsed — with the hash stamps themselves removed. They are excluded for the obvious reason: a hash cannot cover a document that contains it.

  1. Load the landing page and take its rendered text, in document order.
  2. Drop the text of the .hashstamp and .hashline elements.
  3. Collapse each run of whitespace to a single space and trim each line.
  4. Join the lines with newlines and take the SHA-256 of the UTF-8 bytes.

That is exactly what scripts/sign-page.mjs does at build time. Change one word of the copy and the digest changes, which is the entire point.

What this is not, yet

This is a single entry, not the product. There is no hash chain across versions here, no append-only database, no C2PA manifest, and no second reviewer — those are what Autoposter is being built to provide, and claiming them now would be the exact failure the product exists to prevent.

What this entry does establish: a named human at a named legal entity approved this copy, and you can check that the copy has not changed since.