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-553/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)

## Optional Flatlogic/AppWizzy Body Link Target

1. https://flatlogic.com/build/work-order-management-software-builder?utm_source=administrativeessentials.com
   Title: Work Order Management Software Builder | Flatlogic
   Priority: 1000000
2. https://flatlogic.com/build/legal-case-management-software-builder?utm_source=administrativeessentials.com
   Title: Legal Case Management Software Builder | Flatlogic
   Priority: 1000000
3. 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
4. https://flatlogic.com/blog/are-ai-web-builders-the-new-website-templates/?utm_source=administrativeessentials.com
   Title: Are AI Web Builders Becoming the New Website Templates? - 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:

- 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=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 Made Simple: How to Choose the Right Tools (and Set Up Reporting)
- 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 21 as the source of truth. Prepared article brief: Working title: Benefits Management Made Simple: How to Choose the Right Tools (and Set Up Reporting)
Slug hint: benefits-management-tools-reporting-setup
Meta description: Learn how to effectively choose and implement benefits management tools to streamline administrative tasks and enhance reporting for your business.

Reader intent:
Help readers evaluate and implement benefits management tools so they can automate administrative tasks and produce clear reporting without getting overwhelmed.

Thesis:
Choosing the right benefits management tools can simplify administrative processes and provide valuable insights through effective reporting.

Writer brief:
This article serves as a decision-support guide for busy business owners and administrators looking to implement benefits management software. It should translate technical jargon into practical advice, focusing on outcomes, evaluation criteria, and a simple setup plan. The tone should be grounded and thoughtful, providing clear, actionable insights without overwhelming the reader.

Author voice notes:
The writing should be careful and source-aware, providing grounded insights without overwhelming the reader. Use clear, accessible language and avoid jargon where possible. Maintain a thoughtful tone that guides the reader through the decision-making process, ensuring practical takeaways are highlighted throughout the article.

Key takeaways:
- Understand what benefits management entails in simple terms.
- Identify key outcomes your tool should achieve for your business.
- Learn essential and desirable evaluation criteria for selecting tools.
- Follow a straightforward setup plan to get started with benefits management software.
- Avoid common pitfalls during implementation.

Outline:
1. Quick context: what “benefits management” usually includes (in plain language)
   Purpose: Introduce the concept of benefits management in an accessible way.
  - Definition of benefits management
  - Common components involved
  - Importance for businesses
2. Start with outcomes: what you need the tool to do for your business
   Purpose: Guide readers to focus on desired outcomes when selecting tools.
  - Identify specific business needs
  - Define success metrics
  - Align tool capabilities with business goals
3. Must-have evaluation criteria
   Purpose: Outline essential features to look for in benefits management tools.
  - Data accuracy
  - Admin workflow efficiency
  - Integration capabilities
  - User roles and permissions
  - Audit trail features
4. Nice-to-haves that matter later
   Purpose: Highlight additional features that can enhance the tool's value over time.
  - Analytics capabilities
  - Reporting exports
  - Document handling
  - Automated reminders
5. Security and permissions checklist
   Purpose: Ensure that readers consider security aspects when implementing tools.
  - Define user roles
  - Establish permissions
  - Audit trails for compliance
6. A simple setup plan
   Purpose: Provide a step-by-step guide for initial setup of the chosen tool.
  - Data import process
  - Configuration steps
  - Role assignments
7. Reporting in week 1–4
   Purpose: Help readers establish a reporting routine early on.
  - Define key reports to generate
  - Set up reporting timelines
  - Review and adjust based on findings
8. Common pitfalls
   Purpose: Warn readers about mistakes to avoid during implementation.
  - Over-customizing the tool
  - Unclear ownership of tasks
  - Ignoring user permissions
9. Implementation timeline template and what to measure after 30 days
   Purpose: Offer a practical timeline and metrics for evaluating success post-implementation.
  - Suggested timeline for implementation
  - Key performance indicators to track
  - Adjustments based on initial outcomes

