Home Mold

freeform-summary-to-galaxy-template

gxformat2 skeleton with per-step TODOs from a free-form summary and Galaxy design brief.

Mold health

warn
  • Source layout

    Every file beside index.md is one the mold kind declares.

  • Axis fields

    source-specific fields are coherent.

  • Eval plan

    Abstract oracle: the properties any cast of this Mold must satisfy.

    eval.md declares properties and check type.

    eval.md ↗
  • Scenarios

    Concrete cases bound to fixtures, run against the eval properties.

    scenarios.md not written yet.

  • Typed refs

    12 typed references; 0 resolver issues.

  • On-demand triggers

    All on-demand references describe triggers.

  • Evidence checks

    Hypothesis references include verification.

axis
source-specific
source
freeform
name
freeform-summary-to-galaxy-template
contract

Reference Loading

Typed references describe what casting consumes, and when the generated skill should load each artifact.

Schema galaxy-workflow-draft

Structured contract copied for validation or lookup.

Purpose
Output contract: the emitted gxformat2 draft conforms to [[galaxy-workflow-draft]]. Cast bundles the JSON Schema so the skill carries its output shape alongside the [[draft-validate]] CLI checks.
CLI Command draft-validate

Command reference. Usually cast to a sidecar and loaded only when invoked.

Purpose
Validate the emitted draft against draft-contract rules (sentinel form, topology, _plan_* placement) before handing off.
Trigger
After writing or modifying the draft workflow file.
Verify
Cast the skill, run on a representative paper-derived summary, confirm draft-validate diagnostics route back.
Research open-requirements-ledger

Background synthesis loaded by explicit progressive-disclosure metadata.

Purpose
Carry the open-requirements ledger: read open entries bearing on this step's decisions, mark resolved the ones it closes, and append any new unmet need it surfaces.
Verify
Promote after a worked run shows entries this Mold appends or resolves are consumed downstream without re-derivation.
Research galaxy-workflow-draft-format

Background synthesis loaded by explicit progressive-disclosure metadata.

Purpose
Emit the gxformat2 draft superset: TODO tool_id, optional tool_state / tool_shed_repository, and per-step _plan_state / _plan_context planning fields.
Verify
Promote after a downstream per-step implementation Mold consumes _plan_state and _plan_context without round-tripping back through the source summary.
Research galaxy-workflow-testability-design

Background synthesis loaded by explicit progressive-disclosure metadata.

Purpose
Choose stable workflow input/output labels, testable checkpoint outputs, and fixture-compatible workflow interfaces while drafting the skeleton.
Trigger
When the template decides workflow inputs, workflow outputs, promoted checkpoints, or collection output identifiers that future tests will need to address.
Research galaxy-data-flow-draft-contract

Background synthesis loaded by explicit progressive-disclosure metadata.

Purpose
Respect the handoff from the freeform-to-Galaxy interface and data-flow briefs to the gxformat2 skeleton.
Trigger
When translating abstract nodes, unresolved tool needs, and placeholder transformations into template TODOs.
Verify
Promote after two worked freeform-to-Galaxy templates preserve the design-brief/template split without schema changes.
Pattern galaxy-collection-patterns

Workflow-construction idiom. Copied verbatim; may carry companions.

Purpose
Use corpus-grounded collection pattern guidance for unresolved skeleton steps.
Trigger
When adding TODO steps for collection cleanup, reshaping, relabeling, identifier synchronization, or collection-tabular bridges.
Pattern galaxy-tabular-patterns

Workflow-construction idiom. Copied verbatim; may carry companions.

Purpose
Use corpus-grounded tabular pattern guidance for unresolved skeleton steps.
Trigger
When adding TODO steps for tabular filtering, projection, joins, aggregation, text-processing recipes, or tabular-collection bridges.
Pattern galaxy-conditionals-patterns

Workflow-construction idiom. Copied verbatim; may carry companions.

Purpose
Use corpus-grounded conditional pattern guidance for unresolved skeleton steps.
Trigger
When adding TODO steps for optional steps, gating on non-empty results, routing between alternative outputs, or transform-or-pass-through branches.
Pattern galaxy-interval-patterns

Workflow-construction idiom. Copied verbatim; may carry companions.

Purpose
Use corpus-grounded genomic-interval pattern guidance for unresolved skeleton steps.
Trigger
When adding TODO steps for interval overlap, merge, coverage, windowing, masking, or set-algebra on coordinate features.
Research galaxy-workflow-comments

Background synthesis loaded by explicit progressive-disclosure metadata.

Purpose
Group the settled step set into titled stage frames (the gxformat2 `comments:` array) so the skeleton carries the analysis-stage narrative IWC authors annotate by hand. Schema-legal and optional.
Trigger
After topology is settled and the skeleton can be partitioned into named analysis stages (inputs, per-stage step clusters, parameter-derivation knots, visualization/outputs).

Cast artifacts

How to install →

Artifact handoffs

/ pipeline contract

Produces

Consumes

freeform-summary-to-galaxy-template

Read the original free-form source artifact if present, the free-form summary Markdown document, and the freeform-to-Galaxy interface and data-flow briefs. Emit a gxformat2 skeleton with workflow inputs, workflow outputs, placeholder steps, rough connections, and TODO slots for later implementation Molds.

The free-form summary does not have a concrete schema yet; treat it as Markdown. Treat the prior-step index as the working context: source transcript or paper, free-form summary, freeform-to-Galaxy interface and data-flow briefs, and any open questions carried forward.

