Next Work

Roadmap and Boundaries

The roadmap focuses on proof-first expansion: stabilize the .slm runtime, improve tokenizer coverage, stage candidate models, deepen adapters, and expand browser-local composition only after validation.

Explore architecture Markdown view

Near-term

Keep the site honest about current implementation: one local runtime path, strict .slm validation, q8/q4 models, deterministic fixtures, adapter stack proof, selector registry routing, and clear diagnostics.

Improve public docs
Keep llms files aligned
Publish support matrix
Add evidence-oriented examples

Middle-term

Expand model candidates and tokenizer handling where the runtime can prove compatibility. Add more concrete demonstrations of Pythia, Llama-style, low-vocabulary, tied-output, and BPE paths only when conversion and smoke evidence exist.

Tokenizer matrix
Candidate model table
Browser demo evidence
Evaluation sidecars

Future lanes

Future work can explore multi-model routing, richer adapter ecology, OPFS persistence, Web Workers, WebGPU comparison, fixed-point deterministic math, and skill-package routing. Each lane needs a manifest, validator, test, and public-claim boundary.

Multi-model routing
OPFS cache
Worker isolation
WebGPU comparison
Fixed-point fallback

Plain PHP deployment notes

No WordPress bootstrap, theme system, database requirement, composer package, npm build, CDN script, Bootstrap class dependency, or jQuery dependency.

Routes are handled by index.php and server rewrites. Core content lives in data/pages.php. HTML and Markdown share the same page data.

Upload the package to the subdomain root, point Apache/Nginx to the folder, and keep .htaccess enabled for clean routes on Apache.