Open infrastructures · GOVP · Atlas · BiologicalSecure— evidence that stays verifiableGemacode Research · Bilbao
GemacodeResearch Contact
Protocol · public system

GOVP

Gemacode Open Validation Protocol is an open protocol for generating, preserving and independently verifying operational evidence records.

What it answers

Can this operational declaration be verified independently, without relying on the issuer or its internal database?

What it does not answer

GOVP does not prove that the declaration was true when issued. It proves whether the record presented later remains unchanged.

Generate.
Preserve.
Verify.

GOVP is the base verification layer for public Gemacode systems, including BiologicalSecure records.

01 / the artifact

Anatomy of a record

A GOVP record is a small, signed, self-describing object. It binds a statement to an issuer and a domain, so the record cannot be lifted, re-hosted or silently altered.

record.govp.txtEd25519 · GOVP::record.v1
# operational evidence record statement : "Lot 24-A881 inspected; tolerance within spec" canonical : https://example.org/.well-known/govp.txt generated-at : 2026-05-18T09:41:22Z asset-sha256 : 9f2c…e7b1 govp-id : GOVP-7K3…Q2 signature : ed25519:5b9a…0c4f
● PASSsignature valid · domain bound · asset hash matches

Signing input is alphabetically sorted under domain separator GOVP::record.v1, base64-encoded and signed with Ed25519. The canonical field binds the record to its issuing domain.

02 / why

Why it exists

Organizations already know how to store records. The problem is proving that a record presented today is exactly the same record that existed years ago — to an auditor, a regulator or a court that does not trust your database.

03 / threat model

Honest time-anchoring

A bare record's timestamp is issuer-asserted.

By itself, generated-at is a claim by the issuer; a determined issuer could backdate a bare record. GOVP states this openly. Independent time-anchoring — RFC 3161, an eIDAS qualified timestamp, or a transparency log — is offered as an optional layer. Only the anchor, not the bare record, prevents backdating.

How Gemacode works

Built to be checked, not believed

The same commitments stand behind every public system — that is what makes them an infrastructure rather than a set of claims.

Independent verification

Every public record can be checked by a third party, without relying on Gemacode or its servers.

Referenced & evidence-graded

Claims carry sources and evidence levels. Absence of identified evidence is reported as absence — never as approval.

Open, no vendor lock-in

Open protocols and an open verification model, so the ability to verify outlives any single vendor.

04 / ecosystem

An open standard, on every platform

GOVP is not a single app. It is an open protocol with a public specification, cross-language test vectors and implementations that can be independently inspected and verified.

05 / live

Verify a record yourself

The GOVP verifier runs the full check — including the Ed25519 signature — entirely in your browser. Nothing is uploaded. Load a sample, verify it, then change one character and watch it fail.

The verifier and the full GOVP protocol site live under /govp/ — spec, platforms, use cases and the trust model.