v0.23.0
Added
-
A schema field can hold a moment.
type: timestampsits besidetype: datein a type'sfields:block, and
takes2026-09-07T20:18:00Z: UTC, to the second, unquoted. A date is a day and is written quoted, because YAML
rereads an unquoted one as a datetime and a reader's own zone then shifts the day it shows. AZinstant carries
its zone in the value, so no reread moves it.timestamp-formaterrors on a value written in another shape, and on
one naming a moment the calendar does not have. -
A field naming a person carries an actor prefix.
ownertakeshuman:alex.doefor a person, or
role:head-of-engineeringfor a post. Exactly one person holds a post, so a role keeps answerability with one human
and survives a handover that leaves every record naming the previous holder wrong.confirmed.byon an FAQ and
deciderson an ADR takehuman:alone: each records who performed an act, and a post cannot perform one. A
bare name, an agent, a session id and a team alias all failfield-pattern, so the tier boundary between a
discovery and an FAQ is checked rather than described. The three prefixes are [OKF v0.2]'s, whose trust tiers key
offhuman:the same way. A corpus created before this rewrites the field in each record it holds, and
kac validatenames the ones still bare. -
Every record carries its own
type. The universal schema requires the field, directly afterid. Its value is
the singular type name the record's folder declares:standardinstandards/,adrinadrs/. A record read away
from its folder therefore says what it is.type-matches-foldererrors where the field and the folder disagree.
Every_template.mdcarries the line, sokac newwrites it. A corpus created before this adds the line to each
record it holds, andkac validatenames the ones that are missing it.
Changed
- An FAQ records every confirmation, rather than the last one.
confirmedreplacesconfirmed-byand
confirmed-onwith a list, one entry per confirmation and oldest first:
- { at: 2026-09-07T20:18:00Z, by: human:alex.doe }. The moment and the person are one entry, so they are edited
together and neither can be left behind. A reader asking when the answer was last checked, by whom, and who checked
it before that now has all three. The shape is [OKF v0.2]'s. A corpus holding FAQs written before this rewrites the
two keys as one entry per record, andkac validatenames the ones still carrying the old pair.