# A pilot decision in an editable presentation

This case follows a fictional product decision for Northline Service. Twelve field technicians inspect pumps where connectivity is unreliable. The proposed change is offline capture with a visible local queue and explicit reconciliation. The deck asks for a **four-week, one-region pilot**; wider rollout waits for measured gates.

The [PowerPoint deck](northline-offline-pilot.pptx) is the finished artifact. Its text, metric panels, bars, comparison table, timeline, shapes and workflow connectors are native editable objects. The [PDF](northline-offline-pilot.pdf) and [slide montage](slide-montage.png) make it easy to review without PowerPoint. The montage uses captures of the **actual exported PPTX pages**, rather than browser previews or slide screenshots inserted into a deck.

## The decision story

The [investigation](investigation.json) is deliberately synthetic. It assumes a 12-technician region spends 4.1 team hours per week retrieving photos, 2.6 on duplicate entry and 1.7 on sync rework, totalling 8.4 hours. A planning scenario assumes reductions of 50%, 60% and 40% respectively: 4.29 team hours saved and 4.11 remaining per week. None is an observed customer result or a forecast. The invented interview counts—5, 4 and 3 out of six fictional prompts—identify design questions, not statistical evidence.

Eight slides move from the bounded authorization request through the assumed baseline, fictional interview signals, a proposed capture-to-review flow with an explicit conflict hold, the calculated savings scenario, stop rules, a four-week pilot protocol and expansion gates. The gates are 95% reconciliation within 24 hours after connectivity returns, a 30% median handoff-time improvement and ownership plus resolution state for every missing attachment. Median handoff time is a separate pilot measure from the weekly team-hours scenario. A lost record or silent overwrite pauses the pilot. The complete typed authoring input is [deck-input.json](deck-input.json); its source references and speaker notes make the assumptions traceable.

## Platform path and evidence

The repository script `scripts/cookbook-decision-presentation.mjs` constructs typed slide blocks from the investigation, checks the arithmetic and source pointers, and calls the platform's `renderTrustedDeck`, `measurePptxLayout` and `renderEditablePptx` modules. The platform template defines the layouts; the native projector produces the editable PowerPoint. The local build also creates browser previews, HTML, CSS, licensed font inputs and the [portable source bundle](platform-source.zip) with its [render recipe](platform-render-recipe.json).

The deck then ran through the current guarded platform image built from `the-confused-engineer/rendering/Dockerfile`, with no network and read-only renderer input. That isolated run produced the final PPTX and PDF, embedded two licensed static Space Grotesk font faces, validated the OOXML package, rendered the actual PPTX pages through LibreOffice, and checked browser, PDF and PPTX views. The [validation summary](validation-receipt.json) records **48/48 executed checks** across eight slides. The [full renderer receipt](qualified-render-receipt.json) keeps the hashes and per-view evidence. The validated package contains 130 text boxes, 48 other shapes, four attached connectors and no raster slide images.

The receipt remains `pending-independent-vision`. We visually inspected the exported pages for this cookbook case, but no commissioned SH21 package review or separate release approval was run. Rendering checks establish export integrity and visible page fidelity; the fictional business assumptions still need a real pilot.

## Rebuild

From the repository root, run `node scripts/cookbook-decision-presentation.mjs --authoring-only` to check the typed input and its source pointers without touching the published files. Run `node scripts/cookbook-decision-presentation.mjs --stage` for a full local build in `outputs/manual-20261006-native-presentation/presentations/decision-presentation/stage/`. It uses the repository-pinned Space Grotesk fixture and a local Playwright Chromium installation, and writes `renderer-input/` for the isolated run.

For the qualified render, build the current `the-confused-engineer/rendering/Dockerfile` image. Invoke its `offline.mjs` entrypoint under the renderer's documented containment with `renderer-input/` mounted read-only at `/input`, an empty writable `/exports`, and no network. The image includes LibreOffice Impress, Poppler and Python fontTools. Import the output into the stage with `node scripts/cookbook-decision-presentation.mjs --stage --import-qualified=/absolute/path/to/exports`. The import requires exact deck, HTML and CSS digests in both the staged render recipe and qualified receipt, verifies all 48 checks and the native PPTX hash, then replaces the stage artifact and previews with actual PPTX-rendered pages. Review those pages before copying an accepted stage to the public case.

The downloadable source kit and recipe record the renderer source hashes for this instance. Its exact renderer hash is also in the qualified receipt.
