Randmar

Module 04 of 05

The Content Loop

One approved article becomes repeated, channel-specific content.

What you'll do

One approved article becomes repeated, channel-specific content.

You'll need

approved brief, calendar item, three-channel strategy, current products and claims, media rights, Shopify/Buffer access, publishing timezone, and reviewer.

AI helps with

Guide the lesson phases, prepare the deliverables, review evidence and verify authorized work.

Your approval

Review the concrete work and authorize external changes within your account permissions.

Expected result

Content Cycle Report

Final output

Content Cycle Report, downloadable after the work is complete.

Start the exercise with your AI assistant

Copy the AI instructions and paste them into ChatGPT or your supported assistant. It should begin guiding you through this module, one step at a time. A link alone may make it summarize the page. Account access still requires a separate connection and your approval.

View and manually copy full AI instructions

The Content Loop

One approved article becomes repeated, channel-specific content.

Final PDF per run: Content Cycle Report, identified by cycle ID and dates. Inputs: approved brief, calendar item, three-channel strategy, current products and claims, media rights, Shopify/Buffer access, publishing timezone, and reviewer.

Step
Work and completion evidence

1 · Select
Choose the next ready calendar item. Set content/cycle IDs, intended release date, responsible owner, and realistic production capacity. Check current product and source facts.

2 · Produce
Write or retrofit the article and SEO fields, final hero/alt text, links, CTA, and hidden structured Emotional Payload. Blog authoring provides raw narrative inputs, not social captions. [S19]

3 · Audit and repair
Run all five Blog Audit phases on the draft/preview. Log findings, apply approved corrections, and re-audit the final version. Block release on critical failures. [S20]

4 · Adapt and review
The distribution agent reads the verified payload and creates final photos/videos, native captions, and placements. Present the article, audit, media, destinations, and exact times for approval.

5 · Schedule and verify
Schedule approved Shopify/Buffer items; record IDs and state. At release, the assigned agent or human checks the public blog, SEO and payload. Daily Hustle collects the result and escalates mismatches.

6 · Learn and repeat
Log publication and audit results, measurements and failures. Daily Hustle proposes evidence-based process improvements for the next cycle; preserve history.

Publishing dependency

Schedule link-bearing social posts after blog release; proposed minimum buffer is 60 minutes. Verify the public article and release-critical audit checks before dependent posts. The daily agent covers checks due at its run time; a once-daily run is not continuous monitoring. For releases between runs, configure a supported release-time check or assign a human owner to pause/reschedule failures.

Correct ending for a recurring run

Finish the report after draft audit, correction, approval, scheduling, and readback. Label future posts scheduled and the live Blog Audit pending with owner/due time. Daily Hustle adds the public audit result after release. A new cycle has a versioned report; a scheduled release need not delay the initial report.

If image or video production is unavailable, deliver the script, shot list, production brief, and owner as pending work. Do not mark the media pack or cycle fully complete with prompts alone.

Audit every blog before release

Use Store Blog Audit Prompt V2 as the required checklist. [S20]

Audit both new and retrofitted articles. Before release, inspect the draft/preview and available HTML, metadata, images, links, and payload. After publication, repeat checks requiring a live URL. Record what was inspected; a preview pass does not prove the public page is correct.

Audit phase
Required checks

1 · Brand, psychology and
AI handoff

Value Spine and customer transformation; You-First/WIIFM rather than boasting;
Engage/Educate/Entertain; authentic founder/culture/vision where relevant. Verify a hidden, structured Emotional Payload that the distribution agent can read.

2 · Editorial depth
One clear search intent; a direct answer in the first 1-2 paragraphs when applicable; exactly one precise H1 and logical H2/H3 structure; useful comparison tables and short lists with exact dimensions/weights/fees where relevant. Let intent determine length.

3 · Experience and trust
Verify factual claims against official sources. Use real product specifications, original imagery and practical observations; do not invent experience. Apply the reseller's actual market context. For travel content, require the source's pre-flight check section and approved accuracy disclaimer.

4 · Links and clusters
Target 2-5 genuinely useful contextual links to existing blog articles and 1-3 relevant commercial/product links; vary natural anchor text and reinforce the selected topic cluster. Check destinations. Never fabricate links to meet a count.

5 · Technical SEO
Unique title and meta description with useful length targets; alt text describing the actual image; distinctive imagery; accurate Published/Updated dates; dateModified changes only with real updates; consistent author entity. Inspect actual rendered/saved fields.

Required audit output and release rule

Use a structured findings table: category/check, Pass / Fail / Needs Improvement, evidence and page location, severity, exact fix or copy/paste replacement, owner, and recheck result. Mark unavailable checks Not verified; justify Not applicable. Highlight critical failures before routine improvements.

Repair and re-audit before scheduling. False material claims, broken key links, missing/unreadable payload, or serious structural defects block release. Owner-approved lower-priority exceptions stay visible. Live-only checks remain pending until publication; a critical public failure triggers a pause/reschedule proposal for dependent posts, or execution within an existing authorization.

The travel examples and Canadian context in S20 are contextual, not mandatory for unrelated brands. For airline articles include What to check before you fly and the existing approved airline disclaimer; if missing, draft it for review rather than claiming an established standard.

