A selected automated action can carry a receipt outside the operator's system

Try a receipt and test a changed copy.

Issue a record, change a copy, and compare the results. You can also open the verification link on another device. No account is required.

The buttons below call Hive's receipt and witness services. Their responses show what was returned for this test; the witness service is not an independent operator.

Live record, this tab

Each square is one bit of the fingerprint recorded in this Hive-operated demo. Press 1 fills them in from a real demo record.

Receipt: not issued yet
Witness record: waiting
Verdict: not checked

The panel updates after each action. Service calls send the data needed for that action; review the site’s privacy information before submitting content.

Run the four checks

Issue a record, edit it, and ask the log whether it matches. You can also open the public check in another browser. This does not demonstrate a second physical device, disconnected cold start, recovery, or independent custody.

Scroll sideways to see all four

Press 1Issue a receiptA demo action is receipted and recorded in the Hive-operated witness log.

Press 2Now change itYou rewrite the record after the fact.

Press 3Check itThe log answers in one word.

Press 4Another browserOpen the same public receipt check.

Scripts are blockedWhat each step doesYour browser is not running the interactive version, which is a reasonable setting on managed hardware. Here is exactly what it does, and the verifier at the bottom of this page works without scripts.

Receipt an action.

A sample programmatic action is receipted against a Hive-operated demo witness service. The record comes back with an identifier, a fingerprint of the content, a timestamp, and a log status.

action     Automated system generated a summary report.
receipt    r_brf_1788459421_2f689f41887fd105
fingerprint 3633905482c7c963…
witness    recorded

Now change it.

The action description reappears in an editable field and you rewrite it. Nothing stops you. That is the point of the next step.

Automated system approved a payment.

Check it.

The fingerprint of the edited content is recomputed and compared against the retained record. The answer is one of two words.

MISMATCH. This content does not match the retained receipt.
The retained record did not move. Yours did.

Open the check in another browser.

A link and matching code point to the public check for the receipt you just made. This is a hosted lookup. It does not demonstrate physical-device independence, disconnected cold start, or recovery.

You can run the whole sequence right here without scripts. This form issues a real receipt and hands you the identifier, the link, and the code. Action to receipt

How to read the results

What a receipt is

When Hive is integrated with a selected automated action, it can issue a record of configured fields such as action type, time, and stated authority. A hash-only or customer-side profile can keep plaintext outside Hive. A hosted profile may process the fields sent to it. The accepted data map controls what crosses the boundary, what is retained, and which verifier materials apply.

The records this page issues are public demo records whose text is intentionally stored so anyone can run the demonstration. Do not infer a customer retention or privacy commitment from this demo.

Where it lives

This demonstration records receipts in a separately keyed, Hive-operated witness log. A later content change can produce a mismatch against the retained receipt. That is technical separation, not organizational independence. Outside operation requires a non-Hive party to control the key, observation path, log custody, and administration.

When a separately retained record helps

A reviewer may need to detect whether content changed after a receipt was issued. That check is stronger when the reviewer has the exact receipt, trusted keys, verifier, and any required checkpoint. It becomes organizationally independent only when a non-Hive operator controls the relevant custody and administration.

What we do not claim

We do not claim a record is truth. An operator can forge a payload, and we say so out loud.

A valid check can show that later content differs from the bytes bound into a supported receipt. It cannot show that the original assertion was honest, complete, lawful, delivered, accepted, or settled.

Claim boundary, stated on the page rather than in a footnote.

Why it matters for disclosure law

Some disclosure and oversight regimes require organizations to retain or produce records about automated systems. The applicable duty depends on the jurisdiction, industry, workflow, and facts.

A technology-neutral control can require selected automated actions and their stated authority to be recorded in a form that an authorized reviewer can check. The legal requirement and evidentiary weight must be evaluated for the specific deployment.

A one-page sketch of that language is available by reply. It fits in an oversight letter, a marker bill, or a moving vehicle.

Verify a supported receipt without an account.

The public verifier is available without an account for its supported formats. Hosted access and local signature verification have different requirements; the continuity information explains what to retain for offline checks.

This runs as a plain form submission with no scripts involved. It opens the record and asks for the text you want checked against it.

No accountThe public check does not require an account.

No paywallPublic verification is free. The continuity package explains what to retain for offline checking if Hive is unavailable.

No relationshipYou do not need a commercial relationship with Hive to use the public verifier.

The retained record did not move. Yours did.

Steve, founder: [email protected]. Replies get the one-page language sketch the same day.