How do I use it day to day?
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 honestly labeled "planned".
1.0 · WORKBENCHSpecs in. Evidence out.
Type what engineering gives you; leave unknowns blank — the system never guesses. The engine computes with rules vetted through legal review; every threshold sits next to its source line.
Enter specs
Copy from the spec sheet; leave unknowns blank. Missing input returns "insufficient information" — 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 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, timestamp — 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 = UNKNOWN — no guessing, 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 never issues a shipping conclusion.
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 (for encryption items, typically ENC) — with the reminder that 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, end use — the checks that 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: "per the country chart, for this reason code, an initial assessment of no license — and here is what you still must 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 — so this product turns it into an auditable pipeline.
Ledger
One record per part number: classification basis, legal review, 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 — where conditions apply — no submission; every determination cites its provision, and unclear cases are flagged for counsel.
Evidence bundle
Filing and decision records packaged into a printable evidence bundle with source snapshots and verbatim excerpts — archived for the required retention period, ready when audited.
4.0 · RESEARCHERWe have AI too. It speaks only from cited evidence.
Ask about terms, "why was this assessed this way", or amendment impact — every answer carries citation cards. When nothing grounds an answer, it says so. Staff work advises, the commander decides.
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: "which of my part numbers are affected" — 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 (demonstration data) — reserve now and be notified at opening. The cloud edition is planned for roadmap Stage 1.