gen-types

Type definition generation reads your build artifacts and outputs actual source files with type schemas for domain models, effects, API endpoints, and storage. The process enforces a mandatory generation order—effects modules first—to ensure base types exist before dependent types are created.

Type generation produces artifacts under artifacts/v{N}/gen/{language}/src, supporting multiple language targets. The output includes domain models, effects modules (Result, App, Errors), API schemas, and storage models as actual source files in your chosen language.

Mandatory generation order ensures effects modules—base types like Result, App, and Errors—are created first. This validates that core dependencies exist before other types reference them, preventing missing dependency errors in downstream code.

Yes. Type generation applies to end-to-end code-generation workflows for domain models, effects modules, API schemas, and storage models. It ingests your build artifacts and produces corresponding type files with deterministic ordering and validation.

Type generation validates that core effect modules (Result, App, Errors) exist before completion. It enforces the mandatory generation order and confirms all required outputs are present in the artifacts directory before finishing.

Type generation succeeds when it produces all required source files under artifacts/v{N}/gen/{language}/src in the correct order and validates the existence of mandatory effects modules without errors.