real

Core

Purpose

Lexical rules, let/print, expect gates, pipelines, and include. This is the smallest useful .spark surface.

  • let fixture-only
  • print fixture-only
  • expect fixture-only
  • pipeline fixture-only
  • include fixture-only

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

ModeBehavior
dry-runFixtures only. No GPU. No network.
liveNeeds keys / trainer URL. Fail-loud on miss.

Exit codes

ExitMeaning
0success / expect pass
1expect fail or language fail
2usage / unknown method / missing program
4credential unavailable or CAP miss

What it does not do

Does not train models or call external AI.