<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>World-Models on Step Into Dev</title><link>https://stepinto.dev/tags/world-models/</link><description>Recent content in World-Models on Step Into Dev</description><generator>Hugo</generator><language>en-gb</language><lastBuildDate>Tue, 07 Jul 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://stepinto.dev/tags/world-models/index.xml" rel="self" type="application/rss+xml"/><item><title>The World Model Equation Is a WHERE Clause</title><link>https://stepinto.dev/posts/world-models-102/</link><pubDate>Tue, 07 Jul 2026 00:00:00 +0000</pubDate><guid>https://stepinto.dev/posts/world-models-102/</guid><description>&lt;p&gt;The &lt;a href="https://stepinto.dev/posts/world-models-101/"&gt;first code post&lt;/a&gt; in this series opened with a jab at explanations that lead with &amp;ldquo;a conditional probability, a subscript, a latent variable, and half the audience gone by paragraph three&amp;rdquo;. I also promised the maths would eventually arrive, once it described something you&amp;rsquo;d already watched run. This post makes good on that: it takes exactly those three scary things, one at a time, and shows that you&amp;rsquo;ve been writing all of them in TypeScript for years under different names.&lt;/p&gt;</description></item><item><title>A World Model in Forty Lines of TypeScript</title><link>https://stepinto.dev/posts/world-models-101/</link><pubDate>Mon, 06 Jul 2026 00:00:00 +0000</pubDate><guid>https://stepinto.dev/posts/world-models-101/</guid><description>&lt;p&gt;Every explanation of world models I&amp;rsquo;ve read starts the same way. A conditional probability, a subscript, a latent variable, and half the audience gone by paragraph three. Which is a shame, because the core idea fits in a few lines of code and most working programmers already have the intuition. They&amp;rsquo;ve just never had it pointed at.&lt;/p&gt;
&lt;p&gt;So this series starts with TypeScript. We&amp;rsquo;ll get to the equations eventually, but only once they&amp;rsquo;re describing something you&amp;rsquo;ve already watched run. (If you&amp;rsquo;d rather have today&amp;rsquo;s ideas with no code at all, the &lt;a href="https://stepinto.dev/posts/world-models-001/"&gt;previous post&lt;/a&gt; covers the same ground in prose.)&lt;/p&gt;</description></item><item><title>Your Time Series Is Already Training Data</title><link>https://stepinto.dev/posts/world-models-001/</link><pubDate>Sun, 05 Jul 2026 00:00:00 +0000</pubDate><guid>https://stepinto.dev/posts/world-models-001/</guid><description>&lt;p&gt;At &lt;a href="https://getunimo.com"&gt;Unimo&lt;/a&gt; we spend our days watching telemetry from energy hardware. Temperatures, states of charge, power flows, a reading every few seconds from devices sitting in buildings we&amp;rsquo;ll never visit. Alongside the readings sits a second stream that gets far less attention: the commands. Turn this on. Back that off. Hold here.&lt;/p&gt;
&lt;p&gt;For years I thought of those two streams as operations data. You keep them so you can draw dashboards, catch faults, and win arguments about what actually happened last Tuesday. Then I started reading about world models, and it slowly dawned on me that we&amp;rsquo;d been sitting on something else entirely. Interleave the two streams and you get a long record of &lt;em&gt;the world was like this, we did that, and here is what happened next&lt;/em&gt;. That record is exactly what a world model is trained on. We hadn&amp;rsquo;t been keeping logs. We&amp;rsquo;d been keeping lessons.&lt;/p&gt;</description></item></channel></rss>