A summary generated once is a snapshot — the source keeps changing and the derived text silently stops being true, because nobody re-asks after every edit.
← Back to patterns
Google
Magic Ink: Information Software and the Graphical Interface Malleable Software: Restoring User Agency in a World of Locked-Down Apps
Inline & Contextual
Smart Document
AI Blocks That Watch Your Content
A summary generated in chat is a snapshot: edit the source afterwards and the summary silently stops being true, because nobody re-asks after every change. Smart Document treats AI outputs as derived blocks — spreadsheet formulas over prose — bound to visible source content: edit the source and the summary, translation, and action chips recompute in place, so derived text cannot quietly drift from what it describes.
Metaphor
Spreadsheet Formula
Interaction
Reactive, Block-based
Use case
Document Editing, Summarization, Translation
Failure mode
Linear History
Control mechanisms
Auto-updating Blocks · Action Chips · Formality Slider
Reference examples
Notion AI autofill · Coda AI Block · Google Sheets =AI()
Interactive Example
The live side-by-side is the comparison.
This prototype already contains the contrast between chat and the pattern response. It stands as the primary comparison surface for this page.
AI output is a snapshot. A document is a moving target.
Generate a summary in chat, keep editing the source, and the summary is wrong the moment you look away. The two artifacts live in different places with no link between them, so the generated content silently drifts out of sync with the thing it describes — and nobody is told.
Smart Document treats AI outputs as reactive blocks bound to visible source content, the way a spreadsheet cell recalculates when its inputs change. Edit the source, switch the language, adjust the formality, and the dependent blocks update in place — each one showing its source and the rule it used, so the derivation stays live and inspectable rather than a stale paste.
If the source can change, the output should not be a fixed copy — it should be a formula.
DOPE Lens
How this pattern improves AI interaction quality.
Observability
Each block displays what it derives from and visibly recomputes when the source changes — freshness is shown state, not an assumption
Directability
Edit the source, switch the target language, slide formality — the derived blocks follow the change without being re-prompted
Predictability
Blocks behave like spreadsheet formulas: any source edit deterministically triggers a re-derivation, so derived text is never silently stale
Explainability
A block reads as source plus rule: it names the content it consumes and the transformation it applies, so stale-vs-fresh is decidable by inspection
Fit
Where it earns its place.
Use it
when
when
AI outputs depend on a living source document and stale answers cause real confusion.
Avoid
when
when
The output must be a fixed snapshot — a signed-off summary, an audit artifact — where live re-derivation is a liability, not a feature.
In the wild
Where this pattern already ships.
Real implementations from products users already know. Each entry shows how the pattern got applied — what shipped, where it sits in the product, what it traded off.
Notion · AI autofill
Notion
The auto-updating surface is AI autofill, not the inline AI block — the block needs a Generate click. Autofill offers Summary, Translate and Key info bound to the page body, with a run trigger of "on page edits", so the derived text re-derives in place. That triad is exactly the summary / translation / action-chips the pattern names.
Visit Notion ↗
Coda AI Block
Coda
AI Block creates dynamic summaries and action lists that update as source data changes. Reactivity is documented behaviour, not a bug.
Visit Coda ↗
Google Sheets =AI()
Kept as the instructive near-miss rather than dropped. =AI() / =Gemini() looks like the spreadsheet-formula metaphor and is not one: the output is inserted as static text and only updates when a human clicks "Refresh and insert". Change a referenced cell and nothing recalculates — the borrowed metaphor without the binding underneath it.
Visit Google ↗
Research Frame
Why this pattern exists, and where it breaks.
Bind AI outputs to their source like spreadsheet formulas: edit the source and the summary, translation, and action chips recompute in place.
Chat has no binding between answer and document — the summary lives in a transcript that never learns the source moved on.
Text that rewrites itself while the user is not looking feels haunted unless every recompute is visibly cued and traceable to the source edit that caused it.
Common questions
What people ask about this pattern.
When should I use the Smart Document pattern?
+
AI outputs depend on a living source document and stale answers cause real confusion.
When should I avoid the Smart Document pattern?
+
The output must be a fixed snapshot — a signed-off summary, an audit artifact — where live re-derivation is a liability, not a feature.
What problem does Smart Document solve?
+
A summary generated once is a snapshot — the source keeps changing and the derived text silently stops being true, because nobody re-asks after every edit.
Why is chat the wrong fit for this?
+
Chat has no binding between answer and document — the summary lives in a transcript that never learns the source moved on.
Grounded in Research
Not just opinion.
The papers, guidelines, and usability studies this pattern rests on.
Bret Victor
worrydream.com · long-form essay · 2006
Distinguishes information software (you read) from manipulation software (you operate) and argues most products misclassify themselves. The case for generated answers that are interfaces, not paragraphs.
Geoffrey Litt, Paul Sonnentag, Peter van Hardenberg, Alexander Obenauer
Ink & Switch · 2024
Argues software should be end-user-modifiable as a default, with LLMs as the editing surface. The frame behind Generative UI, Smart Document, and the broader post-chat document model.
Related Patterns
Curated connections, not just neighbors.
Hand-picked relationships — what this pattern pairs with in practice, what it replaces, what it builds on, and what builds on it.
Often paired with
Ghost Text Editor
Ghost Text Editor speeds up writing the source; Smart Document keeps the summary and translation built from it current.
Often paired with
Citation Trail
Smart Document keeps the summary in step with its source; Citation Trail traces each summary sentence back to a source span.
Often paired with
Generative UI
Generative UI makes AI output clickable and Smart Document binds it to its source, so the result is both interactive and current.