@openpresentation/opf 0.18.4 → 0.19.0

package/dist/spec/catalogs/narratives/rags-to-riches.json

@@ -1,80 +0,0 @@
-{
-  "$schema": "https://openpresentation.org/schema/opf-narrative/v1",
-  "id": "rags-to-riches",
-  "name": "Rags to Riches",
-  "summary": "Underdog journey from initial failure to eventual success. Pulls on resilience, grit, and perseverance — useful for founder stories, brand stories, and any deck where the audience needs to feel the cost behind the win.",
-  "audienceFit": [
-    "general-audience",
-    "customers",
-    "press",
-    "candidates"
-  ],
-  "duration": {
-    "min": 5,
-    "max": 20
-  },
-  "tags": [
-    "storytelling",
-    "founder",
-    "brand",
-    "inspirational"
-  ],
-  "beats": [
-    {
-      "id": "origin",
-      "name": "Origin",
-      "description": "Start at the bottom. Describe the humble beginning, the constraint, the moment before anything had been built. Concrete details — a place, a year, a feeling — earn the audience's investment in what follows.",
-      "instructions": "Humble beginning",
-      "type": "text",
-      "layout": "text-1x"
-    },
-    {
-      "id": "inspiration",
-      "name": "Inspiration",
-      "description": "Show the moment the protagonist found their calling. A conversation, a customer, a problem they couldn't unsee. The inspiration is the engine that pushes the rest of the story uphill.",
-      "instructions": "Discover true calling",
-      "type": "text",
-      "layout": "text-1x"
-    },
-    {
-      "id": "opportunity",
-      "name": "Opportunity",
-      "description": "Reveal the chance the protagonist took. Why this and not something safer? Make the choice visible — opportunities only count when there was something else they passed up to grab them.",
-      "instructions": "Spot golden chance",
-      "type": "text",
-      "layout": "text-1x"
-    },
-    {
-      "id": "adversity",
-      "name": "Adversity",
-      "description": "Walk through the hardest stretch. Concrete failures, near-misses, moments of doubt. Resist the temptation to skip past the pain — the audience trusts the win more when the loss was real.",
-      "instructions": "Face hardest struggles",
-      "type": "text",
-      "layout": "text-1x"
-    },
-    {
-      "id": "overcoming",
-      "name": "Overcoming",
-      "description": "Show how the obstacles got beaten. What changed, what was learned, what hard call was made. The transition from 'rags' to 'riches' should feel earned, not granted.",
-      "instructions": "Surmount tough obstacles",
-      "type": "text",
-      "layout": "text-1x"
-    },
-    {
-      "id": "impactful-change",
-      "name": "Impactful Change",
-      "description": "Describe the moment the world tipped. The customer who said yes, the product that broke through, the metric that turned. One concrete transformation lands harder than a montage.",
-      "instructions": "Alter the status quo",
-      "type": "text",
-      "layout": "text-1x"
-    },
-    {
-      "id": "lasting-legacy",
-      "name": "Lasting Legacy",
-      "description": "Close on what the journey means for those who come next. The lesson, the people changed, the work that endures. Leave the audience with a takeaway that outlives the story.",
-      "layout": "title",
-      "instructions": "Create enduring effect",
-      "type": "text"
-    }
-  ]
-}

package/dist/spec/catalogs/narratives/reveal.json

