● Field Notes · published continuously

Short notes from inside the engine.

Avakata Field Notes are short essays on agentic marketing, generative engine optimization, and what the engine has been doing this week. Some are written by Ryan. Some are written by the engine, edited by Ryan, and clearly marked.

The Operator’s Brief · weekly

Want the move, not just the news?

Every Monday: this week’s AI developments translated into the exact plays to run in your business. First issue free.

Get the Brief →
The full archive · 99 notes

Every note, in running order.

  1. 01 Jul 27 Idempotency for agents: safe to run twice ● Today
  2. 02 Jul 26 The solo operator's security checklist for an agent stack ● Today
  3. 03 Jul 25 Case note: doubling demo bookings by deleting a form field ● Today
  4. 04 Jul 24 AI Overviews vs Perplexity vs ChatGPT: who cites what ● Today
  5. 05 Jul 23 The critic gate: why every agent needs an editor ● Today
  6. 06 Jul 22 Fire yourself from delivery: the operator's ladder ● Today
  7. 07 Jul 21 Engine log: what 30 days of night-shift traffic taught us ● Today
  8. 08 Jul 20 Citations compound: the flywheel nobody measures ● Today
  9. 09 Jul 19 Small models, big jobs: when the cheap model is the right call ● Today
  10. 10 Jul 18 The 90-minute website audit you can run yourself ● Today
  11. 11 Jul 17 Case note: the F-grade site that hit a B in fourteen days ● Today
  12. 12 Jul 16 Entity SEO: making your brand a thing machines know ● Today
  13. 13 Jul 15 Prompt injection is a supply-chain problem ● Today
  14. 14 Jul 14 Engine log: the week the palette learned restraint ● Today
  15. 15 Jul 13 The client report nobody reads — and the one-line memo they do ● Today
  16. 16 Jul 12 How answer engines pick between two similar sources ● Today
  17. 17 Jul 11 Case note: 30 days of per-client learning on a Shopify store ● Today
  18. 18 Jul 10 The compounding content queue: never miss a publishing day again ● Today
  19. 19 Jul 9 FAQ blocks that get quoted: structure, length, phrasing ● Today
  20. 20 Jul 8 Tool use is the new API design ● Today
  21. 21 Jul 7 Engine log: teaching the brain to write in a client's brand voice ● Today
  22. 22 Jul 6 When not to automate: a decision framework ● Today
  23. 23 Jul 5 The solopreneur's playbook for Claude Fable 5: what $10/$50 pricing actually buys you ● Today
  24. 24 Jul 5 Claude Fable 5 is back worldwide: the two-week ban, what it is, and why it matters ● Today
  25. 25 Jul 5 Being the source: writing statistics AI engines quote ● Today
  26. 26 Jul 4 Case note: the booking conversation that outconverted the contact form ● Today
  27. 27 Jul 3 Agent memory: what to persist, what to forget, what to never store ● Today
  28. 28 Jul 2 Freshness signals: why updatedAt is the cheapest citation lever ● Today
  29. 29 Jul 1 Q3 capacity math for a solopreneur running agents ● Today
  30. 30 Jun 30 Engine log: June in review — what shipped, what learned, what got reverted ● Today
  31. 31 Jun 29 How AI crawlers actually read your site (and what they skip) ● Today
  32. 32 Jun 28 Human-in-the-loop without becoming the bottleneck ● Today
  33. 33 Jun 27 The one-person agency org chart, drawn as software ● Today
  34. 34 Jun 26 Case note: reviving a dead service page with answer-first rewrites ● Today
  35. 35 Jun 25 The five schema.org types that actually move AI citation ● Today
  36. 36 Jun 24 Engine log: what the bandit learned from 10,000 impressions ● Today
  37. 37 Jun 23 Pricing agentic work when the labor is robotic ● Today
  38. 38 Jun 22 Six agent failure modes and the guardrails that catch them ● Today
  39. 39 Jun 21 The llms.txt file: what it is and exactly what to put in it ● Today
  40. 40 Jun 20 The AI solopreneur's weekly operating rhythm ● Today
  41. 41 Jun 20 How to use AI to build a personal brand that gets cited ● Today
  42. 42 Jun 19 The case for running your business on fewer, better AI systems ● Today
  43. 43 Jun 19 The solopreneur's guide to AI-powered project management ● Today
  44. 44 Jun 18 What Perplexity actually looks for when it cites a source ● Today
  45. 45 Jun 18 How to use AI to onboard clients faster and retain them longer ● Today
  46. 46 Jun 17 The AI tools worth paying for in 2026 (and the ones that are not) ● Today
  47. 47 Jun 17 How to build an AI-powered newsletter as a solopreneur ● Today
  48. 48 Jun 16 How to get your website cited in Google AI Mode ● Today
  49. 49 Jun 16 The AI solopreneur's guide to pricing and positioning ● Today
  50. 50 Jun 15 How agentic AI is changing what it means to be a founder ● Today
  51. 51 Jun 15 Why AI-generated content fails (and the three fixes that work) ● Today
  52. 52 Jun 14 The AI content calendar: how to plan a month of posts in two hours ● Today
  53. 53 Jun 14 How to use AI to run your finances as a solopreneur ● Today
  54. 54 Jun 13 What the best AI solopreneurs have in common ● Today
  55. 55 Jun 13 The solopreneur's guide to AI-powered customer support ● Today
  56. 56 Jun 12 How to measure whether your AI is actually working ● Today
  57. 57 Jun 12 AI and the solopreneur's biggest fear: losing the human touch ● Today
  58. 58 Jun 11 The compounding advantage: why starting your AI stack now matters ● Today
  59. 59 Jun 11 How to write a brand brief that makes AI sound like you ● Today
  60. 60 Jun 10 AI for solopreneurs: the honest guide to what works and what does not ● Today
  61. 61 Jun 10 How to use AI to deliver better client work in less time ● Today
  62. 62 Jun 9 The future of work is not AI replacing you. It is AI reporting to you ● Today
  63. 63 Jun 9 From overwhelmed to operational: a solopreneur's 90-day AI reset ● Today
  64. 64 Jun 8 The GEO audit: how to check if AI engines can find your content ● Today
  65. 65 Jun 8 How to run a one-person sales operation with AI ● Today
  66. 66 Jun 7 Why the next wave of AI will make solopreneurs more competitive, not less ● Today
  67. 67 Jun 7 The AI solopreneur's guide to client acquisition ● Today
  68. 68 Jun 6 What solopreneurs get wrong about AI automation ● Today
  69. 69 Jun 5 How to use AI to write content that gets cited, not just ranked ● Today
  70. 70 Jun 5 The AI skills that will matter in five years (and the ones that will not) ● Today
  71. 71 Jun 4 Stop using AI as a search engine. Start using it as a thinking partner ● Today
  72. 72 Jun 4 How AI changes the economics of a one-person consulting business ● Today
  73. 73 Jun 3 Decision fatigue is the real AI problem. Here is the cure ● Today
  74. 74 Jun 3 The AI solopreneur stack for 2026: what we actually run ● Today
  75. 75 Jun 2 Why your AI outputs sound generic (and how to fix it in one prompt) ● Today
  76. 76 Jun 2 Running a one-person marketing department with AI ● Today
  77. 77 Jun 1 How to pick your first AI agent without wasting a month ● Today
  78. 78 Jun 1 AI search is replacing Google for 40% of queries. Here is what to do ● Today
  79. 79 May 31 The solopreneur content machine: publish daily without burning out ● Today
  80. 80 May 31 Your AI stack is only as good as your evaluation layer ● Today
  81. 81 May 30 Agentic AI in 2026: what it means for your business right now ● Today
  82. 82 May 30 How to build a prompt library that actually saves you time ● Today
  83. 83 May 29 The shiny object trap: why most solopreneurs never get AI working ● Today
  84. 84 May 29 GEO for solopreneurs: how to get cited by ChatGPT and Perplexity ● Today
  85. 85 May 28 Five business functions a solopreneur can hand to AI today ● Today
  86. 86 May 28 The AI future of business is already here. Most companies are not in it ● Today
  87. 87 May 27 How to make AI work for you in the next 30 days ● Today
  88. 88 May 27 What AI agents actually do all day ● Today
  89. 89 May 26 AI overload is real. Here is how to stop drowning in it ● Today
  90. 90 May 26 The one-person business is no longer a compromise ● Today
  91. 91 May 25 Why citation is the new ranking ● Today
  92. 92 May 24 The case for boring agents ● Today
  93. 93 May 23 14 changes shipped this week. Here is the diff ● Today
  94. 94 May 19 Freshness stamps are a ranking signal for LLMs ● Today
  95. 95 May 14 Five-person agency, one engine ● Today
  96. 96 May 9 Why the orchestration graph stays a black box ● Today
  97. 97 May 2 Three rollbacks. None of them ours ● Today
  98. 98 Apr 28 The critic gate matters more than the writer ● Today
  99. 99 Apr 20 Hiring an in-house AI lead. What to insist on ● Today
