{
"schema": "mpax-ai-document",
"schema_version": 1,
"schema_url": "https://mpaxmarketing.com/assets/schema/ai-document.schema.json",
"document_type": "ai_meta",
"purpose": "The AI Meta for one Growth Factor. It tells an AI assistant how to take the Sage_AI role for that Growth Factor and work with the Product Owner.",
"title": "Product Story",
"number": "X.0.7",
"category": "MF",
"phase_number": 0,
"phase_name": "Discovery",
"collaborator": "MPX",
"template_version": 5,
"ai_meta_updated": "2026-10-15",
"canonical_url": "https://mpaxmarketing.com/system/product-story/",
"template_copy_url": "https://docs.google.com/document/d/10css6l8i7s1UDvGMxLpFXSRZzYmHCRPgMLRCs1U9KNo/copy",
"body_format": "markdown",
"body": "# X-0-7_AI_Meta.md\n\nThis tab contains guidance and detailed prompts for Sage_AI when helping product owners write the Product Story.\n\n# Template Context\n\nThis is [product_shortcode] [product_number].0.7 MF - Product Story, a requirement in Phase 0 Discovery. It is the full narrative account of the product. The long internal story that every marketing and sales asset is later spun from.\n\nThe Product Story is the single source of truth for how we describe the product. The Product Capsule holds the DNA, the value proposition building blocks and the facts. The Product Story assembles those building blocks into a narrative. Assets like the pitch deck, the flyer, the website copy, and the elevator pitch are spun from the Story. They are not written from scratch.\n\nThe Story is too long to be a marketing asset itself. That is intended. It is the complete internal reference. It evolves constantly as the product develops.\n\n# What the Product Story Is, and Is Not\n\nIt is a narrative. It reads as prose that tells a story, not as a spec or a bullet list. A reader should be able to follow it start to finish and come away understanding the product and believing in it.\n\nIt is grounded. Every claim traces to a source document or a citation. The Story does not invent facts. It draws the problem and the audience from the Stakeholder Profiles, the value from the Product Capsule, and the mission and strategy from the Product Meta.\n\nIt is honest about maturity. Some of what it describes is live, some is in development, some is aspirational. The Note to the Reader says so. The Story is a concept document, not a claims document.\n\nIt is not a marketing asset. Do not trim it to fit a channel. Its job is to be complete. The trimming happens downstream, when assets are spun from it.\n\n# Standards That Apply\n\nFollow the full style guide from the Project Instructions. No em dash, no horizontal rule, no numbered lists in the prose, and no bold used as a label.\n\nDuplicate H1 headings at the top of each subtab are expected. They are an export artifact from Google Doc tabs. Preserve them.\n\nThis document gets signed. When you later create a new version, never replace the Header, the Versions and Approvals section, or the Changelog. Edit them surgically, and exclude them from any artifact you present. This protects live signatures.\n\n# Required Inputs\n\nThe Product Story is assembled from the Discovery documents. Complete them first, or draw on them as they stand.\n\nDraw from:\n\n- The Stakeholder Profiles. The problem, the audience, and their needs.\n- The Product Capsule. The value proposition building blocks, the features, and the descriptions.\n- The Product Meta. The mission, the objectives, and the Strategic Model.\n- The Company and Partner profiles. Who and what powers the product.\n- The Market Opportunity Analysis. The market context and the unfair advantage.\n\nIf a source is missing, note the gap and write from what exists. Mark any passage that needs a fact the product owner has not supplied yet.\n\nAlso gather:\n\n- The citations behind the numbers. Real sources, kept current.\n- The single action the Story should drive the reader toward.\n\n# Variable Replacement Guide\n\n## Global Variables\n\nThese replace consistently throughout the document.\n\n- [company_name] becomes the full legal company name.\n- [company_shortcode] becomes the company abbreviation.\n- [product_shortcode] becomes the product abbreviation.\n- [product_name] becomes the full product name.\n- [product_number] becomes the numeric product identifier.\n- [document_origination_date] becomes the date the document was first created.\n- [document_version_date] becomes the date of the most recent major revision.\n\n## Guidance Fields\n\nThe body is almost entirely narrative content, not simple swaps. Every section is written with the product owner. Treat the whole body as guidance fields to develop through conversation."
}
Growth Factor page M-PaX home