Quick start
This path builds the maintained Rust CLI and runs the read-only corpus gate. Run it from the repository root.
Overview#
This path builds the maintained Rust CLI and runs the read-only corpus gate. Run it from the repository root.
Prerequisites#
- Rust/Cargo compatible with
Cargo.tomlandCargo.lock. - The repository checkout, including the
*-examples/directories. - Extra tools are command-specific: the macOS monospace font (Menlo or SF Mono) for rendered PTY screenshots,
ghfor README refresh/drift, andstadofor remote Weles capture/audit. The read-only catalog gate below needs none of those.
Build#
cargo build --release
./target/release/spis --helpThe top-level help identifies the program as spis — evidence-grade reference corpus tooling and lists the maintained subcommands. Invoke the built Rust binary directly.
Validate the checked-in catalogs#
./target/release/spis generate-example-catalogs --checkThis command validates only and writes nothing. Read its current per-catalog counts and named invariant failures; historical totals are not a verdict for the active corpus.
partial is not a failure of the gate. It means the record and its explicit gaps are internally consistent. The gate fails when schemas, indexes, hashes, paths, status, or required evidence fields contradict one another.
Measure without changing data#
./target/release/spis verify-reference-evidence --catalog pricing-page-examplesWithout --apply, verification measures without rewriting records. A successful exit means measurement completed, not that the records meet every completeness floor. See the offline audit walkthrough.
Next steps#
- Learn the reference pipeline.
- Use the CLI command index before any mutating or networked command.
- Follow the record lifecycle walkthrough against a dedicated active corpus.
- Read the runbook before any network or fleet operation.