nmnmcc Effect
Make computational effects visible in the project's native model. Keep dependencies, failure, resource lifetime, cancellation, concurrency, and the point where description becomes execution explicit.
- Identify the effect model already owned by the project.
- Model the workflow and its boundaries before choosing API names.
- Compose supported work inside that model and isolate foreign calls.
- Verify types, behavior, cleanup, and execution at the owned edge.
Read the detailed guide, then the matching ecosystem guide when the project uses Algebraic Effects, Effect, Cats Effect, or ZIO. Ask before an unavoidable escape hatch.