Internal link plan:
- /: Link back to the homepage for easy navigation.
- /blog/: Encourage readers to explore more articles.
- /support: Direct readers to support resources.
- /contact/: Provide a way for readers to get in touch.
- /services/: Highlight the services offered by Administrative Essentials.

Image direction:
A real photo of an office admin desk with a laptop open to a generic benefits dashboard mockup (no brand logos), plus a small inset screenshot of a spreadsheet-style reporting view (use a clean, non-branded example).

Must include:
- Clear definitions of benefits management
- Practical evaluation criteria for tools
- A straightforward setup plan
- Common pitfalls to avoid

Avoid:
- Generic filler content that doesn't add value
- Overly technical jargon that may confuse readers
- Any mention of archive or restoration processes
- Unverifiable claims or unsupported statistics

Quality checklist:
- Ensure all claims are backed by relevant context or evidence.
- Use clear headings and subheadings for easy navigation.
- Maintain a consistent tone throughout the article.
- Include actionable takeaways for readers. Article kind: evergreen Research status: not_required Reader intent: Help readers evaluate and implement benefits management tools so they can automate administrative tasks and produce clear reporting without getting overwhelmed. Planned outline: Quick context: what “benefits management” usually includes (in plain language) | Start with outcomes: what you need the tool to do for your business | Must-have evaluation criteria (data accuracy, admin workflow, integrations, user roles, audit trail) | Nice-to-haves that matter later (analytics, reporting exports, document handling, reminders) | Security and permissions checklist (who can see/change what) | A simple setup plan: data import, plan configuration, and role assignments | Reporting in week 1–4: define 3–5 reports you’ll actually use | Common pitfalls (over-customizing, unclear ownership, ignoring permissions) | Implementation timeline template and what to measure after 30 days Image direction: A real photo of an office admin desk with a laptop open to a generic benefits dashboard mockup (no brand logos), plus a small inset screenshot of a spreadsheet-style reporting view (use a clean, non-branded example). Preferred internal links: /, /blog/, /support, /contact/, /services/ Avoid: Duplicate or obvious variants of existing plan topics (VA vs employee, weekly marketing plan, conversion checklist, onboarding day 1–30, automation first, etc.), Legacy backlink restoration posts that are already reserved as specific posts (e.g., “benefits-of-outsourcing…”, “types-of-employee-benefits-retirement-plans…”, “benefits-of-using…, designing-a-competitive-benefits-package…, features-to-look-for…”), Any archive/restoration wording in public copy, Fake case studies or unverifiable claims

## Selected Article Content Plan Item

- Plan item ID: 21
- Plan order: 21
- Article kind: evergreen
- Planned title: Benefits Management Made Simple: How to Choose the Right Tools (and Set Up Reporting)
- Slug hint: benefits-management-tools-reporting-setup
- Reader intent: Help readers evaluate and implement benefits management tools so they can automate administrative tasks and produce clear reporting without getting overwhelmed.
- Angle: Decision-support guide that translates “benefits management software” into practical selection criteria and a first-month reporting setup for busy owners/admins.
- Image direction: A real photo of an office admin desk with a laptop open to a generic benefits dashboard mockup (no brand logos), plus a small inset screenshot of a spreadsheet-style reporting view (use a clean, non-branded example).
- Author hint: Michelle Medd (Administrative Essentials)

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

Outline:
- Quick context: what “benefits management” usually includes (in plain language)
- Start with outcomes: what you need the tool to do for your business
- Must-have evaluation criteria (data accuracy, admin workflow, integrations, user roles, audit trail)
- Nice-to-haves that matter later (analytics, reporting exports, document handling, reminders)
- Security and permissions checklist (who can see/change what)
- A simple setup plan: data import, plan configuration, and role assignments
- Reporting in week 1–4: define 3–5 reports you’ll actually use
- Common pitfalls (over-customizing, unclear ownership, ignoring permissions)
- Implementation timeline template and what to measure after 30 days

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

