Certificate and live status
A signed PDF proves that a document has not been altered. It does not prove that what the document says is still true. For a fact with a short half-life — this animal is alive, this animal is unencumbered — a document that travels on its own becomes a bearer instrument for a claim that expired days ago. So the certificate is a snapshot, and the endpoint it points at is the authority.
Certificate of registration
This certificate carries no personal information about the owner.
Live status, read just now
GET /v1/certificates/{cert_id}/status — public, unauthenticated,
no personal information. Anyone holding the certificate can check it; nobody needs an
account, and nobody learns who the farmer is.
Now change the underlying fact
Record a death against the animal. Nothing about the certificate document changes — no new PDF is issued, no signature is invalidated. Only the register changes, and the status endpoint tells the truth on the next read.
Then refresh: the status flips to animal_deceased, driven by the event stream
rather than by anyone editing the certificate.