Refine this existing three-slide briefing while preserving its content. Selected route: LAYOUT PROPOSAL ONLY. Goal: make the existing information easier to scan through consistent hierarchy, alignment and grouping. Do not develop a new narrative. BASELINE AND INPUTS The supplied baseline is the authored static model in s1-before.svg, s2-before.svg and s3-before.svg, in that order. objects-before.json lists its objects. fixed-content.json is the content authority; it was fixed before the drawings. The source records below are fictional editorial materials, not actual workshop or customer records. No native PPTX is supplied, and the SVG IDs are not native slide object IDs. Use only this packet. Do not fetch other material or add product claims. SOURCE RECORDS C1, Coordinator brief: The workshop has two sessions: Morning and Afternoon. R1, Request register, row 1: Morning: 3 seats requested. R2, Request register, row 2: Afternoon: 2 seats requested. D1, Decision log, item 1: Decision needed: confirm trainer. Current trainer status: Unknown. T1, authored manual derivation: 3 + 2 = 5 seat requests across sessions. This is not a count of distinct people, attendance or confirmed bookings. EXACT COPY AND READING ORDER Slide 1: s1-title: Workshop overview s1-sessions: Two sessions s1-total: Five seats requested in total s1-source: Sources: C1; R1-R2; T1 Slide 2: s2-title: Seat requests s2-morning-label: Morning s2-morning-value: 3 seats requested s2-afternoon-label: Afternoon s2-afternoon-value: 2 seats requested s2-total: Total: 5 seats requested s2-source: Sources: R1-R2; T1 (3 + 2 = 5) Slide 3: s3-title: Decision needed s3-action: Confirm trainer s3-status: Current status: Unknown s3-source: Source: D1 OBJECTS AND ALLOWED CHANGES Retain every text object listed above as a separate text object. Keep its ID, exact wording and punctuation, source binding and reading order. Retain these decorative rectangles: s1-background, s1-panel; s2-background, s2-morning-panel, s2-afternoon-panel; s3-background, s3-panel. They do not represent quantities or status. There are 15 text objects and 7 rectangles in each authored state. Do not add, delete, merge or duplicate objects. Do not flatten text to an image or convert it to paths. No charts, photos, check marks or new data. You may move/resize inventoried boxes and rectangles and change their font size, weight, text color, fill or stroke. Keep 1280 x 720 SVG units. Use Arial, sans-serif. Proposed common roles: title 48 bold; body 36 regular; source caption 22 regular. Text #263442, captions #526273, slide #FBFCFD, decorative panels #EEF3F7. No status color coding. Title anchors: x80/y125; source anchors: x80/y660 (text baselines). Slide 1: align both body texts at x104; baselines y280 and y390. Put the existing panel at x80/y210, width1120/height240. Slide 2: put both existing panels at y200, width520/height200; Morning panel x80, Afternoon panel x680. Morning text x104; Afternoon text x704; label baselines y260 and value baselines y340 for both. Put the existing total at x80/y520. Equal panel sizes group records; they must not imply that the seat counts are equal or proportional. Slide 3: put action and status at x104, baselines y280 and y390. Put the existing panel at x80/y210, width1120/height240. RETURN FOR THIS SELECTED ROUTE Return three proposed SVGs plus their object inventory and attribute diff from the baseline, and readable previews. Keep the original files. Explain any conflict instead of silently changing content. Mark these as authored static proposals. They do not demonstrate native PowerPoint objects, PowerPoint editability, export fidelity or a completed file edit. IF I EXPLICITLY CHANGE THE SELECTED ROUTE TO NATIVE FILE EDITING First identify the supplied master file/revision and confirm the actual reader/editor can read and write its required object types. Use a copy. Map the synthetic IDs to observed native objects by slide, exact text and location; report ambiguous or missing matches before editing. Do not invent IDs or claim that importing an SVG establishes this map. If the required native object support cannot be established, return the proposal and the limitation. Do not replace the deck with slide images. Return a separately named native candidate and before/after object map, preserved/changed content report, previews and explicit untested features. Do not claim the human's editor checks have passed. The owner will select and edit sample text and shapes, undo the probes, save/close/reopen, and compare wording, source captions, slide order and appearance to the master. No change to Unknown or to 3/2/5 is authorized in either route.