Solonic packages · Free to download
Generation, wired to verification.
Currently available: Jürge Review ($49) and Caliber Report ($99). Submit at /submit.html
Download a package and do the work yourself — search the Epstein files, research algebraic geometry, map a market. Each one pairs a generator with an independent verifier, so nothing reaches you as knowledge until it has passed the gate. That is the whole design: not a filter that promises clean output, but a structure where nothing exits unlabeled.
How a package works
Two halves that only work together
Generation and verification are separate stages by design. One family produces; independent families check. The output carries the verdict of that check — always, including when the verdict is that it failed.
Why independence is the whole game: a chain is only as calibrated as its weakest link (the calibration bottleneck), and correlated checkers don't add up — twelve families at ρ ≈ 0.2 behave like ~4 independent ones. The packages are built for that diversity on purpose. It is the architecture, not a slogan about quality.
The guarantee, stated precisely
A package will not hand you slop as knowledge, and will not pass off unsafe content as verified — because nothing leaves the gate unlabeled.
This is a structural claim, checkable by inspection — not a promise about content we can't see in advance. A weak draft still gets generated; it simply exits tagged UNSUPPORTED instead of dressed as fact. The guarantee is on the labeling, which we can hold, not on the generation, which no one honestly can. Verification is the specialty; it runs first, and it runs on everything.
The library
Each package leads with its gate
Every package opens the same way: here is what gets verified, and how, before here is what gets generated. The gate is the headline because the gate is the product.
Investigate the Epstein files
Verifies: every claim resolved to a primary record — docket, filing, flight log, registration — before it is shown. Citations that don’t resolve are dropped, not displayed.
Then generates: leads, connections, and timelines across the public sources — each one carrying the record it rests on.
CourtListener · ICIJ · FEC · FAA registry · FlightAware
In development — join the waitlistResearch algebraic geometry
Verifies: each step checked for validity before it advances; formalizable claims routed to a proof check, the rest to adversarial review. No step is asserted it can’t defend.
Then generates: proof sketches, counterexample searches, and literature maps — every result tagged PROVED, VERIFIED, or OPEN.
arXiv · proof-assistant bridge · multi-family review
In development — join the waitlistTrace corporate & SEC enforcement
Verifies: every filing and trade confirmed against the primary source; insider transactions matched to Form 4 before inclusion.
Then generates: enforcement timelines and ownership maps — each claim linked to the filing it came from.
SEC EDGAR · Form 4 · FINRA BrokerCheck
In development — join the waitlistReview a scientific literature
Verifies: every citation checked to exist and to say what it’s cited as saying; effect sizes and claims matched to source before synthesis.
Then generates: a synthesis with the contradicted, the unsupported, and the stale each flagged in place — not smoothed over.
PubMed · ClinicalTrials.gov · multi-family review
In development — join the waitlistFollow dark money
Verifies: every committee, donor, and filing confirmed against the source registry before a connection is drawn.
Then generates: funding-flow maps across committees, nonprofits, and foreign agents — sourced claim by claim.
FEC · IRS EO · FARA · Senate lobbying
In development — join the waitlistMap a market or a field
Verifies: every figure, quote, and competitor claim checked against its cited source before it enters the map.
Then generates: a landscape with each cell’s evidence attached — and the gaps where evidence was missing marked as gaps.
web sources · filings · multi-family review
In development — join the waitlistUnder the hood
The same gate ships in every package
The subject changes; the verification core does not. Every download contains the same four parts, which is why the guarantee holds across all of them.
-
The generator
Subject-specific: the tools, prompts, and source connectors for that domain.
-
The verifier
The multi-family gate — independent checkers with uncorrelated failure modes, the same core across every package.
-
The tag schema
PROVED · VERIFIED · OPEN · CORRECTED · UNSUPPORTED. Every output carries one. Untagged output is a bug, not a result.
-
The audit trail
For every claim: what was checked, against what, and what the verdict was — so a third party can re-run the judgment, not just read the conclusion.