Proof of Human.

Loading records…

How sealingworks.

Sealing is designed to work like this: every hour, a fingerprint of all decisions completed in that hour is published outside HumanAgent, where we don't control it. If any record were altered afterwards, the fingerprint would no longer match what was published, and anyone could check that.

One fingerprint covers hundreds of records, which is why it is hourly rather than per decision. The hourly external anchoring is not live yet: every record already carries its audit hash and can be verified at /verify, and the sealed date will appear once the external batch is running.

Records created before sealing was introduced carry a single catch-up seal batch date. Those show a gap between their reviewed date and their sealed date. That gap is visible on purpose — hiding it would defeat the point.

Cogacha verifies it's a human.HumanAgent verifies which human.

What this fingerprint covers.

The record ID is a SHA-256 fingerprint of the decision's canonical fields. Recompute the SHA-256 of these fields joined in this order and you get the record ID above.

use_case | sector | reviewer_id | credential_type |
license_state | decision | reviewed_at | intake_ref

More from this sector.

Verify aProof of Human.

Paste a record ID and check it against the published seal.