Skip to main content
The SINT conformance suite is a 157-test certification harness that any SINT-compliant gateway implementation must pass. The suite is language-agnostic; a reference runner ships with the TypeScript reference implementation and ports to Python, Go, and Rust.

​
The five categories

​
Exit criteria

An implementation is certified SINT-compliant if:
≥ 154/157 tests pass (≥ 97.5%)
All 52 ledger integrity tests pass (100% mandatory)
Zero state-machine coverage failures
The ledger integrity gate is binary because a partial-integrity ledger is not an auditable ledger.

​
Running the suite

Results are emitted as JSON + human-readable Markdown:

​
The benchmark suite

Separate from the conformance suite, seven benchmarks (BM-*) measure performance characteristics. These are not certification gates but ship with every release. Adversarial condition: every BM-PG-* benchmark includes a flood test (10,000 ESCALATE/min). Gateway must maintain T0 p50 ≤ 2ms under flood. This is the protocol’s DoS resilience test.

​
Hardware target matrix

​
Certification bundle

On passing, the suite emits a certification bundle — a JSON document suitable for submission to external auditors, internal compliance teams, or standards bodies. The bundle contains:
  • Per-invariant evidence (I-T1 through I-G3)
  • Per-tier benchmark results with confidence intervals
  • Full test log with timestamps
  • SHA-256 hash of the test harness at runtime
  • Gateway version and commit hash
  • Reproducibility metadata (hardware, OS, runtime versions)
Example bundle: docs/reports/certification-bundle-summary.md.
Independent implementation? If you’ve built a non-TypeScript SINT gateway, we’d love to see your conformance results. Open a PR against docs/implementations.md and we’ll link to your implementation from this page.