◇ Open Values Standardfor builders

Spec / open-values-attestation

Open Values Attestation v0.1

A public record of one person's response to a proposal: support, concern, needs work, oppose or abstain, with a comment. Attestations live inside the governance ledger at content/governance/proposals.json; the current ones are examples and none of them count.

Draft. It may still change before it is called stable. A file someone writes by hand or with a tool, and keeps.

Who writes it and who reads it

Written by pipeline/build_proposals.js. Read by governance ledger, generated governance index, future dumb relays.

Fields

FieldWhat it meansType
format requiredAlways "open-values-attestation". Tells a reader which Open Values format this is.always "open-values-attestation"
version requiredThe version of the attestation format this record follows. Must start with 0.1.0.string
id requiredA unique name for this attestation, in lowercase letters, numbers and hyphens.see slug
status requiredWhere the attestation stands: template (an example), submitted, withdrawn, or archived.one of "template", "submitted", "withdrawn", "archived"
proposal requiredThe id of the proposal this attestation responds to.see slug
stance requiredThe position taken on the proposal: support, concern, needs-work, oppose, or abstain.one of "support", "concern", "needs-work", "oppose", "abstain"
attester requiredWho made the attestation.see actor
created requiredThe date the attestation was made, as YYYY-MM-DD.see date
publicComment requiredWhat the attester wants to say about the proposal, published with the record.see nonEmptyString
signature requiredHow the attestation was signed and whether that signature has been checked.see signature
counted requiredWhether this attestation counts towards a result. It may be true only when the ledger's counting conditions all hold; every seed record has false.boolean
privacy requiredA sentence saying what private details the record leaves out, such as "Template record; contains no private contact details."see nonEmptyString

A reader MUST ignore fields it does not know, so a file can carry more than this list and still be read. A writer MUST NOT change what a listed field means.

A file that passes

An attestation names a proposal, stance, attester, public comment, signature metadata, and counted flag.

{
  "format": "open-values-attestation",
  "version": "0.1.0",
  "id": "attestation-example",
  "status": "template",
  "proposal": "proposal-example",
  "stance": "support",
  "attester": {
    "type": "pseudonymous",
    "id": "example-attester",
    "display": "Example attester"
  },
  "created": "2026-07-08",
  "publicComment": "This is a non-counted template support record.",
  "signature": {
    "method": "none-template",
    "verified": false
  },
  "counted": false,
  "privacy": "Contains no private contact details."
}

A file that must be rejected

Attestations must explicitly say whether they count.

{
  "format": "open-values-attestation",
  "version": "0.1.0",
  "id": "attestation-example",
  "status": "template",
  "proposal": "proposal-example",
  "stance": "support",
  "attester": {
    "type": "pseudonymous",
    "id": "example-attester",
    "display": "Example attester"
  },
  "created": "2026-07-08",
  "publicComment": "This is a non-counted template support record.",
  "signature": {
    "method": "none-template",
    "verified": false
  },
  "privacy": "Contains no private contact details."
}

The schema

Its address is https://openvaluesstandard.org/schema/attestation-v0.1.schema.json. Validators can fetch it there; the file is also in the repository at app/data/standard/schemas/attestation.schema.json.

The key words MUST, MUST NOT, SHOULD, SHOULD NOT and MAY are used as described in RFC 2119 and RFC 8174 when, and only when, they appear in capitals.

Whether this format fits your app is your call. The spec says what a file MUST hold. Which formats you read and write, and what your app does with them, is yours to decide.