Public documentation

Find the exact boundary.

This page links the maintained guides and specifications without restating them. Normative requirements live under standard/; guides and profiles must not silently strengthen those requirements.

Interoperability material below uses Supply Chain Integrity, Transparency, and Trust (SCITT).

Documentation coordinate: verifier-standard 1.5.0, released 2026-09-18. The assembled site also carries machine-readable build metadata; the versioned release artifacts preserve this coordinate. Normative ownership remains under standard/.

Start with the quickstart Read the specifications Inspect the implementation reference

Start here

Quickstart — install, inspect, capture, validate, and refute.
Install Verifier — supported interpreters, the published release, and a source checkout.
Your first receipt — plan, run, validate, and refute one generic run end to end.
Typical use cases — ten situations, the mechanism for each, and what each one leaves unestablished.
Seal an artifact — freeze, seal, thaw, and detect a changed byte.
Publish a silo — commit, export, rebuild, and clone an experimental artifact-network snapshot.
Repository walkthrough — what lives where and which surface owns which claim.
Current maturity — normative, implementation, evidence-binding, conformance, and missing-mechanism status.
Claims and limits — allowed wording and prohibited inference.
Concepts and precedents — terminology and intellectual lineage.
Acronyms and abbreviated terms — canonical repository expansion key.
Conformance architecture — normative, wire, schema, runtime, and test ownership.
Artifact freeze, seal, and thaw — exact-byte preservation, finite self-closing seals, external anchors, and copy-on-write descendants.
Realms and time capsules — discrete, continuous, causal, problem-space, branching, cyclic, and atemporal structures with explicit mappings.
Artifact-first reference mechanisms — governing zero-identity/zero-knowledge (ZIZK) boundaries; process-bound TRUST, ROT, and RUST semantics; bounded identity disclosure; and the recorded reduced instruction set computer (RISC) Zero proof.
command-line interface (CLI) and application programming interface (API) reference — generated from the importable package.
Python application programming interface (API) guide — the supported exports organized by task, with the four non-PASS paths.
Python API stability — supported exports, versioning, and deprecation lifecycle.

Normative specifications

Verification complex and conformance — numbering, evidence independence, and aggregation.
Object and Graph specifications — VSTD-1..5 and VSTD-Graph-1..5, with persistent site navigation.
Wire identifiers — frozen dispatch values and historical names.

Profiles and interoperability

Experimental workflow — allocation, platform events, and explicit horizons.
Competition evaluation — bounded scored-evaluation claims.
VSTD-3 profile guidance — compatibility, threat-model, reference, and vendor-integration entry point.
SCITT semantic boundary — explicit non-substitution between transparency receipts and VSTD verdicts.
Supply Chain Integrity, Transparency, and Trust (SCITT) crosswalk — separate verdicts and current source status.
Stored interoperability components — exact retained bytes, catalog bindings, nonexecuting planning, and installation limits.
Component hub — digest-bound static discovery without fetching, installation, execution, ranking, or qualification.
Platform interoperability — configured intent, exact-run evidence, and cross-operating-system comparison limits.
Experimental graph topology — simultaneous equations, temporal relations, and bounded structural diagnostics.
Experimental artifact awareness and composed untraversability — observer-relative finite knowledge closure without universal confidentiality or runtime enforcement.
Ecosystem map — what adjacent systems supply and VSTD must not replace.

Project and contribution

Human maintainer guide — five-As claim traversal and bounded conclusions.
Automated-contributor rules — repository invariants and safe change behavior.
Repository contradiction status — the current live maintainer annunciator.
Roadmap — implemented surface, open gates, and non-goals.
Contributing — tests, compatibility, and claim discipline.
Governance — current decision rights and centralization boundary.
Security — private vulnerability reporting boundary.
Releases — reproducible artifacts, manifests, attestations, and publication gates.
Changelog — released and pending coordinates.