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.3.0, released 2026-09-08. The assembled site also
carries machine-readable build metadata;
the versioned release
artifacts preserve this coordinate. Normative ownership remains under
standard/.
Start here
- Quickstart — install, inspect, capture, validate, and refute.
- 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 API stability — supported exports, versioning, and deprecation lifecycle.
Normative specifications
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
Verifier