{
    "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": "Risk Management, Regulatory \u0026 Legal Activities",
    "number": "X.2.6",
    "category": "MGMT",
    "phase_number": 2,
    "phase_name": "Development",
    "collaborator": "MPX",
    "template_version": 1,
    "ai_meta_updated": "2026-10-15",
    "canonical_url": "https://mpaxmarketing.com/system/risk-management-regulatory-legal-activities/",
    "template_copy_url": "https://docs.google.com/document/d/1m8LE_p4feVtTHqxszvsr-4d1wyfzpM6FsrkxgH5jUYM/copy",
    "body_format": "markdown",
    "body": "# X-2-6 AI Meta\n\nThis tab contains guidance for Sage_AI when helping a product owner complete the Risk Management, Regulatory \u0026 Legal Activities Growth Factor.\n\n## Template Context\n\nThis is [product_number].2.6 MGMT Risk Management, Regulatory \u0026 Legal Activities, a Growth Factor in Phase 2 Development. It is the execution record for [product_number].1.6 MGMT Risk Management, Regulatory \u0026 Legal Plan.\n\nThe relationship between the two documents is the whole point of this Growth Factor. The plan is the current state. It says what must be handled, rates each risk, and states the response. This document is the history. It says what was done, when, by what means, and with what result.\n\nThe plan is edited as understanding changes. This document is only ever appended to. An activity that turned out to be unnecessary is marked Retired rather than deleted, so the decision stays visible.\n\n## Required Inputs\n\nPlanning documents:\n- [product_shortcode] [product_number].1.6 MGMT Risk Management, Regulatory \u0026 Legal Plan, required. This is the parent and the source of every activity.\n- [product_shortcode] [product_number].1.5 DEV Development Plan, required. It sets the version sequence that obligations are timed against.\n- [product_shortcode] [product_number].1.7 Alpha User Recruitment, where an alpha panel exists. It carries the consent and agreement obligations.\n\nDevelopment documents:\n- [product_shortcode] [product_number].2.2 DEV Technical Specification, for security, access control, and data handling as actually built.\n\n## Global Variable Replacements\n\nWalk the product owner through replacing variables using Google Docs find and replace.\n\nStandard variables:\n- [company_name], full legal company name\n- [product_shortcode], 2 to 4 character product abbreviation, used in prose instead of the product\n- [product_name], full product name\n- [product_number], numeric product identifier\n- [document_origination_date], date the document was first created\n- [document_version_date], date of the most recent major revision\n\nGuidance fields get replaced with real content as you work through each section.\n\n## Section by Section Workflow\n\n### Overview and Goals\n\nHelp the product owner edit the variables. The prose stands as written for most products. Change it only where the plan and activities relationship works differently for this product.\n\n### How This Document Works\n\nThis section is standard template text. Do not rewrite it per product. The three subsections state the split, the entry rules, and the loop for changing the plan. Changing them per product defeats the purpose of having a convention.\n\nThe one thing to confirm is the plan change loop. It assumes the plan carries a Pending Updates tab. If this product does not use that pattern, adjust the last subsection to describe what it does use.\n\n### Activities\n\nThis is the whole document. Everything above it is orientation.\n\nBuild the list out in full before any activity is worked. The value of this document comes from a reader being able to see the entire obligation at once, which means a half-built list is worse than no list.\n\nThe method for building it:\n- Walk the tactical plan in the parent, group by group. Every obligation becomes an activity.\n- Walk the risk register. Add an activity for any risk whose mitigation is work rather than a standing posture. A risk mitigated by an ongoing practice, such as one owner per table, does not need its own activity. A risk mitigated by a discrete piece of work, such as a restore test, does.\n- Walk the legal documentation framework. Each required document is an activity, or is grouped with the documents it is drafted and reviewed alongside.\n- Add an activity for each version boundary review and each phase review the plan schedules.\n- Add anything already done that discharges a plan obligation, even if it happened before this document existed.\n\nThen order the whole set. Priority and logical sequence, not category and not version. Completed work sits at the top because it came first. An item that can change the sequence of other items, such as confirming a vendor commitment term, sits early even when it is small.\n\nFormat:\n- Activity name as an H2, named the way it would be said out loud rather than after its risk number.\n- Status, Source, description, optional details, then Actions.\n- Status carries one word and one date. Open, Done, or Retired.\n- Each action line begins with the same three words.\n- Evidence is named inline on the action that produced it, with its location. Do not build a separate evidence index. An index is a second thing to maintain and it goes stale.\n\nWhat belongs in an activity that is not in the plan:\n- Defects found during execution that touch security, access control, or data handling.\n- Decisions taken under time pressure, and what they cost.\n- Anything the plan did not anticipate.\n\nThis is what makes the document a record rather than a checklist. A product owner will resist writing these down. Prompt for them directly at each review.\n\nClosing a risk:\n- An activity that closes a risk says how it was closed.\n- Distinguish a risk closed by mitigation from a risk closed because the work carrying it was removed from the plan. These are different outcomes and only one of them means the exposure was handled.\n- The closed rating goes into the plan. The reason stays here.\n\n### Reviews\n\nA version boundary review or a phase review is an activity like any other. It carries a status, a date, and actions.\n\nA review does three things. It re-rates each risk. It closes what is no longer live. It adds what the last version created.\n\nThe re-rating decisions and their reasoning go in the details of the review activity. The resulting ratings go into the plan. Guide the owner through both halves, because the second half is the one that gets skipped.\n\n## Wrapup\n\nWhen the activity list is built out:\n\n1. Save the document in the product folder.\n2. Copy the document link.\n3. Set the project status in the header. In Progress while activities are open, Active once the phase obligations are met and the document is signed. This Growth Factor is rarely Complete before the phase review, because obligations keep arriving.\n4. Add the document to Sage_AI project knowledge or to the document index.\n\nThis Growth Factor is met when every obligation in the parent plan has an activity here, every activity has a status, and every closed risk in the parent has a findable reason in this document."
}

Growth Factor page M-PaX home