This hub gathers how the pitch and fundraising materials get reframed per audience. The structural spine is that [every sentence reads from the prospect's experience] (Narrative_ProspectPerspective), stripping git/MCP/RDF/architecture so one pitch works across elevator, deck, and demo. From there the children fan into concrete audience maps: a [four-frame resonance map] (Obs_AudienceMapping) (enterprise governance, Series A CEO autonomy, ops-lead trust, technical-leader accountability), and a dated [two-document fundraising split] (Narrative_TwoAudienceDocumentStrategy) (Mar 13) separating plain-language F&F from technically-fluent VC/angel, with a collaborator as the F&F readability test. A distribution-channel wrinkle arrives Mar 17: [Tony's white-paper AI-filter observation] (Obs_WhitePaperAIFilter) — executives now triage long documents through Claude rather than reading them. Two further entries sit at the style layer rather than the narrative layer: an [explicit vision-CEO vs ops/technical bifurcation] (StyleObs_AudienceSegmentation) and a [three-camp reviewer taxonomy] (StyleObs_CampStructure). Together they describe audience-dependent messaging across prospects, funders, and reviewers — not a single resolved frame.
Witness phrases
verbatim Every sentence is written from the prospect's experience, not the product's architecture
verbatim If he can't understand it, it's not direct enough.
verbatim Enterprise buyer (governance), Series A CEO (contractor autonomy), Ops lead (trust), Technical leader (accountability via citations and review).
verbatim I'm literally going to put it into Claude and say give me a summary of that, tell me if I should read that or not.
verbatim Strip-all-jargon principle vs. the VC/angel doc that deliberately 'keeps industry language' — the prospect-perspective rule reverses by audience.
verbatim The white-paper AI-filter cuts against crafting prose for a human reader at all — the real audience may be the executive's summarizer, not the executive.
verbatim Two children (attached as 'related', not 'broader') are reviewer/decision framing, not prospect framing — the camp taxonomy is about structuring disagreement, an outlier to the audience-resonance mainline.
verbatim Audience cuts differ across children: four-frame buyer map vs. a binary vision-CEO/ops split vs. F&F-vs-VC — no single canonical segmentation.
In this area
Narrative_ProspectPerspective Every sentence is written from the prospect's experience, not the product's architecture
ObservationObs_AudienceMapping Four distinct audience resonance frames: Enterprise buyer (governance), Series A CEO (contractor autonomy), Ops lead (trust), Technical leader (accountability via citations and review).
ObservationObs_WhitePaperAIFilter Tony's articulation of the white paper AI filter problem — executives will summarize with AI rather than read.
StyleObservationStyleObs_AudienceSegmentation Explicit audience bifurcation: 'vision-oriented CEOs' vs 'ops leads and technical buyers'. Signals audience-dependent messaging strategy. Structural segmentation marker.
2 further nodes are not published in the public projection. Each node links from the entity index.