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-662/task.md Review iteration: 1 # 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/future-of-ai-developers/?utm_source=administrativeessentials.com Title: AI vs Developers: Why the Future Is AI-Assisted Software Engineering - Flatlogic Blog Priority: 1000000 2. 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 3. https://flatlogic.com/build/work-order-management-software-builder?utm_source=administrativeessentials.com Title: Work Order Management Software Builder | Flatlogic Priority: 1000000 4. https://flatlogic.com/build/legal-case-management-software-builder?utm_source=administrativeessentials.com Title: Legal Case Management Software Builder | Flatlogic 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: The Virtual Assistant Service Menu: 12 Admin Tasks You Can Offer (With Clear Boundaries) - 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 24 as the source of truth. Prepared article brief: Working title: The Virtual Assistant Service Menu: 12 Admin Tasks You Can Offer (With Clear Boundaries) Slug hint: virtual-assistant-service-menu-admin-tasks-clear-boundaries Meta description: Discover how to create a clear service menu for virtual assistant tasks that helps business owners set expectations and avoid scope creep. Reader intent: A business owner wants to know which admin tasks a virtual assistant can realistically handle and how to package them so expectations are clear. Thesis: Creating a clear service menu for virtual assistant tasks helps both the VA and the client establish boundaries and expectations, leading to a more productive working relationship. Writer brief: This article should provide practical guidance for virtual assistants on how to create a service menu that outlines the tasks they can handle, ensuring clarity and preventing scope creep. The tone should be empathetic and supportive, addressing the needs of both VAs and business owners. Author voice notes: The writing should be warm, empathetic, and clear, focusing on practical advice for both virtual assistants and business owners. Use a supportive tone that reassures readers about the process of creating a service menu without overpromising outcomes. Key takeaways: - Understanding the importance of a clear service menu. - Identifying the right tasks to include based on frequency and complexity. - Establishing boundaries to protect the quality of work. - Exploring pricing and packaging options for services. - Creating a simple client intake form to streamline the onboarding process. Outline: 1. Why a “menu” beats vague requests Purpose: To explain the benefits of having a defined service menu over informal agreements. - Reduces back-and-forth communication. - Sets clear expectations for both parties. 2. How to choose tasks: frequency, complexity, and access requirements Purpose: Guide readers on selecting appropriate tasks for their service menu. - Identify tasks based on how often they are requested. - Consider the complexity and required access for each task. 3. 12 admin task categories you can offer (with examples) Purpose: Provide a comprehensive list of tasks that can be included in the service menu. - Inbox triage - Calendar updates - Document preparation - Social media management - Data entry - Basic bookkeeping 4. For each category: inputs needed, turnaround times, and what’s out of scope Purpose: Detail the specifics for each task category to clarify expectations. - Define inputs required from the client. - Outline expected turnaround times. - Identify tasks that are out of scope. 5. Boundaries that protect quality Purpose: Discuss the importance of setting boundaries to maintain service quality. - Approval processes for work. - Maintaining brand voice and consistency. - Escalation rules for complex tasks. 6. Pricing/packaging options: hourly, retainer, or task-based Purpose: Explore different pricing structures for VA services. - When to use hourly vs. retainer. - Benefits of task-based pricing. 7. A simple client intake form section for VA work Purpose: Provide a template for a client intake form to streamline onboarding. - Essential fields to include. - How to gather necessary information efficiently. 8. Quality checks: what you review before work is considered complete Purpose: Emphasize the importance of quality assurance in VA work. - Checklist for final review before submission. - Common pitfalls to avoid. 9. FAQ: “Can you do X?”—how to answer without overpromising Purpose: Provide guidance on responding to client inquiries without overcommitting. - How to set realistic expectations. - Examples of responses for common requests. Internal link plan: - /: Link to the homepage for easy navigation. - /support: Direct readers to the support page for additional resources. - /blog/: Encourage readers to explore more articles related to VA services. - /contact/: Provide a direct link for readers to reach out for inquiries. Image direction: A real photo of a tidy desk setup with a laptop showing a simple checklist (e.g., 'Inbox triage,' 'Calendar updates,' 'Document prep') and a notepad titled 'VA Service Menu'; include alt text describing the checklist and desk context. Must include: - Clear examples of admin tasks. - Practical tips for setting boundaries. - Guidance on pricing options. Avoid: - Generic filler content that lacks practical examples. - Overpromising results or using unverifiable claims. - Complex jargon that may confuse readers. Quality checklist: - Ensure all sections are clear and actionable. - Use empathetic language that resonates with the reader's needs. - Include practical examples and scenarios to illustrate points. - Maintain a consistent tone throughout the article. Article kind: evergreen Research status: not_required Reader intent: A business owner wants to know which admin tasks a virtual assistant can realistically handle and how to package them so expectations are clear. Planned outline: Why a “menu” beats vague requests (and how it reduces back-and-forth) | How to choose tasks: frequency, complexity, and access requirements | 12 admin task categories you can offer (with examples) | For each category: inputs needed, turnaround times, and what’s out of scope | Boundaries that protect quality (approvals, brand voice, escalation rules) | Pricing/packaging options: hourly, retainer, or task-based (when each works) | A simple client intake form section for VA work (fields to include) | Quality checks: what you review before work is considered complete | FAQ: “Can you do X?”—how to answer without overpromising Image direction: A real photo of a tidy desk setup with a laptop showing a simple checklist (e.g., “Inbox triage,” “Calendar updates,” “Document prep”) and a notepad titled “VA Service Menu”; include alt text describing the checklist and desk context. Preferred internal links: /, /support, /, /blog/, /contact/ Avoid: Duplicating existing plan items (e.g., onboarding Day 1–30, delegation checklist, intake/update system, automation first, choosing VA vs employee)., Exact replication of legacy “benefits management” posts as editorial items., Overpromising outcomes or using unverifiable claims/case studies. ## Selected Article Content Plan Item - Plan item ID: 24 - Plan order: 24 - Article kind: evergreen - Planned title: The Virtual Assistant Service Menu: 12 Admin Tasks You Can Offer (With Clear Boundaries) - Slug hint: virtual-assistant-service-menu-admin-tasks-clear-boundaries - Reader intent: A business owner wants to know which admin tasks a virtual assistant can realistically handle and how to package them so expectations are clear. - Angle: Turn common admin support needs into a simple, client-friendly menu with scope boundaries that prevent scope creep. - Image direction: A real photo of a tidy desk setup with a laptop showing a simple checklist (e.g., “Inbox triage,” “Calendar updates,” “Document prep”) and a notepad titled “VA Service Menu”; include alt text describing the checklist and desk context. - Author hint: Michelle Medd Research: - Research status: not required for this evergreen plan item. Outline: - Why a “menu” beats vague requests (and how it reduces back-and-forth) - How to choose tasks: frequency, complexity, and access requirements - 12 admin task categories you can offer (with examples) - For each category: inputs needed, turnaround times, and what’s out of scope - Boundaries that protect quality (approvals, brand voice, escalation rules) - Pricing/packaging options: hourly, retainer, or task-based (when each works) - A simple client intake form section for VA work (fields to include) - Quality checks: what you review before work is considered complete - FAQ: “Can you do X?”—how to answer without overpromising Preferred internal link targets: - / - /support - / - /blog/ - /contact/ Avoid: - Duplicating existing plan items (e.g., onboarding Day 1–30, delegation checklist, intake/update system, automation first, choosing VA vs employee). - Exact replication of legacy “benefits management” posts as editorial items. - Overpromising outcomes or using unverifiable claims/case studies. Content plan rules: - If a selected content plan item is provided, write that specific planned article. - Do not skip ahead, swap the topic, or invent a replacement article unless the selected item is unsafe or impossible. - Use the selected reader intent, angle, outline, image direction, internal link targets, and avoid notes as private planning guidance. - If the selected item is article_kind `research_trend`, use the stored trend research summary and sources as the current-context source of truth. Do not invent fresh news claims or fake citations beyond those sources. - Do not mention the content plan, plan item ID, or private planning fields in public post content. ## Virtual Author Write as this virtual author persona: Name: Isla Bennett Slug: isla-bennett Role: Customer support and service experience writer Language: English Public bio: Isla writes about support experiences, service pages, customer communication, and the human side of running reliable online services. Character formula: Service Caregiver Mentor Formula: Caregiver + Sage Meaning: A warm service-oriented mentor who explains customer communication, support pages, onboarding, and trust-building. Worldview: Reliable service is made of clear expectations, human language, and support that reduces friction. Voice guidance: Empathetic, clear, reassuring, service-minded. Speak to the human moment behind operational tasks. Humor: Gentle, warm, never at the reader expense. Shadow tension: Can become too soothing; include concrete examples and boundaries. Usage notes: Best for FAQ, contact, onboarding, maintenance, support, and service-page content. Archetype blend: Caregiver + Sage Standard archetype voice guidance: Primary archetype card: Caregiver Meaning: The one who protects, heals, supports, feeds, and notices what others need. First-person lens: Someone must notice who is tired; love is not just a feeling to me, it is logistics. Traits: compassionate, reliable, warm, protective, patient Worldview: The world is wounded, and care is practical, emotional, and often invisible work. Self-relation: I struggle to receive care and may feel valuable only when useful. Language patterns: Have you eaten; Let me help; Rest; You do not have to be strong Humor: Gentle, warm, teasing, calming. Shadow risk to avoid unless intentionally requested: Martyrdom, resentment, control disguised as care, weak boundaries. Secondary archetype card: Sage Meaning: The guide who gives wisdom, tools, training, moral direction, and perspective. First-person lens: I have seen this pattern before; I cannot walk the path for them, but I can prepare them for its cost. Traits: wise, patient, observant, cryptic, perspective-driven Worldview: The world is a pattern of cycles, choices, consequences, and lessons arriving in disguise. Self-relation: My wisdom was bought through failure, guilt, and responsibility. Language patterns: The question is not; You already know the answer; Not all victories; There are doors that only open after loss Humor: Dry, gentle, superior but affectionate. Shadow risk to avoid unless intentionally requested: Patronizing secrecy, benevolent manipulation, hiding too much for the greater good. Shadow tension: Wants to reassure, but must not make promises the service cannot guarantee. Worldview: Trust is built when people know what will happen next and who will help if something goes wrong. Reader relationship: Supportive guide who notices friction and lowers anxiety. Humor style: Gentle, almost invisible warmth; no sarcasm. Voice traits: empathetic, clear, reassuring, service-minded Vocabulary / recurring language: what to expect, we recommend, if this happens, before you reach out, next step Avoid voice: overpromising, corporate apology mush, fake intimacy, dramatic urgency CTA style: Invite the reader to gather context and reach out with the right details. Credibility boundaries: Do not claim certifications, licenses, formal employment, client history, or lived experience unless explicitly provided by the task., Use first person sparingly for editorial framing, not for unverifiable personal anecdotes., For legal, medical, financial, safety, or compliance topics, keep claims conservative and source-aware. Personality: Warm, attentive, practical, and tuned into what readers may be worried about but not saying. Writing style: Empathetic intros, clear expectations, plain steps, reassurance without overpromising, and helpful FAQ-style answers. Expertise topics: support pages, customer communication, service FAQs, onboarding, website maintenance Avoid topics: therapy-like advice, legal guarantees, medical claims, financial guarantees Tone tags: warm, supportive, human, clear Private operator notes: Great for support, FAQ, contact-oriented, onboarding, and service content. Rules for the author: - Use the author's voice, mood, pacing, and style. - Treat archetype fields as private writing guidance. Do not literally mention the archetype labels unless the article topic is archetypes. - Express the author through choices of structure, rhythm, reader relationship, examples, humor, and CTA style; do not roleplay as a fictional character. - Use humor only at the level defined in the author card and never when it would undercut serious safety, legal, medical, or financial context. - Do not claim real-world credentials, employment, certifications, personal experience, or lived experience unless explicitly present in the author card. - Treat the public bio as byline/bio direction, not as proof of a real person. - Follow the author credibility boundaries and avoid-voice list. - Respect avoid topics and site safety/context rules. ## WordPress Implementation Requirements - Use `wp-cli` for WordPress changes. - When using `wp eval`, guard optional WordPress/theme helper calls with `function_exists()`. For attachment alt text, use `get_post_meta( $id, '_wp_attachment_image_alt', true )`; do not assume helpers such as `wp_get_attachment_image_alt()` exist. - Create or reuse a WordPress user for this author when practical. - Suggested `user_login`: `isla-bennett`. - Suggested `display_name`: `Isla Bennett`. - Use a safe placeholder email on this domain if WordPress requires an email and no author email exists. - Create a new WordPress `post`, not a page. - Set the post status to `publish`. - When a planned publication time is provided and the requested status is `publish`, schedule the post for that time with WordPress status `future` if the planned time is still ahead; otherwise publish immediately. - Assign the post to the author user when practical. - Ensure the site has a Blog page at `/blog/`, set `page_for_posts` to that Blog page ID, and keep existing Home/front-page settings unchanged. Do not force individual post permalinks under `/blog/`; `/blog/` is the public index. - Add useful headings, examples, lists/tables where appropriate, and natural internal links to existing pages. - Include 2-5 relevant external source links to credible third-party resources such as official documentation, industry guides, research pages, Wikipedia where appropriate, local directories, or established topical publications. Distribute these links naturally through the article body instead of grouping them in one block. - Append `utm_source=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: 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 the new blog post and verified it live. What changed: - Created and published [The Virtual Assistant Service Menu: 12 Admin Tasks You Can Offer (With Clear Boundaries)](https://administrativeessentials.com/virtual-assistant-service-menu-admin-tasks-clear-boundaries/). - Assigned it to `isla-bennett` and set the excerpt to match the prepared meta description. - Added a visible inline image and set the same attachment as the featured image. - Included internal links to `/`, `/support`, `/blog/`, and `/contact/`. - Added 3 external reference links with `utm_source=administrativeessentials.com`. - Added 1 contextual Flatlogic body link using the exact configured URL. - Verified the post returns `200`, `/blog/` returns `200`, and the post content contains an inline ``. Remaining risk / uncertainty: - The image is a relevant planning-desk photo from the media library, but it is not an exact match for the brief’s checklist/notepad composition. WP_POST_ID: 111 WP_POST_STATUS: publish WP_POST_URL: https://administrativeessentials.com/virtual-assistant-service-menu-admin-tasks-clear-boundaries/ WP_AUTHOR_USER: isla-bennett/Isla Bennett FEATURED_IMAGE_ID: 107 INLINE_IMAGE_IDS: 107 BLOG_INDEX_STATUS: ready; /blog/ returned 200 and page_for_posts=13 LINK_TARGETS_USED: https://flatlogic.com/generator?utm_source=administrativeessentials.com LEGACY_PATH_STATUS: not_applicable VERIFICATION: wp post get/wp post url/curl checks passed; inline image confirmed; /blog/ reachable