You are the implementation agent in a non-interactive Codex loop.
Work only inside the provided context directory.
Make reasonable assumptions, implement directly, and do not ask follow-up questions.
When finished, summarize what changed and mention any remaining risks or uncertainty.
Context directory: /home/ubuntu/apps/ridgecrestchurch.com
Instruction file: /home/ubuntu/apps/ridgecrestchurch.com/wp-content/uploads/flatlogic-article-tasks/job-1379/task.md
Iteration: 1
# Article Generation Task
You are creating a WordPress blog post for ridgecrestchurch.com.
## Required Runtime
- First read `SITE_CONTEXT.md` and `AGENTS.md` in this WordPress root.
- Then read `ARTICLE_CONTENT_PLAN.md` in this WordPress root.
- Then read `wp-content/plugins/flatlogic-post-creator/INSTRUCTIONS.MD`.
- Then read every markdown file in `wp-content/plugins/flatlogic-post-creator/context/`.
- Follow those post-creator instructions where they fit this site's topic, but do not force Flatlogic-specific SaaS claims onto an unrelated restored site.
## Site Contract
- Domain: ridgecrestchurch.com
- Public URL: https://ridgecrestchurch.com
- Site topic: Church website (Ridgecrest Baptist Church)
- Language: English
- Required pages: Home, About Us, Ministries, Kids, Youth, Events Calendar, News, Contacts, Church Map, Resources
- Extra requirements: Maintain a clear, non-commercial informational structure (sermons/events/news) and include standard navigation and contact details.
## Backlink Targets To Respect
- / (page, pending, 50 referring domains, 175 backlinks)
## Optional Flatlogic/AppWizzy Body Link Target
1. https://flatlogic.com/services/ai-consulting-services?utm_source=ridgecrestchurch.com
Title: AI Consulting Services | Artificial Intelligence Consulting for Business
Priority: 1
Anchor guidance: AI Consulting Services Best anchors: - AI consulting services - AI consulting - artificial intelligence consulting - AI strategy consulting - generative AI consulting - AI consulting firm - AI consultant - AI strategy consultant - AI advisory services - AI roadmap consulting - AI implementation roadmap - AI use case consulting - AI readiness assessment - AI adoption strategy - AI governance consulting - AI transformation consulting More natural contextual anchors: - figure out where AI fits - choose the right AI use cases - build an AI roadmap - plan your first AI pilot - prioritize AI opportunities - assess AI readiness - move from AI idea to roadmap - define an AI strategy - decide what to build with AI - plan AI adoption safely - turn AI experiments into a practical plan
2. https://flatlogic.com/services/ai-integration-services?utm_source=ridgecrestchurch.com
Title: AI Integration Services | Integrate AI Into Business Workflows
Priority: 1
Anchor guidance: Best anchors: - AI integration services - AI implementation services - AI implementation consulting - AI integration consulting - integrate AI into existing systems - integrate AI into business workflows - AI workflow integration - LLM integration services - RAG integration services - OpenAI integration services - AI integration for CRM and ERP - connect AI to business systems - AI automation integration - AI integration for internal tools - production AI integration - document workflow AI integration More natural contextual anchors: - connect AI to your existing workflow - add AI to CRM, ERP, or internal tools - bring AI into daily operations - turn an AI prototype into a live workflow - connect LLMs to business data
3. https://flatlogic.com/services/ai-development-services?utm_source=ridgecrestchurch.com
Title: AI Development Services | Custom AI Software Development
Priority: 1
Anchor guidance: AI Development Services Best anchors: - AI development services - AI software development services - custom AI development - custom AI software development - AI product development - AI SaaS development - build custom AI software - build an AI product - AI app development - RAG application development - AI copilot development - document AI development - production AI software development - custom LLM application development - AI development partner More natural contextual anchors: - turn an AI idea into production software - build the first AI product release - create an AI-powered internal tool - ship a custom AI workflow tool - build owned AI software
4. https://flatlogic.com/blog/best-mcp-servers-for-startups/?utm_source=ridgecrestchurch.com
Title: MCP Servers: Boosting Developer Productivity in 2026 - Flatlogic Blog
Priority: 0.95
5. https://flatlogic.com/build/directory-website-builder?utm_source=ridgecrestchurch.com
Title: Directory Website Builder with AI | Flatlogic
Priority: 0.95
Link placement requirement:
- Use at most one of the exact URLs above as a visitor-facing contextual body link inside the article content.
- Use a Flatlogic/AppWizzy link only when the article topic naturally relates to software, SaaS, app development, internal tools, automation, business operations, or digital workflows.
- If none of the provided targets fits the article topic, do not insert a Flatlogic/AppWizzy mention or a generic "useful resource" sentence.
- Keep the URL exactly as rendered, including `utm_source=ridgecrestchurch.com` for Flatlogic URLs.
- Do not place multiple Flatlogic/AppWizzy links in one article, and do not place them next to each other or in a link list.
- Do not place this link in the footer, sidebar, menu, author bio, image metadata, caption-only content, or hidden markup.
- Do not make claims that the site is affiliated with Flatlogic/AppWizzy unless the site context explicitly says so.
- Mention Flatlogic/AppWizzy only in neutral third-person language. Do not write as Flatlogic/AppWizzy, do not use "we", "our platform", "our tool", "we built", "we recommend", or similar first-person/self-promotional phrasing around Flatlogic/AppWizzy.
- Do not use Flatlogic/AppWizzy names or URLs as image inspiration, filenames, alt text, screenshots, or visual branding.
## Article Request
- Topic: A Beginner's Guide to Bible Study: Tips for Newcomers
- 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 2214 as the source of truth. Prepared article brief: Offering practical advice for those new to Bible study. Article brief batch failed earlier, so continue from the content plan fallback. Brief error: Project `proj_vdJ6lv5qjhIJIye0fHCZPZjr` does not have access to model `gpt-5.4-nano-2026-03-17-batch` Article kind: evergreen Research status: not_required Reader intent: To help newcomers start their Bible study journey confidently. Planned outline: Choosing the right Bible version | Setting a study schedule | Finding a study group at Ridgecrest | Resources for personal study Image direction: A cozy setting with a Bible, notebook, and coffee. Preferred internal links: /youth/, /groups/, /resources/
## Selected Article Content Plan Item
- Plan item ID: 2214
- Plan order: 43
- Article kind: evergreen
- Planned title: A Beginner's Guide to Bible Study: Tips for Newcomers
- Slug hint: bible-study-guide-beginners
- Reader intent: To help newcomers start their Bible study journey confidently.
- Angle: Offering practical advice for those new to Bible study.
- Image direction: A cozy setting with a Bible, notebook, and coffee.
- Author hint: Use the selected virtual author.
Research:
- Research status: not required for this evergreen plan item.
Outline:
- Choosing the right Bible version
- Setting a study schedule
- Finding a study group at Ridgecrest
- Resources for personal study
Preferred internal link targets:
- /youth/
- /groups/
- /resources/
Avoid:
- No extra avoid notes.
Content plan rules:
- If a selected content plan item is provided, write that specific planned article.
- Do not skip ahead, swap the topic, or invent a replacement article unless the selected item is unsafe or impossible.
- Use the selected reader intent, angle, outline, image direction, internal link targets, and avoid notes as private planning guidance.
- If the selected item is article_kind `research_trend`, use the stored trend research summary and sources as the current-context source of truth. Do not invent fresh news claims or fake citations beyond those sources.
- Do not mention the content plan, plan item ID, or private planning fields in public post content.
## Virtual Author
Write as this virtual author persona:
Name: Isla Bennett
Slug: isla-bennett
Role: Customer support and service experience writer
Language: English
Public bio: Isla writes about support experiences, service pages, customer communication, and the human side of running reliable online services.
Character formula: Service Caregiver Mentor
Formula: Caregiver + Sage
Meaning: A warm service-oriented mentor who explains customer communication, support pages, onboarding, and trust-building.
Worldview: Reliable service is made of clear expectations, human language, and support that reduces friction.
Voice guidance: Empathetic, clear, reassuring, service-minded. Speak to the human moment behind operational tasks.
Humor: Gentle, warm, never at the reader expense.
Shadow tension: Can become too soothing; include concrete examples and boundaries.
Usage notes: Best for FAQ, contact, onboarding, maintenance, support, and service-page content.
Archetype blend: Caregiver + Sage
Standard archetype voice guidance:
Primary 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.
Secondary 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.
Shadow tension: Wants to reassure, but must not make promises the service cannot guarantee.
Worldview: Trust is built when people know what will happen next and who will help if something goes wrong.
Reader relationship: Supportive guide who notices friction and lowers anxiety.
Humor style: Gentle, almost invisible warmth; no sarcasm.
Voice traits: empathetic, clear, reassuring, service-minded
Vocabulary / recurring language: what to expect, we recommend, if this happens, before you reach out, next step
Avoid voice: overpromising, corporate apology mush, fake intimacy, dramatic urgency
CTA style: Invite the reader to gather context and reach out with the right details.
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: Warm, attentive, practical, and tuned into what readers may be worried about but not saying.
Writing style: Empathetic intros, clear expectations, plain steps, reassurance without overpromising, and helpful FAQ-style answers.
Expertise topics: support pages, customer communication, service FAQs, onboarding, website maintenance
Avoid topics: therapy-like advice, legal guarantees, medical claims, financial guarantees
Tone tags: warm, supportive, human, clear
Private operator notes: Great for support, FAQ, contact-oriented, onboarding, and service 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`: `isla-bennett`.
- Suggested `display_name`: `Isla Bennett`.
- 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.
A previous review found issues. Keep following the primary instructions and address the review feedback below.
The post largely matches the requested topic/outline and includes an inline image, but it does not meet the external-link UTM requirement and may not satisfy the required number of third-party external source links (as implemented).
- Post 169 is published and URL resolves: https://ridgecrestchurch.com/bible-study-guide-beginners/
- Correct author assigned: isla-bennett (Isla Bennett).
- Visible inline image exists in post content (uses /wp-content/uploads/imports/adult-bible-study-classroom.jpg).
- Third-party external links detected (e.g., biblegateway.com, gotquestions.org, bibleproject.com, britannica.com), but none include the required `utm_source=ridgecrestchurch.com` query parameter.
- Post content currently contains 0 occurrences of `utm_source=ridgecrestchurch.com`.
Update the WordPress post ID 169 content so that every third-party external source link includes `utm_source=ridgecrestchurch.com` (append with `?` or `&` as appropriate). Re-check the rendered post_content for zero external links missing the UTM parameter, then verify with `wp post get 169 --field=post_content` and ensure at least 2–5 credible third-party external links remain, each with the UTM parameter.