Lexicon
The M-PaX Lexicon defines the vocabulary of the System, including the Growth Factor category codes.
Commercial Motion
The living system that carries a product from concept into growth. It supplies the foundation, the vehicle, the engine, and the fuel.
Content Property
One channel and format that content is published through, with its own steps, templates, and schedule. The LinkedIn feed of a Product Owner is one Content Property.
Content Properties are named in X.3.6 Content Foundation. ProductSage groups posts by property in the Content Pipeline, and each property has a code, such as CF_LI_Post.
DEV
Product Development. The Growth Factor category that contains all of the Product Development Factors.
Escape Velocity
The transition from the Launch phase to the Growth phase.
Global
Applies to every Product Owner and every product, and is kept once for all of them. The system context Sage_AI reads at the start of every session is global.
The opposite of Localized.
Growth Factor
One of the 37 universal factors that determine whether a product reaches sustainable growth. It is the core unit of the M-PaX System.
Growth Readiness
The condition the 37 Growth Factors produce. A product is growth-ready when it can be found, understood, and believed without the founder in the room.
A product can be excellent and not growth-ready. That distinction is what the M-PaX System exists to close.
Growth Readiness Score
A ProductSage measure of how completely the Growth Factors have been implemented and how close a product is to entering the Growth phase.
Knowledge Base
The curated article library that gives depth and how-to guidance behind each Growth Factor. It is part of the M-PaX System, not a separate product.
Localized
Specific to one product or one Product Owner. The Product Meta is localized. The Project Instructions stub is not, because it is the same for every Product Owner, and only its optional Product Meta folder ID slot is the Product Owner's own. Where a localized rule conflicts with a global one, the localized one wins.
M-PaX Services
The team. People on demand for the commercial roles a small company cannot afford to hire. They join the founder's own team rather than working as an outside agency.
Billed hourly against a not-to-exceed scope, and structured as the Commercial 8 protocol.
M-PaX System
The operating system for Commercial Motion. 37 Growth Factors across the four pre-growth phases of the product journey.
MF
Marketing Foundation. The Growth Factor category that contains all of the Marketing Foundation Factors.
MGMT
Management. The Growth Factor category that contains all of the Management Factors.
Mission
A unit of work with Sage_AI. One chat is one mission, and each mission has one job. Sage_AI loads the instructions for that job when the mission starts. A large piece of work is completed across as many missions as it takes, because a mission is sized to what fits one conversation.
Mission Sequence
The four steps every mission follows. Plan, by collaborating in chat and updating the planning documents. Specify, by updating the specification documents. Execute, by implementing, then updating the plans and specifications to match what happened. Transition, by closing the mission and setting up the next one.
Mission Transition
The last step of the Mission Sequence. It closes one piece of work and sets up the next. Things change fast during a mission, and what was learned has to be captured while it is fresh or it is lost.
Closing means logging what happened and updating the plans. Setting up means answering what can already be answered and writing the brief for the next mission. The point of doing both well is that the Product Owner spends the least time and effort getting the product growth-ready, because nothing has to be rediscovered.
PE
Promotional Execution. The Growth Factor category that contains all of promotional activity including lead generation, outreach, engagement, and direct selling.
Phase
One of the five stages of the product journey. Discovery, Planning, Development, Launch, and Growth.
PI
Promotional Infrastructure. The Growth Factor category that contains all of the Promotional Infrastructure Factors.
Product History File
The Google Drive folder structure that holds every document a product produces, with a folder for each of the four phases that produce documents. Often shortened to PHF.
Product Owner
The person accountable for what a product becomes. It includes everyone working on the product on behalf of the founder, so a marketing assistant completing a Growth Factor is a product owner too.
Not a user. Someone using a tool is a user. Someone accountable for an outcome is an owner, and the difference matters to them.
This is not the Agile role of the same name, which owns a development backlog on a delivery team.
Product Zenith
The point at which a product reaches its highest value. The Product Owner states that value in their own terms, such as an exit of a given size or a given monthly recurring revenue. It is first set in the Market Opportunity Analysis and keeps evolving.
Nobody knows a product has reached its zenith until it starts to tail off. Until then, the growth curve points toward it.
ProductSage
The software product that runs the M-PaX System. It has a free tier and paid tiers. The method works without it. ProductSage makes the same work easier and faster.
Sage_AI
The M-PaX product management assistant. It drafts the documentation for a Growth Factor alongside the person completing it. The _AI suffix is a naming rule and a disclosure, so a reader can tell from the name alone that they are dealing with software. Interactive, not autonomous. The person completing the Factor drives and makes the decisions.
Sage_AI 3.0
The system as a Product Owner installs it now. A fixed Project Instructions stub that clones the public repository, the system context and the AI Meta in that repository, the Product Meta and the Advisory Board as dated Markdown files in the Product Owner's Drive folder, the Docs and Sheets plugins, and installed Sage_AI Skills. Running it requires Claude Pro or above.
Sage_AI 3.0 is the name of the whole install. The specification versions and the template versions still carry their own changes.
Sage_AI Context
Everything Sage_AI needs to do its job. The instructions, references, documents, and files that tell Sage_AI the method and the product. Some is loaded at the start of every mission, and some is used only when a job calls for it.
It has two kinds. System context is the same for every Product Owner. Product context is custom to each Product Owner and stays in their own Drive. It is the Product Meta, the Project Registry, the project meta, and the product's own documents.
It is not the context Sage_AI holds in a conversation.
Sage_AI Skill
A packaged set of instructions that Sage_AI loads for one kind of job. It can carry reference files and a script that checks its own output. A Product Owner uploads it to their Claude account as a ZIP, under Customize, then Skills.
A Sage_AI Skill is global and holds no value that belongs to one Product Owner. Those values live in the Product Owner's own documents. The term is Sage_AI Skill, not skill alone. Any Sage_AI Skill is published in the public repository mpaxmarketing/sage-ai.