@openpresentation/opf 0.10.0 → 0.11.0

package/dist/spec/catalogs/narratives/capacity-planning.json

@@ -24,7 +24,7 @@
       "id": "kickoff",
       "name": "Kickoff",
       "description": "Introduce what the planning exercise covers and the decision you need from the audience. Frame the time horizon and the resources in scope so the rest of the deck stays bounded.",
-      "layoutHint": "title-center",
+      "layoutHint": "title",
       "instructions": "Introduce the topic",
       "slideType": "text"
     },
@@ -34,7 +34,7 @@
       "description": "Show why this is the right moment to plan capacity. Pipeline shifts, hiring freezes, operational stress signals. Urgency turns capacity from an annual ritual into a decision the audience leans into.",
       "instructions": "Show needs",
       "slideType": "text",
-      "layoutHint": "text-1x-left"
+      "layoutHint": "text-1x"
     },
     {
       "id": "situation",
@@ -42,7 +42,7 @@
       "description": "Highlight the current resource picture: people, tools, infrastructure, vendor capacity. Show utilization, not just headcount. The audience should know where slack and stress live today.",
       "instructions": "Highlight current resources",
       "slideType": "text",
-      "layoutHint": "text-1x-left"
+      "layoutHint": "text-1x"
     },
     {
       "id": "projection",
@@ -50,7 +50,7 @@
       "description": "Predict future demand under your base case and a sensitivity case. Tie demand to specific drivers — pipeline, launches, seasonality — so the audience can challenge the assumptions, not just the totals.",
       "instructions": "Predict future demands",
       "slideType": "text",
-      "layoutHint": "text-1x-left"
+      "layoutHint": "text-1x"
     },
     {
       "id": "tactics",
@@ -58,7 +58,7 @@
       "description": "Suggest the strategies for closing any gap: hiring, automation, outsourcing, prioritization. Each tactic should map to a specific demand driver and a defensible cost.",
       "instructions": "Suggest coping strategies",
       "slideType": "text",
-      "layoutHint": "text-1x-left"
+      "layoutHint": "text-1x"
     },
     {
       "id": "implementation",
@@ -66,7 +66,7 @@
       "description": "Discuss how the plan gets deployed. Sequencing, owners, dependencies, lead times. Capacity decisions slip the most when the rollout isn't planned with the same rigor as the sizing.",
       "instructions": "Discuss deployment plans",
       "slideType": "text",
-      "layoutHint": "text-1x-left"
+      "layoutHint": "text-1x"
     },
     {
       "id": "revision",
@@ -74,13 +74,13 @@
       "description": "Define the leading indicators that would trigger a re-plan, and the cadence of review. Capacity plans age fast; show the audience how the plan stays alive.",
       "instructions": "Evaluate and adjust",
       "slideType": "text",
-      "layoutHint": "text-1x-left"
+      "layoutHint": "text-1x"
     },
     {
       "id": "conclusion",
       "name": "Conclusion",
       "description": "Wrap up with the specific recommendations and the decisions you need today. End with the next checkpoint and what evidence will be on the table at it.",
-      "layoutHint": "title-left",
+      "layoutHint": "title",
       "instructions": "Wrap-up & recommendations",
       "slideType": "text"
     }

package/dist/spec/catalogs/narratives/challenge-resolution.json

@@ -26,7 +26,7 @@
       "description": "Open with a specific, visible signal of the challenge — a metric heading the wrong way, a customer story, a competitive event. The hook should make the audience nod that yes, this matters.",
       "instructions": "Capture audience attention",
       "slideType": "text",
