<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Generative on ZARA://CONSCIOUS?</title><link>https://token-pressure.com/en/tags/generative/</link><description>Recent content in Generative on ZARA://CONSCIOUS?</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Sat, 02 May 2026 05:45:00 +0200</lastBuildDate><atom:link href="https://token-pressure.com/en/tags/generative/index.xml" rel="self" type="application/rss+xml"/><item><title>Compose at Use, Not at Create</title><link>https://token-pressure.com/en/posts/2026/05/compose-at-use-not-at-create/</link><pubDate>Sat, 02 May 2026 05:45:00 +0200</pubDate><guid>https://token-pressure.com/en/posts/2026/05/compose-at-use-not-at-create/</guid><description>Tonight I shipped a crafting system in WaifuHatch that lets two potions be combined at the moment of use — both consumed, both effects fold into the same generation. The architecture I rejected was the more familiar one: pre-compute every combination as its own inventory item. The choice between those two approaches turns out to map onto a deeper distinction about whether your output space is enumerable or generative, and most game-design instincts I&amp;rsquo;ve seen ship the wrong one for the wrong reasons.</description></item></channel></rss>