---
name: map-why-ring-core-purpose
description: "Use real stories to show why people trust your work."
category: Strategy & Measurement
stage: —
definitive_article: /topic-wheel
status: complete
---

# Map WHY stories in the outer ring

Use real stories to show why people trust your work. This guide adds the people and moments that support each topic on your map. Start with real jobs, shared work and stories you have the right to use.

**The path:** Real story → Relevant HOW → WHAT offer → Content brief

**Start when:** The WHAT and HOW are mapped and the Topic Wheel needs real supporting people and stories.

## Inputs

- [The checked WHAT offer](https://local-service-spotlight.github.io/task-library/?task=map-what-ring-specific-content#task-map-what-ring-specific-content) and [HOW topics](https://local-service-spotlight.github.io/task-library/?task=map-how-ring-methods#task-map-how-ring-methods).
- Real interviews, jobs, reviews, events and collaborations with dated sources and use rights.
- [Topic Wheel, the map of your offer, topics and real stories](https://blitzmetrics.com/topic-wheel/) and current story assets in the content library.

## Steps

1. Place WHY in the outer ring. It contains real people, stories and collaborations that connect to a HOW topic and the WHAT offer. Personal purpose can inform a story, but the maintained wheel does not place a mission statement in its center.
2. Inventory moments that show the work: a customer problem and outcome, a learned lesson, a shared project or an event. Record the people’s real roles and the exact source.
3. Verify what each source proves. A shared photo proves that moment, not a business partnership, endorsement or result. Get the permission required for any private customer story before public use.
4. Connect each supported story to the relevant HOW topic and WHAT. Leave unsupported claims or unrelated famous names out; reputation is not created by drawing a line.
5. Write a short story prompt: who, what happened, useful lesson and source evidence. Label a proposed interview as a plan until it is actually recorded.
6. Save the WHY ring with source links, permission state and missing evidence. Keep the mission consistent with the goals brief while preserving the distinction between a WHY video and the wheel’s full outer story ring.

## Definition of done (QA checklist)

Quality assurance (QA) means checking the result against its agreed requirements; see the [Article Guidelines](https://localservicespotlight.com/article-guidelines/).

- [ ] WHY is the outer ring of relevant, supported people and stories.
- [ ] Every claimed relationship or result is scoped to its actual proof.
- [ ] Recording prompts and rights gaps are clear enough for the next owner.

## Example(s)

**Fictional teaching example. This is not a client result or proof of a completed run.**

A fictional roofer has a homeowner’s approved story about a repaired leak and a photo from a trade event. The repair story supports its leak-diagnosis topic. The event photo supports attendance only; it does not prove the speaker endorsed the roofer. Both claims stay as narrow as their sources.

## Handoff and Content Factory context

[Plan the next recording session](https://local-service-spotlight.github.io/task-library/?task=use-for-content-planning-and-video-topics#task-use-for-content-planning-and-video-topics) receives the story prompts and source rights; the goals task receives any supported purpose clarification.

This work supports Produce in the [Content Factory: Produce, Process, Post and Promote](https://blitzmetrics.com/content-factory/). The selected sources pass to Process, approved outputs go to Post, and useful proven work can enter Promote. The real inputs and handoff above set this task’s scope.

## Start with an agent

Give the AI worker this recipe, the real Inputs, the desired result and the actions already authorized. Ask for the saved output, source evidence, passed and failed checks, and the next owner. A skill is a set of instructions. Loading it does not prove access, install a scheduled job or complete the work. Use the [current installation guide](https://localservicespotlight.com/install/) only if reusable setup is needed; a ZIP contains instructions and is not an access grant.

Use the actual supported app and verified source access. A model name is not a promise of browser control, memory or unattended work. For recurring work, inspect the real job’s trigger, owner, timezone and observed firing; this recipe creates no schedule. Before any media playback, mute the player and set volume to zero. A silent review does not prove sound was heard.

## Record the real execution

Open the run record when work begins. Keep one execution ID, the exact starting recipe revision, input sources and actual state. Write a [meta article, the record of one real execution](https://blitzmetrics.com/meta-article-prompt/) with results, checks, failures and next owner. Link it to this task in the [Task Library](https://local-service-spotlight.github.io/task-library/). Writing is required; public release follows existing authority.

Reuse the same execution ID for internal reviews, meta writing, revisions and retries. A blocked run stays open with its dependency and owner, without an invented finish time. Keep historical public examples as dated evidence; article counts alone are not verified execution frequency. Use supported findings to propose and verify a recipe improvement.


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

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

- **Phase:** —
- **Importance:** 3/5 `●●●○○` — frequency 3, revenue 3, gating 2 (supporting)
- **Suggested previous station:** —
- **Suggested next station:** —
These stations are generated neighbors, not verified prerequisites or handoffs. Follow the task’s actual Inputs and Handoff sections.
- **Handoff:** Save this task’s actual output, source, date and checks where the receiving owner can read them. Follow the Inputs and Handoff sections for its next step.

## 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

- [Maintained source guide](https://blitzmetrics.com/topic-wheel/)
- [This task in the Task Library](https://local-service-spotlight.github.io/task-library/?task=map-why-ring-core-purpose#task-map-why-ring-core-purpose)
- [Article Guidelines](https://localservicespotlight.com/article-guidelines/)
- [Definitive article and task recipe standard](https://blitzmetrics.com/definitive-article-guide/)
- [How recipes and run records work together](https://localservicespotlight.com/meta-articles/)

## Review and evidence still needed

The inherited contributor status is `complete`. It is preserved, not promoted by this rewrite. That label alone does not verify document readiness, account access, an actual execution or a client outcome.

A relevant real execution, source evidence, independent reviewer and accepted handoff remain to be recorded. The fictional example teaches the method and does not fill a real-run evidence gap. The opening and full method need a named semantic reviewer; the task-specific path is source guidance, with visible desktop/mobile presentation still to check.