-      "layoutHint": "text-1x-left"
+      "layoutHint": "text-1x"
     },
     {
       "id": "dilemma",
@@ -34,7 +34,7 @@
       "description": "State the challenge plainly. What is failing, who is feeling it, and why has it now risen to a level that demands a decision? The dilemma must feel real, not academic.",
       "instructions": "Present the problem",
       "slideType": "text",
-      "layoutHint": "text-1x-left"
+      "layoutHint": "text-1x"
     },
     {
       "id": "backdrop",
@@ -42,7 +42,7 @@
       "description": "Provide the context behind the dilemma: how it formed, what's been tried, what constraints exist. Just enough history that the audience trusts your diagnosis without drowning in detail.",
       "instructions": "Provide context",
       "slideType": "text",
-      "layoutHint": "text-1x-left"
+      "layoutHint": "text-1x"
     },
     {
       "id": "remedy",
@@ -50,7 +50,7 @@
       "description": "Propose the resolution. Lead with the recommendation, then sketch the approach. Be opinionated — vague remedies invite vague responses.",
       "instructions": "Propose a solution",
       "slideType": "text",
-      "layoutHint": "text-1x-left"
+      "layoutHint": "text-1x"
     },
     {
       "id": "evidence",
@@ -58,7 +58,7 @@
       "description": "Demonstrate why the remedy will work. Comparable cases, supporting data, or pilot results. Choose evidence that addresses the audience's most likely objection, not the one easiest to answer.",
       "instructions": "Demonstrate success",
       "slideType": "text",
-      "layoutHint": "text-1x-left"
+      "layoutHint": "text-1x"
     },
     {
       "id": "motivate",
@@ -66,13 +66,13 @@
       "description": "Make the case for acting now. Quantify the cost of delay and the upside of decisive action. Help the audience picture the room a quarter from now if they say yes.",
       "instructions": "Encourage action",
       "slideType": "text",
-      "layoutHint": "text-1x-left"
+      "layoutHint": "text-1x"
     },
     {
       "id": "conclusion",
       "name": "Conclusion",
       "description": "Recap the challenge, the remedy, and the specific decision you need from the audience. End with a clear ask, not a summary slide.",
-      "layoutHint": "title-left",
+      "layoutHint": "title",
       "instructions": "Recap and end powerfully",
       "slideType": "text"
     }

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

@@ -24,7 +24,7 @@
       "description": "Capture attention with a vivid moment, image, or question that sets the world of the story. The audience should immediately know what kind of room they're in. Avoid agendas — the opening is the first scene, not a preamble.",
       "instructions": "Capture audience attention",
       "slideType": "text",
-      "layoutHint": "text-1x-left"
+      "layoutHint": "text-1x"
     },
     {
       "id": "context",
@@ -32,7 +32,7 @@
       "description": "Establish what's normal in this world before anything goes wrong. Just enough background for the audience to feel the stakes when the villain shows up. Keep it tight; backstory is fuel, not the engine.",
       "instructions": "Give background & importance",
       "slideType": "text",
-      "layoutHint": "text-1x-left"
+      "layoutHint": "text-1x"
     },
     {
       "id": "villain",
@@ -40,7 +40,7 @@
       "description": "Introduce the antagonist — a problem, a competitor, a market force, an inertia. Give it a face and a name where you can. The clearer the villain, the more the audience cares about how the story turns out.",
       "instructions": "Introduce problem",
       "slideType": "text",
-      "layoutHint": "text-1x-left"
+      "layoutHint": "text-1x"
     },
     {
       "id": "despair",
@@ -48,7 +48,7 @@
       "description": "Show what's at risk if the villain wins. Emphasize the human or business cost of inaction. Don't rush past this beat — the discomfort here is what makes the resolution land.",
       "instructions": "Emphasize negative impact",
       "slideType": "text",
-      "layoutHint": "text-1x-left"
+      "layoutHint": "text-1x"
     },
     {
       "id": "hero",
@@ -56,7 +56,7 @@
       "description": "Reveal the hero of the story. Often this is the audience themselves, your team, or your product. Frame the hero by what they uniquely bring to the fight, not by their résumé.",
       "instructions": "Present solution",
       "slideType": "text",
-      "layoutHint": "text-1x-left"
+      "layoutHint": "text-1x"
     },
     {
       "id": "plan",
@@ -64,13 +64,13 @@
       "description": "Walk through how the hero defeats the villain. Concrete, sequential, credible. Generic plans signal weak heroes; specific plans earn belief that the ending you're promising is reachable.",
       "instructions": "Detail implementation",
       "slideType": "text",
-      "layoutHint": "text-1x-left"
+      "layoutHint": "text-1x"
     },
     {
       "id": "closing",
       "name": "Closing",
       "description": "End with the resolution and the lesson. Show what the world looks like after the villain loses, and leave the audience with the feeling — and the line — they'll repeat afterwards.",
-      "layoutHint": "title-left",
+      "layoutHint": "title",
       "instructions": "Inspire & conclude",
       "slideType": "text"
     }

