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
ADR-007 — Cedar Docs reading-page delivery
Status
Accepted September 7, 2026, by Ada in the repository decision record. Acceptance is documented; implementation is not complete. The repository record remains authoritative, though its URL is not supplied.
Scope and requirements
Scope is one public documentation reading page, not operational dashboards or every application. Readers need a daily reviewed summary that remains readable without a live data connection at reading time. Only reviewed audience-safe content belongs in it. Daily review is the intended process, not a service-level guarantee; no exact schedule, hosting service or real-time guarantee is required.
Alternatives and decision
Alternatives: live queries at page load, which depend on a connection when reading, or generated snapshots after review, which separate generation from reading. We chose reviewed snapshots for reading-time independence. No benchmarks, costs, capacity, uptime measurements or security audit are supplied; this is not a claim that snapshots are universally superior or prove security.
Consequences and implementation
Ada accepts that content can be stale until the next reviewed generation. No automatic refresh job or exact generation guarantee exists in this record. An implementation owner, due date, deployment and verification result remain unspecified.
Decision history
A changed decision needs a new reviewed record superseding ADR-007 while preserving its history and rationale. An HTML companion does not accept another decision, update the repository or deploy the architecture.
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 Docs · ADR-007</title><style>
*{box-sizing:border-box}html{color-scheme:light}body{margin:0;background:#f5f8fc;color:#182e46;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:#23486b;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 ADR-007 / Accepted September 7, 2026</p><h1>A reviewed snapshot, not a live query.</h1><p class="intro">Cedar Docs public documentation reading page · Technical decision owner: Ada.</p></header>
<section class="lead"><h2>Decision accepted. Work not yet complete.</h2><p>Use generated snapshots after review so the page remains readable without a live data connection at reading time.</p></section>
<section><h2>The constraint comes first</h2><p>Readers need a daily reviewed summary, not live operational data. This decision covers one public documentation reading page—not operational dashboards or every application.</p><p>Only reviewed audience-safe content belongs on the page. Daily review is the intended process, not a proven service-level guarantee.</p></section>
<section><h2>The alternatives actually considered</h2><div class="grid"><article class="card"><p class="label">Not chosen for this scope</p><h3>Live queries at page load</h3><p>Reading would depend on a data connection at that time.</p></article><article class="card"><p class="label">Chosen</p><h3>Generated snapshots after review</h3><p>Reviewed content generation is separate from reading.</p></article></div><p class="note">No performance benchmarks, costs, capacity estimates, security audit, or uptime measurements were supplied.</p></section>
<section class="warning"><h2>The accepted cost is staleness.</h2><p>Content can be stale until the next reviewed generation. Ada accepts that tradeoff for this scope. No real-time guarantee is required.</p><p>No automatic refresh job or exact generation time is established by the source.</p></section>
<section><h2>What remains unimplemented</h2><p>No implementation owner, due date, deployment, or verification result was supplied. Decision ownership does not automatically assign implementation work.</p></section>
<section class="card"><h2>Change the decision without erasing its history.</h2><p>A new reviewed record must supersede ADR-007 if the decision changes. Retain the earlier rationale and keep the repository record authoritative.</p><p>Repository URL not supplied. This companion neither edits the record nor deploys the design.</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.