<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Decision-Framework on Adrian Spiridon</title><link>https://adrianspiridon.dev/tags/decision-framework/</link><description>Recent content in Decision-Framework on Adrian Spiridon</description><generator>Hugo</generator><language>en-US</language><lastBuildDate>Fri, 04 Sep 2026 00:00:00 +0300</lastBuildDate><atom:link href="https://adrianspiridon.dev/tags/decision-framework/index.xml" rel="self" type="application/rss+xml"/><item><title>Build-Time vs Runtime AI: An Instruction–Data Variability Framework</title><link>https://adrianspiridon.dev/blog/build-time-vs-runtime-ai/</link><pubDate>Fri, 04 Sep 2026 00:00:00 +0300</pubDate><guid>https://adrianspiridon.dev/blog/build-time-vs-runtime-ai/</guid><description>Not every feature that can use AI should keep AI in the runtime path. A useful distinction is whether the task and input space can be specified at design time. If they can, deterministic software is usually the better runtime architecture; if either remains open-ended, runtime AI starts to earn its place.</description></item></channel></rss>