chain-composer

To compose type-safe pipeline chains, you apply canonical templates to subdomain task types and validate compatibility deterministically, producing a Pipeline Spec JSON. This process ensures your pipeline chain maintains type safety throughout its execution stages.

You validate type compatibility for a pipeline specification by running the artifact-utils validator against your composed chain. This deterministic validation checks whether template-adapted steps align correctly before outputting the final Pipeline Spec JSON.

You can tailor pipeline chains for CI, production, personal, or work contexts by applying operator-profile gates during composition. These gates adjust the generated Pipeline Spec JSON to match the specific environmental requirements of each deployment target.

A domain manifest must explicitly declare prerequisites like references_needed and scripts_needed before pipeline spec composition begins. The chain-composer respects these declared dependencies to ensure all required components are available during type-safe chain generation.

The best way to generate a Pipeline Spec JSON for a pipeline scaffolder is to start from canonical templates per subdomain task type, adapt them with domain-specific steps, and validate the chain. This produces a complete spec ready for scaffolding.

Pipeline chain composition fails type compatibility validation when subdomain task types and adapted domain-specific steps do not align deterministically. The artifact-utils validator rejects mismatches between canonical templates and manifest requirements, preventing an invalid Pipeline Spec from being generated.