The file format
What is inside a file this site saves. This page is for people who want to read or write the file with their own tools. Nobody needs it to use the site.
Every file has two halves. The top half is plain text a person can read in any program. Under a line of dashes, the same list is written again as data, so software can read it. A ledger with two tasks saves as this:
Example: five neighbours and one ladder
=======================================
Saved 2026-06-24 | 2 tasks: 1 late, 1 done.
1. [Late, was due 21 Jun 2026] Put a sign-out sheet on the shed door.
who: Rin | by: 2026-06-21 | will check: Wen
counts as done when: The sheet is on the door and has at least one entry.
2. [Done 17 Jun 2026] Replace the frayed strap before anyone else uses the ladder.
who: Joss | by: 2026-06-18 | checked by: Wen on 2026-06-18
counts as done when: New strap fitted, old one binned.
Made at theworkparty.org. Open this file there to see the list and add to it. Nothing was sent anywhere.
---
{
"format": "open-values-agreement",
"version": "0.1",
"recorded": "2026-06-24",
"name": "Example: five neighbours and one ladder",
"agreed": [
{
"id": "l2v711g",
"what": "Replace the frayed strap before anyone else uses the ladder.",
"who": "Joss",
"by": "2026-06-18",
"done_when": "New strap fitted, old one binned.",
"state": "done",
"state_on": "2026-06-17",
"checker": "Wen",
"checked_by": "Wen",
"checked_on": "2026-06-18",
"from": {
"question": "",
"recorded": "2026-06-14"
}
},
{
"id": "l4nko26",
"what": "Put a sign-out sheet on the shed door.",
"who": "Rin",
"by": "2026-06-21",
"done_when": "The sheet is on the door and has at least one entry.",
"state": "open",
"checker": "Wen",
"from": {
"question": "",
"recorded": "2026-06-14"
}
}
],
"open": []
}
A group’s record and a ledger are the same kind of file: a list of tasks. A group’s record adds the question the group settled and who was there. A ledger adds what happened to each task.
The format’s name is open-values-agreement. Its schema, the formal description that software checks a file against, is published at openvaluesstandard.org, where the Institute’s sites publish the file formats they share.
Fields for the whole file
| Field | What it holds |
|---|---|
| format | Always open-values-agreement. |
| version | 0.1. |
| recorded | The day the browser saved the file, as 2026-06-14. |
| question | The question a group settled. A ledger leaves it out. |
| name | A name for the ledger: a person, a group or an organization. A group’s record leaves it out. |
| present | Who was there. |
| agreed | The tasks: one entry for each. |
| open | What was not settled, including who disagreed and with what. This field has nothing to do with a task’s state “open”, which means not done yet. |
| led_by, led_by_hoped | Who led the conversation, and what they hoped for going in. |
| decided_by | How the group decided: everyone, no-objection, most or one-person. |
| dissent_read_by_holders | True when everyone named as disagreeing has read how their disagreement is worded. |
| checked_by | Who checks that the tasks get done. |
| revision | For a revised record: which record it revises, and which tasks were added or dropped. |
Fields for each task
| Field | What it holds | When |
|---|---|---|
| what | The task, in the words it was written in. | Since 0.1 |
| who | Who is doing it. | Since 0.1 |
| by | By when. A date as 2026-06-21 lets the ledger say when a task is late; words such as “next meeting” are kept as written. | Since 0.1 |
| done_when | What counts as done. | Since 0.1 |
| state | What happened: open (not done yet), done, let-go (dropped) or changed. Left out, a task is open. “Late” is never written: a reader works it out from the date. | Added 2026-11-11 |
| state_on | The day that was written down. | Added 2026-11-11 |
| state_note | Why it was dropped, what it changed to, or any other note. | Added 2026-11-11 |
| checker | Who will check this task. | Added 2026-11-17 |
| checked_by | Who checked this task. Left out until someone has. | Added 2026-11-11 |
| checked_on | The day the check was written down. | Added 2026-11-17 |
| history | What the task said before each change. | Added 2026-11-11 |
| id | A short code made from the task’s words, so two copies of a ledger can be read together. | Added 2026-11-11 |
| from | For a task that came from a group’s record: the question the group settled, and the date. | Added 2026-11-11 |
What changed
17 November 2026. A task keeps who will check apart from who checked: checker is the person named, and checked_by with checked_on is written once someone has checked. Files saved from 11 to 17 November kept both in checked_by. When one is opened, a name on an unfinished task is read as the person who will check.
11 November 2026. A task can carry what happened to it, and a file can be a ledger. The seven task fields marked above, and the file’s name, were added as optional fields. The version stays 0.1, because the schema allows fields it does not list and every file written before this date still opens. The schema does not describe the new fields yet; until it does, this page is where they are written down.
12 October 2026. A group’s record can name who checks.
28 September 2026. A group’s record can say who led the conversation, how the group decided, and that the people named as disagreeing have read how it is worded.
What reads it
The group form writes the file and reads it back to revise it. The ledger reads any number of them together and writes one. Both are this site’s own pages. No tool made by anyone else reads the format yet.
The decisions the Institute publishes with a number are a different layout. They are on the decision records page.