datelock

Evidence has a date.

01

as_of retrieval

Every search is evaluated at an explicit historical cutoff. A unit is eligible only when its stored publication evidence is in force on or before as_of. A bare year means the final day of that year. Later material cannot leak backward into the result.

02

What a receipt contains

A receipt records the pack and inputs needed to inspect a result: content_hash, as_of, language, selected unit_ids, and verification detail. Current receipts carry meta with retrieval size, a query hash, and the exact impl identity. The public verifier displays the pack hash and implementation verbatim.

03

The certification boundary

Only verify=PASS is certified. Retrieval rank is not a truth score. An issued receipt proves that the service recorded those bytes; it does not make a failed, unknown, mismatched, or stale-pack result certified. The verification page labels a result certified only when the replay API returns verified.

04

Connect an MCP client

Use the remote server endpoint. Replace the placeholder with a key issued to you; never put a key in browser code.

{
  "mcpServers": {
    "datelock": {
      "type": "http",
      "url": "https://staging-api.datelock.dev/mcp",
      "headers": {
        "Authorization": "Bearer YOUR_DATELOCK_API_KEY"
      }
    }
  }
}

The browser verifier does not call /mcp and does not contain an API key.