Documentation
These pages are rendered straight from the repository's markdown on every push, so they never drift from the code they describe.
Prerequisites, the two-command quick start, and how to read a result.
What you need installed, the two-command quick start, the four-verdict taxonomy and exit codes, and what CI does differently from your machine.
2 · RECIPEHow to consume a Community-tier provider today: build a thin executable over the engine's public SDK, referencing exactly the providers you need.
3 · GUIDEThree worked examples — Postman, xUnit, SpecFlow — each re-authored (not auto-converted) onto the orders-dotnet sample, with a field-by-field mapping table and an honest account of what doesn't map.
Each is a real service with its own database, broker, or cache — not a toy echo.
REST → Postgres row → Kafka event → outbound webhook callback. Five steps.
PYTHON · FASTAPIREST → MySQL row → Redis cache entry → RabbitMQ event, with a read-through cache proof. Five steps.
JAVA · SPRING BOOT 3.3REST → SQL Server row → NATS JetStream event → SMTP receipt e-mail. Four steps.
NODE.JS · JSON-RPC 2.0JSON-RPC → Postgres → Kafka → an independent worker role consuming an injected adjustment, via a custom runner and the Community rpc.json-rpc provider. Ten steps.
How this repository is run.
Overview, the sample catalogue table, quick start, and directory layout.
HOWThe quality bar for a new sample, and how to add one.
SECHow to report a vulnerability in a sample application or test suite.
CoCThe standards this community holds itself to.
Where the pieces this repository depends on live.
The architecture blueprint, the YAML DSL specification, and the language reference.
HUBThe community provider registry — including rpc.json-rpc, consumed by the ledger-jsonrpc sample.
TELEMETRYThe optional, privacy-allowlisted run-metadata aggregation service.