From: Cameron Otsuka Date: Thu, 18 Jun 2026 22:19:02 +0000 (-0700) Subject: fix link X-Git-Url: https://git.otsuka.systems/?a=commitdiff_plain;h=8e4e5c0a7b28d4a18dca9323b4a8a3ddf4eed022;p=cotsuka.github.io fix link --- diff --git a/content/articles/from-ai-tools-to-ai-loops/index.mdx b/content/articles/from-ai-tools-to-ai-loops/index.mdx index 29feb4b..bbf781a 100644 --- a/content/articles/from-ai-tools-to-ai-loops/index.mdx +++ b/content/articles/from-ai-tools-to-ai-loops/index.mdx @@ -2,7 +2,7 @@ title: From AI Tools to AI Loops type: newsletter date: 2026-06-09 -modified: 2026-06-10 +modified: 2026-06-18 description: The move away from prompting and towards crafting the AI ouroboros. publication: name: Inference Draft @@ -23,7 +23,7 @@ import ouroboros from './from-ai-tools-to-ai-loops.png'; alt="Robot Ouroboros Artwork" /> -I wrote [last week](03%20Projects/Inference%20Draft/2026/Tokenmaxxing%20as%20Management%20Theory.md) about tokenmaxxing as the awkward adoption phase of AI inside companies: first you get everyone using the tool, then you figure out whether any of that usage is actually enhancing output. +I wrote [last week](/articles/2026-06-02-tokenmaxxing-as-management-theory/) about tokenmaxxing as the awkward adoption phase of AI inside companies: first you get everyone using the tool, then you figure out whether any of that usage is actually enhancing output. Looping is the next phase. The question is no longer, "Can an employee use AI at each step of the workflow?" The question becomes, "Can the *entire workflow* turn into an automated loop?"