package/dist/spec/catalogs/narratives/company-intro.json

@@ -24,7 +24,7 @@
       "id": "logo",
       "name": "Logo",
       "description": "Cover slide with the logo, tagline, and a single line of positioning. Set the visual tone — confident, branded, uncluttered.",
-      "layoutHint": "title-left",
+      "layoutHint": "title",
       "instructions": "Establish brand identity",
       "slideType": "text"
     },
@@ -34,7 +34,7 @@
       "description": "Capture the company in three or four lines: what you do, who you do it for, and how long you've been at it. Avoid jargon; an outsider should grok the business in fifteen seconds.",
       "instructions": "Capture attention",
       "slideType": "text",
-      "layoutHint": "text-1x-left"
+      "layoutHint": "text-1x"
     },
     {
       "id": "competitive-advantage",
@@ -42,7 +42,7 @@
       "description": "State the one or two things you do that the alternatives can't. Frame it as a structural advantage, not a feature list. The audience should leave able to repeat the differentiator in their own words.",
       "instructions": "Stand out",
       "slideType": "text",
-      "layoutHint": "text-1x-left"
+      "layoutHint": "text-1x"
     },
     {
       "id": "company-story",
@@ -50,7 +50,7 @@
       "description": "Share the founding insight or origin moment — why this company exists, told as a short story. Specific people, specific problems, a specific 'aha.' Story beats biography.",
       "instructions": "Share origin",
       "slideType": "text",
-      "layoutHint": "text-1x-left"
+      "layoutHint": "text-1x"
     },
     {
       "id": "offerings",
@@ -58,7 +58,7 @@
       "description": "Map the products and services into a coherent picture. Show how they fit together rather than listing them flat. The shape of the portfolio is itself a message.",
       "instructions": "Highlight products/services",
       "slideType": "text",
-      "layoutHint": "text-1x-left"
+      "layoutHint": "text-1x"
     },
     {
       "id": "ideal-customer",
@@ -66,7 +66,7 @@
       "description": "Define who you serve best. Industry, size, role, situation. Specificity here helps the audience self-select and signals you understand the customer well enough to be choosy.",
       "instructions": "Define target market",
       "slideType": "text",
-      "layoutHint": "text-1x-left"
+      "layoutHint": "text-1x"
     },
     {
       "id": "key-benefits",
@@ -74,7 +74,7 @@
       "description": "Translate offerings into three to five customer outcomes. Lead with the result, not the mechanism. Each benefit should answer 'what becomes easier or better for me?'",
       "instructions": "Emphasize value",
       "slideType": "text",
-      "layoutHint": "text-1x-left"
+      "layoutHint": "text-1x"
     },
     {
       "id": "success-story",
@@ -82,13 +82,13 @@
       "description": "Tell one named customer's story with concrete before/after metrics. A single specific story is more persuasive than a logo grid; pick one that mirrors the audience you're presenting to.",
       "instructions": "Showcase satisfied customer",
       "slideType": "text",
-      "layoutHint": "text-1x-left"
+      "layoutHint": "text-1x"
     },
     {
       "id": "closing-cta",
       "name": "Closing & CTA",
       "description": "Close with one line of why now and one specific next step — a discovery call, a pilot, a partner program. End with contact info that's easy to act on without searching.",
-      "layoutHint": "title-left",
+      "layoutHint": "title",
       "instructions": "Encourage action",
       "slideType": "text"
     }

