sprawll
Research artifacts you can defend.
Every AI research tool can write you a report.
sprawll is the one that refuses to publish a claim it can't pin to an archived source.
Highlights
- 🧾 Evidence-gated output — only claims that survive span-level verification against archived sources ship; everything else is withheld, never silently included
- 📦 Byte-for-byte archives — every source captured as WARC, with canonical snapshots every claim offset points into
- 🔢 Deterministic numeric guard — every figure in a claim must literally exist in a cited source
- 🔒 Local-first — prefers a local Ollama model; sources and drafts never leave your machine
- 💸 Hard budget cap — API fallback is checked against a dollar ceiling before every call
- 🔁 Replayable — re-verify any run from its archive with zero network access
Quick start
$ pip install sprawll
$ sprawll research-pack "solar e-bike charging on university campuses" \
-u https://example.edu/solar-project \
-u https://example.org/cycling-economy
What you get back:
| Artifact | What it is |
|---|---|
report.md |
Only claims that survived verification, each cited; single-source claims flagged |
diagnostics.md |
Every claim that failed, with the exact unsupported span named |
corpus.warc.gz |
The sources as they existed when fetched, byte-for-byte |
snapshots/ |
The canonical extracted text every claim offset points into |
How it verifies
Source-first pipeline:
fetch → archive (WARC) → extract → harvest facts → draft (only from harvested facts) → ground → render
The grounding gate has two layers:
- Span model (LettuceDetect, MIT) — checks every claim against source text, chunked with tracked offsets
- Numeric guard (deterministic) — every figure in a claim must literally exist in a cited source. Catches the hedged wrong numbers models gloss over
Publication is binary: supported claims ship, everything else goes to diagnostics. Claims one source supports and another contradicts publish as supported but contested. If the span model is unavailable, the LLM-judge fallback brands the whole report DEGRADED.
Local-first
sprawll prefers a local LLM. If Ollama is running, your sources and drafts never leave your machine:
$ ollama pull qwen3:14b # ~9 GB, fits a 12 GB GPU
API keys (ANTHROPIC_API_KEY / OPENAI_API_KEY) are the fallback, capped by a hard dollar ceiling (SPRAWLL_BUDGET_USD, default $2 — checked before every call). Pin explicitly:
$ export SPRAWLL_LLM=ollama/qwen3:14b
$ export SPRAWLL_LLM=litellm/anthropic/claude-sonnet-5
No LLM at all? sprawll refuses to draft undefended text — sprawll audit still grounds claims you wrote yourself.
Replay and audit
$ sprawll research-pack --from-archive runs/<run-dir> # re-verify, no network
$ sprawll audit claims.json snapshots/ # just the grounding gate
Failed sources are taxonomized (fetch_failed, robots_blocked, paywalled, timeout, extract_empty) and shown in the report's source table — a source that couldn't be archived is a fact about the corpus, not a rounding error.
Install notes
- First grounding run downloads the LettuceDetect weights (~1.5 GB).
License
Release files for sprawll 0.0.2
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| sprawll-0.0.2.tar.gz | 25.9 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| sprawll-0.0.2-py3-none-any.whl | Python 3 | none | any | Details |
Total release size:46.4 kB
Release files / sprawll-0.0.2.tar.gz
| Download URL | sprawll-0.0.2.tar.gz |
|---|---|
| Size | 25.9 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
949dbca187bcd01d23c38c8b8d1cb1b0981a73046b81a45e87ebeea5b0583b67
|
|
BLAKE2b-256 checksum How to use checksums |
ee6c99ac2d5de6ebbb679cdf32e19fe8fa6f471234ad896e9a5d1f015280a099
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.12
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Jul 13, 2026.
Transparency logRelease files / sprawll-0.0.2-py3-none-any.whl
| Download URL | sprawll-0.0.2-py3-none-any.whl |
|---|---|
| Size | 20.5 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
a3ce5c23ae1325818794e6581b2a0be4a43ee970f1ad83d664b92659954ac900
|
|
BLAKE2b-256 checksum How to use checksums |
5440d76c6ec5076fc0219d4d4fdd05566c0e5926744c17708af0ec908b8739c5
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.12
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Jul 13, 2026.
Transparency log