Task Output Space
A task output space defines what values a model is allowed to produce. It is the difference between predicting a class, a scalar, a ranked list, a sequence, a mask, a box, a graph, coordinates, an answer, or an action.
A task can be written as:
where is the input space and is the output space.
If only some outputs are valid for an input , define:
where is the validity function.
Common Output Spaces
- Class label: .
- Scalar or vector: .
- Ranked list: with ordered candidates.
- Retrieved set: .
- Sequence: with syntax or vocabulary constraints.
- Spatial object: box, mask, keypoints, segmentation map, or dense field.
- Graph: nodes, edges, labels, or generated graph structure.
- Coordinates: with geometric constraints.
- Action: tool call, policy action, plan step, or control command.
Loss and Metric Implications
Changing changes the loss and metric:
where is the training loss, is the metric set, and is the validity check.
For example, a generated molecule string can be scored by token loss, validity, uniqueness, property prediction, docking score, or downstream assay relevance. These are not interchangeable.
The output space should be interpreted together with Modality-task map, because the same raw modality can produce a class, scalar, ranking, sequence, mask, graph, coordinates, or action depending on the task.
Changing the output space usually changes Metric selection and the relevant failure modes.
Checks
- What exactly is one target output?
- Is the output independent, ranked, sequential, spatial, temporal, geometric, graph-structured, or an action?
- What makes an output invalid?
- Are invalid outputs filtered, repaired, penalized, or counted as failures?
- Does the metric score local pieces, whole-object validity, utility, or human preference?
- Does decoding or post-processing change the effective output space?