@openpresentation/opf 0.1.0 → 0.2.1

package/dist/spec/catalogs/narratives/strategic-advisory.json

@@ -1,85 +1,85 @@
-{
-  "$schema": "https://openpresentation.org/schema/opf-narrative/v1",
-  "id": "strategic-advisory",
-  "name": "Strategic Advisory",
-  "summary": "Consulting-style advisory deck applying Minto's pyramid: title, situation/complication/question, the answer in one sentence, and three argued points with a process. Use when the audience expects a recommendation and the case for it, in that order.",
-  "audienceFit": [
-    "executives",
-    "boards",
-    "leadership-teams",
-    "clients"
-  ],
-  "durationRange": {
-    "minMinutes": 15,
-    "maxMinutes": 45
-  },
-  "tags": [
-    "consulting",
-    "advisory",
-    "strategy",
-    "minto"
-  ],
-  "beats": [
-    {
-      "id": "title",
-      "name": "Title",
-      "description": "Open with a one-line summary statement that captures the recommendation, not the topic. The title slide is the headline of the entire engagement — make it specific enough that someone reading only this slide already understands the position.",
-      "layoutHint": "title-left",
-      "instructions": "Brief summary sentence",
-      "slideType": "text"
-    },
-    {
-      "id": "scq",
-      "name": "Situation, Complication, Question",
-      "description": "Frame the engagement on a single slide: the relevant status quo, what needs to change, and the question that needs to be resolved. This is the SCQ shorthand — context, tension, prompt. Don't yet answer."
-    },
-    {
-      "id": "answer",
-      "name": "Answer",
-      "description": "Deliver the recommendation in a single sentence. No arguments yet, no caveats. The answer is the apex of the pyramid; the rest of the deck supports it.",
-      "instructions": "A solution in one sentence, no arguments yet",
-      "slideType": "text",
-      "layoutHint": "text-1x-left"
-    },
-    {
-      "id": "arguments",
-      "name": "Arguments",
-      "description": "Preview the three top-level arguments that defend the answer. One slide naming all three so the audience knows where the deck is going. Each argument should be a complete claim, not a topic.",
-      "instructions": "Support the solution",
-      "slideType": "text",
-      "layoutHint": "text-1x-left"
-    },
-    {
-      "id": "argument-1",
-      "name": "Argument 1",
-      "description": "Develop the first argument with supporting data, examples, and reasoning. Lead with the claim, then the evidence — Minto-style. The slide should stand alone if pulled out.",
-      "instructions": "First key point",
-      "slideType": "text",
-      "layoutHint": "text-1x-left"
-    },
-    {
-      "id": "argument-2",
-      "name": "Argument 2",
-      "description": "Develop the second argument the same way. Vary the type of evidence — quantitative, qualitative, comparative — so the audience hears the case from multiple angles.",
-      "instructions": "Second key point",
-      "slideType": "text",
-      "layoutHint": "text-1x-left"
-    },
-    {
-      "id": "argument-3",
-      "name": "Argument 3",
-      "description": "Develop the third argument and walk through the supporting process or methodology. This is often where the 'how' lives — the implementation insight that makes the recommendation feel actionable.",
-      "instructions": "Third key point with a process",
-      "slideType": "text",
-      "layoutHint": "text-1x-left"
-    },
-    {
-      "id": "summary",
-      "name": "Summary",
-      "description": "Recap the answer and arguments in a single slide and point to additional resources. Close with the explicit next step you want the audience to take.",
-      "layoutHint": "title-left",
-      "instructions": "Recap the answer, provide additional resources",
-      "slideType": "text"
-    }
-  ]
-}
+{
+  "$schema": "https://openpresentation.org/schema/opf-narrative/v1",
+  "id": "strategic-advisory",
+  "name": "Strategic Advisory",
+  "summary": "Consulting-style advisory deck applying Minto's pyramid: title, situation/complication/question, the answer in one sentence, and three argued points with a process. Use when the audience expects a recommendation and the case for it, in that order.",
+  "audienceFit": [
+    "executives",
+    "boards",
+    "leadership-teams",
+    "clients"
+  ],
+  "durationRange": {
+    "minMinutes": 15,
+    "maxMinutes": 45
+  },
+  "tags": [
+    "consulting",
+    "advisory",
+    "strategy",
+    "minto"
+  ],
+  "beats": [
+    {
+      "id": "title",
+      "name": "Title",
+      "description": "Open with a one-line summary statement that captures the recommendation, not the topic. The title slide is the headline of the entire engagement — make it specific enough that someone reading only this slide already understands the position.",
+      "layoutHint": "title-left",
+      "instructions": "Brief summary sentence",
+      "slideType": "text"
+    },
+    {
+      "id": "scq",
+      "name": "Situation, Complication, Question",
+      "description": "Frame the engagement on a single slide: the relevant status quo, what needs to change, and the question that needs to be resolved. This is the SCQ shorthand — context, tension, prompt. Don't yet answer."
+    },
+    {
+      "id": "answer",
+      "name": "Answer",
+      "description": "Deliver the recommendation in a single sentence. No arguments yet, no caveats. The answer is the apex of the pyramid; the rest of the deck supports it.",
+      "instructions": "A solution in one sentence, no arguments yet",
+      "slideType": "text",
+      "layoutHint": "text-1x-left"
+    },
+    {
+      "id": "arguments",
+      "name": "Arguments",
+      "description": "Preview the three top-level arguments that defend the answer. One slide naming all three so the audience knows where the deck is going. Each argument should be a complete claim, not a topic.",
+      "instructions": "Support the solution",
+      "slideType": "text",
+      "layoutHint": "text-1x-left"
+    },
+    {
+      "id": "argument-1",
+      "name": "Argument 1",
+      "description": "Develop the first argument with supporting data, examples, and reasoning. Lead with the claim, then the evidence — Minto-style. The slide should stand alone if pulled out.",
+      "instructions": "First key point",
+      "slideType": "text",
+      "layoutHint": "text-1x-left"
+    },
+    {
+      "id": "argument-2",
+      "name": "Argument 2",
+      "description": "Develop the second argument the same way. Vary the type of evidence — quantitative, qualitative, comparative — so the audience hears the case from multiple angles.",
+      "instructions": "Second key point",
+      "slideType": "text",
+      "layoutHint": "text-1x-left"
+    },
+    {
+      "id": "argument-3",
+      "name": "Argument 3",
+      "description": "Develop the third argument and walk through the supporting process or methodology. This is often where the 'how' lives — the implementation insight that makes the recommendation feel actionable.",
+      "instructions": "Third key point with a process",
+      "slideType": "text",
+      "layoutHint": "text-1x-left"
+    },
+    {
+      "id": "summary",
+      "name": "Summary",
+      "description": "Recap the answer and arguments in a single slide and point to additional resources. Close with the explicit next step you want the audience to take.",
+      "layoutHint": "title-left",
+      "instructions": "Recap the answer, provide additional resources",
+      "slideType": "text"
+    }
+  ]
+}

