A chart is not its source
A chart or slide deck can look finished while being difficult to revise, verify, or hand to someone else. The missing piece is usually not another export. It is a compact packet that keeps the source facts, transformation, presentation source, rendered deliverable, and review evidence connected.
This is a method, not a tool comparison or a performed build. Matplotlib, Marp CLI, and PPT Master illustrate three different artifact contracts. None was installed or run for this article, and no output-quality, compatibility, performance, or deterministic-build result is claimed.
Five layers, five different questions
- Source facts. What data and assertions entered the work?
- Transformation. What code, settings, and versions changed them?
- Presentation source. Where do narrative, layout, and accessibility choices live?
- Rendered deliverable. Which exact file will the reader receive?
- Review evidence. What did a person inspect, in which viewer, and what remains open?
The layers should be linked, not collapsed. A PNG cannot reveal the data transformation that produced it. Markdown slide source may be easy to diff while its PDF rendering still depends on browser, theme, and font behavior. An editable presentation file can expose native objects without preserving why a chart says what it says.
Three artifact contracts
| Contract | What the official source establishes | What the packet still has to preserve |
|---|---|---|
| Programmatic chart | Matplotlib documents saving figures in formats including PNG, PDF, and SVG. | Input data, chart code, version, parameters, labels/alt description, output hash, and review notes. |
| Text-first deck | Marp CLI documents conversion from Markdown to HTML, PDF, PPTX, PNG, and JPEG, plus presenter notes as text. | Markdown, theme CSS, local assets, fonts, CLI/version, output hash, and viewer review. |
| Editable presentation | PPT Master’s repository documents native PowerPoint output and editable shapes, with separate native chart/table options. | Original source material, generated project source, exact PPTX, target viewer, editability inspection, and unresolved layout issues. |
These are not equivalent promises. “Editable” says something about the receiving artifact; it does not prove factual lineage. “Text-first” helps review changes; it does not make two renders byte-identical. “Generated from code” helps repeat a transformation; it does not establish that the chosen chart communicates honestly.
Build the packet before the export
Use the blank source-to-deliverable packet before handing work off. Keep fields empty until evidence exists. A useful packet names:
- the source files and their identities;
- the transformation entry point, version, parameters, and environment assumptions;
- every font, theme, image, template, and remote asset dependency;
- the presentation source and intended editable layer;
- each rendered deliverable and its digest;
- accessibility checks for reading order, contrast, labels, captions, and alternatives; and
- the viewer, reviewer, date, observed defects, and unresolved decisions.
A hash proves identity, not quality. A successful export proves that one process produced a file, not that its numbers are right, its text fits, or another application will render it the same way. Human review belongs in the packet as its own layer.
A bounded handoff
For a real delivery, give the recipient the smallest complete set: source facts, transformation source, declared dependencies, presentation source, final deliverable, and review record. Say which layer they should edit. If only the exported file is safe to share, say that the handoff is not reproducible instead of implying otherwise.
Primary sources:
- Matplotlib
savefigreference - Marp CLI canonical repository and conversion documentation
- PPT Master canonical repository
- PPT Master editability FAQ
The five-layer packet, comparison, worksheet, and conclusions are original. The captured research supplied discovery leads only; third-party examples and screenshots are not reproduced.