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 29feb4b64e06beb18599cda4c6e922f3f671652c..bbf781add0db969aa4de1dc6084b8a09ddf1e93f 100644 (file)
--- 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?"