Security

The active Ed25519 key below comes from the same authoritative registry as the public endpoint.

Registry URL

/.well-known/govidence-keys.json

Active key ID

ed1

SHA-256 public key fingerprint

sha256:ae70526168b49de8fa5f5fb075d300f07f49c1b3f624109b7c718295b45fa51f

Verification can run offline using a supplied public key. Confirm its fingerprint through an independent channel before trusting it. The registry is served by GoVidence itself.

The standalone Node.js offline verifier is available from Compliance and Documentation. It uses a Verification Package and a locally supplied public key registry.

A valid signature establishes that the verified content matches the content signed by the corresponding private key, assuming the public key is authentic and trusted.

A signature alone does not prove:

• the agent actually performed the action;
• the data is true or complete;
• no trace was omitted;
• independent time attestation;
• legal or regulatory compliance;
• that the signing key was never compromised.

Fictional example. No real data.

{
  "package_format": "govidence.verification-package.v1",
  "trace_id": "fictional_trace_example",
  "agent_id": "fictional_agent_example",
  "action_type": "llm.completion",
  "decision": "ALLOWED",
  "signature": {
    "alg": "Ed25519",
    "key_id": "FICTIONAL_KEY_NOT_IN_REGISTRY",
    "value": "PLACEHOLDER_NOT_A_REAL_SIGNATURE"
  }
}

The decision is a recorded preview value, not evidence that GoVidence allowed or blocked an action.

• Policy decisions are recorded, not enforced by GoVidence.
• Client-side redaction is your responsibility. GoVidence also applies pattern-based redaction on the server as a safety net; this is not an exhaustive check. Input and output are stored after any applicable redaction; they do not currently have separate per-field fingerprints.
• In the application, signed evidence is not deleted automatically, and plan history windows are not applied during the pilot. Retention, backups and deletion at the hosting-provider and infrastructure level are not covered by this statement.
• Policy change history identifies the account, not individual users.
• UNVERIFIABLE means the trace cannot be verified (unknown format or missing key). It does not mean it was altered.
• Historical and demo traces may not carry an Ed25519 signature; an HMAC integrity code is a shared-secret mechanism and is not publicly verifiable.

Client-side redaction is your responsibility. GoVidence also applies pattern-based redaction as a server-side safety net; it is not an exhaustive check for personal information.