Preparation, not determinations.
AD/CVD exposure can change duties by an order of magnitude, so SourceAgent treats compliance as evidence to prepare — screened early, cited always, and handed to a licensed customs broker who makes every determination.
Compliance information is for preparation only. Confirm HS classification, AD/CVD applicability, and origin status with a licensed customs broker or customs attorney before importing. See the full disclaimer.
Deterministic screening, at brief time
The screen runs before any supplier shortlist exists — the point where a flag can still change which factories are even eligible.
A versioned, cited knowledge base
Order references live in a versioned dataset with source citations and human review dates — not in a prompt. The same inputs always produce the same flags.
Code decides, never a model
The lookup is plain, testable code matching HS candidates against the knowledge base. A model may suggest candidate codes for a human to confirm; it never creates a flag.
Flags change the workflow
A flagged category holds offers until the review handoff, and the treatment says exactly who resolves it — a licensed customs broker, not the product.
What SourceAgent prepares
Product basis
The structured spec the screen ran against — material, construction, and quantities — so review starts from the same facts the request was matched on.
Candidate HS classification
Model-suggested candidates are only ever suggestions for a human to confirm. No classification is treated as final inside the product.
Risk flags with provenance
Every flag carries its source citation, the knowledge-base version that produced it, and the date the underlying entry was last human-reviewed. A flag with no provenance is a bug, not a feature.
Origin documents and gaps
What has been collected, what is missing, and the review handoff — named gaps instead of a folder of PDFs.
What it will never do
- Issue an HS classification, scope ruling, or origin determination
- Let a model decide a legal or duty number — the screen is deterministic code over a versioned dataset
- Publish supplier offers in a flagged category before the review handoff
- Present screening output as clearance — the treatment always names the reviewer
The boundary is structural, not aspirational: origin and compliance surfaces are security-reviewed, the screen is deterministic by contract, and every one of those surfaces renders the licensed-broker pointer you see on this page.
See the gate inside the workflow.
The compliance stage sits between matching and offers on every request — walk the full eight-stage workflow to see where it holds and what it hands over.
How the workflow runs →