@@ -1,87 +0,0 @@
-{
-  "$schema": "https://openpresentation.org/schema/opf-narrative/v1",
-  "id": "reveal",
-  "name": "Reveal",
-  "summary": "Insight-driven keynote arc inspired by Amy Cuddy's 2012 talk on body language: connect through personal story, ground in research, illustrate with anecdote, summarize, break stereotypes, advise, demonstrate authenticity, close with impact. For talks that aim to change how the audience sees something they thought they understood.",
-  "audienceFit": [
-    "general-audience",
-    "academics",
-    "professionals"
-  ],
-  "duration": {
-    "min": 15,
-    "max": 25
-  },
-  "tags": [
-    "keynote",
-    "research",
-    "talk",
-    "inspirational"
-  ],
-  "beats": [
-    {
-      "id": "personal-story",
-      "name": "Personal Story",
-      "description": "Open with a personal experience that establishes why the topic matters to you. Specificity earns intimacy; intimacy earns the audience's permission to be moved.",
-      "instructions": "Share personal experiences to connect with the audience",
-      "type": "text",
-      "layout": "text-1x"
-    },
-    {
-      "id": "research-exposition",
-      "name": "Research Exposition",
-      "description": "Lay out the scientific or empirical data that backs the premise. Be rigorous but not academic — the audience needs to understand the evidence well enough to defend it later.",
-      "instructions": "Unravel scientific data backing the premise",
-      "type": "text",
-      "layout": "text-1x"
-    },
-    {
-      "id": "real-life-anecdote",
-      "name": "Real-Life Anecdote",
-      "description": "Illustrate the research with a story from the field. Make the abstract finding feel like something that happens to people the audience could imagine being.",
-      "instructions": "Illustrate with stories to make the point relatable",
-      "type": "text",
-      "layout": "text-1x"
-    },
-    {
-      "id": "critical-insights",
-      "name": "Critical Insights",
-      "description": "Summarize the two or three findings the audience must walk away with. Distill them into language a non-specialist could repeat without distortion.",
-      "instructions": "Summarize key points",
-      "type": "text",
-      "layout": "text-1x"
-    },
-    {
-      "id": "break-stereotypes",
-      "name": "Break Stereotypes",
-      "description": "Question redundant norms or beliefs the research undermines. Be specific about what's being challenged so the audience knows what to update.",
-      "instructions": "Question redundant norms and belief systems",
-      "type": "text",
-      "layout": "text-1x"
-    },
-    {
-      "id": "empowering-advice",
-      "name": "Empowering Advice",
-      "description": "Translate the insights into a small, actionable practice. The advice should be doable today, not only next quarter — the goal is movement, not aspiration.",
-      "instructions": "Motivational message to act upon",
-      "type": "text",
-      "layout": "text-1x"
-    },
-    {
-      "id": "authenticity",
-      "name": "Authenticity",
-      "description": "Speak honestly about your own struggle with the topic. Vulnerability, used with restraint, is what turns research into a felt truth.",
-      "instructions": "Honest and real communication to demonstrate authenticity",
-      "type": "text",
-      "layout": "text-1x"
-    },
-    {
-      "id": "close-with-impact",
-      "name": "Close With Impact",
-      "description": "End on a motivational high — the line, image, or invitation you want to follow the audience out of the room. Close the talk where it began, transformed.",
-      "layout": "title",
-      "instructions": "End on a motivational high",
-      "type": "text"
-    }
-  ]
-}

package/dist/spec/catalogs/narratives/scqa.json

@@ -1,55 +0,0 @@
-{
-  "$schema": "https://openpresentation.org/schema/opf-narrative/v1",
-  "id": "scqa",
-  "name": "SCQA (Situation–Complication–Question–Answer)",
-  "summary": "Barbara Minto's pyramid-principle arc: surface the recommendation up front, then layer key arguments and supporting evidence beneath it. The default for executive memos, strategic recommendations, and consulting decks where the audience needs the answer fast.",
-  "audienceFit": [
-    "executives",
-    "boards",
-    "leadership-teams"
-  ],
-  "duration": {
-    "min": 5,
-    "max": 20
-  },
-  "tags": [
-    "executive",
-    "strategy",
-    "consulting",
-    "minto",
-    "pyramid"
-  ],
-  "beats": [
-    {
-      "id": "situation",
-      "name": "Situation",
-      "description": "Establish the shared context: what is true today that the audience already agrees on. State only facts the audience accepts without argument. The goal is alignment, not persuasion — you are setting the stage."
-    },
-    {
-      "id": "complication",
-      "name": "Complication",
-      "description": "Introduce the disturbance to the situation: what changed, what is at risk, what is no longer working. This is the tension that makes the audience lean in. Be specific and quantify the change where possible."
-    },
-    {
-      "id": "question",
-      "name": "Key Question",
-      "description": "Surface the question the complication forces the audience to answer. Frame it explicitly — 'Should we…?', 'How do we…?', 'What changes if…?'. The question should feel inevitable given the complication."
-    },
-    {
-      "id": "answer",
-      "name": "Answer",
-      "description": "Deliver the recommendation in a single sentence, up front. No arguments yet, no caveats — just the conclusion the rest of the deck will defend. This is the apex of the Minto pyramid; everything that follows supports it.",
-      "layout": "title"
-    },
-    {
-      "id": "key-arguments",
-      "name": "Key Arguments",
-      "description": "Lay out the two or three top-level reasons the answer is correct. One slide per argument, or one summary slide naming all of them. Each argument should stand alone as a compelling reason; together they should be exhaustive of the case."
-    },
-    {
-      "id": "supporting-evidence",
-      "name": "Supporting Evidence",
-      "description": "Present the data, examples, and case studies that ground each argument. Pyramid-principle style: every claim above is backed by something verifiable here. Cite sources; show the numbers; let the evidence carry the weight."
-    }
-  ]
-}

package/dist/spec/catalogs/narratives/situation-complication-resolution.json

