The detailed platform specification uses uniquely identified data sets to manage the regulatory information associated with a consignment movement.
The CMDS is assembled from the data elements required for the applicable eFTI subsets rather than from a fixed document template.
Adminyra keeps those subset associations explicit so validation and authority responses can be traced back to the regulatory context.
Operational freight data can change during a movement. Adminyra stores immutable payload versions and a per-element audit trail instead of losing the previous state.
That supports validation, reconstruction and later authority interaction.
No. It is structured data. Human-readable output can be generated, but the regulated dataset itself is machine-processable.
No. Adminyra eFTI is under active development. Production authority exchange stays disabled until the required interoperability, conformity-assessment and certification steps are complete.
Yes. Data mapping, sandbox API work, CMDS lifecycle design and application integration can be prepared before production Gate trust is enabled.
Start with a real freight-data mapping in the sandbox. Production Gate exchange remains locked until the certification and interoperability path is complete.