Crate zebflow 

Zebflow core crate.

This crate is intentionally split into independent subsystems:

1. contracts for stable persisted and transferred format boundaries
2. pipeline for pipeline orchestration (graph traversal, node dispatch)
3. language for sandboxed script execution (Deno)
4. rwe for reactive web template compile/render (TSX → SSR → hydrate)
5. automaton for the LLM call interface, the OpenAI-compatible client and the model loop ai.text.generate runs
6. platform for service composition and web shell (Axum, MCP, DSL)
7. infra for shared runtime infrastructure (WebSocket, storage, scheduler)

The ZebflowEngineKit type wires default implementations so an app entrypoint can keep main.rs thin and delegate all behavior to library modules.

Modules

automaton

Automaton

contracts

Unified contracts for durable and transferred Zebflow objects.

infra

Infrastructure layer — shared runtime services and distributed-system seams.

language

Language module for parsing, compiling, and running user scripts.

mapserver

Lightweight spatial publish/resolve engine.

pipeline

Framework module for pipeline orchestration.

platform

Zebflow platform module.

provision

Provisioning-oriented helpers and adapters.

rwe

Reactive Web Engine (RWE) module.

version

zebfs

ZebFS: Zebflow-native object-style filesystem for project artifacts.

Structs

ZebflowEngineKit

Ready-to-use set of engine registries for pipeline/language/rwe modules.