package/dist/spec/catalogs/narratives/strategic-narrative.json

@@ -1,61 +1,61 @@
-{
-  "$schema": "https://openpresentation.org/schema/opf-narrative/v1",
-  "id": "strategic-narrative",
-  "name": "Strategic Narrative",
-  "summary": "The change-driven founder/sales arc: a tectonic shift creates winners and losers, the audience must respond, and your product is the only credible way to land in the winners' camp. Used for top-of-funnel sales pitches, board re-positioning, and high-stakes founder talks.",
-  "audienceFit": [
-    "customers",
-    "prospects",
-    "board",
-    "investors",
-    "executives"
-  ],
-  "durationRange": {
-    "minMinutes": 10,
-    "maxMinutes": 30
-  },
-  "tags": [
-    "strategic",
-    "sales",
-    "positioning",
-    "category"
-  ],
-  "beats": [
-    {
-      "id": "shift",
-      "name": "The Shift",
-      "description": "Open by naming a large, undeniable change in the world that the audience already half-believes. Technology, regulation, customer behavior, economics — pick the shift that recasts the audience's reality. The shift, not your product, is the protagonist of the first half of the deck."
-    },
-    {
-      "id": "stakes",
-      "name": "Winners and Losers",
-      "description": "Make the consequences of the shift concrete. Who wins, who loses, by how much, on what timeframe. Use specific examples — companies, products, segments — that have already moved or are about to. The audience should feel that standing still is the riskiest choice."
-    },
-    {
-      "id": "promised-land",
-      "name": "Promised Land",
-      "description": "Paint a vivid picture of the future state your audience could occupy if they navigate the shift well. Describe outcomes, not features. The promised land must feel desirable, achievable, and meaningfully different from where they are today."
-    },
-    {
-      "id": "obstacles",
-      "name": "Old Game",
-      "description": "Show why the existing playbook can't get the audience to the promised land. Name the legacy approach honestly and credit what it once did, then explain why the shift has rendered it insufficient. Avoid strawmen — the more fairly you state the old game, the more credible your new game becomes."
-    },
-    {
-      "id": "mechanism",
-      "name": "New Game",
-      "description": "Introduce your category-defining approach as the way to play the new game. Show the principles or capabilities that make it possible only now. Emphasize what's structurally different from the old game, not what's marginally better."
-    },
-    {
-      "id": "evidence",
-      "name": "Evidence",
-      "description": "Prove the new game works. Customer outcomes, named logos, before/after data, third-party validation. Choose evidence that maps directly to the shift you opened with — proof that other audiences in the same boat made it to the promised land."
-    },
-    {
-      "id": "ask",
-      "name": "Call to Action",
-      "description": "Close with the single decision you want the audience to make. Frame it as the obvious next move given the shift, the stakes, and the new game. Make it small enough to say yes to today and large enough to start a real engagement.",
-      "layoutHint": "title-left"
-    }
-  ]
-}
+{
+  "$schema": "https://openpresentation.org/schema/opf-narrative/v1",
+  "id": "strategic-narrative",
+  "name": "Strategic Narrative",
+  "summary": "The change-driven founder/sales arc: a tectonic shift creates winners and losers, the audience must respond, and your product is the only credible way to land in the winners' camp. Used for top-of-funnel sales pitches, board re-positioning, and high-stakes founder talks.",
+  "audienceFit": [
+    "customers",
+    "prospects",
+    "board",
+    "investors",
+    "executives"
+  ],
+  "durationRange": {
+    "minMinutes": 10,
+    "maxMinutes": 30
+  },
+  "tags": [
+    "strategic",
+    "sales",
+    "positioning",
+    "category"
+  ],
+  "beats": [
+    {
+      "id": "shift",
+      "name": "The Shift",
+      "description": "Open by naming a large, undeniable change in the world that the audience already half-believes. Technology, regulation, customer behavior, economics — pick the shift that recasts the audience's reality. The shift, not your product, is the protagonist of the first half of the deck."
+    },
+    {
+      "id": "stakes",
+      "name": "Winners and Losers",
+      "description": "Make the consequences of the shift concrete. Who wins, who loses, by how much, on what timeframe. Use specific examples — companies, products, segments — that have already moved or are about to. The audience should feel that standing still is the riskiest choice."
+    },
+    {
+      "id": "promised-land",
+      "name": "Promised Land",
+      "description": "Paint a vivid picture of the future state your audience could occupy if they navigate the shift well. Describe outcomes, not features. The promised land must feel desirable, achievable, and meaningfully different from where they are today."
+    },
+    {
+      "id": "obstacles",
+      "name": "Old Game",
+      "description": "Show why the existing playbook can't get the audience to the promised land. Name the legacy approach honestly and credit what it once did, then explain why the shift has rendered it insufficient. Avoid strawmen — the more fairly you state the old game, the more credible your new game becomes."
+    },
+    {
+      "id": "mechanism",
+      "name": "New Game",
+      "description": "Introduce your category-defining approach as the way to play the new game. Show the principles or capabilities that make it possible only now. Emphasize what's structurally different from the old game, not what's marginally better."
+    },
+    {
+      "id": "evidence",
+      "name": "Evidence",
+      "description": "Prove the new game works. Customer outcomes, named logos, before/after data, third-party validation. Choose evidence that maps directly to the shift you opened with — proof that other audiences in the same boat made it to the promised land."
+    },
+    {
+      "id": "ask",
+      "name": "Call to Action",
+      "description": "Close with the single decision you want the audience to make. Frame it as the obvious next move given the shift, the stakes, and the new game. Make it small enough to say yes to today and large enough to start a real engagement.",
+      "layoutHint": "title-left"
+    }
+  ]
+}

