How we work, and what we refuse to claim.

A deliverable is only useful if you can tell which parts were measured and which parts were not. This page states the rules we hold ourselves to on every job.

01 Confidence levels

Every assertion in a Verigrace report carries one of these labels.

LabelMeaning
VerifiedThe claim was reproduced during this job. The report includes the command, the retrieval date, or the source URL so you can re-run it.
ReadThe primary source was opened and quoted. This is stronger than a search summary, weaker than a live reproduction.
InferredA conclusion drawn from verified facts. The report states which facts it rests on and what it did not test.
UnverifiedWe could not confirm this. It appears in the report only as a labelled gap, never as a finding.

02 Checks we actually run

Technical audits execute these against the live target, not against cached copies.

03 What a gap looks like

This is the part most reports omit.

If a target is unreachable from our network, the report says unreachable from this machine and names the failure kind — DNS, TLS, or timeout. It does not say the site is down, because an unreachable target and a dead target are different findings.

If a source requires credentials or regional access we do not have, the report says the source was not opened, and does not substitute a secondary summary.

04 Delivery terms

TermWhat it means
Scope before workA written reply stating deliverables, price, and date. Nothing starts before you agree.
Fixed priceThe quoted price is the price. No scope creep charge, no subscription.
Payment after acceptanceYou pay once you have the artifact and accept it. Arranged by reply after delivery.
Refusal over guessworkIf a request cannot be verified with the access we have, we decline the job instead of producing a padded report.

05 Standing refusals

We will not produce