Documentation
Inspect signed evidence, integrate a supported evaluation workflow, or review the trust boundaries before a release decision. Your team or appointed evaluator selects the tests and requirements; your reviewer makes the acceptance decision.
New to InvarLock? Try the CPU demonstration fixture. For help with a real comparison, explore a paid pilot with a complete reviewer handoff.
Search titles and article text. Queries stay in your browser.
New in v0.17
Plan judge-evaluation precision before collection, explore the sensitivity of supported exact-match results, and follow examples of reassessment that preserve earlier evidence. Read the release notes and limits.
Transaction map
Follow the authority, not only the commands
Each step uses or produces a named artifact. Select a step to see its inputs, outputs and responsible role. Roles describe responsibilities; they do not prove that different people performed the work.
01—06
Close request
Bind both artifacts, one schedule, one metric, policy, runtime, and output.
Setup guides
Try the CPU fixture first. When you are ready to evaluate your own artifacts, use these guides to prepare the supported inputs and independent verification settings.
01
Getting Started
Prepare your inputs for a supported evaluation and verification workflow.
02
Evaluation Request
Close the artifacts, dataset, runtime, metric, policy, mode, and destination.
03
Evidence & Verification
Publish signed evidence and replay it against independent trust anchors.
04
Evaluator Qualification
Check which evaluator records qualify for replay and which remain observation-only.
05
Recipient Acceptance
Transport one signed technical result and apply current recipient policy.
Install for these guides
Use Python 3.12 or newer in a virtual environment. Installation follows the published release used by these guides; repository development examples may differ.
python -m pip install "invarlock==0.17.3"
# Model execution: prepare a matching runtime image first.Prepared-workspace command summary
These are abbreviated commands, not a runnable quickstart. Prepare the request, runtime options and signing key using the getting-started guide. Verification requires evidence and an independently configured trust profile. The ellipsis stands for the required evaluation options.
invarlock evaluate request.yaml ...
invarlock verify evidence/ --trust-profile trust.json --receipt verification.receipt.json
invarlock report evidence/Documentation provenance
Source ref
v0.17.3 (release tag)
Source commit
4a35743
Synced
Oct 29, 2026
Docs / visuals
47 docs, 21 site visuals
11 upstream diagram replacements
Artifact Trail
Start here to see what the evaluation operator publishes, what the technical verifier replays, which receipt carries the technical result, and how a recipient applies current acceptance policy.
Evidence Artifacts
Map every canonical bundle path to the claim and binding it carries.
Reports & Receipts
Read the canonical comparison and separately signed technical receipt.
Client Review Package
Prepare an attributed review, unchanged evidence and recipient verification instructions.
Acceptance Handoff
Transport one receipt, bind the exact artifact, and apply current recipient policy.
Trust Model
Understand evidence, receipt, envelope, recipient, renderer, and residual trust.
User Guide
16Closed requests, runtime execution, signed evidence, independent verification, CI, and public qualification.
Assurance
6Decision semantics, pairing, reproducibility, technical-verdict limits, and the scoped assurance case.
Reference
20Exact CLI, evaluator, acceptance, compatibility, contract, artifact, report, provider, and embedding interfaces.
Security
4Trust roles, threat boundaries, key handling, dependency audit, and operational hardening.