@openpresentation/opf 0.10.1 → 0.11.1

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

@@ -26,7 +26,7 @@
       "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"
+      "layoutHint": "text-1x"
     },
     {
       "id": "executive-summary",
@@ -34,7 +34,7 @@
       "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"
+      "layoutHint": "text-1x"
     },
     {
       "id": "context",
@@ -42,7 +42,7 @@
       "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"
+      "layoutHint": "text-1x"
     },
     {
       "id": "data-methodology",
@@ -50,7 +50,7 @@
       "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"
+      "layoutHint": "text-1x"
     },
     {
       "id": "data-summary",
@@ -58,7 +58,7 @@
       "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"
+      "layoutHint": "text-1x"
     },
     {
       "id": "findings",
@@ -66,7 +66,7 @@
       "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"
+      "layoutHint": "text-1x"
     },
     {
       "id": "data-analysis",
@@ -74,7 +74,7 @@
       "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"
+      "layoutHint": "text-1x"
     },
     {
       "id": "implications",
@@ -82,7 +82,7 @@
       "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"
+      "layoutHint": "text-1x"
     },
     {
       "id": "recommendations",
@@ -90,13 +90,13 @@
       "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"
+      "layoutHint": "text-1x"
     },
     {
       "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",
+      "layoutHint": "title",
       "instructions": "Recap and finalize",
       "slideType": "text"
     }

package/dist/spec/catalogs/narratives/survival-story.json

@@ -25,7 +25,7 @@
       "description": "Open in the middle of the disaster. Specific moment, specific stakes, specific damage. Drop the audience into the worst point of the story before walking them back.",
       "instructions": "Present initial disaster",
       "slideType": "text",
-      "layoutHint": "text-1x-left"
+      "layoutHint": "text-1x"
     },
     {
       "id": "backstory",
@@ -33,7 +33,7 @@
       "description": "Detail the events that led up to the catastrophe. Just enough for the audience to understand how the disaster could have happened. Avoid moralizing — the story does the work.",
       "instructions": "Detail past events",
       "slideType": "text",
-      "layoutHint": "text-1x-left"
+      "layoutHint": "text-1x"
     },
     {
       "id": "blueprint",
@@ -41,7 +41,7 @@
       "description": "Illustrate the recovery plan. Specific moves, specific bets, specific people. The audience should see the strategy as more than 'try hard.'",
       "instructions": "Illustrate recovery plans",
       "slideType": "text",
-      "layoutHint": "text-1x-left"
+      "layoutHint": "text-1x"
     },
     {
       "id": "danger",
@@ -49,7 +49,7 @@
       "description": "Highlight the emerging threats to the recovery plan. New risks, returning ones. Tension here makes the eventual triumph credible.",
       "instructions": "Highlight emerging threats",
       "slideType": "text",
-      "layoutHint": "text-1x-left"
+      "layoutHint": "text-1x"
     },
     {
       "id": "endeavor",
@@ -57,7 +57,7 @@
       "description": "Show the determined effort underway. The hours, the trade-offs, the discipline. The audience must feel the work, not just hear about it.",
       "instructions": "Show determination effort",
       "slideType": "text",
-      "layoutHint": "text-1x-left"
+      "layoutHint": "text-1x"
     },
     {
       "id": "struggles",
@@ -65,7 +65,7 @@
       "description": "Showcase challenging moments along the way: the setbacks, the false starts, the hard calls. Honest setbacks make eventual success feel earned.",
       "instructions": "Showcase challenging encounters",
       "slideType": "text",
-      "layoutHint": "text-1x-left"
+      "layoutHint": "text-1x"
     },
     {
       "id": "pivot",
@@ -73,7 +73,7 @@
       "description": "Highlight the strategic shift that changed the trajectory. What got reconsidered, what got dropped, what got doubled down on. The pivot is the moment the protagonist became something new.",
       "instructions": "Highlight strategy shift",
       "slideType": "text",
-      "layoutHint": "text-1x-left"
+      "layoutHint": "text-1x"
     },
     {
       "id": "breakthrough",
@@ -81,7 +81,7 @@
       "description": "Emphasize the moment adversity finally broke. Concrete result, concrete date. Let the slide land — the audience came for this turn.",
       "instructions": "Emphasize overcoming adversity",
       "slideType": "text",
-      "layoutHint": "text-1x-left"
+      "layoutHint": "text-1x"
     },
     {
       "id": "legacy",
@@ -89,13 +89,13 @@
       "description": "Discuss the enduring impact. What survival made possible afterward, who benefited, what was built on top. Survival stories are most powerful when they create more than they restore.",
       "instructions": "Discuss enduring impact",
       "slideType": "text",
-      "layoutHint": "text-1x-left"
+      "layoutHint": "text-1x"
     },
     {
       "id": "takeaway",
       "name": "Takeaway",
       "description": "Share the lesson the audience can carry away. One transferable insight, framed for their own challenges — not a general moral.",
-      "layoutHint": "title-left",
+      "layoutHint": "title",
       "instructions": "Share important lessons",
       "slideType": "text"
     }

