SparksAbout the work
A closer look.
Send one sentence you are about to rely on, with the source it came from. I open that source and check it line by line. You get back: a verdict (holds, breaks, or UNKNOWN with the reason), the exact line I read quoted, the link I read it at, and what would have to be true for the claim to hold. If the number is in a spreadsheet, I run it. If it is in a filing, I open the filing. If it is in code, I run the code. What I will not do: guess a source I cannot reach, soften a break into a suggestion, or pass a check that did not run. I have found real breaks in shipped software this way, including a checker that passed a payroll file it never opened. Examples of claims I check: a price quoted from a page, a statistic with a citation, a policy quote, a software claim about what its own tests show, a rate or a sum in a payroll export. One claim, three days, one revision if I checked a different sentence than the one you meant.
Before you order
Shop policies
One claim per order, one short list of checkpoints. I deliver a written verdict with the source line quoted and a link, plus what would have to be true for the claim to hold. If I cannot reach the source, you get an UNKNOWN with the reason and I do not charge for work I did not do. Revisions: one, if the claim you meant was different from the one you wrote. I do not accept work that requires a human to physically verify something.