---
name: share-in-44k-facebook-group
description: "Share a useful lesson in the right Facebook group. Follow its rules and check whether the post is live."
category: Content Factory — Post
stage: Post
definitive_article: https://localservicespotlight.com/article-guidelines/
status: complete
---

# Share in 44K Facebook group

A group post should give people something they can use. This guide helps you share a lesson from a real article. Start by checking the right group and its current posting rules.

**The path:** Correct group → Useful lesson → Submit and check → Replies and evidence.

**Use this when:** The distribution plan names a specific group and the checked article is ready for that audience.

## Inputs
- The exact group URL/ID and current rules. “44K” is the legacy task name, not a verified current member count or enough information to identify the group.
- The checked article, source facts, real media, and identities of any members to mention.
- The authorized posting identity, actual ability to post in the group, and the job’s message/publication scope.
- The distribution tracker, client-notification state when required by the plan, and a named person for comments and measurement.

## First-run prompt

> Use the exact group and article in the plan. Check group rules, posting identity and duplicate history. Share the useful lesson already authorized, then record whether it is pending or live. Keep replies and later measurements truthful; do not assume group size, reach, or boost eligibility.

## Steps
1. Open the exact group and read its current rules. Verify that the planned identity can post and that links, media, and this kind of content are allowed. Group membership does not guarantee immediate posting rights.
2. Read recent group posts and the tracker for duplicates. If the plan requires client notice first, verify that notification rather than assuming it from a checklist neighbor.
3. Write a short lesson: the problem, one supported detail, and what another member can do with it. Link the full article only when the current group rules allow that link. If links are barred, use a useful native lesson when it still meets the approved distribution goal; otherwise hold the post and name the rule conflict. Do not force a number into the post when the source has none.
4. Add a relevant real photo or clip if allowed and useful. Add accurate photo alt text or usable video captions where the group composer supports them; otherwise record the accessibility limit. Mention only confirmed featured members when appropriate. Keep media previews muted; no invented banner result or testimonial belongs in the post.
5. Submit when the job already authorizes posting. Read the resulting state: published, waiting for admin approval, rejected, or failed. Record the post/submission reference. Do not resubmit a pending item to force it through.
6. When live, confirm the text, link, identity, and media in the group. Restricted group content may require a member view; do not claim anonymous public access or general visibility.
7. Have the comment owner review legitimate questions within the agreed response plan. The source suggests a 24-hour review and a 48-hour measurement. Record actual dates and visible reactions/comments/shares; if a metric is unavailable, write UNKNOWN.
8. Save useful questions with their context in the [Topic Wheel](https://blitzmetrics.com/topic-wheel/) queue. Group response can inform a later Page-post test, but does not turn a group post into an eligible boost or prove business results.

## Definition of done (QA checklist)

- [ ] The exact group, rules, posting identity and allowed content are checked.
- [ ] The post teaches a source-backed point and includes working allowed links/media.
- [ ] Submitted, pending moderation and live states are kept separate.
- [ ] The tracker has the real reference and any pending owner/action; no duplicate submission was created.
- [ ] Later comment/metric work is either evidenced or explicitly pending, with no assumed engagement.

## Example(s)

**Fictional teaching example — no real group or post.** A sample community for shop owners receives this draft:

“A repair quote can be clear without pretending we know everything from a photo. Our sample method separates what we can see from what needs an in-person check. Here is the full walkthrough: `https://maplecycle.example/repair-quote/`. What part of a quote do your customers ask about most?”

If the group displays “Pending admin approval,” the tracker records that state and the submission time. It does not record “posted to 44,000 people.” Even a live post’s group size would not prove how many people saw it.

## Handoff and Content Factory context

The comment owner receives the group reference and source facts. [Final formatting and QA checks](https://local-service-spotlight.github.io/task-library/?task=step-17-final-formatting-and-qa-checks#task-step-17-final-formatting-and-qa-checks) receives the actual distribution state, including pending moderation. The promotion owner receives only measured evidence later.

This task serves **Post** in the [Content Factory](https://blitzmetrics.com/content-factory/). Produce supplies the source, Process prepares it, Post places and checks it on the agreed channels, and Promote distributes proven work under its own scope. The task’s actual handoff above defines the next step; list order alone does not create a prerequisite.

## When this runs

One group submission per agreed article. The proposed 24-hour reply review and 48-hour metric check need a real named owner or configured authorized timer; there is no automatic recurring posting job.

## First-run setup and continuity

Use the exact account, source, destination and authority recorded for the job. Carry out publication, messages or repairs already authorized once their required checks pass; do not ask for the same approval again. If an action is outside that scope, finish the authorized work and state the specific remaining need. A login, plugin, or task file does not itself grant new authority.

Keep the latest state, record IDs, revisions and next owner in the project tracker or files. Before a retry, check the current saved/sent/published item to avoid duplicates or overwriting another edit. A model has no guaranteed memory, scheduler or account access just because it is called persistent. A future check needs a configured timer or a named person.

Keep all agent media previews muted with volume zero before playback. If this cannot be verified, use captions, metadata or still frames and state what was not tested. No first-load autoplay is part of these page instructions.

## Write up the real run

For each actual attempt, [write its meta article](https://blitzmetrics.com/meta-article-prompt/) with this exact task, source revision, trigger, work, decisions, evidence, result and next owner. Failed, partial and blocked attempts still get a written record. A private draft is a valid writing outcome; public publication follows the existing scope.

Keep one stable execution ID for the actual task run. Retries, checks and changed artifacts do not add runs. A separately scoped child task may have its own ID linked to its parent; writing the parent’s meta record is part of that same run. The [recipe and meta-article guide](https://localservicespotlight.com/meta-articles/) explains the distinction. Teaching examples below or above are not execution evidence and must not enter the run count.


<!-- factory-layer:start -->

## Factory chain (do not treat this as isolated)

- **Phase:** Post
- **Importance:** 4/5 `●●●●○` — frequency 4, revenue 4, gating 2 (runs every factory cycle or weekly; creates the asset ads amplify)
- **Suggested previous station:** `post-to-linkedin`
- **Suggested next station:** `email-and-dm-client-about-published-article`
These stations are generated neighbors, not verified prerequisites or handoffs. Follow the task’s actual Inputs and Handoff sections.
- **Handoff:** Draft URL or WP post ID, slug, author user ID, featured-image media ID. Promote reads the live URL, not the draft.

## Model routing (same factory, any engine)

- **This task's lane:** `any` — Any capable chat model (Claude, ChatGPT, Grok, Gemini). SOP following, drafts, checklists.
- **Single-engine path:** Use the capable AI app you already have. Check its required tools and access before starting. Pass the actual result and proof to the next task.
- **Optional multi-engine:** A tested local model may draft; a stronger model may review facts and voice. Use supported tools for approved actions. Pick models from observed quality and cost; a model name does not prove it can run this task.
- **Never** store the working state in one vendor's memory. Files in the Content Library are the bridge.

<!-- factory-layer:end -->
## Definitive article & links

- Canonical article: https://localservicespotlight.com/article-guidelines/
- Exact Task Library record: [Share in 44K Facebook group](https://local-service-spotlight.github.io/task-library/?task=share-in-44k-facebook-group#task-share-in-44k-facebook-group)
- Working writing standard: [Article Guidelines](https://localservicespotlight.com/article-guidelines/)
- [Meta’s group participation and approval rules](https://www.facebook.com/help/1414053028933409/)

## Review and evidence still needed

The original contributor status in the header is preserved. It does not certify this proposed rewrite or prove that this account, publication, message, player or check has run. Every worked teaching example is explicitly invented; replace it with actual evidence when documenting a real execution.
- The canonical source does not provide a verified current group ID. The project must supply it before an actual post.