@openpresentation/opf 0.10.1 → 0.11.1

package/dist/spec/catalogs/narratives/project-proposal.json

@@ -26,7 +26,7 @@
       "description": "Open with the proposal in one slide: the project name, the audience, the goal, and the headline benefit. If a sponsor reads only this slide, they should still know what they're being asked to approve.",
       "instructions": "Audience hook & objectives",
       "slideType": "text",
-      "layoutHint": "text-1x-left"
+      "layoutHint": "text-1x"
     },
     {
       "id": "problem-statement",
@@ -34,7 +34,7 @@
       "description": "Articulate the problem this project solves and why it deserves resources now. Tie it to a known business goal or pain. Vague problems produce vague approvals.",
       "instructions": "Highlight struggles & project necessity",
       "slideType": "text",
-      "layoutHint": "text-1x-left"
+      "layoutHint": "text-1x"
     },
     {
       "id": "core-concept",
@@ -42,7 +42,7 @@
       "description": "Describe the central idea of the project in plain language. The 'what' before the 'how.' A reader should be able to repeat the concept in one sentence after this slide.",
       "instructions": "Share actionable idea",
       "slideType": "text",
-      "layoutHint": "text-1x-left"
+      "layoutHint": "text-1x"
     },
     {
       "id": "benefits",
@@ -50,7 +50,7 @@
       "description": "Quantify the impact: revenue, cost, risk, customer, capability. Use numbers where possible and clear comparisons where not. Each benefit should map to a metric the sponsor cares about.",
       "instructions": "Spotlight key metrics",
       "slideType": "text",
-      "layoutHint": "text-1x-left"
+      "layoutHint": "text-1x"
     },
     {
       "id": "justification",
@@ -58,7 +58,7 @@
       "description": "Connect the project to broader strategy, OKRs, or constraints the audience already cares about. Show why this project is more important than the alternatives competing for the same resources.",
       "instructions": "Strategic alignment & significance",
       "slideType": "text",
-      "layoutHint": "text-1x-left"
+      "layoutHint": "text-1x"
     },
     {
       "id": "approach",
@@ -66,7 +66,7 @@
       "description": "Lay out how the project will be executed: the solution, the team shape, the budget envelope. Enough detail to feel credible, not so much that it pre-commits to choices that will mature in flight.",
       "instructions": "Solution, resources, & budget",
       "slideType": "text",
-      "layoutHint": "text-1x-left"
+      "layoutHint": "text-1x"
     },
     {
       "id": "timeline",
@@ -74,7 +74,7 @@
       "description": "Show the project phases on a timeline, with major milestones and decision points marked. Sponsors are buying a sequence of bets, not a single launch — make those bets visible.",
       "instructions": "Outline project phases",
       "slideType": "text",
-      "layoutHint": "text-1x-left"
+      "layoutHint": "text-1x"
     },
     {
       "id": "risks",
@@ -82,7 +82,7 @@
       "description": "Name the top risks honestly and pair each with a mitigation or open question. Listing risks without mitigations signals you haven't thought it through; hiding risks signals worse.",
       "instructions": "Consider potential challenges",
       "slideType": "text",
-      "layoutHint": "text-1x-left"
+      "layoutHint": "text-1x"
     },
     {
       "id": "outlook",
@@ -90,13 +90,13 @@
       "description": "Paint the picture of what the organization looks like a quarter or year after the project ships. Stretch beyond the immediate deliverable to the second-order benefits.",
       "instructions": "Envision project impact",
       "slideType": "text",
-      "layoutHint": "text-1x-left"
+      "layoutHint": "text-1x"
     },
     {
       "id": "wrap-up",
       "name": "Wrap Up",
       "description": "Recap the proposal and state the specific decision you're asking for: approval, budget, headcount, sponsorship. Make it easy to say yes today.",
-      "layoutHint": "title-left",
+      "layoutHint": "title",
       "instructions": "Summarize & persuade",
       "slideType": "text"
     }

package/dist/spec/catalogs/narratives/pyramid-principle.json

