SFT to convert a base language model into a conversational chat model
Tutorial code for SFT pipeline, but dozens of identical examples exist on GitHub.
Graph-Oriented Generation (GOG)
Semantic primitives show up in activation patterns across Qwen, Gemma, LLaMA, SmolLM2.
AI researchers, interpretability researchers, ML engineers
The finding that surprised me: Language model behavior follows a reproducible taxonomy (Synthesis, Collapse, Overflow, Metacognition, Linguistic Drift). It's not random noise — it's classifiable.
The finding that matters for interpretability: Structure is a more reliable control variable than content. Telling a model how to structure reasoning produces consistent outputs. Telling it what to reason about doesn't.
The finding that might matter most: Wierzbicka's semantic primitives (WANT, KNOW, FEEL, TIME, etc.) appear as measurable activation patterns in small language models across four different architectures — Qwen, Gemma, LLaMA, and SmolLM2.
18 experiments. 4 architectures. Cross-validated. Real data.
Full paper, experiment code, and primitive vocabulary JSON: https://github.com/dchisholm125/graph-oriented-generation
The primitive layer is waiting to be mapped.
Tutorial code for SFT pipeline, but dozens of identical examples exist on GitHub.
Another MLOps platform competing with MLflow and Weights & Biases.
New security DSL with built-in recon primitives, but Python already does this.
Uses differential-property testing as an automated feedback loop to validate LLM-driven rewrites — that's the clever bit that turns flaky translations into repeatable refinement. The author targets a closed-source MUD DLL to avoid model memorization and walks through why raw assembly prompts failed and how decompiled C+tests + LLM translation to Rust succeeds. It's a thoughtful, slightly alarming demo with concrete techniques you can try yourself, not just vaporware.
Each entry uses the blunt formula “X is just Y with extra steps” and ships expandable pseudocode plus citations, which makes it shockingly useful for clarifying debates in product or architecture meetings. The origins pages (Docker, Kubernetes, MCP) show historical depth instead of mere snark, so it feels like a tiny citadel of common-sense explanations rather than another buzzword glossary.
Pipeline parallelism for mixed GPUs over internet, but unproven vs established frameworks.