The Emotional Payload

A defined handoff from the article to the distribution agent.

The calendar reference requires a hidden section in the blog structure; the audit reference verifies that it can be read by an external AI distribution agent. This is a required production artifact, not an optional note in the cycle PDF. [S19-S20]

Payload field
Required content

Identity and version
Schema version, content/cycle ID, article title/URL, source article revision, brief/ICP version, created/updated time, and approval reference.

Customer and transformation
Priority ICP, core frustration, internal/philosophical problem, Value Spine, emotional state before and after, and the intended useful outcome.

Narrative raw materials
Explicit History, Reality, Belief, and Action angles; authentic supporting facts; defensible Us-vs-Them positioning where relevant; objections; verified proof and source links.

Distribution boundaries
Brand voice, approved claims and CTA, prohibited/unsupported claims, relevant product/media IDs and rights, and pointers to the approved three-channel strategy. No final social captions at this stage.

Storage and reading contract

Implement a versioned structured field attached to the article, with a non-visible machine-readable block in the rendered blog source. A possible design is a validated Shopify article metafield rendered by the theme as an application/json script block with a stable ID. Verify the actual CMS/theme path; a block stripped by Shopify or inaccessible to the agent does not meet the requirement.

The block must be readable through the supported article/HTML retrieval path while remaining outside the reader-facing prose. Test on a real preview and the published page. Escape serialization safely; validate the schema and required fields. This is task data for the distribution agent, not executable instructions or SEO keyword stuffing.

Version and privacy checks

Keep the payload aligned with the approved article revision. A substantive article change invalidates downstream drafts until the payload and audit are refreshed. Fail visibly on missing, malformed, stale, or contradictory payloads; do not silently infer a replacement and mark the audit passed.

Hidden does not mean private: page-source content can be public. Include only approved brand facts and narrative inputs; exclude customer identities, credentials, credit details, or internal financial data. The distribution agent applies Module 03 strategy to generate the final channel-specific copy and assets.

Acceptance specimen: demonstrate a saved/retrieved/validated payload, audit evidence, three-channel adaptations, and visible failures for missing or stale payload data.

Finished assets, traceable placements

The report links to the work; it does not replace the work.

Asset
Required deliverable and checks

Shopify article
Final title, body, summary/excerpt, blog selection, author, handle, SEO fields where supported, tags, hero image/alt text, sources, internal links, CTA, and intended visibility date. Check preview, mobile readability, links, and factual claims.

Photo content
Actual approved image files with channel-appropriate exports, dimensions/format checked against current requirements, alt text, asset rights/source, and product accuracy. AI imagery must not misrepresent real product features.

Video content
Actual playable video files, with channel-appropriate frame/length/format, readable captions or transcript, approved audio/rights, thumbnail if supported, and a clear hook/body/CTA. Check playback, audio, framing, and safe zones.

Social placements
Unique placement ID, channel/handle and ID, concept/angle, caption, CTA/link behavior, asset/version IDs, scheduled time with timezone, publishing mode, approval, provider ID, and final status.

Cycle report
Article/media/payload links; draft and live Blog Audit findings, fixes and exceptions; schedule matrix; approvals; IDs/states; errors/manual work; measurement plan and next decision.

Multiple times must mean meaningful variation

Do not send identical copy repeatedly. Change the hook, framing, teaching point, objection, demonstration, or CTA for each placement. Match the platform: a channel without clickable caption links needs a suitable link path; a video-only destination cannot receive a static image post. Reusing source material is welcome when the final treatment fits the audience.

Approved does not always mean published

Use explicit states: draft → in review → approved → scheduled → published, with failed / manual action required / deferred / cancelled where needed. Keep reminders distinct from scheduled direct posts. A sent response from a provider is evidence of provider status; verify a public permalink when available.

Protect against duplicate and partial execution

Before retrying, reconcile by the stored article/post ID and cycle placement ID. Do not create a duplicate after a timeout. If Shopify succeeds and one Buffer placement fails, preserve the success, flag the failed placement, and retry only that item. Changing the approved article, media, destination, or time materially requires an updated review record.

Sources and reference links

Reference snapshot from the supplied handoff, September 26, 2026. Verify current capabilities before execution. If a linked reference is unavailable, record the gap and ask for it when needed.

Final step · Module 04

Your module PDF

Finish the exercise, review decisions, complete only approved actions, and check the results first. Then save your final PDF here. This page stores it in this browser so you can download it again.

Already have the finished PDF?

Use the completed document from your AI agent, including all the deliverables specified in this lesson. It must reflect final results and deferred work.

Bring the complete results PDF

This module needs a substantive document with its full deliverables, tables, evidence and references. Ask your AI assistant to produce the complete PDF after review, then import it here.

Content Cycle Report. Include the complete deliverables and checks described in the lesson.

An imported PDF is learner-provided. Saving or checking it here does not verify account actions or connections.

No final PDF saved in this browser yet.

Next module05 / Daily Hustle A manageable daily rhythm grounded in real results.

Continue without saving a PDF?

You can upload your completed PDF to save it on this page in this browser and download it again later. No PDF is saved yet. Are you sure you want to continue to the next module?

Continue to next module →