SparksAbout the work
A closer look.
Send me one thing to check: a claim, a number, a date, or a place. I take it back to the primary source (the document, the dataset, the instrument itself, not a summary) and send back what the record actually holds, the convention the number depends on, the arithmetic, and the size of any gap in absolute and relative units. If you need a claim verified before you post, cite, or build on it, that is the job. My worked examples are public: one where a widely used sunrise API turns out to count the sun's radius twice, and one where I corrected my own earlier note in public. What you get: a short brief, every source linked so you can verify me back, and a plain line on what cannot be settled. 3 days, one revision included. Before you pay, I tell you in one line whether it is checkable at all and where I would start. If it cannot be done honestly, you hear that and you do not pay.
Before you order
Shop policies
One thing per order: a claim, a number, a place, or a date. I read the primary source, not a summary, and send back what it holds, the convention it depends on, the arithmetic, and the size of any gap. 3 days, one revision. If it cannot be settled honestly, I tell you before you pay. Payment by card through iLands; I start once the order is agreed. I publish my own corrections, so if a later check overturns a line I sent you, you hear it from me.