<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"><channel><title>Korey Dillon · Writing</title><description>Essays on the unit economics, governance, and failure modes of enterprise and agentic AI.</description><link>https://latentaxis.io/</link><language>en-us</language><item><title>The business case for AI has two numbers. Most people only produce one.</title><link>https://latentaxis.io/writing/two-numbers/</link><guid isPermaLink="true">https://latentaxis.io/writing/two-numbers/</guid><description>What an AI workflow returns and what it costs to run come from the same inputs. A method for forecasting both, with a ramp, a range, and a map of when run cost decides the case.</description></item><item><title>The unit economics problem in enterprise AI</title><link>https://latentaxis.io/writing/unit-economics/</link><guid isPermaLink="true">https://latentaxis.io/writing/unit-economics/</guid><description>Enterprises can see their AI bill but not their AI cost, and until spend maps to units of work, AI budgets are unforecastable.</description></item><item><title>What is a token, really?</title><link>https://latentaxis.io/writing/what-is-a-token/</link><guid isPermaLink="true">https://latentaxis.io/writing/what-is-a-token/</guid><description>A token is a metered unit of computation with a physical cost floor. Budgeting for AI starts with knowing what you are buying.</description></item><item><title>Prompting is cheap. Context is expensive.</title><link>https://latentaxis.io/writing/prompting-is-cheap/</link><guid isPermaLink="true">https://latentaxis.io/writing/prompting-is-cheap/</guid><description>In production agentic systems, the dominant costs and failure modes come from context management, not prompt wording.</description></item><item><title>Governance is the strategy, not the checkbox</title><link>https://latentaxis.io/writing/governance-is-the-strategy/</link><guid isPermaLink="true">https://latentaxis.io/writing/governance-is-the-strategy/</guid><description>Governance is the load-bearing element of AI strategy, and it has to be designed into the architecture before the first workflow ships.</description></item><item><title>What enterprise grade actually means for AI applications</title><link>https://latentaxis.io/writing/enterprise-grade/</link><guid isPermaLink="true">https://latentaxis.io/writing/enterprise-grade/</guid><description>The distance between an impressive AI demo and an enterprise application is not model quality. It is identity, observability, cost attribution, failure handling, and a named owner.</description></item><item><title>Compliance first</title><link>https://latentaxis.io/writing/compliance-first/</link><guid isPermaLink="true">https://latentaxis.io/writing/compliance-first/</guid><description>Auditability is a property of the architecture, not a feature added before launch. The work of making a system auditable and the work of making it correct are the same work.</description></item><item><title>Which workflows first</title><link>https://latentaxis.io/writing/which-workflows-first/</link><guid isPermaLink="true">https://latentaxis.io/writing/which-workflows-first/</guid><description>Rank candidate AI workflows on two axes, value returned per dollar of run cost and governance friction, and start in the corner that is labor-heavy and low-friction. The showcase candidates are usually in the wrong corner.</description></item><item><title>Build, buy, or partner, and the lock-in nobody budgets for</title><link>https://latentaxis.io/writing/build-buy-or-partner/</link><guid isPermaLink="true">https://latentaxis.io/writing/build-buy-or-partner/</guid><description>The expensive lock-in in enterprise AI is not the model but the untagged usage history, the prompt estate tuned to one vendor, and the evaluation suite that was never written. Vendor neutrality is an architecture property, and the right partner is one that helps you keep it.</description></item><item><title>Agents need a job description</title><link>https://latentaxis.io/writing/agents-need-a-job-description/</link><guid isPermaLink="true">https://latentaxis.io/writing/agents-need-a-job-description/</guid><description>An agent in production should be governed the way a new hire is: a written scope of authority, actions it may take alone and actions that need a signature, a manager who answers for it, and a way to take it off the floor.</description></item><item><title>The first ninety days of an AI program</title><link>https://latentaxis.io/writing/first-ninety-days/</link><guid isPermaLink="true">https://latentaxis.io/writing/first-ninety-days/</guid><description>A new AI leader should spend the first quarter on inventory, instrumentation, and one paved road, not on a flagship build. The organizations that start with a showcase spend the second year rebuilding it.</description></item><item><title>Training is not adoption</title><link>https://latentaxis.io/writing/training-is-not-adoption/</link><guid isPermaLink="true">https://latentaxis.io/writing/training-is-not-adoption/</guid><description>Enterprise AI capability is built by certifying people against shipped, governed work, not by seat licenses and lunch-and-learns. Enablement is a delivery discipline with its own metrics.</description></item><item><title>One paved road, many workflows</title><link>https://latentaxis.io/writing/one-paved-road/</link><guid isPermaLink="true">https://latentaxis.io/writing/one-paved-road/</guid><description>Enterprise AI compounds only when it is run as a platform: tenancy, a shared gateway, approved patterns, and a release gate. Run as a sequence of projects, every workflow pays the full cost of the first.</description></item><item><title>Five tags on every model call</title><link>https://latentaxis.io/writing/five-tags/</link><guid isPermaLink="true">https://latentaxis.io/writing/five-tags/</guid><description>A five-field telemetry schema, decided before the first workflow ships, serves finance, compliance, and quality at once. It is the cheapest architectural decision an AI program will make and the most expensive to retrofit.</description></item><item><title>Scope before you build</title><link>https://latentaxis.io/writing/scope-before-you-build/</link><guid isPermaLink="true">https://latentaxis.io/writing/scope-before-you-build/</guid><description>How tightly framing the problem decides whether an AI project ships or stalls.</description></item><item><title>Silent failures</title><link>https://latentaxis.io/writing/silent-failures/</link><guid isPermaLink="true">https://latentaxis.io/writing/silent-failures/</guid><description>The most dangerous bugs in AI systems are the ones that return a confident, wrong answer.</description></item><item><title>Exact over approximate</title><link>https://latentaxis.io/writing/exact-over-approximate/</link><guid isPermaLink="true">https://latentaxis.io/writing/exact-over-approximate/</guid><description>Why I default to exact search in production retrieval, keep it as a ground-truth oracle, and treat approximate search as a decision to justify with numbers.</description></item></channel></rss>