Article Brief Deck

Provide the approved article and reference links, audience, learning/decision goal, speaking duration and target slide count. Identify approved claims, data, quotations and images, the requested preset, disclosure rules, note requirements and review owner. Build the source ledger before drafting so a supplied fact, an assumption and a rights question cannot merge into one confident sentence.

Outline the thesis, a few argument beats, selected evidence and the closing discussion. Compose six to ten pages unless the agreed brief calls for a deliberate adjustment; give every page one job and three to five useful talking points. Keep unresolved evidence visibly pending and preserve the article’s qualifications when shortening a quotation or explanation.

Select Field Note, Night Review or High Contrast and populate the style-kit recipes. Replace the fictional demonstration value and all example claims, sources, notes, labels and disclosure text. Complete the argument using built-in treatments first; an attractive photograph must not imply a finding missing from the article.

Choose an image path: reuse suitable library pictures, reuse and generate only gaps, or regenerate the set. Supplied approved images take priority in every path; default to reuse when no preference is available. The three shipped images are all topic-specific to library renovation/interior fit-out, so use them only when that topic fits and do not repeat one on multiple pages. Otherwise keep a labeled frame or use approved new imagery rather than silently inserting unrelated library scenes.

Use Node.js 20+ to list/embed library IDs with scripts/embed-library-images.mjs; the helper verifies each picture against its catalog hash and inlines it into project.json. Optional generation follows the image brief at the slot’s 16:9 aspect: FAL uses a paid submit/status/fetch task with FAL_KEY and no automatic failure retries; a built-in image tool is another supported path. If generation is unavailable, return to suitable existing pictures or list unfilled frames. New pictures should remain illustrative, distinct and free of embedded slide text.

Compose the plan, fill required images and inspect leftover-example reports, then build and check with Python 3 and the style kit. Keep the shared editor unchanged, final assets embedded and interface language independent of content language. The build uses bundled runtime assets; Node is needed for the image-helper paths rather than the core Python assembly.

Open over local HTTP and verify claims, quote attribution, pending labels, contrast, crops, page bounds and notes. Use Edit or E to revise wording, replace pictures and reorder or duplicate pages; test Save, undo/redo and reopening the saved HTML. Export PPTX/PDF from the standalone file, run check-pptx.py and compare in the target presentation application before human factual, rights and accessibility sign-off.