Structured contract copied for validation or lookup.
- Purpose
- Bind the abstract step against the deterministic tool summary manifest emitted upstream — read `parsed_tool` for ports/datatypes and `input_schemas.workflow_step_linked` for valid step `tool_state` shape.
Background synthesis loaded by explicit progressive-disclosure metadata.
- Purpose
- Preserve testable output labels and collection element identifiers while replacing abstract steps with concrete gxformat2 steps.
- Trigger
- When a concrete step changes output labels, emits collection outputs, creates a diagnostic checkpoint, or makes a final output too weakly assertable.
Background synthesis loaded by explicit progressive-disclosure metadata.
- Purpose
- Connect concrete Galaxy tool inputs/outputs while preserving collection mapping and reduction semantics.
- Trigger
- When implementing a step with data_collection inputs, mapped outputs, reductions, or nested collection wiring.
Background synthesis loaded by explicit progressive-disclosure metadata.
- Purpose
- Check whether a concrete tool input/output can preserve the intended source-derived Galaxy collection shape.
- Trigger
- When implementing concrete steps for source-derived File/list/paired/list:paired/list:list inputs or outputs.
Background synthesis loaded by explicit progressive-disclosure metadata.
- Purpose
- Turn operator-derived abstract transforms into concrete Galaxy wiring, collection operations, or review requests.
- Trigger
- When a concrete step implements behavior traced to map, join, groupTuple, branch, mix, combine, or multiMap.
Background synthesis loaded by explicit progressive-disclosure metadata.
- Purpose
- Insert built-in Galaxy collection-operation steps when a direct tool connection cannot express the needed shape.
- Trigger
- When a step needs collection construction, filtering, extraction, zipping, unzipping, flattening, merging, or relabeling.
Background synthesis loaded by explicit progressive-disclosure metadata.
- Purpose
- Implement identifier-derived collection reshaping via Apply Rules.
- Trigger
- When collection element identifiers need regex parsing, nesting-level swaps, regrouping, or paired identifier assignment.
Workflow-construction idiom. Usually condensed during casting.
- Purpose
- Choose corpus-attested collection recipes when implementing concrete Galaxy steps.
- Trigger
- When implementation needs cleanup-after-fanout, sync-by-identifier, singleton unboxing, relabeling, collection reshaping, or collection-tabular bridges.
Workflow-construction idiom. Usually condensed during casting.
- Purpose
- Choose corpus-attested tabular recipes when implementing concrete Galaxy steps.
- Trigger
- When implementation needs row filtering, column projection, computed columns, joins, grouping, SQL, awk, text-processing wrappers, or tabular-collection bridges.
Background synthesis loaded by explicit progressive-disclosure metadata.
- Purpose
- Preserve concrete tool/job failure evidence while implementing step labels, tool ids, output labels, and collection wiring.
- Trigger
- When a selected wrapper has explicit failure semantics, dynamic outputs, non-default stdio rules, strict-shell behavior, or runtime-only failure risk.