Open standard · GOVP-1

Make evidence outlive the system.

GOVP turns claims, processes and decisions into evidence that others can preserve, corroborate and verify independently. No account. No proprietary verifier. No need to trust Gemacode.

Specification, conformance vectors and reference implementations are public.

GOVP-1public record format
Ed25519domain-separated signatures
Offlineindependent verification
Cross-languagebyte-exact conformance
Openno vendor dependency
01 / The problem

The web remembers badly.

Databases are rewritten. CMS pages change. Screenshots are made by interested parties. Even an honest organization cannot prove that today’s record is the one that existed years ago.

Could your organization prove today exactly what it published two years ago?

GOVP does not repair honesty. It repairs demonstrability: what was asserted, by whom, against which artifact, and what independent observers saw.

02 / A real three-node test

When one node lies, the others retain the contradiction.

The GOVP plugin includes a reproducible test using three real WordPress instances over HTTP. Each node generates its own key and accepts the same signed manifest. Node C is then given a different view for the same epoch.

  • Initial state. A, B and C announce the same signed head: two agreements, no alarm.
  • Split view. C announces another hash at the same epoch. A identifies C and retains both signed statements.
  • Node down. B disconnects. A continues reconciling with C without relying on a central server.
  • What this proves. Agreement, attributable contradiction and tolerance of absence—not that the original content is true.
03 / What becomes verifiable

One protocol. Different evidence.

GOVP protects more than documents. Profiles define how to make each kind of claim, process or decision reproducible and honestly bounded.

Public integrity

What an organization said — and when it changed.

Policies, tariffs, certifications, product claims and public histories become independently checkable instead of self-custodied.

Decision integrity

The rules existed before the outcome.

Commit the mechanism first, preserve the inputs and let anyone recompute the result — from game mechanics to scoring systems.

Process integrity

Who approved, reviewed or observed each step.

Consent, editorial review, quality control and audit trails become a chain of attributable acts instead of a final PDF.

Measurement & data integrity

Inputs, method and result stay connected.

Measurements, clinical sessions, datasets and model releases preserve provenance and can be checked against the declared method.

05 / Honest boundary

Integrity is not truth.

A protocol becomes credible when it states what it cannot prove. GOVP reduces measurable doubt; it does not manufacture certainty.

GOVP can prove

  • The exact bytes bound to a record.
  • Which technical identity signed it.
  • Whether the record or artifact changed.
  • What independent observers signed that they saw.
  • Whether declared rules reproduce a result.

GOVP does not prove

  • That the content was true, fair or legal.
  • Physical authenticity without an independent bridge.
  • Independence where no genuine third parties exist.
  • Every intermediate state that was never recorded.
  • An external time unless a time anchor is present.
06 / Open by construction

Do not take our word for it.

The specification, vectors and reference CLI are under private validation before final publication. A valid GOVP record must remain verifiable even if Gemacode, its servers and its products disappear.

Start with evidence

Publish something others can verify.