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.
Framing
The problem
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.
The pattern
Bind AI outputs to their source like spreadsheet formulas: edit the source and the summary, translation, and action chips recompute in place.
Why chat breaks here
Chat has no binding between answer and document — the summary lives in a transcript that never learns the source moved on.
Risks
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.
Avoid 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.
Use when
AI outputs depend on a living source document and stale answers cause real confusion.
DOPE evaluation
- Directability
- Edit the source, switch the target language, slide formality — the derived blocks follow the change without being re-prompted
- Observability
- Each block displays what it derives from and visibly recomputes when the source changes — freshness is shown state, not an assumption
- 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
In the wild
- 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.
- 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.
- Google Sheets =AI() (Google) — 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.
FAQ
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.
Related patterns
- Often paired with: Ghost Text Editor — Reactive blocks + inline ghost text — both stay live as the doc moves.
- Often paired with: Citation Trail — Block-level summaries + sentence-level source mapping inside the same doc.
- Alternative to: Generative UI — Reactive blocks inside a doc vs the whole answer rendered as an interface.