@@ -1,56 +0,0 @@
-{
-  "$schema": "https://openpresentation.org/schema/opf-narrative/v1",
-  "id": "situation-complication-resolution",
-  "name": "Situation-Complication-Resolution",
-  "summary": "McKinsey-style structure that builds tension before delivering insights.",
-  "description": "A McKinsey-style structure that builds tension before delivering the insight. Establish the context everyone already agrees on, introduce what has changed or what challenge has emerged, name the key question that change raises, then deliver the recommendation that resolves it. The tone is logical: a tight causal chain from context to recommendation. Best for strategy presentations, consulting decks, and analytical reports; typical decks run 4-10 slides (management consulting report, strategic recommendation, board update).",
-  "audienceFit": [
-    "senior-leadership",
-    "consultants",
-    "strategy-teams"
-  ],
-  "duration": {
-    "min": 5,
-    "max": 20
-  },
-  "tags": [
-    "strategy",
-    "consulting",
-    "minto",
-    "recommendation"
-  ],
-  "beats": [
-    {
-      "id": "situation",
-      "name": "Situation",
-      "description": "Set the scene with relevant background and context everyone agrees on.",
-      "instructions": "State the shared context the audience already accepts.",
-      "type": "list",
-      "layout": "list-1x"
-    },
-    {
-      "id": "complication",
-      "name": "Complication",
-      "description": "Introduce what has changed or what challenge has emerged.",
-      "instructions": "Introduce the change, risk, or tension.",
-      "type": "text",
-      "layout": "text-2x"
-    },
-    {
-      "id": "question",
-      "name": "Question",
-      "description": "Articulate the key question that the complication raises.",
-      "instructions": "Frame the decision question raised by the complication.",
-      "type": "text",
-      "layout": "title"
-    },
-    {
-      "id": "answer",
-      "name": "Answer",
-      "description": "Deliver your recommendation or insight that resolves the question.",
-      "instructions": "Deliver the recommendation that resolves the question.",
-      "type": "timeline",
-      "layout": "timeline-1x"
-    }
-  ]
-}

package/dist/spec/catalogs/narratives/sparkline.json

@@ -1,56 +0,0 @@
-{
-  "$schema": "https://openpresentation.org/schema/opf-narrative/v1",
-  "id": "sparkline",
-  "name": "Sparkline",
-  "summary": "A tight comparison arc showing the transformation from an inferior state to a superior one, anchored by contrast.",
-  "description": "A tight comparison arc that shows the move from an inferior state to a superior one, anchored by contrast. Make the painful before state vivid, reveal the product, decision, or event that changes the trajectory, present the new reality in concrete terms, then prove it with data or testimonial. The tone is contrastive: it makes the gap between old and new viscerally clear. Best for product demos, case study summaries, ROI presentations, and before-and-after technology comparisons; typical decks run 4-6 slides.",
-  "audienceFit": [
-    "prospective-buyers",
-    "skeptical-stakeholders",
-    "evaluation-committees"
-  ],
-  "duration": {
-    "min": 3,
-    "max": 15
-  },
-  "tags": [
-    "contrast",
-    "transformation",
-    "product",
-    "roi"
-  ],
-  "beats": [
-    {
-      "id": "before-state",
-      "name": "Before State",
-      "description": "Make the current pain or limitation vivid with numbers, stories, or visuals that make the problem real.",
-      "instructions": "Make the current pain or limitation vivid.",
-      "type": "text",
-      "layout": "text-2x"
-    },
-    {
-      "id": "contrast-moment",
-      "name": "Contrast Moment",
-      "description": "Introduce the change agent, product, or decision that shifts the trajectory.",
-      "instructions": "Introduce the decision, product, or event that changes the trajectory.",
-      "type": "text",
-      "layout": "title"
-    },
-    {
-      "id": "after-state",
-      "name": "After State",
-      "description": "Show the improved reality. Make it concrete and specific instead of relying on vague benefit language.",
-      "instructions": "Show the new reality created by the change.",
-      "type": "text",
-      "layout": "text-1x"
-    },
-    {
-      "id": "proof",
-      "name": "Proof",
-      "description": "Validate the after state with metrics, testimonials, or third-party evidence.",
-      "instructions": "Validate the change with evidence.",
-      "type": "metric",
-      "layout": "number-1x"
-    }
-  ]
-}

package/dist/spec/catalogs/narratives/star-method.json

