◇ Open Values Standardfor builders

Spec / open-values-agreement

Open Values Agreement v0.1

The record of what a group agreed: the question, who was there, each agreement with who does it, by when and what counts as done, and what is still open. The Work Party page makes it in the browser and can read it back to revise it.

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 Futurism Institute sites: sites/futurism-institute/public/js/work-party.js. Read by Futurism Institute sites: sites/futurism-institute/public/js/work-party.js.

Fields

FieldWhat it meansType
format requiredAlways "open-values-agreement". Tells a reader that this file is the record of what a group agreed.always "open-values-agreement"
version requiredThe version of the agreement format this file follows, 0.1.string
recorded requiredThe date the browser saved the file, YYYY-MM-DD.string
questionThe question the group settled, such as "Do we buy a second ladder, or share the one we have?"string
presentWho was there, one name per item. First names are enough.list of string
agreed requiredWhat the group agreed, one item per agreement. Rows with nothing in what are left out.list of object
openWhat is still open, one item per line, including who disagreed and with what.list of string
led_byWho led the conversation. Present only when filled in.string
led_by_hopedWhat the person who led hoped for going in. Present only when filled in.string
decided_byHow the group decided: "everyone" (everyone agreed), "no-objection" (nobody objected), "most" (most agreed) or "one-person" (one person decided after hearing everyone). Present only when chosen.string
dissent_read_by_holdersTrue when everyone named in open has read how their disagreement is worded and agrees it is how they would put it. Present only when true.boolean
checked_byWho checks that the agreements get done. Present only when filled in.string
revisionPresent when the file revises an earlier one: what it revises and what changed, computed by the Work Party.any

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.

The schema

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