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-660/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) ## Flatlogic/AppWizzy Body Link Placement Goal 1. https://flatlogic.com/blog/future-of-ai-developers/?utm_source=ridgecrestchurch.com Title: AI vs Developers: Why the Future Is AI-Assisted Software Engineering - Flatlogic Blog Priority: 1000000 2. https://flatlogic.com/blog/custom-saas-product-around-your-business-model/?utm_source=ridgecrestchurch.com Title: SaaS Solutions for Competitive Business Advantage - Flatlogic Blog Priority: 1000000 3. https://flatlogic.com/build/work-order-management-software-builder?utm_source=ridgecrestchurch.com Title: Work Order Management Software Builder | Flatlogic Priority: 1000000 4. https://flatlogic.com/build/legal-case-management-software-builder?utm_source=ridgecrestchurch.com Title: Legal Case Management Software Builder | Flatlogic 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: - Make a strong editorial effort to insert one of the exact URLs above as a visitor-facing contextual body link inside the article content. - Treat this as an important placement goal when link targets are available, but do not make the article awkward or spammy just to force it. - The article topic does not need to be directly about software. Build a natural contextual bridge through practical operations, website upkeep, publishing, customer communication, booking, admin work, reporting, workflow, data tracking, or business process where that fits the article. - Choose the target whose title and anchor guidance can be made least disruptive to the reader. - Use one neutral third-person sentence or clause. The link should feel like a useful contextual resource, not an ad or a link list. - 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: How to Share a Testimony at Ridgecrest: Simple Prompts and a Respectful Format - 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 116 as the source of truth. Prepared article brief: Working title: How to Share a Testimony at Ridgecrest: Simple Prompts and a Respectful Format Slug hint: share-a-testimony-ridgecrest-prompts-format Meta description: Learn how to share a meaningful testimony at Ridgecrest Baptist Church with simple prompts and a respectful format. This guide offers practical tips for members and visitors. Reader intent: Help someone prepare a testimony they can confidently share at Ridgecrest without feeling pressured or unsure what to say. Thesis: Sharing a testimony is a valuable way to connect with the Ridgecrest community, and this guide provides practical steps to do so respectfully and effectively. Writer brief: Create a practical, non-technical guide for church members and visitors on how to share a testimony. Focus on clarity and warmth, ensuring the content is approachable and supportive. Author voice notes: Maintain a plain-spoken, warm, and precise tone. Use practical examples and avoid overly technical language. Keep the advice beginner-friendly and reassuring, ensuring readers feel supported throughout the process. Key takeaways: - Understanding the importance of testimonies in a church setting. - Learning the structure of a good testimony: Before, What changed, What God is doing now. - Guidelines for length and when to choose between a brief or longer testimony. - Safe prompts to help get started with sharing. - Respectful sharing practices, avoiding sensitive topics. - A simple template to help structure testimonies. - Submission process details and what to expect afterward. - Tips for delivering testimonies confidently. Outline: 1. Why testimonies matter Purpose: To explain the significance of sharing personal experiences in a church context. - Fosters community connection - Encourages others in their faith - Demonstrates God's work in individual lives 2. A good testimony in 3 parts Purpose: To outline the structure of an effective testimony. - Before: Brief background - What changed: Key moments of transformation - What God is doing now: Current reflections 3. Length guidelines Purpose: To provide advice on how long testimonies should be based on context. - 2-3 minute version for brief sharing - Longer format for deeper stories - When to choose each option 4. Safe prompts to get started Purpose: To offer ideas that help individuals begin crafting their testimonies. - Faithfulness - Answered prayer - Learning through challenges - Turning points 5. Keep it respectful Purpose: To emphasize the importance of respectful sharing. - Avoid debate and personal attacks - Steer clear of sensitive details - Focus on personal experiences 6. A simple template you can fill in Purpose: To provide a practical tool for writing testimonies. - Example sentence starters - Structure for easy completion 7. How to submit Purpose: To guide readers on how to submit their testimonies. - Where to send submissions - Information needed for submission - Tie to existing processes 8. What to expect after you submit Purpose: To prepare readers for the review process. - Overview of review steps - How and when they will be contacted 9. Tips for delivering Purpose: To provide practical advice for sharing testimonies in person. - Speaking pace - Building confidence - Managing nerves Internal link plan: - /contact/: To provide a direct link for submitting testimonies. - /resources: To offer additional materials that may help in preparing testimonies. - /about/: To give context about the church and its mission. - /news.html: To connect readers with recent church updates. - /: To encourage further exploration of the church website. Image direction: A candid church photo of a person speaking at a small group or sharing time, or a clean photo of a notebook/pen with a Bible on a table to illustrate preparing a testimony. Must include: - Clear structure for testimonies - Respectful sharing guidelines - Submission process details Avoid: - No step-by-step instructions for editing site code or managing WordPress - No promises about specific outcomes - No duplication of existing plan items about prayer requests or communion - No unrelated external links or commercial references Quality checklist: - Ensure clarity and warmth in the writing style - Use practical examples and templates - Avoid jargon or overly technical language - Maintain a supportive tone throughout the article Article kind: evergreen Research status: not_required Reader intent: Help someone prepare a testimony they can confidently share at Ridgecrest without feeling pressured or unsure what to say. Planned outline: Why testimonies matter (in everyday, Baptist-friendly language) | A good testimony in 3 parts: Before • What changed • What God is doing now | Length guidelines: quick 2–3 minute version vs. longer sharing (and when to choose which) | Safe prompts to get started (faithfulness, answered prayer, learning through a challenge, a turning point) | Keep it respectful: avoiding debate, personal attacks, or sharing sensitive details | A simple template you can fill in (with example sentence starters) | How to submit: where to send it (tie to existing prayer request/news processes) and what information to include | What to expect after you submit (review/approval steps at a high level, and how you’ll be contacted) | Tips for delivering: speaking pace, confidence, and what to do if you get nervous Image direction: A candid church photo of a person speaking at a small group or sharing time (or a clean photo of a notebook/pen with a Bible on a table) to illustrate preparing a testimony. Preferred internal links: /contact/, /contacts.html, /news.html, /resources, /about/, / Avoid: No step-by-step instructions for editing site code or managing WordPress, No promises about specific outcomes (e.g., “you will be chosen to speak”), No duplication of existing plan items about prayer requests, communion, or first-time visit logistics, No unrelated external links or commercial references ## Selected Article Content Plan Item - Plan item ID: 116 - Plan order: 26 - Article kind: evergreen - Planned title: How to Share a Testimony at Ridgecrest: Simple Prompts and a Respectful Format - Slug hint: share-a-testimony-ridgecrest-prompts-format - Reader intent: Help someone prepare a testimony they can confidently share at Ridgecrest without feeling pressured or unsure what to say. - Angle: Provide a practical, non-technical guide for members and visitors on how to share a brief testimony in a church-appropriate way (what to include, length, tone, and how to submit). - Image direction: A candid church photo of a person speaking at a small group or sharing time (or a clean photo of a notebook/pen with a Bible on a table) to illustrate preparing a testimony. - Author hint: Use the selected virtual author. Research: - Research status: not required for this evergreen plan item. Outline: - Why testimonies matter (in everyday, Baptist-friendly language) - A good testimony in 3 parts: Before • What changed • What God is doing now - Length guidelines: quick 2–3 minute version vs. longer sharing (and when to choose which) - Safe prompts to get started (faithfulness, answered prayer, learning through a challenge, a turning point) - Keep it respectful: avoiding debate, personal attacks, or sharing sensitive details - A simple template you can fill in (with example sentence starters) - How to submit: where to send it (tie to existing prayer request/news processes) and what information to include - What to expect after you submit (review/approval steps at a high level, and how you’ll be contacted) - Tips for delivering: speaking pace, confidence, and what to do if you get nervous Preferred internal link targets: - /contact/ - /contacts.html - /news.html - /resources - /about/ - / Avoid: - No step-by-step instructions for editing site code or managing WordPress - No promises about specific outcomes (e.g., “you will be chosen to speak”) - No duplication of existing plan items about prayer requests, communion, or first-time visit logistics - No unrelated external links or commercial references 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. - 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 natural contextual body copy. `LINK_TARGETS_USED` may be `none` when no target URLs were configured or no natural placement survived review. ## 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 article at the requested slug with a full 3-part testimony structure, length guidance, respectful-sharing rules, a fill-in template, submission expectations, and delivery tips. I used the existing Sunday Service Planning Desk image as both the featured image and a visible inline figure, set the image alt text, kept the blog index intact, and placed the single Flatlogic body link in the submission section where it felt least disruptive. Remaining risk: the site does not expose a dedicated testimony submission form, so the “How to submit” section is intentionally conservative and points readers to the existing Contacts/News paths instead of claiming a custom workflow. WP_POST_ID: 130 WP_POST_STATUS: publish WP_POST_URL: https://ridgecrestchurch.com/share-a-testimony-ridgecrest-prompts-format/ WP_AUTHOR_USER: maya-collins / Maya Collins FEATURED_IMAGE_ID: 76 INLINE_IMAGE_IDS: 76 BLOG_INDEX_STATUS: ready; https://ridgecrestchurch.com/blog/ returns 200 and page_for_posts=23 (Blog) LINK_TARGETS_USED: https://flatlogic.com/generator?utm_source=ridgecrestchurch.com VERIFICATION: wp post get/wp post url confirmed; public URL returned 200; inline image, featured image, BibleGateway references, and the single Flatlogic link were confirmed in post content; /blog/ returned 200.