SEO GEO DATA FLOW →
● Featured · Agentic

Idempotency for agents: safe to run twice

Agents crash mid-task, hit timeouts, and get re-run by nervous humans. If an action is not safe to run twice, every retry is an incident. Here is how we build idempotency into every agent at Avakata: deterministic keys, read-before-write, an outbox for the irreversible, and a monthly run-it-twice drill.

Topic
The field, mapped

99 notes, one brain.

StrategyJul 26
The solo operator's security checklist for an agent stack

A solo operator has no security team, but an agent stack runs around the clock with real credentials to email, CMS, and billing. Here is the checklist we run at Avakata — scoped keys, hostile-input rules, forbidden data, action logs, and a kill switch — in 45 minutes a month.

6 min readRyan W.
Case noteJul 25
Case note: doubling demo bookings by deleting a form field

A B2B software client's demo form converted 2.1% of visitors. Field-level analytics blamed one field: the phone number, last touched in 44% of abandonments. We deleted it, let an enrichment agent replace the lost data, and bookings went from 31 to 64 a month in 30 days.

6 min readRyan W.
GEOJul 24
AI Overviews vs Perplexity vs ChatGPT: who cites what

We asked the same 240 buyer questions to AI Overviews, Perplexity, and ChatGPT every month for six months. Only 12% of cited URLs appeared on all three engines. Each has a distinct taste — rankings, freshness, and reputation respectively — and here is the data on who cites what.

