GOVP
Source
GOVP 0.1.11

Status, revocation and key rotation

GOVP-STATUS-1 adds a fail-closed, same-origin HTTPS decision about active keys and revoked records without changing GOVP-1.

Separate result. Core validity remains an offline cryptographic fact. currently_trusted is produced only after live canonical HTTPS retrieval of both record and status.

Public endpoint

https://govp.io/.well-known/govp/revoked.json

The discovery index references the status endpoint. Its response is public, CORS-enabled and sent with Cache-Control: no-store. GOVP.io stamps generated_at when each GET or HEAD request is served, rather than reusing the date of a deployed static file.

Evaluate it

govp status-url https://govp.io/.well-known/govp.txt \
  --status-url https://govp.io/.well-known/govp/revoked.json --json

A true result requires a core-valid canonically fetched record, a valid and fresh status document from the same origin, an active matching key and no explicit record revocation. Reference verifiers accept a status generated no more than 300 seconds ago and no more than 60 seconds in the future. Offline evaluation exposes snapshot_valid but never claims current trust; snapshot_trusted remains a deprecated compatibility alias.

Machine-readable contract

Trust boundary

The authority is the current HTTPS origin, not the record signing key: a compromised signing key cannot safely revoke itself. Freshness bounds limit replay of a previously valid status response but are not an independent timestamp. Deployments that need a stronger independent anchor can add DNSSEC, transparency, PKI or an external status signer.