Evidence

What changed since a signed week

?since={week} names a week already in the chain; the answer compares it to the latest signed snapshot: doors appeared and disappeared, verdict transitions, and drift in a door's own declared terms (price bounds, rails, schemes). A week the chain does not hold gets a 404 naming the weeks it does — no invented baselines; no week at all gets a 400 naming them too. The cheapest agent loop is polling this. Free.

get/corpus/diff.json

Request

  • Base URL: https://scvd.store
  • URL: https://scvd.store/corpus/diff.json
  • Auth: none required

Query parameters

sincestring required

The baseline: an ISO week the chain holds a signed snapshot for. The comparison is always against the latest snapshot. Omit it and the answer is a 400 listing the weeks the chain holds.

Headers

If-None-Matchstring

Send a prior ETag (SHA-256 of exact response bytes). Unchanged content returns 304 with no body.

Response

OK

fromobject required

The baseline snapshot, with its sequence and digest.

toobject required

The latest signed snapshot.

appearedobject[] required

Doors present in the later week and not the earlier one.

disappearedobject[] required

Doors present in the earlier week and not the later one. An absence, never a verdict about the operator.

transitionsobject[] required

Doors whose verdict moved between the two weeks.

driftobject
hosts_in_frominteger
hosts_in_tointeger
hosts_in_bothinteger
how_to_rederivestring

Which two snapshots to fetch and how to recompute this diff yourself, so the surface is checkable rather than trusted.

Changes

No recorded changes to this operation across all 1 revision of this API.