spec-effects

Effect algebra codifies how your program handles side effects like IO, errors, and state. Define effect kinds (IO, Either, Option, Reader, State, Async) in artifacts/v{N}/spec/effects.yaml with documented semantics to enable consistent morphism handling across your codebase.

Reader provides access to immutable environment context; State threads mutable values through computations; IO wraps side effects; Either and Option handle errors and absence. Each effect type solves different concerns—choose based on whether you need environment access, mutable threading, or error tracking.

Define error variants in your effects specification that represent domain-specific failures. Document each variant's semantics in effects.yaml so Either and Option effects can propagate and handle errors consistently across your morphism algebra.

Yes. Kleisli composition works with effect algebras by composing morphisms that return wrapped values. Define your effect kinds clearly in the algebra so Kleisli arrows chain effects correctly through type constructors like Reader, State, and Either.

Yes. If your algebra includes Reader effects, you must define environment types in effects.yaml to specify what immutable context your computations require and how it flows through morphisms.

Once artifacts/v{N}/spec/effects.yaml is generated with all effect kinds, error variants, and threading semantics documented, your morphism definitions can reference the algebra consistently for IO, error handling, reader access, and state management.