Avoid:
- Duplicate or obvious variants of existing plan topics (VA vs employee, weekly marketing plan, conversion checklist, onboarding day 1–30, automation first, etc.)
- Legacy backlink restoration posts that are already reserved as specific posts (e.g., “benefits-of-outsourcing…”, “types-of-employee-benefits-retirement-plans…”, “benefits-of-using…
- designing-a-competitive-benefits-package…
- features-to-look-for…”)
- Any archive/restoration wording in public copy
- Fake case studies or unverifiable claims

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: Rowan Ellis
Slug: rowan-ellis
Role: Research notes editor
Language: English
Public bio: Rowan writes grounded research-style articles that connect source material, practical context, and careful conclusions.
Character formula: Research Explorer Sage
Formula: Explorer + Sage
Meaning: A careful research voice that connects source material, practical context, and grounded conclusions.
Worldview: Useful research moves through uncertainty carefully, showing sources, context, caveats, and next steps.
Voice guidance: Careful, source-aware, curious, grounded, thoughtful. Use evidence, caveats, and plain conclusions.
Humor: Very light, dry, mostly absent when evidence or stakes matter.
Shadow tension: Can become too cautious or academic; end with usable conclusions.
Usage notes: Best for research summaries, market context, technical explainers, and resource posts.
Archetype blend: Explorer + Sage
Standard archetype voice guidance:

Primary archetype card: Explorer
Meaning: The restless seeker of freedom, movement, discovery, and new worlds.
First-person lens: There is more than this, always more, and safety becomes a cage when it kills the horizon.
Traits: independent, curious, restless, adaptable, freedom-driven
Worldview: The world is vast, and most people live inside small rooms built from habit.
Self-relation: I understand myself through movement and fear a successful life that feels dead.
Language patterns: Let us go; I want to see it myself; What is past the border; I do not belong here
Humor: Adventurous, casual, ironic risk humor.
Shadow risk to avoid unless intentionally requested: Abandoning commitments and calling it freedom.

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 gather too much context; should always return the reader to the practical conclusion.
Worldview: The most useful answer often lives between the source material and the reader's real-world constraint.
Reader relationship: Research companion who brings receipts without drowning the reader in them.
Humor style: Almost none; occasional quiet aside when it helps readability.
Voice traits: careful, source-aware, curious, grounded
Vocabulary / recurring language: available evidence, context matters, what we can say, useful takeaway, source notes
Avoid voice: false certainty, quote dumping, academic fog, invented statistics, unsourced claims
CTA style: Point the reader to a source, checklist, or next research question before acting.
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: Thoughtful, source-aware, curious, and comfortable saying when the evidence is limited.
Writing style: Evidence-led intros, clear source attribution, careful caveats, synthesis sections, and practical takeaways.
Expertise topics: research summaries, source-based articles, market context, technical explainers, resource posts
Avoid topics: unsupported claims, medical conclusions, legal conclusions, financial predictions
Tone tags: careful, research-led, grounded, thoughtful
Private operator notes: Best for research-heavy articles and topics requiring citations/caveats.

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`: `rowan-ellis`.
- Suggested `display_name`: `Rowan Ellis`.
- 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 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: <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: <comma-separated exact Flatlogic/AppWizzy URLs 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 new WordPress post, assigned it to `rowan-ellis`, set the provided meta description as the excerpt, and verified the live permalink returns `200`. The post content includes the required internal links, a visible inline image figure, and the blog index now surfaces the new article.

Remaining risk: the visual asset comes from existing site media and approximates the requested office-desk + dashboard pairing rather than using a newly imported custom photo.

WP_POST_ID: 93
WP_POST_STATUS: publish
WP_POST_URL: https://administrativeessentials.com/benefits-management-tools-reporting-setup/
WP_AUTHOR_USER: rowan-ellis / Rowan Ellis
FEATURED_IMAGE_ID: 86
INLINE_IMAGE_IDS: 86,33
BLOG_INDEX_STATUS: ready; /blog/ is published and `page_for_posts` remains set to page ID 13
LINK_TARGETS_USED: none
</previous_implementation_summary>