SparkLang · product loop

Compile. Inspect. Train. Serve. Share.

One Spark-native path from a reviewable .spark file to SPARK_BC, local dump, owned tiny coder steps, helpers on the wire, and docs on Pages — CLI first, GUI where it helps.

Five-step Spark loop diagram: compile, decompile, train, serve, share
Original Spark diagram — SPARK_BC orchestration bytecode, not imported neural weights.

Five steps, Spark tools

Inspired by clear CLI→inspect→publish loops elsewhere — rebuilt around our binaries, dumps, and measured model claims. No third-party branding on this page.

Compile / assemble SPARK_BC

Author a .spark program, then ./spark-bootstrap --compile (or open an existing pack). Output is Spark’s own SPARK_BC — orchestration ops like TRAIN / STEP, not a weight dump.

Compile docs · Builder · Opcodes / ISA

# Produce SPARK_BC from a Spark program
./spark-bootstrap --compile examples/spark_train_step.spark \
 -o out/spark-train-step.sparkbc

Decompile / dump / inspect locally

Primary SoT: tools/spark-bc-dump/dump.py — hex, header, mnemonics. One-shot project loop: ./helpers/spark-analyze → local out/analyze/<name>/ (dump, ops list, REPORT stub; optional --serve / --ask). Optional spark-bc-gui for a readable pane. Deterministic inspect first; LLM research is a separate, cited lane.

Decompile docs · Compete / scoreboard · Tools & helpers · Methods vs OpenBin · LLM research notes

# Local analysis folder — no upload
./helpers/spark-analyze docs/examples/spark-train-step.sparkbc
./helpers/spark-analyze examples/spark_train_step.spark --ask
Spark CLI dump.py output showing SPARK_BC hex and header
Spark CLI dump from `dump.py`.
Annotated spark-bc-gui view of SPARK_BC
Annotated spark-bc-gui — Spark / SparkLang only.
SVG mock of Spark dump and function panes using SPARK_BC capture style
IDE-ish panes mock built from Spark dump vocabulary (SPBC magic, TRAIN/STEP) — clearly Spark, not pseudo-C malware reverse engineering.

Voice ask the dump

After inspect, ask in text or speech — ears (STT) → dump context + owned TinyCoder → speaking (TTS). Local only; no OpenBin login. TinyCoder is tiny: dump facts stay SoT; open-ended RE answers carry a status note.

Voice ask docs · Voice / STT / TTS · Model aspects

# Text ask (no mic)
./spark-ask docs/examples/spark-train-step.sparkbc \
 --text "What opcodes are in this dump?"
# Voice loop — dry stub for CI; --mic for live
./spark-speak-ask docs/examples/spark-train-step.sparkbc --dry

Train / step / spark-coder / voice-easy

Run model trainmodel statusexpect in one file. Owned spark-coder is a tiny capability — useful for Spark factory loops, not a claim to beat frontier models.

Train voice / STT / TTS in 3 stepsVoice easy (./spark-voice easy): tiny CI default or --scale large on a consumer GPU (or CPU). Owned heads, trained locally.

Train loop · Spark coder · Voice easy · Model training

# Dry-run — fixtures, no keys
./spark --dry-run examples/train_eval.spark
# Voice easy (tiny / CI)
./spark-voice easy --dry
# Large opt-in
./spark-voice easy --scale large --device auto

Serve / helpers / shadows

Local HTTP surfaces for helpers and shadows — wire a trainer at SPARK_TRAIN_URL, probe serve APIs, keep dry-run as the default gate.

Serve · Tools & helpers

Docs / share (Pages)

Ship factory docs and examples on sparklang.dev (Cloudflare Pages). Share packs and captures from the gallery below — Spark-appropriate examples, not a malware community feed.

CI / Pages · Factory hub

Curated Spark programs and captures you can dry-run or open in the dump tools.

Start here