Knowledge timestamp receipt · runnable
Pin the moment
the machine knew.
A disclosure clock starts when the machine knew, not when a person read the alert. Months later, nobody can reconstruct that instant from logs that anyone with access could have rewritten.
A knowledge timestamp receipt pins it while it is still true. Security teams, regulated issuers, and incident response teams get a signed, chain positioned record of the instant a named detector committed a detection artifact, with no human approval anywhere in the mint path.
Plain English
What your team actually gets.
You get a bound on the latest instant your system can be said to have held a detection. The detector build is digest pinned, the rule version is digest pinned, the time comes from a named external anchor with a declared drift bound, and the entry sits at a stated position in an append only hash chain. The clock stops being an argument and becomes a number you can hand to counsel.
The honest limit
It bounds the latest instant the machine knew. It cannot prove nobody knew earlier. Someone may have seen a signal before the detector fired, and this receipt has nothing to say about that. It fixes the timeline that your judgments get applied to, and it does not make those judgments.
Runnable examples
Press the button.
The verifier answers, live.
Each panel posts a real request body to https://thehiveryiq.com/v1/verify/knowledge-timestamp from your browser. Nothing is precomputed on this page. You see the HTTP status, the verdict, the failed gate when there is one, and the whole JSON response.
Read this before you trust anything below
These example receipts are signed with published demonstration keys. Their key ids all start with did:hive:example: and their seeds are public. Nothing here is secret.
Anyone can regenerate them. That is the point. It shows the API is doing real signature and gate work on the bytes you send, not handing back a canned answer.
Because the seeds are public, an example receipt is a demonstration and it is never evidence of a real event. The response says so itself, in the field key_trust: example_registry. Read that field on every result below.
The machine knew at this instant
Expect valid true. The mint happened inside its own declared latency bound, the emitter path has no human approval in it, and the chain position lines up with the prior entry.
Show the full request body
Minted 96 seconds late, past its own bound
Expect valid false with the failed gate MINT_LATENCY_BOUND. The receipt claims an instant, then gets signed well after the bound it declared for itself. A late mint cannot pin an early moment, so the gate rejects it.
Show the full request body
A human signed off, so it was not autonomous knowledge
Expect valid false with the failed gate AUTONOMOUS_EMITTER. A human approval sits in the mint path. That may be fine operationally, but it is no longer a record of what the machine knew on its own, so it cannot carry this claim.
Show the full request body
The canon contract
What the receipt proves,
and what it refuses to prove.
Both blocks below are copied word for word from the Hive canon registry entry for knowledge.timestamp. We do not soften them for a sales page.
Proves
This receipt attests only that a named detecting system, running a digest pinned software build and a digest pinned rule version, committed the digest of a detection artifact at an instant supplied by a named external time anchor with a declared drift bound, at a stated position in a named append only hash chained sequence, with no human approval in its mint path. It bounds the latest instant at which that system can later be said to have first held the committed artifact, and
Does not prove
it does not establish the earliest such instant. It does not attest that the detection was correct, that the committed artifact described a real condition, or that any condition existed at all, and it does not decide whether any response was reasonable, timely, adequate, or complete. It does not decide whether any materiality, significance, or de minimis assessment was right, it makes no such assessment, and it does not determine that any reporting obligation applies, that any deadline was met or missed, or that any rule, regulation, contract, or duty was complied with or breached. It does not identify any affected system, person, account, or asset, it does not disclose the content of the committed artifact, it does not authorise, require, or excuse any notification, escalation, disclosure, remediation, or enforcement action, and it fixes the timeline to which those judgments are applied and nothing more.
Verbatim from canon/registry/hive-canon-registry.json, anchor knowledge-timestamp
For engineers
The route, the auth, and the schema.
Verify is open and unauthenticated, so it is the fastest honest check you can run. Mint requires a bearer token and fails closed with 401 when the token is missing or wrong.
# no credentials needed. swap in any receipt of this type curl -sS -X POST https://thehiveryiq.com/v1/verify/knowledge-timestamp \ -H 'content-type: application/json' \ -d '{"receipt": RECEIPT_JSON }' # mint needs a bearer token and fails closed without one curl -sS -X POST https://thehiveryiq.com/v1/mint/knowledge/timestamp \ -H 'content-type: application/json' \ -H "authorization: Bearer $HIVE_TYPED_MINT_TOKEN" \ -d '{"receipt": RECEIPT_JSON }'
Schema for this type is published at https://thehiveryiq.com/.well-known/schemas/knowledge-timestamp-v1.json.