Private beta · Curate route · manual review
Trade and sanctions guidance
Help trade systems retrieve the right official context while keeping jurisdiction and date boundaries explicit. Access is manually approved and configured for a bounded source, jurisdiction, and workflow scope.
What this page claims, and where the proof is
- The source boundary and exclusions are defined.
- Named authorities are identified.
- A public retrieval benchmark for this scope.
Stated evidence is quoted as written. Nothing on this page is a service level.
- Delivery route
- Curate
- Jurisdictions
- 4 jurisdictions
- Languages
- English first
- Activation
- Manual review
Exhibit A · Illustrative · not live
One request. Bounded evidence.
Private-beta interface preview. Access is manually configured for the approved source and workflow scope.
Which current restrictions affect exporting dual-use software to this destination?
jurisdictionauthorityprogrammeNo live result is shown. An approved collection must return bounded passages with citations, source metadata, and one immutable version.
Exhibit B · Coverage perimeter
Built for a retrieval problem, not a document dump.1
Evidence, coverage boundaries, and update targets define this private beta. They are not completeness or service-level promises.
In scope · Intended source scope
- Official sanctions programmes
- Export-control guidance
- Authority notices and amendments
Out of scope · Explicitly outside scope
- Entity-screening decisions
- Transaction approval
- Non-public watchlists
- Jurisdictions
- United States, European Union, United Kingdom, United Nations
- Languages
- English first
- Source types
- Programmes, Guidance, Amendments
Official sanctions policy, guidance, legal acts, and amendments. Deterministic entity screening remains outside scope.
Exhibit C · Versions and updates
No version history is published for this scope yet.
Research target: daily monitoring plus event-driven checks for authority notices. No screening service level is approved.
- 01Detect
Compare the approved official source against its sealed snapshot.
- 02Review
Verify the source change, rights boundary, structure, metadata, and lineage.
- 03Evaluate
Rebuild the candidate and run the corpus-specific retrieval fixtures.
- 04Activate
Switch versions only with a tested rollback path and customer notice.
Exhibit D · Evaluation
No public benchmark for this knowledge base yet.1
The published evidence pages currently cover the EU AI Act. The current evidence for this scope is stated below as written, without derived scores.
The private-beta source map covers OFAC, EU, OFSI, and UN authority families, with a documented boundary between guidance retrieval and entity screening.
Intended retrieval contract
Filter the request. Keep the citation boundary in the response.
Private-beta interface preview. The intended contract returns retrieval context for your application. It does not make the decision your workflow owns.
POST /v1/retrieve · illustrative, not live
query: Which current restrictions affect exporting dual-use software to this destination?
filters: jurisdiction, authority, programme, published_at, versionFilters narrow an approved scope. They cannot add sources, jurisdictions, or unverified material.
jurisdiction
authority
programme
published_at
versionAn approved collection must return bounded passages with citations, source metadata, and one immutable version.
passages
citations
source metadata
versionThe bounded job
Who this coverage is for.
How the private beta is intended to be used and delivered.
Audience
Trade compliance, logistics, and cross-border commerce teams
Primary use
Policy lookup, workflow assistance, and change alerts
Intended delivery
Jurisdiction-filtered retrieval with immutable source versions
Private-beta coverage
Official trade-control and sanctions guidance with jurisdiction, authority, programme, date, and version filters.
Shape the roadmap · Private beta · manual approval
Would this source boundary remove real work for your team?
Tell us the workflow, required sources, freshness, filters, and rights that would make it useful.
- What the status means
- Access is manually approved and configured for a bounded source, jurisdiction, and workflow scope.
- Access boundary
- Access is configured for a guidance-focused workflow with source rights confirmed; sanctions screening and transaction decisions remain outside scope.
Provenance notes
- Catalogue recordKnowledge base catalogue
- Status
- Private beta
- Current evidence
- The private-beta source map covers OFAC, EU, OFSI, and UN authority families, with a documented boundary between guidance retrieval and entity screening.
- Publication
- Stated evidence only. No reviewed benchmark or trace is published for this scope.
- Named authorities