package/dist/spec/catalogs/narratives/survey-analysis.json

@@ -1,104 +1,104 @@
-{
-  "$schema": "https://openpresentation.org/schema/opf-narrative/v1",
-  "id": "survey-analysis",
-  "name": "Survey Analysis",
-  "summary": "Structured walk-through of survey results: topic, executive summary, methodology, findings, analysis, implications, recommendations. Built so a reader who only sees the second slide already knows the headline insight.",
-  "audienceFit": [
-    "executives",
-    "researchers",
-    "stakeholders",
-    "marketing-teams"
-  ],
-  "durationRange": {
-    "minMinutes": 20,
-    "maxMinutes": 60
-  },
-  "tags": [
-    "data-driven",
-    "research",
-    "insights",
-    "voice-of-customer"
-  ],
-  "beats": [
-    {
-      "id": "introduction",
-      "name": "Introduction",
-      "description": "Open by naming the question the survey was meant to answer. Why this, why now, who commissioned it. Anchor the audience in the decision the survey is designed to inform.",
-      "instructions": "Present survey topic",
-      "slideType": "text",
-      "layoutHint": "text-1x-left"
-    },
-    {
-      "id": "executive-summary",
-      "name": "Executive Summary",
-      "description": "State the top three findings in plain language on a single slide. A reader who only sees this slide should still be able to make the right call. Avoid hedging — synthesis is the point.",
-      "instructions": "Summarize key findings",
-      "slideType": "text",
-      "layoutHint": "text-1x-left"
-    },
-    {
-      "id": "context",
-      "name": "Context",
-      "description": "Detail the situation behind the survey: prior knowledge, related research, the gap this work fills. Just enough to position the findings as new information rather than restated common sense.",
-      "instructions": "Detail survey background",
-      "slideType": "text",
-      "layoutHint": "text-1x-left"
-    },
-    {
-      "id": "data-methodology",
-      "name": "Data & Methodology",
-      "description": "Describe how the data was collected and from whom. Sample size, recruitment, instrument, timing. Be honest about limitations; methodological transparency is what gives the findings their weight.",
-      "instructions": "Discuss sourcing and collection",
-      "slideType": "text",
-      "layoutHint": "text-1x-left"
-    },
-    {
-      "id": "data-summary",
-      "name": "Data Summary",
-      "description": "Give the audience an overview of the dataset before drilling in. Demographics, response rates, distribution of key variables. Help them calibrate what 'most' and 'few' mean in this study.",
-      "instructions": "Provide data overview",
-      "slideType": "text",
-      "layoutHint": "text-1x-left"
-    },
-    {
-      "id": "findings",
-      "name": "Findings",
-      "description": "Present the key insights one at a time. Lead each finding with the claim, then the chart. Avoid burying the point under the visualization — captions should restate the insight in words.",
-      "instructions": "Highlight key insights",
-      "slideType": "text",
-      "layoutHint": "text-1x-left"
-    },
-    {
-      "id": "data-analysis",
-      "name": "Data Analysis",
-      "description": "Break down the data behind each finding: cross-tabs, segment splits, statistical confidence. This is the slide skeptics will scrutinize — make it scrutinizable.",
-      "instructions": "Break down data",
-      "slideType": "text",
-      "layoutHint": "text-1x-left"
-    },
-    {
-      "id": "implications",
-      "name": "Implications",
-      "description": "Translate findings into 'so what.' What changes for product, marketing, ops, the customer? Implications without consequences are interesting trivia, not research.",
-      "instructions": "Discuss survey implications",
-      "slideType": "text",
-      "layoutHint": "text-1x-left"
-    },
-    {
-      "id": "recommendations",
-      "name": "Recommendations",
-      "description": "Provide the actions that follow from the implications. Prioritize, attach owners, mark which require decisions. This is where research becomes useful.",
-      "instructions": "Provide action plans",
-      "slideType": "text",
-      "layoutHint": "text-1x-left"
-    },
-    {
-      "id": "conclusion",
-      "name": "Conclusion",
-      "description": "Recap the headline finding and the most important recommendation. End with the next step — a follow-on study, a workshop, a decision — so the work doesn't sit on a shelf.",
-      "layoutHint": "title-left",
-      "instructions": "Recap and finalize",
-      "slideType": "text"
-    }
-  ]
-}
+{
+  "$schema": "https://openpresentation.org/schema/opf-narrative/v1",
+  "id": "survey-analysis",
+  "name": "Survey Analysis",
+  "summary": "Structured walk-through of survey results: topic, executive summary, methodology, findings, analysis, implications, recommendations. Built so a reader who only sees the second slide already knows the headline insight.",
+  "audienceFit": [
+    "executives",
+    "researchers",
+    "stakeholders",
+    "marketing-teams"
+  ],
+  "durationRange": {
+    "minMinutes": 20,
+    "maxMinutes": 60
+  },
+  "tags": [
+    "data-driven",
+    "research",
+    "insights",
+    "voice-of-customer"
+  ],
+  "beats": [
+    {
+      "id": "introduction",
+      "name": "Introduction",
+      "description": "Open by naming the question the survey was meant to answer. Why this, why now, who commissioned it. Anchor the audience in the decision the survey is designed to inform.",
+      "instructions": "Present survey topic",
+      "slideType": "text",
+      "layoutHint": "text-1x-left"
+    },
+    {
+      "id": "executive-summary",
+      "name": "Executive Summary",
+      "description": "State the top three findings in plain language on a single slide. A reader who only sees this slide should still be able to make the right call. Avoid hedging — synthesis is the point.",
+      "instructions": "Summarize key findings",
+      "slideType": "text",
+      "layoutHint": "text-1x-left"
+    },
+    {
+      "id": "context",
+      "name": "Context",
+      "description": "Detail the situation behind the survey: prior knowledge, related research, the gap this work fills. Just enough to position the findings as new information rather than restated common sense.",
+      "instructions": "Detail survey background",
+      "slideType": "text",
+      "layoutHint": "text-1x-left"
+    },
+    {
+      "id": "data-methodology",
+      "name": "Data & Methodology",
+      "description": "Describe how the data was collected and from whom. Sample size, recruitment, instrument, timing. Be honest about limitations; methodological transparency is what gives the findings their weight.",
+      "instructions": "Discuss sourcing and collection",
+      "slideType": "text",
+      "layoutHint": "text-1x-left"
+    },
+    {
+      "id": "data-summary",
+      "name": "Data Summary",
+      "description": "Give the audience an overview of the dataset before drilling in. Demographics, response rates, distribution of key variables. Help them calibrate what 'most' and 'few' mean in this study.",
+      "instructions": "Provide data overview",
+      "slideType": "text",
+      "layoutHint": "text-1x-left"
+    },
+    {
+      "id": "findings",
+      "name": "Findings",
+      "description": "Present the key insights one at a time. Lead each finding with the claim, then the chart. Avoid burying the point under the visualization — captions should restate the insight in words.",
+      "instructions": "Highlight key insights",
+      "slideType": "text",
+      "layoutHint": "text-1x-left"
+    },
+    {
+      "id": "data-analysis",
+      "name": "Data Analysis",
+      "description": "Break down the data behind each finding: cross-tabs, segment splits, statistical confidence. This is the slide skeptics will scrutinize — make it scrutinizable.",
+      "instructions": "Break down data",
+      "slideType": "text",
+      "layoutHint": "text-1x-left"
+    },
+    {
+      "id": "implications",
+      "name": "Implications",
+      "description": "Translate findings into 'so what.' What changes for product, marketing, ops, the customer? Implications without consequences are interesting trivia, not research.",
+      "instructions": "Discuss survey implications",
+      "slideType": "text",
+      "layoutHint": "text-1x-left"
+    },
+    {
+      "id": "recommendations",
+      "name": "Recommendations",
+      "description": "Provide the actions that follow from the implications. Prioritize, attach owners, mark which require decisions. This is where research becomes useful.",
+      "instructions": "Provide action plans",
+      "slideType": "text",
+      "layoutHint": "text-1x-left"
+    },
+    {
+      "id": "conclusion",
+      "name": "Conclusion",
+      "description": "Recap the headline finding and the most important recommendation. End with the next step — a follow-on study, a workshop, a decision — so the work doesn't sit on a shelf.",
+      "layoutHint": "title-left",
+      "instructions": "Recap and finalize",
+      "slideType": "text"
+    }
+  ]
+}