Pipeline Composition

Runnable composition lane

Composition examples show how Golden turns small typed pieces into reusable robot-facing graphs without inventing a second runtime. Use this page after the core Flow and Pipeline concepts are clear.

First runnable example

Run the public composition smoke before reading the contracts.

pixi run -e golden-local demo-composable-pipelines

Expected result

The example composes typed modules, resolves registry-backed payloads, and keeps the resulting graph inspectable through the IR and visualization path.

=== Extend Declared Pipeline ===
internal flows: ['counter', 'policy']
policy output after replacement: ProcOut(value=104)

=== Compose Pipeline As Flow ===
[outer] value=5 aux=99
wrapped stage output: Golden_Composable_CounterOutput(aux=99, value=5)

What This Demonstrates

ComposeTyped modules become a graph

Examples can start from small Flows and still expose a single runnable pipeline boundary.

SharePayloads stay registry-backed

Robot state, belief, plans, and commands use named payloads instead of ad hoc dict glue.

InspectThe graph remains visible

The same composition can be rendered as runtime IR or a browser HTML graph artifact.

Public Boundary

This is the public composition lane. A composition example belongs here only when it has a named task, expected output, dependency story, and docs page. Older source folders can remain implementation references without becoming launch paths.

Render the graphUse the HTML visualization lane to inspect the composed pipeline.Check contractsReview composite Flow I/O and field-access rules.