experimental
Experimental
Purpose
Browser/MITM, engine, network, binary, CUDA/PCIe, OS blueprints, and encrypt gateway — each with a status badge.
model decompileexperimentalmodel patchexperimental
Example
model code
model train dataset "examples/fixtures/train/dataset.jsonl" base "fixture-base" out "out/train/job-dry-001" backend "http" method "spark_distill_cpu" -> job
model status "job-dry-001" -> status
expect contains job fixture "examples/fixtures/train/want_accepted.txt"
expect contains status fixture "examples/fixtures/train/want_succeeded.txt"
Dry-run vs live
| Mode | Behavior |
|---|---|
| dry-run | Fixtures only. No GPU. No network. |
| live | Needs keys / trainer URL. Fail-loud on miss. |
Exit codes
| Exit | Meaning |
|---|---|
| 0 | success / expect pass |
| 1 | expect fail or language fail |
| 2 | usage / unknown method / missing program |
| 4 | credential unavailable or CAP miss |
What it does not do
Experimental pages do not claim production readiness. decompile and patch stay experimental until probe AUROC is at least 0.85.