Overseas Expansion Compliance

Problem

Cross-border expansion compliance checks are usually fragmented across sanctions lists, export controls, ODI filings, destination-market access, and customer due diligence. Manual review can miss related entities, jurisdiction-specific rules, and source traceability.

How It Works

The skill organizes dynamic research buddies for the enterprise-overseas-expansion scene. At runtime it reads the live buddies[] from GET /api/playbook, then delegates template selection to cue-research semantic matching rather than relying only on title keywords. Core capabilities cover sanctions and export-control exposure, related-entity screening, U.S. regulatory risk, trade remedies, comparative legal analysis, ODI filing and overseas entity mapping, destination-market access, and overseas customer due diligence. Before execution, it confirms credits, then runs research_run.py for a 3–15 minute research pass and returns a report with source links. If the result is RESULT empty, it states that no content was retrieved instead of inventing findings.

Boundaries

It uses public data such as official lists, regulator disclosures, legal texts, public judgments, registry and customs information. It is useful for compliance working papers and pre-due-diligence screening, not a substitute for formal legal advice, audit, or underwriting. If the scene is not live, matching is weak, or private data is requested, it should flag unavailability or decline.