Hey all,
I've been building AKKU since January — a declarative system configuration tool in Rust. First real multi-crate project for me, so outside eyes on the architecture would be valuable before I lock things down for v0.1.

Instead of imperative commands, you describe desired state and AKKU plans the path, applies it, and rolls back on failure. Five-crate workspace with strict unidirectional dependencies.

cli → api → engine → modules/*
             ↘ shared_libs ↙

The core engine, API layer, conflict detection, plan/approve/rollback flow, and snapshots are all working. The module system interface — how modules register with each layer — is the main open design problem.

ARCHITECTURE.md is the best starting point: AKKU • Repo

Specifically curious whether the layer boundaries and the shared_libs / engine / api split make sense to a fresh eye.
Any Rust-specific feedback welcome too.
Licensed LGPL-3.0.

1 post - 1 participant

Read full topic