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
Pine Reports — Download-07 incident review
Timeline
September 7, 2026; all times UTC. Timeline T-07: download errors first observed at 09:12, monitoring alert at 09:14, rollback started at 09:22, recovery confirmed at 09:30. The observed impact window is 18 minutes; we do not know whether errors occurred earlier.
Impact
Impact I-07: 240 failed download requests during that window. Requests were not deduplicated, so unique affected users are unknown. No overall request denominator, error-rate percentage or data-loss assessment is available.
Recovery and analysis
Recovery R-07: rollback restored downloads at 09:30. No deployment commands, infrastructure identifiers or credentials are included. Analysis A-07: a configuration change preceded the errors, but its causal role remains provisional and under validation. There is no confirmed root cause, mechanism or personal blame established.
Follow-up actions
F-01 remains open: Noor owns validation of the configuration hypothesis, with an agreed September 10 review. Compare reviewed change evidence with the timeline and record whether it supports the hypothesis. F-02 proposes Eli as owner of an alert coverage test. That task is not accepted or scheduled; there is no test result or prevention claim.
Review and source records
Incident owners must review facts and audience before sharing. Source logs and sensitive infrastructure stay out of the reading page. Source URLs are absent; the existing incident tracking workflow remains authoritative. This is a fictional communication exercise, not an actual outage or security instruction.
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>Pine Reports · Download-07 postmortem</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">Fictional incident / September 7, 2026 / All times UTC</p><h1>Downloads recovered. Investigation remains open.</h1><p class="intro">Download-07 · A reviewed account of observed impact, response, and remaining questions.</p></header>
<section class="lead"><h2>240 failed requests over 18 observed minutes.</h2><p>Unique affected users are unknown. There is no supplied request denominator for an error-rate calculation.</p></section>
<section><h2>The verified timeline</h2><ol><li><strong>09:12:</strong> first observed download errors.</li><li><strong>09:14:</strong> monitoring alert.</li><li><strong>09:22:</strong> rollback started.</li><li><strong>09:30:</strong> recovery confirmed.</li></ol><p class="note">Source T-07. The record does not establish whether impact began before 09:12.</p></section>
<section><h2>What recovery establishes</h2><p>The rollback restored report downloads. It does not establish a completed causal analysis or permanent prevention.</p><p class="note">Source R-07. No deployment commands or infrastructure identifiers are included.</p></section>
<section class="warning"><h2>A hypothesis—not a confirmed root cause</h2><p>A configuration change preceded the errors. Its causal role is provisional and still being validated.</p><p>No data-loss assessment was supplied. This page does not claim that no data was lost.</p><p class="note">Sources A-07 and I-07.</p></section>
<section><h2>Follow-through has two different states</h2><div class="grid"><article class="card"><p class="label">F-01 · Open / owner confirmed</p><h3>Noor: validate the hypothesis</h3><p>Review date: September 10, 2026. Compare reviewed change evidence with the timeline and record whether it supports the hypothesis.</p></article><article class="card"><p class="label">F-02 · Proposed / not accepted</p><h3>Eli: proposed alert coverage test</h3><p>Ownership and scheduling are not accepted. The intended test would assess detection coverage; no result exists.</p></article></div></section>
<section><h2>Where the work continues</h2><p>The existing incident tracker remains authoritative. This page does not run remediation, close tasks, or prove recurrence has been prevented.</p><p class="note">Source: accompanying fictional incident notes. Source URLs were not supplied.</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.