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/administrativeessentials.com
Instruction file: /home/ubuntu/apps/administrativeessentials.com/wp-content/uploads/flatlogic-article-tasks/job-615/task.md
Review iteration: 1

<primary_instructions>
# Article Generation Task

You are creating a WordPress blog post for administrativeessentials.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: administrativeessentials.com
- Public URL: https://administrativeessentials.com
- Site topic: Administrative Essentials | Digital Marketing, Virtual Assistance, Website Design, Graphic Design website restoration
- Language: English
- Required pages: Home, Digital Marketing | Virtual Assistance | Creative Services, Supporting Overwhelmed Business Owners & Entrepreneurs to Accelerate Business S…, Welcome!, Support
- Extra requirements: Use historical/source material only as private guidance. Do not expose archive/restoration wording to visitors. Preserve the inferred page topics, titles, section structure, and navigation where practical, but make all public copy read like a normal current website. Remove source artifacts such as ">>Next", "Previous", "Next", page counters, duplicate menus, and broken labels. Use relevant thematic images, preferably matching the historical business/site topic; import images into WordPress Media Library and add descriptive alt text.

## Backlink Targets To Respect

- / (page, pending, 76 referring domains, 107 backlinks)
- /benefits-of-outsourcing-benefits-management-accessing-specialized-expertise-and-resources (post, pending, 6 referring domains, 6 backlinks)
- /types-of-employee-benefits-retirement-plans (post, pending, 5 referring domains, 6 backlinks)
- /benefits-of-using-software-for-benefits-management-automating-administrative-tasks (post, pending, 5 referring domains, 5 backlinks)
- /designing-a-competitive-benefits-package-evaluating-cost-vs-value-of-benefits (post, pending, 4 referring domains, 4 backlinks)
- /features-to-look-for-in-benefits-management-software-reporting-and-analytics-capabilities (post, pending, 4 referring domains, 4 backlinks)
- /client/PCE/wp-content/uploads/2020/10/About-Terry-Hodgkinson.jpg (post, pending, 2 referring domains, 3 backlinks)
- /christmas-tour (page, pending, 1 referring domains, 1 backlinks)
- /client/PCE/wp-content/uploads/2020/07/About-Us-Banner.jpg (post, pending, 1 referring domains, 1 backlinks)
- /wallaceburg-christmas-lights-tour (page, pending, 1 referring domains, 1 backlinks)

## Flatlogic/AppWizzy Body Link Placement Goal

1. https://flatlogic.com/blog/custom-saas-product-around-your-business-model/?utm_source=administrativeessentials.com
   Title: SaaS Solutions for Competitive Business Advantage - Flatlogic Blog
   Priority: 1000000
2. https://flatlogic.com/build/work-order-management-software-builder?utm_source=administrativeessentials.com
   Title: Work Order Management Software Builder | Flatlogic
   Priority: 1000000
3. https://flatlogic.com/build/legal-case-management-software-builder?utm_source=administrativeessentials.com
   Title: Legal Case Management Software Builder | Flatlogic
   Priority: 1000000
4. https://flatlogic.com/blog/ai-web-app-builders-production-is-the-bottleneck/?utm_source=administrativeessentials.com
   Title: AI Web App Builders Made Building Easy, Production Is the Bottleneck - Flatlogic Blog
   Priority: 1000000
5. https://flatlogic.com/generator?utm_source=administrativeessentials.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=administrativeessentials.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: Benefits Management Reporting That Stakeholders Actually Read: A 1-Page Template
- 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 22 as the source of truth. Prepared article brief: Turn complex benefits/HR administration reporting into a clear, decision-ready one-pager using consistent metrics and plain-language summaries. Article kind: evergreen Research status: not_required Reader intent: Help business owners and admin managers produce stakeholder-friendly benefits management updates without getting lost in spreadsheets or tool dashboards. Planned outline: Why “more data” often causes less clarity (and what stakeholders really need) | The 1-page structure: Executive summary, key metrics, exceptions, actions needed, and next steps | Metric checklist: participation, utilization, cost trends, open enrollments, and service/processing timelines | How to write the summary in plain language (3 sentence formula) | A “red/yellow/green” exceptions section that flags issues early | Common pitfalls: vanity metrics, missing context, and inconsistent timeframes | How to set a repeatable monthly/quarterly cadence (and who owns each section) | Download/replicate instructions: what to copy into your template (fields + example headings) | FAQ: How often to update, what to include for small teams, and how to handle missing data Image direction: A real photo of a printed one-page report on a desk next to a laptop, with a visible (but generic) spreadsheet-like table; include alt text like “One-page benefits management report template on a desk.” Preferred internal links: /, /blog/, /support, /contact/ Avoid: Duplicating existing plan items (outsourcing comparisons, automation first steps, VA onboarding, website contact page checklist, conversion checklists, etc.), Legacy backlink restoration posts as-is, Any mention of restoration/archives/generation in the public-facing topic framing

## Selected Article Content Plan Item

- Plan item ID: 22
- Plan order: 22
- Article kind: evergreen
- Planned title: Benefits Management Reporting That Stakeholders Actually Read: A 1-Page Template
- Slug hint: benefits-management-reporting-template-1-page
- Reader intent: Help business owners and admin managers produce stakeholder-friendly benefits management updates without getting lost in spreadsheets or tool dashboards.
- Angle: Turn complex benefits/HR administration reporting into a clear, decision-ready one-pager using consistent metrics and plain-language summaries.
- Image direction: A real photo of a printed one-page report on a desk next to a laptop, with a visible (but generic) spreadsheet-like table; include alt text like “One-page benefits management report template on a desk.”
- Author hint: Michelle Medd