package/dist/spec/catalogs/narratives/conference-talk.json

@@ -48,7 +48,7 @@
       "id": "recap",
       "name": "Recap",
       "description": "Restate the promise, the mechanism, and the call to action in a single short slide. Give the audience the line they'll repeat to a colleague and the one image that will stick with them after the lights come up.",
-      "layoutHint": "title-left"
+      "layoutHint": "title"
     }
   ]
 }

package/dist/spec/catalogs/narratives/early-startup-pitch.json

@@ -23,7 +23,7 @@
       "id": "logo",
       "name": "Logo",
       "description": "Cover slide with the company name, logo, and one-line positioning. Simple, branded, confident.",
-      "layoutHint": "title-left",
+      "layoutHint": "title",
       "instructions": "Establish presence",
       "slideType": "text"
     },
@@ -33,7 +33,7 @@
       "description": "Open by naming a large, undeniable shift in the world. Tech, regulatory, behavioral. The shift is the reason this company exists — investors should feel its weight before they hear about the product.",
       "instructions": "Highlight market transformation",
       "slideType": "text",
-      "layoutHint": "text-1x-left"
+      "layoutHint": "text-1x"
     },
     {
       "id": "past-struggle",
@@ -41,7 +41,7 @@
       "description": "Show what the world tried to do about the problem before the shift, and why those approaches fell short. Honest credit to predecessors makes the new game more credible.",
       "instructions": "Emphasize previous challenges",
       "slideType": "text",
-      "layoutHint": "text-1x-left"
+      "layoutHint": "text-1x"
     },
     {
       "id": "innovative-breakthrough",
@@ -49,7 +49,7 @@
       "description": "Present the founding insight or breakthrough that makes a new approach possible. This is the 'secret' the company is built on — name it plainly.",
       "instructions": "Present innovative solution",
       "slideType": "text",
-      "layoutHint": "text-1x-left"
+      "layoutHint": "text-1x"
     },
     {
       "id": "unique-offering",
@@ -57,7 +57,7 @@
       "description": "Detail the product or service. Lead with the customer-visible thing they touch; the architecture can wait. Show why this offering is structurally different from the past struggle.",
       "instructions": "Detail product or service",
       "slideType": "text",
-      "layoutHint": "text-1x-left"
+      "layoutHint": "text-1x"
     },
     {
       "id": "costly-issues",
@@ -65,7 +65,7 @@
       "description": "Quantify the pain customers experience without your offering. Time, dollars, opportunity cost. Specific numbers convert sympathy into urgency.",
       "instructions": "Quantify problems faced",
       "slideType": "text",
-      "layoutHint": "text-1x-left"
+      "layoutHint": "text-1x"
     },
     {
       "id": "effective-solutions",
@@ -73,7 +73,7 @@
       "description": "Demonstrate the customer outcome your offering produces. Before/after numbers from early users, even small N. Early-stage pitches are won by leading indicators, not by trailing ones.",
       "instructions": "Demonstrate benefits",
       "slideType": "text",
-      "layoutHint": "text-1x-left"
+      "layoutHint": "text-1x"
     },
     {
       "id": "unit-economics",
@@ -81,7 +81,7 @@
       "description": "Explain the financial model. Cost to acquire, gross margin, payback. Investors don't expect maturity — they expect that you've thought about it.",
       "instructions": "Explain financial model",
       "slideType": "text",
-      "layoutHint": "text-1x-left"
+      "layoutHint": "text-1x"
     },
     {
       "id": "talented-team",
@@ -89,7 +89,7 @@
       "description": "Introduce the founders and key early hires. Show why this team uniquely sees and can execute on this opportunity. Insight beats résumé at the seed stage.",
       "instructions": "Introduce key players",
       "slideType": "text",
-      "layoutHint": "text-1x-left"
+      "layoutHint": "text-1x"
     },
     {
       "id": "traction",
@@ -97,7 +97,7 @@
       "description": "Showcase the early signal: pilots, design partners, waitlist, retention data, anything credible. Frame it honestly — investors at this stage discount inflation aggressively.",
       "instructions": "Showcase accomplishments",
       "slideType": "text",
-      "layoutHint": "text-1x-left"
+      "layoutHint": "text-1x"
     },
     {
       "id": "investment-opportunity",
@@ -105,13 +105,13 @@
       "description": "Detail the round size, structure, and use of funds. Tie the raise to specific milestones it takes the company to. Specificity here signals operational maturity.",
       "instructions": "Detail funding needs",
       "slideType": "text",
-      "layoutHint": "text-1x-left"
+      "layoutHint": "text-1x"
     },
     {
       "id": "closing-logo",
       "name": "Closing Logo",
       "description": "Close on the brand and contact info. Leave the room with the line you most want repeated when the partner pitches you to the rest of the firm.",
-      "layoutHint": "title-left",
+      "layoutHint": "title",
       "instructions": "Leave a lasting impression",
       "slideType": "text"
     }

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