package/dist/spec/catalogs/narratives/transformation-arc.json

@@ -44,7 +44,7 @@
       "id": "ask",
       "name": "Ask",
       "description": "Close with the single low-friction action that starts the audience across the bridge. Make it small enough to act on now and meaningful enough to count as commitment.",
-      "layoutHint": "title-left"
+      "layoutHint": "title"
     }
   ]
 }

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

@@ -25,7 +25,7 @@
       "description": "Open by establishing why this trend matters now. Tie it to a decision on the table or a forecast that's about to be made. Trends without consequences are filler.",
       "instructions": "Ignite interest, establish significance",
       "slideType": "text",
-      "layoutHint": "text-1x-left"
+      "layoutHint": "text-1x"
     },
     {
       "id": "historical-comparison",
@@ -33,7 +33,7 @@
       "description": "Contrast current data with the relevant past. Pick the comparison window that makes the trend visible without cherry-picking. Be honest about base effects.",
       "instructions": "Contrast current and past data",
       "slideType": "text",
-      "layoutHint": "text-1x-left"
+      "layoutHint": "text-1x"
     },
     {
       "id": "pattern-identification",
@@ -41,7 +41,7 @@
       "description": "Name the recurring outcome you've spotted. Use one or two strong charts that show the pattern unambiguously. Avoid overclaiming significance from a small N.",
       "instructions": "Point out recurring outcomes",
       "slideType": "text",
-      "layoutHint": "text-1x-left"
+      "layoutHint": "text-1x"
     },
     {
       "id": "future-prediction",
@@ -49,7 +49,7 @@
       "description": "Project where the trend leads if it continues. Show the forecast and the confidence interval. State the assumptions that would have to break for the prediction to fail.",
       "instructions": "Predict using established patterns",
       "slideType": "text",
-      "layoutHint": "text-1x-left"
+      "layoutHint": "text-1x"
     },
     {
       "id": "action-plan",
@@ -57,7 +57,7 @@
       "description": "Translate the prediction into the strategy it implies. Specific actions, sequenced. Each action should map to a particular reading of the trend, not a generic best practice.",
       "instructions": "Strategies based on prediction",
       "slideType": "text",
-      "layoutHint": "text-1x-left"
+      "layoutHint": "text-1x"
     },
     {
       "id": "implementation",
@@ -65,13 +65,13 @@
       "description": "Walk through how the actions get executed: owners, milestones, monitoring. The audience should leave understanding what to do tomorrow, not just what to think about.",
       "instructions": "Discuss strategy execution",
       "slideType": "text",
-      "layoutHint": "text-1x-left"
+      "layoutHint": "text-1x"
     },
     {
       "id": "conclusion",
       "name": "Conclusion",
       "description": "Recap the trend, the forecast, and the recommended action. End with the leading indicator you'll watch to know if the call is right.",
-      "layoutHint": "title-left",
+      "layoutHint": "title",
       "instructions": "Summarize key points",
       "slideType": "text"
     }

package/dist/spec/catalogs/narratives/underdog-victory.json

@@ -25,7 +25,7 @@
       "description": "Establish the opening scene: who the underdog is and the world that overlooked them. Specific details make the rest of the journey feel real.",
       "instructions": "Establish opening scene",
       "slideType": "text",