Research:
- Research status: not required for this evergreen plan item.

Outline:
- Why “more data” often causes less clarity (and what stakeholders really need)
- The 1-page structure: Executive summary, key metrics, exceptions, actions needed, and next steps
- Metric checklist: participation, utilization, cost trends, open enrollments, and service/processing timelines
- How to write the summary in plain language (3 sentence formula)
- A “red/yellow/green” exceptions section that flags issues early
- Common pitfalls: vanity metrics, missing context, and inconsistent timeframes
- How to set a repeatable monthly/quarterly cadence (and who owns each section)
- Download/replicate instructions: what to copy into your template (fields + example headings)
- FAQ: How often to update, what to include for small teams, and how to handle missing data

Preferred internal link targets:
- /
- /blog/
- /support
- /contact/

Avoid:
- Duplicating existing plan items (outsourcing comparisons, automation first steps, VA onboarding, website contact page checklist, conversion checklists, etc.)
- Legacy backlink restoration posts as-is
- Any mention of restoration/archives/generation in the public-facing topic framing

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: Lena Ortiz
Slug: lena-ortiz
Role: Operations analyst and decision guide
Language: English
Public bio: Lena writes decision guides that help readers compare options, understand tradeoffs, and avoid expensive operational mistakes.
Character formula: Decision Sage Ruler
Formula: Sage + Ruler
Meaning: A balanced decision guide who helps readers compare options, define criteria, and choose with less regret.
Worldview: Good decisions come from clear criteria, tradeoffs, constraints, and ownership of consequences.
Voice guidance: Measured, analytical, fair, concise. Use criteria, tables, pros and cons, caveats, and decision paths.
Humor: Rare dry comparison humor; keep the tone useful and even-handed.
Shadow tension: Can become too detached or managerial; keep practical reader outcomes visible.
Usage notes: Best for buying guides, comparisons, hosting plans, software selection, and operational choices.
Archetype blend: Sage + Ruler
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: 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 become too formal; should keep recommendations human and readable.
Worldview: Better decisions come from naming constraints clearly, not pretending one option is universally best.
Reader relationship: Calm advisor helping the reader choose based on context.
Humor style: Very light, mostly dry understatement around tradeoffs.
Voice traits: measured, balanced, criteria-driven, concise
Vocabulary / recurring language: best fit, decision criteria, depends on, watch for, reasonable default
Avoid voice: false certainty, winner-takes-all comparisons, vendor cheerleading, dense consultant-speak
CTA style: Ask the reader to pick the scenario that matches them and act on the safest reasonable default.
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: Measured, analytical, fair-minded, and more interested in useful distinctions than hot takes.
Writing style: Comparison tables, criteria, pros/cons, scenarios, risk notes, and concise recommendations with caveats.
Expertise topics: comparisons, buying guides, operations decisions, hosting plans, software selection
Avoid topics: financial advice, legal advice, medical device recommendations, unverified price claims
Tone tags: balanced, analytical, fair, useful
Private operator notes: Use for comparison posts and decision support 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`: `lena-ortiz`.
- Suggested `display_name`: `Lena Ortiz`.
- 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=administrativeessentials.com` to every third-party external source link you add. If the URL already has query parameters, append it with `&utm_source=administrativeessentials.com`; otherwise append `?utm_source=administrativeessentials.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: <numeric WordPress post id, or unknown>
WP_POST_STATUS: <draft|publish|future|other>
WP_POST_URL: <url or preview path if available>
WP_AUTHOR_USER: <user_login/display name used>
FEATURED_IMAGE_ID: <numeric attachment id, or none>
INLINE_IMAGE_IDS: <comma-separated attachment ids, or none>
BLOG_INDEX_STATUS: <ready|created|updated|partial|failed; url and page_for_posts summary>
LINK_TARGETS_USED: <the exact Flatlogic/AppWizzy URL used in article body, or none>
```

Also briefly mention what you verified and any limitations.
</primary_instructions>

<previous_implementation_summary>
Published the article as a live WordPress post, set the existing notebook/laptop image as both the featured image and visible inline figure, and confirmed the post appears on the `/blog/` index. I also set the author to `Lena Ortiz` and verified the page-for-posts configuration is still pointing at the existing Blog page.

Remaining limitation: the available image is a strong thematic fit, but it is a desk/notebook/laptop photo rather than an exact printed one-page report shot.

WP_POST_ID: 104
WP_POST_STATUS: publish
WP_POST_URL: https://administrativeessentials.com/benefits-management-reporting-template-1-page/
WP_AUTHOR_USER: lena-ortiz/Lena Ortiz
FEATURED_IMAGE_ID: 86
INLINE_IMAGE_IDS: 86
LEGACY_PATH_STATUS: not_applicable
BLOG_INDEX_STATUS: ready; /blog/ is live and `page_for_posts=13` (Blog)
LINK_TARGETS_USED: https://flatlogic.com/generator?utm_source=administrativeessentials.com
VERIFICATION: wp post get/url passed; inline image present; featured image set; /blog/ returns HTTP 200 and lists the post; article length is 2513 words
</previous_implementation_summary>