<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Automation on oceanheart.ai</title>
    <link>https://www.oceanheart.ai/tags/automation/</link>
    <description>Recent content in Automation on oceanheart.ai</description>
    <generator>Hugo</generator>
    <language>en-gb</language>
    <lastBuildDate>Sat, 25 Jul 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://www.oceanheart.ai/tags/automation/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Pattern before automation</title>
      <link>https://www.oceanheart.ai/blog/2026-07-25-pattern-before-automation/</link>
      <pubDate>Sat, 25 Jul 2026 00:00:00 +0000</pubDate>
      <guid>https://www.oceanheart.ai/blog/2026-07-25-pattern-before-automation/</guid>
      <description>&lt;p&gt;This morning I asked an agent to prepare five job applications in five browser tabs. It filled the forms, attached role-specific CVs and cover letters, and stopped before submission so that I could review each one.&lt;/p&gt;&#xA;&lt;p&gt;That sounds like an automated workflow. It wasn&amp;rsquo;t, and that was the point.&lt;/p&gt;&#xA;&lt;p&gt;I was operating the pipeline with the agent, watching what happened in each form and correcting the working rules as we went. Some sites wanted a PDF cover letter, one wanted text in a native field, and another had no place for a cover letter at all. Questions about location, work authorisation, notice period, office attendance, education, and demographics repeated across employers, but rarely with identical wording or options. One form timed out and had to be filled again. Another accepted the application only when I drove the final step.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
