Expand description
Fingerprints, reuse keys, execution ownership, reuse, and end-of-review rechecks.
Structs§
- Changes
- Why the current key differs from an earlier cached result for the same eval and Eval definition.
- Entry
- One record of a key’s history, or with
cache listthe latest record of each key. - Key
- An eval’s reuse key:
hash(evaluation criteria, sorted (name, fingerprint) of the Artifacts it depends on). - Manifest
- What artifactsum covered, saved with executions to explain later changes. A file map that would exceed 64 KiB is omitted; the fingerprint still covers it.
- Parallelism
- How many fingerprints a process computes at once: one bound shared by a Run’s
preparation and its end-of-review rechecks, or by
status. - Prepared
Fingerprint - A prepared fingerprint; artifactsum also carries its manifest.
Enums§
- Unkeyed
- Why an eval has no reuse key: an Artifact it depends on declares
fingerprint: false.
Functions§
- changes
- Explain a changed key against an earlier cached execution of the same Eval definition: which of the target’s files changed, and which dependency Artifacts’ fingerprints changed.
- dependencies
- The Artifacts an eval depends on: its target, the target’s child Artifacts, and the Artifacts the eval names in its instruction or runtime args. Connections further away count only through how the developer defines fingerprints.
- eval_
definition_ hash - Hash the evaluation criteria: what is asked and how the answer is judged, never how the eval is executed. Execution options (backend, model, reasoning, limits, the profile variant), the eval’s id and title, and tool views stay out.
- eval_
key - The eval’s reuse key from prepared fingerprints. Without a fingerprint on every Artifact it depends on, the eval has no key, so it is never reused or published.
- eval_
keys - Keys of every eval whose dependency Artifacts were all prepared, by eval id.
- key
- The reuse key of an Eval definition hash over these fingerprints.
- key_
with_ kinds - Scope kinds distinguish file/folder observation without coupling reuse to repo paths.
- list
- The latest record of every key, or with
historyevery record, latest first per key. - prepare
- Prepare only the selected dependency closure, once per Artifact, computing up to the parallelism’s limit of fingerprints at a time. The result does not depend on completion order: a failure reports the first failing Artifact in input order, and fingerprints after it are cancelled because they cannot change which failure that is.
- recheck
- Recompute the eval’s key after a review: every Artifact it depends on is fingerprinted again, so a change to any of them during the review is detected.
- remove
- Remove every record of an unused key from its history, preserving executions and Runs.
- reuse
- Give a request another execution’s result. A request that waited for this very execution (a live owner it joined, or the Human wait it followed) joined it; any other found a completed record.
- show
- A key’s records, latest first; without
historyonly the latest.