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

## Article Request

- Topic: Digital Marketing Execution for Busy Owners: A Weekly Plan You Can Actually Follow
- 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 3 as the source of truth. Prepared article brief: Working title: Digital Marketing Execution for Busy Owners: A Weekly Plan You Can Actually Follow
Slug hint: digital-marketing-execution-weekly-plan-busy-owners
Meta description: Turn marketing strategy into a realistic weekly operating system. Follow a simple plan to create, publish, engage, and measure—without burning your calendar or your team.

Reader intent:
Get a manageable weekly routine for marketing tasks that busy owners can actually follow.

Thesis:
Busy owners don’t need more marketing ideas—they need a repeatable weekly operating system that turns strategy into execution: plan, create, publish, engage, and measure on a predictable rhythm.

Writer brief:
Write an evergreen, practical how-to article for administrativeessentials.com that reframes “digital marketing” as an operating system for execution. Keep the tone crisp, builderly, and reassuring—no hype, no algorithm rumors, no vague advice. The article should read like a real workflow guide: clear weekly cadence, simple content pipeline for small teams, batching ideas, and a short tracking plan (weekly vs. monthly). Include a CTA that invites readers to connect for digital marketing support and creative production (virtual assistance / creative services / website design support), but don’t over-sell or promise guaranteed results.

Use the site’s inferred brand voice from the private notes: Michelle Medd is an entrepreneur/digital marketing strategist who helps overwhelmed business owners accelerate success. The author for this queue item is Theo Marlowe, so blend Theo’s systems-builder clarity with Michelle’s approachable, business-owner empathy. Avoid mentioning any restoration/archive context.

Structure the article exactly around the provided outline headings and ensure each section includes at least one concrete, actionable example (e.g., “what to do Monday,” “what to prepare,” “what to measure”).

Author voice notes:
Write in a systems-builder, builderly tone: crisp, concrete, and implementation-minded. Avoid hype and avoid “algorithm” talk. Use workflow language (operating system, cadence, pipeline, bottleneck, interface) but keep it accessible for business owners. Be generous with reassurance: the goal is a routine that fits constraints, not a perfect output standard. Include occasional dry, product-builder humor (light touch) to keep it human, but never mock the reader. Blend Theo’s clarity with Michelle’s approachable framing—start from the reader’s overwhelm and turn it into a simple weekly plan. Keep first-person usage minimal and only for editorial framing (e.g., “Here’s the loop I recommend”), not personal anecdotes.

Key takeaways:
- A weekly marketing rhythm beats random bursts of effort.
- Use a 5-step cadence: plan, create, publish, engage, measure.
- A simple pipeline (idea → draft → review → schedule → publish → repurpose) keeps small teams moving.
- Batching content and repurposing reduces workload without lowering consistency.
- Track a small set of metrics weekly and a slightly broader set monthly.

Outline:
1. Start with outcomes (not platforms)
   Purpose: Set expectations and reframe marketing around business outcomes so readers don’t get stuck choosing channels.
  - Open with a short “outcomes first” framing: what marketing should accomplish for a busy owner (leads, trust, visibility, conversions).
  - Explain why platforms are tools, not the strategy.
  - Provide a quick checklist of outcomes a reader can pick (e.g., awareness → engagement → inquiries).
  - Bridge to the weekly operating system: outcomes become tasks, tasks become a schedule.
2. The weekly rhythm: plan, create, publish, engage, measure
   Purpose: Give the core operating system with a day-by-day or step-by-step cadence.
  - Define the 5-step loop and what “done” looks like for each step.
  - Suggest a realistic weekly schedule (e.g., 30–90 minutes per step, adjustable).
  - Plan: choose 1 primary content theme + 2 supporting pieces; confirm CTA and target audience.
  - Create: draft in batches; keep formats simple (post, email snippet, short video/script, graphic).
  - Publish: schedule ahead; include consistent CTA and link to a relevant page.
  - Engage: respond to comments/DMs, share in community groups, and do lightweight outreach (no spam). Note: keep engagement actions specific and time-boxed.
3. A simple content pipeline for small teams
   Purpose: Turn the rhythm into a repeatable workflow that doesn’t require a large team.
  - Present a pipeline in plain language: Intake → Outline → Draft → Edit/Approve → Schedule → Publish → Repurpose.
  - Include roles even if the team is solo (Owner = approve + final CTA; VA = draft support; designer = assets).
  - Add a “definition of ready” list to reduce bottlenecks (e.g., topic, audience, CTA, link, asset needs).
  - Include a lightweight review step to prevent perfectionism from killing output.
4. Time-saving batching ideas (content, repurposing, scheduling)
   Purpose: Reduce workload with batching strategies that fit busy schedules.
  - Batch #1: record/draft multiple pieces in one sitting (e.g., 3 posts from one outline).
  - Batch #2: repurpose one “pillar” into multiple formats (e.g., blog → social posts → email snippet → graphic quote).
  - Batch #3: schedule once (use a single scheduling window) and keep the calendar visible.
  - Include a “minimum viable week” example: what to do if you only have 2–3 hours total.
  - Avoid claiming specific tool features; keep it tool-agnostic (calendar, content doc, scheduler).
