taskforce-model-foundry
Train, evaluate, resume, and export local models with Taskforce Model Foundry. Use for tmf CLI jobs, HF/PEFT fine-tuning, independent quality gates, and OpenClaw or Hermes model-customization workflows.
Taskforce Model Foundry
-
Establish the job contract: dataset provenance, allowed compute host, backend, model path, resource/time budget, independent holdout, and quality thresholds. Default to synthetic data and local CPU. Obtain task-specific authorization before private data, paid compute, remote transfers, production changes, or publishing. Finish with a recorded scope and success criteria.
-
Locate a trusted installation using the command reference. Run version, doctor, and backends checks. Doctor can return success while a missing config is only a warning: validate the actual config separately. Finish with the executable, version, usable backend, and validated config known.
-
Prepare an isolated project directory. Use
initonly for a new synthetic project; for an existing project inspect its configuration before changing it. Keep data outside this skill directory. For HF/PEFT select an existing local model and a dedicated Python environment; inspectdocs/tutorial.mdin the installation for current config fields. Do not invent model download or GPU setup commands. Finish with licensed/provenanced data and disjoint splits. -
Fix the evaluation policy before training.
eval.gatesreplaces the default list in full; validate it, and preserve the approved thresholds. A tiny fixture with fixture-specific gates validates plumbing, not business quality. Finish with a recorded baseline, holdout policy, and explicit gate list or defaults. -
Assign a stable job ID, inspect durable status, then train. After a timeout or disconnected session, query the execution host's durable state before retrying; resume the same job rather than submitting a duplicate. Cancellation uses SIGINT/SIGTERM and exit 130; resume an intentionally cancelled job only when authorized to continue. Finish with durable succeeded, cancelled, or failed state and the actual process exit code, not just a launched-process receipt.
-
Evaluate baseline and tuned model on the independent holdout. Check leakage, sample counts, actual parameter changes, and each declared gate. Treat failed evaluation as a failed deliverable; diagnose it instead of weakening gates after seeing results. Finish with the report path, metrics, and gate verdict.
-
Export only a passing job, preferably pinning its reviewed evaluation report. Verify
checksums.txtfrom the bundle directory. HF/PEFT exports include adapter bytes but reference the local base model: record its identity and availability. Finish with bundle path, digest, lineage, checksum results, and base dependency. -
Report measured results separately from unsupported or unverified capabilities. Read capability and host boundaries before making GPU, remote execution, recovery, or production claims. Include test pass/fail/ skip counts; a skipped test is not a pass. Publishing requires its own actual registry/release and installation verification. Finish with evidence paths, remaining limits, and whether the artifact is local, published, or deployed.
- Downloads
- 72All time
- Security audit
- Pass
- Last updated
- 1d ago
- Current version
- v0.1.0
- License
- MIT-0
