Releases

Type definitions for the SP1 prover

SP1 core machine definitions

Pure Rust ØMQ/ZeroMQ. Facade over omq-compio (default) or omq-tokio. Wire-compatible with libzmq.

Pure Rust ØMQ/ZeroMQ. Facade over omq-compio (default) or omq-tokio. Wire-compatible with libzmq.

The last backend you'll ever need. Rust-powered headless CMS with built-in blog, ecommerce, wallet, payment and 4 plugin engines.

OmniPaxos-backed ConsensusDriver for tsoracle

engenho-scheduler — the first real K8s controller on the engenho substrate. Reconciles pending Pods (no spec.nodeName) by picking a Node via a pluggable SchedulingStrategy trait + patching the Pod through StoreMesh. R8 of the engenho K8s base layer.

engenho-scheduler — the first real K8s controller on the engenho substrate. Reconciles pending Pods (no spec.nodeName) by picking a Node via a pluggable SchedulingStrategy trait + patching the Pod through StoreMesh. R8 of the engenho K8s base layer.

engenho-kubelet — the missing piece between 'Pod object in the store' and 'container running on host'. Per-node controller that watches Pods bound to its node + materializes containers via a pluggable ContainerRuntime backend (PodmanBackend / CriBackend / RunwasiBackend / FakeBackend for tests).

engenho-kubelet — the missing piece between 'Pod object in the store' and 'container running on host'. Per-node controller that watches Pods bound to its node + materializes containers via a pluggable ContainerRuntime backend (PodmanBackend / CriBackend / RunwasiBackend / FakeBackend for tests).

Protobuf build integration for grpc

Protobuf plugin to generate gRPC-Rust service bindings

engenho-controllers — the engenho K8s controller suite. Hosts the Controller trait + canonical implementations: ReplicaSetController (R9), DeploymentController (R9.5), ServiceController (R9.6), GC (R9.7). Each is a thin reconcile loop on engenho-store. Same shape as engenho-scheduler — the second-site for the controller pattern.

engenho-controllers — the engenho K8s controller suite. Hosts the Controller trait + canonical implementations: ReplicaSetController (R9), DeploymentController (R9.5), ServiceController (R9.6), GC (R9.7). Each is a thin reconcile loop on engenho-store. Same shape as engenho-scheduler — the second-site for the controller pattern.

Notification service for data-driven workflows with live and replay APIs.

engenho-apiserver — HTTP K8s API wrapping engenho-store. Translates kubectl REST operations into typed ResourceCommand proposals via the distributed substrate. Layer R7 of the engenho K8s base layer.

engenho-apiserver — HTTP K8s API wrapping engenho-store. Translates kubectl REST operations into typed ResourceCommand proposals via the distributed substrate. Layer R7 of the engenho K8s base layer.

engenho's K8s resource store — etcd-equivalent backed by openraft. Separate Raft group from engenho-revoada (which commits role assignments); this commits K8s resource CRUD. Layer of the Pillar 7 runtime that engenho-apiserver wraps to serve the K8s API surface.

Statistics-driven micro-benchmarking library

engenho's K8s resource store — etcd-equivalent backed by openraft. Separate Raft group from engenho-revoada (which commits role assignments); this commits K8s resource CRUD. Layer of the Pillar 7 runtime that engenho-apiserver wraps to serve the K8s API surface.

engenho-teia — the NATS fabric layer for engenho. Carries Raft RPC, watch streams, content sync, attestation receipts, and observability events across one typed transport. See docs/FABRIC.md.

engenho's distribution layer — dynamic K8s control-plane / worker role shifting via Raft consensus + gossip membership + P2P content sync + BLAKE3 attested transitions. Read docs/DISTRIBUTED.md.

engenho-teia — the NATS fabric layer for engenho. Carries Raft RPC, watch streams, content sync, attestation receipts, and observability events across one typed transport. See docs/FABRIC.md.

engenho-config — the top-level shikumi-back typed configuration surface for the whole engenho substrate. EngenhoConfig owns cluster + revoada + teia + scheduler + controllers + consistency sub-structs; each provides shikumi::TieredConfig with reasonable prescribed_default()s so 90% of operators get a working substrate from cargo run.

engenho's distribution layer — dynamic K8s control-plane / worker role shifting via Raft consensus + gossip membership + P2P content sync + BLAKE3 attested transitions. Read docs/DISTRIBUTED.md.

ergonomic rust client for NetBox 4.x REST API

Rusty API for ddss, a performance-oriented fork of the DDS double dummy solver for bridge

LeIndex MCP and semantic code search engine for AI tools and large codebases

engenho-config — the top-level shikumi-back typed configuration surface for the whole engenho substrate. EngenhoConfig owns cluster + revoada + teia + scheduler + controllers + consistency sub-structs; each provides shikumi::TieredConfig with reasonable prescribed_default()s so 90% of operators get a working substrate from cargo run.

engenho-config — the top-level shikumi-back typed configuration surface for the whole engenho substrate. EngenhoConfig owns cluster + revoada + teia + scheduler + controllers + consistency sub-structs; each provides shikumi::TieredConfig with reasonable prescribed_default()s so 90% of operators get a working substrate from cargo run.