License applications

Workflow states

• draft — application authoring.
• internal_review — compliance review before EO.
• eo_approved — EO attestation and packet hash bound.
• submitted_to_portal — manual upload logged with regulator case ID.
• converted_to_license — approved application becomes an active license record.

Empowered Official approval

EO approval requires warning acknowledgement, packet hash confirmation, and attestation. Direct draft-to-EO-approved transitions are refused. Editing EO-attested fields after approval recalls the approval — enforced in the database, not just the UI.

Filing boundary

Trade generates a structured JSON packet stored in the private exports bucket. The Empowered Official uploads manually at DECCS or SNAP-R using their own credentials. Trade logs the external case ID — it does not file with regulators on your behalf. PDF packet generation is not shipped.

In the browser

• Sidebar → License applications — confirm list and status column.
• Open a draft — walk internal_review → eo_approved states in demo if seeded.
• Locate JSON packet download and manual submission log — no in-app regulator filing.