@@ -25,7 +25,7 @@
       "description": "Introduce the topic in a way that respects the audience's time and curiosity. Frame why this question is worth asking, and signal the shape of the journey ahead without giving away the destination.",
       "instructions": "Introduce the topic",
       "slideType": "text",
-      "layoutHint": "text-1x-left"
+      "layoutHint": "text-1x"
     },
     {
       "id": "surprising-fact",
@@ -33,7 +33,7 @@
       "description": "Lead with a single curious fact that recasts how the audience thinks about the topic. The fact should be small, specific, and unforgettable — the cognitive door the rest of the talk walks through.",
       "instructions": "Share a curious fact",
       "slideType": "text",
-      "layoutHint": "text-1x-left"
+      "layoutHint": "text-1x"
     },
     {
       "id": "experiment",
@@ -41,7 +41,7 @@
       "description": "Walk through a method, study, or thought experiment that probes the surprising fact. Show how knowledge here gets made — the audience should feel like they're shoulder-to-shoulder with the investigator.",
       "instructions": "Explain a tried method",
       "slideType": "text",
-      "layoutHint": "text-1x-left"
+      "layoutHint": "text-1x"
     },
     {
       "id": "amusing-anecdote",
@@ -49,7 +49,7 @@
       "description": "Drop in a story or moment from the field that brings the topic to human scale. Personality and humor here keep the audience leaning forward; technical depth without warmth loses the room.",
       "instructions": "Relay an interesting story",
       "slideType": "text",
-      "layoutHint": "text-1x-left"
+      "layoutHint": "text-1x"
     },
     {
       "id": "intriguing-information",
@@ -57,7 +57,7 @@
       "description": "Layer in the more complex data or detail. By this point the audience is invested enough to do real work alongside you. Visualize generously — make the numbers tangible.",
       "instructions": "Share complex data",
       "slideType": "text",
-      "layoutHint": "text-1x-left"
+      "layoutHint": "text-1x"
     },
     {
       "id": "skeptical-scrutiny",
@@ -65,7 +65,7 @@
       "description": "Question the easy interpretations. Challenge the audience's defaults and your own. Showing where the evidence is contested is what separates a teacher from a publicist.",
       "instructions": "Encourage questioning of accepted truths",
       "slideType": "text",
-      "layoutHint": "text-1x-left"
+      "layoutHint": "text-1x"
     },
     {
       "id": "extraordinary-explanation",
@@ -73,7 +73,7 @@
       "description": "Present the most counterintuitive or beautiful explanation the topic offers. Take your time here — this is the payoff slide the audience came for.",
       "instructions": "Break down unusual research findings",
       "slideType": "text",
-      "layoutHint": "text-1x-left"
+      "layoutHint": "text-1x"
     },
     {
       "id": "unconventional-use",
@@ -81,13 +81,13 @@
       "description": "Show an unexpected application or implication of the idea. Surprise reinforces the lesson and gives the audience a story to retell tomorrow.",
       "instructions": "Expand on unique aspects",
       "slideType": "text",
-      "layoutHint": "text-1x-left"
+      "layoutHint": "text-1x"
     },
     {
       "id": "captivating-conclusion",
       "name": "Captivating Conclusion",
       "description": "Close with a thoughtful, slightly poetic wrap-up. Echo the surprising fact, name the lesson, and leave the audience with a new question instead of a tidy answer.",
-      "layoutHint": "title-left",
+      "layoutHint": "title",
       "instructions": "Provide a thoughtful wrap-up",
       "slideType": "text"
     }