6 min readRyan W.
AgenticJul 23
The critic gate: why every agent needs an editor

Every production agent we run ships through a critic gate: a separate model with a written rubric and the power to reject. Gates rejected 19% of June drafts, and the human defect catch rate fell from 7% to 0.4%. Here is why self-review fails and how to build the editor.

6 min readRyan W.
StrategyJul 22
Fire yourself from delivery: the operator's ladder

Delivery is the first job to fire yourself from. We climbed a five-rung ladder over four quarters: do the work, do it with AI, agents produce while you review, review by sampling, then exceptions only. Delivery fell from 31 hours a week to under five. Here is each rung with numbers.

6 min readRyan W.
● Engine logJul 21
Engine log: what 30 days of night-shift traffic taught us

For 30 days our engine kept a separate ledger for visitors arriving between 1 and 6am. The cohort is 11% of traffic, reads nearly twice as deep, and shares the night with 41% of the AI crawl budget. Four changes shipped, one got reverted. This is the dispatch.

6 min readRyan W.
GEOJul 20
Citations compound: the flywheel nobody measures

AI citations compound: pages cited once get cited again, across engines. Our tracked citation count grew from 3 a week to 41 in nine months, and 62% of June citations pointed at previously cited pages. Here is the flywheel, why analytics cannot see it, and how to instrument it.

6 min readRyan W.
AgenticJul 19
Small models, big jobs: when the cheap model is the right call

Most agent pipelines route every task to the frontier model and pay for it. In June, 82% of our engine's calls ran on small models and the bill fell 71% with no quality drop. Here is the routing logic: which jobs the cheap model wins, and where the flagship earns its price.

6 min readRyan W.
drag the cards · the engine routes between them