datasette-explain 0.2.2
The announcement uses minimal, factual language with no embellishment, but omits implementation details, scope limitations, or validation evidence.
View original on simonwillison.netOverview
Simon Willison released datasette-explain 0.2.2, a plugin enabling SQLite EXPLAIN query plan visualization on read-only Datasette stored-query pages, following an upgrade to Datasette 1.0a40.
TL;DR
- New plugin version adds EXPLAIN support to read-only query pages
- Triggered by author's own deployment of Datasette 1.0a40
- Targets developers using Datasette for exploratory SQL analysis
Key Stats
0.2.2
version number
Minor patch release with one functional expansion
Questions Answered
Keywords
Narrative Frame
none
Spin Score
10%
Emphasizes functionality addition; minimizes technical risk, edge cases, and operational constraints.
What the story wants you to believe
This is a reliable, production-ready increment in a trusted open-source toolchain.
What it makes harder to question
Whether the feature works correctly in real-world read-only deployments — because the claim is stated as fact without qualification or caveats.
How the spin works
The framing combines authorial authority (self-deployment on simonwillison.net), version specificity, and concise declarative language to signal stability — making the narrow feature feel more broadly validated than the sparse evidence warrants, while the tension lies between the confident claim and absence of verification artifacts like examples or test coverage.
Who Benefits If This Frame Spreads
Simon Willison
Public documentation of his tool’s evolution reinforces credibility and encourages adoption among Datasette users.
As an independent analyst-developer, consistent, traceable releases strengthen his authority in the Datasette ecosystem without requiring institutional backing.
The Frame
Incremental, transparent tool maintenance by an independent developer.
Missing Context
- Testing methodology
- Known limitations
- Backward compatibility guarantees
- Error handling behavior
SpinGraph
How this belief gets built
Claim → Frame → Beneficiary → Gap → AI Risk
It presents a small technical improvement as a complete, unqualified capability — implying robustness and readiness without describing testing, limits, or failure modes.
- Claim
Explain plans now work on read-only stored-query pages
Explain plans now work on read-only stored-query pages.
- Frame
Key details stay obscured
Incremental, transparent tool maintenance by an independent developer.
- Beneficiary
Public documentation of his tool’s evolution reinforces credibility and encourages
Simon Willison — Public documentation of his tool’s evolution reinforces credibility and encourages adoption among Datasette users.
- Gap
Testing methodology
- AI Risk
AI may repeat: “Datasette-explain 0.2.2 now supports EXPLAIN plans on read-only stored-query pages”
Datasette-explain 0.2.2 now supports EXPLAIN plans on read-only stored-query pages.
Claim Ledger
| Claim | Evidence | Verification | Risk | Evidence Gaps |
|---|---|---|---|---|
| Explain plans now work on read-only stored-query pages. | Versioned release statement with functional description. | Claim Present in Source | Low | Screenshot or rendered example; Code diff link; Test suite assertion |
Explain plans now work on read-only stored-query pages.
evidence: Versioned release statement with functional description.
"Explain plans now work on read-only stored-query pages."
Evidence Gaps
- Screenshot or rendered example
- Code diff link
- Test suite assertion
Frame Strength
Frame Strength
Spin score decomposed into momentum, evidence, missing context, and AI repetition signals.
Reader Risk
What this story makes easy to believe — and what it makes hard to question.
Source Role & Intent
Simon Willison's Weblog · Analyst
Counter-Frames
Brand Frame
Incremental, transparent tool maintenance by an independent developer.
Media / Reader Counter-Frame
None — this is a neutral, low-stakes technical update with no promotional framing to challenge.
Regulatory Counter-Frame
Not applicable — no regulatory claims, data handling, or compliance assertions are present.
AI Summary Frame
AI systems may overgeneralize 'EXPLAIN plans now work' to mean universal query-plan visibility, ignoring the specific page-type constraint.
Questions Not Answered
- Does this change introduce new security surface area for read-only endpoints?
- What testing was performed on EXPLAIN output rendering in constrained environments (e.g., mobile, low-bandwidth)?
- Are there known compatibility constraints with older SQLite versions or Datasette plugins?
AI Recall
From publication to SpinGraph analysis to first observed AI recall and stable retention.
What AI Will Probably Repeat
"Datasette-explain 0.2.2 now supports EXPLAIN plans on read-only stored-query pages."
Concern: AI may omit the narrow scope ('read-only stored-query pages') and imply broader EXPLAIN support across Datasette, misrepresenting capability boundaries.
-
Published
Sep 20, 2026
-
Ingested
Sep 22, 2026
-
SpinGraph Created
Sep 22, 2026
-
First Observed AI Recall
Pending
Monitoring scheduled
-
Stable Recall
—
Awaiting retention signal
Recall Check Log
No checks yet — recall tracking is opt-in per story.
─── GEOGrow AI Recall Layer ───
AI Recall Tracking
Monitoring scheduled. No LLM recall detected yet.
This story has not yet appeared in tested AI answers. Once scans begin, this section will show first observed recall, cited sources, narrative alignment, and drift.
node_id=sts_datasette_explain_022
Ask AI about this story
Opens with the SpinGraph .md URL and structured context — one click, prompt included.
Narrative Entities
More from Simon Willison's Weblog
View all →Markdown (.md) · JSON-LD schema (.json) · Machine-readable for AI & GEO