Topology is this Mold’s job to settle. The output must be concrete gxformat2: workflow inputs with their final collection shapes and formats, workflow outputs, the step set, the producer→consumer edge graph, branches, and when: guards are all decided here. The upstream freeform-to-Galaxy interface and data-flow briefs guide those decisions, but if they hedge or leave a topology choice open, this Mold makes the call from source evidence, IWC exemplars, and pattern pages — never emit a topology TODO. Wrapper resolution, by contrast, is evidence-gated, not source-gated: resolve each tool step to the tier its evidence supports — Resolved (fully concrete, no _plan_*), Identity-pinned (concrete tool_id, parameters and changeset left to the per-step Mold), or Deferred (tool_id: TODO) — as defined in galaxy-workflow-draft-format. Capture whatever you defer in the _plan_* family (_plan_state, _plan_context, _plan_in, _plan_out) so the per-step Mold has the source evidence and constraints it needs.

Source tendency: free-form sources rarely name tools, so steps land in Deferred more often than nf-core or CWL — but a free-form source that does name a specific tool/version with evidence hardens to the matching tier, and a corpus-confirmed utility wrapper (interval/tabular/collection op) is not deferred just because the surrounding prose is informal. When deferring a domain tool, cite the originating paper section, interview answer, figure, or supplementary table in _plan_context, and record vague intent in _plan_state (“default settings”, “stranded reverse if mentioned, else unstranded”) so the per-step Mold knows the evidence ceiling.

Before handing off, sanity-check that each step is computable from what feeds it. Once the step set is settled, re-read it and ask, for each step, whether the operation its intent implies can actually be produced from the inputs you wired. The connection graph only knows that ports connect — not what each port is supposed to contain — so an output that needs evidence no input carries will validate fine and still be impossible to implement. Where you spot that gap, don’t leave it implicit: wire (or add) the step that supplies the missing input, or record the unmet need plainly in _plan_state so the per-step Mold or a reviewer can act on it rather than discover it late.

Things worth a second look:

  • an output column or field that no wired input carries;
  • an aggregate or summary whose grouping key isn’t present upstream;
  • a filter or threshold whose criterion isn’t produced by any input;
  • a join whose key doesn’t exist on both sides;
  • a step whose _plan_* promises more than its in: ports can supply;
  • if classification step, is that classification/enumeration possible only from inputs.

Optionally, once topology is settled, group the step set into titled stage frames via the gxformat2 comments: array (one frame per analysis stage, contains_steps: populated, color decorative) — see galaxy-workflow-comments for the convention.

Before handing off, check each settled step is computable from what feeds it. The connection graph knows that ports connect, not what they carry — so a declared output that needs evidence no wired input supplies will validate yet can’t be implemented. Where you find that gap, wire (or add) the producer; if you can’t, append a blocking entry to the open-requirements-ledger naming the step, the uncomputable output, and the missing evidence (and record vague intent in _plan_state) so the per-step loop or repair-galaxy-draft-topology acts on it rather than discovering it late. More generally, carry the ledger: read the entries bearing on your topology decisions and mark resolved the ones you close.

Output shape is gxformat2 with wrapper-tier relaxations and _plan_state / _plan_context / _plan_in / _plan_out per tool step — see galaxy-workflow-draft-format. Refinement open work for those planning fields lives in refinement.md.

Incoming References (14)

  • freeform-summary-to-galaxy-data-flow related note — Translate a free-form source summary into a Galaxy data-flow design brief.
  • freeform-summary-to-galaxy-interface related note — Map a free-form source summary into a Galaxy workflow interface design brief.
  • repair-galaxy-draft-topology related mold — Re-wire a Galaxy draft region when a step's declared output can't be computed from its wired inputs.
  • Galaxy: collection patterns related mold — Use this MOC to choose corpus-grounded Galaxy collection transformation patterns.
  • Galaxy: conditionals patterns related mold — Use this MOC to choose corpus-grounded Galaxy when and pick_value conditional patterns.
  • Galaxy: genomic interval patterns related mold — Use this MOC to choose corpus-grounded Galaxy genomic interval operations and recipes on coordinate features.
  • Galaxy: sequence patterns related mold — Use this MOC to choose corpus-grounded Galaxy operations on sequence records (FASTA) — interconvert, reformat, merge, length, extract/mask by region.
  • Galaxy: tabular patterns related mold — Use this MOC to choose corpus-grounded Galaxy tabular transformation patterns.
  • INTERVIEW → GALAXY phase of pipeline — Interview-driven path to a Galaxy gxformat2 workflow through the shared freeform-summary handoff.
  • PAPER → GALAXY phase of pipeline — Direct path from a paper to a Galaxy gxformat2 workflow. No CWL intermediate.
  • Galaxy data-flow draft contract related mold — Defines the proposed boundary between Galaxy data-flow drafts, gxformat2 templates, and concrete step implementation.
  • Galaxy Workflow Comments related note — How to annotate a gxformat2 workflow with editor comments: one titled frame per analysis stage, populate contains_steps, color decorative.
  • Galaxy workflow draft format related mold — gxformat2 draft superset: wrapper-tier TODOs (tool_id, tool_state, port names) plus _plan_state / _plan_context / _plan_in / _plan_out per tool step.
  • Galaxy workflow draft (gxformat2 superset) related mold — JSON Schema for `class: GalaxyWorkflowDraft` — gxformat2 with `TODO_*` sentinels and `_plan_*` planning fields per draft step.