01 / The familiar format
You could share this as a wiki page.
A fictional wiki entry with the same underlying facts. Read it here, then compare how the HTML version presents the information.
Team wiki · Fictional example
Harbor support-guide pilot — presentation recap
Source and audience
September 7, 2026. For colleagues who missed the presentation: these four slide cues and approved notes are the complete source. No recording, additional research, private presenter reminders, chart data or source URLs are included.
Slides 1–2 — Progress
Slide 1, “Pilot overview” (N1): four support guides are planned; the full title list is not supplied. Slide 2, “Three ready” (N2): three passed editorial review. “Ready” means editorial review only, not approved launch or proven customer usefulness. Adoption and impact are unmeasured.
Slides 3–4 — Open questions
Slide 3, “Next step” (N3): account recovery awaits a policy answer; owner and due date are unspecified. Slide 4, “September 14” (N4): September 14, 2026 is the pilot target, not an approved launch. The sponsor still needs to decide, but the exact question and deadline are absent.
Adaptation and privacy
The reading version should preserve those note-to-claim mappings and open questions. The audience needs current state and unresolved work, not editable slides or animation. In a real deck, private reminders need explicit audience approval before inclusion. Sharing an adaptation does not approve launch or publish the guides.
02 / The HTML version
Same information. See what needs your attention.
This is the complete static HTML example, not a screenshot. Scroll inside the preview to read it all. It has no live data, scripts, forms, or external resources.
Inspect the complete HTML source
This is the authored source for the example. The preview above passes through our HTML sanitizer before rendering in an isolated frame.
<!doctype html><html lang="en"><head><meta charset="utf-8"><meta name="viewport" content="width=device-width, initial-scale=1"><title>Harbor pilot: a deck adapted for readers</title><style>
*{box-sizing:border-box}html{color-scheme:light}body{margin:0;background:#faf6fa;color:#302439;font:17px/1.65 system-ui,sans-serif}main{max-width:1000px;margin:auto;padding:clamp(20px,5vw,64px)}h1,h2,h3,p{margin:0 0 18px}h1{font:500 clamp(32px,5vw,58px)/1.14 Georgia,serif;letter-spacing:-.025em;overflow-wrap:anywhere}h2{font:500 29px/1.3 Georgia,serif;overflow-wrap:anywhere}h3{font-size:19px;line-height:1.4}.label{font:700 12px/1.6 system-ui,sans-serif;letter-spacing:.08em;text-transform:uppercase}.intro{font-size:20px}.lead{background:#53355f;color:white;padding:24px;margin:28px 0}.lead p:last-child{margin:0}.grid{display:grid;grid-template-columns:repeat(auto-fit,minmax(min(100%,230px),1fr));gap:20px;margin:24px 0}.card{background:white;border:1px solid #bbc5c4;padding:24px}.metric{font:500 38px/1.2 Georgia,serif;display:block;margin-bottom:12px}section{margin:36px 0}ul,ol{padding-left:22px}li{margin-bottom:12px}.note{font-size:14px}.warning{border-left:5px solid #956118;padding-left:20px}a{color:inherit;text-underline-offset:4px}a:focus-visible,summary:focus-visible{outline:3px solid #956118;outline-offset:4px}table{width:100%;border-collapse:collapse;table-layout:fixed;font-size:15px}th,td{text-align:left;vertical-align:top;border-bottom:1px solid #bbc5c4;padding:12px 8px;overflow-wrap:anywhere}caption{text-align:left;font-weight:700;padding:12px 0}pre,code{white-space:pre-wrap;overflow-wrap:anywhere}footer{border-top:1px solid #bbc5c4;padding-top:24px;margin-top:40px;font-size:14px}@media(max-width:480px){th,td{padding:10px 4px;font-size:14px}}@media print{body{background:white}.card,.lead{break-inside:avoid}h2,h3{break-after:avoid}}
</style></head><body><main><header><p class="label">Harbor pilot / Fictional reading adaptation / September 7, 2026</p><h1>Three guides passed editorial review. Launch is still unapproved.</h1><p class="intro">This is the context behind a four-slide pilot update, written for a colleague who missed the presentation.</p></header><section class="lead"><h2>What the progress means</h2><p>Four support guides are planned. Three passed editorial review. That establishes review progress, not launch approval or proven customer usefulness.</p><p class="note">Slides 1–2, approved notes N1–N2. No adoption or impact measurement is available.</p></section><section><h2>What remains unresolved</h2><p>The account-recovery guide awaits a policy answer. The source does not supply the answer's owner or due date.</p><p>The sponsor still needs to make a decision. The precise decision question and deadline are absent, so this page does not invent them.</p><p class="note">Slides 3–4, notes N3–N4.</p></section><section class="warning"><h2>Read September 14 as a target</h2><p>September 14, 2026 is the pilot target—not an approved launch date. Sharing this adaptation does not approve launch or publish any guide.</p><p class="note">Slide 4, note N4.</p></section><section><h2>From slide cue to standalone meaning</h2><h3>Source-to-result mapping</h3><table><thead><tr><th scope="col">Slide cue</th><th scope="col">Context restored from notes</th></tr></thead><tbody><tr><th scope="row">Pilot overview</th><td>N1 supplies four planned guides; the complete title list is absent.</td></tr><tr><th scope="row">Three ready</th><td>N2 limits readiness to editorial review and states that impact is unmeasured.</td></tr><tr><th scope="row">Next step</th><td>N3 identifies the pending account-recovery policy answer without an owner or date.</td></tr><tr><th scope="row">September 14</th><td>N4 identifies a target and an unresolved sponsor decision.</td></tr></tbody></table></section><section><h2>Questions for the next review</h2><ul><li>Who owns the policy answer, and what date is agreed?</li><li>What exact decision does the sponsor need to make, and by when?</li><li>What will establish launch approval in the existing workflow?</li></ul><p>No source links or chart data were supplied. Private presenter reminders are not part of this reading view. The output is an adaptation, not an editable slide file.</p></section><footer>Fictional worked example by share/artifacts. Names, dates, figures and records are invented for demonstration. Static snapshot; no live data or automatic updates.</footer></main></body></html>
Make the next one about your work.
- Take the task to your agent. We provide a request with the goal, example, and checks. Copy it into the conversation where your context lives.
- Supply only what is missing. Use material your agent is authorized to access. Don’t substitute the example’s invented facts for your own.
- Review a draft before sharing. Check facts, readability, and sensitive information. Publishing and choosing who can open it are separate, explicit decisions.
Make this with my agentNo publishing connection is needed for an initial local draft. Your agent needs to be able to create an HTML file; preview and connection support vary by client.