audience-generate-search

Build an audience from a description

Purpose

audience-generate-search is the build leaf anchored on a plain-English description — the user arrives with who they want to reach, not an owned list. It runs the parent's shared discovery and scoring, then composes — or partitions — the approved working set into a measured result.

The leaf is split from its sibling by input anchor (description here; an owned list is audience-generate-list), and inside it the objective picks the strategy. Two output families ship today:

• A signal stack — the boolean shape of one audience and its measured reach. The landing mode picks the compose strategy: a size band composed with greedy (signals added one at a time, reach measured after every step, until the audience lands inside the band), maximum credible reach composed with broad (the core ORed into a wide pool, dead-weight skipped, lightly gated, the union flagged when it swells toward the whole universe), or precision composed with lift (from the scored pool, the signals with the most lift over a must-have base are picked, for the highest-propensity audience).
• A roster — an entity set with classification, from a Classify strategy. The grouping objective ("where do they cluster", event/site-selection) partitions the brief's people into the best-concentrated groups with group (disjoint cells across one or more axes; entity IDs + group label + score inputs). The crossing objective (a lead list of in-market companies, employees of these firms) composes a seed audience and crosses the employment graph to the related entities — employers of these people, or employees of these companies — then keeps those that pass a target-side filter with traverse (the qualified set: entity IDs + source provenance, membership only — ranking or segmenting that set is a separate strategy). Both return a roster with an ID-only roster_uri.

This is a delta over audience-generate: the unique work here is the objective, the strategy that hits it, and — for the roster objectives — the partition (grouping) or the graph crossing (crossing) that the stack objectives don't have. Discovery, scoring, the working-set record, the pivot loop, and the landing are the parent's shared spine (audience-generate → The shared spine), composed with verbatim — not restated. The inputs are the audience description and the objective's target (a band for greedy; no target for broad; a must-have base + output mode for lift; the grouping dimension for group; the crossing direction + optional target filter for traverse); an /watt:explore signal pool — or a lookalike signal pool from audience-generate-list — carries in as a pre-seeded working set, discovery skipped for the angles it covers.