audience-analyze-search

Analyze a market from a brief

Purpose

audience-analyze-search is the way into the read for a user who arrives with a brief, not signals — "who's in the market for roofing near Nashville", "profile this audience". It discovers the signals behind the brief, organizes them into three pools, lets the operator steer which signals land in which pool, materializes the audience, and hands it to the shared read. Size is an output, never a target — there's no band and no strategy procedure; the headcount is whatever the composed signals land at.

This is a delta over audience-analyze: the unique work here is getting from a brief to a built signal stack; once that stack exists, the read and the shareable report are the parent's shared procedure (audience-analyze → The read & report), composed with verbatim — not restated.

Works with

• Called by: the audience-analyze router, when the user brought a brief and no signals.
• Runs inline (the same discovery and scoring explore uses, here feeding a built-and-read audience):
  • signal discovery — one concept per beat: a pool's concept (in the user's phrasing, tagged with its role) → validated candidate signals with evidence (context/discovery.md).
  • signal scoring — the gathered signals scored against the model (relevance · freshness · rarity/specificity · breadth/size · coverage), grounded on the brief, so the operator can see how each stacks up and curate — traits-only, never a set of people (context/scoring.md).
  • adjacencies (optional, at a pivot checkpoint) — adjacent concepts / unprobed domains worth adding to a pool (context/adjacencies.md).
• Runs the read inline — the profiling procedure (context/profiling.md) in mode A (the built stack) → the two-section read; the parent's shared read, run inline on the main thread.

Language

Inherits the parent's table (signals / must-haves / exclusions; lift explained once; sample named). Internally the three pools map to the boolean shape — defining → OR (core), must-have → AND (must_have), exclusion → AND_NOT (exclusion) — but the operator only ever sees defining signals, must-haves, exclusions. No AND/OR/NOT, no boolean-"pools" jargon at the surface (signal pool, the kept-signals carrier, is the user's word and fine).