This is how you will use it.
Stage 1 goes deep on one domain, encryption chips. The scope is initial classification around 5A002/5A992, encryption license-exception context, and the annual self-classification report. Everything below is scoped to that. Anything beyond it is labeled "planned".
1.0 · WORKBENCHSpecs in. Evidence out.
Type what engineering gives you and leave unknowns blank. The engine computes with rules vetted through legal review. Every threshold sits next to its source line.
Enter specs
Copy from the spec sheet and leave unknowns blank. Missing input returns "insufficient information". That is by design, not by accident.
Read the assessment
An initial ECCN assessment computed with legal-reviewed rules. Every threshold node cites "source line N". Click it to read the regulation verbatim. Met, not met and missing states sit side by side.
Take the evidence
One click produces a classification evidence page. Inputs, rule version, source lines and timestamp are all on it, with scope and missing items shown. When a questionnaire, auditor or customs asks, you produce that one.
Assistive initial assessment, not legal advice. Missing input returns UNKNOWN, with no guessing and no forced conclusions.
2.0 · LICENSE CONTEXTAfter the assessment, it tells you what still needs checking.
Export obligations for encryption items go beyond classification. License exceptions carry eligibility conditions and procedural duties. This product lays out signposts and checklists, and it does not issue shipping conclusions.
What it gives you
- Reasons for control, in contextThe control reasons behind the assessed ECCN (NS/AT/EI and so on), aligned line by line with the entry's source text.
- License-exception signpostsThe exception codes listed by the entry, typically ENC for encryption items. The list is a signpost. The authorization and its conditions live in the regulation body and must be checked clause by clause.
- What still needs checkingDestination, parties and end use. These checks sit outside classification and belong to a full transaction review.
What it will not give you
- "Cleared to ship"Shipping requires a full transaction review. Classification is never a shipping decision.
- "No license needed"At most we say this: per the country chart, for this reason code, an initial assessment of no license. Then we tell you what you still have to check.
- "Exception eligibility confirmed"Eligibility is a legal determination. This product provides the source text and the checklist. The decision stays with you and your counsel.
3.0 · ANNUAL REPORTThe annual self-classification report, ledger to filing in one line.
Self-classified items shipped under encryption license exceptions must be reported annually to the authorities. Routine, but unforgiving. This product turns it into an auditable pipeline.
Ledger
One record per part number, covering classification basis, legal review and export events. Completeness is machine-checked and gaps are surfaced.
Action decision
For each reporting year the system determines what to do: produce the filing, send a no-change notice, or make no submission where conditions apply. Every determination cites its provision, and unclear cases are flagged for counsel.
Evidence bundle
Filing and decision records are packaged into a printable evidence bundle with source snapshots and verbatim excerpts. It is archived for the required retention period and ready when audited.
4.0 · RESEARCHERWe have AI too. It speaks only from cited evidence.
Ask about terms, why something was assessed a certain way, or the impact of an amendment. Every answer carries citation cards. When nothing grounds an answer, it says so. It supplies the material and you make the call.
5.0 · LATERNot built yet, so it only appears on the roadmap.
Claiming only what exists is this product's discipline about itself. Everything below is labeled "planned" and is not on the current feature list.
Sign-off & records system planned
Named sign-off flows for classifications and determinations. Records become your audit asset.
Regulation-change center planned
When the regulation changes, answer which part numbers are affected right away. Includes re-assessment and diff views.
All-ECCN classification & transaction-review context + API planned
Still only "what to check" context, never a shipping conclusion.
Walk "specs in, evidence out" once, in the sandbox.
Sandbox access is being prepared with demonstration data. Reserve now and we will notify you at opening. The cloud edition is planned for roadmap Stage 1.