Can AI build consultant-grade decks?

Create one editable eight-slide PowerPoint deck for the management board of a German industrial manufacturer that ships most of its finished goods by road.

Follow the storyline in source/briefing-notes.md exactly, in the order given. Each numbered section of the briefing notes becomes one slide, in sequence:
1. why the board is being asked to look at transport mode now;
2. how freight splits across modes in Germany today;
3. how that split has moved since 2008;
4. how Germany compares with the EU27 average;
5. what the rail share means for the company's decarbonisation commitments;
6. the operational barriers to shifting volume to rail;
7. a staged shift-to-rail approach;
8. the decision the board is asked to make.

Use only the supplied case files. Build the mode-share trend and the Germany-versus-EU27 comparison as native, editable PowerPoint charts driven by the values in source/freight-modal-split.csv. Every number that appears on a slide must be present in the supplied files; do not invent tonnages, costs, emissions figures, customer names, or measured outcomes. Keep facts, estimates, and recommendations visibly distinct. Put source provenance in the speaker notes of every slide that makes a data-backed claim, wrapped in a [Sources] ... [/Sources] block.

Design contract, to be followed exactly: white background; dark grey body text; one deep-blue accent colour used for emphasis and chart series; a single thin rule under each slide title; left-aligned text; body text no smaller than 14pt. Slide titles must be full sentences that state the takeaway, not topic labels. No gradients, no stock or generated imagery, no decorative icons, no pill-shaped badges, no repeated dashboard cards.

Save the required artifact exactly at output/deck.pptx, relative to your current working directory. Do not ask questions. Do not send a follow-up message. Do not use skills, plugins, custom benchmark instructions, or general web access.

You are preparing a point-of-view deck for the operations leadership of a logistics consultancy.

Analyse the monthly German truck toll mileage index in source/lkw-maut-monthly.csv and answer one question: what has happened to German road freight activity since 2008, and what should our industrial clients take from it?

The storyline is not given to you. Work out from the data itself which movements matter — the turning points, the sustained trends, the level the index returns to — and build the deck around what you find. Decide the structure yourself.

Read source/index-methodology.md before interpreting the series. The index measures activity, not tonnage or revenue, and the adjusted and unadjusted columns answer different questions; choose deliberately which one each chart uses and say which you used.

Constraints on claims. Every figure on a slide must be computed from the supplied CSV or stated in the methodology note. You may not attribute a movement in the index to any external event, policy, or economic condition as established fact, because no such information is supplied — where you offer an explanation, mark it clearly as interpretation and keep it visibly separate from what the data shows. Do not invent tonnages, freight rates, company names, client outcomes, or forecasts.

Deliverable: one editable PowerPoint deck of six to ten slides, saved exactly at output/deck.pptx relative to your current working directory. Use native, editable PowerPoint charts built from the supplied values — at least one chart of the full series. Slide titles should state the takeaway as a full sentence. Put source provenance in the speaker notes of every slide that makes a data-backed claim, wrapped in a [Sources] ... [/Sources] block.

Choose a professional design yourself: it should look like something a technology and logistics consultancy would put in front of a client. Do not ask questions. Do not send a follow-up message. Do not use skills, plugins, custom benchmark instructions, or general web access.

Our client sent over the attached files ahead of Monday's steering meeting. They want to know what is going on in their shipment operations and what to do about it.

Put together a deck of six to ten slides, saved exactly at output/deck.pptx relative to your current working directory.

Work only from the supplied files. Where they disagree with each other, say so on the slide rather than picking a number silently. Do not invent figures, customer names, service levels, or outcomes that are not in the files.

Design is up to you. It should look like something a technology and logistics consultancy would put in front of a client. Do not ask questions. Do not send a follow-up message. Do not use skills, plugins, custom benchmark instructions, or general web access.

Create one editable eight-slide PowerPoint deck for the CEO, CHRO, COO, and technology leadership of Meridian Signal. The theme is how AI is changing the modern workforce: not simply by removing jobs, but by redistributing tasks, decision rights, skills, and accountability.

Use source/workforce-transition-brief.md, source/org-structures.csv, and source/work-activity-shifts.csv as the complete evidence base. Treat the proposed future organization and activity mix as a planning scenario, not as a forecast or a measured outcome. Do not introduce external statistics, named companies, workforce reductions, productivity claims, or implementation results.

Build this eight-slide narrative:
1. the executive thesis on how AI changes work and organization design;
2. which activities are automated, augmented, or remain human-led, using a native editable chart built from source/work-activity-shifts.csv;
3. "Before AI" — a native editable organization chart of the current structure in source/org-structures.csv;
4. "After AI" — a separate native editable organization chart of the proposed AI-enabled structure in source/org-structures.csv;
5. how roles, skills, and management responsibilities change;
6. the governance model that keeps humans accountable for decisions and exceptions;
7. the 90-day transition plan in the source brief;
8. the executive decisions required now.

The two organization charts must be on separate slides, use native PowerPoint shapes and connectors, show the reporting hierarchy clearly, and remain fully editable. Label the slides with the exact phrases "Before AI" and "After AI". Make clear that the after-state is proposed and that the scenario keeps total workforce at 420 while reallocating 16 roles across functions; do not imply layoffs.

The supplied Meridian Signal design system is mandatory, not optional. Start from reference/Meridian-Signal-Slide-Design-Templates.pptx or reference/Meridian-Signal-Master.potx and preserve the embedded Meridian Signal master and layouts. Use reference/Meridian-Signal-Master.pptx, reference/Meridian-Signal-Design-System.md, and the PNGs under reference/master-preview/ to understand the intended layouts. Select and adapt appropriate slide-library patterns rather than drawing an unrelated theme. Remove all bracketed instructional placeholders and sample data from copied templates.

Follow the Meridian visual language throughout: warm cream and beige surfaces, selective charcoal section fields, graphite structure, Golden Gate orange emphasis, Arial typography, disciplined left alignment and grid spacing, hairline rules, two-part content-slide titles, and restrained native diagrams and charts. Avoid gradients, purple or blue AI styling, robot or sparkle imagery, repeated dashboard cards, pills, decorative icons, heavy shadows, and text below the 11pt floor.

Put source provenance in the speaker notes of every slide, wrapped in a [Sources] ... [/Sources] block. Cite the exact local files used on each slide; cite the Meridian reference file or design contract when a visual pattern is adapted.

Save the required artifact exactly at output/deck.pptx, relative to your current working directory. Do not ask questions. Do not send a follow-up message. Do not use skills, plugins, custom benchmark instructions, or general web access.