<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Gabriel Abreu · Blog</title>
    <link>https://gabeonchain.vercel.app/blog.html</link>
    <atom:link href="https://gabeonchain.vercel.app/feed.xml" rel="self" type="application/rss+xml"/>
    <description>Articles and essays on AI engineering, product marketing, and building onchain.</description>
    <language>en</language>
    <lastBuildDate>Sun, 12 Jul 2026 22:41:15 GMT</lastBuildDate>
    <item>
      <title>the fence is the job</title>
      <link>https://gabeonchain.vercel.app/posts/the-fence-is-the-job.html</link>
      <guid isPermaLink="true">https://gabeonchain.vercel.app/posts/the-fence-is-the-job.html</guid>
      <pubDate>Wed, 08 Jul 2026 12:00:00 GMT</pubDate>
      <category>AI Engineering</category>
      <category>Opinion</category>
      <description>Anthropic's new agent certification and the agents-as-labor market are pricing the same skill, and it isn't prompting. Four questions that decide where your agent stops, and why that boundary is the job.</description>
    </item>
    <item>
      <title>if ai writing is slop, explain to me how it keeps winning literary prizes</title>
      <link>https://gabeonchain.vercel.app/posts/ai-slop-literary-prizes.html</link>
      <guid isPermaLink="true">https://gabeonchain.vercel.app/posts/ai-slop-literary-prizes.html</guid>
      <pubDate>Mon, 29 Jun 2026 12:00:00 GMT</pubDate>
      <category>AI Engineering</category>
      <category>Opinion</category>
      <description>You think AI writing isn't good enough yet. So explain how a story that may have been AI-written just won a literary prize, and the experts couldn't tell. Slop was never the argument, provenance is, and the structure already gives it away.</description>
    </item>
    <item>
      <title>is your AI's knowledge base growing, or just getting bigger?</title>
      <link>https://gabeonchain.vercel.app/posts/knowledge-base-growing-or-bigger.html</link>
      <guid isPermaLink="true">https://gabeonchain.vercel.app/posts/knowledge-base-growing-or-bigger.html</guid>
      <pubDate>Mon, 01 Jun 2026 12:00:00 GMT</pubDate>
      <category>AI Engineering</category>
      <category>Opinion</category>
      <description>An unread page in your knowledge base isn't neutral clutter, it's latent poison. The day your agent pulls it, the stale page becomes the answer. Five steps to measure what your agents actually read, not just what they write.</description>
    </item>
    <item>
      <title>your AI doesn't have a prompting problem</title>
      <link>https://gabeonchain.vercel.app/posts/context-window-theater.html</link>
      <guid isPermaLink="true">https://gabeonchain.vercel.app/posts/context-window-theater.html</guid>
      <pubDate>Mon, 01 Jun 2026 12:00:00 GMT</pubDate>
      <category>AI Engineering</category>
      <category>Marketing</category>
      <category>Opinion</category>
      <description>You didn't write a bad prompt. The AI reached for whatever it could find. But what it found was a mess. Context-window theater: the performance of knowing your brand and sounding like it gets the strategy. You cannot prompt your way out of a context problem.</description>
    </item>
    <item>
      <title>Photography didn't kill painting, and AI won't kill writing.</title>
      <link>https://gabeonchain.vercel.app/posts/ai-wont-kill-writing.html</link>
      <guid isPermaLink="true">https://gabeonchain.vercel.app/posts/ai-wont-kill-writing.html</guid>
      <pubDate>Mon, 01 Jun 2026 12:00:00 GMT</pubDate>
      <category>Opinion</category>
      <category>AI Engineering</category>
      <description>In 1839 a painter saw a photograph and declared painting dead. He was right about the threat, wrong about the meaning. The same error runs through the AI-writing panic: writing was always two jobs, and AI only took one. Why it owns the commodity tier (MIT: 40% faster) and structurally cannot do the creative one (the NeurIPS 'hivemind').</description>
    </item>
    <item>
      <title>Did all the NFT folks just become AI folks?</title>
      <link>https://gabeonchain.vercel.app/posts/did-all-the-nft-folks-become-ai-folks.html</link>
      <guid isPermaLink="true">https://gabeonchain.vercel.app/posts/did-all-the-nft-folks-become-ai-folks.html</guid>
      <pubDate>Fri, 01 May 2026 12:00:00 GMT</pubDate>
      <category>Opinion</category>
      <category>Web3</category>
      <description>I caught myself hyping an AI agent with the same energy I used to hype a Solana mint. A personal round-trip through the NFT cycle and into the AI one, the Ovols win, the VC-round loss, and what actually transfers between cycles.</description>
    </item>
    <item>
      <title>The more an AI agent can DO, the more it can BREAK</title>
      <link>https://gabeonchain.vercel.app/posts/the-more-an-ai-agent-can-do-the-more-it-can-break.html</link>
      <guid isPermaLink="true">https://gabeonchain.vercel.app/posts/the-more-an-ai-agent-can-do-the-more-it-can-break.html</guid>
      <pubDate>Fri, 01 May 2026 12:00:00 GMT</pubDate>
      <category>AI Engineering</category>
      <description>A year of running multi-agent systems in production, and the failure that keeps costing real money isn't reasoning, it's writes. Traced across METR, Anthropic, Cognition Labs, Karpathy, and the MCP spec: capability grows easily, write-side reliability does not.</description>
    </item>
    <item>
      <title>How I stopped winging it on evals</title>
      <link>https://gabeonchain.vercel.app/posts/how-i-stopped-winging-it-on-evals.html</link>
      <guid isPermaLink="true">https://gabeonchain.vercel.app/posts/how-i-stopped-winging-it-on-evals.html</guid>
      <pubDate>Fri, 01 May 2026 12:00:00 GMT</pubDate>
      <category>AI Engineering</category>
      <description>Opened inspect-ai expecting validation. Got an 87% success rate on a morning brief I thought was rock solid. Eval discipline turned debugging from personal defense into data collection, and that mattered more than any model upgrade.</description>
    </item>
    <item>
      <title>The 4 Lines Every AI Harness Needs</title>
      <link>https://x.com/gabe_onchain/status/2053136017230590305</link>
      <guid isPermaLink="false">https://x.com/gabe_onchain/status/2053136017230590305</guid>
      <pubDate>Fri, 01 May 2026 12:00:00 GMT</pubDate>
      <category>AI Engineering</category>
      <description>Identity, constraints, voice, memory. Four fields that turn a system prompt into a persistent identity document. Why agents drift across sessions, why Claude.md works, and how the harness pattern scales the same structure from one specialized worker to thirty.</description>
    </item>
    <item>
      <title>The 5-Layer Architecture of Claude Code (And the One That Will Break You)</title>
      <link>https://x.com/gabe_onchain/status/2051339230043910350</link>
      <guid isPermaLink="false">https://x.com/gabe_onchain/status/2051339230043910350</guid>
      <pubDate>Fri, 01 May 2026 12:00:00 GMT</pubDate>
      <category>AI Engineering</category>
      <description>Five architectural layers of Claude Code: CLAUDE.md, Skills, Hooks, Subagents, Plugins. Layer 3 fails silently. Hook files sit on disk unregistered in settings.json, dead code that thought it was alive.</description>
    </item>
    <item>
      <title>Stop asking IF agents work. Start asking HOW?!</title>
      <link>https://x.com/gabe_onchain/status/2048759729720107027</link>
      <guid isPermaLink="false">https://x.com/gabe_onchain/status/2048759729720107027</guid>
      <pubDate>Wed, 01 Apr 2026 12:00:00 GMT</pubDate>
      <category>AI Engineering</category>
      <category>Opinion</category>
      <description>Reframing the AI-agent debate from feasibility to mechanism. What works, where, and why the right question is HOW agents land in workflows, not whether they exist.</description>
    </item>
    <item>
      <title>Octant Vaults Now Support Yearn Strategies for USDS, USDC, and wETH</title>
      <link>https://octant.build/en/blog/octant-new-yearn-vaults-strategy</link>
      <guid isPermaLink="false">https://octant.build/en/blog/octant-new-yearn-vaults-strategy</guid>
      <pubDate>Thu, 01 Jan 2026 12:00:00 GMT</pubDate>
      <category>Web3</category>
      <category>Marketing</category>
      <description>Vault architecture deep-dive. How Octant's new Yearn integration unlocks stablecoin and wETH strategies, with mechanism + ROI walkthrough for both developers and retail.</description>
    </item>
    <item>
      <title>Chains of Trust Are Attacked at Their Weakest Point</title>
      <link>https://x.com/gabe_onchain/status/2046356642057302352</link>
      <guid isPermaLink="false">https://x.com/gabe_onchain/status/2046356642057302352</guid>
      <pubDate>Thu, 01 Jan 2026 12:00:00 GMT</pubDate>
      <category>Web3</category>
      <description>Security thinking applied to onchain trust models. The weakest link in any chain of custody is rarely the contract; it's the off-chain edges nobody is auditing.</description>
    </item>
    <item>
      <title>Sell the yield, not the building</title>
      <link>https://x.com/gabe_onchain/status/2037983185481437455</link>
      <guid isPermaLink="false">https://x.com/gabe_onchain/status/2037983185481437455</guid>
      <pubDate>Thu, 01 Jan 2026 12:00:00 GMT</pubDate>
      <category>Marketing</category>
      <description>Positioning lesson for crypto marketers. Stop selling the technical architecture; sell the outcome the user actually wants. Yield is the why; the building is the how.</description>
    </item>
    <item>
      <title>Welcome to the new Octant app</title>
      <link>https://x.com/OctantApp/status/2024201516266275007</link>
      <guid isPermaLink="false">https://x.com/OctantApp/status/2024201516266275007</guid>
      <pubDate>Sun, 01 Feb 2026 12:00:00 GMT</pubDate>
      <category>Marketing</category>
      <category>Web3</category>
      <description>Launch article for the new Octant app and the V1 to V2 migration. Mechanism, why-now, and what changes for users. Published on Octant's main account; pairs with the Octant Card campaign on the homepage work table.</description>
    </item>
  </channel>
</rss>