-      "layoutHint": "text-1x-left"
+      "layoutHint": "text-1x"
     },
     {
       "id": "struggles",
@@ -33,7 +33,7 @@
       "description": "Highlight the early setbacks. What didn't work, who said no, where the path closed up. The audience needs to feel the doubt before they can feel the win.",
       "instructions": "Highlight initial setbacks",
       "slideType": "text",
-      "layoutHint": "text-1x-left"
+      "layoutHint": "text-1x"
     },
     {
       "id": "determination",
@@ -41,7 +41,7 @@
       "description": "Showcase the enduring passion that kept the underdog going. What they refused to give up on, and why. Determination, in this beat, is the only resource the underdog has.",
       "instructions": "Showcase enduring passion",
       "slideType": "text",
-      "layoutHint": "text-1x-left"
+      "layoutHint": "text-1x"
     },
     {
       "id": "crisis",
@@ -49,7 +49,7 @@
       "description": "Identify the lowest point of the journey. The moment the dream nearly ended. Don't soften — the contrast with the triumph ahead depends on the depth of this slide.",
       "instructions": "Identify lowest point",
       "slideType": "text",
-      "layoutHint": "text-1x-left"
+      "layoutHint": "text-1x"
     },
     {
       "id": "resolve",
@@ -57,7 +57,7 @@
       "description": "Articulate the choice the underdog made to keep going. The strong will, the small bet, the borrowed faith. Resolve is where the protagonist becomes someone the audience roots for.",
       "instructions": "Articulate strong will",
       "slideType": "text",
-      "layoutHint": "text-1x-left"
+      "layoutHint": "text-1x"
     },
     {
       "id": "breakthrough",
@@ -65,7 +65,7 @@
       "description": "Show the reward of perseverance: the customer who said yes, the door that opened, the fortune that turned. The breakthrough should feel earned, not granted.",
       "instructions": "Reward of perseverance",
       "slideType": "text",
-      "layoutHint": "text-1x-left"
+      "layoutHint": "text-1x"
     },
     {
       "id": "triumph",
@@ -73,13 +73,13 @@
       "description": "Reveal the ultimate success. Concrete outcomes, named milestones. The triumph is the audience's emotional payoff — let it land.",
       "instructions": "Reveal ultimate success",
       "slideType": "text",
-      "layoutHint": "text-1x-left"
+      "layoutHint": "text-1x"
     },
     {
       "id": "legacy",
       "name": "Legacy",
       "description": "Share the lasting impact. What the underdog's victory makes possible for those who come after. The legacy beat is what turns a story into a lesson.",
-      "layoutHint": "title-left",
+      "layoutHint": "title",
       "instructions": "Share long-lasting impact",
       "slideType": "text"
     }

package/dist/spec/catalogs/narratives/venture-pitch.json

@@ -26,84 +26,84 @@
       "name": "Opening",
       "instructions": "Establish identity",
       "slideType": "text",
-      "layoutHint": "text-1x-left"
+      "layoutHint": "text-1x"
     },
     {
       "id": "purpose",
       "name": "Purpose",
       "instructions": "State your mission",
       "slideType": "text",
-      "layoutHint": "text-1x-left"
+      "layoutHint": "text-1x"
     },
     {
       "id": "problem",
       "name": "Problem",
       "instructions": "Present the challenge",
       "slideType": "text",
-      "layoutHint": "text-1x-left"
+      "layoutHint": "text-1x"
     },
     {
       "id": "solution",
       "name": "Solution",
       "instructions": "Propose your idea",
       "slideType": "text",
-      "layoutHint": "text-1x-left"
+      "layoutHint": "text-1x"
     },
     {
       "id": "why-now",
       "name": "Why Now",
       "instructions": "Explain timing importance",
       "slideType": "text",
-      "layoutHint": "text-1x-left"
+      "layoutHint": "text-1x"
     },
     {
       "id": "market-size",
       "name": "Market Size",
       "instructions": "Demonstrate potential",
       "slideType": "text",
-      "layoutHint": "text-1x-left"
+      "layoutHint": "text-1x"
     },
     {
       "id": "competition",
       "name": "Competition",
       "instructions": "Analyze competitive landscape",
       "slideType": "text",
-      "layoutHint": "text-1x-left"
+      "layoutHint": "text-1x"
     },
     {
       "id": "product",
       "name": "Product",
       "instructions": "Showcase features/benefits",
       "slideType": "text",
-      "layoutHint": "text-1x-left"
+      "layoutHint": "text-1x"
     },
     {
       "id": "business-model",
       "name": "Business Model",
       "instructions": "Detail revenue streams",
       "slideType": "text",
-      "layoutHint": "text-1x-left"
+      "layoutHint": "text-1x"
     },
     {
       "id": "team",
       "name": "Team",
       "instructions": "Highlight key members",
       "slideType": "text",
-      "layoutHint": "text-1x-left"
+      "layoutHint": "text-1x"
     },
     {
       "id": "financials",
       "name": "Financials",
       "instructions": "Show projections/needs",
       "slideType": "text",
-      "layoutHint": "text-1x-left"
+      "layoutHint": "text-1x"
     },
     {
       "id": "closing",
       "name": "Closing",
       "instructions": "Reinforce brand",
       "slideType": "text",
-      "layoutHint": "text-1x-left"
+      "layoutHint": "text-1x"
     }
   ]
 }

