<!--
  Template: purpose.md
  Owner: operator (adopt, populate, then remove this HTML comment)
  Purpose: structural skeleton for a content-publishing purpose / mission doc.
  Source: @stravica-ai/digital-operator-pa templates. See packages/engineering-pa/README.md.

  This doc is the top of the mission stack. Every subordinate rule
  (voice guide, banned tells, engagement guides) serves one of the
  anchor goals below, or gets cut. When a subordinate rule surfaces a
  hard case, the reader falls back to this doc for the tie-break.
-->

# Content-publishing purpose

**Status:** draft | in-review | live
**Last reviewed:** YYYY-MM-DD
**Owner:** operator name

## Mission

<!-- OPERATOR: replace with a one-line mission summary. Not a slogan —
the operator's honest statement of what content publishing is for.
Example shape: "Make it easy for people who care about <domain> to find
the operator's work, judge it, and act on it." -->

## Anchor goals

<!-- OPERATOR: replace with a numbered list of anchor goals. Every
subordinate rule serves one of these or gets cut. Four to seven anchors
is a healthy range — fewer and the mission is too abstract to
tie-break, more and the anchors overlap. Each anchor is one clause + one
sentence of what it means in practice.

1. <Anchor name>. <One-sentence expansion — what does this look like when
   it's working?>
2. <Anchor name>. <One-sentence expansion.>
3. <Anchor name>. <One-sentence expansion.>
4. <Anchor name>. <One-sentence expansion.>
-->

## What "success" looks like at scale

<!-- OPERATOR: replace with the north-star — what does the mission look
like when it's fully working? Not a metric. A picture. The kind of thing
that lets you tell whether a shipped piece of content moved the operator
towards the north star or sideways.

Example (Barry's operating instance): "Influencers writing their own
posts about the operator's work, without the operator prompting them.
The operator has become a reference point in the domain, not a self-
promoting voice."

Populate with the operator's own north star. -->

## Downstream consequences

<!-- OPERATOR: replace with the operational implications of the mission.
These are the "if the mission is X, then Y" statements that shape
day-to-day decisions.

Examples:
- Cold audience → the post links out to the newsletter, not to a specific
  concept page. First contact needs a low-commitment ramp.
- Warm audience → the post links to a specific concept page. Someone who
  already knows the operator's terminology can go deep.
- Guest posts on other properties → link back to the operator's own
  property, never to a paywall.

Populate with the consequences your mission actually implies. Cut any
that feel invented rather than derived. -->

## Scope fence

<!-- OPERATOR: replace with what this mission does NOT cover. Explicit
non-goals shorten future debates.

Examples:
- This mission does NOT cover paid ads. If the operator runs ads, they
  serve a different mission with different rules.
- This mission does NOT cover internal comms (Slack, email newsletters
  to existing customers). Those are relationship maintenance, not
  audience acquisition.
- This mission does NOT cover conference talks. Talks are a different
  surface with different economics.

Populate with the operator's actual non-goals. Better to over-fence at
the start than under-fence. -->

## Review + refresh cadence

<!-- OPERATOR: replace with the operator's review discipline. Template
default:

**Quarterly review**, or immediately after any of:

- A shift in the operator's business model (new product line, new
  audience, spun-off property).
- A shift in the platform landscape that materially changes the
  audience economics (an algorithm change that reshapes engagement,
  a new platform gaining traction, an old platform losing traction).
- A material miss on one of the anchor goals — if the mission says X
  and the shipped content is not producing X, the mission or the
  execution is wrong. Diagnose which before shipping the next batch.

Change this section only if the operator's review discipline differs. -->
