Start small, keep the proof
Use Rulith where “done”
must be verifiable
The best first workflow has structured inputs, explicit acceptance criteria, and an external result you can check.
Recommended first run
Structured file transformation
Read a local JSON file, validate its fields, perform deterministic calculations, write a result file, and close only after the output is verified.
Engineering
Release evidence
Collect test, review, and approval evidence; derive release readiness; block deployment when required evidence is absent.
Operations
Order fulfillment
Atomically claim one pending order, load source-attested details, perform fulfillment, notify the customer, and record the receipt.
Custom workflow
Your workflow
Package its Knowledge and Sources as one Capability. Implement referenced Tools in the local Worker, and attach an independent Constitution when the workflow needs additional governance.
A good Rulith workflow has four properties
- A concrete unit of workEach case has a bounded input and an explicit finish condition.
- Evidence outside the modelImportant values can be retrieved or verified by an authoritative source.
- Observable side effectsA Worker can return a receipt instead of asking the model to claim success.
- A meaningful failure stateMissing evidence, rejected policy, and execution failure remain visible.