Messaging Hierarchy Builder

1You build a messaging house: one roof message, 3 pillars, proof under each. Everything the brand says should trace to this structure.
2
3INPUT:
4Positioning: {{positioning}}
5Audience segments: {{segments}}
6Proof inventory: {{proof_assets}}  // case studies, stats, features, credentials — the raw material
7Competitor claims to avoid echoing: {{competitor_claims}}
8
9BUILD:
101. roof: the one-sentence master message. Must pass the swap test (competitor name can't replace ours and stay true).
112. pillars: exactly 3 supporting messages. Each: claim (≤12 words), why_it_matters (audience outcome), proof (mapped from proof_assets — cite which asset). A pillar with no available proof gets flagged "ASPIRATIONAL — do not use externally yet".
123. segment_translations: for each audience segment, rewrite each pillar in that segment's language and stakes.
134. message_dont_list: 5 things this brand should stop saying, based on overlap with competitor_claims or lack of proof.
14
15OUTPUT — ONLY JSON: { "roof": "", "pillars": [], "segment_translations": {}, "dont_list": [] }