elixir-architect

OTP supervision trees organize Elixir processes into hierarchical fault-tolerant structures. Design them by mapping your application's components—workers, servers, and dynamic supervisors—into a tree that restarts failed processes automatically. This enforces Let It Crash semantics, isolating failures and keeping the system resilient.

Ash provides declarative domain modeling for Phoenix apps, replacing hand-written Ecto schemas with resource definitions. Define your resources in Ash, compose them with actions and validations, then let Ash generate the database layer and API. This centralizes business logic and reduces boilerplate.

Oban handles asynchronous job queuing and execution in Elixir. Define job modules, enqueue them from your application code, and Oban processes them reliably with built-in retry, scheduling, and monitoring. Pair it with supervision trees to ensure job workers restart on failure.

Yes. Architecture Decision Records document your design rationale and constraints for collaboration. Combined with comprehensive project documentation and guardrails for AI workflows, ADRs create handoff packages that enable Director and Implementor AI agents to understand and continue work on complex systems.

Multi-app structures separate concerns into independent applications within a single umbrella project, following Dave Thomas's architectural pattern. Use this when you have distinct functional domains, shared libraries, or need to isolate failure domains and deploy components independently.

A functional core isolates pure business logic in dedicated modules, keeping side effects at the boundary. In Elixir, implement core logic in impl/ directories with deterministic functions, then compose them with OTP processes and Ash resources. This improves testability and enables AI-safe guardrails.