Home Mold

paper-summary-to-galaxy-template

gxformat2 skeleton with per-step TODOs from a paper summary and the paper-to-Galaxy design brief.

Mold health

warn
  • Source layout

    Directory Mold with only index.md frontmatter.

  • Axis fields

    source-specific fields are coherent.

  • Eval plan

    eval.md not written yet.

  • Typed refs

    6 typed references; 0 resolver issues.

  • On-demand triggers

    All on-demand references describe triggers.

  • Evidence checks

    Hypothesis references include verification.

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

Reference Loading

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

Researchgalaxy-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.
Researchgalaxy-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.
Researchgalaxy-data-flow-draft-contract

Background synthesis loaded by explicit progressive-disclosure metadata.

Purpose
Respect the handoff from the combined paper-to-Galaxy design brief to the gxformat2 skeleton.
Trigger
When translating abstract nodes, unresolved tool needs, and placeholder transformations into template TODOs.
Verify
Promote after two worked paper-to-Galaxy templates preserve the design-brief/template split without schema changes.
Patterngalaxy-tabular-patterns

Workflow-construction idiom. Usually condensed during casting.

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.

Artifact handoffs

/ pipeline contract

Produces

  • galaxy-workflow-draft yaml galaxy-workflow-draft.gxwf.yml

    gxformat2 draft (see [[galaxy-workflow-draft-format]]): topology fully resolved (workflow inputs, outputs, step set, edges); tool_id / tool_state / tool_shed_repository and wrapper-determined port names may be TODO with free-text _plan_state / _plan_context / _plan_in / _plan_out per step for later implementation Molds.

    consumed by

Consumes

paper-summary-to-galaxy-template

Read the original paper artifact, the paper summary Markdown document, and the paper-to-Galaxy design brief. Emit a gxformat2 skeleton with workflow inputs, workflow outputs, placeholder steps, rough connections, and TODO slots for later implementation Molds.

The paper summary does not have a concrete schema yet; treat it as Markdown. Treat the prior-step index as the working context: paper source, paper summary, paper-to-Galaxy design brief, 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 paper-to-Galaxy design brief guides those decisions, but if it hedges or leaves a topology choice open, this Mold makes the call from source evidence, IWC exemplars, and pattern pages — never emit a topology TODO. What is deferred to per-step authoring is strictly wrapper-tier: tool_id, tool_version, tool_shed_repository, tool_state, and the wrapper-determined port names that surface in in: / out: / outputSource. Capture deferred intent 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.

Defer thoughtfully. When research surfaces a Foundry pattern page that names the exact recipe — a galaxy-collection-patterns reshape, a conditional-run-optional-step gate, a galaxy-tabular-patterns filter — fill the step in as completely as the pattern allows: concrete tool_id, parameters, port names from the pattern’s worked example. Pattern pages encode resolved choices; emitting TODO over a covered recipe discards real evidence the per-step Mold cannot recover. Paper sources will rarely give you enough to fill a domain tool step concretely — defer those wrappers and parameters, but cite the originating paper section / figure / supplementary table in _plan_context and use _plan_state to record vague intent (“default settings”, “stranded reverse if mentioned, else unstranded”) so the per-step Mold knows the evidence ceiling.

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 (6)

  • Galaxy: collection patternsrelated mold— Use this MOC to choose corpus-grounded Galaxy collection transformation patterns.
  • Galaxy: conditionals patternsrelated mold— Use this MOC to choose corpus-grounded Galaxy when and pick_value conditional patterns.
  • Galaxy: tabular patternsrelated mold— Use this MOC to choose corpus-grounded Galaxy tabular transformation patterns.
  • PAPER → GALAXYphase of pipeline— Direct path from a paper to a Galaxy gxformat2 workflow. No CWL intermediate.
  • Galaxy data-flow draft contractrelated mold— Defines the proposed boundary between Galaxy data-flow drafts, gxformat2 templates, and concrete step implementation.
  • Galaxy workflow draft formatrelated 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.