Indexes
An index holds documents ingested from an external system — a PIM, ERP, CMS, or anything else that can push JSON. Each document is a record: one product, one article, one row. Speedtrain reads indexes; it never writes back to them. Documents are managed by whoever pushes them in. Find them under Content sources → Indices.Stage outputs
A stage output is the content one task configuration has produced. Feeding it into a second task is how you chain jobs:The input is chosen at session time
This is the design decision worth internalising: a task configuration does not name its input. The input is bound when a review session starts. One configuration can therefore run over different indexes, over a filtered subset of an index, or over another task’s output, with no change to the configuration itself. When starting a session you choose between:Index
Index
A raw index, optionally narrowed by a selection predicate so the session covers only part of it.
Stage output
Stage output
Another task’s output. By default this means that task’s published version, accepted items only.
Prior session
Prior session
The exact outputs of one specific past run. Useful for pipeline testing, because stage two then consumes precisely what a chosen stage-one session accepted.
Testing sessions get the richer options — selection predicates, version selectors, filters. Real review sessions are deliberately stricter: they identify the feed and nothing else, so what runs in production is unambiguous.
Document shape
A document is whatever JSON you push. Use your source system’s own field names. One key is reserved: a top-level$images array attaches pictures to the record, so that a vision-capable model can see them. Add a content source