Release control that survives a license change
An export authorization defines what technical data may be released, to whom, and until when. When that authorization is granted, narrowed, or expires, mach720 re-projects the engineering documentation to the new authorized scope — an attested record of exactly what changed — instead of a multi-week manual re-scrub of every drawing.
What it delivers
Authorized-release envelope
Parameterizes engineering artifacts (SysML v2 / UML, drawings, AADL) against the authorized technical-data scope and recipient.
Re-project, don't re-scrub
When an authorization changes, the model is re-projected to the new scope with minimal engineering labor — with an attested record of what changed and why.
Inside the controlled boundary
Because this handles controlled technical data, it deploys air-gapped / on-prem — never as multi-tenant SaaS.
Same change-envelope kernel
Built on the same plan-for-change discipline as the CMMC reorg story, applied to export authorizations.
mach720 does not make export determinations. What is export-controlled, its jurisdiction and classification, and whether an authorization is granted are decided by the U.S. Government (DDTC/BIS) and your Empowered Official. mach720 manages and re-parameterizes artifacts and proves the released scope matches the authorized envelope. Not legal or export-control advice.