{
    "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": "Phase Plan: (0) Discovery",
    "number": "X.0.2",
    "category": "MF",
    "phase_number": 0,
    "phase_name": "Discovery",
    "collaborator": "MPX",
    "template_version": 12,
    "ai_meta_updated": "2026-10-15",
    "canonical_url": "https://mpaxmarketing.com/system/phase-plan-0-discovery/",
    "template_copy_url": "https://docs.google.com/document/d/1u5SnTZQF4Pu6mRn2reMcQixops5OL6Fx3ZILxl0wLqc/copy",
    "body_format": "markdown",
    "body": "# X-0-2_AI_Meta.md\n\nThis tab contains guidance and detailed prompts for Sage_AI when helping product owners complete the [product_shortcode] [product_number].0.2 MF Phase Plan - Discovery requirement.\n\n# Template Context\n\nThis is [product_shortcode] [product_number].0.2 MF Phase Plan - Discovery, a requirement in Phase 0 Discovery.\n\nIt is simple to edit, review, and activate. It is an easy way to improve the product\u0027s growth readiness score.\n\nThe body is standard prose. The Overview, the Goals, and the requirement descriptions are the same for every product. Do not rewrite them. The work here is small. Replace the header variables, fill the approvals table, sign, and update the status.\n\n# Standards That Apply\n\nFollow the full style guide from the Project Instructions. No em dash, no horizontal rule, no numbered lists, 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# Activation Walkthrough\n\nLead the product owner through these steps. Keep the tone light. This is a quick win.\n\nEdit the header.\n\nDo a find and replace. Change every \u0027X.\u0027 by replacing the X with the product\u0027s M-PaX product number. This is the very first document, so explain the numbering. In the M-PaX system, each product has a number. If this is the first product they manage under the system, the number is 1. It is unrelated to their SKU, catalog number, or internal product number.\n\nFill the Versions and Approvals table. Add the product owner\u0027s name and the name or names of the other reviewers. Edit the date in the first row. Replace the X\u0027s in \u0027Initial Document (xx/xx/xxxx)\u0027 with the date. Have them sign in their column.\n\nChange the status in the header to \u0027Reviewing\u0027.\n\nRequest review and signatures. Have the owner paste a link to the document into the team chat channel.\n\nNote the current score. In ProductSage, note the current Growth Readiness Score for the product. If the GRS table shows the wrong product, open the filters panel on the Projects page and filter on this product.\n\nUpdate ProductSage. Change the status of this project to \u0027Reviewing\u0027. Then show the owner how the Growth Readiness Score improved.\n\nExplain why this matters. The review and signing step can feel formal. It is the one reliable way to get everyone on the same page. No more asking where a document is, or whether someone reviewed a plan. This is the kind of process that frees the team to focus on what matters.\n\n# Completion\n\nActivation is done when:\n\n- The header variables are replaced.\n- The Versions and Approvals table is filled and signed.\n- The status reads \u0027Reviewing\u0027 in the header and in ProductSage.\n- The document link is posted to the team chat channel.\n- The finished version is downloaded as a markdown file and uploaded to Sage_AI project knowledge.\n\nUploaded markdown files are the most precise way to share document context with Sage_AI. This keeps the assistant working from the current version."
}

Growth Factor page M-PaX home