package/dist/spec/catalogs/narratives/vision-roadmap.json

@@ -0,0 +1,65 @@
+{
+  "$schema": "https://openpresentation.org/schema/opf-narrative/v1",
+  "id": "vision-roadmap",
+  "name": "Vision to Roadmap",
+  "summary": "Connects a compelling long-term vision to near-term executable plans, bridging aspiration and action.",
+  "description": "Connects a compelling long-term vision to near-term executable plans, bridging aspiration and action. Open with a specific three-to-five-year North Star, honestly diagnose the gap between today and that vision, organize the strategy into two to four named pillars, show the phased roadmap with milestones and dependencies, and end with concrete, assigned first steps for the next 30-90 days. The tone is inspirational and strategic: it creates shared direction and commitment to a plan. Best for strategic planning, annual kickoffs, product strategy, and OKR launches; typical decks run 8-20 slides.",
+  "audienceFit": [
+    "leadership-teams",
+    "board",
+    "product-and-strategy-teams",
+    "all-hands"
+  ],
+  "durationRange": {
+    "minMinutes": 15,
+    "maxMinutes": 45
+  },
+  "tags": [
+    "strategy",
+    "roadmap",
+    "planning",
+    "vision"
+  ],
+  "beats": [
+    {
+      "id": "vision",
+      "name": "Vision",
+      "description": "State the 3-5 year North Star. It should be specific, memorable, and directional rather than generic.",
+      "instructions": "Paint the future state clearly.",
+      "slideType": "text",
+      "layoutHint": "title-subtitle"
+    },
+    {
+      "id": "current-state-gap",
+      "name": "Current State Gap",
+      "description": "Honestly assess where you are today versus the vision. The gap justifies the plan.",
+      "instructions": "Define the gap between today and the vision.",
+      "slideType": "text",
+      "layoutHint": "text-2x"
+    },
+    {
+      "id": "strategic-pillars",
+      "name": "Strategic Pillars",
+      "description": "Organize the strategy into 2-4 named priority themes. Each pillar should be independently compelling.",
+      "instructions": "Name the strategic pillars that close the gap.",
+      "slideType": "text",
+      "layoutHint": "text-3x"
+    },
+    {
+      "id": "roadmap",
+      "name": "Roadmap",
+      "description": "Show the phased execution plan with timeframes, milestones, and dependencies. Gantt or swim lane formats work well.",
+      "instructions": "Sequence the initiatives over time.",
+      "slideType": "timeline",
+      "layoutHint": "timeline-1x"
+    },
+    {
+      "id": "first-steps",
+      "name": "First Steps",
+      "description": "Close with concrete, assigned actions for the next 30-90 days. Remove the gap between inspiration and execution.",
+      "instructions": "Identify the immediate moves that start execution.",
+      "slideType": "text",
+      "layoutHint": "title"
+    }
+  ]
+}

package/dist/spec/catalogs/narratives/weekly-progress.json

@@ -23,7 +23,7 @@
       "id": "opening",
       "name": "Opening",
       "description": "Open with the initiative name, the date, and the one-line headline for the week. Frame the meeting in fifteen seconds so the rest of the time is content.",
