Main
Keep stages explicit so you can route models/backends without rewriting application logic.
Start with one workflow and measure latency per stage; only then scale out and add caching/memory policies.
Design for observability early: trace stage boundaries and store replayable inputs/outputs for debugging.
Source-backed notes
- README installs the daemon via Homebrew cask and the client SDK via
pip install pyorla. - README describes components: stage mapper, workflow orchestrator, and a memory manager for shared inference state.
- README includes an academic citation to arXiv:2603.13605.
FAQ
- Is this a prompt library?: No — it’s a runtime/engine; you still define your tasks and policies.
- Do I need the Python SDK?: Only if your clients are Python; the daemon can be used independently per docs.
- Is it production-ready?: Validate on your workloads first; treat it as an evolving, research-backed system.