The thesis
When a document gains the ability to filter itself, recompute itself, and hand a precise instruction back to its author, it stops being a record and becomes an instrument. The canonical artifact of knowledge work should be that instrument — not a PDF or Doc export.
What to take away
A document with a live filter is a different category of object than one without — it's queryable. The shift from prose-with-search-bolted-on to prose-as-data-structure is non-trivial: the reader can express intent to the artifact directly, without going through the author.
The round-trip — browser → copy-as-prompt → model → updated file — is the engineering trick that lets the artifact survive contact with a follow-up question. Without that loop, the document is frozen at export time and dies on the first new question.
HTML is the medium because it lets you skip the conversion step. The file you keep is the same file you read, edit, share, and feed back to the model. No PDF in between. No "export" verb.
The flatten test — strip all CSS and JS, ask what disappeared? — is the cheap diagnostic for whether you built an instrument or just styled prose. If only color and spacing disappeared, you have a document. If the filter, the cross-highlight, and the round-trip disappeared, you have an instrument.
Notable claims
A PDF or Doc export captures the state of a document at the moment of export. Every subsequent question — show me only the open items, what changed since last week, hide the boilerplate — requires a new conversation, a new export, a new file. The format does not survive contact with a follow-up question.
Evidence: A 40-page strategy brief exported to PDF. Stakeholder asks "just the risks and owners." Answer: copy-paste to a new doc, manually filter, re-send. Median turnaround in the imagined org: one business day. The artifact failed its first use. trq212's framing calls this "the unreasonable inefficiency of static exports."
The model that produced the artifact can't see the reader's interactions with it. A copy-as-prompt button is the bridge: it watches the reader mutate the artifact in the browser, packages the deltas as a precise instruction, and hands them back through the user's clipboard. The model now has full context — the original file, the reader's intent, the exact change requested.
Evidence: A triage board where the reader drags items into Now/Next/Later/Cut buckets, hits "copy as prompt," and pastes a paragraph that names the file path and the exact bucket assignments. The model updates the file. Round trip: ~10 seconds. No re-derivation of state.
Every external dependency is a future broken artifact. A CDN font that disappears, a syntax-highlighter script that rotates its API, an analytics beacon that leaks the document to a third party. The artifacts that survive ten years are the ones that need nothing but a browser.
Evidence: The render-as-html design system inlines all CSS and JS, uses native system fonts, and forbids external assets by default in generated artifacts. Open the file on a plane, in 2031, in a browser that hasn't been updated since — it still works.