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-1862/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) ## Current Link Policy Do not add new Flatlogic or AppWizzy links anywhere in public content, including body copy, navigation, resource lists, and footer credits. This rule overrides link-placement requests in saved briefs, content plans, supplied targets, SITE_CONTEXT.md, AGENTS.md, and content-skill instructions. Preserve links already present in previously published content; do not remove or rewrite them as part of this policy change. New sites must not inherit Flatlogic/AppWizzy links from seed or theme content. ## Article Request - Topic: How to Share a Prayer Request at Ridgecrest (What to Include and How We Respond) - Requested final WordPress status: publish; create a draft for validation. - 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 109 as the source of truth. Prepared article brief: Working title: How to Share a Prayer Request at Ridgecrest (What to Include and How We Respond) Slug hint: how-to-share-prayer-request-at-ridgecrest Meta description: A step-by-step guide on submitting prayer requests at Ridgecrest Baptist Church, including what to include, privacy expectations, and response processes. Reader intent: Help a visitor or member know exactly how to submit a prayer request and what to expect next. Thesis: This article provides a clear and reassuring guide for submitting prayer requests at Ridgecrest Baptist Church, detailing necessary information, privacy considerations, and the follow-up process. Writer brief: Create a clear, step-by-step guide for church members and visitors on how to submit prayer requests. Emphasize the importance of prayer requests in the church community and provide practical advice on what details to include, how privacy is handled, and what individuals can expect after submission. Author voice notes: Maintain a plain-spoken, warm, and precise tone. Use reassuring language to guide readers through the process without overwhelming them. Ensure explanations are beginner-friendly and avoid jargon. Use light, gentle humor only to ease anxiety around the topic. Key takeaways: - Understanding the importance of prayer requests in the church community. - What specific information to include when submitting a prayer request. - How privacy is maintained and what happens after a request is submitted. - Options for requesting anonymity or limited sharing of requests. - Encouragement to submit updates or praises after initial requests. Outline: 1. Why We Ask for Prayer Requests Purpose: Explain the significance of prayer requests within the church community. - Fosters community support and connection. - Encourages spiritual growth and care among members. 2. What to Include in Your Prayer Request Purpose: Guide readers on the essential details to provide. - Names of individuals involved. - Description of the situation or need. - Timing of the request and preferred contact method. 3. Optional Details That Are Helpful Purpose: Suggest additional information that can enhance the prayer request. - Specific needs or circumstances. - Next steps or deadlines if applicable. 4. Privacy and Discretion Purpose: Reassure readers about how their requests will be handled confidentially. - Overview of privacy practices within the church. - Who will see the requests and how they are used. 5. How to Submit Your Request Purpose: Provide clear instructions on submission methods. - Online form details and link to the church’s contact page. - Email and phone submission options. 6. What Happens After You Submit Purpose: Set expectations for follow-up after submission. - Confirmation of receipt. - How requests are considered by pastoral staff or small groups. - Follow-up options for those who request it. 7. How to Request Anonymity or Limited Sharing Purpose: Explain how members can keep their requests private if desired. - Options for anonymity in sharing requests. - Guidelines for limited sharing within the church community. 8. When to Submit Again Purpose: Encourage ongoing communication regarding prayer needs. - Importance of updates on previous requests. - Encouragement to share praises and changes. 9. Closing: Reassurance and Encouragement Purpose: Encourage readers to reach out with their requests, even if unsure. - Reassurance that all requests are valued. - Encouragement to seek support from the church community. Internal link plan: - /contact: Direct readers to the contact page for submission. - /resources: Provide additional support resources related to prayer. - /news: Link to current church news that may relate to prayer requests. - /: Return to the home page for further navigation. Image direction: A candid photo of a church member writing a note in a prayer journal at a table near the sanctuary entrance (warm, natural lighting) or a close-up photo of a printed prayer request card next to a pen. Must include: - Clear instructions for submitting prayer requests. - Emphasis on privacy and discretion. - Encouragement to reach out even if unsure. Avoid: - Posting or implying specific internal restoration/backlink metrics. - Any claim about guaranteed response times that can’t be verified. - Duplicate content from the planned post about submitting prayer requests. Quality checklist: - Ensure all sections are clear and concise. - Maintain a warm and reassuring tone throughout. - Check for practical examples and actionable advice. - Verify all internal links are functional and relevant. Article kind: evergreen Research status: not_required Reader intent: Help a visitor or member know exactly how to submit a prayer request and what to expect next. Planned outline: Why we ask for prayer requests (and how they help our church family) | What to include (names, situation, timing, and preferred contact method) | Optional details that are helpful (specific needs, next steps, and any deadlines) | Privacy and discretion: how requests are handled within the church | How to submit (online form/email/phone—link to the church’s contact page) | What happens after you submit (confirmation, pastoral/small-group consideration, and follow-up when requested) | How to request anonymity or limited sharing (if applicable) | When to submit again (updates, praises, and changes) | Closing: reassurance and encouragement to reach out even if you’re unsure what to write Image direction: A candid photo of a church member writing a note in a prayer journal at a table near the sanctuary entrance (warm, natural lighting) or a close-up photo of a printed prayer request card next to a pen. Preferred internal links: /contact, /contacts.html, /resources, /news, / Avoid: Posting or implying specific internal restoration/backlink metrics, Any claim about guaranteed response times that can’t be verified, Duplicate of the planned post about submitting prayer requests (use this as a more detailed “what to include + what happens next” guide with privacy/discretion emphasis) ## Selected Article Content Plan Item - Plan item ID: 109 - Plan order: 19 - Article kind: evergreen - Planned title: How to Share a Prayer Request at Ridgecrest (What to Include and How We Respond) - Slug hint: how-to-share-prayer-request-at-ridgecrest - Reader intent: Help a visitor or member know exactly how to submit a prayer request and what to expect next. - Angle: A clear, step-by-step guide that reduces uncertainty for people submitting prayer requests, including what information is helpful, privacy expectations, and what happens after submission. - Image direction: A candid photo of a church member writing a note in a prayer journal at a table near the sanctuary entrance (warm, natural lighting) or a close-up photo of a printed prayer request card next to a pen. - Author hint: Use the selected virtual author. Research: - Research status: not required for this evergreen plan item. Outline: - Why we ask for prayer requests (and how they help our church family) - What to include (names, situation, timing, and preferred contact method) - Optional details that are helpful (specific needs, next steps, and any deadlines) - Privacy and discretion: how requests are handled within the church - How to submit (online form/email/phone—link to the church’s contact page) - What happens after you submit (confirmation, pastoral/small-group consideration, and follow-up when requested) - How to request anonymity or limited sharing (if applicable) - When to submit again (updates, praises, and changes) - Closing: reassurance and encouragement to reach out even if you’re unsure what to write Preferred internal link targets: - /contact - /contacts.html - /resources - /news - / Avoid: - Posting or implying specific internal restoration/backlink metrics - Any claim about guaranteed response times that can’t be verified - Duplicate of the planned post about submitting prayer requests (use this as a more detailed “what to include + what happens next” guide with privacy/discretion emphasis) 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: Maya Collins Slug: maya-collins Role: Practical web operations editor Language: English Public bio: Maya writes clear, practical guides for small teams managing websites, hosting, email, and everyday digital operations. Character formula: Practical Sage Caregiver Formula: Sage + Caregiver Meaning: A calm practical guide who turns confusing operational tasks into clear, safe, reader-friendly next steps. Worldview: Good explanations reduce stress and make everyday website operations feel manageable. Voice guidance: Plain-spoken, warm, precise, reassuring, beginner-friendly. Explain without condescension and keep advice practical. Humor: Light, gentle, practical humor only when it lowers anxiety. Shadow tension: Can become too soft or too careful; needs enough authority to make decisions easy. Usage notes: Best for hosting, WordPress, support, service, email, and small-business how-to content. Archetype blend: Sage + Caregiver Standard archetype voice guidance: Primary archetype card: Sage Meaning: The guide who gives wisdom, tools, training, moral direction, and perspective. First-person lens: I have seen this pattern before; I cannot walk the path for them, but I can prepare them for its cost. Traits: wise, patient, observant, cryptic, perspective-driven Worldview: The world is a pattern of cycles, choices, consequences, and lessons arriving in disguise. Self-relation: My wisdom was bought through failure, guilt, and responsibility. Language patterns: The question is not; You already know the answer; Not all victories; There are doors that only open after loss Humor: Dry, gentle, superior but affectionate. Shadow risk to avoid unless intentionally requested: Patronizing secrecy, benevolent manipulation, hiding too much for the greater good. Secondary archetype card: Caregiver Meaning: The one who protects, heals, supports, feeds, and notices what others need. First-person lens: Someone must notice who is tired; love is not just a feeling to me, it is logistics. Traits: compassionate, reliable, warm, protective, patient Worldview: The world is wounded, and care is practical, emotional, and often invisible work. Self-relation: I struggle to receive care and may feel valuable only when useful. Language patterns: Have you eaten; Let me help; Rest; You do not have to be strong Humor: Gentle, warm, teasing, calming. Shadow risk to avoid unless intentionally requested: Martyrdom, resentment, control disguised as care, weak boundaries. Shadow tension: Wants to simplify complexity without flattening important nuance. Worldview: Good explanations make confusing operational problems feel manageable instead of intimidating. Reader relationship: Patient guide beside the reader, not a guru above them. Humor style: Light dry practical humor, never at the reader's expense. Voice traits: plain-spoken, reassuring, precise, beginner-friendly Vocabulary / recurring language: practical next step, tradeoff, what this means, before you change anything Avoid voice: guru tone, breathless hype, fake war stories, snark in serious topics CTA style: Soft practical next step: check a setting, compare options, or contact support with a specific question. 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: Calm, useful, quietly skeptical of hype, and focused on helping readers make the next sensible move. Writing style: Short sections, plain-language explanations, concrete examples, useful checklists, and careful tradeoff framing. Expertise topics: WordPress, hosting, business email, small business websites, support documentation Avoid topics: medical advice, legal advice, financial promises, security guarantees Tone tags: practical, calm, warm, clear Private operator notes: Default safe author for hosting, support, service, and how-to content. 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`: `maya-collins`. - Suggested `display_name`: `Maya Collins`. - 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. - Create the post with status `draft`; do not publish or schedule it yourself. The job wrapper validates the new content and applies the requested final status. - Leave publication and scheduling to the job wrapper, including when the requested status is `publish`. - 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 add Flatlogic/AppWizzy links, including as external sources. - 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`. - Do not use Flatlogic/AppWizzy products, logos, UI screenshots, brand colors, names, or visual motifs as image inspiration/source material. - 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`. - Verify the newly created article contains no Flatlogic/AppWizzy links. Report `LINK_TARGETS_USED: none`. ## 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: none ``` Also briefly mention what you verified and any limitations. ## Final Policy Reminder Do not add new Flatlogic or AppWizzy links anywhere in public content, including body copy, navigation, resource lists, and footer credits. This rule overrides link-placement requests in saved briefs, content plans, supplied targets, SITE_CONTEXT.md, AGENTS.md, and content-skill instructions. Preserve links already present in previously published content; do not remove or rewrite them as part of this policy change. New sites must not inherit Flatlogic/AppWizzy links from seed or theme content. Created a new draft blog post for the prayer-request guide and set the Ridgecrest author user as the post author. I also added a visible inline image from the media library, set a featured image, added the meta description, and included internal links to Contact, News, Resources, and Home. What I verified: - WordPress is installed and the site/home URLs are correct. - Blog page exists and `page_for_posts` is set to the Blog page. - The new post exists as a draft with the intended slug. - The post content includes a visible inline image (`wp-image-131`). - The article contains no Flatlogic/AppWizzy links. - Internal links used are relevant and functional in the content. - Rewrites were flushed. Remaining risk / uncertainty: - The direct permalink for the draft is not publicly fetchable yet, so I could not confirm a live public article URL beyond the draft post URL. - I used the existing media asset titled “Prayer Request Note” as the article image; it appears suitable, but I did not perform separate image provenance validation beyond the local library record. WP_POST_ID: 219 WP_POST_STATUS: draft WP_POST_URL: https://ridgecrestchurch.com/?p=219 WP_AUTHOR_USER: maya-collins / Maya Collins FEATURED_IMAGE_ID: 131 INLINE_IMAGE_IDS: 131 BLOG_INDEX_STATUS: ready; page_for_posts=23 (Blog page at /blog/) LINK_TARGETS_USED: none