◇ Open Values Standardfor builders

Spec / ovs-errand-registry

Open Values Errand Registry v0.1

A list of everyday tasks, such as the weekly grocery shop, each broken into the categories a person picks from to do it. Conscious Consuming keeps it.

Stable. A change that breaks existing files needs a new version. A file someone writes by hand or with a tool, and keeps.

Who writes it and who reads it

Written by pipeline/build_errands.js. Read by Ask, future errand runner.

Fields

FieldWhat it meansType
format requiredAlways "ovs-errand-registry". Tells a reader that this file is the list of errands.always "ovs-errand-registry"
version requiredThe version of the errand registry format this file follows, 0.1.string
updated requiredThe day the file was last changed, as YYYY-MM-DD.string
errands requiredThe errands. An errand is a real task, such as the weekly grocery shop, broken into the categories a person picks from to do it.list

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

Errands map a practical task to one or more category-picking steps.

{
  "format": "ovs-errand-registry",
  "version": "0.1",
  "updated": "2026-07-07",
  "errands": [
    {
      "id": "ovs:errand/pick-a-bank",
      "label": "Pick a bank",
      "aliases": [
        "choose a bank"
      ],
      "reads": "Choose where everyday money should sit.",
      "output": "list",
      "tradeoff": [
        "fees",
        "environment"
      ],
      "steps": [
        {
          "cat": "banking",
          "pick": "one",
          "note": "The everyday account where pay, bills, and savings begin."
        }
      ]
    }
  ]
}

A file that must be rejected

Errand steps must use known pick modes.

{
  "format": "ovs-errand-registry",
  "version": "0.1",
  "updated": "2026-07-07",
  "errands": [
    {
      "id": "ovs:errand/pick-a-bank",
      "label": "Pick a bank",
      "aliases": [],
      "reads": "Choose where everyday money should sit.",
      "output": "list",
      "steps": [
        {
          "cat": "banking",
          "pick": "many",
          "note": "The everyday account."
        }
      ]
    }
  ]
}

The schema

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