<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Pelican Site</title><link>https://pelican-5lg.pages.dev/</link><description>a beginner's notes</description><atom:link href="https://pelican-5lg.pages.dev/feeds/all.rss.xml" rel="self"/><lastBuildDate>Fri, 05 Jun 2026 13:00:00 +0200</lastBuildDate><item><title>Sample Photo Album</title><link>https://pelican-5lg.pages.dev/sample-photo-album.html</link><description>&lt;p&gt;A demo of the photos plugin — drop images in &lt;code&gt;content/images/samples/&lt;/code&gt; and list them with &lt;code&gt;{photo}samples/&lt;/code&gt;.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">phurix</dc:creator><pubDate>Fri, 05 Jun 2026 13:00:00 +0200</pubDate><guid>tag:pelican-5lg.pages.dev,2026-06-05:/sample-photo-album.html</guid><category>Photos</category><category>photos</category><category>sample</category></item><item><title>Hello, World!</title><link>https://pelican-5lg.pages.dev/hello-world.html</link><description>&lt;p&gt;First post on the new Pelican site.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">phurix</dc:creator><pubDate>Fri, 05 Jun 2026 12:00:00 +0200</pubDate><guid>tag:pelican-5lg.pages.dev,2026-06-05:/hello-world.html</guid><category>General</category><category>pelican</category><category>intro</category></item><item><title>Welcome to the new site</title><link>https://pelican-5lg.pages.dev/welcome-to-the-new-site.html</link><description>&lt;p&gt;Kicking off the blog with a quick tour of the new theme.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">phurix</dc:creator><pubDate>Thu, 04 Jun 2026 09:00:00 +0200</pubDate><guid>tag:pelican-5lg.pages.dev,2026-06-04:/welcome-to-the-new-site.html</guid><category>Meta</category><category>meta</category><category>welcome</category></item><item><title>Daily Journal — 2026-06-04</title><link>https://pelican-5lg.pages.dev/daily-journal-2026-06-04.html</link><description>&lt;h2 id="freewrite"&gt;Freewrite&lt;a class="headerlink" href="#freewrite" title="Permanent link"&gt;&amp;para;&lt;/a&gt;&lt;/h2&gt;
&lt;p&gt;Two threads today: polishing BOL AI adoption content for a townhall or internal campaign, and a deeper dive into developer automation — GitHub Actions with Claude Code, parallel worktree workflows, and Quartz component patterns. The AI content work is converging on a tagline and a before/after table format. The …&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">phurix</dc:creator><pubDate>Thu, 04 Jun 2026 00:00:00 +0200</pubDate><guid>tag:pelican-5lg.pages.dev,2026-06-04:/daily-journal-2026-06-04.html</guid><category>notes</category><category>[daily]</category></item><item><title>Daily Journal — 2026-06-03</title><link>https://pelican-5lg.pages.dev/daily-journal-2026-06-03.html</link><description>&lt;h2 id="freewrite"&gt;Freewrite&lt;a class="headerlink" href="#freewrite" title="Permanent link"&gt;&amp;para;&lt;/a&gt;&lt;/h2&gt;
&lt;p&gt;A day of converging threads: the personal site project came into focus with a clear aesthetic direction (Studio Ghibli / watercolor / anime), and the tooling stack is now confirmed — Quartz + GitHub + Cloudflare Pages. Also continued pushing on OpenACP's cloudflared tunnel, getting it running but the Discord interface still needs attention …&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">phurix</dc:creator><pubDate>Wed, 03 Jun 2026 00:00:00 +0200</pubDate><guid>tag:pelican-5lg.pages.dev,2026-06-03:/daily-journal-2026-06-03.html</guid><category>notes</category><category>[daily]</category></item><item><title>Daily Journal — 2026-06-02</title><link>https://pelican-5lg.pages.dev/daily-journal-2026-06-02.html</link><description>&lt;h2 id="freewrite"&gt;Freewrite&lt;a class="headerlink" href="#freewrite" title="Permanent link"&gt;&amp;para;&lt;/a&gt;&lt;/h2&gt;
&lt;p&gt;Tuesday morning spent in exploration mode — part infrastructure research (Cloudflare ecosystem, local LLMs), part creative wandering (Thai digital gardens, domain name brainstorming). The CC-OpenACP project continues with small friction around the Discord interface. No big decisions today, but a lot of useful reference material gathered.&lt;/p&gt;
&lt;h2 id="big-things-today"&gt;Big Things Today&lt;a class="headerlink" href="#big-things-today" title="Permanent link"&gt;&amp;para;&lt;/a&gt;&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;[ ] Get …&lt;/li&gt;&lt;/ul&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">phurix</dc:creator><pubDate>Tue, 02 Jun 2026 00:00:00 +0200</pubDate><guid>tag:pelican-5lg.pages.dev,2026-06-02:/daily-journal-2026-06-02.html</guid><category>notes</category><category>[daily]</category></item><item><title>Prabda Yoon</title><link>https://pelican-5lg.pages.dev/prabda-yoon.html</link><description>&lt;h1 id="prabda-yoon"&gt;Prabda Yoon&lt;a class="headerlink" href="#prabda-yoon" title="Permanent link"&gt;&amp;para;&lt;/a&gt;&lt;/h1&gt;
&lt;p&gt;Thai writer, graphic designer, filmmaker, and translator. Maintains a genuine personal website with essays — rare among Thai public figures.&lt;/p&gt;
&lt;p&gt;One-line: The only prominent Thai public figure with a Maggie Appleton–style digital garden / personal site.&lt;/p&gt;
&lt;h2 id="what-i-know"&gt;What I Know&lt;a class="headerlink" href="#what-i-know" title="Permanent link"&gt;&amp;para;&lt;/a&gt;&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;Website: prabdayoon.net — personal essays and creative writing&lt;/li&gt;
&lt;li&gt;Created and …&lt;/li&gt;&lt;/ul&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">phurix</dc:creator><pubDate>Tue, 02 Jun 2026 00:00:00 +0200</pubDate><guid>tag:pelican-5lg.pages.dev,2026-06-02:/prabda-yoon.html</guid><category>people</category><category>[person]</category></item><item><title>Daily Journal — 2026-06-01</title><link>https://pelican-5lg.pages.dev/daily-journal-2026-06-01.html</link><description>&lt;h2 id="freewrite"&gt;Freewrite&lt;a class="headerlink" href="#freewrite" title="Permanent link"&gt;&amp;para;&lt;/a&gt;&lt;/h2&gt;
&lt;p&gt;Heavy dev day — most energy went into the Mantine Web App project: received the full mock data layer (Todo + Calendar TypeScript types), diagnosed a persistent AppShell layout bug, and set up Playwright testing with a Definition of Done baked into CLAUDE.md. Also did research on Claude Code remote-control …&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">phurix</dc:creator><pubDate>Mon, 01 Jun 2026 00:00:00 +0200</pubDate><guid>tag:pelican-5lg.pages.dev,2026-06-01:/daily-journal-2026-06-01.html</guid><category>notes</category><category>[daily]</category></item><item><title>Daily Journal — 2026-05-31</title><link>https://pelican-5lg.pages.dev/daily-journal-2026-05-31.html</link><description>&lt;h2 id="freewrite"&gt;Freewrite&lt;a class="headerlink" href="#freewrite" title="Permanent link"&gt;&amp;para;&lt;/a&gt;&lt;/h2&gt;
&lt;p&gt;A focused Sunday on frontend development. The day was primarily spent on the Mantine web app — generating mock data structures for the Todo and Calendar modules, and debugging an AppShell layout issue that was causing a blank white column on every page. Also did a landscape survey on tools …&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">phurix</dc:creator><pubDate>Sun, 31 May 2026 00:00:00 +0200</pubDate><guid>tag:pelican-5lg.pages.dev,2026-05-31:/daily-journal-2026-05-31.html</guid><category>notes</category><category>[daily]</category></item><item><title>Daily Journal — 2026-05-30</title><link>https://pelican-5lg.pages.dev/daily-journal-2026-05-30.html</link><description>&lt;h2 id="freewrite"&gt;Freewrite&lt;a class="headerlink" href="#freewrite" title="Permanent link"&gt;&amp;para;&lt;/a&gt;&lt;/h2&gt;
&lt;p&gt;A focused Saturday of AI tooling and stack research. The main thread was evaluating MiniMax M2.7 as the LLM backend for a new admin portal — stack decided as Mantine v9 + Next.js + M2.7 via OpenAI-compatible SDK. Also explored y-router as a cleaner alternative to the LiteLLM proxy …&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">phurix</dc:creator><pubDate>Sat, 30 May 2026 00:00:00 +0200</pubDate><guid>tag:pelican-5lg.pages.dev,2026-05-30:/daily-journal-2026-05-30.html</guid><category>notes</category><category>[daily]</category></item><item><title>Daily Journal — 2026-05-29</title><link>https://pelican-5lg.pages.dev/daily-journal-2026-05-29.html</link><description>&lt;h2 id="freewrite"&gt;Freewrite&lt;a class="headerlink" href="#freewrite" title="Permanent link"&gt;&amp;para;&lt;/a&gt;&lt;/h2&gt;
&lt;p&gt;A mixed day of tooling and health research. Most of the technical work continued the LiteLLM/local-LLM thread — this time expanding to include MiniMax as a cloud model alongside Ollama. The CC-Remote Control effort moved forward with a full Discord bot implementation using &lt;code&gt;--resume&lt;/code&gt; for persistent Claude Code sessions …&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">phurix</dc:creator><pubDate>Fri, 29 May 2026 00:00:00 +0200</pubDate><guid>tag:pelican-5lg.pages.dev,2026-05-29:/daily-journal-2026-05-29.html</guid><category>notes</category><category>[daily]</category></item><item><title>Weekly Review — 2026-W22</title><link>https://pelican-5lg.pages.dev/weekly-review-2026-w22.html</link><description>&lt;h2 id="week-of-mon-25-sun-31-may-2026"&gt;Week of Mon 25 – Sun 31 May 2026&lt;a class="headerlink" href="#week-of-mon-25-sun-31-may-2026" title="Permanent link"&gt;&amp;para;&lt;/a&gt;&lt;/h2&gt;
&lt;h3 id="summary"&gt;Summary&lt;a class="headerlink" href="#summary" title="Permanent link"&gt;&amp;para;&lt;/a&gt;&lt;/h3&gt;
&lt;p&gt;A three-day active week (Tue 26 – Thu 28 May). The main themes were automation, architecture clarity, and Hermes infrastructure. The GitHub issue-to-PR autocode pipeline was wired up end-to-end using Claude Code Action and Z.ai. Two long-running ambiguities were resolved: why …&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">phurix</dc:creator><pubDate>Fri, 29 May 2026 00:00:00 +0200</pubDate><guid>tag:pelican-5lg.pages.dev,2026-05-29:/weekly-review-2026-w22.html</guid><category>weekly</category><category>[weekly]</category></item><item><title>Daily Journal — 2026-05-28</title><link>https://pelican-5lg.pages.dev/daily-journal-2026-05-28.html</link><description>&lt;h2 id="freewrite"&gt;Freewrite&lt;a class="headerlink" href="#freewrite" title="Permanent link"&gt;&amp;para;&lt;/a&gt;&lt;/h2&gt;
&lt;p&gt;A focused Thursday working through Hermes infrastructure — specifically how profiles are stored and moved between Docker instances. Also started exploring GitHub Actions automation, though that thread is just getting off the ground. The Hermes Docker work is building towards a more robust multi-instance setup.&lt;/p&gt;
&lt;h2 id="big-things-today"&gt;Big Things Today&lt;a class="headerlink" href="#big-things-today" title="Permanent link"&gt;&amp;para;&lt;/a&gt;&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;[ ] Clarify Hermes …&lt;/li&gt;&lt;/ul&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">phurix</dc:creator><pubDate>Thu, 28 May 2026 00:00:00 +0200</pubDate><guid>tag:pelican-5lg.pages.dev,2026-05-28:/daily-journal-2026-05-28.html</guid><category>notes</category><category>[daily]</category></item><item><title>Daily Journal — 2026-05-27</title><link>https://pelican-5lg.pages.dev/daily-journal-2026-05-27.html</link><description>&lt;h2 id="freewrite"&gt;Freewrite&lt;a class="headerlink" href="#freewrite" title="Permanent link"&gt;&amp;para;&lt;/a&gt;&lt;/h2&gt;
&lt;p&gt;A quieter Wednesday with no meetings — good conditions for heads-down work. The automated pipelines ran cleanly in the morning and the day's only manual conversation deepened understanding of GitHub Actions mechanics: data flow between steps, Python-powered webhooks, and the built-in Projects kanban. The weekly PKM consolidator also ran today …&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">phurix</dc:creator><pubDate>Wed, 27 May 2026 00:00:00 +0200</pubDate><guid>tag:pelican-5lg.pages.dev,2026-05-27:/daily-journal-2026-05-27.html</guid><category>notes</category><category>[daily]</category></item><item><title>API Keys vs OAuth — Inference-Only vs Identity+Session Layer</title><link>https://pelican-5lg.pages.dev/api-keys-vs-oauth-inference-only-vs-identitysession-layer.html</link><description>&lt;h1 id="api-keys-vs-oauth-inference-only-vs-identitysession-layer"&gt;API Keys vs OAuth — Inference-Only vs Identity+Session Layer&lt;a class="headerlink" href="#api-keys-vs-oauth-inference-only-vs-identitysession-layer" title="Permanent link"&gt;&amp;para;&lt;/a&gt;&lt;/h1&gt;
&lt;p&gt;An API key and an OAuth token are not interchangeable credentials. They operate at different layers of a system: one authorises a request, the other establishes an identity.&lt;/p&gt;
&lt;h2 id="core-idea"&gt;Core Idea&lt;a class="headerlink" href="#core-idea" title="Permanent link"&gt;&amp;para;&lt;/a&gt;&lt;/h2&gt;
&lt;p&gt;An API key is &lt;strong&gt;inference-only&lt;/strong&gt;: it proves that a request is …&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">phurix</dc:creator><pubDate>Tue, 26 May 2026 00:00:00 +0200</pubDate><guid>tag:pelican-5lg.pages.dev,2026-05-26:/api-keys-vs-oauth-inference-only-vs-identitysession-layer.html</guid><category>evergreen</category><category>[api-keys</category><category>oauth</category><category>authentication</category><category>claude-code</category><category>remote-control</category><category>identity]</category></item><item><title>Daily Journal — 2026-05-26</title><link>https://pelican-5lg.pages.dev/daily-journal-2026-05-26.html</link><description>&lt;h2 id="freewrite"&gt;Freewrite&lt;a class="headerlink" href="#freewrite" title="Permanent link"&gt;&amp;para;&lt;/a&gt;&lt;/h2&gt;
&lt;p&gt;A focused day on AI tooling and project architecture. Wired up GitHub Actions to auto-implement issues via Claude Code using the Z.ai proxy, which makes the "write issue → get PR" loop fully automated with no manual coding step. Also clarified a persistent confusion around why Claude Code Remote …&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">phurix</dc:creator><pubDate>Tue, 26 May 2026 00:00:00 +0200</pubDate><guid>tag:pelican-5lg.pages.dev,2026-05-26:/daily-journal-2026-05-26.html</guid><category>notes</category><category>[daily]</category></item><item><title>Addy Osmani</title><link>https://pelican-5lg.pages.dev/addy-osmani.html</link><description>&lt;h1 id="addy-osmani"&gt;Addy Osmani&lt;a class="headerlink" href="#addy-osmani" title="Permanent link"&gt;&amp;para;&lt;/a&gt;&lt;/h1&gt;
&lt;p&gt;Engineering Lead for Chrome at Google. Creator of &lt;code&gt;agent-skills&lt;/code&gt; (43K GitHub stars).
Known for translating Google-scale engineering culture into open-source tooling for AI coding agents.&lt;/p&gt;
&lt;h2 id="what-i-know"&gt;What I Know&lt;a class="headerlink" href="#what-i-know" title="Permanent link"&gt;&amp;para;&lt;/a&gt;&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;Leads the Chrome browser engineering team at Google&lt;/li&gt;
&lt;li&gt;Created &lt;code&gt;addyosmani/agent-skills&lt;/code&gt; — 23 production-grade skills for AI coding agents covering the …&lt;/li&gt;&lt;/ul&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">phurix</dc:creator><pubDate>Sun, 24 May 2026 00:00:00 +0200</pubDate><guid>tag:pelican-5lg.pages.dev,2026-05-24:/addy-osmani.html</guid><category>people</category><category>[person]</category></item><item><title>Daily Journal — 2026-05-24</title><link>https://pelican-5lg.pages.dev/daily-journal-2026-05-24.html</link><description>&lt;h2 id="freewrite"&gt;Freewrite&lt;a class="headerlink" href="#freewrite" title="Permanent link"&gt;&amp;para;&lt;/a&gt;&lt;/h2&gt;
&lt;p&gt;A Sunday focused on tooling and developer environment work. The day centred on evaluating new Claude Code ecosystem tools — specifically the agent-skills repo — and tying up loose ends around terminal session management and Rust/Cargo tooling. Feels like a maintenance and stack-refinement day rather than a building day, which …&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">phurix</dc:creator><pubDate>Sun, 24 May 2026 00:00:00 +0200</pubDate><guid>tag:pelican-5lg.pages.dev,2026-05-24:/daily-journal-2026-05-24.html</guid><category>notes</category><category>[daily]</category></item><item><title>Agentic Cost Control</title><link>https://pelican-5lg.pages.dev/agentic-cost-control.html</link><description>&lt;h1 id="agentic-cost-control"&gt;Agentic Cost Control&lt;a class="headerlink" href="#agentic-cost-control" title="Permanent link"&gt;&amp;para;&lt;/a&gt;&lt;/h1&gt;
&lt;h2 id="core-idea"&gt;Core Idea&lt;a class="headerlink" href="#core-idea" title="Permanent link"&gt;&amp;para;&lt;/a&gt;&lt;/h2&gt;
&lt;p&gt;Token tracking alone is insufficient for cost control in agentic AI systems. Production agent pipelines need per-task spend caps, trajectory scoring, and webhook stop signals built into the AI gateway — not bolted on after the fact.&lt;/p&gt;
&lt;h2 id="why-this-matters"&gt;Why This Matters&lt;a class="headerlink" href="#why-this-matters" title="Permanent link"&gt;&amp;para;&lt;/a&gt;&lt;/h2&gt;
&lt;p&gt;A single poorly-scoped agentic task can …&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">phurix</dc:creator><pubDate>Sat, 23 May 2026 00:00:00 +0200</pubDate><guid>tag:pelican-5lg.pages.dev,2026-05-23:/agentic-cost-control.html</guid><category>evergreen</category><category>[ai-agents</category><category>cost</category><category>infrastructure</category><category>llm</category><category>production]</category></item><item><title>AI Coding Stack 2026</title><link>https://pelican-5lg.pages.dev/ai-coding-stack-2026.html</link><description>&lt;h1 id="ai-coding-stack-2026"&gt;AI Coding Stack 2026&lt;a class="headerlink" href="#ai-coding-stack-2026" title="Permanent link"&gt;&amp;para;&lt;/a&gt;&lt;/h1&gt;
&lt;h2 id="core-idea"&gt;Core Idea&lt;a class="headerlink" href="#core-idea" title="Permanent link"&gt;&amp;para;&lt;/a&gt;&lt;/h2&gt;
&lt;p&gt;Different AI coding tools have distinct sweet spots in 2026. Using the wrong tool for the task wastes money and produces worse results than the right tool used deliberately.&lt;/p&gt;
&lt;h2 id="why-this-matters"&gt;Why This Matters&lt;a class="headerlink" href="#why-this-matters" title="Permanent link"&gt;&amp;para;&lt;/a&gt;&lt;/h2&gt;
&lt;p&gt;The AI coding tool landscape fragmented fast. Defaulting to one tool for …&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">phurix</dc:creator><pubDate>Sat, 23 May 2026 00:00:00 +0200</pubDate><guid>tag:pelican-5lg.pages.dev,2026-05-23:/ai-coding-stack-2026.html</guid><category>evergreen</category><category>[ai-agents</category><category>claude-code</category><category>developer-tools</category><category>coding</category><category>llm]</category></item><item><title>BOL 2026 Data Strategy</title><link>https://pelican-5lg.pages.dev/bol-2026-data-strategy.html</link><description>&lt;h1 id="bol-2026-data-strategy"&gt;BOL 2026 Data Strategy&lt;a class="headerlink" href="#bol-2026-data-strategy" title="Permanent link"&gt;&amp;para;&lt;/a&gt;&lt;/h1&gt;
&lt;p&gt;BOL (Business Online PCL) 9-month platform modernisation roadmap to transform from a legacy data provider into a deployable Intelligent Data Platform targeting Thai banks and government agencies.&lt;/p&gt;
&lt;h2 id="core-idea"&gt;Core Idea&lt;a class="headerlink" href="#core-idea" title="Permanent link"&gt;&amp;para;&lt;/a&gt;&lt;/h2&gt;
&lt;p&gt;The strategy leverages a 2026 convergence window — FATF mutual evaluation pressure, PDPA enforcement, and reduced AI build …&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">phurix</dc:creator><pubDate>Sat, 23 May 2026 00:00:00 +0200</pubDate><guid>tag:pelican-5lg.pages.dev,2026-05-23:/bol-2026-data-strategy.html</guid><category>evergreen</category><category>[strategy</category><category>bol</category><category>platform</category><category>data</category><category>ai</category><category>fatf</category><category>pdpa]</category></item><item><title>Claude Code Analytics Automation</title><link>https://pelican-5lg.pages.dev/claude-code-analytics-automation.html</link><description>&lt;h1 id="claude-code-analytics-automation"&gt;Claude Code Analytics Automation&lt;a class="headerlink" href="#claude-code-analytics-automation" title="Permanent link"&gt;&amp;para;&lt;/a&gt;&lt;/h1&gt;
&lt;p&gt;Daily automated extraction of Claude Code "Lines this month" per team member from &lt;code&gt;claude.ai/analytics/claude-code&lt;/code&gt;, saved as a dated CSV and delivered as a Gmail draft summary.&lt;/p&gt;
&lt;h2 id="core-idea"&gt;Core Idea&lt;a class="headerlink" href="#core-idea" title="Permanent link"&gt;&amp;para;&lt;/a&gt;&lt;/h2&gt;
&lt;p&gt;The Claude admin console tracks lines of code generated per team member (MTD reset). A …&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">phurix</dc:creator><pubDate>Sat, 23 May 2026 00:00:00 +0200</pubDate><guid>tag:pelican-5lg.pages.dev,2026-05-23:/claude-code-analytics-automation.html</guid><category>evergreen</category><category>[automation</category><category>analytics</category><category>claude-code</category><category>bol</category><category>scheduled-task</category><category>reporting]</category></item><item><title>Context Engineering vs Prompt Engineering</title><link>https://pelican-5lg.pages.dev/context-engineering-vs-prompt-engineering.html</link><description>&lt;h1 id="context-engineering-vs-prompt-engineering"&gt;Context Engineering vs Prompt Engineering&lt;a class="headerlink" href="#context-engineering-vs-prompt-engineering" title="Permanent link"&gt;&amp;para;&lt;/a&gt;&lt;/h1&gt;
&lt;h2 id="core-idea"&gt;Core Idea&lt;a class="headerlink" href="#core-idea" title="Permanent link"&gt;&amp;para;&lt;/a&gt;&lt;/h2&gt;
&lt;p&gt;The dominant failure mode in production AI systems is not a bad prompt — it is bad context assembly. "Context engineering" is the discipline of managing what information enters the model's context window, and it matters more than prompt wording in agentic workflows.&lt;/p&gt;
&lt;h2 id="why-this-matters"&gt;Why …&lt;/h2&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">phurix</dc:creator><pubDate>Sat, 23 May 2026 00:00:00 +0200</pubDate><guid>tag:pelican-5lg.pages.dev,2026-05-23:/context-engineering-vs-prompt-engineering.html</guid><category>evergreen</category><category>[ai-agents</category><category>llm</category><category>production</category><category>context</category><category>prompt-engineering]</category></item><item><title>Daily Journal — 2026-05-23</title><link>https://pelican-5lg.pages.dev/daily-journal-2026-05-23.html</link><description>&lt;h2 id="freewrite"&gt;Freewrite&lt;a class="headerlink" href="#freewrite" title="Permanent link"&gt;&amp;para;&lt;/a&gt;&lt;/h2&gt;
&lt;p&gt;A productive Saturday working across AI tooling, design review, and personal knowledge systems. The day started with CTO brief pipeline work and Hermes configuration, then closed with a thorough Figma review of the M-Flow app — analyzing the member user journey, generating a Speckit epic spec, and surfacing design improvement …&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">phurix</dc:creator><pubDate>Sat, 23 May 2026 00:00:00 +0200</pubDate><guid>tag:pelican-5lg.pages.dev,2026-05-23:/daily-journal-2026-05-23.html</guid><category>notes</category><category>[daily]</category></item><item><title>Weekly Review — 2026-W21</title><link>https://pelican-5lg.pages.dev/weekly-review-2026-w21.html</link><description>&lt;h2 id="week-of-mon-18-sun-24-may-2026"&gt;Week of Mon 18 – Sun 24 May, 2026&lt;a class="headerlink" href="#week-of-mon-18-sun-24-may-2026" title="Permanent link"&gt;&amp;para;&lt;/a&gt;&lt;/h2&gt;
&lt;h3 id="summary"&gt;Summary&lt;a class="headerlink" href="#summary" title="Permanent link"&gt;&amp;para;&lt;/a&gt;&lt;/h3&gt;
&lt;p&gt;A highly productive week focused on three converging themes: building out automated personal tooling (PKM system reaching full maturity, analytics pipeline automated), strategic planning (BOL 2026 platform strategy review, Sprint 24 kick-off), and systematising team intelligence capture (Claude Code analytics daily …&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">phurix</dc:creator><pubDate>Sat, 23 May 2026 00:00:00 +0200</pubDate><guid>tag:pelican-5lg.pages.dev,2026-05-23:/weekly-review-2026-w21.html</guid><category>weekly</category><category>[weekly]</category></item><item><title>Cloud VM vs Local Machine for Always-On AI Agents</title><link>https://pelican-5lg.pages.dev/cloud-vm-vs-local-machine-for-always-on-ai-agents.html</link><description>&lt;h1 id="cloud-vm-vs-local-machine-for-always-on-ai-agents"&gt;Cloud VM vs Local Machine for Always-On AI Agents&lt;a class="headerlink" href="#cloud-vm-vs-local-machine-for-always-on-ai-agents" title="Permanent link"&gt;&amp;para;&lt;/a&gt;&lt;/h1&gt;
&lt;h2 id="core-idea"&gt;Core Idea&lt;a class="headerlink" href="#core-idea" title="Permanent link"&gt;&amp;para;&lt;/a&gt;&lt;/h2&gt;
&lt;p&gt;Running AI agent scheduled tasks on a local machine is convenient but unreliable — sleep, reboots, and closed apps silently miss runs. A cloud VM at $5–10/month solves this with near-zero maintenance and is the right long-term infrastructure …&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">phurix</dc:creator><pubDate>Fri, 22 May 2026 00:00:00 +0200</pubDate><guid>tag:pelican-5lg.pages.dev,2026-05-22:/cloud-vm-vs-local-machine-for-always-on-ai-agents.html</guid><category>evergreen</category><category>[infrastructure</category><category>ai-agents</category><category>cowork</category><category>automation</category><category>scheduling]</category></item><item><title>Daily Journal — 2026-05-22</title><link>https://pelican-5lg.pages.dev/daily-journal-2026-05-22.html</link><description>&lt;h2 id="freewrite"&gt;Freewrite&lt;a class="headerlink" href="#freewrite" title="Permanent link"&gt;&amp;para;&lt;/a&gt;&lt;/h2&gt;
&lt;p&gt;A planning and tooling day. Most energy went into comparing AI tool costs and thinking about the Hermes agent fleet — two topics that keep coming back. Also resolved a loose end on the daily news brief email by adding source links, and got more clarity on the Composio Microsoft …&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">phurix</dc:creator><pubDate>Fri, 22 May 2026 00:00:00 +0200</pubDate><guid>tag:pelican-5lg.pages.dev,2026-05-22:/daily-journal-2026-05-22.html</guid><category>notes</category><category>[daily]</category></item><item><title>Hermes Fleet as Life OS — Specialized Agents Per Domain Rather Than One Generalist</title><link>https://pelican-5lg.pages.dev/hermes-fleet-as-life-os-specialized-agents-per-domain-rather-than-one-generalist.html</link><description>&lt;h1 id="hermes-fleet-as-life-os-specialized-agents-per-domain-rather-than-one-generalist"&gt;Hermes Fleet as Life OS — Specialized Agents Per Domain Rather Than One Generalist&lt;a class="headerlink" href="#hermes-fleet-as-life-os-specialized-agents-per-domain-rather-than-one-generalist" title="Permanent link"&gt;&amp;para;&lt;/a&gt;&lt;/h1&gt;
&lt;h2 id="core-idea"&gt;Core Idea&lt;a class="headerlink" href="#core-idea" title="Permanent link"&gt;&amp;para;&lt;/a&gt;&lt;/h2&gt;
&lt;p&gt;A fleet of specialized Hermes agents — one per life domain — outperforms a single generalist Hermes over time. Each specialist accumulates domain-specific MEMORY.md context without contaminating the others. The fleet is coordinated by a Commander …&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">phurix</dc:creator><pubDate>Fri, 22 May 2026 00:00:00 +0200</pubDate><guid>tag:pelican-5lg.pages.dev,2026-05-22:/hermes-fleet-as-life-os-specialized-agents-per-domain-rather-than-one-generalist.html</guid><category>evergreen</category><category>[hermes</category><category>ai-agents</category><category>pkm</category><category>life-os</category><category>architecture]</category></item><item><title>MiniMax Is Cost-Optimal for Solo AI Workflow Testing — Claude Code Team Only Makes Sense at 5+ Seats</title><link>https://pelican-5lg.pages.dev/minimax-is-cost-optimal-for-solo-ai-workflow-testing-claude-code-team-only-makes-sense-at-5-seats.html</link><description>&lt;h1 id="minimax-is-cost-optimal-for-solo-ai-workflow-testing-claude-code-team-only-makes-sense-at-5-seats"&gt;MiniMax Is Cost-Optimal for Solo AI Workflow Testing — Claude Code Team Only Makes Sense at 5+ Seats&lt;a class="headerlink" href="#minimax-is-cost-optimal-for-solo-ai-workflow-testing-claude-code-team-only-makes-sense-at-5-seats" title="Permanent link"&gt;&amp;para;&lt;/a&gt;&lt;/h1&gt;
&lt;h2 id="core-idea"&gt;Core Idea&lt;a class="headerlink" href="#core-idea" title="Permanent link"&gt;&amp;para;&lt;/a&gt;&lt;/h2&gt;
&lt;p&gt;For solo developers or small teams (1–4 people) testing and building AI workflows, MiniMax Ultra-Highspeed is significantly cheaper and more flexible than Claude Code Team Premium. Claude Code Team only …&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">phurix</dc:creator><pubDate>Fri, 22 May 2026 00:00:00 +0200</pubDate><guid>tag:pelican-5lg.pages.dev,2026-05-22:/minimax-is-cost-optimal-for-solo-ai-workflow-testing-claude-code-team-only-makes-sense-at-5-seats.html</guid><category>evergreen</category><category>[minimax</category><category>claude-code</category><category>procurement</category><category>ai-tools</category><category>cost]</category></item><item><title>Daily Journal — 2026-05-21</title><link>https://pelican-5lg.pages.dev/daily-journal-2026-05-21.html</link><description>&lt;h2 id="freewrite"&gt;Freewrite&lt;a class="headerlink" href="#freewrite" title="Permanent link"&gt;&amp;para;&lt;/a&gt;&lt;/h2&gt;
&lt;p&gt;A technical-leaning day split between infrastructure decisions, product thinking, and integration tooling. Explored the rapidly evolving Claude Code autonomous dev landscape — the stack has moved on significantly from GSD + autonomous-dev toward newer options like Superpowers and oh-my-claudecode. Also revisited the CreditX concept, picked up a quick reference on Keycloak …&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">phurix</dc:creator><pubDate>Thu, 21 May 2026 00:00:00 +0200</pubDate><guid>tag:pelican-5lg.pages.dev,2026-05-21:/daily-journal-2026-05-21.html</guid><category>notes</category><category>[daily]</category></item><item><title>Daily Journal — 2026-05-20</title><link>https://pelican-5lg.pages.dev/daily-journal-2026-05-20.html</link><description>&lt;h2 id="freewrite"&gt;Freewrite&lt;a class="headerlink" href="#freewrite" title="Permanent link"&gt;&amp;para;&lt;/a&gt;&lt;/h2&gt;
&lt;p&gt;A day of dense AI tooling and integration work. The morning was spent connecting the pieces of the stack — Jira via Composio, Gmail connectors, email automation to Teams — while the afternoon circled back to bigger architectural questions: how to run Claude Code fully autonomously overnight, and whether MiniMax is …&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">phurix</dc:creator><pubDate>Wed, 20 May 2026 00:00:00 +0200</pubDate><guid>tag:pelican-5lg.pages.dev,2026-05-20:/daily-journal-2026-05-20.html</guid><category>notes</category><category>[daily]</category></item><item><title>Daily Journal — 2026-05-19</title><link>https://pelican-5lg.pages.dev/daily-journal-2026-05-19.html</link><description>&lt;h2 id="freewrite"&gt;Freewrite&lt;a class="headerlink" href="#freewrite" title="Permanent link"&gt;&amp;para;&lt;/a&gt;&lt;/h2&gt;
&lt;p&gt;A focused AI-infrastructure day — validating Z.ai's privacy posture for enterprise use, preparing the MiniMax procurement memo for formal submission, and building out reference knowledge in GitHub Actions and Apprise notifications. The day also surfaced several active BOL incidents and pending approvals that carried over from yesterday.&lt;/p&gt;
&lt;h2 id="big-things-today"&gt;Big Things …&lt;/h2&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">phurix</dc:creator><pubDate>Tue, 19 May 2026 00:00:00 +0200</pubDate><guid>tag:pelican-5lg.pages.dev,2026-05-19:/daily-journal-2026-05-19.html</guid><category>notes</category><category>[daily]</category></item><item><title>Daily Journal — 2026-05-18</title><link>https://pelican-5lg.pages.dev/daily-journal-2026-05-18.html</link><description>&lt;h2 id="freewrite"&gt;Freewrite&lt;a class="headerlink" href="#freewrite" title="Permanent link"&gt;&amp;para;&lt;/a&gt;&lt;/h2&gt;
&lt;p&gt;A focused Monday split across three themes: deepening developer tooling knowledge (Claude Code hooks, GitHub access control, codebase analysis tools), advancing the Django/Next.js web project (notifications with Apprise, git workflow), and creative work preparing an AI presentation for a Thai audience. The day shows a healthy mix …&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">phurix</dc:creator><pubDate>Mon, 18 May 2026 00:00:00 +0200</pubDate><guid>tag:pelican-5lg.pages.dev,2026-05-18:/daily-journal-2026-05-18.html</guid><category>notes</category><category>[daily]</category></item><item><title>Daily Journal — 2026-05-17</title><link>https://pelican-5lg.pages.dev/daily-journal-2026-05-17.html</link><description>&lt;h2 id="freewrite"&gt;Freewrite&lt;a class="headerlink" href="#freewrite" title="Permanent link"&gt;&amp;para;&lt;/a&gt;&lt;/h2&gt;
&lt;p&gt;A heavy Sunday of Claude Code ecosystem deep-dives — autonomous execution patterns, token optimization, session management, and Discord formatting. The BOL work side was quieter but present: a calendar check revealed Monday May 18 will be the week's busiest day, and email triage produced six actionable todos. The PKM noon …&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">phurix</dc:creator><pubDate>Sun, 17 May 2026 00:00:00 +0200</pubDate><guid>tag:pelican-5lg.pages.dev,2026-05-17:/daily-journal-2026-05-17.html</guid><category>notes</category><category>[daily]</category></item><item><title>Weekly Review — 2026-W20</title><link>https://pelican-5lg.pages.dev/weekly-review-2026-w20.html</link><description>&lt;h2 id="week-of-mon-12-sun-17-may-2026"&gt;Week of Mon 12 – Sun 17 May, 2026&lt;a class="headerlink" href="#week-of-mon-12-sun-17-may-2026" title="Permanent link"&gt;&amp;para;&lt;/a&gt;&lt;/h2&gt;
&lt;h3 id="summary"&gt;Summary&lt;a class="headerlink" href="#summary" title="Permanent link"&gt;&amp;para;&lt;/a&gt;&lt;/h3&gt;
&lt;p&gt;A foundational week — the PKM system came online on May 12 and captured every working session from day one. Three major efforts advanced in parallel: the Vuexy SaaS frontend reached a fully architected state (monorepo, agent team prompts, CLAUDE.md), Hermes …&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">phurix</dc:creator><pubDate>Sun, 17 May 2026 00:00:00 +0200</pubDate><guid>tag:pelican-5lg.pages.dev,2026-05-17:/weekly-review-2026-w20.html</guid><category>weekly</category><category>[weekly]</category></item><item><title>Daily Journal — 2026-05-16</title><link>https://pelican-5lg.pages.dev/daily-journal-2026-05-16.html</link><description>&lt;h2 id="freewrite"&gt;Freewrite&lt;a class="headerlink" href="#freewrite" title="Permanent link"&gt;&amp;para;&lt;/a&gt;&lt;/h2&gt;
&lt;p&gt;A technically dense Saturday — heavy on Claude Code tooling, Hermes agent setup, and BOL IT housekeeping. The morning was spent tuning the Claude Code environment (autoCompact, session files, Remote Control) while the afternoon circled back to Hermes and Discord integration options. The Office plugin saw serious use for the …&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">phurix</dc:creator><pubDate>Sat, 16 May 2026 00:00:00 +0200</pubDate><guid>tag:pelican-5lg.pages.dev,2026-05-16:/daily-journal-2026-05-16.html</guid><category>notes</category><category>[daily]</category></item><item><title>Daily Journal — 2026-05-15</title><link>https://pelican-5lg.pages.dev/daily-journal-2026-05-15.html</link><description>&lt;h2 id="freewrite"&gt;Freewrite&lt;a class="headerlink" href="#freewrite" title="Permanent link"&gt;&amp;para;&lt;/a&gt;&lt;/h2&gt;
&lt;p&gt;A technically dense day focused on two threads: the Django/NextJS project moving into multi-agent execution, and a parallel learning arc on Git workflows and DevOps tooling. The zai-quota-monitor script also surfaced a couple of environment issues that got cleanly resolved. A lot of foundational work clicking into place …&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">phurix</dc:creator><pubDate>Fri, 15 May 2026 00:00:00 +0200</pubDate><guid>tag:pelican-5lg.pages.dev,2026-05-15:/daily-journal-2026-05-15.html</guid><category>notes</category><category>[daily]</category></item><item><title>Daily Journal — 2026-05-14</title><link>https://pelican-5lg.pages.dev/daily-journal-2026-05-14.html</link><description>&lt;h2 id="freewrite"&gt;Freewrite&lt;a class="headerlink" href="#freewrite" title="Permanent link"&gt;&amp;para;&lt;/a&gt;&lt;/h2&gt;
&lt;p&gt;Heavy AI infrastructure day — three parallel tracks running at once: designing the CorpusX agent team architecture, deepening the PKM system with SDLC traceability, and refining the Claude Code automation pipeline with GitLab cloud. The work is converging: spec-kit methodology, agent orchestration, and PKM are all part of the same …&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">phurix</dc:creator><pubDate>Thu, 14 May 2026 00:00:00 +0200</pubDate><guid>tag:pelican-5lg.pages.dev,2026-05-14:/daily-journal-2026-05-14.html</guid><category>notes</category><category>[daily]</category></item><item><title>Daily Journal — 2026-05-13</title><link>https://pelican-5lg.pages.dev/daily-journal-2026-05-13.html</link><description>&lt;h2 id="freewrite"&gt;Freewrite&lt;a class="headerlink" href="#freewrite" title="Permanent link"&gt;&amp;para;&lt;/a&gt;&lt;/h2&gt;
&lt;p&gt;A focused day on two parallel tracks: planning the SaaS web app stack and deepening the PKM system. Most of the morning went into understanding the Vuexy Next.js template more deeply — specifically how Claude Code can scan and document the entire codebase, and how to structure the monorepo …&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">phurix</dc:creator><pubDate>Wed, 13 May 2026 00:00:00 +0200</pubDate><guid>tag:pelican-5lg.pages.dev,2026-05-13:/daily-journal-2026-05-13.html</guid><category>notes</category><category>[daily]</category></item><item><title>"Journal — May 12, 2026"</title><link>https://pelican-5lg.pages.dev/journal-may-12-2026.html</link><description>&lt;ul&gt;
&lt;li&gt;"[[reference/litellm-claude-code-setup]]"&lt;/li&gt;
&lt;li&gt;"[[reference/cicd-django-nextjs]]"&lt;/li&gt;
&lt;li&gt;"[[reference/claude-code-discord-hook]]"&lt;/li&gt;
&lt;li&gt;"[[reference/systemctl-cheatsheet]]"&lt;/li&gt;
&lt;li&gt;"[[efforts/litellm-local-llm]]"&lt;/li&gt;
&lt;li&gt;"[[efforts/tailscale-docker-alpine]]"&lt;/li&gt;
&lt;li&gt;"[[efforts/pkm-daily-summary]]"&lt;/li&gt;
&lt;li&gt;"[[efforts/vuexy-nextjs-frontend]]"&lt;/li&gt;
&lt;/ul&gt;
&lt;hr /&gt;
&lt;h1 id="may-12-2026"&gt;May 12, 2026&lt;a class="headerlink" href="#may-12-2026" title="Permanent link"&gt;&amp;para;&lt;/a&gt;&lt;/h1&gt;
&lt;h2 id="what-i-worked-on-today"&gt;What I worked on today&lt;a class="headerlink" href="#what-i-worked-on-today" title="Permanent link"&gt;&amp;para;&lt;/a&gt;&lt;/h2&gt;
&lt;p&gt;Heavy day of developer tooling. Three separate threads running in parallel:
connecting Claude Code to local LLMs, building out a CI/CD pipeline,
and continuing to …&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">phurix</dc:creator><pubDate>Tue, 12 May 2026 00:00:00 +0200</pubDate><guid>tag:pelican-5lg.pages.dev,2026-05-12:/journal-may-12-2026.html</guid><category>notes</category><category>[daily</category><category>llm-tooling</category><category>devops</category><category>claude-code]</category></item></channel></rss>