architecture-authority

Enforce deterministic architecture in Rust crates by defining a strict architectural contract that specifies domain boundaries, safety invariants, and auditability for planning and execution. This blocks unsafe changes and guides refactors.

The best way to structure Rust crates with domain-driven design is to apply a canonical crate structure with ubiquitous language, use case isolation, and controller-free business logic. This enforces strict boundary rules and library-first philosophy.

Plan a Rust refactor by requesting an architectural plan with a unified diff detailing impacted files, determinism impacts, safety impacts, recommended tests, and a rollback strategy. This ensures auditability and preserves system integrity.

You should not use clean architecture for Rust refactoring when changes violate absolute rejection conditions, fail explicit boundary compliance, or bypass safety models like journal, undo, and quarantine policies required to preserve integrity.

Yes, the dirctl architecture contract supports undo and quarantine policies through its safety model. It enforces strict ordering, journal policies, and explicit boundary compliance to guarantee safe execution and auditability.

Yes, you can use a library-first philosophy in Rust to isolate business logic from controllers. The architectural contract mandates use case isolation and controller-free business logic to maintain strict domain boundaries.