Learn
Use public SDK documentation, examples, capability contracts, and clean-room game evidence.
Build scripts users can understand and the host can constrain.
The ZavoBot publisher path combines Rust tooling, declared capabilities, source review, reproducible artifacts, versioned support, and transparent commercial terms.
Creator applications are not open yet. The application form remains disabled until identity and review operations are live.
Build
Develop in Rust, exercise the simulator, and package a deterministic Wasm component.
Review
Submit source, artifact, declared capabilities, tests, support scope, and privacy evidence.
Publish
Release a signed version with clear access, changelog, status, and user support ownership.
Publisher contract
A Store relationship, not a black box.
The commercial and technical rules are designed to remain inspectable.
- Planned 80% creator / 20% platform revenue allocation
- Paid scripts use 30-day seats rather than permanent ambiguity
- Each version binds its exact capabilities and source revision
- Unsafe, deceptive, or unsupported behavior can be quarantined
- Support and maintenance expectations are visible before purchase