RAGBAZFor reviewers
Inspect the exported interface and the allowed host calls before approving a runtime.
- WIT contract
- declared effects
- evidence-ready artifacts
Glither / WIT / WASI Components
Compile policy into a sandboxed component.
Glither is the RAGBAZ rule language for consequential automation. The compiler path turns typed policies and strategies into WIT-described WebAssembly Components so host capabilities are explicit, portable, and reviewable before execution.
Why this boundary matters.
Agent gates, mail filters, trading strategies, and reviewer workflows should not depend on invisible callbacks. WIT makes the contract inspectable before the runtime is trusted.
For operators
Run policies in a constrained host with explicit inputs, outputs, and failure behavior.
- Wasmtime/WASI host
- fail-closed gates
- portable deployment unit
For builders
Author one rule surface, then generate Rust component code and companion checks from the same source.
- glither.governance
- glither.hft
- Rust and oracle path
Pilot journey.
The current slice is intentionally narrow: prove the compiler membrane, show the generated artifact, and keep the unfinished runtime claims visible.
Choose one ruleset.
Start with one governance or strategy file that has a meaningful action boundary. The pilot is strongest when the policy can be explained to a reviewer without reading host code.
inputpolicy.glithsample eventexpected allow / hold / deny result
Generate the WIT world.
The WIT output is the contract reviewers can inspect: imports, exports, record types, and declared effect boundaries before a component is admitted to a host.
outputworld.witeffect listdiagnostic report
Build the component.
The Rust component path is the implementation target for the current slice. OCI distribution and full host conformance remain work-in-progress surfaces, not production guarantees.
outputcomponent.wasmmanifesthost fixture
Package review evidence.
The useful buyer artifact is not only a binary. It is the source, WIT contract, build log, test fixture, and a short status note that says what is implemented and what is not.
packetsourceWITcomponentstatus note
Status boundary. The Glither component compiler path is an active implementation track. The public promise today is a reviewable design and pilot handoff for WIT/WASI component work; production host admission, registry promotion, and long-running conformance gates are still being hardened.
Start with one rule and one host boundary.
The pilot output is a Glither source file, generated WIT, component artifact, and an operator-facing evidence packet.