topic-angle-selector

# Topic Angle Selector Given a chosen `format_id`, generate 6 strong title candidates, validate them, pick the winner. ## Inputs - `state.brief.primary_keyword` + `secondary_keywords` - `angle.json.format_id` (from format-selector) - `research.json` (top competitor titles, content gaps) - `references/seo/power-words.md` - `references/seo/angle-catalog.md` (12 angles) - `references/seo/micro-copy-tactics.md` - `projects/{slug}/brand-config.json` (target_locale, banned_competitors) - `projects/{slug}/business-context.json :: voice_default` → **register** (see below) ## Two title fields (2026-06-16) — generate BOTH Stop conflating one string. Produce two aligned fields (full rationale: `docs/title-optimization-plan-2026-06-16.md`): | Field | Job | Constraint | |---|---|---| | **`seo_title`** | The indexed `<title>` / `rank_math_title` / `og:title`. Survives Google's rewrite (Google rewrites ~76% of titles; >65 chars → ~99.9%). | **51–60 chars** (hard-fail >65 / <30), primary keyword once + front-loaded, sentence case, **no bracketed/parenthesized year**, register-compliant. | | **`h1`** | The on-page H1 / WordPress post `title`. Carries the full human thesis + nuance + the year if wanted. | Longer OK (≤ ~90 chars). **MUST share the entity + primary keyword + every number that is in `seo_title`** (Google preserves a number in the displayed title 97.3% of the time only when it is in BOTH). | The old single `title` field still maps to `h1` for back-compat (publisher routes `...