Select a named test.
QUALIFICATION LAB / PINNED USTAV SOURCE
Explore the rules.
Inspect the tests.
Follow eight named cases through authorization, local settlement and pool custody. Compare the reported outcomes with the code that defines them.
LOCAL TESTS
The published example comes from actual offline Rust tests. Imported reports are unsigned claims. Passing a test does not establish a security audit, chain activation or production readiness.
Capability contract ↗Files stay in browser memory, up to 1 MiB each. No upload, automatic saving, keys or browser execution.
Loading the source catalog…
01 / SOURCE → SUITE → TEST
A graph of
reported outcomes.
A “passed” negative case means the expected rejection succeeded. Select a test to inspect its assertions and pinned source.
● Passed● Failed● Ignored / no report
Drag the graph to pan. Use the zoom buttons, or focus the graph and use arrow keys, +, − and Home. The case list offers the same test selection.
02 / COVERAGE & SOURCE CLAIMS
Look past
the pass count.
Every expected case must be present exactly once. Suite counts and exit codes are checked against the named results.
Elapsed times include Cargo and compilation overhead. They are not comparable benchmarks or throughput measurements.
Inspect source comparisons and report bytes
| Field | Report claim | Published pin | Comparison |
|---|
No report loaded.
03 / COMPARE REPORTED RUNS
What changed
between two runs?
Keep a baseline, then open another report. Compare source claims and named test outcomes; elapsed times do not establish a performance regression.
No baseline selected.
Open a baseline and a current report to compare.
04 / REPRODUCE IN YOUR CHECKOUT
Run the
same named tests.
The local runner checks the protocol pin before and after execution. It runs the three fixed suites offline and records named outcomes and output hashes.
POSIX SHELL / FROM THE BLOCH MARKETS REPOSITORY
The source catalog is loading.
Requires the pinned checkout, Rust toolchain and cached dependencies. Public test fixtures only; never production keys.
OPEN INPUTS / EXPLICIT BOUNDARIES