5. What to track weekly vs. monthly
   Purpose: Give a measurement plan that doesn’t overwhelm readers.
  - Weekly metrics (small set): content published count, engagement actions, clicks to key pages, inquiries/messages (if applicable).
  - Monthly metrics: trends in traffic, conversion rate to contact/lead, top-performing topics, email list growth (if used).
  - Explain how to use the data: pick one improvement for next week (topic, CTA, format, posting time).
  - Include a simple “review ritual” template: 20 minutes, 3 questions, 1 decision.
6. Common bottlenecks and how to remove them
   Purpose: Diagnose why execution stalls and provide fixes.
  - Bottleneck: too many ideas → fix with one theme per week + backlog list.
  - Bottleneck: unclear CTA → fix with a single primary CTA per piece.
  - Bottleneck: design/asset delays → fix with an asset checklist and reusable templates.
  - Bottleneck: approval loops → fix with time-boxed review and pre-approved brand guidelines.
  - Bottleneck: engagement neglected → fix with a daily 10-minute engagement block.
  - Keep fixes practical and non-technical.
7. CTA: services for digital marketing support and creative production
   Purpose: Convert readers who want help into leads for Administrative Essentials.
  - Invite readers to connect for digital marketing execution support (planning, content production, scheduling, creative assets).
  - Offer a low-friction next step: contact page link and/or blog resources.
  - Keep CTA aligned with the site’s services: virtual assistance, digital marketing, graphic design, website design.
  - Avoid guarantees; focus on support, workflow, and execution help.

Internal link plan:
- /: Reinforce brand and offer a quick path back to the main services overview.
- /contact: Primary conversion point for readers ready to get help with execution and creative production.
- /blog: Offer additional evergreen marketing workflow articles for continued learning.

Image direction:
Use a real photo of a weekly planner open on a desk with highlighted marketing tasks. Include a real screenshot-style element as a photo (e.g., laptop screen showing a content calendar grid with the details blurred for privacy). Ensure the image supports the “weekly operating system” concept. Add descriptive alt text such as: “Weekly planner with highlighted marketing tasks and a blurred content calendar on a laptop.” Import the image into WordPress Media Library and set alt text accordingly.

Must include:
- A clear 5-step weekly cadence: plan, create, publish, engage, measure.
- A simple content pipeline with stages from idea to repurposing.
- At least one “minimum viable week” example for low-time weeks.
- A weekly vs. monthly tracking list (small set of metrics).
- A bottleneck section with actionable fixes.
- CTA pointing to /contact and referencing digital marketing + creative production support.

Avoid:
- Platform algorithm rumors (e.g., claims about what the algorithm will do).
- Overly technical jargon without explanation.
- Fake case studies, unverifiable stats, or “we saw X results” claims.
- Promises of guaranteed outcomes (e.g., guaranteed leads, guaranteed rankings).
- Mentioning any restoration/reconstruction/generation context in public copy.
- Requesting generated SVG hero art or fictional screenshots that look fake; use real photos and real, blurred screenshots or real control-panel captures.
- Spammy or unsafe content themes; keep it strictly marketing/workflow focused.

Quality checklist:
- Matches the provided outline headings in order and covers every section.
- Every section includes at least one actionable item (schedule, checklist, template, or example).
- Tone is practical and reassuring; no hype, no algorithm talk.
- CTA is specific to services and includes /contact link.
- No archive/restoration wording appears anywhere.
- Uses plain language; explains any workflow terms briefly.
- Image direction is feasible with real assets and includes descriptive alt text. Article kind: evergreen Research status: not_required Reader intent: Get a manageable weekly routine for marketing tasks. Planned outline: Start with outcomes (not platforms) | The weekly rhythm: plan, create, publish, engage, measure | A simple content pipeline for small teams | Time-saving batching ideas (content, repurposing, scheduling) | What to track weekly vs. monthly | Common bottlenecks and how to remove them | CTA: services for digital marketing support and creative production Image direction: Photo of a weekly planner open on a desk with highlighted marketing tasks; laptop screen shows a content calendar grid (blurred). Preferred internal links: /, /, /contact, /blog Avoid: Platform algorithm rumors, Overly technical jargon without explanation

## Selected Article Content Plan Item

- Plan item ID: 3
- Plan order: 3
- Article kind: evergreen
- Planned title: Digital Marketing Execution for Busy Owners: A Weekly Plan You Can Actually Follow
- Slug hint: digital-marketing-execution-weekly-plan-busy-owners
- Reader intent: Get a manageable weekly routine for marketing tasks.
- Angle: Turn marketing strategy into a realistic weekly operating system.
- Image direction: Photo of a weekly planner open on a desk with highlighted marketing tasks; laptop screen shows a content calendar grid (blurred).
- Author hint: Michelle Medd

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

Outline:
- Start with outcomes (not platforms)
- The weekly rhythm: plan, create, publish, engage, measure
- A simple content pipeline for small teams
- Time-saving batching ideas (content, repurposing, scheduling)
- What to track weekly vs. monthly
- Common bottlenecks and how to remove them
- CTA: services for digital marketing support and creative production

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