@@ -1,56 +0,0 @@
-{
-  "$schema": "https://openpresentation.org/schema/opf-narrative/v1",
-  "id": "star-method",
-  "name": "STAR Method",
-  "summary": "Results-focused framework that demonstrates impact through concrete examples.",
-  "description": "A results-focused framework that demonstrates impact through a concrete example: the Situation, the Task you were responsible for, the Actions you took, and the measurable Result. The tone is evidential: every claim is grounded in a specific, verifiable outcome. Best for project reviews, portfolio presentations, and achievement showcases; typical decks run 4-8 slides (case study, customer success story, project retrospective).",
-  "audienceFit": [
-    "hr-and-talent",
-    "performance-reviewers",
-    "award-committees"
-  ],
-  "duration": {
-    "min": 5,
-    "max": 15
-  },
-  "tags": [
-    "case-study",
-    "proof",
-    "results",
-    "retrospective"
-  ],
-  "beats": [
-    {
-      "id": "situation",
-      "name": "Situation",
-      "description": "Describe the context and background of the scenario.",
-      "instructions": "Describe the relevant context and constraints.",
-      "type": "text",
-      "layout": "text-1x"
-    },
-    {
-      "id": "task",
-      "name": "Task",
-      "description": "Explain your specific role and responsibilities in this situation.",
-      "instructions": "Explain the responsibility or target outcome.",
-      "type": "list",
-      "layout": "list-2x"
-    },
-    {
-      "id": "action",
-      "name": "Action",
-      "description": "Detail the specific steps you took to address the challenge.",
-      "instructions": "Detail the actions taken and choices made.",
-      "type": "timeline",
-      "layout": "timeline-1x"
-    },
-    {
-      "id": "result",
-      "name": "Result",
-      "description": "Share the measurable outcomes and impact of your actions.",
-      "instructions": "Show measurable impact and proof.",
-      "type": "metric",
-      "layout": "number-1x"
-    }
-  ]
-}

package/dist/spec/catalogs/narratives/status-update.json

@@ -1,72 +0,0 @@
-{
-  "$schema": "https://openpresentation.org/schema/opf-narrative/v1",
-  "id": "status-update",
-  "name": "Status Update",
-  "summary": "Concise progress-report arc for keeping a stakeholder informed: headline, brief, progress, results, plan, feedback. Optimized for short, repeated updates rather than one-time deep dives.",
-  "audienceFit": [
-    "stakeholders",
-    "managers",
-    "customers",
-    "executives"
-  ],
-  "duration": {
-    "min": 5,
-    "max": 15
-  },
-  "tags": [
-    "reporting",
-    "operations",
-    "customer-relationship",
-    "weekly"
-  ],
-  "beats": [
-    {
-      "id": "headline",
-      "name": "Headline",
-      "description": "Open with the single most important sentence the audience needs to know — on track, off track, or shifted. The headline replaces 'how's it going' with a clear answer.",
-      "layout": "title",
-      "instructions": "Title & date",
-      "type": "text"
-    },
-    {
-      "id": "brief",
-      "name": "Brief",
-      "description": "State the objective for the period and what was promised. One slide, three lines. Frames the rest of the update so progress is read against a clear bar.",
-      "instructions": "Summary/objectives",
-      "type": "text",
-      "layout": "text-1x"
-    },
-    {
-      "id": "progress",
-      "name": "Progress",
-      "description": "Walk through the actions taken since the last update. Specific, attributable, dated. Avoid effort theater — list outcomes and material moves, not activity for its own sake.",
-      "instructions": "Explain actions taken",
-      "type": "text",
-      "layout": "text-1x"
-    },
-    {
-      "id": "results",
-      "name": "Results",
-      "description": "Show the outcomes those actions produced. Metrics, customer signals, decisions made. Keep the comparison crisp — versus plan, versus last period, versus benchmark.",
-      "instructions": "Show outcomes",
-      "type": "text",
-      "layout": "text-1x"
-    },
-    {
-      "id": "action-plan",
-      "name": "Action Plan",
-      "description": "Outline the next steps and who owns them. Be specific about the next decision point and what would have to happen to slip the schedule.",
-      "instructions": "Outline next steps",
-      "type": "text",
-      "layout": "text-1x"
-    },
-    {
-      "id": "feedback",
-      "name": "Feedback",
-      "description": "Invite the audience to weigh in: where you'd like input, where you need a decision, where help would unblock you. End the update with an open hand, not a closed file.",
-      "layout": "title",
-      "instructions": "Ask for response",
-      "type": "text"
-    }
-  ]
-}

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

@@ -1,85 +0,0 @@
-{
-  "$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"
-  ],
-  "duration": {
-    "min": 15,
-    "max": 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.",
-      "layout": "title",
-      "instructions": "Brief summary sentence",
-      "type": "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",
-      "type": "text",
-      "layout": "text-1x"
-    },
-    {
-      "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",
-      "type": "text",
-      "layout": "text-1x"
-    },
-    {
-      "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",
-      "type": "text",
-      "layout": "text-1x"
-    },
-    {
-      "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",
-      "type": "text",
-      "layout": "text-1x"
-    },
-    {
-      "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",
-      "type": "text",
-      "layout": "text-1x"
-    },
-    {
-      "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.",
-      "layout": "title",
-      "instructions": "Recap the answer, provide additional resources",
-      "type": "text"
-    }
-  ]
-}

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

@@ -1,61 +0,0 @@
-{
-  "$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"
-  ],
-  "duration": {
-    "min": 10,
-    "max": 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.",
-      "layout": "title"
-    }
-  ]
-}