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
Cedar Help — delivery and maintenance handoff, September 7, 2026
Delivered files
Delivery D-08: eight revised article drafts and maintenance guide version 1 were delivered September 7. Morgan acknowledged receipt of all files, not acceptance of maintenance responsibility. Individual article titles and versions are not in this excerpt.
Review status
Review R-06: six articles are accepted; two await terminology review. Consult the full review log to identify the accepted articles. Content acceptance is not permission to publish.
Open issues
Issue I-02: Casey owns terminology review, targeted for September 10, not guaranteed. One outdated reference must be removed before affected articles are published. Casey also owns identifying those articles and correcting the reference; the identifiers and a separate correction date remain open.
Ownership and access
Ownership O-03: Casey remains delivery owner until Morgan explicitly accepts maintenance in the existing project record. Morgan has not accepted, and the transfer date is unconfirmed. Access A-01: Morgan can read the draft folder, but publishing permission needs verification through the approved access process.
Scope and references
Scope S-01 excludes software changes and the rest of the knowledge base. Authoritative references are the full review log, draft folder, maintenance guide and ownership record; their URLs are not supplied. Post-transfer support coverage also needs confirmation.
Next review
Casey and Morgan should review article outcomes, identifiers and reference correction, publishing permission, support coverage and recorded acceptance. No review date is agreed. Sharing this record does not publish articles, grant access, close issues or transfer responsibility.
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>Cedar Help · Project handoff</title><style>
*{box-sizing:border-box}html{color-scheme:light}body{margin:0;background:#f6f4ee;color:#182e36;font:17px/1.65 system-ui,sans-serif}main{max-width:980px;margin:auto;padding:clamp(20px,5vw,64px)}h1,h2,h3,p{margin:0 0 18px}h1{font:500 clamp(34px,5vw,60px)/1.12 Georgia,serif;letter-spacing:-.025em;overflow-wrap:anywhere}h2{font:500 29px/1.25 Georgia,serif}h3{font-size:19px;line-height:1.4}.label{font:700 12px/1.5 system-ui,sans-serif;letter-spacing:.12em;text-transform:uppercase}.intro{font-size:20px}.lead{background:#173f4b;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:#fff;border:1px solid #b9c8c9;padding:24px}.metric{font:500 42px/1.1 Georgia,serif;display:block;margin-bottom:12px}section{margin:36px 0}ul,ol{padding-left:22px}li{margin-bottom:12px}.note{font-size:14px;color:#425c62}.warning{border-left:5px solid #a96215;padding-left:20px}footer{border-top:1px solid #b9c8c9;padding-top:24px;margin-top:40px;font-size:14px}@media print{body{background:white}.card,.lead{break-inside:avoid}}
</style></head><body><main>
<header><p class="label">Fictional example / Cedar Help / September 7, 2026</p><h1>The files arrived. The transfer is still pending.</h1><p class="intro">Eight article drafts and a maintenance guide are delivered. Review and responsibility are separate questions.</p></header>
<aside class="lead"><p class="label">Ownership · not yet transferred</p><h2>Casey remains delivery owner.</h2><p>Morgan has acknowledged receipt, not accepted maintenance responsibility. The transfer date is unconfirmed. Record acceptance in the existing project workflow.</p></aside>
<section><h2>What was delivered—and what is accepted</h2><div class="grid"><article class="card"><span class="metric">8 drafts</span><h3>All files received</h3><p>Delivered September 7 with maintenance guide version 1. Individual article titles and versions were not supplied.</p><p class="note">Source: delivery note D-08.</p></article><article class="card"><span class="metric">6 accepted</span><h3>2 await terminology review</h3><p>Check the full review log to identify the accepted articles. Content acceptance is not permission to publish.</p><p class="note">Source: review log R-06.</p></article></div></section>
<section class="warning"><p class="label">Open issue · I-02</p><h2>Resolve the terminology and outdated reference.</h2><p>Casey owns the terminology review. Target: September 10, 2026, not a guaranteed completion date.</p><p>One outdated reference must be removed before the affected articles are published. Casey also owns confirming the affected article identifiers and correcting the reference. Those identifiers are not supplied; no separate correction date is agreed.</p></section>
<section><h2>What each side still needs to do</h2><div class="grid"><article class="card"><p class="label">Delivery · Casey</p><h3>Keep ownership until acceptance</h3><p>Complete the review and reference follow-up. Do not move open issues to Morgan by default.</p></article><article class="card"><p class="label">Receiving owner · Morgan</p><h3>Confirm readiness to take over</h3><p>Reading access to the draft folder is confirmed. Publishing permission and post-transfer support coverage are not confirmed.</p><p class="note">Check permissions through the approved access process.</p></article></div><p class="note">Sources: ownership note O-03, access note A-01, and reference inventory.</p></section>
<section><h2>References to check before taking over</h2><ul><li><strong>Full review log:</strong> identify accepted articles and confirm the two outstanding reviews.</li><li><strong>Draft folder:</strong> check article versions and affected identifiers.</li><li><strong>Maintenance guide version 1:</strong> review the operating instructions and confirm support coverage.</li><li><strong>Ownership record:</strong> record any explicit acceptance.</li></ul><p class="note">Source URLs were not supplied. This example does not invent links or provide credentials.</p></section>
<section><h2>Outside this handoff</h2><p>Software changes and the rest of the knowledge base are excluded.</p><p class="note">Source: scope note S-01.</p></section>
<section class="card"><p class="label">Next review · date not agreed</p><h2>Casey and Morgan: confirm the remaining conditions.</h2><ol><li>Confirm the two articles' review outcome, affected identifiers, and reference correction.</li><li>Confirm publishing permission and post-transfer support coverage.</li><li>Record ownership acceptance when agreed in the existing project workflow.</li></ol><p>This page does not collect acceptance. Sharing it does not authorize article publication, grant access, close issues, or transfer responsibility.</p></section>
<footer>Fictional worked example by share/artifacts. Names, dates, and records are invented for demonstration. Source: the fictional handoff notes accompanying this example. 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.