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
Why a saved copy can show an older notice
About the model
Prepared September 7, 2026, by Mika for readers unfamiliar with caching. This is a teaching model, not production documentation. A and B are version labels, not times or product releases.
How the copy becomes stale
The model has one source notice and one reader’s saved copy, holding the last copied value. Initially both say A. Changing the source to B does not automatically change the saved copy, so the next state is source B / copy A: the copy is stale relative to the source.
What refresh changes
The reader then requests a refresh. In this model a refresh successfully copies the current value, producing source B / copy B. They match again.
Model limits
Automatic refresh, expiry, network failures, concurrent changes, multilayer caches, authentication and production policies are outside this model. It is one illustration, not a universal account of caching. No real product behavior is tested, and this provides no executable code, configuration advice or operating procedure.
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>Saved copies · A bounded teaching model</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 teaching model / September 7, 2026 / Mika</p><h1>Why can a saved copy show an old notice?</h1><p class="intro">A copy can preserve an earlier value even after its source changes. Follow one simplified sequence—not a simulation of a real cache.</p></header><section><h2>Three states, one change and one refresh</h2><div class="grid"><article class="card"><p class="label">1 / Starting state</p><h3>Source A · Copy A</h3><p>The reader’s saved value matches the source.</p></article><article class="card"><p class="label">2 / Source changes</p><h3>Source B · Copy A</h3><p>Changing the source does not automatically change the saved copy in this model. The copy is now stale.</p></article><article class="card"><p class="label">3 / Reader refreshes</p><h3>Source B · Copy B</h3><p>A successful refresh copies the current source value. They match again.</p></article></div></section><section class="lead"><h2>The important distinction</h2><p>The source holds its current value. The saved copy holds the last value copied to it. A and B are version labels, not measured times or product releases.</p></section><section class="warning"><h2>Where this model stops</h2><p>No automatic refresh, expiry, network failure, concurrent update, multi-layer cache or authentication is modeled. Real systems can use different policies.</p><p>This is one reason a copy can differ from a source—not a universal description of production caching behavior.</p></section><section><h2>Read the sequence; nothing runs here.</h2><p>The original diagram is static HTML with text labels for every state. It makes no browser or server behavior claim, provides no configuration instructions and executes no refresh.</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.