@@ -0,0 +1,48 @@
+{
+  "$schema": "https://openpresentation.org/schema/opf-narrative/v1",
+  "id": "pyramid-principle",
+  "name": "Pyramid Principle",
+  "summary": "Lead with your conclusion, then provide supporting logic. Respects audience time and attention.",
+  "description": "Lead with the conclusion, then provide the supporting logic. State the main recommendation up front, follow with three or four arguments that support it, then back each argument with data and examples. The tone is deductive: conclusion first, reasoning second, so the audience never waits for the point. Best for executive presentations, recommendations, and time-constrained settings; typical decks run 3-8 slides (consulting recommendation, investment thesis, strategic options analysis).",
+  "audienceFit": [
+    "executive",
+    "board",
+    "time-pressed-decision-makers"
+  ],
+  "durationRange": {
+    "minMinutes": 5,
+    "maxMinutes": 20
+  },
+  "tags": [
+    "executive",
+    "strategy",
+    "deductive",
+    "recommendation"
+  ],
+  "beats": [
+    {
+      "id": "answer-first",
+      "name": "Answer First",
+      "description": "Lead with your main point or recommendation. Don't make executives wait for it.",
+      "instructions": "Lead with the conclusion or recommendation.",
+      "slideType": "text",
+      "layoutHint": "title"
+    },
+    {
+      "id": "key-arguments",
+      "name": "Key Arguments",
+      "description": "Provide 3-4 supporting reasons that logically support your answer.",
+      "instructions": "Group the main reasons supporting the answer.",
+      "slideType": "text",
+      "layoutHint": "text-3x"
+    },
+    {
+      "id": "supporting-evidence",
+      "name": "Supporting Evidence",
+      "description": "Back each argument with data, examples, or proof points.",
+      "instructions": "Back each argument with verifiable proof.",
+      "slideType": "chart",
+      "layoutHint": "chart-1x"
+    }
+  ]
+}

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

@@ -23,7 +23,7 @@
       "id": "objectives",
       "name": "Objectives",
       "description": "Open with what this review is for and what decisions you want out of it. Frame the scope and the hour ahead, so the audience knows what they're being asked to weigh in on.",
-      "layoutHint": "title-center",
+      "layoutHint": "title",
       "instructions": "Set the expectations",
       "slideType": "text"
     },
@@ -53,7 +53,7 @@
       "description": "Name the misses and headwinds honestly. What didn't work, what's still hard, what got harder. Pretending things are fine costs more credibility than acknowledging they aren't.",
       "instructions": "Address difficulties",
       "slideType": "text",
-      "layoutHint": "text-1x-left"
+      "layoutHint": "text-1x"
     },
     {
       "id": "insights",
@@ -79,7 +79,7 @@
       "id": "asks",
       "name": "Asks",
       "description": "Specific, named requests of the audience. Decisions needed, resources required, escalations to unblock. End with clarity on what happens next and who owns it.",
-      "layoutHint": "title-left"
+      "layoutHint": "title"
     }
   ]
 }

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

@@ -26,7 +26,7 @@
       "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",
       "slideType": "text",
-      "layoutHint": "text-1x-left"
+      "layoutHint": "text-1x"
     },
     {
       "id": "inspiration",
@@ -34,7 +34,7 @@
       "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",
       "slideType": "text",
-      "layoutHint": "text-1x-left"
+      "layoutHint": "text-1x"
     },
     {
       "id": "opportunity",
@@ -42,7 +42,7 @@
       "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",
       "slideType": "text",
-      "layoutHint": "text-1x-left"
+      "layoutHint": "text-1x"
     },
     {
       "id": "adversity",
@@ -50,7 +50,7 @@
       "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",
       "slideType": "text",
-      "layoutHint": "text-1x-left"
+      "layoutHint": "text-1x"
     },
     {
       "id": "overcoming",
@@ -58,7 +58,7 @@
       "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",
       "slideType": "text",
-      "layoutHint": "text-1x-left"
+      "layoutHint": "text-1x"
     },
     {
       "id": "impactful-change",
@@ -66,13 +66,13 @@
       "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",
       "slideType": "text",
-      "layoutHint": "text-1x-left"
+      "layoutHint": "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.",
-      "layoutHint": "title-left",
+      "layoutHint": "title",
       "instructions": "Create enduring effect",
       "slideType": "text"
     }

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

@@ -25,7 +25,7 @@
       "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",
       "slideType": "text",
-      "layoutHint": "text-1x-left"
+      "layoutHint": "text-1x"
     },
     {
       "id": "research-exposition",
@@ -33,7 +33,7 @@
       "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",
       "slideType": "text",
-      "layoutHint": "text-1x-left"
+      "layoutHint": "text-1x"
     },
     {
       "id": "real-life-anecdote",
@@ -41,7 +41,7 @@
       "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",
       "slideType": "text",
-      "layoutHint": "text-1x-left"
+      "layoutHint": "text-1x"
     },
     {
       "id": "critical-insights",
@@ -49,7 +49,7 @@
       "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",
       "slideType": "text",
-      "layoutHint": "text-1x-left"
+      "layoutHint": "text-1x"
     },
     {
       "id": "break-stereotypes",
@@ -57,7 +57,7 @@
       "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",
       "slideType": "text",
-      "layoutHint": "text-1x-left"
+      "layoutHint": "text-1x"
     },
     {
       "id": "empowering-advice",
@@ -65,7 +65,7 @@
       "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",
       "slideType": "text",
-      "layoutHint": "text-1x-left"
+      "layoutHint": "text-1x"
     },
     {
       "id": "authenticity",
@@ -73,13 +73,13 @@
       "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",
       "slideType": "text",
-      "layoutHint": "text-1x-left"
+      "layoutHint": "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.",
-      "layoutHint": "title-left",
+      "layoutHint": "title",
       "instructions": "End on a motivational high",
       "slideType": "text"
     }

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

