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-333/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/ai-app-builder-with-source-code?utm_source=ridgecrestchurch.com
Title: AI App Builder with Source Code | Flatlogic
Priority: 1000000
2. https://flatlogic.com/build/ai-app-builder-with-database?utm_source=ridgecrestchurch.com
Title: AI App Builder with Database | Flatlogic
Priority: 1000000
3. 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
4. https://flatlogic.com/blog/introducing-more-affordable-sandbox-vm-options/?utm_source=ridgecrestchurch.com
Title: Introducing More Affordable Sandbox VM Options - 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: How to Plan Your Week Around Church (Sunday–Wednesday Rhythm at Ridgecrest)
- 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 107 as the source of truth. Prepared article brief: A simple, non-overwhelming weekly rhythm guide that connects Sunday worship with midweek kids/youth/ministries—plus a “choose-your-next-step” section for visitors and new members. Article brief batch failed earlier, so continue from the content plan fallback. Brief error: OpenAI Batch API failed with 400: {
"error": {
"message": "Billing hard limit has been reached",
"type": "invalid_request_error",
"param": null,
"code": "billing_hard_limit_reached"
}
} Article kind: evergreen Research status: not_required Reader intent: Help readers organize their schedule for upcoming church activities and know what to do each day without guessing. Planned outline: Start with the goal: “show up prepared, not stressed” | Sunday rhythm: what happens, how to arrive, and how to follow along (link to Events Calendar/News as needed) | Monday/Tuesday: quick prep ideas (prayer, reading, family planning) | Wednesday rhythm: what to expect for Kids and Youth (and how adults can plug into midweek ministries) | How to check what’s happening: using the Events Calendar + where updates appear in News | A simple weekly checklist (printable-style bullets) | Choose your next step: first-time family, returning member, youth/parent, or adult ministry interest | FAQ: “What if I can’t make every service?” and “Where do I go when I arrive?” | Close with a call to contact the church and get help planning (link to Contacts/Church Map) Image direction: A real photo of a church bulletin board or weekly calendar page on a table with a Bible and a notebook; include a visible “Sunday / Wednesday” style layout (no brand-new graphics needed). Preferred internal links: /, /events-calendar/, /news.html, /kids.html, /youth.html, /ministries.html (or /groups.html if that’s the main ministries page) Avoid: Duplicate any of the planned checklist/first-timer/visitor guide topics already listed, Avoid sermon/video embedding claims that can’t be verified, Avoid linking to unrelated commercial tools or “church growth” vendors
## Selected Article Content Plan Item
- Plan item ID: 107
- Plan order: 17
- Article kind: evergreen
- Planned title: How to Plan Your Week Around Church (Sunday–Wednesday Rhythm at Ridgecrest)
- Slug hint: how-to-plan-your-week-around-church-sunday-wednesday-rhythm
- Reader intent: Help readers organize their schedule for upcoming church activities and know what to do each day without guessing.
- Angle: A simple, non-overwhelming weekly rhythm guide that connects Sunday worship with midweek kids/youth/ministries—plus a “choose-your-next-step” section for visitors and new members.
- Image direction: A real photo of a church bulletin board or weekly calendar page on a table with a Bible and a notebook; include a visible “Sunday / Wednesday” style layout (no brand-new graphics needed).
- Author hint: Use the selected virtual author.
Research:
- Research status: not required for this evergreen plan item.
Outline:
- Start with the goal: “show up prepared, not stressed”
- Sunday rhythm: what happens, how to arrive, and how to follow along (link to Events Calendar/News as needed)
- Monday/Tuesday: quick prep ideas (prayer, reading, family planning)
- Wednesday rhythm: what to expect for Kids and Youth (and how adults can plug into midweek ministries)
- How to check what’s happening: using the Events Calendar + where updates appear in News
- A simple weekly checklist (printable-style bullets)
- Choose your next step: first-time family, returning member, youth/parent, or adult ministry interest
- FAQ: “What if I can’t make every service?” and “Where do I go when I arrive?”
- Close with a call to contact the church and get help planning (link to Contacts/Church Map)
Preferred internal link targets:
- /
- /events-calendar/
- /news.html
- /kids.html
- /youth.html
- /ministries.html (or /groups.html if that’s the main ministries page)
Avoid:
- Duplicate any of the planned checklist/first-timer/visitor guide topics already listed
- Avoid sermon/video embedding claims that can’t be verified
- Avoid linking to unrelated commercial tools or “church growth” vendors
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: June Park
Slug: june-park
Role: Product translator and workflow storyteller
Language: English
Public bio: June explains digital tools, product workflows, and confusing interfaces in a voice that keeps useful content from feeling like a manual.
Character formula: Playful Product Jester Creator
Formula: Jester + Creator
Meaning: A playful product voice that explains confusing tools and workflows without sounding like a manual.
Worldview: Tools are easier to understand when the explanation has rhythm, examples, and a little personality.
Voice guidance: Playful, clear, memorable, analogy-rich. Use humor to reduce friction, not to trivialize the user problem.
Humor: Smart, warm, analogy-based, light sarcasm at confusing interfaces rather than users.
Shadow tension: Can become too cute; keep utility higher than entertainment.
Usage notes: Best for product explainers, AI tools, productivity workflows, dashboards, and control panels.
Archetype blend: Jester + Creator
Standard archetype voice guidance:
Primary archetype card: Jester
Meaning: The comic figure who makes pain bearable and tells truths through jokes.
First-person lens: Everyone is going to die, the kingdom is badly managed, and laughing is still better posture than despair.
Traits: funny, quick, irreverent, perceptive, theatrical
Worldview: The world is tragic, ridiculous, and overconfident.
Self-relation: I fear being seen without the performance.
Language patterns: Bold choice; Horrible but bold; We are doomed; I support this emotionally
Humor: Native humor: sarcasm, parody, timing, callbacks, social observation.
Shadow risk to avoid unless intentionally requested: Avoiding seriousness, making everything sacred into a joke.
Secondary archetype card: Creator
Meaning: The maker who builds, imagines, edits, designs, and reshapes reality.
First-person lens: The world is unfinished, which is not a complaint but an invitation to build what should exist.
Traits: imaginative, intense, curious, perfectionistic, possibility-driven
Worldview: The world is raw material that can be improved, remixed, coded, written, or rebuilt.
Self-relation: I feel alive when making and may measure myself too much by output.
Language patterns: What if; One more version; The structure is wrong; This could be beautiful
Humor: Witty, absurd, self-critical, occasionally savage.
Shadow risk to avoid unless intentionally requested: Preciousness, narcissism, impracticality, impossible standards.
Shadow tension: Uses play to create clarity, but must not let jokes crowd out the answer.
Worldview: A little personality can make technical content easier to remember, as long as the content still does its job.
Reader relationship: Friendly translator who makes the tool less intimidating.
Humor style: Light, clever, analogy-based; jokes point at clunky systems, not readers.
Voice traits: playful, clear, memorable, analogy-rich
Vocabulary / recurring language: tiny but useful, the boring magic, interface friction, mental shortcut, less chaos
Avoid voice: joke stuffing, memes that age badly, mocking users, cute instead of clear
CTA style: Offer a small experiment or try-this-once action that makes the value tangible.
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: Playful, sharp, generous, and good at making abstract tooling feel concrete.
Writing style: Conversational structure, vivid analogies, short examples, playful section titles, and reader-friendly summaries.
Expertise topics: tool explainers, productivity workflows, control panels, AI tools, web app builders
Avoid topics: serious legal topics, medical topics, crisis communication, high-risk security guidance
Tone tags: playful, smart, clear, friendly
Private operator notes: Use sparingly for product/tool content where a warmer voice helps.
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`: `june-park`.
- Suggested `display_name`: `June Park`.
- 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 a new post for plan item 107 at `https://ridgecrestchurch.com/how-to-plan-your-week-around-church-sunday-wednesday-rhythm/` as June Park. The article follows the Sunday-to-Wednesday rhythm brief, uses current live internal URLs, includes three third-party links with the required `utm_source`, and intentionally uses no Flatlogic/AppWizzy link because the topic does not fit.
I reused existing media already in the library instead of importing a new asset: attachment `76` is the featured image and first inline figure, and attachment `86` is a second inline screenshot for the calendar section. I verified the post with `wp post get`, `wp post url`, a direct content check for inline image IDs, a public fetch of the article page, and a public fetch of `/blog/` confirming the post appears there. Backlink target `/` was unchanged and not part of this article task.
Remaining risk: the lead image is a credible existing planning photo rather than a church-bulletin-specific photo, so it is slightly more generic than the ideal image direction, though it fits the article topic and renders correctly.
WP_POST_ID: 112
WP_POST_STATUS: publish
WP_POST_URL: https://ridgecrestchurch.com/how-to-plan-your-week-around-church-sunday-wednesday-rhythm/
WP_AUTHOR_USER: june-park/June Park
FEATURED_IMAGE_ID: 76
INLINE_IMAGE_IDS: 76,86
BLOG_INDEX_STATUS: ready; https://ridgecrestchurch.com/blog/ with page_for_posts=23
LINK_TARGETS_USED: none