AI.IQ Article 2 — staying-current-with-ai goes from stub to full prose

What was done

Replaced the “coming soon” stub body at src/pages/dev-iq/ai-iq/staying-current-with-ai.astro with the full article. Structure follows PLAN.md §6:

1. The overload problem
2. The four-line filter (limit inputs, schedule it, build don’t just read, filter for relevance)
3. Follow builders, not hype
4. Trust, but test
5. The podcast — Moonshots
6. The distillation layer (moonshots.botgui.de with disclosure)
7. Pattern recognition across episodes
8. The north star
9. Why this matters for an engineering firm

Source material was .tmp/0005_26_05_11_ai_section_and_article/ask.md, which already contained Ryan’s spine — the TL;DR, the four-rule filter, the “find a podcast where you’re not the smartest person in the room” line, the four-bucket botgui.de structure, the north star quote. Work was structural polish + transitions + the engineering-firm closer; no new opinions invented.

Specific decisions

• Voice: First-person Ryan throughout. The PageHero now reads “By Ryan Benson · May 2026 · 8 min read” in the meta line.
• Sponsor disclosure: Applied twice — once in the TL;DR card, once in §6 when re-introducing botgui.de. Matches the pattern in PLAN.md §6.
• Internal links: Closer (§9) links to both /dev-iq/ai-iq/getting-found-by-ai/ and /dev-iq/land-use-intelligence/ to ladder up to Bailey’s “same discipline” thesis.
• External links: Only moonshots.botgui.de, marked rel="noopener sponsored" per Google’s guidance on linking to owned property.
• Headings: Every <h2> carries a stable id (e.g., #the-four-line-filter, #north-star) so the article is deep-linkable.
• Schema: Article JSON-LD only; no FAQPage (article is essay-shaped, not Q&A). Author = Person, Ryan Benson at /about/ryan-benson/.
• CTA: Routes to /contact/?topic=feedback per the BACKLOG decision (no ?topic=ai-workflow taxonomy added).
• Source landscape (§3): Newsletter row (Rundown AI, TLDR AI, The Batch), YouTube row (AI Explained, Matt Wolfe), community row (r/LocalLLaMA, r/MachineLearning) — all current as of the knowledge cutoff. None pruned.

Why

Ryan green-lit “proceed with what we have” after my honest read that ask.md alone gives a competent-but-generic listicle rather than a Bailey-shaped piece. The article ships now because the moonshots.botgui.de section + the engineering-firm closer carry enough weight to justify publication. A follow-up “Part 2” with a specific anecdote and a Bailey-engineering tool use case is queued in BACKLOG.md as a potential refresh.

Verification

• npm run build clean; 208 pages, 124 Pagefind-indexed (up from 123 — the article now has indexable body content), 5,312 indexed words (up from 5,124).
• dist/dev-iq/ai-iq/staying-current-with-ai/index.html renders all 9 sections with stable anchor IDs.
• Article JSON-LD @id correct.
• Internal links resolve, external link carries rel="noopener sponsored".

Files affected

Modified:

• src/pages/dev-iq/ai-iq/staying-current-with-ai.astro — stub body replaced with full prose; PageHero meta updated; styles refactored from .stub-card to .tldr-card + .article-body prose styles.

Created:

• src/content/devlog/2026-05-11-staying-current-with-ai-prose.md (this entry).

What’s still backlog

• Future v2 / Part 2: a specific anecdote (claim Ryan tested + outcome), a Bailey-engineering AI tool use case (the Eagle Nephi research workflow is the obvious candidate), and a vulnerability moment where the AI was wrong. Per BACKLOG.md “AI.IQ section follow-ups” — not a v1 blocker.
• Contact-form ?topic=ai-workflow — deferred per BACKLOG decision; revisit if this article generates volume.

Cadence

Per CLAUDE.md “trickle, don’t dump”: this is the first new module of the week. Eagle Article 1 (.tmp/0004_26_05_11_eagle_article/PLAN.md) is the natural next ship.

AI-visibility re-test

Per memory feedback_visibility_retest_cadence.md, do not re-run the 10 AI-visibility queries earlier than three weeks after deploy. Earliest re-test 2026-06-01.