Templates

A template pack is a pinned, validated set of templates that turns proposed artifacts into text. It does not discover domain meaning, choose output ownership, or write files.

Pack contract

A pack declares:

• a stable pack ID and version;
• the supported generation-contract version;
• a renderer ID and version;
• reusable output recipe IDs, definition scopes, path patterns, owners, and template IDs;
• the content of each referenced template.

TemplatePackLoader normalises and validates this manifest before planning. Unsafe paths, duplicate identities, missing templates, incompatible contracts, and unsupported renderers are diagnostics, not best-effort fallbacks.

Generation flow

1. Configuration selects compatible inputs.
2. Pack orchestration expands each output recipe over matching definitions in the canonical context.
3. The generation planner receives those concrete artifact descriptors and produces proposed artifacts with ownership and provenance.
4. A bounded renderer adapter renders those artifacts.
5. Output application previews or applies owned changes.

The reference renderer uses Scriban behind IRendererAdapter. Templates receive an immutable artifact rendering context and a bounded projection of each declared semantic input. They use Scriban variables, loops, and conditions to produce the output structure; expected output files are test oracles, not templates. Templates cannot read arbitrary files, mutate the model, or choose additional output paths.

See template packs for manifest validation and template rendering for limits, diagnostics, and provenance.