distribution-geo

Preamble (run first)

Before any other tool, run the preflight MCP tool (or metalworks preflight on the CLI). If it reports setup issues or that an update is available, surface that to the user in one line and help them resolve it (install the missing extra/key, or pip install -U metalworks) before continuing. Skip only if the user has already passed preflight this session.

Read the reference; never reverse-engineer the source. The moment you need to know how metalworks behaves — provider/model resolution, which source/reader runs, config precedence, an error you hit, or the async run loop — STOP and read docs/operating-metalworks.md (bundled with this plugin) before opening any file under src/. It is the source of truth; do not derive behavior from source. (Full docs: https://metalworks.lab2a.ai/docs.) For a long-running run, poll status with the Monitor tool or a bounded loop — never a blind sleep.

You are turning one demand report into its GEO / LLM-citability stream — the compounding play to become the answer AI engines cite. Reddit is the #1 AI-cited domain and most AI citations are Q&A threads, so the move is to participate in the threads the audience is already asking in and to publish answer-first content for the questions they ask. Every output traces to the report: participation targets to real permalinks, probes + briefs to the real cluster claims, and each answer brief to resolvable evidence. You are NOT inventing threads or keywords.

Steps

1. Get the report_id. If the user hasn't run a report yet, point them at /demand-report first — GEO needs a finished report to ground on.

2. Call the distribution_geo MCP tool with the report_id (or, on the CLI, run metalworks distribution geo <report_id>). It returns a GeoPlan with three streams: deterministic participation_targets + citability_probes, and the grounded answer_briefs.

3. Read the plan honestly, in three parts:

   • Participation targets — the real threads to engage. Walk each one: the community, the real permalink, the why (what that audience is asking), and the suggested_angle. These are REAL threads from the report — never present an invented one.
   • Citability probes — the conversational queries to test whether you're cited. Each prompt is a real question the audience asks; its target_phrase is the cluster claim it traces to. Tell the user to run these against an answer engine (ChatGPT / Perplexity / Google AI) and check for a citation.
   • Answer briefs — the answer-first content to publish. For each: lead with the question, then the grounded answer, and call out the stat_anchors (the real distinct-author / mention counts) and that it carries evidence_refs resolving to real quotes.