read 3 timessame text, same places, same fingerprintsummarized 3 timeswritten by a model, and marked soevery response says which part is which
These parts are the same on every read
Under one version and one configuration of getclean, the same page or the same file gives the same output in each of these parts.A model works in named steps only
A model works in these steps, and in no others.
The output of a model step is not promised to be the same on a second call. For that reason, each such output is marked: a highlight says
judged, a filled field comes with the words of the source, and a summary is named as a model’s text.
Every response names its steps
execution in a response has the version and the configuration of getclean, and one entry for each model step that ran, with the version of that step.
Part of a response
recognition, which is a fixed step that repeats under one version. An empty models list means that no model and no recognition took part in the response.
One switch turns every model step off
A request that sendsdeterministic_only as true runs no step whose output could differ between 2 runs. Highlights are found word for word only, and a publisher’s kind comes only from what is already known. A search returns its results in the merged order of the datasources and searches the web alone unless you name datasources. A request for a summary or a schema is refused. Every part of a fetch’s response then repeats, except what belongs to the call itself, such as its time and its id. A search still returns what its datasources have on the day it runs.
The policy of a key can set this for every call. A regulated team can then give its agents a key that no model step can run under.
A pinned version reads a page the same way after a change
The text and the ids repeat under one version and its configuration. A later version of getclean can read a page differently. To get the same reading across such a change, send the version aspinned_version, and the call runs under that version and its configuration.
get_limits lists the versions that are served. A version is served for at least version_minimum_days days after its change is announced. During its last version_notice_days days, each response that has notices has the notice version_retiring.
A fingerprint can be compared only within one view, one version, one configuration, and one kind of source. A report that will be checked later should store these 4 facts beside each fingerprint, because the check has to run under the same ones.