RawPair currently manages containers via API calls. While this improves encapsulation and portability, orchestration is still imperative: containers are launched with parameters, and their success is inferred through status polling or indirect checks.
This issue proposes integrating rezn (once it reaches shipped state) to shift RawPair's orchestration toward a declarative, contract-enforced model. Instead of “start and hope,” workloads would be defined as signed plans, validated upfront, and executed deterministically.
Why:
- Even with API calls to Docker, we're still doing imperative orchestration with optimistic assumptions
rezn will enable pre-execution validation, including contract checks (preconditions, invariants)- Workloads are compiled into canonical JSON (via JCS) and digitally signed
- Moves RawPair closer to a minimal, K8s-free platform-as-a-service
- Enables reproducible, auditable executions across nodes
- Opens the door to multi-node orchestration, reproducibility, and better auditing - without Kubernetes
RawPair currently manages containers via API calls. While this improves encapsulation and portability, orchestration is still imperative: containers are launched with parameters, and their success is inferred through status polling or indirect checks.
This issue proposes integrating rezn (once it reaches shipped state) to shift RawPair's orchestration toward a declarative, contract-enforced model. Instead of “start and hope,” workloads would be defined as signed plans, validated upfront, and executed deterministically.
Why:
reznwill enable pre-execution validation, including contract checks (preconditions, invariants)