Verifiable systems in Zig and Elixir for markets, ML infrastructure and proofs. Hosting is not proof: every public claim below has a command that reproduces it.
zinging (zig-substrate v3.12.0) — Zero-allocation computational substrate unifying 7 Zig 0.15.2 engines (core, lob, seqab, vecdb, infer, quant, ioflow, chess) behind 202 C ABI symbols, standalone Python wheels, Homebrew (brew install smc17/tap/substrate), JSON-RPC daemon (stdio / --unix / --tcp), and WebAssembly (live browser playground):
- Measured:
49.3 MITCH msg/s ·1.23 Mpure-Zig H3 cells/s ·90.6 Mchessperft(5)nps ·1.09 MBlack-Scholes opts/s ·24 KBWASM - Proof:
700/700unit tests ·67/67differential & real-datasetsubstrate verify all·341/3415-tier E2E ·14-parser mutation fuzzer (0panics,0leaks) - Quickstarts: Live WASM Playground ·
brew install smc17/tap/substrate· 30s Python & C11 quickstarts · v3.12.0 Release + Wheel
Start with a small reasoning, recording or market-data task. The portable CLI preview includes seven CLIs, matching source, recorded checks and checksums. Choose the matching platform or build from source.
Make missing evidence fail: a runnable solver-checking lab, with exact status handling, refusal tests and an inspectable record.
Three systems that share one rule: Zig for the hot path, the BEAM for the control plane, a proof for every claim.
Markets and data
| Repo | What it is | Proof |
|---|---|---|
| zkdb | Columnar time-series database with q/kdb+ semantics: SIMD aggregation, asof and window joins. | 47/47 tests, fresh clone |
| zkdb-elixir | The same kernels as an Erlang NIF, so OTP can supervise them. | mix test 5/5, builds the NIF itself |
| jevy | Options market-making laboratory: Zig hot path, Python research layer, paper only. | Publicly viewable research · proprietary terms |
| finance-segway | Governed financial-model archetypes with hashed historical cases, not forecasts. | 596 strict tests · secondary review |
| MarketDataSimulator | A deterministic teaching exchange: matching, recovery, wire integrity. | .NET 10 · 392 tests per measured runtime |
ML infrastructure in Zig
| Repo | What it is | Proof |
|---|---|---|
| tokenizers-zig | HuggingFace tokenizer.json: BPE, WordPiece, Unigram. |
195 pass with pinned files · 48-input task · T5 gap retained |
| safetensors-zig | safetensors reader with header and overlap validation. | 19 pass, 2 optional skipped |
| faiss-zig | Flat, HNSW, IVFFlat and IVFPQ vector search. | 76/76 tests |
| znap | Zero-allocation inference: 30→6 policy in 32 ns, stories15M at ~700 tok/s. | 625/625 tests · M2 Max, zig build bench |
| qsr-zig | GF(2) matrix rank with SIMD elimination. | 800 differential trials vs a naive reference |
Proofs and tools
| Repo | What it is | Proof |
|---|---|---|
| method-wagwan | Replay a repository's history; models propose, deterministic programs decide. | Design + roadmap; Phase 1 pre-registration in progress |
| logic-zig | An executable museum of logic and a fail-closed trust kernel (CDCL, BMC, DRAT). | 391 tests per native ARM64 runtime · CLI preview |
| zig-h3 | Uber H3 v4: all 70 functions, pure-Zig and C-wrapper paths. | 211 tests cross-checked against libh3 v4.1.0 |
| zag | A terminal, block model and agent runtime in one Zig program. | 613 Linux tests |
Aerospace, marine & systems tooling (newly public)
| Repo | What it is |
|---|---|
| strip | Evidence-bearing aerospace computation and 6-DOF flight simulation substrate in Zig (WGS84, US76, FMI 3.0, MAVLink). |
| yard | Naval architecture and marine engineering in Zig: 72 primitive modules (BEM hydrodynamics, AUVs, AIS, seakeeping). |
| evals-agentic-control | Deterministic evaluation harness and control benchmarks for agentic coding workflows. |
| sentinel-sbom | High-speed SBOM auditing and supply-chain verification CLI. |
| distro-blog-builder | Standalone Zig static-site and RSS/sitemap builder. |
| cfr-solver-zig · zig-cobs | Counterfactual Regret Minimization solver & zero-alloc COBS wire framing in Zig. |
- Public roadmap board: every open issue in every public repo, by system and priority.
- STANDARDS.md: proof levels, labels, how an issue moves, and what every repo contains.
- OPS.md: last night's fresh-clone gates, depth meters and open regressions for every public repo.
- Want to help? Each repo's README starts with links to its Status, Roadmap and Contributing guide. Issues labelled
status: readyorgood first issueare scoped and waiting. - Found a number that does not reproduce? Every repo has a "Challenge a claim" issue template.
- PyO3: explain buffered stdout when embedding Python
- Faiss: explain how data structure affects IVFPQ recall
- NixOS: make CrowdSec hub refresh optional at startup
- H3: list zig-h3 on the community bindings page
- H3: fix
polygonToCellsCLI dropping vertices with whitespace before] - H3: honor
CMAKE_INSTALL_INCLUDEDIRfor header install destination
These are open contributions, pending upstream checks and review.
method-wagwan Phase 1 (replaying Ghostty; zig-h3 as smoke test) · Hex package for zkdb-elixir · Zig 0.16 migration notes
A large private corpus is not a portfolio. Repos become public one at a time, after a clean clone builds on Zig 0.16.0 and a five-minute README exists.
sketch / scaffold / compiled / unit-tested / integration-tested / audited / benchmarked. Speedups without commit, hardware class, workload, and script are not claims. Definitions and rules: STANDARDS.md.