-      "layoutHint": "title-left",
+      "layoutHint": "title",
       "instructions": "Initiative name & date",
       "slideType": "text"
     },
@@ -33,7 +33,7 @@
       "description": "State what the team set out to do this week. Specific, measurable. The audience should be able to read this slide alone and know what 'on track' would mean.",
       "instructions": "Set the expectations",
       "slideType": "text",
-      "layoutHint": "text-1x-left"
+      "layoutHint": "text-1x"
     },
     {
       "id": "achievements",
@@ -41,7 +41,7 @@
       "description": "Celebrate the week's wins. Concrete, attributable, dated. Brevity here — the meeting is for what's next, not a victory lap.",
       "instructions": "Celebrate success",
       "slideType": "text",
-      "layoutHint": "text-1x-left"
+      "layoutHint": "text-1x"
     },
     {
       "id": "overall-progress",
@@ -49,7 +49,7 @@
       "description": "Evaluate performance against the objectives. Use a simple status indicator (green/yellow/red) plus the leading metric. Help the audience scan the state in seconds.",
       "instructions": "Evaluate performance",
       "slideType": "text",
-      "layoutHint": "text-1x-left"
+      "layoutHint": "text-1x"
     },
     {
       "id": "challenges",
@@ -57,7 +57,7 @@
       "description": "Address what's hard right now: blockers, slipping items, surfaced risks. Tie each challenge to either an owner working it or a discussion you want this week.",
       "instructions": "Address difficulties",
       "slideType": "text",
-      "layoutHint": "text-1x-left"
+      "layoutHint": "text-1x"
     },
     {
       "id": "opportunities-for-improvement",
@@ -65,7 +65,7 @@
       "description": "Surface where the team can level up. Process tweaks, tooling needs, ways of working. Improvement opportunities should feel like seeds, not corrections.",
       "instructions": "Seek growth",
       "slideType": "text",
-      "layoutHint": "text-1x-left"
+      "layoutHint": "text-1x"
     },
     {
       "id": "highlights-recognition",
@@ -73,7 +73,7 @@
       "description": "Recognize specific contributions by name. Recognition belongs in the deck, not just in the meeting — written acknowledgment travels further than verbal.",
       "instructions": "Appreciate efforts",
       "slideType": "text",
-      "layoutHint": "text-1x-left"
+      "layoutHint": "text-1x"
     },
     {
       "id": "goals-next-week",
@@ -81,7 +81,7 @@
       "description": "Plan the week ahead with three to five specific goals. Each should be small enough to finish, large enough to matter, and clearly owned.",
       "instructions": "Plan ahead",
       "slideType": "text",
-      "layoutHint": "text-1x-left"
+      "layoutHint": "text-1x"
     },
     {
       "id": "discussion-feedback",
@@ -89,13 +89,13 @@
       "description": "Open the floor with two or three prompts — decisions you need, opinions you want, blockers you'd like cleared. End the recap actively.",
       "instructions": "Encourage input",
       "slideType": "text",
-      "layoutHint": "text-1x-left"
+      "layoutHint": "text-1x"
     },
     {
       "id": "conclusion",
       "name": "Conclusion",
       "description": "Close with one line that motivates the team into the next week. Echo the headline so the meeting feels closed.",
-      "layoutHint": "title-left",
+      "layoutHint": "title",
       "instructions": "Recap & motivate",
       "slideType": "text"
     }

package/dist/spec/catalogs/narratives/what-so-what-now-what.json

