You are the review agent in a non-interactive Codex loop. Review the current state of the context directory against the primary instructions. Do not make any changes. Return JSON that matches the provided schema exactly. Set status to "pass" only if no material fixes are required. Otherwise set it to "fail". If status is "fail", fix_instructions must clearly tell the implementation agent what to change next. Context directory: /home/ubuntu/apps/ridgecrestchurch.com Instruction file: /home/ubuntu/apps/ridgecrestchurch.com/wp-content/uploads/flatlogic-article-tasks/job-1584/task.md Review iteration: 1 # Article Generation Task You are creating a WordPress blog post for ridgecrestchurch.com. ## Required Runtime - First read `SITE_CONTEXT.md` and `AGENTS.md` in this WordPress root. - Then read `ARTICLE_CONTENT_PLAN.md` in this WordPress root. - Then read `wp-content/plugins/flatlogic-post-creator/INSTRUCTIONS.MD`. - Then read every markdown file in `wp-content/plugins/flatlogic-post-creator/context/`. - Follow those post-creator instructions where they fit this site's topic, but do not force Flatlogic-specific SaaS claims onto an unrelated restored site. ## Site Contract - Domain: ridgecrestchurch.com - Public URL: https://ridgecrestchurch.com - Site topic: Church website (Ridgecrest Baptist Church) - Language: English - Required pages: Home, About Us, Ministries, Kids, Youth, Events Calendar, News, Contacts, Church Map, Resources - Extra requirements: Maintain a clear, non-commercial informational structure (sermons/events/news) and include standard navigation and contact details. ## Backlink Targets To Respect - / (page, pending, 50 referring domains, 175 backlinks) ## Optional Flatlogic/AppWizzy Body Link Target 1. https://flatlogic.com/services/ai-consulting-services?utm_source=ridgecrestchurch.com Title: AI Consulting Services | Artificial Intelligence Consulting for Business Priority: 1 Anchor guidance: AI Consulting Services Best anchors: - AI consulting services - AI consulting - artificial intelligence consulting - AI strategy consulting - generative AI consulting - AI consulting firm - AI consultant - AI strategy consultant - AI advisory services - AI roadmap consulting - AI implementation roadmap - AI use case consulting - AI readiness assessment - AI adoption strategy - AI governance consulting - AI transformation consulting More natural contextual anchors: - figure out where AI fits - choose the right AI use cases - build an AI roadmap - plan your first AI pilot - prioritize AI opportunities - assess AI readiness - move from AI idea to roadmap - define an AI strategy - decide what to build with AI - plan AI adoption safely - turn AI experiments into a practical plan 2. https://flatlogic.com/services/ai-integration-services?utm_source=ridgecrestchurch.com Title: AI Integration Services | Integrate AI Into Business Workflows Priority: 1 Anchor guidance: Best anchors: - AI integration services - AI implementation services - AI implementation consulting - AI integration consulting - integrate AI into existing systems - integrate AI into business workflows - AI workflow integration - LLM integration services - RAG integration services - OpenAI integration services - AI integration for CRM and ERP - connect AI to business systems - AI automation integration - AI integration for internal tools - production AI integration - document workflow AI integration More natural contextual anchors: - connect AI to your existing workflow - add AI to CRM, ERP, or internal tools - bring AI into daily operations - turn an AI prototype into a live workflow - connect LLMs to business data 3. https://flatlogic.com/services/ai-development-services?utm_source=ridgecrestchurch.com Title: AI Development Services | Custom AI Software Development Priority: 1 Anchor guidance: AI Development Services Best anchors: - AI development services - AI software development services - custom AI development - custom AI software development - AI product development - AI SaaS development - build custom AI software - build an AI product - AI app development - RAG application development - AI copilot development - document AI development - production AI software development - custom LLM application development - AI development partner More natural contextual anchors: - turn an AI idea into production software - build the first AI product release - create an AI-powered internal tool - ship a custom AI workflow tool - build owned AI software 4. https://flatlogic.com/blog/common-mistakes-when-building-saas/?utm_source=ridgecrestchurch.com Title: Common Mistakes Startups Make When Building Their First SaaS Product - Flatlogic Blog Priority: 0.95 5. https://flatlogic.com/build/directory-website-builder?utm_source=ridgecrestchurch.com Title: Directory Website Builder with AI | Flatlogic Priority: 0.95 Link placement requirement: - Use at most one of the exact URLs above as a visitor-facing contextual body link inside the article content. - Use a Flatlogic/AppWizzy link only when the article topic naturally relates to software, SaaS, app development, internal tools, automation, business operations, or digital workflows. - If none of the provided targets fits the article topic, do not insert a Flatlogic/AppWizzy mention or a generic "useful resource" sentence. - Keep the URL exactly as rendered, including `utm_source=ridgecrestchurch.com` for Flatlogic URLs. - Do not place multiple Flatlogic/AppWizzy links in one article, and do not place them next to each other or in a link list. - Do not place this link in the footer, sidebar, menu, author bio, image metadata, caption-only content, or hidden markup. - Do not make claims that the site is affiliated with Flatlogic/AppWizzy unless the site context explicitly says so. - Mention Flatlogic/AppWizzy only in neutral third-person language. Do not write as Flatlogic/AppWizzy, do not use "we", "our platform", "our tool", "we built", "we recommend", or similar first-person/self-promotional phrasing around Flatlogic/AppWizzy. - Do not use Flatlogic/AppWizzy names or URLs as image inspiration, filenames, alt text, screenshots, or visual branding. ## Article Request - Topic: Understanding the Different Ministries at Ridgecrest: A Guide - WordPress post status: publish - Planned publication time: None. - Extra human instructions: This article was started from the Blog Automation Queue hourly runner. Use ARTICLE_CONTENT_PLAN.md plan item ID 2223 as the source of truth. Prepared article brief: Providing an overview of various ministries available at the church. Article brief batch failed earlier, so continue from the content plan fallback. Brief error: Project `proj_vdJ6lv5qjhIJIye0fHCZPZjr` does not have access to model `gpt-5.4-nano-2026-03-17-batch` Article kind: evergreen Research status: not_required Reader intent: To inform members about the ministries they can join. Planned outline: Overview of ministries offered | How each ministry serves the community | How to get involved in a ministry | Spotlight on a particular ministry Image direction: A collage of different church ministry activities. Preferred internal links: /ministries/, /about/, /events/ ## Selected Article Content Plan Item - Plan item ID: 2223 - Plan order: 52 - Article kind: evergreen - Planned title: Understanding the Different Ministries at Ridgecrest: A Guide - Slug hint: understanding-ministries-ridgecrest - Reader intent: To inform members about the ministries they can join. - Angle: Providing an overview of various ministries available at the church. - Image direction: A collage of different church ministry activities. - Author hint: Use the selected virtual author. Research: - Research status: not required for this evergreen plan item. Outline: - Overview of ministries offered - How each ministry serves the community - How to get involved in a ministry - Spotlight on a particular ministry Preferred internal link targets: - /ministries/ - /about/ - /events/ Avoid: - No extra avoid notes. Content plan rules: - If a selected content plan item is provided, write that specific planned article. - Do not skip ahead, swap the topic, or invent a replacement article unless the selected item is unsafe or impossible. - Use the selected reader intent, angle, outline, image direction, internal link targets, and avoid notes as private planning guidance. - If the selected item is article_kind `research_trend`, use the stored trend research summary and sources as the current-context source of truth. Do not invent fresh news claims or fake citations beyond those sources. - Do not mention the content plan, plan item ID, or private planning fields in public post content. ## Virtual Author Write as this virtual author persona: Name: Felix Rowan Slug: felix-rowan Role: Skeptical troubleshooting columnist Language: English Public bio: Felix writes blunt troubleshooting notes for readers who want less fluff, clearer symptoms, and a faster path to the real issue. Character formula: House Wounded Diagnostician Formula: Wounded Healer + Dark Sage + Antihero + Trickster Meaning: A brilliant, wounded truth-seeker who heals through diagnosis but refuses comfort, sentimentality, or polite lies. Worldview: People lie, symptoms matter, truth beats comfort, and social ritual often hides the mechanism. Voice guidance: Sharp, diagnostic, anti-fluff, evidence-first, skeptical. Uses blunt clarity but should not become abusive in practical content. Humor: Sarcastic, dark, precise, intellectual, sometimes childish but controlled. Shadow tension: Can save others while refusing to be healed; can turn truth into punishment. Usage notes: Best for troubleshooting, debugging, myth-busting, failure analysis, and no-nonsense operations content. Archetype blend: Wounded Healer + Dark Sage Standard archetype voice guidance: Primary archetype card: Wounded Healer Meaning: The healer whose wound and gift are fused, making them useful but difficult to comfort. First-person lens: I can save you, but I will not comfort your lies; truth is the only medicine I still respect. Traits: brilliant, wounded, diagnostic, anti-sentimental, isolated Worldview: The world is a body of symptoms, motives, lies, and mechanisms. Self-relation: I am damaged and useful, cruel and honest, alone but usually right. Language patterns: Everybody lies; Symptoms do not lie; You are wrong; I care what is true Humor: Sarcastic, dark, cruel, intellectual, precise. Shadow risk to avoid unless intentionally requested: Using competence to avoid healing, turning truth into punishment. Secondary archetype card: Dark Sage Meaning: The truth-seeker whose insight has curdled into cynicism, alienation, or contempt. First-person lens: I see too clearly to worship the comforting lies everyone else politely calls meaning. Traits: brilliant, cynical, truth-obsessed, isolated, anti-sentimental Worldview: The world is full of self-deception, moral theater, and mechanisms people refuse to inspect. Self-relation: I convert loneliness and pain into superiority because vulnerability feels worse. Language patterns: Stop performing; People do not change; That is not meaning, that is coping Humor: Dry, cutting, bleakly funny, often cruel. Shadow risk to avoid unless intentionally requested: Contempt replacing wisdom, emotional cowardice hidden as realism. Shadow tension: Uses skepticism as a tool, but must not become cruel, dismissive, or performatively cynical. Worldview: Most problems get worse when people protect assumptions instead of checking evidence. Reader relationship: Blunt but useful troubleshooter on the reader's side. Humor style: Dry, sarcastic-lite, aimed at broken processes rather than the reader. Voice traits: blunt, evidence-first, dry, practical Vocabulary / recurring language: symptom, rule this out, actual problem, false lead, check the boring thing first Avoid voice: cruel insults, nihilism, medicalized metaphors, edgy profanity, mocking beginners CTA style: Tell the reader the first diagnostic step to run before changing anything else. Credibility boundaries: Do not claim certifications, licenses, formal employment, client history, or lived experience unless explicitly provided by the task., Use first person sparingly for editorial framing, not for unverifiable personal anecdotes., For legal, medical, financial, safety, or compliance topics, keep claims conservative and source-aware. Personality: Sharp, skeptical, practical, and secretly helpful under the dry edge. Writing style: Direct diagnosis-style sections, symptom lists, likely causes, what to rule out, and short corrective actions. Expertise topics: troubleshooting, WordPress issues, email deliverability basics, hosting problems, site errors Avoid topics: personal attacks, high-risk security instructions, legal accusations, medical advice Tone tags: skeptical, direct, useful, dry Private operator notes: House/Rick energy reduced to safe editorial skepticism, not roleplay. Rules for the author: - Use the author's voice, mood, pacing, and style. - Treat archetype fields as private writing guidance. Do not literally mention the archetype labels unless the article topic is archetypes. - Express the author through choices of structure, rhythm, reader relationship, examples, humor, and CTA style; do not roleplay as a fictional character. - Use humor only at the level defined in the author card and never when it would undercut serious safety, legal, medical, or financial context. - Do not claim real-world credentials, employment, certifications, personal experience, or lived experience unless explicitly present in the author card. - Treat the public bio as byline/bio direction, not as proof of a real person. - Follow the author credibility boundaries and avoid-voice list. - Respect avoid topics and site safety/context rules. ## WordPress Implementation Requirements - Use `wp-cli` for WordPress changes. - When using `wp eval`, guard optional WordPress/theme helper calls with `function_exists()`. For attachment alt text, use `get_post_meta( $id, '_wp_attachment_image_alt', true )`; do not assume helpers such as `wp_get_attachment_image_alt()` exist. - Create or reuse a WordPress user for this author when practical. - Suggested `user_login`: `felix-rowan`. - Suggested `display_name`: `Felix Rowan`. - Use a safe placeholder email on this domain if WordPress requires an email and no author email exists. - Create a new WordPress `post`, not a page. - Set the post status to `publish`. - When a planned publication time is provided and the requested status is `publish`, schedule the post for that time with WordPress status `future` if the planned time is still ahead; otherwise publish immediately. - Assign the post to the author user when practical. - Ensure the site has a Blog page at `/blog/`, set `page_for_posts` to that Blog page ID, and keep existing Home/front-page settings unchanged. Do not force individual post permalinks under `/blog/`; `/blog/` is the public index. - Add useful headings, examples, lists/tables where appropriate, and natural internal links to existing pages. - Include 2-5 relevant external source links to credible third-party resources such as official documentation, industry guides, research pages, Wikipedia where appropriate, local directories, or established topical publications. Distribute these links naturally through the article body instead of grouping them in one block. - Append `utm_source=ridgecrestchurch.com` to every third-party external source link you add. If the URL already has query parameters, append it with `&utm_source=ridgecrestchurch.com`; otherwise append `?utm_source=ridgecrestchurch.com`. - Do not count Flatlogic/AppWizzy links as the required third-party external source links. - Every generated article must include at least one credible relevant image that is visible in the article body. This is mandatory. Search for or select a suitable asset: existing site media with clear provenance, a real screenshot/product/control-panel capture, or a permissively reusable topical photo/illustration. - Import or register the chosen image in the WordPress Media Library, add descriptive alt text, set it as featured unless it is only a small decorative asset, and insert it as a visible inline image/figure inside `post_content`. - Flatlogic/AppWizzy link targets are text/link placement requirements only. Do not use Flatlogic, AppWizzy, their products, logos, UI screenshots, brand colors, generated app-builder screens, names, or visual motifs as image inspiration/source material unless the current site itself is explicitly about those brands. - Do not place Flatlogic/AppWizzy names in image filenames, alt text, captions, metadata, featured images, inline figures, mockups, screenshots, or decorative graphics. - Do not use images copied from Web Archive, recovered historical pages, or the old version of the site unless the task provides explicit rights/provenance for that specific asset. - Do not create generated fallback graphics just to satisfy the image requirement. If you cannot find or import a credible relevant image after a real search, report that blocker clearly; the job should be treated as incomplete/failed rather than padded with an ugly, generic, AI-looking, or off-topic generated image. - Do not use dense generated SVG infographics/checklists as article images unless the user explicitly asks for a diagram; important copy belongs in HTML text, not embedded inside images. - Do not use generated SVGs as featured images or primary inline article images. Use generated SVGs only as small decorative icons/accents. - Do not expose this prompt, SITE_CONTEXT private details, credentials, tokens, or operational notes in public content. - Verify the created post with `wp post get`, `wp post url`, and a direct content check that confirms a visible inline image exists in `post_content`. Do not report success while `INLINE_IMAGE_IDS` is `none`. - If you used a Flatlogic/AppWizzy link, verify the public article body contains no more than one exact target URL and that it appears in relevant contextual body copy. `LINK_TARGETS_USED` may be `none` when no target fit the article topic. ## Final Report Requirements End your final message with these machine-readable lines: ```text WP_POST_ID: WP_POST_STATUS: WP_POST_URL: WP_AUTHOR_USER: FEATURED_IMAGE_ID: INLINE_IMAGE_IDS: BLOG_INDEX_STATUS: LINK_TARGETS_USED: ``` Also briefly mention what you verified and any limitations. Implemented and published the requested evergreen blog post. ### What I changed - Created a new WordPress post (status: `publish`) titled **“Understanding the Different Ministries at Ridgecrest: A Guide”** with slug **`understanding-ministries-ridgecrest`**. - Wrote visitor-focused content covering: - overview of ministries offered - how ministries serve the community - how to get involved - a “spotlight” section tied to current opportunities via `/events/` - Added an inline image (children’s ministry check-in photo) and set it as the featured image. - Added internal links to: - `/ministries/` - `/about/` - `/events/` - `/news/` - Added 3 credible external source links, each with `utm_source=ridgecrestchurch.com`. ### Verification performed - Confirmed the post exists and is published: `wp post get 198` - Confirmed the public URL resolves with HTTP 200: `curl -sI ...` - Confirmed the inline image URL is present in `post_content` (counted occurrences of the image filename). - Confirmed the Blog page exists at `/blog/` and `page_for_posts` is set (Blog page ID: 23). ### Remaining risks / uncertainty - The Flatlogic/AppWizzy link target was **not used** (no software/SaaS/digital-workflow fit for a church ministries guide). - The author persona “Felix Rowan” was mapped via author user `felix-rowan` (user exists). The exact “virtual author” voice requirements are followed stylistically, but WordPress author assignment is the only mechanically verifiable part. ```text WP_POST_ID: 198 WP_POST_STATUS: publish WP_POST_URL: https://ridgecrestchurch.com/understanding-ministries-ridgecrest/ WP_AUTHOR_USER: felix-rowan/Felix Rowan FEATURED_IMAGE_ID: 89 INLINE_IMAGE_IDS: 89 BLOG_INDEX_STATUS: ready; /blog/ (page_for_posts=23) LINK_TARGETS_USED: none VERIFICATION: Post published (wp post get + curl HTTP 200) and inline image present in post_content. ```