Trade Launch Readiness

What this page is

Trade is ready for core compliance workflow demos. Some advanced modules are beta or pilot-scoped. SFTP intake is built behind a flag but is not production-ready until transport proof and a production secret resolver are complete.

Use this page before customer or buyer demos to confirm which modules you may exercise and which must be presented as roadmap or behind-feature-flag.

Module status

• Trade Core — LIVE. Workspace shell, audit, dashboard, navigation.
• Transactions — LIVE. Screening, intake, holds, certification, evidence linkage.
• Approvals — LIVE. Adjudication, claim/release, decision rationale, audit row.
• Evidence — LIVE. Regenerable evidence packs from stored workflow data.
• Import / CSV Intake — LIVE. Manual and CSV ingest paths with validation surfacing.
• Analytics — LIVE. Queue pressure, license risk, diversion signal views.
• Settings / API Keys / Connectors UI — LIVE for UI; connector maturity varies (see caveats below).
• Licensing — BETA. License headers, lines, drawdowns, alerts, documents, transaction linkage. Pilot hardening is the gate for any stronger claim.
• License Applications — BETA. Draft, EO approval, JSON packet, manual submission log, conversion to active license. PDF packet generation and direct BIS/DDTC filing are not shipped.
• CDD secure_portal — OPERATOR-READY / pilot. Behind NEXT_PUBLIC_CDD_ENABLED; internal pickup proof only.
• CDD outbound transports (SharePoint, Cryptshare, SFTP, FAA SharePoint) — NOT SHIPPED. Proof-contract stubs only; production-target builds fail closed on controlled payload.
• Inbound SFTP — PARTIAL. Settings UI, cron route, and ssh2-sftp-client adapter exist behind SFTP_ADAPTER_ENABLED. Not production-ready.
• SFTP production secret resolver — NOT SHIPPED. Tests use an in-memory resolver; Vault/KMS integration is deferred.
• SFTP real customer transport proof — UNVERIFIED. Tier-3 staging transport checklist is pending.

What we will not claim

If a marketing slide or buyer conversation needs language tighter than these bullets, raise it before committing — these are the launch guardrails for May 2026.

• No production-ready SFTP transport.
• No live ERP integration; no direct SAP, Oracle, or NetSuite sync.
• No direct regulator filing; no automated BIS or DDTC portal submission.
• No outbound CDD SFTP support; outbound SFTP for CDD is a proof-contract stub only.
• No PDF license application packets — Trade emits JSON; the Empowered Official uploads at DECCS or SNAP-R.

Core demo checklist

• Open Dashboard — confirm queue pressure tiles render.
• Import or view Transactions — confirm rows and screening signals.
• Review a held item in Approvals — claim, inspect, record a disposition with rationale.
• Generate an Evidence pack — confirm regeneration completes and contents reflect stored facts.
• View the Audit trail — confirm append-only rows scoped to organization_id.
• Open a Help article — confirm the new-user path and contextual hints render.
• Confirm module statuses on this page match the demo script before walking a buyer through.

Pilot checklist

• Licensing demo path — exercise headers, lines, drawdown, alerts; present as BETA.
• License application EO path — draft, EO approval, JSON packet download; present as BETA, no PDF, no direct filing.
• CDD secure_portal path — request, readiness check, approval, package, pickup proof; present as OPERATOR-READY pilot behind feature flag.
• SFTP stays off unless explicitly staged — never flip SFTP_ADAPTER_ENABLED in production until the Tier-3 runbook gate is signed off.

Proof checklist

This checklist is intentionally read-only. State lives in the audit doc and runbook, not in product data.

• Platform handoff smoke — pending real-handoff staging walkthrough.
• SFTP Tier-3 transport proof — pending per the staging validation runbook.
• Production secret resolver (Vault, KMS, or equivalent) — pending; tests still use the in-memory resolver.
• Full customer staging walkthrough — pending separate staging alias and end-to-end run.