Why the COA Check Gives You No Overall Verdict

The most requested change to the HempDash COA check is a single overall result. One answer: compliant or not.

We do not ship it, and the reasoning is worth stating plainly rather than hiding behind a design decision.

What the check does

You can upload a certificate of analysis without an account and receive rule-scoped findings, reported per requirement.

Each finding attaches to a specific requirement. Where a required field is absent, the finding says which field. Where a value cannot be derived, the finding says which input is missing.

What it deliberately does not do

• It does not render an overall verdict.
• It never states that a product may be offered for sale.
• Where a rule's enforcement posture is pending verification, it returns NEEDS_REVIEW rather than a pass or a failure.

Why a single verdict would be dishonest

Producing one answer requires collapsing things we genuinely do not know into a confident output.

Take a concrete case. The Texas total delta-9 THC threshold is verified as text — it can be cited precisely against the adopted rules. Its enforcement posture is a separate question and is genuinely under review.

Folding that into a green checkmark converts an open question into a reassurance. And the person acting on that reassurance carries the consequence — not us.

That is the whole argument. A tool that tells you which specific requirement is unmet is doing work you can act on. A tool that tells you that you are "compliant" is making a promise it has no standing to make.

What happens to your document

Documents are processed in memory only. Nothing is written to a database, to object storage, or to a temp file.

Extracted text is sent to an AI provider solely to locate fields. No document content is logged — logs carry the byte count and the outcome, and metrics are numeric-only.

How to read the output

Treat each finding as a discrete item of work:

• Missing field — a certificate defect. Take it back to the vendor or the laboratory.
• Underivable value — a required value that cannot be computed from what was reported. Reading more carefully will not fix it.
• NEEDS_REVIEW — the rule is real, and its enforcement posture is not settled. This is information, not an error.

What it cannot tell you

Whether your product may lawfully be offered for sale. Whether you would pass an inspection. Whether a certificate is authentic in the sense of not having been altered.

Those are outside what a field-set review can establish, and a tool claiming otherwise would be overstating what it did.