Text compose

Renders one template per record into one field. No model, no key, $0.

Connector	`text/compose`
Role	compose
Records	any type
Tier	built in
Credential	none
Cost	unset in the manifest; `gtme plan` prints what the step declares at run time
Source	internal/adapters

Use it

It ships inside the binary. In a pipeline file:

steps:
  - id: compose
    use: text/compose
    with:
      template: TEMPLATE

Replace the placeholder:

TEMPLATE: the template rendered once per record over record.* (the uses:/of: fields) and config.* (ADR-057); the result is the one field provides: declares. The runner loads {file:} before validation.

gtme plan pipeline.yaml checks the credential is set and that every field this step needs is provided by a step before it, without calling anyone.

Needs

Whatever fields the step's uses: line names. The runner checks them at plan time.

Provides

The fields the step's provides: line declares.

Config

Key	Type	What it does
`template` required	string	The template rendered once per record over record.* (the uses:/of: fields) and config.* (ADR-057); the result is the one field provides: declares. The runner loads {file:} before validation.

On this page, connector means what gtme calls an adapter. This one is a process adapter compiled into the binary. Two adapter tiers explains the difference.