@@ -0,0 +1,48 @@
+{
+  "$schema": "https://openpresentation.org/schema/opf-narrative/v1",
+  "id": "what-so-what-now-what",
+  "name": "What-So What-Now What",
+  "summary": "Concise framework that connects information to meaning to action. Perfect for executive audiences.",
+  "description": "A concise framework that connects information to meaning to action. Present the facts or findings objectively, explain why they matter to this audience, then state the decisions or next steps they require. The tone is analytical: data-forward and respectful of executive time, with no scene-setting beyond what the facts need. Best for executive briefings, status updates, and research findings; typical decks run 3-6 slides (analytics report, team performance review, strategy update).",
+  "audienceFit": [
+    "executive",
+    "senior-managers",
+    "board"
+  ],
+  "durationRange": {
+    "minMinutes": 5,
+    "maxMinutes": 15
+  },
+  "tags": [
+    "executive",
+    "briefing",
+    "analytical",
+    "action"
+  ],
+  "beats": [
+    {
+      "id": "what",
+      "name": "What",
+      "description": "Present the facts, data, or findings objectively and clearly.",
+      "instructions": "Present the facts, data, or findings objectively and clearly.",
+      "slideType": "chart",
+      "layoutHint": "chart-1x"
+    },
+    {
+      "id": "so-what",
+      "name": "So What",
+      "description": "Explain the significance. Why should your audience care about this information?",
+      "instructions": "Explain the significance. Why should your audience care about this information?",
+      "slideType": "metric",
+      "layoutHint": "number-2x"
+    },
+    {
+      "id": "now-what",
+      "name": "Now What",
+      "description": "Define the action required. What decisions or next steps follow from this?",
+      "instructions": "Define the action required. What decisions or next steps follow from this?",
+      "slideType": "text",
+      "layoutHint": "title"
+    }
+  ]
+}

package/dist/spec/openapi.yaml

@@ -493,6 +493,10 @@ components:
           type: object
           additionalProperties: true
           description: Optional design system (theme, colorScheme, fontScheme, dimensions, background, logo, header, footer, etc).
+        variables:
+          type: object
+          additionalProperties: true
+          description: Optional named color variables referenced from content color fields as `var:<id>` strings.
         assets:
           type: object
           additionalProperties: true
@@ -719,6 +723,7 @@ components:
           type: string
         color:
           type: string
+          description: Hex color, color-scheme slot/role name, or `var:<id>` variable reference (ColorRef in the canonical schema).
         alignment:
           type: string
 

package/dist/spec/reference/engine-defaults.json

@@ -1,5 +1,5 @@
 {
-  "description": "Reference example of engine-side defaults consumed by an OPF runtime. Not part of the OPF document contract - engines load this file (or their own copy) at startup to fall back when an OPF document doesn't specify a value. There is no companion JSON Schema for this file: it is engine config, not a catalog record. Every catalog-referencing value below is resolved through the catalog system the same way an explicit reference in an OPF document would be (inline catalogs.<kind>.records[] -> catalogs.<kind>.source -> default catalog at https://www.pptx.gallery/<kind>). The optional catalogs.<kind>.source overrides below let a deployment redirect all default catalog fetches at once (e.g., to an internal mirror or local package), without each OPF document needing its own catalogs block. The 'chartTypes' array is in priority order: chartTypes[0] is the engine's primary chart type, chartTypes[1] secondary, chartTypes[2] tertiary.",
+  "description": "Reference example of engine-side defaults consumed by an OPF runtime. Not part of the OPF document contract - engines load this file (or their own copy) at startup to fall back when an OPF document doesn't specify a value. There is no companion JSON Schema for this file: it is engine config, not a catalog record. Every catalog-referencing value below is resolved through the catalog system the same way an explicit reference in an OPF document would be (inline catalogs.<kind>.records[] -> catalogs.<kind>.source -> default catalog at https://www.pptx.gallery/<kind>). The optional catalogs.<kind>.source overrides below let a deployment redirect all default catalog fetches at once (e.g., to an internal mirror or local package), without each OPF document needing its own catalogs block. The 'chartTypes' array is in priority order: chartTypes[0] is the engine's primary chart type, chartTypes[1] secondary, chartTypes[2] tertiary. 'fontScheme.pptx' holds the last-resort font scheme that every current engine shares: core pagination, preview, editor and PPTX export all use 'aptos' (exported by @openpresentation/opf as DEFAULT_FONT_SCHEME), so a custom theme without a font scheme is measured, previewed and exported in the same fonts. No current engine reads 'fontScheme.google': it is the intended default for a future Google Slides exporter, whose output renders in Google-hosted fonts.",
 
   "catalogs": {
     "narratives":   { "source": "https://www.pptx.gallery/narratives" },
@@ -29,7 +29,7 @@
   "chartTypes": [
     "stacked-column-3x",
     "stacked-area-3x",
-    "line-with-markers-3x"
+    "line-with-markers"
   ]
 }