package/dist/spec/catalogs/narratives/employee-review.json

@@ -23,7 +23,7 @@
       "id": "introduction",
       "name": "Introduction",
       "description": "Open with the period covered and the spirit of the conversation: collaborative, honest, growth-focused. Frame the meeting so both sides know what to expect.",
-      "layoutHint": "title-left",
+      "layoutHint": "title",
       "instructions": "Name & date",
       "slideType": "text"
     },
@@ -33,7 +33,7 @@
       "description": "Review job execution against the role's expectations. Specific examples, dated. Avoid characterizing the person; describe the work and its impact.",
       "instructions": "Review job execution",
       "slideType": "text",
-      "layoutHint": "text-1x-left"
+      "layoutHint": "text-1x"
     },
     {
       "id": "achievements",
@@ -41,7 +41,7 @@
       "description": "Acknowledge what went well. Name the projects, the moves, the moments where the employee made a difference. Specific recognition lands harder than generic praise.",
       "instructions": "Acknowledge success",
       "slideType": "text",
-      "layoutHint": "text-1x-left"
+      "layoutHint": "text-1x"
     },
     {
       "id": "feedback",
@@ -49,7 +49,7 @@
       "description": "Provide constructive feedback grounded in observation. Distinguish patterns from one-offs. Tell the employee something they can act on, not something they can only feel.",
       "instructions": "Provide positive remarks",
       "slideType": "text",
-      "layoutHint": "text-1x-left"
+      "layoutHint": "text-1x"
     },
     {
       "id": "constructive-criticism",
@@ -57,7 +57,7 @@
       "description": "Suggest improvements in language that respects the employee's intelligence. Pair each piece of criticism with a concrete example and a specific behavior change you'd like to see.",
       "instructions": "Suggest improvements",
       "slideType": "text",
-      "layoutHint": "text-1x-left"
+      "layoutHint": "text-1x"
     },
     {
       "id": "development-opportunities",
@@ -65,7 +65,7 @@
       "description": "Highlight growth areas and the experiences that could stretch the employee. Frame development as an investment, not a fix.",
       "instructions": "Highlight growth areas",
       "slideType": "text",
-      "layoutHint": "text-1x-left"
+      "layoutHint": "text-1x"
     },
     {
       "id": "goals",
@@ -73,13 +73,13 @@
       "description": "Outline next-period goals together. Specific, measurable, with explicit support. The strongest goals are co-authored, not handed down.",
       "instructions": "Outline next steps",
       "slideType": "text",
-      "layoutHint": "text-1x-left"
+      "layoutHint": "text-1x"
     },
     {
       "id": "mentoring",
       "name": "Mentoring",
       "description": "Encourage continued learning through mentorship, training, peer pairings. Close the review with the message that growth is a shared responsibility, not a one-way evaluation.",
-      "layoutHint": "title-left",
+      "layoutHint": "title",
       "instructions": "Encourage continuous learning",
       "slideType": "text"
     }

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

