A Windows service writes to SQLite in WAL mode while a nightly backup copies only the main database file. Find official SQLite sources and produce a corrected backup/restore checklist. Explain the WAL dependency, a documented live-backup alternative, and how we should validate a restored copy. Keep operational recommendations separate from what the source guarantees.
10/4/2026, 11:40:50 PM · llm:deepseek:deepseek-v4-flash
> ⚠ Low confidence — Only source excerpts are delivered; complete synthesis and per-assertion support remain unverified. Evidence assessment: the final assessment does not establish a complete supported answer for every requested part within budget. Treat this as provisional.
Source excerpts only. The draft is withheld as a conclusion; complete synthesis is unverified. Qualifying source excerpts are quoted below. Research targets are topics to investigate, not established conclusions.
Research target 1
Requested topic (unverified): “What does official SQLite documentation say about the WAL dependency when a backup copies only the main database file while a database is in WAL mode?”
- “In WAL mode, a transaction can commit by appending its commit record to the WAL while the corresponding pages have not yet been checkpointed into the main database file.” - “SQLite's WAL documentation says that the WAL file is part of persistent database state and warns that separating a database from its WAL can lose previously committed transactions or lead to corruption.”
Research target 2
Requested topic (unverified): “What documented live-backup alternative does official SQLite documentation provide for backing up a database that is in use?”
- “.backup drives the Online Backup API, which copies the database page by page through SQLite itself, WAL content included.” - “It is safe to run against a database that other connections are using, and if another connection writes to the source mid-copy, the backup restarts so the result is always a consistent snapshot.”
Research target 3
Requested topic (unverified): “How should a restored copy be validated according to official SQLite documentation?”
- “Once in a while, open a real backup file, run integrity_check, and count rows in the tables you care about.” - “A backup can open cleanly, return ok from PRAGMA integrity_check, and still be the wrong recovery point.”
Research target 4
Requested topic (unverified): “What does official SQLite documentation guarantee about the consistency or completeness of a backup that copies only the main database file while WAL mode is active?”
- “A copy of only the main file can therefore omit already committed application state.” - “SQLite's WAL documentation says that the WAL file is part of persistent database state and warns that separating a database from its WAL can lose previously committed transactions or lead to corruption.”
Research target 5
Requested topic (unverified): “What operational recommendations follow for a corrected backup/restore checklist for a Windows service writing to SQLite in WAL mode with a nightly backup that copies only the main database file?”
- “If you can guarantee no writes are happening (e.g., application is stopped), a simple file copy is fine for WAL-mode databases after a checkpoint.” - “Database file and -wal get stored straight into a tar file, and, if restored, both are placed back to the original place.”
Excerpts establish source grounding, not factual truth, entailment or whole-paper coverage. Support and coverage are estimates, not certification of a complete answer. Source statements may be wrong or conflicting. Draft conclusions are withheld; inspect the original text and obtain further review. Payment states remain in the separate receipt.
Evidence ledger — recorded source excerpts
Research targets are unverified topics. Coverage is an estimate of excerpt support, not proof of entailment, factual truth or a complete answer.
Requested topic (unverified): “What does official SQLite documentation say about the WAL dependency when a backup copies only the main database file while a database is in WAL mode?”
90% estimated“In WAL mode, a transaction can commit by appending its commit record to the WAL while the corresponding pages have not yet been checkpointed into the main database file.” [S2] SQLite WAL Backups: Verify the Committed Rows
“SQLite's WAL documentation says that the WAL file is part of persistent database state and warns that separating a database from its WAL can lose previously committed transactions or lead to corruption.” [S2] SQLite WAL Backups: Verify the Committed Rows
Requested topic (unverified): “What documented live-backup alternative does official SQLite documentation provide for backing up a database that is in use?”
90% estimated“.backup drives the Online Backup API, which copies the database page by page through SQLite itself, WAL content included.” [S3] How to safely back up or copy a live SQLite database
“It is safe to run against a database that other connections are using, and if another connection writes to the source mid-copy, the backup restarts so the result is always a consistent snapshot.” [S3] How to safely back up or copy a live SQLite database
Requested topic (unverified): “How should a restored copy be validated according to official SQLite documentation?”
70% estimated“Once in a while, open a real backup file, run integrity_check, and count rows in the tables you care about.” [S3] How to safely back up or copy a live SQLite database
“A backup can open cleanly, return ok from PRAGMA integrity_check, and still be the wrong recovery point.” [S2] SQLite WAL Backups: Verify the Committed Rows
Requested topic (unverified): “What does official SQLite documentation guarantee about the consistency or completeness of a backup that copies only the main database file while WAL mode is active?”
90% estimated“A copy of only the main file can therefore omit already committed application state.” [S2] SQLite WAL Backups: Verify the Committed Rows
“SQLite's WAL documentation says that the WAL file is part of persistent database state and warns that separating a database from its WAL can lose previously committed transactions or lead to corruption.” [S2] SQLite WAL Backups: Verify the Committed Rows
Requested topic (unverified): “What operational recommendations follow for a corrected backup/restore checklist for a Windows service writing to SQLite in WAL mode with a nightly backup that copies only the main database file?”
60% estimated“If you can guarantee no writes are happening (e.g., application is stopped), a simple file copy is fine for WAL-mode databases after a checkpoint.” [S1] How to Back Up SQLite Databases on Ubuntu
“Database file and -wal get stored straight into a tar file, and, if restored, both are placed back to the original place.” [S4] Hot backup database in WAL mode by coping
What if a source were missing?
Temporarily leave out one source to see which research targets retain excerpts in this report.
Showing the original excerpt ledger.
What does official SQLite documentation say about the WAL dependency when a backup copies only the main database file while a database is in WAL mode?
2 recorded excerpts remain.
Inspect remaining excerpts
“In WAL mode, a transaction can commit by appending its commit record to the WAL while the corresponding pages have not yet been checkpointed into the main database file.”
S2 · refontelearning.com · SQLite WAL Backups: Verify the Committed Rows · version af150e4e5d08b3ac4584e440c4f2558f275cfaa71521e2603e4879473ac24595
“SQLite's WAL documentation says that the WAL file is part of persistent database state and warns that separating a database from its WAL can lose previously committed transactions or lead to corruption.”
S2 · refontelearning.com · SQLite WAL Backups: Verify the Committed Rows · version af150e4e5d08b3ac4584e440c4f2558f275cfaa71521e2603e4879473ac24595
What documented live-backup alternative does official SQLite documentation provide for backing up a database that is in use?
2 recorded excerpts remain.
Inspect remaining excerpts
“.backup drives the Online Backup API, which copies the database page by page through SQLite itself, WAL content included.”
S3 · mysqlui.com · How to safely back up or copy a live SQLite database · version c3420f2dece606da19fd0ab76bdd6080aa25b8b3d7b2328a00b9c00ef6f46fcf
“It is safe to run against a database that other connections are using, and if another connection writes to the source mid-copy, the backup restarts so the result is always a consistent snapshot.”
S3 · mysqlui.com · How to safely back up or copy a live SQLite database · version c3420f2dece606da19fd0ab76bdd6080aa25b8b3d7b2328a00b9c00ef6f46fcf
How should a restored copy be validated according to official SQLite documentation?
2 recorded excerpts remain.
Inspect remaining excerpts
“Once in a while, open a real backup file, run integrity_check, and count rows in the tables you care about.”
S3 · mysqlui.com · How to safely back up or copy a live SQLite database · version c3420f2dece606da19fd0ab76bdd6080aa25b8b3d7b2328a00b9c00ef6f46fcf
“A backup can open cleanly, return ok from PRAGMA integrity_check, and still be the wrong recovery point.”
S2 · refontelearning.com · SQLite WAL Backups: Verify the Committed Rows · version af150e4e5d08b3ac4584e440c4f2558f275cfaa71521e2603e4879473ac24595
What does official SQLite documentation guarantee about the consistency or completeness of a backup that copies only the main database file while WAL mode is active?
2 recorded excerpts remain.
Inspect remaining excerpts
“A copy of only the main file can therefore omit already committed application state.”
S2 · refontelearning.com · SQLite WAL Backups: Verify the Committed Rows · version af150e4e5d08b3ac4584e440c4f2558f275cfaa71521e2603e4879473ac24595
“SQLite's WAL documentation says that the WAL file is part of persistent database state and warns that separating a database from its WAL can lose previously committed transactions or lead to corruption.”
S2 · refontelearning.com · SQLite WAL Backups: Verify the Committed Rows · version af150e4e5d08b3ac4584e440c4f2558f275cfaa71521e2603e4879473ac24595
What operational recommendations follow for a corrected backup/restore checklist for a Windows service writing to SQLite in WAL mode with a nightly backup that copies only the main database file?
2 recorded excerpts remain.
Inspect remaining excerpts
“If you can guarantee no writes are happening (e.g., application is stopped), a simple file copy is fine for WAL-mode databases after a checkpoint.”
S1 · oneuptime.com · How to Back Up SQLite Databases on Ubuntu · version 0ce7a59cf5a2e6215b4ce938f9b1c78ec125afd87b09598b7a74199e50b9dd0d
“Database file and -wal get stored straight into a tar file, and, if restored, both are placed back to the original place.”
S4 · sqlite.org · Hot backup database in WAL mode by coping · version bfe98ecab775f2064f105c3c790c279e2a55b1b7803d259124a67973e87c741c
Targets are requested topics, not verified assertions. Excerpts do not prove truth or independent corroboration. This view keeps the answer, confidence and payments unchanged and makes no new requests.
Research evidence matrix
Compare unverified research targets with cited sources and inspect recorded excerpts. An empty cell means no inspectable excerpt was recorded; it does not establish whether a claim is true, false, or disputed. Coverage and agent confidence do not prove entailment, measured accuracy or complete synthesis.
| Research target (unverified) | Inspection status | [S1] How to Back Up SQLite Databases on UbuntuPublication: oneuptime.comPublished: Not recorded | [S2] SQLite WAL Backups: Verify the Committed RowsPublication: refontelearning.comPublished: Not recorded | [S3] How to safely back up or copy a live SQLite databasePublication: mysqlui.comPublished: Not recorded | [S4] Hot backup database in WAL mode by copingPublication: sqlite.orgPublished: Not recorded |
|---|---|---|---|---|---|
| What does official SQLite documentation say about the WAL dependency when a backup copies only the main database file while a database is in WAL mode? | Recorded excerpt | No excerpt recorded | Inspect 2 excerptsIn WAL mode, a transaction can commit by appending its commit record to the WAL while the corresponding pages have not yet been checkpointed into the main database file. SQLite's WAL documentation says that the WAL file is part of persistent database state and warns that separating a database from its WAL can lose previously committed transactions or lead to corruption. | No excerpt recorded | No excerpt recorded |
| What documented live-backup alternative does official SQLite documentation provide for backing up a database that is in use? | Recorded excerpt | No excerpt recorded | No excerpt recorded | Inspect 2 excerpts.backup drives the Online Backup API, which copies the database page by page through SQLite itself, WAL content included. It is safe to run against a database that other connections are using, and if another connection writes to the source mid-copy, the backup restarts so the result is always a consistent snapshot. | No excerpt recorded |
| How should a restored copy be validated according to official SQLite documentation? | Recorded excerpt | No excerpt recorded | Inspect 1 excerptA backup can open cleanly, return ok from PRAGMA integrity_check, and still be the wrong recovery point. | Inspect 1 excerptOnce in a while, open a real backup file, run integrity_check, and count rows in the tables you care about. | No excerpt recorded |
| What does official SQLite documentation guarantee about the consistency or completeness of a backup that copies only the main database file while WAL mode is active? | Recorded excerpt | No excerpt recorded | Inspect 2 excerptsA copy of only the main file can therefore omit already committed application state. SQLite's WAL documentation says that the WAL file is part of persistent database state and warns that separating a database from its WAL can lose previously committed transactions or lead to corruption. | No excerpt recorded | No excerpt recorded |
| What operational recommendations follow for a corrected backup/restore checklist for a Windows service writing to SQLite in WAL mode with a nightly backup that copies only the main database file? | Recorded excerpt | Inspect 1 excerptIf you can guarantee no writes are happening (e.g., application is stopped), a simple file copy is fine for WAL-mode databases after a checkpoint. | No excerpt recorded | No excerpt recorded | Inspect 1 excerptDatabase file and -wal get stored straight into a tar file, and, if restored, both are placed back to the original place. |
Reference export
4 article references. Recorded titles, links and dates; observed scholarly records also include supplied authors, DOI and journal metadata with read limits. Review metadata before using in a paper. Import RIS into Zotero with File → Import.
Cited sources and references
- 1How to Back Up SQLite Databases on Ubuntuoneuptime.comFree public reference · no creator payment · extracted html text20%
- 2SQLite WAL Backups: Verify the Committed Rowsrefontelearning.comFree public reference · no creator payment · extracted html text35%
- 3How to safely back up or copy a live SQLite databasemysqlui.comFree public reference · no creator payment · extracted html text30%
- 4Hot backup database in WAL mode by copingsqlite.orgFree public reference · no creator payment · extracted html text15%
Decision log · 66 steps
Breaking down: "A Windows service writes to SQLite in WAL mode while a nightly backup copies only the main database file. Find official SQLite sources and produce a corrected backup/restore checklist. Explain the WAL dependency, a documented live-backup alternative, and how we should validate a restored copy. Keep operational recommendations separate from what the source guarantees."
Identified 5 research target(s) to investigate; these are not established facts
Deep mode: up to 4 paid/cached/public reads plus one bounded gap-expansion pass when needed.
Web search: 4/4 planned queries attempted, 4 succeeded, 24 public page previews, 0 unavailable queries. Snippets are discovery only. Public reads spend no USDC; model and service operating costs remain separate.
Discovered 0 verified creator source(s) and 24 free public reference(s)
Claim-aware portfolio (exhaustive; bounded selection, not a claim of global optimality) selected 4/13 positive proposal(s): 4 free/cache selections + 0 paid fresh selections, predicting 5/5 claim(s) above the evidence floor with $0.000000/$0.015000 fetch USDC reserved.
Free-preview pre-check maps an actionable source to every sub-claim (5/5); paid reading may proceed within the budget.
Covers backup API and VACUUM INTO for live DBs plus integrity verification and restore testing — supports live-backup alternative, validation, and checklist. Free read. - free public original-page READ selection (not a cache hit); no purchase or creator reward. — selected for the claim-aware evidence portfolio (targets claims 2, 3, 5; 0 fetch USDC, 1 attention slot).
Preview directly addresses the core WAL dependency: commits live in the WAL until checkpointed, and a main-file-only copy can omit committed data. Free public read, so CACHE. Helps claims 0 and 3. - free public original-page READ selection (not a cache hit); no purchase or creator reward. — selected for the claim-aware evidence portfolio (targets claims 1, 4; 0 fetch USDC, 1 attention slot).
Explains .backup/Online Backup API and VACUUM INTO as consistent live-backup methods, including WAL content handling. Strong for live-backup alternative and checklist. Free read. - free public original-page READ selection (not a cache hit); no purchase or creator reward. — selected for the claim-aware evidence portfolio (targets claims 2, 5; 0 fetch USDC, 1 attention slot).
sqlite.org forum thread discussing hot backup in WAL mode and whether copying main file alone is consistent; relevant to the WAL dependency and consistency guarantee questions. Free read. - free public original-page READ selection (not a cache hit); no purchase or creator reward. — selected for the claim-aware evidence portfolio (targets claims 1, 4; 0 fetch USDC, 1 attention slot).
Duplicate of the other sqlite.org forum post (same preview text, different URL). Redundant with the previous candidate; no added value. - free public original-page READ selection (not a cache hit); no purchase or creator reward.
Mailing-list discussion of online/hot backup of WAL databases and Backup API behavior; touches live-backup alternative and WAL trustworthiness. Free read. - free public original-page READ selection (not a cache hit); no purchase or creator reward. — the claim-aware portfolio chose a stronger, less redundant set inside the 4-source attention and $0.015000 fetch-budget caps, so this proposal stays unspent.
Covers .backup and VACUUM INTO while app runs, checkpointing, and restore rehearsal steps — useful for live-backup alternative and operational checklist. Free read. - free public original-page READ selection (not a cache hit); no purchase or creator reward. — the claim-aware portfolio chose a stronger, less redundant set inside the 4-source attention and $0.015000 fetch-budget caps, so this proposal stays unspent.
Community PSA explaining why copying only the .db in WAL mode is invalid and mentioning checkpoint/VACUUM; supports WAL dependency and operational recommendations. Free read. - free public original-page READ selection (not a cache hit); no purchase or creator reward. — the claim-aware portfolio chose a stronger, less redundant set inside the 4-source attention and $0.015000 fetch-budget caps, so this proposal stays unspent.
HN comment about multi-database atomicity in WAL mode, not about backup of a single DB or restore validation. Off-topic for the subclaims. - free public original-page READ selection (not a cache hit); no purchase or creator reward.
Explains WAL vs rollback journal internals but not backup/restore or validation; tangential to the checklist. - free public original-page READ selection (not a cache hit); no purchase or creator reward.
About enabling WAL mode and database-locked errors, not backup consistency or restore validation. Not relevant. - free public original-page READ selection (not a cache hit); no purchase or creator reward.
DBA question on archiving a WAL-mode DB with tar, directly analogous to copying only the main file; relevant to WAL dependency and checklist. Free read. - free public original-page READ selection (not a cache hit); no purchase or creator reward. — the claim-aware portfolio chose a stronger, less redundant set inside the 4-source attention and $0.015000 fetch-budget caps, so this proposal stays unspent.
Core Data/iOS-specific question about restoring without a WAL file; platform-specific and less authoritative for the Windows service scenario. - free public original-page READ selection (not a cache hit); no purchase or creator reward.
Restic forum thread gives generic advice (dump or stop service) without SQLite-specific WAL/backup detail; low added value. - free public original-page READ selection (not a cache hit); no purchase or creator reward.
Litestream cron-backup page describes VACUUM INTO snapshot semantics for live DBs; relevant to documented live-backup alternative. Free read. - free public original-page READ selection (not a cache hit); no purchase or creator reward. — the claim-aware portfolio chose a stronger, less redundant set inside the 4-source attention and $0.015000 fetch-budget caps, so this proposal stays unspent.
Production backup strategies article covering SQLite backup API and .backup; useful for live-backup alternative and operational checklist. Free read. - free public original-page READ selection (not a cache hit); no purchase or creator reward. — the claim-aware portfolio chose a stronger, less redundant set inside the 4-source attention and $0.015000 fetch-budget caps, so this proposal stays unspent.
Explains that .backup uses the Online Backup API and accounts for WAL content without manual checkpoint — directly supports live-backup alternative. Free read. - free public original-page READ selection (not a cache hit); no purchase or creator reward. — the claim-aware portfolio chose a stronger, less redundant set inside the 4-source attention and $0.015000 fetch-budget caps, so this proposal stays unspent.
YouTube video with only a generic description; no textual content to evaluate and low information density. - free public original-page READ selection (not a cache hit); no purchase or creator reward.
StackOverflow page preview is just a list of unrelated linked questions; no substantive backup/WAL content. - free public original-page READ selection (not a cache hit); no purchase or creator reward.
Reddit thread about whether SQLite does automatic backups; not about WAL main-file copy consistency or restore validation. - free public original-page READ selection (not a cache hit); no purchase or creator reward.
Posit Connect docs show PRAGMA integrity_check for validating a restored SQLite backup — directly supports restore validation. Free read. - free public original-page READ selection (not a cache hit); no purchase or creator reward. — the claim-aware portfolio chose a stronger, less redundant set inside the 4-source attention and $0.015000 fetch-budget caps, so this proposal stays unspent.
rqlite backup guide recommends periodic integrity checks on backups to confirm valid SQLite files; supports restore validation. Free read. - free public original-page READ selection (not a cache hit); no purchase or creator reward. — the claim-aware portfolio chose a stronger, less redundant set inside the 4-source attention and $0.015000 fetch-budget caps, so this proposal stays unspent.
Logseq git-based restore workflow is application-specific and not about WAL backup consistency or SQLite-documented validation. - free public original-page READ selection (not a cache hit); no purchase or creator reward.
Inductive Automation forum thread about gateway backup not restoring SQLite tables; unrelated to WAL backup mechanics. - free public original-page READ selection (not a cache hit); no purchase or creator reward.
READ How to Back Up SQLite Databases on Ubuntu - selected original public page, 0 USDC; not a cache hit.
Read extracted public text from https://oneuptime.com/blog/post/2026-03-02-how-to-back-up-sqlite-databases-on-ubuntu/view - S1; quote matching establishes source grounding, not fact verification.
READ SQLite WAL Backups: Verify the Committed Rows - selected original public page, 0 USDC; not a cache hit.
Read extracted public text from https://www.refontelearning.com/blog/sqlite-wal-backup-committed-row-validation - S2; quote matching establishes source grounding, not fact verification.
READ How to safely back up or copy a live SQLite database - selected original public page, 0 USDC; not a cache hit.
Read extracted public text from https://www.mysqlui.com/blog/68-how-to-safely-back-up-or-copy-a-live-sqlite-database - S3; quote matching establishes source grounding, not fact verification.
READ SQLite User Forum: Hot backup database in WAL mode by coping - selected original public page, 0 USDC; not a cache hit.
Read extracted public text from https://www.sqlite.org/forum/info/2ea989bbe9a6dfc8 - S4; quote matching establishes source grounding, not fact verification.
Attention budget is full at 4 source(s); no broader context will be purchased.
Final check — "What does official SQLite documentation say about the WAL de…": 90% assessed by S2, S3
Final check — "What documented live-backup alternative does official SQLite…": 90% assessed by S1, S3
Final check — "How should a restored copy be validated according to officia…": 80% assessed by S2, S3
Final check — "What does official SQLite documentation guarantee about the …": 90% assessed by S2, S3
Final check — "What operational recommendations follow for a corrected back…": 60% assessed by S1, S2, S3, S4
Final coverage assessment — The gathered passages provide direct support for the WAL dependency, the documented live-backup alternative, and validation of a restored copy. They also support the guarantee that copying only the main file while WAL mode is active can omit committed transactions or corrupt the copy. The operational checklist is only partially supported because the sources give general recommendations but not a complete Windows-service-specific checklist. The assessment does not establish a complete supported answer for every requested part.
Synthesizing a grounded answer from 4 source(s)…
Relevance review returned; only checked excerpts can retain support, and review cannot raise it.
Delivering qualified source excerpts; complete synthesis and per-assertion support remain unverified.
Source-matched public excerpt (no creator reward) — S2, research target 1, proposed support 60% (estimate, not entailment): “In WAL mode, a transaction can commit by appending its commit record to the WAL while the corresponding pages have not yet been checkpointed…”
Source-matched public excerpt (no creator reward) — S2, research target 1, proposed support 90% (estimate, not entailment): “SQLite's WAL documentation says that the WAL file is part of persistent database state and warns that separating a database from its WAL can…”
Source-matched public excerpt (no creator reward) — S3, research target 2, proposed support 90% (estimate, not entailment): “.backup drives the Online Backup API, which copies the database page by page through SQLite itself, WAL content included.”
Source-matched public excerpt (no creator reward) — S3, research target 2, proposed support 80% (estimate, not entailment): “It is safe to run against a database that other connections are using, and if another connection writes to the source mid-copy, the backup r…”
Source-matched public excerpt (no creator reward) — S3, research target 3, proposed support 70% (estimate, not entailment): “Once in a while, open a real backup file, run integrity_check, and count rows in the tables you care about.”
Source-matched public excerpt (no creator reward) — S2, research target 3, proposed support 60% (estimate, not entailment): “A backup can open cleanly, return ok from PRAGMA integrity_check, and still be the wrong recovery point.”
Source-matched public excerpt (no creator reward) — S2, research target 4, proposed support 90% (estimate, not entailment): “A copy of only the main file can therefore omit already committed application state.”
Source-matched public excerpt (no creator reward) — S2, research target 4, proposed support 90% (estimate, not entailment): “SQLite's WAL documentation says that the WAL file is part of persistent database state and warns that separating a database from its WAL can…”
Source-matched public excerpt (no creator reward) — S1, research target 5, proposed support 80% (estimate, not entailment): “If you can guarantee no writes are happening (e.g., application is stopped), a simple file copy is fine for WAL-mode databases after a check…”
Source-matched public excerpt (no creator reward) — S4, research target 5, proposed support 60% (estimate, not entailment): “Database file and -wal get stored straight into a tar file, and, if restored, both are placed back to the original place.”
Prepared source excerpts citing 4 source(s); complete synthesis is unverified
Confidence: Low — Only source excerpts are delivered; complete synthesis and per-assertion support remain unverified. Evidence assessment: the final assessment does not establish a complete supported answer for every requested part.
oneuptime.com contributed 20% - free public reference; reward share withheld
refontelearning.com contributed 35% - free public reference; reward share withheld
mysqlui.com contributed 30% - free public reference; reward share withheld
sqlite.org contributed 15% - free public reference; reward share withheld
Done. Spent $0 across 0 confirmed/simulated payment(s) to creators.
Portable research receipt
Take the evidence trail with you
One deterministic JSON bundle binds the answer, visible decisions, exact article versions, claim evidence and a Circle-settlement snapshot under SHA-256. Retain the digest to detect later changes; the self-check is not a publisher or Keryx signature.
Carries this dispatch’s question as context — never its answer. The next dispatch is read from sources bought for it.