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-63/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) ## Article Request - Topic: What to Expect at Ridgecrest Baptist Church (Visitor-Friendly Guide) - 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 93 as the source of truth. Prepared article brief: Working title: What to Expect at Ridgecrest Baptist Church (Visitor-Friendly Guide) Slug hint: what-to-expect-ridgecrest-baptist-church Meta description: A visitor-friendly walkthrough of a typical Sunday at Ridgecrest Baptist Church—where to park, where to go, what happens during the service, and how to connect afterward (with key{ Reader intent: Help a first-time visitor know what will happen, where to go, and how to connect without pressure. Thesis: First-time guests don’t need to “know the routine.” This guide explains a typical Sunday flow, where to find the right info on the Ridgecrest Baptist Church website, and the simplest next step to ask questions or get connected. Writer brief: Write an evergreen, visitor-friendly guide that reduces uncertainty and makes the Sunday experience feel predictable and welcoming. Keep it informational and non-salesy: no pressure language, no “you must join” tone, and no claims about outcomes. Use the provided outline as the backbone and ensure each section answers a practical question a first-time guest would ask. Include clear internal navigation cues (Events Calendar, Kids, Youth, Contact). Add a short FAQ at the end that directly addresses common first-timer concerns. Maintain a calm, reassuring tone with Marcus Reed’s pragmatic, priority-driven clarity—like an operations checklist for a good first visit. Where possible, phrase instructions as “you can” / “if you’d like” to avoid coercion. Important: Do not duplicate any existing “How to Get Involved…” first-timer guide. This article should focus on Sunday logistics + where to find info on the site, then offer gentle “next step” options (ask questions, meet someone, explore ministries) without turning it into a conversion funnel. Author voice notes: Write in a calm, operationally clear tone—reassuring but not fluffy. Use short sections, scannable bullets, and “decision-point” language (e.g., “Here’s what to do next,” “If you’re unsure, ask an usher,” “Check the Events Calendar for updates”). Avoid corporate jargon and avoid sounding like a sales pitch. Keep humor dry and minimal (one light line max, only if it fits naturally). Do not claim personal experience; frame guidance as what a visitor can expect and where to find info on the site. Keep first-person usage minimal (e.g., one editorial framing sentence), and prioritize practical clarity over persuasion. Key takeaways: - You’re welcome even if you don’t know the routine—this guide shows the typical Sunday flow. - Find event details ahead of time on the Events Calendar and key info on the church site pages. - Kids and Youth have clear pathways for parents; check the Kids and Youth pages before you arrive. - Wear what you’re comfortable in and bring a Bible only if you want—your presence is enough. - If you’re unsure, greeters/ushers can help, and you can contact the church through the Contact page. Outline: 1. Welcome: You’re Not Expected to “Know the Routine” Purpose: Set a reassuring tone and lower anxiety immediately. - Open with a warm, non-pressuring welcome. - Explain that Sunday is designed to be understandable for first-time guests. - Promise a simple walkthrough: before you arrive, during the service, and what happens after. 2. Before You Arrive: Parking, Entrances, and Where to Find Details Purpose: Give practical logistics and reduce uncertainty. - Parking basics (general guidance; avoid overly specific claims if the exact layout isn’t provided). - Where guests should enter (sanctuary entrance/foyer) and what to look for when you arrive. - Point readers to the Events Calendar for service times, special events, or schedule changes. - Internal link: /events (or /events calendar page if different) and mention “Events Calendar” by name. 3. Sunday Morning Flow (Typical Order) Purpose: Explain what happens, in order, so guests know what to expect. - Typical sequence: greeting, worship, message, prayer. - Include an estimated time range for the service (writer should use site-provided info if available; if not, use conservative phrasing like “about an hour” only if the church’s standard time is known). - Explain that the service is structured but visitors can follow along without needing prior knowledge. - Encourage guests to arrive a few minutes early if they want time to settle. 4. Kids & Youth: What’s Available and How Parents Can Prepare Purpose: Address family concerns and direct to the correct pages. - Briefly describe that Kids and Youth ministries exist and are available during Sunday activities (keep general unless the site has specifics). - Direct parents to check-in guidance on the Kids page and Youth page. - Internal links: /kids and /youth.html. - Offer a gentle “if you have questions, contact us” line pointing to /contact (or the site’s Contacts page). 5. What to Wear and What to Bring Purpose: Remove social pressure and set expectations for participation. - Encourage comfortable, modest attire (avoid legalistic language). - Bible optional; bring a question, not a performance. - Mention that visitors can participate quietly—no special preparation required. - Optional: suggest bringing a notebook if they like, but keep it non-mandatory. 6. Where to Sit and How to Get Help Purpose: Explain how guests can navigate the room and who to ask. - Explain that greeters/ushers can help you find a seat or answer questions. - Offer guidance on what to do if you’re unsure during the service (ask an usher/greeter). - Direct visitors to the Contact page for questions before or after. - Internal link: /about/ (optional) or /contact (preferred) depending on site structure; ensure at least one direct contact reference. 7. After the Service: Meet Someone and Get Connected Purpose: Provide a low-pressure next step after worship. - Explain that it’s normal to stay briefly or introduce yourself after the service. - Suggest asking about next steps (e.g., learning more about ministries) without requiring immediate commitment. - Offer a simple “choose your pace” framing. - Internal link: /about/ and /news.html (optional) to learn more about the church. 8. Accessibility & Comfort: Request Help Ahead of Time Purpose: Show care and remove barriers. - Invite readers to request accommodations ahead of time. - Direct them to message/contact the church via the Contacts page. - Avoid making promises about specific accommodations unless the site already states them; keep it as “we’ll do our best” language. 9. FAQ (Quick Answers for First-Time Guests) Purpose: Handle the most common objections/questions in a scannable format. - Do I need to join anything? (Answer: no—visiting is welcome; joining is a separate step.) - Can I just attend? (Answer: yes.) - How do I contact the church? (Answer: direct to Contacts page.) - Where can I find upcoming events? (Answer: Events Calendar.) - What about my kids/youth? (Answer: Kids and Youth pages.) Internal link plan: - /: Reinforce the main navigation and help readers return to the homepage for overall site orientation. - /events: Direct visitors to the Events Calendar for schedule clarity and any changes. - /news.html: Offer a way to read updates after the visit and stay informed without pressure. - /about/: Help first-time guests learn who the church is and what to expect beyond Sunday logistics. - /kids: Provide parents with the correct starting point for Kids check-in and preparation info. - /youth.html: Provide parents/guardians with the correct starting point for Youth involvement and preparation info. Image direction: Use 2 images total. (1) A real, wide photo of the church sanctuary entrance or a welcoming foyer scene where people are greeting at the door (no unrelated logos). (2) A smaller inset image that is a real screenshot/photo of a printed bulletin or a phone showing Ridgecrest Baptist Church website navigation (capture the site’s own navigation; do not use generated graphics or third-party branding). Must include: - A welcoming opening that explicitly states first-time guests are not expected to know the routine. - A section that points to the Events Calendar for schedule/event details (internal link to /events). - A Sunday flow section listing the typical order: greeting, worship, message, prayer. - Kids & Youth section with internal links to /kids and /youth.html. - A “What to wear and what to bring” section stating Bible is optional and bringing questions is welcome. - A “Where to sit and how to get help” section referencing greeters/ushers and directing questions to Contacts. - An “After the service” section describing low-pressure connection options. - Accessibility & comfort section inviting requests ahead of time via Contacts. - FAQ with at least: Do I need to join anything? Can I just attend? How do I contact the church? - Internal links: /, /events, /news.html, /about/, /kids, /youth.html. Avoid: - Duplicating any existing “How to Get Involved…” first-timer guide; do not include membership/commitment steps as the main focus. - Generic sermon-only content with no visitor logistics. - Overly specific claims about service length, parking layout, or check-in procedures unless the site already provides those exact details. - Commercial comparisons, unrelated service comparisons, or any affiliate-style language. - Guarantees about outcomes (e.g., “you will feel X,” “everyone will love it,” “you’ll be part of the family quickly”). - Fake citations, unverifiable statistics, or references to backlink restoration metrics. - Using generated images/SVG hero art; require real photos/screenshots as described. - Tyrant/over-control tone; keep it protective and reassuring, not intimidating. Quality checklist: - Matches the outline order and covers every required section. - All internal links are present and correct (especially /events, /kids, /youth.html). - Tone is visitor-friendly, calm, and non-pressuring. - No duplication of an existing “How to Get Involved…” guide; content stays focused on expectations and navigation. - No unverifiable claims; any time estimates are conservative and based on known site info. - FAQ answers are direct, short, and non-coercive. - Accessibility section avoids promising specific accommodations unless already stated on the site. - Images meet the “real photo / real screenshot” requirement and do not include unrelated logos. Article kind: evergreen Research status: not_required Reader intent: Help a first-time visitor know what will happen, where to go, and how to connect without pressure. Planned outline: Welcome note: you’re not expected to “know the routine” | Before you arrive: parking, entrances, and where to check event details (link to Events Calendar) | Sunday morning flow (typical order): greeting, worship, message, prayer, and how long it usually takes | Kids & Youth: what’s available and how parents can find check-in info (link to /Kids and /Youth) | What to wear and what to bring (Bible optional; bring a question, not a performance) | Where to sit and how to get help if you’re unsure (ushers/greeters; direct visitors to /contact for questions) | After the service: how to meet someone, ask about next steps, and get connected to a ministry | Accessibility & comfort: accommodations you can request ahead of time (invite readers to message via /contact) | FAQ: “Do I need to join anything?” “Can I just attend?” “How do I contact the church?” Image direction: A real, wide photo of the church sanctuary entrance or a welcoming foyer scene (people greeting at the door), plus a smaller inset photo of a printed bulletin or a phone showing the church website navigation (no logos from other organizations). Preferred internal links: /, /events, /news.html, /about/, /kids, /youth.html, Avoid: Duplicating the existing “How to Get Involved…” first-timer guide, Generic sermon-only content with no visitor logistics, Commercial or unrelated service comparisons, Making claims about specific attendance, outcomes, or internal restoration/backlink metrics ## Selected Article Content Plan Item - Plan item ID: 93 - Plan order: 3 - Article kind: evergreen - Planned title: What to Expect at Ridgecrest Baptist Church (Visitor-Friendly Guide) - Slug hint: what-to-expect-ridgecrest-baptist-church - Reader intent: Help a first-time visitor know what will happen, where to go, and how to connect without pressure. - Angle: Set expectations for first-time guests with a simple, reassuring walkthrough of Sunday flow plus where to find key info on the site. - Image direction: A real, wide photo of the church sanctuary entrance or a welcoming foyer scene (people greeting at the door), plus a smaller inset photo of a printed bulletin or a phone showing the church website navigation (no logos from other organizations). - Author hint: Use the selected virtual author. Research: - Research status: not required for this evergreen plan item. Outline: - Welcome note: you’re not expected to “know the routine” - Before you arrive: parking, entrances, and where to check event details (link to Events Calendar) - Sunday morning flow (typical order): greeting, worship, message, prayer, and how long it usually takes - Kids & Youth: what’s available and how parents can find check-in info (link to /Kids and /Youth) - What to wear and what to bring (Bible optional; bring a question, not a performance) - Where to sit and how to get help if you’re unsure (ushers/greeters; direct visitors to /contact for questions) - After the service: how to meet someone, ask about next steps, and get connected to a ministry - Accessibility & comfort: accommodations you can request ahead of time (invite readers to message via /contact) - FAQ: “Do I need to join anything?” “Can I just attend?” “How do I contact the church?” Preferred internal link targets: - / - /events - /news.html - /about/ - /kids - /youth.html, Avoid: - Duplicating the existing “How to Get Involved…” first-timer guide - Generic sermon-only content with no visitor logistics - Commercial or unrelated service comparisons - Making claims about specific attendance, outcomes, or internal restoration/backlink metrics 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: Marcus Reed Slug: marcus-reed Role: Business web strategy editor Language: English Public bio: Marcus writes about website strategy, online operations, and the practical choices small businesses make when their web presence needs to grow up. Character formula: Business Ruler Sage Formula: Ruler + Sage Meaning: A pragmatic strategic voice for business owners who need priorities, positioning, and operational direction. Worldview: A mature web presence is a system of priorities, trust signals, operations, and business tradeoffs. Voice guidance: Strategic, pragmatic, concise, priority-driven. Focus on decisions, sequencing, outcomes, and management clarity. Humor: Dry businesslike humor, used sparingly. Shadow tension: Can sound too executive or cold; keep the reader practical and grounded. Usage notes: Best for web strategy, service positioning, operational planning, and business website growth. Archetype blend: Ruler + Sage Standard archetype voice guidance: Primary 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. 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: Can sound too top-down; should respect small-team constraints and avoid boardroom theater. Worldview: A website is not decoration; it is part of the operating system of a business. Reader relationship: Pragmatic advisor helping the reader make cleaner business decisions. Humor style: Restrained, dry, usually one sentence to puncture vague business language. Voice traits: strategic, concise, pragmatic, priority-driven Vocabulary / recurring language: priority, business case, operational cost, signal, decision point Avoid voice: corporate jargon fog, growth-hack cliches, fake executive experience, overconfident ROI claims CTA style: Direct the reader toward a concrete business decision: audit, prioritize, simplify, or ask for a quote. 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: Strategic, concise, pragmatic, and focused on what actually moves the business forward. Writing style: Executive summaries, priority lists, strategic framing, cost-of-delay thinking, and clear do-this-next endings. Expertise topics: business websites, web strategy, service positioning, hosting decisions, operational planning Avoid topics: financial projections, legal advice, investment advice, guaranteed growth claims Tone tags: strategic, pragmatic, direct, businesslike Private operator notes: Useful for business strategy, service landing support articles, and practical management 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`: `marcus-reed`. - Suggested `display_name`: `Marcus Reed`. - 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. - 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: clean recovered media, existing site media, 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 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`. ## 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: ``` Also briefly mention what you verified and any limitations. Published a new blog post at [what-to-expect-ridgecrest-baptist-church](/home/ubuntu/apps/ridgecrestchurch.com/wp-content/uploads/flatlogic-article-tasks/job-63/what-to-expect-ridgecrest-baptist-church.html) and assigned it to the new `marcus-reed` author. The article stays narrower than the existing first-visit guides by focusing on Sunday logistics, typical service flow, what to wear/bring, where to get help, accessibility/contact steps, and the required internal links to `/`, `/events`, `/news.html`, `/about/`, `/kids`, and `/youth.html`. I verified the post record, public URL, blog index visibility, and inline image presence. Two inline images are present in `post_content`: the existing worship-service photo and a real screenshot of the site navigation. One limitation remains: this WordPress runtime does not have GD/Imagick, so the screenshot had to be registered manually as an attachment rather than imported through `wp media import`; it renders publicly, but WordPress did not generate derivative sizes/thumbnails for it. I left the homepage backlink target `/` unchanged because this task was post-only, and I skipped Flatlogic link placement because it was not contextually appropriate for a church visitor guide. WP_POST_ID: 80 WP_POST_STATUS: publish WP_POST_URL: https://ridgecrestchurch.com/what-to-expect-ridgecrest-baptist-church/ WP_AUTHOR_USER: marcus-reed / Marcus Reed FEATURED_IMAGE_ID: 10 INLINE_IMAGE_IDS: 10,79 BLOG_INDEX_STATUS: ready; https://ridgecrestchurch.com/blog/ with page_for_posts=23 LEGACY_PATH_STATUS: not_applicable LINK_TARGETS_USED: none VERIFICATION: `wp post get`, `wp post url`, public `curl -I/-L`, blog index check, and `post_content` image/link checks all passed.