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

  1. The source boundary and exclusions are defined.Stated1
  2. Named authorities are identified.Stated2
  3. A public retrieval benchmark for this scope.Not yet published1

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.

QueryIllustrative · not live

Which current restrictions affect exporting dual-use software to this destination?

jurisdictionauthorityprogramme

No 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
Core source. Programmes · Guidance · Amendments, English firstJurisdiction scope, configured per workflow. 4 jurisdictionsOutside. Entity-screening decisions; Transaction approval
Jurisdictions
United States, European Union, United Kingdom, United Nations
Languages
English first
Source types
Programmes, Guidance, Amendments
Coverage window

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.

  1. 01Detect

    Compare the approved official source against its sealed snapshot.

  2. 02Review

    Verify the source change, rights boundary, structure, metadata, and lineage.

  3. 03Evaluate

    Rebuild the candidate and run the corpus-specific retrieval fixtures.

  4. 04Activate

    Switch versions only with a tested rollback path and customer notice.

Limit
Update targets are not completeness or service-level promises.

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.

Current evidence, as stated on the catalogue record1
Limit
Evidence, coverage boundaries, and update targets define this private beta. They are not completeness or service-level promises.

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.

Example

POST /v1/retrieve · illustrative, not live

query: Which current restrictions affect exporting dual-use software to this destination?
filters: jurisdiction, authority, programme, published_at, version

Limit
The intended contract returns retrieval context only.

The 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

  1. Catalogue record
    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.
    Knowledge base catalogue