Evidence and limits
Inspect the source and output behind major capabilities. Planned benchmarks and hosted workflows stay separate from what you can run locally today.
Rendered samples
The same source spec produced three branded ten-slide decks and an eleven-slide enterprise-template fixture. Inspect a representative slide, open the full contact sheet, or download the editable PowerPoint.
Slide 2 of 10. 2 native charts and 3 native tables in the deck.
View all slidesDownload sample PPTX
Slide 2 of 10. 2 native charts and 3 native tables in the deck.
View all slidesDownload sample PPTX
Slide 2 of 10. 2 native charts and 3 native tables in the deck.
View all slidesDownload sample PPTX
Slide 3 of 11. 2 native charts and 3 native tables in the deck.
View all slidesDownload sample PPTXRendered with LibreOffice 7.4.7.2 40(Build:2). These are compatibility captures, not Microsoft PowerPoint fidelity or brand approval. Automated structural checks found no flagged issues. The capture container substituted 8 requested font roles. Inspect the PPTX at presentation size before adopting a template.
Capture and source metadataWhat to inspect
Curated examples list source specs, generated deck paths, rendering path, screenshot asset, and launch-blocker status so screenshots stay connected to implementation.
Next proof: Add a per-example lineage drawer linking spec, validation report, generated PPTX, and final capture.
Renderer metadata separates native PowerPoint chart output from shape-based analytical visuals, structural slides, and the Mekko compatibility path.
Next proof: Add side-by-side editability screenshots after real PowerPoint captures are available.
The marketing flow now includes a captured review-report asset tied to the screenshot manifest; normalized diff proof remains a follow-up.
Next proof: Add normalized-diff proof and connect each review artifact to a per-example lineage drawer.
Launch status is derived from the screenshot manifest and validator rather than hand-written page copy, keeping blockers explicit.
Next proof: Keep strict launch validation in release checks and replace remaining non-blocking preview placeholders.
Quickstart paths present CLI, Python SDK, MCP, and HTTP job-service entry points for local automation and agent workflows.
Next proof: Add a concrete draft, critique, repair, validate, render transcript tied to one generated deck.
The Next.js service-job proof page shows a sanitized lifecycle fixture with queued request, completed status, events, and artifact manifest, while distinguishing the available local browser-console prototype from planned hosted workspace management.
Next proof: Capture a live local API run or TUI job view after the service fixture format is approved for demos.
The claims ledger gives each major claim a status, evidence summary, and source link so copy can stay aligned with product maturity.
Next proof: Expand claims coverage for SDK, MCP, HTTP service, templates, and validation reports.
The CLI, SDK, MCP, and HTTP service give Paralleliz a real local automation foundation, but the token-efficiency claim still needs benchmark evidence.
Next proof: Add a benchmark comparing prompt-only deck generation with Paralleliz spec, diff, validate, and render loops.
Template placeholder examples, roadmap notes, and FAQ copy describe brand integration without implying a hosted enterprise workflow exists yet.
Next proof: Create a before-and-after template route with placeholder mapping and final branded output.