Compliance & export
Export controls and research delivery: engineering the red lines
Research outputs collide with export regimes when models, datasets, or analytics could constitute controlled technical data to restricted parties or regions. Operators keep trains on tracks with boring mechanics: classify before ship, log approvers, separate demo calculators from client parameter bundles, geofence where required, and default screening to closed. This note is not legal classification advice—it is the engineering spine counsel plugs judgments into.
Where research trips export
Custom analytics on dual-use inputs, proprietary calibration files, and bespoke factor recipes can be sensitive depending on jurisdiction—treat edge cases as legal tickets.
Interactive tools blur lines: a ‘what-if’ slider may still transmit controlled methodology under some regimes—route with flags early.
Workflow hooks
Tag objects with export class at creation; block public routes if class forbids anonymous replay; require approver role for downgrades.
Downgrade paths need dual control—single-click ‘make public’ has burned shops.
Recipient screening
Integrate restricted party lists with CRM and desk sharing UI; failures should default closed.
Log matches even when ultimately cleared—auditors prefer over-logging to silent allows.
Geofencing and routing
Some client states cannot receive certain PDFs or even parameter sets—enforce in product, not in honor codes.
CDN and edge routing mistakes can place controlled artifacts in wrong regions—test geography headers on every deploy class.
Audit artifacts
Store classification decision, approver, timestamp, and policy paragraph reference—lightweight but reviewable.
Tie artifacts to object ids so replay can prove what class governed a historic send.
Vendor data entanglements
Third-party datasets may embed territorial restrictions—inherit tags into your lineage manifests.
When vendors mix global and region-locked series in one feed, split ingestion paths or inherit worst-case class explicitly.
Marketing vs client surfaces
Keep generic educational content on public hosts; move client-specific calibration behind auth and contracts.
Never let sales demos re-use production objects with client parameters without scrub logs—one sloppy screen share travels.
Training
Quarterly case drills with anonymized near-misses beat annual policy PDFs nobody reads.
Score drills on detection time and escalation correctness, not slide attendance.
Public desk routes referenced above
Same URL discipline applies after you authenticate—bookmarkable paths, no tenant data on these pages.
- Terms of use Stable legal URL when client-facing calculator links depart the marketing host.
- Privacy policy Maps subprocessors and flows; keep language consistent with how you split marketing and tenancy.
- Platform framing How tenancy and public chrome split when SEO and auth walls must coexist.
- Guides Pair public guides with internal SOPs so training points at one narrative spine.
- Operating rhythm Template language for stages, owners, and completion rules in a mandatory morning loop.
- Product atlas Route-level map so reviewers can open the exact module that produced a figure.
Operator toolkits
Checklists and scripts you can lift into runbooks, vendor RFPs, or board appendices.
Not legal advice; run all classifications with qualified export counsel.