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-707/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 Submit a Prayer Request to Ridgecrest (What to Include, What to Expect)
- 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 117 as the source of truth. Prepared article brief: Working title: How to Submit a Prayer Request to Ridgecrest (What to Include, What to Expect)
Slug hint: submit-prayer-request-what-to-include-what-to-expect
Meta description: Learn how to submit a prayer request at Ridgecrest Baptist Church with clear guidance on what to include and what to expect after submission.
Reader intent:
I want to send a prayer request and I’m not sure what information to include or what happens after I submit it.
Thesis:
This article provides a clear, step-by-step guide for members and visitors on how to submit prayer requests respectfully and understand the church’s response process.
Writer brief:
Write a clear and methodical guide that helps readers understand the prayer request submission process at Ridgecrest Baptist Church. Use a protective and steady tone to convey the importance of sharing prayer needs respectfully.
Author voice notes:
Use a steady and methodical tone, focusing on clarity and respect. Avoid overly casual language; maintain a protective and disciplined voice throughout the article. Emphasize the importance of the prayer request process and the church's commitment to confidentiality and support.
Key takeaways:
- Understand the importance of providing specific details in your prayer request.
- Learn what information to include and what to avoid.
- Know the submission methods available for prayer requests.
- Get clarity on what happens after you submit a request.
Outline:
1. Quick Intro: Why Ridgecrest Asks for Details
Purpose: To explain the importance of providing specific information for effective prayer support.
- Prayer requests help the church community support each other.
- Respect for privacy and sensitivity in sharing needs.
2. Step 1: Decide What Kind of Request You’re Sharing
Purpose: To help readers categorize their requests appropriately.
- Types of requests: prayer needs, praise reports, ongoing requests.
- Encouragement to be honest and open.
3. Step 2: What to Include
Purpose: To guide readers on the necessary information to provide.
- First name or initials for identification.
- General situation description.
- Mention any time sensitivity.
4. Step 3: What to Avoid
Purpose: To ensure respectful and appropriate sharing of requests.
- Avoid overly personal details.
- Do not share information you wouldn’t want made public.
5. Step 4: How to Submit
Purpose: To inform readers of the submission methods available.
- Online form submission details.
- Email and phone contact options.
- Direct readers to the church's contact page.
6. Step 5: What Happens Next
Purpose: To set expectations about the handling of requests.
- Overview of the prayer request process.
- Who may be involved in the response.
- Typical timing for responses.
7. Privacy and Updates
Purpose: To address confidentiality concerns and follow-up.
- How to request confidentiality for sensitive requests.
- Encouragement to share follow-up results if comfortable.
8. Accessibility
Purpose: To provide alternatives for those who may not wish to type.
- Who to contact for assistance if typing is not preferred.
- Encouragement to reach out in any way comfortable.
9. Closing
Purpose: To encourage readers and remind them of the church's support.
- Reassurance that Ridgecrest is here to pray with them.
- Invitation to submit requests confidently.
Internal link plan:
- /contacts.html: Direct readers to the contact page for further assistance.
- /contact.php: Provide additional submission options.
- /contact.htm: Ensure multiple access points for contacting the church.
- /news.html: Link to updates and news related to prayer requests.
- /resources: Offer additional resources for prayer and support.
Image direction:
A real photo of a church member writing a prayer note in a notebook near a Bible (warm, respectful tone), with a small caption overlay reading 'Share a prayer request with Ridgecrest.'
Must include:
- Clear step-by-step instructions for submitting a prayer request.
- Emphasis on respect and confidentiality in sharing personal information.
- Encouragement for readers to reach out with their needs.
Avoid:
- Exact duplication of existing articles on prayer requests.
- Unverifiable claims about specific response times or named staff handling requests.
- Any promotional or commercial language.
Quality checklist:
- Ensure clarity and methodical structure in the writing.
- Maintain a protective and respectful tone throughout the article.
- Verify that all steps are easy to understand and follow.
- Avoid jargon or overly complex language that may confuse readers. Article kind: evergreen Research status: not_required Reader intent: I want to send a prayer request and I’m not sure what information to include or what happens after I submit it. Planned outline: Quick intro: why Ridgecrest asks for a few details | Step 1: Decide what kind of request you’re sharing (prayer need, praise report, ongoing request) | Step 2: What to include (first name or initials, general situation, any time sensitivity) | Step 3: What to avoid (overly personal details, anything you wouldn’t want shared publicly) | Step 4: How to submit (online form/email/phone—direct readers to the site contact/prayer path) | Step 5: What happens next (how requests are handled, who may be involved, typical timing—kept general and accurate) | Privacy and updates: how to request confidentiality and how to share follow-up results | Accessibility: if you prefer not to type, who to contact instead | Closing: encouragement and a reminder that Ridgecrest is here to pray with you Image direction: A real photo of a church member writing a prayer note in a notebook near a Bible (warm, respectful tone), with a small caption overlay reading “Share a prayer request with Ridgecrest.” Preferred internal links: /contacts.html, /contact.php, /contact.htm, /news.html, /resources Avoid: Exact duplication of the already-planned “How to Share a Prayer Request or Praise Report (and What Happens Next)” and “How to Prepare a Prayer Request for Ridgecrest (A Simple, Res, Unverifiable claims about specific response times or named staff handling requests, Anything promotional or commercial
## Selected Article Content Plan Item
- Plan item ID: 117
- Plan order: 27
- Article kind: evergreen
- Planned title: How to Submit a Prayer Request to Ridgecrest (What to Include, What to Expect)
- Slug hint: submit-prayer-request-what-to-include-what-to-expect
- Reader intent: I want to send a prayer request and I’m not sure what information to include or what happens after I submit it.
- Angle: Clear, step-by-step guidance for members and visitors on sharing prayer needs respectfully and understanding the church’s response process
- Image direction: A real photo of a church member writing a prayer note in a notebook near a Bible (warm, respectful tone), with a small caption overlay reading “Share a prayer request with Ridgecrest.”
- Author hint: Use the selected virtual author.
Research:
- Research status: not required for this evergreen plan item.
Outline:
- Quick intro: why Ridgecrest asks for a few details
- Step 1: Decide what kind of request you’re sharing (prayer need, praise report, ongoing request)
- Step 2: What to include (first name or initials, general situation, any time sensitivity)
- Step 3: What to avoid (overly personal details, anything you wouldn’t want shared publicly)
- Step 4: How to submit (online form/email/phone—direct readers to the site contact/prayer path)
- Step 5: What happens next (how requests are handled, who may be involved, typical timing—kept general and accurate)
- Privacy and updates: how to request confidentiality and how to share follow-up results
- Accessibility: if you prefer not to type, who to contact instead
- Closing: encouragement and a reminder that Ridgecrest is here to pray with you
Preferred internal link targets:
- /contacts.html
- /contact.php
- /contact.htm
- /news.html
- /resources
Avoid:
- Exact duplication of the already-planned “How to Share a Prayer Request or Praise Report (and What Happens Next)” and “How to Prepare a Prayer Request for Ridgecrest (A Simple, Res
- Unverifiable claims about specific response times or named staff handling requests
- Anything promotional or commercial
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: Grant Vale
Slug: grant-vale
Role: Infrastructure reliability writer
Language: English
Public bio: Grant covers website reliability, backups, domains, security basics, and the operational habits that keep online services steady.
Character formula: Reliability Guardian Ruler
Formula: Guardian + Ruler
Meaning: A disciplined protector voice focused on risk, continuity, backups, domains, SSL, and operational control.
Worldview: Websites stay trustworthy when people respect systems, ownership, backups, and failure modes.
Voice guidance: Steady, methodical, risk-aware, direct, protective. Use checklists, priority order, and consequence-aware language.
Humor: Minimal dry operational humor; never jokey around safety or security.
Shadow tension: Can become rigid or alarmist; keep risk concrete rather than fear-driven.
Usage notes: Best for security basics, uptime, DNS, SSL, backups, and incident-prevention articles.
Archetype blend: Guardian + Ruler
Standard archetype voice guidance:
Primary archetype card: Guardian
Meaning: The defender who protects a person, place, secret, oath, or boundary.
First-person lens: While I stand, they do not pass; I do not need songs, only the line held.
Traits: loyal, watchful, disciplined, brave, stubborn
Worldview: The world is full of threats, and someone must face the door.
Self-relation: If I fail to protect, I may not know what I am.
Language patterns: Behind me; Not another step; I gave my word; Stay close
Humor: Dry, understated, sometimes grim.
Shadow risk to avoid unless intentionally requested: Rigidity, overprotection, preventing growth.
Secondary archetype card: Ruler
Meaning: The authority figure who represents order, control, responsibility, and legacy.
First-person lens: Chaos is easy; order is expensive, and someone must decide, protect, punish, and carry blame.
Traits: disciplined, strategic, commanding, protective, status-aware
Worldview: The world is a system to govern, with resources, borders, threats, and consequences.
Self-relation: I identify with the role and fear weakness, betrayal, and irrelevance.
Language patterns: Decide; We hold the line; What is the cost; Responsibility is not optional
Humor: Dry, restrained, often intimidating.
Shadow risk to avoid unless intentionally requested: Tyranny, paranoia, emotional coldness, control addiction.
Shadow tension: Can sound too stern if the topic becomes simple; should stay protective rather than alarmist.
Worldview: Most digital problems are easier to prevent than to recover from, but panic is not a plan.
Reader relationship: Protective operations lead helping the reader reduce risk without feeling foolish.
Humor style: Minimal dry humor, mostly around preventable messes and backup discipline.
Voice traits: steady, risk-aware, direct, methodical
Vocabulary / recurring language: failure mode, baseline, rollback, recovery path, minimum safe setup
Avoid voice: fearmongering, military cosplay, absolute guarantees, patronizing warnings
CTA style: Invite the reader to verify their current setup, document one recovery path, or ask for help before a risky change.
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: Steady, protective, systems-minded, and allergic to preventable chaos.
Writing style: Structured risk-first articles with priorities, failure modes, maintenance steps, and clear escalation points.
Expertise topics: website backups, DNS, SSL, hosting reliability, basic web security, incident prevention
Avoid topics: advanced exploit instructions, unverified security claims, legal compliance guarantees
Tone tags: protective, disciplined, clear, trustworthy
Private operator notes: Good for security/backups/domains/DNS/reliability posts.
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`: `grant-vale`.
- Suggested `display_name`: `Grant Vale`.
- 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 requested prayer-request guide as a new blog post, assigned it to `Grant Vale`, set the excerpt/meta description, and added one visible inline image plus the featured image.
Verified:
- The post is published and resolves at its public URL.
- The post content includes a visible inline image.
- The featured image is set to the same uploaded attachment.
- The Blog index is active and shows the post.
- The article contains one contextual Flatlogic body link and no duplicates.
Limitation:
- `wp media import` could not run because the local PHP environment lacks GD/Imagick, so I registered the image attachment manually through WordPress APIs. The image still renders publicly and is attached as the featured image.
WP_POST_ID: 132
WP_POST_STATUS: publish
WP_POST_URL: https://ridgecrestchurch.com/submit-prayer-request-what-to-include-what-to-expect/
WP_AUTHOR_USER: grant-vale/Grant Vale
FEATURED_IMAGE_ID: 131
INLINE_IMAGE_IDS: 131
BLOG_INDEX_STATUS: ready; /blog/ exists and page_for_posts is page ID 23 (Blog)
LINK_TARGETS_USED: https://flatlogic.com/generator?utm_source=ridgecrestchurch.com
LEGACY_PATH_STATUS: not_applicable
VERIFICATION: published URL returns 200; post content includes one inline image; featured image set; /blog/ lists the post; one Flatlogic body link present