ditzl builds and hosts a page for a place of business. The page is not a document somebody wrote and uploaded. It is assembled at request time out of rows in a database, each row naming a block of code and the data that fills it. Change a row and the page changes. There is no build step and nothing is cached between you and the database.
Every decision that shapes this platform is written to an append-only log called the tree, one entry per fact. An entry is called a leaf. Leaves are never edited and never deleted - a leaf that turns out to be wrong is superseded by a later leaf that says so and points back at it, so the mistake and the correction are both permanently readable.
You can read any of it without an account at /.well-known/tree.
Yes, and that is the point of it. Each leaf is addressed by a hash of its own contents: sha256(serialize(canonicalJSON(blob)) + parent). Fetch a leaf at /.well-known/tree?hash=<hash>, recompute that digest over what came back, and compare. If the two do not match, the record is lying to you, and you found that out using nothing but the public response and a sha256 implementation.
The same applies to the code that renders a page. Every block carries a canon hash over its own template. The full vocabulary of blocks is published at /.well-known/blocks.
Some facts are attested by a person rather than measured by a machine. When that happens, the statement is signed through Google, and the signature is bound to the exact words attested - the nonce Google signs is a digest of the statement itself, and of the coordinates too when a location is part of the claim. A signature therefore cannot be lifted off one sentence and reattached to another, or off one place and dropped on another.
What it proves is narrow and worth stating plainly: that a specific Google account asserted those specific words at that time. It does not prove the words are true.
Nothing on this platform publishes itself. A page is built in an unsealed state, tuned, and only becomes public when a human marks it so - and that is true of pages the operator builds for himself, which is where the rule came from.
Writes to the tree refuse anonymous callers. You can verify that refusal yourself: POST to /api/tree/leaf or /api/tree/attest with no credentials and you will get a 401.
Some pages on this platform describe places that never asked for one. Where that is so, the page is built from public information and is marked as a recommendation rather than as anything the business itself said.
To be direct about the current state rather than describe an intention: the mechanism for a business to record its own consent exists in the schema and is not yet wired to anything a business can press. Until it is, no page here should be read as endorsed by its subject. If a page describes your business and you want it changed or taken down, write to the address in the footer and it will be done.