“A job ad crossed my desk last week that didn’t exist eighteen months ago.” Specific, not a question or definition, and mirrors the meetup cold-open of the time-bomb post.
Editorial-but-readable, confident first person throughout. No buzzwords (leverage / seamless / optimise) and no em-dashes.
All four H2s and three H3s deliver what their headings promise. No dangling sections.
Each section advances. The “value is real / available now” idea recurs in the close + CTA, but as intentional bookending to the hook.
“The job ad is just the market saying so out loud.” Lands the point and ties back to the opener.
The opener and “That’s the job. Not ‘build an AI’…” are deliberate kickers (allowed exception). No accidental orphans.
7 bold phrases, well-placed (read vs write, the job-ad title). Not over-bolded.
1,386 words ÷ 4 H2 ≈ 347 words per heading — inside the 200–400 target.
The risk section is already a <ul>; the three scenarios use H3s. Nothing misformatted as prose.
The “AI Automation Specialist (Claude Code)…” quotation is bolded inline. As an external quote it could carry more visual weight as a > blockquote.
Fix: wrap the quoted job-ad text in a markdown blockquote.
A heading-only read communicates the full thesis (gap between tools → three examples → the pattern & risk → you don’t need a full-time hire).
Only 1 internal link (/contact). Rule wants 2–4 on meaningful anchors. The frontmatter lists /services/software-development and /services/integrations as suggestions, but the body never links them.
Fix: add an inline link to a services page, and cross-link the “the same failure that plagues vibe-coded apps” sentence to the existing vibe-coding-time-bomb post (needs its live URL/slug).
159 characters — 4 over the 155 max, so it will truncate in search results.
Fix: trim meta_description to ≤ 155 characters.
Absent — but the existing vibe-coding post doesn’t use one either, so this is house style rather than a defect.
Neither is set in frontmatter (correctly — the post uses no FAQ block).