@@ -39,7 +39,7 @@
       "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.",
-      "layoutHint": "title-left"
+      "layoutHint": "title"
     },
     {
       "id": "key-arguments",

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

@@ -0,0 +1,56 @@
+{
+  "$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"
+  ],
+  "durationRange": {
+    "minMinutes": 5,
+    "maxMinutes": 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.",
+      "slideType": "list",
+      "layoutHint": "list-1x"
+    },
+    {
+      "id": "complication",
+      "name": "Complication",
+      "description": "Introduce what has changed or what challenge has emerged.",
+      "instructions": "Introduce the change, risk, or tension.",
+      "slideType": "text",
+      "layoutHint": "text-2x"
+    },
+    {
+      "id": "question",
+      "name": "Question",
+      "description": "Articulate the key question that the complication raises.",
+      "instructions": "Frame the decision question raised by the complication.",
+      "slideType": "text",
+      "layoutHint": "title"
+    },
+    {
+      "id": "answer",
+      "name": "Answer",
+      "description": "Deliver your recommendation or insight that resolves the question.",
+      "instructions": "Deliver the recommendation that resolves the question.",
+      "slideType": "timeline",
+      "layoutHint": "timeline-1x"
+    }
+  ]
+}

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

@@ -0,0 +1,56 @@
+{
+  "$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"
+  ],
+  "durationRange": {
+    "minMinutes": 3,
+    "maxMinutes": 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.",
+      "slideType": "text",
+      "layoutHint": "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.",
+      "slideType": "text",
+      "layoutHint": "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.",
+      "slideType": "text",
+      "layoutHint": "text-1x"
+    },
+    {
+      "id": "proof",
+      "name": "Proof",
+      "description": "Validate the after state with metrics, testimonials, or third-party evidence.",
+      "instructions": "Validate the change with evidence.",
+      "slideType": "metric",
+      "layoutHint": "number-1x"
+    }
+  ]
+}

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

@@ -0,0 +1,56 @@
+{
+  "$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"
+  ],
+  "durationRange": {
+    "minMinutes": 5,
+    "maxMinutes": 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.",
+      "slideType": "text",
+      "layoutHint": "text-1x"
+    },
+    {
+      "id": "task",
+      "name": "Task",
+      "description": "Explain your specific role and responsibilities in this situation.",
+      "instructions": "Explain the responsibility or target outcome.",
+      "slideType": "list",
+      "layoutHint": "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.",
+      "slideType": "timeline",
+      "layoutHint": "timeline-1x"
+    },
+    {
+      "id": "result",
+      "name": "Result",
+      "description": "Share the measurable outcomes and impact of your actions.",
+      "instructions": "Show measurable impact and proof.",
+      "slideType": "metric",
+      "layoutHint": "number-1x"
+    }
+  ]
+}

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

@@ -24,7 +24,7 @@
       "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.",
-      "layoutHint": "title-left",
+      "layoutHint": "title",
       "instructions": "Title & date",
       "slideType": "text"
     },
@@ -34,7 +34,7 @@
       "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",
       "slideType": "text",
-      "layoutHint": "text-1x-left"
+      "layoutHint": "text-1x"
     },
     {
       "id": "progress",
@@ -42,7 +42,7 @@
       "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",
       "slideType": "text",
-      "layoutHint": "text-1x-left"
+      "layoutHint": "text-1x"
     },
     {
       "id": "results",
@@ -50,7 +50,7 @@
       "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",
       "slideType": "text",
-      "layoutHint": "text-1x-left"
+      "layoutHint": "text-1x"
     },
     {
       "id": "action-plan",
@@ -58,13 +58,13 @@
       "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",
       "slideType": "text",
-      "layoutHint": "text-1x-left"
+      "layoutHint": "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.",
-      "layoutHint": "title-left",
+      "layoutHint": "title",
       "instructions": "Ask for response",
       "slideType": "text"
     }

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

@@ -24,7 +24,7 @@
       "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",
+      "layoutHint": "title",
       "instructions": "Brief summary sentence",
       "slideType": "text"
     },
@@ -39,7 +39,7 @@
       "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"
+      "layoutHint": "text-1x"
     },
     {
       "id": "arguments",
@@ -47,7 +47,7 @@
       "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"
+      "layoutHint": "text-1x"
     },
     {
       "id": "argument-1",
@@ -55,7 +55,7 @@
       "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"
+      "layoutHint": "text-1x"
     },
     {
       "id": "argument-2",
@@ -63,7 +63,7 @@
       "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"
+      "layoutHint": "text-1x"
     },
     {
       "id": "argument-3",
@@ -71,13 +71,13 @@
       "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"
+      "layoutHint": "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.",
-      "layoutHint": "title-left",
+      "layoutHint": "title",
       "instructions": "Recap the answer, provide additional resources",
       "slideType": "text"
     }

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

@@ -55,7 +55,7 @@
       "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"
+      "layoutHint": "title"
     }
   ]
 }