mine-rs-architecture

To prevent dependency cycles in a Rust monorepo, establish strict dependency direction by separating the deterministic core logic from SDK, Python bindings, CLI, and agentic tooling layers. Each crate must own a clear responsibility and depend only on lower layers.

The best way to add a new mining capability without architectural coupling is to place it in the correct crate based on existing layering rules. Maintain the separation between the Rust core, SDK, and tools to ensure deterministic logic remains isolated from external integrations.

Python integration maintains deterministic logic by using a dedicated binding layer that separates the Rust core from Python components. This preserves the monorepo structure by keeping external integrations isolated from the deterministic core logic and SDK boundaries.

Yes, agentic tooling can be used alongside CLI and SDK layers in a Rust workspace by maintaining clear crate boundaries. Agentic components must remain a separate implementation layer with distinct responsibilities to avoid coupling with the deterministic core logic.

Module ownership in a Rust monorepo needs refactoring when adding features that cross existing crate boundaries or violate dependency direction. Refactoring ensures the layered API structure and separation between implementation layers remain intact.

Rust workspace architecture breaks down when new packages bypass crate boundaries and create unwanted dependency directions. Enforce monorepo layering rules by assigning each new package to the correct implementation layer, preserving the deterministic core and SDK separation.