Cobalt Ribbon Pitch Deck

Provide the topic/outline, audience, one desired decision, approximate count and the figures, dates and permitted images that must be accurate. Identify which measures are illustrative and supply their meaning/units. Choose the slide language explicitly if it should differ from the default English.

Outline problem, vision, solution, evidence, roadmap, team and final invitation using the eight recipes as a vocabulary. Adapt length to the brief. Keep the roadmap light and the other pages dark, using the solution card/photo overlap only in its intended role rather than repeating it throughout.

Choose Cobalt Ribbon, Violet Ribbon, Teal Ribbon or Amber Ribbon during generation. Preserve the embedded font pair and 12-column grid: 77px margins, 26px gutters, content roughly y79–634 on the 1280×720 canvas. Use a scrim on the copy side. Titles stay within seven words (cover five), visible page copy within about forty-five, with no more than three blocks and roughly thirty percent empty; detail goes to notes.

Choose suitable library reuse, generate only gaps or regenerate the set, with approved user assets first. The thirteen bundled pictures can be checksum-verified and embedded by the Node helper. Distinguish decorative ribbons from documentary imagery. Team windows can share a deliberate group-photo crop or use approved separate portraits, but fictional sample people must never become real employee identities.

For authorized new pictures, use the available built-in tool or the optional paid FAL helper with FAL_KEY. Record a returned task ID and use status/fetch on that task without automatically resubmitting failures; account limits or charges may apply. Follow the kit’s 16:9/3:2 source aspects and frame crops, keep words outside new art and list unavailable slots rather than claim a complete visual build.

Populate recipes with approved copy, values and notes, resolve example leftovers, then compose/build/check with Python 3. Node belongs to the media-helper path rather than core assembly. Keep fonts/images embedded and the shared editor unchanged. Review factual disclosures even when the restrained visual style leaves little space for a footnote.

Open over local HTTP and inspect every page for legible type over ribbons, chart labels, accurate numbers, crops, block alignment and bounds. Use Edit or E to change wording, images, order and notes; test object changes, undo/redo, Save and reopening. Named accents are generation choices; the shared editor does not include a preset switcher.

Present the HTML or export the requested PPTX/PDF, run check-pptx.py and inspect the result in PowerPoint, Keynote or WPS. Confirm text/notes, rendered charts and actual font substitution before sharing; file creation alone does not verify presentation fidelity or the business case.