@tuned-tensor/cli 0.9.0 → 0.9.1
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 +34 -0
- package/dist/chunk-DAP2Z7EZ.js +4400 -0
- package/dist/chunk-DAP2Z7EZ.js.map +1 -0
- package/dist/index.js +324 -70
- package/dist/index.js.map +1 -1
- package/dist/local-runtime.js +1630 -0
- package/dist/local-runtime.js.map +1 -0
- package/docs/local-runtime/architecture.md +91 -0
- package/docs/local-runtime/spark.md +107 -0
- package/examples/local-runtime/dry-runner.json +14 -0
- package/examples/local-runtime/general-regression.jsonl +4 -0
- package/examples/local-runtime/local-runner.json +25 -0
- package/examples/local-runtime/smoke-spec.json +41 -0
- package/package.json +15 -5
- package/training/local-runner/pyproject.toml +25 -0
- package/training/local-runner/src/evaluate.py +274 -0
- package/training/local-runner/src/model_contract.py +47 -0
- package/training/local-runner/src/prefetch.py +192 -0
- package/training/local-runner/src/serve.py +272 -0
- package/training/local-runner/src/sft_data.py +97 -0
- package/training/local-runner/src/train.py +289 -0
- package/training/local-runner/uv.lock +1204 -0
package/README.md
CHANGED
|
@@ -112,6 +112,40 @@ 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.
|
|
123
|
+
|
|
124
|
+
```bash
|
|
125
|
+
# Generate the canonical four-step recipe for either target.
|
|
126
|
+
tt pipeline init --target local --file pipeline.json
|
|
127
|
+
tt pipeline init --target cloud --file cloud-pipeline.json
|
|
128
|
+
|
|
129
|
+
# Validate and show resolved targets plus explicit cross-target transfers.
|
|
130
|
+
tt pipeline validate --file pipeline.json
|
|
131
|
+
tt --json pipeline plan --file pipeline.json
|
|
132
|
+
|
|
133
|
+
# Preview any plan without execution, transfer, network calls, or billing.
|
|
134
|
+
tt --json pipeline run --dry-run --file pipeline.json --only baseline
|
|
135
|
+
|
|
136
|
+
# Execute an ordered local plan using the unified CLI's bundled runtime.
|
|
137
|
+
tt --json pipeline run --file pipeline.json \
|
|
138
|
+
--spec tunedtensor.json --config local-runner.json
|
|
139
|
+
```
|
|
140
|
+
|
|
141
|
+
`--only` and `--skip` preserve dependency safety: a selected step cannot refer
|
|
142
|
+
to an omitted predecessor. Local plans execute directly and may omit, reorder,
|
|
143
|
+
or repeat supported components. Cloud and mixed-target plans remain preview-only
|
|
144
|
+
until the bounded hosted dispatcher and artifact handoff are deployed; execution
|
|
145
|
+
fails closed rather than silently running the fixed cloud workflow. The Pi agent
|
|
146
|
+
may describe, validate, and prepare a plan, but has no direct pipeline-execute
|
|
147
|
+
tool.
|
|
148
|
+
|
|
115
149
|
## Hosted quick start
|
|
116
150
|
|
|
117
151
|
```bash
|