+∑≠-∑+∑≠-∑+∑≠-∑+∑≠-∑+∑≠-∑+∑≠-∑+∑≠-∑+∑≠-∑+∑≠-∑+∑≠-∑+∑≠-∑+∑≠-∑+∑≠-∑+∑≠-∑+∑≠-∑+∑≠-∑+∑≠-∑+∑≠-∑+∑≠-∑+∑≠-∑+∑≠-∑+∑≠-∑
REDUCE CREATIVE FRICTION THROUGH INTELLIGENT AUTOMATION FOR PUBLIC GOODS.
GOAL: Amplify human creativity through removing obstacles between alignment of intention and manifestation.
+∑≠-∑+∑≠-∑+∑≠-∑+∑≠-∑+∑≠-∑+∑≠-∑+∑≠-∑+∑≠-∑+∑≠-∑+∑≠-∑+∑≠-∑+∑≠-∑+∑≠-∑+∑≠-∑+∑≠-∑+∑≠-∑+∑≠-∑+∑≠-∑+∑≠-∑+∑≠-∑+∑≠-∑+∑≠-∑
This is a Rust binary LLM orchestration engine. A recursive tool for building tools. It interfaces with the AI agents; deterministically store requests, acknowledgements, process logs, and responses for actions during an agentic llm for:
reflection
reuse
context refinement
Engines create engines, strands become webs, task become distribution, accountably.
By leveraging multiple LLMs with Prompt Request Loops, Data Ingestion Sandloops, Testing Edge‑Case Loops, and Random Audit/Snapshot Loops, we create a pipeline that maximizes each agent’s strengths while maintaining deterministic, auditable workflows across the entire network.
The first feature of this rust binary is a an network node for our agent development workspace:
- Nodes use cryptographic identities (Call other nodes for complex task coordination)
- Nodes are self replicating: (Manage & request distributed state across the network for comprehensive context)
- Nodes are self optimizing: (Execute prompt sandloops for continuous quality improvement )
- We implement the P2P network configuration & cryptographic identities with the Commonware library.
- We provide deterministic state management inside each node binary, via Cnidarium
- Nodes ingest state back to the core orchestrator in snapshot form, reducing storage on all nodes during long‑running agent workflows and fallbacks.
- Requirements Mgmt: Define verifiable goals to align autonomy & prevent drift.
- Risk Mgmt: Mitigate uncertainties like bias for reliable decisions.
- Verification & Validation: Test AI in real scenarios for safety & efficacy.
- Lifecycle Mgmt: Guide iterative dev from concept to ops.
- Design Definition: Optimize architectures via trades for goal-oriented behavior.
| Package | Binary | Description |
|---|---|---|
ergors |
ergors |
Node engine - network, storage, orchestration |
ergors-cli |
ergors-cli |
CLI client for node management |
ho-std |
— | Shared library - types, traits, custody |
ergors-proto |
— | Proto definitions & code generation |
| Resource | Description |
|---|---|
| Specs | Technical specifications |
| Custody & Auth | Security, key management, encryption |
| Network | P2P networking |
| Storage | Cnidarium state management |
cargo install just # Task runnerjust install # Builds and installs ergors + ergors-cli to ~/.cargo/binergors init # Create node identity, config, and data directories
ergors init llms # Configure LLM provider API keys
ergors start # Start the engineWe use just as our task runner. Run just help to see all available commands.
# Development
just dev init # Run engine commands in dev mode
just dev start # Start engine with RUST_BACKTRACE=1
just cli <args> # Run CLI in dev mode
just watch # Rebuild on file changes (requires cargo-watch)
# Building
just build # Debug build
just build-release # Release build
just proto # Regenerate proto types
# Quality
just check # Quick syntax check (cargo chec)
just clippy # Lint with clippy
just fmt # Format code
just test # Run all tests
# CI
just ci # Full pipeline: fmt, clippy, test, build
just ci-quick # Quick check without tests| Command | Description |
|---|---|
just install |
Build release + install ergors and ergors-cli to PATH |
just install-engine |
Install only the engine |
just install-cli |
Install only the CLI |
just uninstall |
Remove installed binaries |
just which |
Show installed binary locations |
just build-pkg ergors # Build specific package (debug)
just build-pkg ergors release # Build specific package (release)
just test-pkg ho-std # Test specific packagejust env # Show environment info
just version # Show binary versions
just clean # Remove build artifacts
just rebuild # Clean + release build
just doc-open # Build and open documentationfor a dedicated list of environment variables and their defaults check here.
Controls the logging level for the entire application. This is the standard Rust tracing environment variable.
Levels (from least to most verbose):
error- Only errorswarn- Warnings and errorsinfo- Informational messages, warnings, and errors (default)debug- Debug information plus all abovetrace- Trace-level debugging plus all above
Examples:
# Basic levels
export RUST_LOG=info # Default - general operational logs
export RUST_LOG=debug # Detailed debugging information
export RUST_LOG=trace # Very verbose trace-level logging
# Module-specific levels
export RUST_LOG=ergors=debug,tower_http=info # Debug for ergors, info for tower_http
export RUST_LOG=ergors::server=trace # Trace only server module
# Target specific components
export RUST_LOG=ergors::middleware=debug # Debug middleware operations
export RUST_LOG=ergors::storage=trace # Trace storage operationsTests using orchestration servers are essentially scripts that can be used to verify integrity of logic, including its deployments, upgrades and migrations. we have a dedicated library and tooling specifically for this purpose.
- static responses from prompt requests
- completions
- prompts
- toolcalling
- api calls
- mpc servers
- embeddings
- key gen siging libary
- custody middleware integration tests (reference penumbra testing library)
- integration test library
We have ported into this workspace existing designs from the following code-bases:
THANK YOU to the contributors of these, go show some support to their projects