Thanks for helping shape the runtime foundation for Lily Protocol.
This repository is intentionally scaffolded, not feature-complete. We want the core runtime patterns to be clear enough that contributors can extend them in small, reviewable increments.
Before opening a pull request:
- Check for an existing issue or open one first for larger changes
- Prefer extension points over deep, one-off implementations
- Keep public APIs typed and documented
- Add or update tests for behavior you change
npm install
npm run build
npm run test
npm run verify- New memory backends behind the existing interface
- Additional tool adapters and runtime policies
- Improved task coordination and observability
- Provider adapters for model integration
- Runtime safety checks and policy guards
- Keep PRs scoped to one concern
- Explain why the change belongs in the runtime foundation
- Document new extension points in the README or inline docs
- Avoid shipping completed subsystems where a scaffold is more appropriate
src/runtimecontains runtime composition and bootstrap behaviorsrc/tasksandsrc/actionsdrive the minimal happy-path executionsrc/toolsdefines the contributor-facing tool contractsrc/memory,src/providers, andsrc/stateare deliberately thin abstractions for follow-up work
Please include:
- Node.js version
- Steps to reproduce
- Expected behavior
- Actual behavior
- Relevant logs or test output