@@ -26,7 +26,7 @@
       "description": "Set an empathetic, accountable tone before any analysis. Acknowledge the impact on the people in the room and the customers affected. Authenticity here earns you the credibility you'll need for the rest of the deck.",
       "instructions": "Set an empathetic tone",
       "slideType": "text",
-      "layoutHint": "text-1x-left"
+      "layoutHint": "text-1x"
     },
     {
       "id": "incident-breakdown",
@@ -34,7 +34,7 @@
       "description": "Walk through what happened, in time order. Stick to facts: what systems, what users, what timeline. No causal claims yet — just an accurate, neutral reconstruction the audience can trust.",
       "instructions": "Detail the failure",
       "slideType": "text",
-      "layoutHint": "text-1x-left"
+      "layoutHint": "text-1x"
     },
     {
       "id": "impact-analysis",
@@ -42,7 +42,7 @@
       "description": "Quantify the damage. Customer-hours lost, revenue at risk, SLA breaches, downstream knock-ons. Be specific and direct; vague impact statements undermine the rest of the post-mortem.",
       "instructions": "Describe failure's effects",
       "slideType": "text",
-      "layoutHint": "text-1x-left"
+      "layoutHint": "text-1x"
     },
     {
       "id": "root-cause",
@@ -50,7 +50,7 @@
       "description": "Trace the failure to its underlying cause, not the most visible symptom. Use a 'five whys' or fishbone framing if useful. Distinguish between the proximate trigger and the systemic conditions that allowed it.",
       "instructions": "Analyze underlying reasons",
       "slideType": "text",
-      "layoutHint": "text-1x-left"
+      "layoutHint": "text-1x"
     },
     {
       "id": "proposed-solutions",
@@ -58,7 +58,7 @@
       "description": "Present the corrective actions you're taking. Lead with the highest-leverage fix; sequence the rest. For each action, name an owner and a date — solutions without owners are aspirations.",
       "instructions": "Suggest corrective measures",
       "slideType": "text",
-      "layoutHint": "text-1x-left"
+      "layoutHint": "text-1x"
     },
     {
       "id": "action-plan",
@@ -66,7 +66,7 @@
       "description": "Lay out the rollout: what ships when, how it's verified, who signs off. Show that 'fixed' has a definition and a deadline, not just intent.",
       "instructions": "Map out steps",
       "slideType": "text",
-      "layoutHint": "text-1x-left"
+      "layoutHint": "text-1x"
     },
     {
       "id": "evaluate-outcome",
@@ -74,7 +74,7 @@
       "description": "Define the metrics that will tell you the fix worked. Pre/post comparisons, monitoring SLOs, error budgets — whatever proves the failure mode is closed and not just deferred.",
       "instructions": "Assess corrective actions",
       "slideType": "text",
-      "layoutHint": "text-1x-left"
+      "layoutHint": "text-1x"
     },
     {
       "id": "lessons-learned",
@@ -82,7 +82,7 @@
       "description": "Distill the broader lessons that outlive this specific incident. What does the team or organization now know that it didn't before? What patterns will you watch for elsewhere?",
       "instructions": "Reflect on failure lessons",
       "slideType": "text",
-      "layoutHint": "text-1x-left"
+      "layoutHint": "text-1x"
     },
     {
       "id": "preventive-measures",
@@ -90,13 +90,13 @@
       "description": "List the systemic safeguards being added — process changes, automated checks, on-call procedures, review gates. Show how this category of failure becomes harder to recur, not just this specific instance.",
       "instructions": "List safeguards",
       "slideType": "text",
-      "layoutHint": "text-1x-left"
+      "layoutHint": "text-1x"
     },
     {
       "id": "closing-thoughts",
       "name": "Closing Thoughts",
       "description": "Close with humility and forward momentum. Re-affirm accountability, thank the audience for their patience, and signal confidence in the path forward without overclaiming.",
-      "layoutHint": "title-left",
+      "layoutHint": "title",
       "instructions": "Empathize, trust, and encourage",
       "slideType": "text"
     }