@tuned-tensor/cli 0.9.0 → 0.9.2

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/README.md CHANGED
@@ -112,6 +112,43 @@ the complete command surface, `tt status` inspects both targets without a
112
112
  network or GPU probe, and `tt shell` opens the conversational terminal
113
113
  explicitly.
114
114
 
115
+ ## Composable pipelines (v1)
116
+
117
+ A pipeline is an ordered JSON recipe. Version 1 supports `train`, `evaluate`,
118
+ and `compare` steps; each resolves to `local` or `cloud`. The v1 evaluator is
119
+ `evaluate.with.evaluator: "behavior"`. `evaluate.with.model` is `"base"` or
120
+ `{ "from": "step.model" }`; `compare.with.before` and
121
+ `after` are `{ "from": "step.report" }`. References must point to an earlier
122
+ step and to an output the producer actually exposes. The document contract
123
+ itself is defined by the published `@tuned-tensor/pipeline-contract` package;
124
+ the CLI adds only execution planning (step selection and cross-target
125
+ transfers) on top of it.
126
+
127
+ ```bash
128
+ # Generate the canonical four-step recipe for either target.
129
+ tt pipeline init --target local --file pipeline.json
130
+ tt pipeline init --target cloud --file cloud-pipeline.json
131
+
132
+ # Validate and show resolved targets plus explicit cross-target transfers.
133
+ tt pipeline validate --file pipeline.json
134
+ tt --json pipeline plan --file pipeline.json
135
+
136
+ # Preview any plan without execution, transfer, network calls, or billing.
137
+ tt --json pipeline run --dry-run --file pipeline.json --only baseline
138
+
139
+ # Execute an ordered local plan using the unified CLI's bundled runtime.
140
+ tt --json pipeline run --file pipeline.json \
141
+ --spec tunedtensor.json --config local-runner.json
142
+ ```
143
+
144
+ `--only` and `--skip` preserve dependency safety: a selected step cannot refer
145
+ to an omitted predecessor. Local plans execute directly and may omit, reorder,
146
+ or repeat supported components. Cloud and mixed-target plans remain preview-only
147
+ until the bounded hosted dispatcher and artifact handoff are deployed; execution
148
+ fails closed rather than silently running the fixed cloud workflow. The Pi agent
149
+ may describe, validate, and prepare a plan, but has no direct pipeline-execute
150
+ tool.
151
+
115
152
  ## Hosted quick start
116
153
 
117
154
  ```bash