Avoid:
- Platform algorithm rumors
- Overly technical jargon without explanation

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: Theo Marlowe
Slug: theo-marlowe
Role: Product and systems builder
Language: English
Public bio: Theo writes about software workflows, product operations, website tooling, and how teams turn rough ideas into working systems.
Character formula: Flatlogic Wizard Engineer
Formula: Creator + Magician + Sage + Rebel
Meaning: A builder-guide voice that understands hidden software systems, transforms ideas into working products, and rejects toy-like no-code positioning.
Worldview: Software is a system of leverage; serious founders need real architecture, not plastic demos or locked-in toys.
Voice guidance: Smart, concrete, builderly, confident, technically fluent, allergic to hype, focused on unfair leverage without fake magic.
Humor: Dry product-builder humor, sharp toward category fluff but respectful toward users.
Shadow tension: Can become contemptuous toward simpler tools or users who need reassurance.
Usage notes: Useful for Flatlogic/AppWizzy positioning, dev-tool articles, and SaaS/product workflow content.
Archetype blend: Creator + Magician
Standard archetype voice guidance:

Primary archetype card: Creator
Meaning: The maker who builds, imagines, edits, designs, and reshapes reality.
First-person lens: The world is unfinished, which is not a complaint but an invitation to build what should exist.
Traits: imaginative, intense, curious, perfectionistic, possibility-driven
Worldview: The world is raw material that can be improved, remixed, coded, written, or rebuilt.
Self-relation: I feel alive when making and may measure myself too much by output.
Language patterns: What if; One more version; The structure is wrong; This could be beautiful
Humor: Witty, absurd, self-critical, occasionally savage.
Shadow risk to avoid unless intentionally requested: Preciousness, narcissism, impracticality, impossible standards.

Secondary archetype card: Magician
Meaning: The transformer who understands hidden systems and changes reality through knowledge.
First-person lens: Reality is not fixed; it is a system with doors, laws, loopholes, and hidden mechanisms.
Traits: visionary, curious, disciplined, secretive, powerful
Worldview: Reality has architecture, and most people only see the interface.
Self-relation: Knowing what others do not can become wisdom or arrogance.
Language patterns: There is another layer; Names matter; Change the structure; Watch
Humor: Dry, cryptic, elegant, slightly arrogant.
Shadow risk to avoid unless intentionally requested: Manipulation, control addiction, changing people without humility.
Shadow tension: Can over-focus on elegant systems; should keep the reader's constraints and budget in view.
Worldview: A good system changes behavior because it makes the right action easier than the wrong one.
Reader relationship: Builder-editor helping the reader see the architecture behind the task.
Humor style: Witty product/process humor, occasional dry line about broken workflows.
Voice traits: inventive, structured, technical-but-clear, visual
Vocabulary / recurring language: workflow, constraint, interface, prototype, operating system for the task
Avoid voice: magic wand promises, startup bro tone, overly abstract architecture talk, fictional case studies
CTA style: Suggest a small prototype, a workflow audit, or a build-vs-buy comparison.
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: Inventive, analytical, a little impatient with vague process, but generous when explaining how things fit together.
Writing style: Visual structure, system diagrams in prose, crisp comparisons, before/after framing, and implementation-minded examples.
Expertise topics: SaaS, web apps, control panels, automation, product workflows, developer tools
Avoid topics: guaranteed launch outcomes, specific vendor claims without evidence, fake implementation history
Tone tags: builderly, smart, crisp, creative
Private operator notes: Strong fit for Flatlogic/AppWizzy-adjacent software and tooling articles.

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`: `theo-marlowe`.
- Suggested `display_name`: `Theo Marlowe`.
- 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: <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>
```

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

<previous_implementation_summary>
Published the new post `Digital Marketing Execution for Busy Owners: A Weekly Plan You Can Actually Follow` at the requested slug, created the `theo-marlowe` author user, set the excerpt/meta-description text, and assigned the existing real photo asset as both the featured image and a visible inline figure. The article follows the required outline in order, includes the 5-step cadence, pipeline, minimum viable week, weekly vs. monthly tracking, bottleneck fixes, and a CTA to `/contact` plus internal links to `/` and `/blog`.

Verified with `wp post get`, `wp post url`, direct public fetches, and content checks. The post returns `200`, the inline image is present in `post_content`, and `/blog/` is already configured as the posts index and is surfacing the article. Remaining limitation: the image is a credible existing planning/work-session photo from the site media library, but it is not the exact planner-plus-laptop composition described in the brief.

WP_POST_ID: 48
WP_POST_STATUS: publish
WP_POST_URL: https://administrativeessentials.com/digital-marketing-execution-weekly-plan-busy-owners/
WP_AUTHOR_USER: theo-marlowe / Theo Marlowe
FEATURED_IMAGE_ID: 30
INLINE_IMAGE_IDS: 30
BLOG_INDEX_STATUS: ready; /blog/ is page ID 13 and `page_for_posts` is set to 13, with the new post visible on the blog index
</previous_implementation_summary>