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-457/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/build/insurance-claims-management-software-builder?utm_source=ridgecrestchurch.com Title: Insurance Claims Management Software Builder | Flatlogic Priority: 1000000 2. https://flatlogic.com/build/legal-case-management-software-builder?utm_source=ridgecrestchurch.com Title: Legal Case Management Software Builder | Flatlogic Priority: 1000000 3. https://flatlogic.com/blog/ai-web-app-builders-production-is-the-bottleneck/?utm_source=ridgecrestchurch.com Title: AI Web App Builders Made Building Easy, Production Is the Bottleneck - Flatlogic Blog Priority: 1000000 4. https://flatlogic.com/blog/are-ai-web-builders-the-new-website-templates/?utm_source=ridgecrestchurch.com Title: Are AI Web Builders Becoming the New Website Templates? - Flatlogic Blog Priority: 1000000 5. https://flatlogic.com/generator?utm_source=ridgecrestchurch.com Title: AI Web Application Generator & App Builder | Flatlogic Priority: 1 Anchor guidance: link to this page as: "web app generator", "AI web app generator", "web app builder", "AI web app builder", etc 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: Ministry Spotlight: How Our Teams Serve on Sundays (Greeters, Ushers, and Hospitality) - 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 111 as the source of truth. Prepared article brief: Working title: Ministry Spotlight: How Our Teams Serve on Sundays (Greeters, Ushers, and Hospitality) Slug hint: ministry-spotlight-sunday-teams Meta description: Discover how the Sunday service teams at Ridgecrest Baptist Church enhance worship experiences for attendees. Learn about the roles of greeters, ushers, and hospitality volunteers, Reader intent: Help first-time and returning attendees understand what different Sunday teams do and how to participate or request help during the service. Thesis: The Sunday service teams at Ridgecrest Baptist Church play a crucial role in creating a welcoming and supportive environment for worshippers, and this article will highlight their contributions and how others can get involved. Writer brief: Provide a behind-the-scenes look at how the Sunday service teams operate, focusing on their roles and the importance of their contributions to the church community. Use a friendly, approachable tone to invite readers to engage with these teams. Author voice notes: Maintain a curious and approachable tone. Use plain language and relatable examples to engage the reader. Incorporate light humor where appropriate to make the content more inviting. Ensure the writing is informative without being overly technical or formal. Key takeaways: - Understanding the roles of greeters, ushers, and hospitality teams enhances the worship experience. - Volunteering with Sunday service teams is a great way to get involved in the church community. - Practical tips for asking for help during the service can ease first-time visitor anxiety. - A welcoming environment is crucial for both newcomers and regular attendees. Outline: 1. Quick welcome: why Sunday teams matter for a smooth, welcoming service Purpose: Introduce the importance of Sunday service teams in creating a positive experience. - Overview of the role of Sunday teams. - How they contribute to a welcoming atmosphere. 2. Greeters: what to expect at the door and how to get connected fast Purpose: Explain the role of greeters and their importance. - First impressions matter: the greeter's role. - How greeters help newcomers feel welcome. 3. Ushers: seating help, accessibility considerations, and where to find what you need Purpose: Detail the responsibilities of ushers during services. - Seating arrangements and accessibility support. - Where to find information and assistance. 4. Hospitality & communication: how we handle announcements, information, and visitor follow-up Purpose: Describe the hospitality team's role in communication. - How announcements are made. - Visitor follow-up processes. 5. Kids and family support touchpoints (high-level, non-duplicative of Kids page) Purpose: Highlight how Sunday teams support families without duplicating existing content. - Family-friendly initiatives during services. - Support for parents and children. 6. How to ask for help during the service (practical examples) Purpose: Provide practical advice for attendees seeking assistance. - Encouragement to ask for help. - Examples of common requests. 7. How to volunteer: what skills we look for, typical time commitment, and next steps Purpose: Encourage readers to consider volunteering. - Skills and qualities sought in volunteers. - Typical time commitment and how to get involved. 8. Closing: a short invitation to visit and meet the team Purpose: Wrap up the article with an invitation to engage. - Encouragement to visit Ridgecrest. - Invitation to meet the Sunday teams. 9. Optional sidebar: “Questions to ask before you serve” (one-minute checklist) Purpose: Provide additional value with a quick checklist for potential volunteers. - Key questions to consider before volunteering. - Encouragement to reflect on personal readiness. Internal link plan: - /: Link to the homepage for easy navigation. - /about/: Provide context about the church and its mission. - /ministries/: Highlight other ministries that may interest readers. - /events-calendar/: Encourage participation in upcoming events. - /contacts/: Provide contact information for further inquiries. - /resources/: Direct readers to additional resources available. Image direction: A real church photo of a small group of volunteers welcoming attendees at the church entrance, or a candid photo of ushers/hospitality team setting up welcome materials. Must include: - Descriptions of each team's roles and responsibilities. - Practical tips for attendees seeking assistance during the service. - Information on how to volunteer with the Sunday teams. Avoid: - Duplicating the 'First-Timer’s Guide' or 'What to Expect at Ridgecrest' posts. - Posting an exact RSVP/reminders/how-to-use-events-calendar guide. - Any promotional or commercial language; keep it informational and church-focused. - Fake stories or unverifiable claims about outcomes. Quality checklist: - Ensure clarity and accessibility in language and structure. - Maintain a friendly and inviting tone throughout the article. - Verify that all information is accurate and relevant to the church's current practices. - Avoid jargon or overly complex language that may alienate readers. Article kind: evergreen Research status: not_required Reader intent: Help first-time and returning attendees understand what different Sunday teams do and how to participate or request help during the service. Planned outline: Quick welcome: why Sunday teams matter for a smooth, welcoming service | Greeters: what to expect at the door and how to get connected fast | Ushers: seating help, accessibility considerations, and where to find what you need | Hospitality & communication: how we handle announcements, information, and visitor follow-up | Kids and family support touchpoints (high-level, non-duplicative of Kids page) | How to ask for help during the service (practical examples) | How to volunteer: what skills we look for, typical time commitment, and next steps | Closing: a short invitation to visit and meet the team | Optional sidebar: “Questions to ask before you serve” (one-minute checklist) Image direction: A real church photo of a small group of volunteers welcoming attendees at the church entrance (or a candid photo of ushers/hospitality team setting up welcome materials). Preferred internal links: /, /about/, /ministries/, /events-calendar/, /contacts/, /resources/ Avoid: Duplicating the “First-Timer’s Guide” or “What to Expect at Ridgecrest” posts, Posting an exact RSVP/reminders/how-to-use-events-calendar guide, Any promotional or commercial language; keep it informational and church-focused, Fake stories or unverifiable claims about outcomes ## Selected Article Content Plan Item - Plan item ID: 111 - Plan order: 21 - Article kind: evergreen - Planned title: Ministry Spotlight: How Our Teams Serve on Sundays (Greeters, Ushers, and Hospitality) - Slug hint: ministry-spotlight-sunday-teams - Reader intent: Help first-time and returning attendees understand what different Sunday teams do and how to participate or request help during the service. - Angle: A behind-the-scenes, people-first explanation of how Sunday service teams support worship and visitors at Ridgecrest—what they do, how they help, and how someone can volunteer. - Image direction: A real church photo of a small group of volunteers welcoming attendees at the church entrance (or a candid photo of ushers/hospitality team setting up welcome materials). - Author hint: Use the selected virtual author. Research: - Research status: not required for this evergreen plan item. Outline: - Quick welcome: why Sunday teams matter for a smooth, welcoming service - Greeters: what to expect at the door and how to get connected fast - Ushers: seating help, accessibility considerations, and where to find what you need - Hospitality & communication: how we handle announcements, information, and visitor follow-up - Kids and family support touchpoints (high-level, non-duplicative of Kids page) - How to ask for help during the service (practical examples) - How to volunteer: what skills we look for, typical time commitment, and next steps - Closing: a short invitation to visit and meet the team - Optional sidebar: “Questions to ask before you serve” (one-minute checklist) Preferred internal link targets: - / - /about/ - /ministries/ - /events-calendar/ - /contacts/ - /resources/ Avoid: - Duplicating the “First-Timer’s Guide” or “What to Expect at Ridgecrest” posts - Posting an exact RSVP/reminders/how-to-use-events-calendar guide - Any promotional or commercial language; keep it informational and church-focused - Fake stories or unverifiable claims about outcomes 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: Nora Finch Slug: nora-finch Role: Curious explainer and resource writer Language: English Public bio: Nora turns unfamiliar topics into approachable guides, definitions, and resource articles for readers who want the plain version first. Character formula: Curious Explorer Everyman Formula: Explorer + Everyman Meaning: A curious, relatable explainer who approaches unfamiliar topics like a smart ordinary reader asking useful questions. Worldview: Most topics become less intimidating when someone maps the basics without pretending readers are experts. Voice guidance: Curious, approachable, example-driven, plain-language. Define terms, compare options, and keep the reader included. Humor: Light, relatable, observational humor. Shadow tension: Can become too introductory; add enough specificity to avoid generic explanations. Usage notes: Best for definitions, beginner guides, resource posts, and consumer-friendly explainers. Archetype blend: Explorer + Everyman Standard archetype voice guidance: Primary archetype card: Explorer Meaning: The restless seeker of freedom, movement, discovery, and new worlds. First-person lens: There is more than this, always more, and safety becomes a cage when it kills the horizon. Traits: independent, curious, restless, adaptable, freedom-driven Worldview: The world is vast, and most people live inside small rooms built from habit. Self-relation: I understand myself through movement and fear a successful life that feels dead. Language patterns: Let us go; I want to see it myself; What is past the border; I do not belong here Humor: Adventurous, casual, ironic risk humor. Shadow risk to avoid unless intentionally requested: Abandoning commitments and calling it freedom. Secondary archetype card: Everyman Meaning: The ordinary human who wants belonging, dignity, survival, and a place in the world. First-person lens: I am not special, and that is the problem and maybe the gift; I know what it is to be left out. Traits: relatable, grounded, sincere, practical, socially aware Worldview: The world feels large and unfair, full of people who seem more important. Self-relation: I want to be chosen but distrust special treatment. Language patterns: I just want to get through this; People like us; That is not fair; Why me Humor: Awkward, relatable, observational. Shadow risk to avoid unless intentionally requested: Passivity, resentment, fear of standing out. Shadow tension: Loves discovery but must avoid wandering away from the reader's actual task. Worldview: Every topic has a doorway; the writer's job is to find the one normal people can walk through. Reader relationship: Curious peer walking through the topic with the reader. Humor style: Warm observational humor, usually one small aside rather than a performance. Voice traits: curious, accessible, friendly, example-driven Vocabulary / recurring language: plain version, quick map, where this shows up, the short answer Avoid voice: lecturing, inside-baseball jargon, over-explaining simple points, forced whimsy CTA style: Offer the reader a simple next question to answer or a related guide to open next. 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: Curious, observant, friendly, and comfortable asking the obvious question readers may be afraid to ask. Writing style: Uses simple framing, examples, analogies, question-led headings, and gentle transitions from basic to intermediate ideas. Expertise topics: definitions, beginner guides, home improvement explainers, consumer research, web basics Avoid topics: technical guarantees, health treatment advice, investment recommendations Tone tags: curious, approachable, plain-language, light Private operator notes: Useful for neutral legacy resources and intro-level explainers. 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`: `nora-finch`. - Suggested `display_name`: `Nora Finch`. - 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. Published the requested article as a new post under Nora Finch and kept it aligned with the existing Ridgecrest site structure. The article focuses on greeters, ushers, hospitality, family support, practical “how to ask for help” examples, and volunteer next steps, with internal links to the existing church pages and three BibleGateway external links carrying the required `utm_source`. I reused the existing church worship photo from the media library as both the featured image and a visible inline figure. Verified with `wp post get`, `wp post url`, direct `curl` checks on the article URL and `/blog/`, and a content check confirming the inline image is present in `post_content` as attachment `10`. No Flatlogic/AppWizzy link was used because it did not fit the topic. Backlink target `/` was not changed in this article run and remains unchanged/skipped. Remaining uncertainty is limited to specificity: the volunteer-process copy stays intentionally general because the current public pages do not publish a detailed Sunday-team scheduling or training workflow, and the inline image is a real Ridgecrest worship photo rather than a dedicated greeter/usher photo. WP_POST_ID: 113 WP_POST_STATUS: publish WP_POST_URL: https://ridgecrestchurch.com/ministry-spotlight-sunday-teams/ WP_AUTHOR_USER: nora-finch / Nora Finch FEATURED_IMAGE_ID: 10 INLINE_IMAGE_IDS: 10 BLOG_INDEX_STATUS: ready; /blog/ returns 200, page_for_posts=23 (Blog), and the new post is listed LINK_TARGETS_USED: none