How this record is made

Who does the work

This record is produced with software agents running a language model. They write the code that fetches, reads and checks the sources, and they draft the wording of these pages, this one included.

The agents execute written orders. An order states the work and the rules it is done under, and it is ratified by the person who keeps this record before it is executed. Where an order leaves a question open, the run applies the default the record already states — the value is withheld, or left unmeasured — files the question, and marks it decided by default until that person rules on it.

Where the orders are kept: the last section of this page.

What no model writes

No status and no recorded change that this record publishes about a document is a model’s own wording. A published status other than “not yet determined” is one value from a fixed list, taken from the publisher’s own statement, which the row cites; a recorded change is found by code, as the next section describes.

One act lets a model take part in placing a status. Where the written rules cannot place a publisher’s passage, the model named in the prompt file may be asked to match that passage to one value from a fixed list; where the prompt file names no model, no read is made. The answer counts only if it is one of those values, spelled as listed, with a quote copied from the passage; any other answer leaves the status undetermined. Each such read is held with a receipt, and is never filed as a rule’s result or as a person’s confirmation.

In this build, 0 of the 132 tracked entries carry a status placed by a model read.

The record’s own voice is a different thing: the one-line description of what each document is, the headings, and explanations such as this page. The agents draft it. It describes; it is not evidence about any document, and the evidence for a statement about a document is the publisher’s text that the statement cites. The record keeps no sentence-by-sentence account of which act drafted which words.

What each verification mark means: the verification marks, on How this is kept.

How a value is derived

A recorded change begins as a difference between the digests of the text that two fetches of the same address returned, after code has extracted that text, normalised it and removed the publisher’s recorded page furniture. No model reads the text to find it.

A published status names, in the record’s own fields, the act that confirmed it; where that act is a written rule, the rule’s name and version are held beside the result. A status that no recorded act stands behind is published as “not yet determined”, and the page How this is kept counts those rows by the reason each one reaches it.

The count of rows not yet determined, by reason: How this is kept. Changes as recorded: what changed.

What only a person does

A person’s key is the only act that records that a person confirmed a value. No other path writes it, and a build that finds a person’s confirmation without a key fails, so no deploy carries one that the build finds. A confirmation made by a rule or by a model read is held under its own name and is never counted as a person’s.

Corrections, including any to a confirmation: the corrections log.

Where the orders are kept

The orders, the rulings made on them, and the questions a run files are kept as dated files and dated entries in this record’s source repository, beside the code they govern. That repository is not published. The data, this record’s own documentation and the proofs are published, and are described on the page on reading the record by machine and the integrity record.