◇ Open Values Standardfor builders

Spec / ovs-pulse

Open Values Pulse v0.1

The list of recent changes to the catalogue: facts files and guides added or corrected, and facts files with sources old enough to need checking again. The site's build writes it from git history.

Stable. A change that breaks existing files needs a new version. A file a build step makes from other files. Change the sources, not this file.

Who writes it and who reads it

Written by pipeline/build_pulse.js. Read by status surfaces, preview context.

Fields

FieldWhat it meansType
format requiredAlways "ovs-pulse". Tells a reader that this file is the list of recent changes to the catalogue.always "ovs-pulse"
version requiredThe version of the pulse format this file follows, 0.1.string
built requiredThe day the file was built, as YYYY-MM-DD.string
windowDays requiredHow many days of history the file looks back over, such as 90.integer
entries requiredThe recent changes, newest first, up to a fixed limit (160 in the current builder), plus the latest entry for any page that limit would leave out.list
truncated requiredHow many further changes were left out because the list hit its limit. 0 means nothing was left out.integer

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

A pulse feed records calm dated changes against resolvable Open Values nodes.

{
  "format": "ovs-pulse",
  "version": "0.1",
  "built": "2026-07-07",
  "windowDays": 90,
  "entries": [
    {
      "date": "2026-07-07",
      "node": "ovs:cat/banking",
      "kind": "stale",
      "what": "Ethical banking has one older claim queued for refresh.",
      "source": "https://example.org/source"
    }
  ],
  "truncated": 0
}

A file that must be rejected

Pulse entries use a small known kind vocabulary.

{
  "format": "ovs-pulse",
  "version": "0.1",
  "built": "2026-07-07",
  "windowDays": 90,
  "entries": [
    {
      "date": "2026-07-07",
      "node": "ovs:cat/banking",
      "kind": "viral",
      "what": "Bad fixture."
    }
  ],
  "truncated": 0
}

The schema

Its address is https://openvaluesstandard.org/schema/pulse-v0.1.schema.json. Validators can fetch it there; the file is also in the repository at app/data/standard/schemas/pulse.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.